Multiprotocol Label Switching (MPLS) Traffic Engineering (TE) Management Information Base (MIB)

MPLS Transport Profile (MPLS-TP) Operations, Administration, and Maintenance (OAM) Identifiers Management Information Base (MIB)

“…This document uses terminology from the Multiprotocol Label Switching Architecture [RFC3031], the MPLS Traffic Engineering (TE) MIB [RFC3812], the MPLS Label Switching Router (LSR) MIB [RFC3813], the OAM Framework for MPLS-Based Transport Networks [RFC6371], "MPLS Transport Profile (MPLS-TP) Identifiers" [RFC6370], MPLS-TP Identifiers Following ITU-T Conventions [RFC6923], and OAM in MPLS Transport Networks [RFC5860]. The MPLS transport profile OAM identifiers MIB module is designed to satisfy the following requirements and constraints:…”

“…At the time of this writing, SNMP SET is no longer recommended as a way to configure MPLS networks as was described in [RFC3812]. However, since the MIB modules specified in this document are intended to work in parallel with the MIB modules for MPLS specified in [RFC3812], certain objects defined here are specified with a MAX-ACCESS of read-write or read-create so that specifications of the base tables in [RFC3812] and the new MIB modules in this document are consistent.…”

“…However, since the MIB modules specified in this document are intended to work in parallel with the MIB modules for MPLS specified in [RFC3812], certain objects defined here are specified with a MAX-ACCESS of read-write or read-create so that specifications of the base tables in [RFC3812] and the new MIB modules in this document are consistent. Although the example described in Section 6 specifies means to configure OAM identifiers for MPLS-TP Tunnels, this should be seen as indicating how the MIB values would be returned in the specified circumstances having been configured by alternative means.…”

A Path Computation Element (PCE)-Based Architecture

“…For example, in Figure 5 the NMS supplies the head-end LSR with a fully computed explicit path for the TE LSP that it is to establish through signaling. The NMS uses a management plane mechanism to send this request and encodes the data using a representation such as the TE MIB module [RFC3812].…”

Generalized Multiprotocol Label Switching (GMPLS) Traffic Engineering Management Information Base

“…In particular, it describes managed objects for modeling Generalized Multiprotocol Label Switching (GMPLS) [RFC3945] based traffic engineering (TE). The tables and objects defined in this document extend those defined in the equivalent document for MPLS traffic engineering [RFC3812], and management of GMPLS traffic engineering is built on management of MPLS traffic engineering.…”