Skip to main content
NetApp Knowledge Base

CONTAP-355057: MetroCluster commands listing HA partner connection with iWARP adapter instead of RoCE

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

Issue

On platforms with separate MetroCluster IP (iWARP) and HA (RoCE) interconnects, some of the MetroCluster commands may display HA Partner entries after a MetroCluster FC-to-IP transition.
Example:
DR                    Source          Destination
Group Cluster Node    Network Address Network Address Partner Type Config State
----- ------- ------- --------------- --------------- ------------ ------------
1     ClusterA
              Check Result: warning
              Ping Error: Unable to transmit a "ping" packet from the network address "192.168.1.1" to "192.168.1.2" on node "ClusterA-01" in cluster "ClusterA". Reason: ping: bind: Can't assign requested address
              ClusterA-01
                 Home Port: e1b-20
                      -               192.168.1.2  HA Partner   completed
 
Another effect of this is the output of "metrocluster configuration-settings calibration show" contains a loop
Example: 
 
 
cluster::*> metrocluster configuration-settings calibration show
Error: show failed: Loop detected in next() for table metrocluster_calibration. Next on "3 172.11.22.0 4294967295 85f6f3e5-d02b-11e6-9f68-00a01212d1a7 e1a" returned "3 172.17.21.0 2
       a6c467d0-da36-affe-85ba-d0abbac4d4ca e2a-10".

 

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.