MPLS-OAM-ID-STD-MIB

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-TYPE

This object contains an unused value for mplsOamIdMegIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMegIndex.

OBJECT-TYPE

This table contains information about the Maintenance Entity Groups (MEGs). A MEG, as mentioned in the MPLS-TP OAM framework, defines a set of one or more Maintenance Entities (MEs). MEs define a relationship between any two points of a transport path in an OAM domain to which maintenance and monitoring operations apply.

OBJECT-TYPE

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.

OBJECT-TYPE

Index for the conceptual row identifying a MEG within this MEG table. Managers should obtain new values for row creation in this table by reading mplsOamIdMegIndexNext.

OBJECT-TYPE

Each MEG has a unique name amongst all those used or available to a service provider or operator. It facilitates easy identification of administrative responsibility for each MEG.

OBJECT-TYPE

Indicates the operator type for the MEG. Conceptual rows having 'iccBased' as the operator type MUST have valid values for the objects mplsOamIdMegIdIcc and mplsOamIdMegIdUmc when the row status is active.

OBJECT-TYPE

Global uniqueness is assured by concatenating the ICC with a Country Code (CC). The Country Code (alpha-2) is a string of two alphabetic characters represented with uppercase letters (i.e., A-Z). This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.

OBJECT-TYPE

Unique code assigned to a network operator or service provider; maintained by the ITU-T. This is the ITU Carrier Code used to form the MEGID. This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.

OBJECT-TYPE

Unique code assigned by a network operator or service provider. This code is appended to mplsOamIdMegIdIcc to form the MEGID. This object MUST contain a non-null value if the MplsOamIdMegOperatorType value is iccBased (2); otherwise, a null value with octet size 0 should be assigned.

OBJECT-TYPE

Indicates the service type for the MEG. If the service type indicates tunnel (1), the service pointer in the mplsOamIdMeTable points to an entry in the point-to-point mplsTunnelTable (RFC 3812). If the service type indicates lsp (2), the service pointer in the mplsOamIdMeTable points to an entry in the co-routed or associated bidirectional mplsTunnelTable. If the value is the pseudowire (3) service type, the service pointer in the mplsOamIdMeTable points to an entry in the pwTable (RFC 5601). If the value is the section (4) service type, the service pointer in the mplsOamIdMeTable points to an entry in the mplsTunnelTable (RFC 3812).

OBJECT-TYPE

Indicates the MP location type for this MEG. If the value is perNode, then the MEG in the LSR supports only perNode MEPs/MIPs, i.e., only one MEP/MIP in an LSR. If the value is perInterface, then the MEG in the LSR supports perInterface MEPs/MIPs, i.e., two MEPs/MIPs in an LSR.

OBJECT-TYPE

Indicates the transport path flow for this MEG. In the case of a unidirectional point-to-point transport path, a single unidirectional ME is defined to monitor it. In the case of associated bidirectional point-to-point transport paths, two independent unidirectional MEs are defined to independently monitor each direction. In the case of co-routed bidirectional point-to-point transport paths, a single bidirectional ME is defined to monitor both directions congruently. In the case of unidirectional point-to-multipoint transport paths, a single unidirectional ME for each leaf is defined to monitor the transport path from the root to that leaf.

OBJECT-TYPE

This object specifies the operational status of the Maintenance Entity Group (MEG). This object is used to send the notification to the SNMP manager about the MEG. The value up (1) indicates that the MEG and its monitored path are operationally up. The value down (2) indicates that the MEG is operationally down. When the value of mplsOamIdMegOperStatus is up (1), all the bits of mplsOamIdMegSubOperStatus must be cleared. When the value of mplsOamIdMegOperStatus is down (2), at least one bit of mplsOamIdMegSubOperStatus must be set.

OBJECT-TYPE

This object specifies the reason why the MEG operational status, as indicated by the object mplsOamIdMegOperStatus, is down. This object is used to send the notification to the SNMP manager about the MEG. The bit 0 (megDown) indicates that the MEG is down. The bit 1 (meDown) indicates that the ME table is down. The bit 2 (oamAppDown) indicates that the OAM application (LSP or PW) monitored by this MEG is down. Currently, BFD is the only supported OAM application. The bit 3 (pathDown) indicates that the underlying LSP or PW is down.

OBJECT-TYPE

This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in the active(1) state, no objects in that row can be modified by the agent except mplsOamIdMegRowStatus.

OBJECT-TYPE

This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.

OBJECT-TYPE

This object contains an unused value for mplsOamIdMeIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMeIndex.

OBJECT-TYPE

This object contains an unused value for mplsOamIdMeMpIndex, or a zero to indicate that none exist. Negative values are not allowed, as they do not correspond to valid values of mplsOamIdMeMpIndex.

