Skip to main content
NetApp Knowledge Base

Management port - e0M down

  1. Last updated
  2. Save as PDF
Views:
2,829
Visibility:
Public
Votes:
3
Category:
fas-systems
Specialty:
hw
Last Updated:

Applies to

  • FAS systems
  • AFF systems

Issue

  • SP Ethernet Link is down in SYSCONFIG-A of ASUP.

    Service Processor           Status: Online
        Firmware Version:   5.1P4
        Mgmt MAC Address:   00:A0:98:BD:70:10
        Ethernet Link:      down, 10Mb, half duplex
        Using DHCP:         no

  • Port e0M is also down in NETWORK-PORTS.XML of ASUP.
  • The e0M port which hosts the management LIF is down and the following messages are reported in event logs:

Wed Mar 24 08:40:25 IST [Node-name: mgmt_port_link_status_poll: netif.linkDown:info]: Ethernet e0M: Link down, check cable.
Wed Mar 24 08:40:35 IST [Node-name: vifmgr: vifmgr.port.monitor.failed:error]: The "link_flapping" health check for port e0M (node XXXX) has failed. The port is operating in a degraded state.
Wed Mar 24 08:41:05 IST [Node-name: vifmgr: vifmgr.portdown:notice]: A link down event was received on node Node-name, port e0M.

  • The issue remains after a cable swap with the one in the partner
  • The issue remains when connecting a laptop directly to the port
  • The issue remains after a power cycling service processor (SP)

 

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.