Skip to main content
NetApp Knowledge Base

New HA pair setup with "dual NIC" option not using the extra card for cluster port

  1. Last updated
  2. Save as PDF
Views:
80
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
hw
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP ASAr2
  • New setup
  • Any models with shared Cluster/HA ports and a "dual NIC" cluster port option

Issue

When setting up a new HA pair with an extra expansion card (NIC) for cluster/HA ports, the additional NIC is not auto-configured as a cluster/HA port.

The default ports for a "single NIC" configuration are both still utilized as the cluster/HA ports.

Example:

An AFF-C60 with the dual NIC cluster port option has a card in slot 2 to use e4a and e2a as the cluster/HA ports, per Hardware Universe.

c60.png

The output of "network port show" reports e4a and e4b are the current cluster ports even with the new card installed in slot 2:

Node: localhost
Speed(Mbps) Health
Port      IPspace      Broadcast Domain Link MTU  Admin/Oper  Status
--------- ------------ ---------------- ---- ---- ----------- --------
e0M       Default      -                up   1500 auto/1000   -
e2a       Default      -                up   9000 auto/100000 -
e2b       Default      -                down 9000 auto/auto   -
e3a       Default      -                up   9000 auto/10000  -
e3b       Default      -                down 9000 auto/auto   -
e3c       Default      -                up   9000 auto/10000  -
e3d       Default      -                down 9000 auto/auto   -
e4a       Cluster      -                up   9000 auto/100000 -
e4b       Cluster      -                down 9000 auto/auto   -

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.