OBJECT-TYPE

This table contains MPLS-TP ME information. The ME is some portion of a transport path that requires management bounded by two points (called MEPs), and the relationship between those points to which maintenance and monitoring operations apply. This table is generic enough to handle MEP and MIP information within a MEG.

OBJECT-TYPE

An entry in this table represents an MPLS-TP ME. This entry represents the ME if the source and sink MEPs are defined. An ME is a point-to-point entity. One ME has two such MEPs. A MEG is a group of one or more MEs. One MEG can have two or more MEPs. For a point-to-point LSP, one MEG has one ME, and this ME is associated with two MEPs (source and sink MEPs) within a MEG. Each mplsOamIdMeIndex value denotes the ME within a MEG. In the case of unidirectional point-to-point transport paths, a single unidirectional ME is defined to monitor it, and mplsOamIdMeServicePointer points to a unidirectional point-to-point path. In the case of associated bidirectional point-to-point transport paths, two independent unidirectional MEs are defined to independently monitor each direction, and each mplsOamIdMeServicePointer MIB object points to a unique unidirectional transport path. This has implications for transactions that terminate at or query a MIP, as a return path from a MIP to a source MEP does not necessarily exist within the MEG. In the case of co-routed bidirectional point-to-point transport paths, a single bidirectional ME is defined to monitor both directions congruently, and the mplsOamIdMeServicePointer MIB object points to a co-routed bidirectional point-to-point transport path. In the case of unidirectional point-to-multipoint transport paths, a single unidirectional ME for each leaf is defined to monitor the transport path from the root to that leaf, and each leaf has different transport path information in the mplsOamIdMeServicePointer MIB object. Note that the MplsOamIdMeEntry should be created manually once the MEG is configured for OAM operations.

OBJECT-TYPE

Uniquely identifies an ME index within a MEG. Managers should obtain new values for row creation in this table by reading mplsOamIdMeIndexNext.

OBJECT-TYPE

Indicates the Maintenance Point (MP) index that is used to create multiple MEPs in a node of a single ME. The value of this object can be the MEP index or the MIP index. Managers should obtain new values for row creation in this table by reading mplsOamIdMeMpIndexNext.

OBJECT-TYPE

This object denotes the ME name. Each ME has a unique name within a MEG.

OBJECT-TYPE

Indicates the MP interface. If the mplsOamIdMegMpLocation object value is perNode (1), the MP interface index should point to the incoming interface or outgoing interface, or be zero (to indicate that the MP OAM packets are initiated from the forwarding engine). If the mplsOamIdMegMpLocation object value is perInterface (2), the MP interface index should point to the incoming interface or outgoing interface.

OBJECT-TYPE

Indicates the source MEP index of the ME. This object should be configured if the mplsOamIdMegOperatorType object in the mplsOamIdMegEntry is configured as iccBased (2). If the MEG is configured for an IP-based operator, the value of this object should be set to zero, and the MEP ID will be automatically derived from the service identifiers (MPLS-TP LSP/PW Identifier).

OBJECT-TYPE

Indicates the sink MEP index of the ME. This object should be configured if the mplsOamIdMegOperatorType object in the mplsOamIdMegEntry is configured as iccBased (2). If the MEG is configured for an IP-based operator, the value of this object should be set to zero, and the MEP ID will be automatically derived from the service identifiers (MPLS-TP LSP/PW Identifier).

OBJECT-TYPE

Indicates the MP type within the MEG. The object should have the value mep (1) only in the ingress or egress nodes of the transport path. The object can have the value mip (2) in the intermediate nodes and possibly in the egress nodes of the transport path.

OBJECT-TYPE

Indicates the direction of the MEP. This object should be configured if mplsOamIdMeMpType is configured as mep (1); otherwise, notApplicable (3) is set.

OBJECT-TYPE

This variable represents a pointer to the MPLS-TP transport path. This value MUST point at an entry in the mplsTunnelEntry if mplsOamIdMegServicePointerType is configured as tunnel (1), lsp (2), or section (4), or at an entry in the pwEntry if mplsOamIdMegServicePointerType is configured as pseudowire (3). Note: This service pointer object is placed in the ME table instead of the MEG table, since it will be useful in the point-to-multipoint case, where each ME will point to different branches of a point-to-multipoint tree.

OBJECT-TYPE

This variable is used to create, modify, and/or delete a row in this table. When a row in this table is in the active(1) state, no objects in that row can be modified by the agent except mplsOamIdMeRowStatus.

OBJECT-TYPE

This variable indicates the storage type for this object. Conceptual rows having the value 'permanent' need not allow write access to any columnar objects in the row.

OBJECT-IDENTITY

OBJECT-IDENTITY

OBJECT-IDENTITY