Skip to main content
ONTAP MetroCluster

Cabling the controller peering, data, and management ports

Contributors netapp-pcarriga netapp-martyh netapp-aoife
PDFs

You must cable the controller module ports used for cluster peering, management and data connectivity.

This task must be performed on each controller module in the MetroCluster configuration.

At least two ports on each controller module should be used for cluster peering.

The recommended minimum bandwidth for the ports and network connectivity is 1 GbE.

  1. Identify and cable at least two ports for cluster peering and verify they have network connectivity with the partner cluster.

    Cluster peering can be done on dedicated ports or on data ports. Using dedicated ports provides higher throughput for the cluster peering traffic.

    Cluster and SVM peering express configuration

  2. Cable the controller's management and data ports to the management and data networks at the local site.

    Use the installation instructions for your platform at the ONTAP Hardware Systems Documentation.

    Note MetroCluster IP systems do not have dedicated high-availability (HA) ports. Depending on your platform, HA traffic is served using the MetroCluster, local cluster, or shared cluster/MetroCluster interface. When using ONTAP Hardware Systems Documentation to install your platform, you should not follow the instructions to cable the cluster and HA ports.