Removing or replacing a control enclosure and its expansion enclosures
You can use the management GUI and the command-line interface (CLI) to remove or replace the control enclosure and all its attached expansion enclosures.
About this task
Important: Before you remove or replace a control enclosure and its expansion
enclosures, note that all FlashCopy mappings on the control enclosure are lost if their dependencies
are not resolved before the controller is removed.
- Make sure that your volume data is backed up.
- Determine the volumes, hosts, and arrays that are affected by the removal:
- All the volumes that belong to the I/O group and the hosts that require access to them.
- Which arrays have member drives in the enclosures.
- The list of volumes that depend on these arrays.
You can use the management GUI and command-line interface (CLI) filtering capabilities to obtain this information.
- Decide which volumes are still necessary, and plan for their migration. Consider both available storage pool capacity and the system configuration limits.
- If FlashCopy copies with their associated bitmaps are on the control enclosure that you plan to remove or replace, you must first resolve the dependencies. Otherwise, the bitmaps are lost, which causes target volumes to go offline. For help, refer to the rmnodecanister command before you remove the second node canister.
The procedure provides the necessary steps for removing or replacing volumes.