To connect or disconnect a SCSI controller, use the following commands:
To connect a controller: cfgadm -c connect controller
To disconnect a controller: cfgadm -c disconnect controller
Disconnecting the controller suspends all I/O activity on the SCSI bus until you issue the cfgadm -c connect command.
The DR software initiated by the disconnect command performs some basic checking to prevent critical partitions from being disconnected. However, the software cannot detect all cases. If controllers on the system are for disks that contain critical components of the root file system, disconnecting these controllers would cause the system to hang and would require a system boot. Therefore, as a precaution, a confirmation prompt always appears after you issue the command to disconnect. The command is run only after you provide the confirmation.
Caution - Because of the risks in disconnect operations, always exercise caution to avoid causing the system to fall into an unknown state. |
The following example disconnects the SCSI controller c2 and also shows the confirmation prompt that follows the command.
# cfgadm -c disconnect c2 WARNING: Disconnecting critical partitions may cause system hang. Continue (yes/no)?
The following example shows the state of the c2 controller after it has been disconnected. The Receptacle field in the output indicates the controller's new state. Further, the devices that are attached to it are also disconnected.
# cfgadm -al Ap_Id Type Receptacle Occupant Condition c2 unavailable disconnected configured unknownThe controller is disconnected. c2::dsk/c2t0d0 unavailable disconnected configured unknownAttached device is disconnected. c3 scsi-sas connected configured unknown c3::dsk/c3t0d0 disk connected configured unknown c3::dsk/c3t1d0 disk connected configured unknown c3::dsk/c3t2d0 disk connected configured unknown c3::dsk/c3t3d0 disk connected configured unknown