Skip to main content
NetApp Knowledge Base

Data port goes down after node reboot

  1. Last updated
    Aug 5, 2024
  2. Save as PDF
Views:
1,172
Visibility:
Public
Votes:
1
Category:
aff-series
Specialty:
hw
Last Updated:
8/5/2024, 11:21:53 AM

Applies to

  • ONTAP 9
  • AFF Systems
  • FAS Systems

Issue

  • A data port is down after a reboot of the node:
cluster::> system node run -node Node-01 -command sysconfig -a

slot 1: 1G/10G Ethernet Controller CNA EP 8324
(Multiple Dual-port, QLogic CNA 8324(8362) rev. 2)
e1a MAC Address:    02:a0:98:e9:c6:72 (auto-10g_sr-fd-up)
e1b MAC Address:    00:a0:98:e9:bd:f0 (auto-unknown-fd-down)

  • The following messages are seen in the event logs:

[Node-01: intr: netif.linkDown:info]: Ethernet e1b: Link down, check cable.
[Node-01: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-01, port e1b.
[Node-01: vifmgr: vifmgr.reach.unassn:notice]: Network port e1b on node Node-01 is not assigned to any broadcast domain. No broadcast domains appear to be reachable from this port.
[Node-01: vifmgr: vifmgr.reach.skipped:notice]: Network port e1b on node Node-01 was not scanned for reachability because it was administratively or operationally down at the time of the scan.

  • The port remains down even after reseating the SFP and cable connected to it.

 

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.