MPLS-TE-EXT-STD-MIB: View SNMP OID List / Download MIB

This MIB module contains generic object definitions for extending the MPLS Traffic Engineering tunnels in transport networks. Copyright (c) 2015 IETF Trust and the persons identified as authors of the code. All rights reserved. Redistribution and use in source and binary forms, with or without modification, is permitted pursuant to, and subject to the license terms contained in, the Simplified BSD License set forth in Section 4.c of the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info).

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

This table allows the operator to map a node or LSR identifier (IP-compatible [Global_ID::Node_ID] or ICC-based [ICC_Operator_ID::Node_ID]) with a local identifier. This table is created to reuse the existing mplsTunnelTable for MPLS-based transport network tunnels also. Since the MPLS tunnel's Ingress/Egress LSR identifiers' size (Unsigned32) value is not compatible for MPLS-TP Tunnel, i.e., Global_ID::Node_ID of size 8 bytes and ICC_Operator_ID::Node_ID of size 12 bytes, there exists a need to map the Global_ID::Node_ID or ICC_Operator_ID::Node_ID with the local identifier of size 4 bytes (Unsigned32) value in order to index (Ingress/Egress LSR identifier) the existing mplsTunnelTable.

An entry in this table represents a mapping identification for the operator or service provider to a node or an LSR. As per RFC 6370, IP-compatible mapping is represented as Global_ID::Node_ID. As per RFC 6923, the CC and the ICC form the ICC_Operator_ID as CC::ICC, and ICC-compatible mapping is represented as ICC_Operator_ID::Node_ID. Note: Each entry in this table should have a unique [Global_ID and Node_ID] or [CC::ICC and Node_ID] combination.

This object is used in accommodating the bigger- size Global_ID::Node_ID and/or the ICC_Operator_ID::Node_ID with the smaller-size LSR identifier in order to index the mplsTunnelTable. The local identifier is configured between 0 and 16777215, as the valid IP address range starts from 16777216(01.00.00.00). This range is chosen to determine whether the mplsTunnelTable's Ingress/Egress LSR ID is an IP address or local identifier. If the configured range is not an IP address, the operator is expected to retrieve the complete information (Global_ID::Node_ID or ICC_Operator_ID::Node_ID) from mplsTunnelExtNodeConfigTable. This way, the existing mplsTunnelTable is reused for bidirectional tunnel extensions for MPLS-based transport networks. The local identifier allows the operator to assign a unique identifier to map Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID. As this local identifier is unique within the node and the same syntax of this object can be used for MPLS-TE tunnel also, it is up to the operator/local management entity to choose a non-conflicting value for indexing the MPLS and MPLS-TP tunnel entries.

This object indicates the Global Operator Identifier. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set true.

This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress ID or Egress ID. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set to false.

This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Carrier Code (ICC) either for Ingress ID or Egress ID. This object has no meaning when mplsTunnelExtNodeConfigIccValid is set to false.

This object indicates the Node_ID within the scope of a Global_ID or ICC_Operator_ID.

Denotes whether or not this entry uses mplsTunnelExtNodeConfigCcId, mplsTunnelExtNodeConfigIccId, and mplsTunnelExtNodeConfigNodeId for mapping the ICC-based identifiers with the local identifier. Note that if this variable is set to false, then the mplsTunnelExtNodeConfigGlobalId and mplsTunnelExtNodeConfigNodeId objects should have the valid information.

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.

This object allows the operator to create, modify, and/or delete a row in this table.

This read-only table allows the operator to retrieve the local identifier for a given Global_ID::Node_ID in an IP-compatible operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (local identifier) from Src-Global_Node_ID or Dst-Global_Node_ID. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable.

An entry in this table represents a mapping of Global_ID::Node_ID with the local identifier. An entry in this table is created automatically when the local identifier is associated with Global_ID and Node_Id in the mplsTunnelExtNodeConfigTable. Note: Each entry in this table should have a unique Global_ID and Node_ID combination.

This object indicates the Global_ID.

This object indicates the Node_ID within the operator.

This object contains an IP-compatible local identifier that is defined in mplsTunnelExtNodeConfigTable.

This read-only table allows the operator to retrieve the local identifier for a given ICC_Operator_ID::Node_ID in an ICC operator environment. This table MAY be used in on-demand and/or proactive OAM operations to get the Ingress/Egress LSR identifier (local identifier) from Src-ICC or Dst-ICC. The Ingress and Egress LSR identifiers are used to retrieve the tunnel entry. This table returns nothing when the associated entry is not defined in mplsTunnelExtNodeConfigTable.

