VMWARE-NSX-MANAGER-MIB :: vmwNsxMFabricConnEamFailed

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › VMWARE-NSX-MANAGER-MIB › vmwNsxMFabricConnEamFailed

vmwNsxMFabricConnEamFailed

Module: VMWARE-NSX-MANAGER-MIB

OID (symbolic): VMWARE-NSX-MANAGER-MIB::vmwNsxMFabricConnEamFailed

OID (numeric): 1.3.6.1.4.1.6876.90.1.2.7.0.19

Node type: NOTIFICATION-TYPE

Description: NSX Manager relies on the ESX Agent Manager service in VC for deploying/monitoring NSX vibs on ESX. The connection to this EAM service has gone down. This could be due to EAM service or VC restart/stop or an issue in the EAM service. Action required: In the NSX UI, traverse to Manage, then NSX Management Service. Verify that the status of VC connection on this page is Green. Use the VC IP to verify that EAM is UP by visiting https:///eam/mob. Frequency of traps: Once per switch from success to failed EAM connection

Examples

Send this trap to an SNMP manager — replace <manager> with the IP or hostname of your monitoring server (SNMPv2c):

snmptrap -v2c -c public <manager> '' VMWARE-NSX-MANAGER-MIB::vmwNsxMFabricConnEamFailed
snmptrap -v2c -c public <manager> '' 1.3.6.1.4.1.6876.90.1.2.7.0.19

Listen for incoming traps on the manager host (-f keeps it in the foreground, -Lo prints to stdout — useful for testing):

snmptrapd -f -Lo -c /dev/null authCommunity log public

Example snmptrapd log entry:

zoo11-linux.zoo [UDP: [192.168.30.111]:54358->[192.168.30.10]:162]:
  DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (286747222) 33 days, 4:31:12.22
  SNMPv2-MIB::snmpTrapOID.0 = OID: VMWARE-NSX-MANAGER-MIB::vmwNsxMFabricConnEamFailed

Start monitoring VMware NSX Manager appliances, SDDC/vSphere environments (controller/transport-node fault-event notification status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the VMWARE-NSX-MANAGER-MIB::vmwNsxMFabricConnEamFailed OID value, configure state conditions and alerts, and monitor any VMware NSX Manager appliances, SDDC/vSphere environments (controller/transport-node fault-event notification status) from a single console.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.6876vmwareVMWARE-ROOT-MIB
1.3.6.1.4.1.6876.90vmwNsxManagerVMWARE-ROOT-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6876.90.1vmwNsxManagerMIBVMWARE-NSX-MANAGER-MIB
1.3.6.1.4.1.6876.90.1.2vmwNsxMNotificationVMWARE-NSX-MANAGER-MIB
1.3.6.1.4.1.6876.90.1.2.7vmwNsxMFabricVMWARE-NSX-MANAGER-MIB
1.3.6.1.4.1.6876.90.1.2.7.0vmwNsxMFabricPrefixVMWARE-NSX-MANAGER-MIB
1.3.6.1.4.1.6876.90.1.2.7.0.19vmwNsxMFabricConnEamFailedVMWARE-NSX-MANAGER-MIB