SNMP Tarp "enterprises.3183.1.1.0.356100" is received.
search cancel

SNMP Tarp "enterprises.3183.1.1.0.356100" is received.

book

Article ID: 422813

calendar_today

Updated On:

Products

VMware vSphere ESX 8.x VMware vSphere ESXi

Issue/Introduction

The ESX host sent the following SNMP trap.

SNMPv2-MIB::snmpTrapOID.0 SNMPv2-SMI::enterprises.3183.1.1.0.356100

SNMPv2-SMI::enterprises.3183.1.1.1 "## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
   ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##
  ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ##"

SNMPv2-SMI::enterprises.3183.1.1.2.0 "Network controller 1 port 3 function 0 with physical network address ##:##:##:##:##:##:## - Link down"

SNMP-COMMUNITY-MIB::snmpTrapAddress.0 ###.###.###.###

SNMP-COMMUNITY-MIB::snmpTrapCommunity.0 "####"

SNMPv2-MIB::snmpTrapEnterprise.0 SNMPv2-SMI::enterprises.3183.1.1

Environment

VMware vSphere ESX

Cause

The trap resulted from a Link Down event on the ESX host's Physical Network Interface (PNIC).

Resolution

  1. Identify the Source Host:

    Use the SNMP-COMMUNITY-MIB::snmpTrapAddress.0 OID (e.g., ###.###.###.###) in the received trap to determine the IP address of the ESX host that sent the alert.

    SNMP-COMMUNITY-MIB::snmpTrapAddress.0 ###.###.###.###


  2. Check Physical Connectivity:

    Verify the link status of the physical network interface on the affected ESX host.

    Confirm the health and configuration of the connected network switch port.

    If the link status is confirmed to be healthy, investigate the ESX logs (e.g., vmkernel.log) for any software-related event that may have caused the Link Down notification without a physical failure.

 

 

Additional Information

The exact output format of the SNMP trap may vary based on the user interface of the SNMP manager.