MetroCluster Manuals ( CA08871-401 )
Platform port assignments for Cisco 3232C or 36-port Cisco 9336C-FX2 switches
The port usage in a MetroCluster IP configuration depends on the switch model and platform type.
Review the following considerations before using the configuration tables:
-
The tables in this section are for Cisco 3232C switches or 36-port Cisco 9336C-FX2 switches that aren’t connecting NS224 storage.
If you have a 36-port Cisco 9336C-FX2 switch and at least one MetroCluster configuration or DR group is connecting NS224 shelves to the MetroCluster switch, use the tables in Platform port assignments for a 36-port Cisco 9336C-FX2 switch connecting NS224 storage.
-
The following tables show the port usage for site A. The same cabling is used for site B.
-
You cannot configure the switches 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 ETERNUS HX6100 or ETERNUS AX4100 in the "MetroCluster 4" group.
| The RCF file version is different to the version of the RCFfilegenerator tool used to generate the file. For example, you can generate an RCF file version 2.00 using RCFfilegenerator v1.6c. |
Choose the correct cabling table for your configuration
Use the following table to determine which cabling table you should follow.
| If your system is… | Use this cabling table… |
|---|---|
ETERNUS AX1200, ETERNUS AX1200 ASA ETERNUS AX2100 ETERNUS AX2200, ETERNUS AX2200 ASA ETERNUS AC2100, ETERNUS AC2100 ASA ETERNUS HX2200 |
Cisco 3232C or Cisco 9336C-FX2 platform port assignments (group 1) |
ETERNUS AX1300 |
Cisco 3232C or Cisco 9336C-FX2 platform port assignments (group 2) |
ETERNUS AX2300 ETERNUS HX6200 |
The table you follow depends on whether you are using a 25G (group 3a) or 100G (group 3b) Ethernet card. |
ETERNUS AX4100, ETERNUS AX4100 ASA ETERNUS HX6100 |
Cisco 3232C or Cisco 9336C-FX2 platform port assignments (group 4) |
ETERNUS AX4200 |
Cisco 3232C or Cisco 9336C-FX2 platform port assignments (group 5) |
Review the platform port assignments to cable an ETERNUS AX1200, ETERNUS AX1200 ASA, ETERNUS AX2100, ETERNUS AX2200, ETERNUS AX2200 ASA, ETERNUS AC2100, ETERNUS AC2100 ASA, ETERNUS HX2200 system to a Cisco 3232C or 9336C-FX2 switch:
Review the platform port assignments to cable an ETERNUS AX1300 system to a Cisco 3232C or 9336C-FX2 switch:
Review the platform port assignments to cable an ETERNUS AX2300 or ETERNUS HX6200 system to a Cisco 3232C or 9336C-FX2 switch using a four-port 25G Ethernet card.
| This configuration requires a four-port 25G Ethernet card in slot 4 to connect the local cluster and HA interfaces. |
Review the platform port assignments to cable an ETERNUS AX2300 or ETERNUS HX6200 system to a Cisco 3232C or 9336C-FX2 switch using a two-port 100G Ethernet card.
| This configuration requires a two-port 100G Ethernet card in slot 4 to connect the local cluster and HA interfaces. |
Review the platform port assignments to cable an ETERNUS AX4100, ETERNUS AX4100 ASA or ETERNUS HX6100 system to a Cisco 3232C or 9336C-FX2 switch:
| Using ports in the "MetroCluster 4" group requires ONTAP 9.13.1 or later. |
Review the platform port assignments to cable an ETERNUS AX4200 system to a Cisco 3232C or 9336C-FX2 switch:
