permalink | sidebar | keywords | summary |
---|---|---|---|
install-ip/port_usage_3232c_9336c.html |
sidebar |
cabling, cable, component, link, site, management, network, networks, hardware, component, switch, cluster, connection, management, data, configuring, configure |
The port usage in a MetroCluster IP configuration depends on the switch model and platform type. |
The port usage in a MetroCluster IP configuration depends on the switch model and platform type.
Review these considerations before using the tables:
-
The following tables show the port usage for site A. The same cabling is used for site B.
-
The switches cannot be configured with ports of different speeds (for example, a mix of 100 Gbps ports and 40 Gbps ports).
-
If you are configuring a single MetroCluster with the switches, use the MetroCluster 1 port group.
Keep track of the MetroCluster port group (MetroCluster 1, MetroCluster 2, MetroCluster 3, or MetroCluster 4). You will need it when using the RcfFileGenerator tool as described later in this configuration procedure.
-
The RcfFileGenerator for MetroCluster IP also provides a per-port cabling overview for each switch.
Use this cabling overview to verify your cabling.
-
RCF file version v2.10 or later is required for 25G breakout mode for MetroCluster ISLs.
-
ONTAP 9.13.1 or later and RCF file version 2.00 are required to use a platform other than FAS8200 or AFF A300 in the "MetroCluster 4" group.
When cabling more than one MetroCluster configuration to a Cisco 3132Q-V switch, you must cable each MetroCluster according to the appropriate table. For example, if cabling a FAS2750 and an AFF A700 to the same Cisco 3132Q-V switch. Then you cable the FAS2750 as per "MetroCluster 1" in Table 1, and the AFF A700 as per "MetroCluster 2" or "MetroCluster 3" in Table 2. You cannot physically cable both the FAS2750 and the AFF A700 as "MetroCluster 1".