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/.2544/.1/fsp150cm/cmServiceAssuranceMIB/.1/esaProbeStatsTable/esaProbeStatsEntry/esaProbeStatsY1731P2RNegLossOccurrences

esaProbeStatsY1731P2RNegLossOccurrences

OBJECT-TYPE

1.3.6.1.4.1.2544.1.12.8.1.7.1.54

Access

read-only

Status

current

Source

CM-SA-MIB

Sub-identifiers

Description

This attribute is only applicable to Y.1731 probes. This is the number of occurences of negative frame loss from Source MEP (Probe) to Destination MEP (Reflector). If these counts are non-zero then there could be some kind of provisioning mismatch between the Probe MEP and Reflector MEP. Here are some scenarios this can happen: - Probe MEP is configured to count in-profile frames only and the Reflector MEP is configured to count all frames with a mismatch in value for the attribute cfmMepLmCountInProfileFrames. - Probe MEP is configured to count data frames for specific VLAN priority and the Reflector MEP is configured to count data frames for all the priorities with a mismatch in values for the attributes cfmMepLmTxCountAllPrios or cfmMepLmRxCountAllPrios. NOTE: This could possibly happen due to reasons not related to configuration such as frame reordering in the network.

Syntax

PerfCounter64