mplsOamIdMegEntry

An entry in this table represents an 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
mplsOamIdMegOperatorType set to ipCompatible (1),
then as per RFC 6370 (MEG_ID for an LSP is LSP_ID, and
MEG_ID for a PW is PW_Path_ID), MEP_ID can be
automatically formed.
            
For a co-routed bidirectional LSP, MEG_ID is
A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID::
Node_ID::Tunnel_Num}::LSP_Num.
            
For an 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 an LSP, MEP_ID is formed using
Global_ID::Node_ID::Tunnel_Num::LSP_Num.
            
For a PW, MEG_ID is formed using AGI::
A1-{Global_ID::Node_ID::AC_ID}::
Z9-{Global_ID::Node_ID::AC_ID}.
            
For a PW, MEP_ID is formed using
AGI::Global_ID::Node_ID::AC_ID.
            
MEP_ID is retrieved from the mplsOamIdMegServicePointer
object based on the mplsOamIdMegServicePointerType value.
The ICC MEG_ID for an LSP and a PW is formed using the
objects mplsOamIdMegIdIcc and mplsOamIdMegIdUmc.
            
MEP_ID can be formed using MEG_ID::MEP_Index.

MIB

MPLS-OAM-ID-STD-MIB

OID

.1.3.6.1.2.1.10.166.21.1.2.1

Type

row

Status

current

Parent

mplsOamIdMegTable

Table

mplsOamIdMegTable

Children

13