Where to Go From Here
If you did not follow this procedure correctly, you might see an error the next time you run the scdidadm -r command or the scgdevs command. If you see an error message that says did reconfiguration discovered invalid diskpath, go to How to Update Sun Cluster Software to Reflect Proper Device Configuration.
How to Move a Disk Cable From One Node to Another Node
Use this procedure to move a disk cable from one node to another node.
Caution - Failure to follow this cabling procedure
might introduce invalid device IDs (DIDs) and render the devices inaccessible.
Delete all references to the DID device path that you are removing from all volume manager and data service configurations.
For more information, see your Sun Cluster data services collection and your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Stop all I/O to the affected disk(s).
For more information, see your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Unplug the cable from the old node.
From the old node, unconfigure all drives that are affected by the recabling.
# cfgadm
Or reboot the old node.
# reboot -- -r
From the old node, update the Solaris device link.
# devfsadm -C
From the old node, update the DID device path.
# scdidadm -C
Connect the cable to the new node.
From the new node, configure the drives in the new location.
# cfgadm
Or reboot the new node.
# reboot -- -r
From the new node, create the new Solaris device links.
# devfsadm
From the new node, add the new DID device path.
# scgdevs
Add the DID device path on the new node to any volume manager and data service configurations that are required.
When you configure data services, check that your node failover preferences are set to reflect the new configuration.
For more information, see your Sun Cluster data services collection and your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
Where to Go From Here
If you did not follow this procedure correctly, you might see an error the next time you run the scdidadm -r command or the scgdevs command. If you see an error message that says did reconfiguration discovered invalid diskpath, go to How to Update Sun Cluster Software to Reflect Proper Device Configuration.
How to Update Sun Cluster Software to Reflect Proper Device Configuration
If you see the following error when you run the scdidadm -r command or the scgdevs command, the Sun Cluster software does not reflect the proper device configuration because of improper device recabling.
did reconfiguration discovered invalid diskpath. This path must be removed before a new path can be added. Please run did cleanup (-C) then re-run did reconfiguration (-r). |
Use this procedure to ensure that the Sun Cluster software becomes aware of the new configuration and to guarantee device availability.
Ensure that your cluster meets the following conditions.
The cable configuration is correct.
The cable that you are removing is detached from the old node.
The old node is removed from any volume manager or data service configurations that are required.
For more information, see your Sun Cluster data services collection and your Solstice DiskSuite/Solaris Volume Manager or VERITAS Volume Manager documentation.
From all nodes, one node at a time, unconfigure all drives.
# cfgadm
Or reboot all nodes, one node at a time.
# reboot -- -r
From all nodes, one node at a time, update the Solaris device link.
# devfsadm -C
From all nodes, one node at a time, update the DID device path.
# scdidadm -C
From all nodes, one node at a time, configure all drives.
# cfgadm
Or reboot all nodes, one node at a time.
# reboot -- -r
From any node, add the new DID device path.
# scgdevs
From all nodes that are affected by the recabling, verify that SCSI reservations are in the correct state.
# scdidadm -R device