Sun Storage 6130 Array
 

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

The procedure is different on the data host side whether the array is connected through a SAN or is directly attached to hosts (Directly Attached Storage - DAS).
On a SAN environment, be careful if the type of zoning used is a WWN-based zoning. You will have to reconfigure it after the HBA replacement in order to get the array to recognize the new WWN.
A data host is a host which is connected to the array using FC connections.
A management host is a host that is used to administer the array through BUI (Browser User Interface) or CLI.
Procedure :
===========
1) Put the HBA offline :
------------------------
On a SAN environment, type the following command on the data host where the HBA needs to be replaced :
# cfgadm -c unconfigure cX
where cX is the controller number of the faulty HBA.
If there are multiple arrays connected to the HBA (SAN environment), you will have to do the following actions for each array.
2) Delete the initiator using the BUI :
---------------------------------------
If you use the BUI, do the following. If you use the CLI, go to the next step.
Launch the Web Console software : in a browser, type :
https://management_host_IP_address:6789
Enter login and password.
Launch Sun StorEdge 6130 Configuration Service.
Click on the array that is connected to the HBA.
Go to Physical.
-> select the initiator that will be physically changed.
-> keep track of its name, the host to which it belongs and the OS type.
-> click on Delete.
Go to step 3.
2) Delete the initiator using the CLI :
---------------------------------------
On the management host type :
Login with adequate username.
# /opt/se6x20/cli/bin/sscs login -h localhost -u username
Enter password
# /opt/se6x20/cli/bin/sscs list -a arrayname initiator
Verify the name of the appropriate initiator
# /opt/se6x20/cli/bin/sscs list -a arrayname initiator initiator-id
Keep track of its name, the host to which it belongs and the OS type
# /opt/se6x20/cli/bin/sscs delete -a arrayname initiator initiator-id
Example :
# /opt/se6x20/cli/bin/sscs login -h localhost -u root
Password :
# /opt/se6x20/cli/bin/sscs list array
Array: se6130a-crm-a-epar02
# /opt/se6x20/cli/bin/sscs list -a se6130a-crm-a-epar02 initiator
Initiator: s4u-280ra-c6
Initiator: s4u-280ra-c8
# /opt/se6x20/cli/bin/sscs list -a se6130a-crm-a-epar02 initiator s4u-280ra-c6
Initiator: s4u-280ra-c6
WWN:      21:01:00:E0:8B:2A:46:4A
Host:     s4u-280ra
OS Type:  Solaris (with Traffic Manager)
# /opt/se6x20/cli/bin/sscs delete -a se6130a-crm-a-epar02 initiator s4u-280ra-c6
# /opt/se6x20/cli/bin/sscs list -a se6130a-crm-a-epar02 initiator
Initiator: s4u-280ra-c8
4) Change the HBA on the data host :
------------------------------------
Use the corresponding HBA and/or host type documentation in order to have the correct procedure and to see if a reconfiguration boot must be performed.
Once the HBA has been changed and the data host is up, connect the fibre and type the following to see if the new HBA views all attached components :
# cfgadm -al
Example :
# cfgadm -al
...
c6                             fc-fabric    connected    unconfigured   unknown
c6::200600a0b8170e2c           disk         connected    unconfigured   unknown
If not, verify that the cable is correctly plugged in using LEDs on the HBA side and the switch side (SAN) or controller side (DAS).
In order to get the new WWN of the controller, type :
# luxadm -e dump_map /dev/cfg/cX
The new WWN is the one indicated in the line that ends with : (Unknown Type,Host Bus Adapter).
Be careful to note the port WWN and not the node WWN.
Example :
# luxadm -e dump_map /dev/cfg/c6
Pos  Port_ID Hard_Addr Port WWN         Node WWN         Type
1    10300   0         200600a0b8170e2c 200600a0b8170e2b 0x0  (Disk device)
2    10f00   0         210100e08b32e14d 200100e08b32e14d 0x1f (Unknown Type,Host Bus Adapter)
If there are multiple arrays connected to the HBA (SAN environment), you will have to do the following actions for each array.
5) Recreate the initiator on the BUI :
--------------------------------------
If you use the BUI, do the following. If you use the CLI, go to the next step.
Launch the Web Console software : in a browser, type :
https://management_host_IP_address:6789
Enter login and password.
Launch Sun StorEdge 6130 Configuration Service.
Click on the array that is connected to the HBA.
If there are multiple arrays connected to the HBA (SAN environment), you will have to do the following for each array.
Go to Physical
-> click on New.
-> enter the initiator name, host name and host type that were defined for the previous initiator.
-> select the new WWN in the scroll bar menu. If it doesn't show up in a SAN environment, check for zoning configuration.
-> click on OK.
Go to step 7.
6) Recreate the initiator using the CLI :
-----------------------------------------
On the management host type :
Login with adequate username.
# /opt/se6x20/cli/bin/sscs login -h localhost -u username
Enter password
Recreate the initiator :
# /opt/se6x20/cli/bin/sscs create -a arrayname -w wwn -h host -o os-type initiator initiator-id
# /opt/se6x20/cli/bin/sscs list -a arrayname initiator
Verify that the initiator has been created.
# /opt/se6x20/cli/bin/sscs list -a arrayname initiator initiator-id
Verify that the settings are correct.
Example :
# /opt/se6x20/cli/bin/sscs login -h localhost -u username
Password :
# /opt/se6x20/cli/bin/sscs create -a se6130a-crm-a-epar02 -w 210100e08b32e14d -h s4u-280ra -o solaris initiator s4u-280ra-c6
# /opt/se6x20/cli/bin/sscs list -a se6130a-crm-a-epar02 initiator
Initiator: s4u-280ra-c6
Initiator: s4u-280ra-c8
# /opt/se6x20/cli/bin/sscs list -a se6130a-crm-a-epar02 initiator s4u-280ra-c6
Initiator: s4u-280ra-c6
WWN:      21:01:00:E0:8B:32:E1:4D
Host:     s4u-280ra
OS Type:  Solaris (with Traffic Manager)
7) Place the initiator online :
-------------------------------
- SAN : # cfgadm -c configure cX
# luxadm -e forcelip /dev/cfg/cX (optional)
- DAS : # luxadm -e forcelip /dev/cfg/cX
Verify that all LUNs are correctly seen using :
# cfgadm -al -o show_FCP_dev cX
Example :
# cfgadm -al -o show_FCP_dev c6
Ap_Id                          Type         Receptacle   Occupant     Condition
c6                             fc-fabric    connected    configured   unknown
c6::200600a0b8170e2c,0         disk         connected    configured   unknown
c6::200600a0b8170e2c,10        disk         connected    configured   unknown
c6::200600a0b8170e2c,98        disk         connected    configured   unknown
c6::200600a0b8170e2c,240       disk         connected    configured   unknown
See if all is ok at format or using the luxadm display command if SSTM is used.

This solution has no attachment