Skip to main content
NetApp Knowledge Base

Why is ASUP not generated for certain NIC cable disconnection tests?

Views:
102
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
core
Last Updated:

Applies to

  • ONTAP 9
  • AutoSupport (ASUP)

Answer

During network cable disconnection tests, ASUP is not generated for certain NIC disconnections due to the default settings on ONTAP.
 
  • Behavior observed:
  1. Service(Data) NIC Cable Disconnection  - No ASUP message is generated.
EMS log:
[node: intr: netif.linkDown:info]: Ethernet e2a: Link down, check cable.
[node: intr: net.ifgrp.lacp.link.inactive:error]: ifgrp a0a, port e2a has transitioned to an inactive state. The interface group is in a degraded state.
[node: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node, port e2a.
  1. Cluster-Interconnect NIC Cable Disconnection - No ASUP message is generated.
EMS log:
[node: intr: netif.linkDown:info]: Ethernet e1a: Link down, check cable.
[node: vifmgr: vifmgr.portdown:notice]: A link down event was received on node node, port e1a.
[node: vifmgr: vifmgr.clus.linkdown:EMERGENCY]: The cluster port e1a on node node has gone down unexpectedly.
[node: vifmgr: vifmgr.lifmoved.linkdown:notice]: LIF node_clus2 (on virtual server 4294967293), IP address 169.254.254.83, is being moved to node node, port e0a.
[node: vifmgr: vifmgr.reach.noreach:notice]: Network port e1a on node node cannot reach its expected broadcast domain Cluster:Cluster. No other broadcast domains appear to be reachable from this port.
  1. HA-Interconnect NIC Cable Disconnection - ASUP message "HA INTERCONNECT DOWN" is generated.
EMS log:
[node: statd: ic.HAInterconnectDown:error]: HA interconnect: Interconnect down for 2 minutes: link0 down
[node: statd: callhome.hainterconnect.down:alert]: Call home for HA INTERCONNECT DOWN due to link0 down.
  1. Disk Shelf Connection NIC Cable Disconnection - ASUP message "DISK REDUNDANCY FAILED" is generated.
EMS log:
[node: intr: netif.linkDown:info]: Ethernet e4a-30: Link down, check cable.
[node: intr: nvmeof.timeout:notice]: Timeout on subnqn nqn.2014-08.org.nvmexpress.discovery, controller ID 9, qpair ID 0, sequence number 3704.
[node: intr: nvmeof.timeout:notice]: Timeout on subnqn nqn.2014-08.org.nvmexpress:1b96:1b96:241163800956:X4032WCOFB15TNVE, controller ID 9, qpair ID 0, sequence number 2017.
[node: intr: nvmeof.timeout:notice]: Timeout on subnqn nqn.2014-08.org.nvmexpress:1b96:1b96:241025800131:X4032WCOFB15TNVE, controller ID 9, qpair ID 0, sequence number 2066.
[node: dsa_disc: callhome.dsk.redun.fault:error]: Call home for DISK REDUNDANCY FAILED.
 
  • Reason:
    • With disconnecting the HA-Interconnect NIC and Disk Shelf NIC reports the "hainterconnect.down" and "dsk.redun.fault" are defined to send ASUP as below:
ontap914::> system node autosupport trigger show -fields autosupport-message,to,noteto -node ontap914-01  -autosupport-message *hainterconnect.down*
node        autosupport-message to      noteto
----------- ------------------- ------- -------
ontap914-01 hainterconnect.down enabled enabled
 
ontap914::> system node autosupport trigger show -fields autosupport-message,to,noteto -node ontap914-01  -autosupport-message *dsk.redun*
node        autosupport-message to      noteto
----------- ------------------- ------- -------
ontap914-01 dsk.redun.fault     enabled enabled
  • But disconnecting the Service(Data) NIC and Cluster-Interconnect NIC reports netif.linkDown and vifmgr.portdown etc are not defined to send ASUP:

ontap914::> system node autosupport trigger show -fields autosupport-message,to,noteto -node ontap914-01  -autosupport-message *net*        

node        autosupport-message to      noteto
----------- ------------------- ------- -------
ontap914-01 clus.net.degraded   enabled enabled
ontap914-01 mcc.network.stats   disabled disabled
ontap914-01 netif.fatal.error   enabled enabled
ontap914-01 netif.init.failed   enabled enabled
ontap914-01 netif.uncorEccError enabled enabled
ontap914-01 netinet.dup.clustIP enabled enabled
6 entries were displayed.

ontap914::> system node autosupport trigger show -fields autosupport-message,to,noteto -node ontap914-01  -autosupport-message *vifmgr*
There are no entries matching your query.

Additional Information

additionalInformation_text
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.