MIB Viewer

Search, upload, browse, or download from a database of over 11,000 SNMP MIBs. MIB Viewer lets you look up any MIB object by name, OID, or number, view its syntax, access level, and description, trace its place in the MIB tree, and generate ready-to-run SNMP commands — all in your browser.

What's a MIB?

A MIB (Management Information Base) is a structured document that defines the data a device exposes over SNMP — things like interface counters, system uptime, or CPU load. Each module declares a set of named objects, organized into a tree.

What's SNMP?

SNMP (Simple Network Management Protocol) is how network devices — routers, switches, servers — report status and statistics to monitoring tools. It's the protocol; MIBs are the vocabulary it uses to describe what's being asked for.

What's an OID?

An OID (Object Identifier) is the numeric address of one piece of data in a MIB — a dotted sequence like 1.3.6.1.2.1.1.1, read from the root of a global tree down to one specific object. Names are easier to read; OIDs are what's actually sent over the wire.

Try it: sysDescr (1.3.6.1.2.1.1.1) →

Get started

Search for a MIB or OID above, or pick one from the list on the left.

Have your own MIB file? Drop it on the upload zone in the sidebar (or click to browse) to parse and explore it right away — it stays private to this browser session and isn't added to the shared library.

iso/org/dod/internet/private/enterprises/.6876/.120/vmwNSXsysMIB/vmwNsxTDataCenterNotifications/vmwNsxTFederationFeaturePrefix/vmwNsxTFederationFeature/vmwNsxTFederationRtepBGPDown

vmwNsxTFederationRtepBGPDown

NOTIFICATION-TYPE

1.3.6.1.4.1.6876.120.1.0.32.0.1

Status

current

Source

VMWARE-NSX-MIB

Sub-identifiers

Description

RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is down. Reason: vmwNsxTDataCenterFailureReason. Action required: 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node. 2. Switch to REMOTE_TUNNEL_VRF context. 3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status. 4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary to get the BGP neighbor status. 5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned to the interface with name remote-tunnel-endpoint. 6. Check if the ping is working successfully between assigned RTEP IP address (vmwNsxTDataCenterBGPSourceIP) and the remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP. 7. Check /var/log/syslog for any errors related to BGP. 8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint configuration on the edge node. This will update the RTEP IP assigned to the affected edge node. If the reason indicates `Edge is not ready`, check why the Edge node is not in good state. 1. Invoke the NSX CLI command `get edge-cluster status` to check reason why Edge node might be down. 2. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well. 3. Check any Edge health related alarms to get more information.