The alarm 'Edge node NIC eth0 link is down' opens and resolves after 3 seconds.

Products

• VMware NSX

Issue/Introduction

The "Edge node NIC eth0 link is down" alarm is triggered and clears approximately three seconds later. The NSX Edge VM's appears up in vSphere.

• The following events are recorded in /var/log/syslog:
  
  yyyy-mm-ddThh:mm:ss.sssZ <edge-name> NSX 1162 - [nsx@6876 comp="nsx-edge" subcomp="nsx-sha" username="nsx-sha" level="CRITICAL" eventFeatureName="edge_health" eventType="edge_nic_link_status_down" eventSev="critical" eventState="On"] Edge node NIC eth0 link is down.
  yyyy-mm-ddThh:mm:ss.sssZ <edge-name> NSX 1162 - [nsx@6876 comp="nsx-edge" subcomp="nsx-sha" username="nsx-sha" level="CRITICAL" eventFeatureName="edge_health" eventType="edge_nic_link_status_down" eventSev="critical" eventState="Off"] Edge node NIC eth0 link is up.

• In /var/log/syslog, the command sudo cat /sys/class/net/eth0/operstate time out just before the alarm occurred.

  yyyy-mm-ddThh:mm:ss.sssZ <edge-name> NSX 1225 - [nsx@6876 comp="nsx-edge" subcomp="nsx-sha" username="nsx-sha" level="INFO" s2comp="fork-executor-1"] Exception caught when running cmd '{'cmd': ['sudo', 'cat', '/sys/class/net/eth0/operstate'], 'input': None, 'shell': False, 'timeout': 4, 'check_return': True, 'env': None, 'type': 0, 'proc_tree': True, 'timestamp': 392962.240507027, 'seq': 106666}': {'seq': 106666, 'type': 0, 'executor': 1, 'timestamp': 392962.24113893, 'execute_time': 10.7467318289564, 'stdout': b'up\n', 'stderr': b'', 'exception': TimeoutExpired(['sudo', 'cat', '/sys/class/net/eth0/operstate'], 4)}

Environment

VMware NSX-T Data Center (3.x)

VMware NSX (4.x)

Cause

The sudo cat /sys/class/net/eth0/operstate check triggers a link-down alarm if it returns down or encounters an exception. If the command cannot complete, it indicates that the NSX Edge was unstable at the time.

Resolution

Check for infrastructure issues such as temporary CPU contention or degraded storage performance.

If you believe you have encountered this issue, please open a support request with Broadcom Support. For more information, see Creating and managing Broadcom support cases.