Disconnecting the existing DR group from the fabric
PDF of this doc site
Install a fabric-attached MetroCluster
Cable a fabric-attached MetroCluster configuration
- Install and cable MetroCluster components
- Configure hardware for sharing a Brocade 6510 FC fabric during transition
Plan and install a MetroCluster configuration with array LUNs
- Install and cable the MetroCluster components in a configuration with array LUNs
- Cable a fabric-attached MetroCluster configuration
Install a MetroCluster IP configuration
- Configure the MetroCluster hardware components
Install a stretch MetroCluster configuration
- Cable a two-node SAS-attached stretch MetroCluster configuration
- Cable a two-node bridge-attached stretch MetroCluster configuration
- Perform switchover, healing, and switchback
Maintain the MetroCluster components
- Hot add storage to a MetroCluster FC configuration
Transition from MetroCluster FC to MetroCluster IP
- Transition nondisruptively from a MetroCluster FC to a MetroCluster IP configuration (ONTAP 9.8 and later)
Upgrade, refresh, or expand the MetroCluster configuration
- Expand a two-node MetroCluster FC configuration to a four-node configuration
- Install a fabric-attached MetroCluster
You must disconnect the existing controller modules from the FC switches in the fabric.
This task must be performed at each MetroCluster site.
Disable the HBA ports that connect the existing controller modules to the switch fabric undergoing maintenance:
storage port disable -node node-name -port port-number
On the local FC switches, remove the cables from the ports for the existing controller module’s HBA, FC-VI, and ATTO bridges.
You should label the cables for easy identification when you re-cable them. Only the ISL ports should remain cabled.