Use this procedure to move a disk cable from one node to another node.
Failure to follow this cabling procedure might introduce invalid device IDs and render the devices inaccessible.
Delete all references to the device ID 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 device ID 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 device ID path.
# scgdevs |
Add the device ID 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.
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.