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/vmwNsxTNodeAgentsHealthFeaturePrefix/vmwNsxTNodeAgentsHealthFeature/vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPU

vmwNsxTNodeAgentsHealthNodeAgentsDownOnDPU

NOTIFICATION-TYPE

1.3.6.1.4.1.6876.120.1.0.12.0.5

Status

current

Source

VMWARE-NSX-MIB

Sub-identifiers

Description

The agents running inside the Node VM appear to be down on DPU vmwNsxTDataCenterDPUId. Action required: 1. If Vmk50 on DPU vmwNsxTDataCenterDPUId is missing, refer to this Knowledge Base article https://kb.vmware.com/s/article/67432. 2. If Hyperbus 4094 on DPU vmwNsxTDataCenterDPUId is missing, restarting nsx-cfgagent on DPU vmwNsxTDataCenterDPUId or restarting the container host VM may help. 3. If container host VIF is blocked, check the connection to the Controller to make sure all configurations are sent down. 4. If nsx-cfg-agent on DPU vmwNsxTDataCenterDPUId has stopped, restart nsx-cfgagent on DPU vmwNsxTDataCenterDPUId . 5. If the node-agent package is missing, check whether node-agent package has been successfully installed in the container host vm. 6. If the interface for node-agent in container host vm is down, check the eth1 interface status inside the container host vm.