Sun Storage 6920 System
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 6xxx Arrays
 

The purpose of this document is to provide basic steps for initiator deletion for the 6920 array, via the Browser User Interface(BUI) or sscs Command Line Interface(CLI).

Content will be limited to a basic usage using the CLI or BUI interfaces for deleting initiators, and provide help with some usage failure scenarios for this activity. Consider reviewing some of the following documents if you are looking to perform actions beyond the scope of this document:

• Best Practices for the Sun StorEdge 6920 System, Version 3.0.1
• Sun StorEdge 6920 System CLI Quick Reference Guide, Release 3.0
• <Document: 1009915.1> Troubleshooting Sun StorEdge[TM] 6920 Configuration Problems
• Sun StorEdge 6920 System Administration Guide For the Browser Interface Management Software, Release 3.0

To permanently delete an Initiator, the "State" must be Free, and the
"Status" must be Offline. Reference document <Document: 1011349.1> : Validating Mapping Deletion for Volumes and Initiators for a Sun StorEdge[TM] 6290.

• If the State is Allocated, you must delete all mappings to the initiator, prior to deletion. Reference document <Document: 1005606.1> : Validating Volume Mapping Deletion for a Sun StorEdge[TM] 6920.
• If the State is Free and the Status is Online, the initiator cannot be deleted unless 6920 is prevented from seeing the initiator WWN. This can be done by shutting down the host, unplugging a cable, or rezoning the Storage Area Network(SAN). The initiator can be deleted, but will be listed again when the Service Processor probes the 6920 after 5 to 10 minutes.
• If the State is Allocated and the Status is Offline, you will not be able to delete the initiator, unless you can make the HBA available to the storage ports. This status typically occurs due to moving an HBA connection to a different 6920 port, without unmapping volumes first. If you cannot make the HBA accessible again, please go to Step D.
• If the State is Free and the Status is Offline, go to Step B.

B. Basic Usage Using Browser or SSCS interfaces

SSCS

sscs delete initiator <initiator_name>

An example:

sscs delete initiator testing

BUI

1. Click on Configuration Services or Common Array Manager link.
2. Click on Physical Storage Tab or Menu tree
3. Click on Initiators tab or Menu tree
4. Check the box next to the initiator name
5. Click the Delete button
6. Click OK to confirm.

At this point the Pop-Up window will disappear, and the main browser screen will refresh, and a success or failure message will be displayed in the Volume Summary page. The initiator will no longer be listed.

• If you received a failure notification, continue to Step C.
• If you received a success notification, you have validated that initiator deletion is complete.

C. Deletion Failure

Please review the following list for a failure message and corresponding action. Please follow the action that describes your symptom.

BUI
Message:
<initiator> - You cannot delete the specified initiator because it is in use.

Action:
You must delete all mappings to the initiator, prior to deletion. Reference document <Document: 1011349.1> : Validating Mapping Deletion for Volumes and Initiators for a Sun StorEdge[TM] 629.

Message:
An error occurred. Please contact your system administrator

Action:
Please go to Step D.

SSCS

Message:
<initiator>: Online initiators cannot be deleted

Action:
Remove connection via SAN to this initiator. The 6920 can still see this HBA WWN.

Message:
You cannot delete the specified initiator because it is in use.; operation failed.

Action:
The initiator is still mapped to at least one volume. Remove the mapping and try again. Reference document <Document: 1011349.1> : Validating Mapping Deletion for Volumes and Initiators for a Sun StorEdge[TM] 6290.

Message:
Error: The operation failed.

Action:
Please go to Step D.

D. Data Collection

Please collect the following data:

• 6920 Solution Extract, Reference document <Document: 1003756.1> : How to collect an extractor from a Sun StorEdge[TM] 6920 (2.x and 3.x)
• The message given by SSCS or BUI(screen capture if possible)
• The command used, if by SSCS
• The output of:

sscs list initiator
sscs list initiator <initiator name>

Once this information is collected, please contact Sun Support

Sun Support

E. Validate that FC Server status is not Allocated Offline.

The fc server status can be checked in the solution extract by looking at extract_path/DSP/dsp00/show_fc_servers or by running show fc-servers on the DSP.

============================
|  COMMAND: show fc-servers
============================
+-----------------------------------------------------------------------------+
|                         >> FIBRECHANNEL SERVERS <<                          |
+-----------------------------------------------------------------------------+
|SVSD:                 |                    |                |                |
|  Server Name         | Instance           | State          | Status         |
|----------------------+--------------------+----------------+----------------|
|SVSD:DEFAULT          |                    |                |                |
|  rigel_hba1          | rigel_hba1/3/3     | Allocated      | Offline        |
|                      | rigel_hba1/4/1     | Allocated      | Offline        |
|                      | rigel_hba1/2/1     | Allocated      | Online         |

The FC Server(Initiator) is named on the left(bold).  Each FC server can have multiple 
instances, which indicate which SIO port on the DSP the particular FC Server has been seen.
In the case above, the initiator rigel_hba1 were plugged into SIO Slot 3 port 3, 
SIO Slot 4 port 1, and SIO Slot 2 port 1.  

In order for an Initiator to be deleted by the User Interface, all of the FC Server instances
for that Initiator must have the same state.

• If the State and Status of ANY of the FC Server Instances for the Initiator are Allocated Offline Go to Step F.
• If the State and Status of the FC Server Instances are Free Online, the customer needs to either unplug the Cable to the port, shut the host down, or zone the
  Initiator WWN away from the DSP ports on the SAN.  Otherwise the Initiator will continue to reappear.
• If the State and Status of the FC Server  the FC Server Instances are Free Offline, and the Initiator can't be deleted through the User Interface, Go to Step G.
• If the State and Status of the FC Server Instances are Allocated Online, there is still a volume mapping that needs to be deleted.

1. Allow the HBA WWN to be seen by all of the instances listed in show fc servers for that Initiator.  Recheck the status of the initiator and delete following Step A.
2. Cold boot the DSP by logging into the DSP and issuing reboot now.  This will require an outage.
   
3. Log into the DSP, enter config mode, and run no storage fc-server initiator_name/SIO_SLOT/SIO_PORT :

G.  Validate that services are running properly on the SP

Reference document <Document: 1007129.1> : Validating Services on a Sun StorEdge 6920 Service Processor

H. Escalate

Provide the following:

• Description of what is not being displayed properly


• Results of Step E.


• Results of Step F.


• Location of everything in Step D
  

This solution has no attachment