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/.6527/.3/.1/.2/.11/.1/tmnxOamP2mpLspPingCtlTable/tmnxOamP2mpLspPingCtlEntry/tmnxOamP2mpLspPingCtlOptionalTLV

tmnxOamP2mpLspPingCtlOptionalTLV

OBJECT-TYPE

1.3.6.1.4.1.6527.3.1.2.11.1.21.1.9

Access

read-write

Status

current

Source

TIMETRA-OAM-TEST-MIB

Sub-identifiers

Description

The value of tmnxOamP2mpLspPingCtlOptionalTLV specifies which optional Type/Length/Value (TLV) structure to include in the MPLS echo request launched for the specified test. 'vpnRecursiveFec(2)' specifies the proprietary inclusion of an RFC 6512 'VPN-Recursive FEC Element'. 'vpnRecursiveFec(2)' is required to successfully ping a P2MP leaf with the following characteristics: 1. The path between the P2MP root and the targeted leaf is a Virtual Private Network (VPN), e.g. an SROS Virtual Private Routed Network (VPRN) service. And .. 2. The VPN has an RFC 4364 'Option B' boundary between two Border Gateway Protocol (BGP) Autonomous Systems. And .. 3. The leaf resides on an SROS node (with support for this object) on the far side of the boundary (with respect to the root). A leaf residing on a non-SROS node may not respond (or may respond with an error) when 'vpnRecursiveFec(2)' is specified. 'none(1)' specifies the inclusion of none of the optional TLVs described above.

Syntax

INTEGER { none (1), vpnRecursiveFec (2) }