Skip to main content
NetApp Knowledge Base

InterconnectAdapterOfflineAlert FCVI port 2x in a two-node stretch MetroCluster

  1. Last updated
  2. Save as PDF
Views:
80
Visibility:
Public
Votes:
0
Category:
metrocluster
Specialty:
metrocluster
Last Updated:

Applies to

  • 2 Node
  • Stretch MetroCluster
  • ONTAP 9
  • FC-VI errors

Issue

  • InterconnectAdapterOfflineAlert reported on FCVI port 2a in a two-node bridge-attached stretch MetroCluster with no switches.
  •  One node panics with message:

PANIC: nested machine check exception detected on CPU 12, no coredump will be generated.

  •  System Health Alert shows:
::> system health alert show
Node: node-01
Alert ID: InterconnectAdapterOfflineAlert
Resource: fcvi_device_0
Severity: Major
Indication Time: Tue Mar 18 09:18:56 2025
Suppress: false
Acknowledge: false
Probable Cause: Physical link on port 2a is offline.
Possible Effect: DR protection of NVRAM mirror might be compromised.
 Corrective Actions: 
1. Ensure that the FC-VI link has not been tampered with.
2. Verify that the physical status of the FC-VI adapter is "Up" by using the command "metrocluster interconnect adapter show".
3. If the configuration includes fabric switches, ensure that they are properly cabled and configured.
 
  • Event logs show the following messages:

Cluster-1:

Tue Aug 20 12:55:29 +0000 [node-01A: ispfcvi2500_port2: fcvi.update.link.state:notice]: FC-VI adapter: Physical link is down on port 2a.
Cluster-2:
Tue Aug 20 12:55:30 +0000 [node-02A: ispfcvi2500_port2: fcvi.update.link.state:notice]: FC-VI adapter: Physical link is down on port 2a.

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.