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/.6296/sleMgmt/.16/sleMplsTpOam/.1/sleMplsTpOamMegInfoTable/sleMplsTpOamMegInfoEntry

sleMplsTpOamMegInfoEntry

OBJECT-TYPE

1.3.6.1.4.1.6296.101.16.17.1.1.1

Access

read-only

Status

current

Source

SLE-MPLS-TP-OAM-MIB

Sub-identifiers

Description

An entry in this table represents MPLS-TP MEG. An entry can be created by a network administrator or by an SNMP agent as instructed by an MPLS-TP OAM Framework. When a new entry is created with sleMplsTpOamMegOperatorType set to ipCompatible (1), then as per [RFC6370] (MEG_ID for LSP is LSP_ID and MEG_ID for PW is PW_Path_ID), MEP_ID can be automatically formed. For co-routed bidirectional LSP, MEG_ID is A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num. For associated bidirectional LSP, MEG_ID is A1- {Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9- {Global_ID::Node_ID::Tunnel_Num::LSP_Num} For LSP, MEP_ID is formed using, Global_ID::Node_ID::Tunnel_Num::LSP_Num For PW, MEG_ID is formed using AGI::A1- {Global_ID::Node_ID::AC_ID}:: Z9- {Global_ID::Node_ID::AC_ID}. For PW, MEP_ID is formed using AGI::Global_ID::Node_ID::AC_ID MEP_ID is retrieved from the sleMplsTpOamMegServicePointer object based on the sleMplsTpOamMegServiceType value. ICC MEG_ID for LSP and PW is formed using the objects sleMplsTpOamMegIdIcc and sleMplsTpOamMegIdUmc. MEP_ID can be formed using MEG_ID::MEP_Index.

Syntax

SleMplsTpOamMegInfoEntry

Children (6)

.1sleMplsTpOamMegInfoIndex .2sleMplsTpOamMegInfoName .3sleMplsTpOamMegInfoOperatorType .4sleMplsTpOamMegInfoServiceType .5sleMplsTpOamMegInfoMegLevel .6sleMplsTpOamMegInfoOperStatus