Using TDM/xWDM and encryption equipment with MetroCluster IP configurations
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
- Install and Configure MetroCluster Tiebreaker
- 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 should be aware of certain considerations for using multiplexing equipment in the MetroCluster IP configuration.
These considerations apply only to direct, dedicated MetroCluster back-end links and switches, not links shared with non-MetroCluster traffic.
The Hardware Universe tool provides some notes about the requirements that TDM/xWDM equipment must meet to work with a MetroCluster IP configuration.
Using encryption on WDM or external encryption devices
When using encryption on WDM devices in the MetroCluster IP configuration, your environment must meet the following requirements:
The external encryption devices or DWDM equipment must have been certified by the vendor with the switch in question.
The certification should cover the operating mode (such as trunking and encryption).
The overall end-to-end latency and jitter, including the encryption, cannot be above the maximum stated in the IMT or in this document.
Any SFPs or QSFPs supported by the equipment vendor are supported for the MetroCluster ISLs. SFPs and QSFPs can be acquired from NetApp or the equipment vendor.
Considerations for ISLs
The ISLs on one fabric should all be the same speed and length.
The ISLs on one fabric should all have the same topology. For example, they should all be direct links, or if the configuration uses WDM, then they should all use WDM.
If you are sharing ISLs with a non-MetroCluster network, you must follow the guidelines in the section Considerations for sharing private layer 2 networks.
The maximum supported difference in distance between fabric 1 and fabric 2 is 20 km.