In the Sun Cluster 3.0 Hardware Guide, the following procedures are incorrect or do not exist:
The task map "Configuring StorEdge A3500 Disk Drives" in Chapter 7 contains an error. The task "Increase the drive capacity of a LUN" is titled incorrectly. You cannot increase the drive capacity of a LUN. You can, however, increase the size of the drive group. Therefore, you do not need to remove the LUN from any diskset or disk group. The task should read: "Increase the size of the drive group. Follow the same procedure used in a non-cluster environment."
No procedures are documented in the Sun Cluster 3.0 GA AnswerBook for recabling disks without introducing redundant disk paths in the Cluster Configuration Repository (CCR).
When you recable devices within a cluster, the cluster must become aware of the new device configuration. To ensure that the cluster becomes aware of the new configuration and to guarantee device availability, use the following procedures:
Use the following procedure to move a disk cable to a new adapter within a node.
Quiesce all I/O to the affected disk(s).
Unplug the cable from the old adapter.
Run the cfgadm(1M) command on the local node to unconfigure all drives affected by the move.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the devfsadm -C command on the local node to clean up the Solaris device link.
Run the scdidadm -C command on the local node to clean up the DID device path.
Connect the cable to the new adapter.
Run the cfgadm command on the local node to configure the drives in the new location.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the scgdevs command to add the new DID device path.
Use the following procedure to move a disk cable from one node to another node.
Delete all references to the path you wish to remove from all volume manager and data service configurations.
Quiesce all I/O to the affected disk(s).
Unplug the cable from the old node.
Run the cfgadm command on the old node to unconfigure all drives affected by the move.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the devfsadm -C command on the old node to clean up the Solaris device link.
Run the scdidadm -C command on the old node to clean up the DID device path.
Connect the cable to the new node.
Run the cfgadm command on the new node to configure the drives in the new location.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the devfsadm command on the new node to create the new Solaris device links.
Run the scgdevs command on the new node to add the new DID device path.
Add the path on the new node to any required volume manager and data service configurations.
When configuring data services, check that your node failover preferences are set to reflect the new configuration.
If the preceding procedures are not followed correctly, an error might be logged the next time you run the scdidadm -r command or the scgdevs command. To update the cluster software to reflect the proper device configuration, perform the following steps.
Make sure cable configuration is as you want it to be. Make sure the cable is detached from the old node.
Make sure the old node is removed from any required volume manager or data service configurations.
Run the cfgadm command on the old node to unconfigure all drives affected by the move.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the devfsadm -C command on the node from where you removed the cable.
Run the scdidadm -C command on the node from where you removed the cable.
Run the cfgadm command on the new node to configure the drives in the new location.
Or, reboot the node by using the following command.
# reboot -- -r |
Run the scgdevs command on the new node to add the new DID device path.
Run the scdidadm -R device command on the new node to make sure that SCSI reservations are in the correct state.