An entry in this table represents a mapping of ICC_Operator_ID::Node_ID with the local identifier. An entry in this table is created automatically when the local identifier is associated with ICC_Operator_ID::Node_ID in the mplsTunnelExtNodeConfigTable.

This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Country Code (CC) either for Ingress or Egress LSR ID. The CC is a string of two alphabetic characters represented with uppercase letters (i.e., A-Z).

This object allows the operator or service provider to configure a unique MPLS-TP ITU-T Carrier Code (ICC) either for Ingress or Egress LSR ID. The ICC is a string of one to six characters, each character being either alphabetic (i.e., A-Z) or numeric (i.e., 0-9) characters. Alphabetic characters in the ICC should be represented with uppercase letters.

This object indicates the Node_ID within the ICC-based operator.

This object contains an ICC-based local identifier that is defined in mplsTunnelExtNodeConfigTable.

This table represents extensions to mplsTunnelTable in order to support MPLS-TP Tunnels. As per MPLS-TP Identifiers (RFC 6370), LSP_ID for IP-based co-routed bidirectional tunnel: A1-{Global_ID::Node_ID::Tunnel_Num}::Z9-{Global_ID:: Node_ID::Tunnel_Num}::LSP_Num LSP_ID for IP based associated bidirectional tunnel: A1-{Global_ID::Node_ID::Tunnel_Num::LSP_Num}:: Z9-{Global_ID::Node_ID::Tunnel_Num::LSP_Num} mplsTunnelTable is reused for forming the LSP_ID as follows: Source Tunnel_Num is mapped with mplsTunnelIndex, Source Node_ID is mapped with mplsTunnelIngressLSRId, Destination Node_ID is mapped with mplsTunnelEgressLSRId, and LSP_Num is mapped with mplsTunnelInstance. Source Global_ID::Node_ID and/or ICC_Operator_ID::Node_ID and Destination Global_ID::Node_ID and/or ICC_Operator_ID::Node-ID are maintained in the mplsTunnelExtNodeConfigTable. mplsTunnelExtNodeConfigLocalId is used to create an entry in mplsTunnelTable.

An entry in this table represents additional MPLS-TP- specific tunnel configurations.

This object points to the opposite-direction tunnel entry.

Denotes whether or not this tunnel uses mplsTunnelExtOppositeDirPtr for identifying the opposite- direction tunnel information. Note that if this variable is set to true, then the mplsTunnelExtOppositeDirPtr should point to the first accessible row of the valid opposite- direction tunnel.

This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. The values of this object and the mplsTunnelExtDestTnlLspIndex object together can be used to identify an opposite-direction LSP, i.e., if the mplsTunnelIndex and mplsTunnelInstance hold the value for forward LSP, this object and mplsTunnelExtDestTnlLspIndex can be used to retrieve the reverse-direction LSP and vice versa. This object and mplsTunnelExtDestTnlLspIndex values provide the first two indices of tunnel entry, and the remaining indices can be derived as follows: the Ingress and Egress Identifiers should be swapped in order to index the other direction tunnel.

This object is applicable only for the bidirectional tunnel that has the forward and reverse LSPs in the different tunnel entries. This object holds the instance index of the opposite-direction tunnel.

Denotes whether or not this tunnel uses mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex for identifying the opposite-direction tunnel information. Note that if this variable is set to true, then the mplsTunnelExtDestTnlIndex and mplsTunnelExtDestTnlLspIndex objects should have the valid opposite-direction tunnel indices.

This object denotes whether the mplsTunnelIngressLSRId contains the local value that is used to reference the complete Ingress Global_ID::Node_ID or ICC_Operator_ID from the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelIngressId itself provides the complete Ingress LSR ID.

This object denotes whether the mplsTunnelEgressLSRId contains the local value, which is used to reference the complete Egress Global_ID::Node_ID or ICC_Operator_ID::Node_ID from the mplsTunnelExtNodeConfigTable. If this object is set to FALSE, mplsTunnelExtNodeConfigTable will not contain an entry to reference the local identifier with Global_ID::Node_ID or ICC_Operator_ID::Node_ID value. This object is set to FALSE for legacy implementations like MPLS TE tunnels where mplsTunnelEgressId itself provides the complete Egress LSR ID.

Compliance statement for agents that provide full support the MPLS-TE-EXT-STD-MIB module.

Compliance statement for agents that only provide read-only support for the MPLS-TE-EXT-STD-MIB module.

Necessary, but not sufficient, set of objects to implement tunnels. In addition, depending on the operating environment, the following groups are mandatory.

Object(s) needed to implement IP-compatible tunnels.

Object(s) needed to implement ICC-based tunnels.