PRVT-MPLS-LDP-MIB: View SNMP OID List / Download MIB

This MIB contains managed object definitions for the 'Multiprotocol Label Switching, Label Distribution Protocol, LDP'.

This table contains information about the Label Switching Router (LSR) or Label Edge Router (LER) that is running the MPLS Label Distribution Protocol.

An entry in this table contains the LSR objects specific to an instance of PRVT-CR-LDP.

The Label Switching Router's Identifier.

A indication of whether this Label Switching Router supports loop detection. none(1) -- Loop Detection is not supported on this LSR. other(2) -- Loop Detection is supported but by a method other than those listed below. hopCount(3) -- Loop Detection is supported by Hop Count only. pathVector(4) -- Loop Detection is supported by Path Vector only. hopCountAndPathVector(5) -- Loop Detection is supported by both Hop Count And Path Vector. Since Loop Detection is determined during Session Initialization, an individual session may not be running with loop detection. This object simply gives an indication of whether or not the LSR has the ability to support Loop Detection and which types. Enumeration: 'hopCountAndPathVector': 5, 'none': 1, 'other': 2, 'hopCount': 3, 'pathVector': 4.

This table contains information about the MPLS Label Distribution Protocol Entities which exist on this Label Switching Router (LSR) or Label Edge Router (LER).

An entry in this table represents an LDP entity. An entry can be created by a network administrator or by an SNMP agent as instructed by LDP.

The LDP identifier. The first four octets encode an IP address assigned to the LSR, and the last two octets identify a specific label space within the LSR.

This index is used as a secondary index to uniquely identify this row. Before creating a row in this table, the 'mplsLdpEntityIndexNext' object should be retrieved. That value should be used for the value of this index when creating a row in this table. NOTE: if a value of zero (0) is retrieved, that indicates that no rows can be created in this table at this time. A secondary index (this object) is meaningful to some but not all, LDP implementations. For example an LDP implementation which uses PPP would use this index to differentiate PPP sub-links. Another way to use this index is to give this the value of ifIndex. However, this is dependant on the implementation. This field is deprecated in the following tables provided by PRVT-CR-LDP Session Controller. - mplsLdpEntityTable. - mplsLdpPeerTable. In these tables the value of the Entity Index will always be filled in to be 1.

The version number of the protocol. The value of 0 on a read indicates that the version of the protocol is unknown. Otherwise, the value of this object represents the version of the LDP protocol. Section 3.5.3 in the LDP Specification specifies that the version of the LDP protocol is negotiated during session establishment. The value of this object represents the value that is sent in the initialization message.

The administrative status of this LDP Entity. If this object is changed from 'enable' to 'disable' and this entity has already attempted to establish contact with a Peer (which implies that the 'mplsLdpEntityRowStatus' object has been set to 'active'), then all contact with that Peer is lost and all information from that Peer needs to be removed from the MIB. (This implies that the network management subsystem should clean up any related entry in the mplsLdpPeerTable. This further implies that a 'tear-down' for that session is issued and the session and all information related to that session cease to exist). At this point the user is able to change values which are related to this entity. When the admin status is set back to 'enable', then this Entity will attempt to establish a new session with the Peer. Enumeration: 'enable': 1, 'disable': 2.

The operational status of this LDP Entity. The value of unknown(1) indicates that the operational status cannot be determined at this time. The value of unknown should be a transient condition before changing to enabled(2) or disabled(3). Enumeration: 'disabled': 3, 'unknown': 1, 'enabled': 2.

The TCP Port for LDP. The default value is the well-known value of this port.

The UDP Discovery Port for LDP. The default value is the well-known value for this port.

The maximum PDU Length that is sent in the Common Session Parameters of an Initialization Message. According to the LDP Specification [RFC3036] a value of 255 or less specifies the default maximum length of 4096 octets, this is why the value of this object starts at 256. The receiving LSR MUST calculate the maximum PDU length for the session by using the smaller of its and its peer's proposals for Max PDU Length.

The 16-bit integer value which is the proposed keep alive hold timer for this LDP Entity.

The 16-bit integer value which is the proposed Hello hold timer for this LDP Entity. The Hello Hold time in seconds. An LSR maintains a record of Hellos received from potential peers. This object represents the Hold Time in the Common Hello Parameters TLV of the Hello Message. A value of 0 is a default value and should be interpretted in conjunction with the mplsLdpEntityTargetPeer object. If the value of this object is 0: if the value of the mplsLdpEntityTargetPeer object is false(2), then this specifies that the Hold Time's actual default value is 15 seconds (i.e., the default Hold time for Link Hellos is 15 seconds). Otherwise if the value of the mplsLdpEntityTargetPeer object is true(1), then this specifies that the Hold Time's actual default value is 45 seconds (i.e., the default Hold time for Targeted Hellos is 45 seconds). A value of 65535 means infinite (i.e., wait forever). All other values represent the amount of time in seconds to wait for a Hello Message. Setting the hold time to a value smaller than 15 is not recommended, although not forbidden according to RFC3036. For auto-created entities that use the global label space (and therefore might correspond to more than one adjacency over more than one interface), this value will only be meaningful if all interfaces that correspond to this entity are configured to use the same hello hold time, since this property can be configured on a per interface basis. If the interfaces have differing configurations, the value returned on a MIB Get will be 0.

When attempting to establish a session with a given Peer, the given LDP Entity should send out the SNMP notification, 'mplsLdpInitSessionThresholdExceeded', when the number of Session Initialization messages sent exceeds this threshold. The notification is used to notify an operator when this Entity and its Peer are possibly engaged in an endless sequence of messages as each NAKs the other's Initialization messages with Error Notification messages. Setting this threshold which triggers the notification is one way to notify the operator. The notification should be generated each time this threshold is exceeded and for every subsequent Initialization message which is NAK'd with an Error Notification message after this threshold is exceeded. A value of 0 (zero) for this object indicates that the threshold is infinity, thus the SNMP notification will never be generated.

For any given LDP session, the method of label distribution must be specified.

The LDP Entity can be configured to use either conservative or liberal label retention mode. If the value of this object is conservative(1) then advertized label mappings are retained only if they will be used to forward packets, i.e., if label came from a valid next hop. If the value of this object is liberal(2) then all advertized label mappings are retained whether they are from a valid next hop or not.

If the value of this object is 0 (zero) then Loop Detection for Path Vectors is disabled. Otherwise, if this object has a value greater than zero, then Loop Dection for Path Vectors is enabled, and the Path Vector Limit is this value. Also, the value of the object, 'mplsLdpLsrLoopDetectionCapable', must be set to either 'pathVector(4)' or 'hopCountAndPathVector(5)', if this object has a value greater than 0 (zero), otherwise it is ignored.

If the value of this object is 0 (zero), then Loop Detection using Hop Counters is disabled. If the value of this object is greater than 0 (zero) then Loop Detection using Hop Counters is enabled, and this object specifies this Entity's maximum allowable value for the Hop Count. Also, the value of the object mplsLdpLsrLoopDetectionCapable must be set to either 'hopCount(3)' or 'hopCountAndPathVector(5)' if this object has a value greater than 0 (zero), otherwise it is ignored.

This specifies whether the loopback or interface address is to be used as the transport address in the transport address TLV of the hello message. If the value is interface(1), then the IP address of the interface from which hello messages are sent is used as the transport address in the hello message. Otherwise, if the value is loopback(2), then the IP address of the loopback interface is used as the transport address in the hello message. Enumeration: 'interface': 1, 'loopback': 2.

If this LDP entity uses targeted peer then set this to true.

The type of the internetwork layer address used for the Extended Discovery. This object indicates how the value of mplsLdpEntityTargetPeerAddr is to be interpreted.

The value of the internetwork layer address used for the Extended Discovery. The value of mplsLdpEntityTargetPeerAddrType specifies how this address is to be interpreted.

Specifies the optional parameters for the LDP Initialization Message. If the value is generic(1) then no optional parameters will be sent in the LDP Initialization message associated with this Entity. If the value is atmParameters(2) then a row must be created in the mplsLdpEntityAtmTable, which corresponds to this entry. If the value is frameRelayParameters(3) then a row must be created in the mplsLdpEntityFrameRelayTable, which corresponds to this entry.

The value of sysUpTime on the most recent occasion at which any one or more of this entity's counters suffered a discontinuity. The relevant counters are the specific instances associated with this entity of any Counter32 object contained in the 'mplsLdpEntityStatsTable'. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

Specifies whether the LDP Entity is to be used for accepting 'unsolicited' Hello messages that include the R bit. The value of this object is ignored unless mplsLdpEntityTargetedPeer is set to true mplsLdpEntityTargetedPeerAddr is set to 0.

An object that allows entries in this table to be created and deleted using the RowStatus convention. Once the 'mplsLdpEntityAdminStatus' object has the value of 'up' and this object has the value of 'active' then the Entity will atttempt to contact an LDP Peer. If the value of this object is changed to 'notInService', then the Entity looses contact with the LDP Peer and all information related to that Peer must be removed from the MIB. This has the same effect as changing 'mplsLdpEntityAdminStatus' from 'enable' to 'disable'. When this object is set to 'active' and the value of the 'mplsLdpEntityAdminStatus' is 'enable' then this Entity will attempt to contact the Peer and establish new sessions.

This table contains the next available values of mplsLdpEntityIndex for all entities.

An entry in this table represents the next available mplsLdpEntityIndex for a specific LDP entity. This MIB table is indexed by the PRVT-LDP entity Index.

This object contains an appropriate value to be used for mplsLdpEntityIndex when creating entries in the mplsLdpEntityTable. The value 0 indicates that no unassigned entries are available. To obtain the mplsLdpEntityIndex value for a new entry, the manager issues a management protocol retrieval operation to obtain the current value of this object. After each retrieval, the agent should modify the value to the next unassigned index.

This table is a read-only table which augments the mplsLdpEntityTable. The purpose of this table is to keep statistical information about the LDP Entities on the LSR.

A row in this table contains statistical information about an LDP Entity. Some counters contained in a row are for fatal errors received during a former LDP Session associated with this entry. For example, an LDP PDU received on a TCP connection during an LDP Session contains a fatal error. That error is counted here, because the session is terminated. If the error is NOT fatal (i.e., the Session remains), then the error is counted in the mplsLdpSessionStatsEntry.

A count of the Session Initialization messages which were sent or received by this LDP Entity and were NAK'd. In other words, this counter counts the number of session initializations that failed. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

A count of the Session Rejected/No Hello Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

A count of the Session Rejected/Parameters Advertisement Mode Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

A count of the Session Rejected/Parameters Max Pdu Length Error Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

A count of the Session Rejected/Parameters Label Range Notification Messages sent or received by this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Bad LDP Identifier Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Bad PDU Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Bad Message Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Bad TLV Length Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Malformed TLV Value Fatal Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Session Keep Alive Timer Expired Errors detected by the session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Shutdown Notifications received related to session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

This object counts the number of Shutdown Notfications sent related to session(s) (past and present) associated with this LDP Entity. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpEntityDiscontinuityTime.

The value of sysUpTime at the time of the most recent addition or deletion to/from the mplsLdpPeerTable/mplsLdpSessionTable.

Information about LDP peers known by Entities in the mplsLdpEntityTable. The information in this table is based on information from the Entity-Peer interaction during session initialization but is not appropriate for the mplsLdpSessionTable, because objects in this table may or may not be used in session establishment.

Information about a single Peer which is related to a Session. NOTE: this table is used to augment the mplsLdpSessionTable.

The LDP identifier of this LDP Peer.

For any given LDP session, the method of label distribution must be specified.

If the value of this object is 0 (zero) then Loop Dection for Path Vectors for this Peer is disabled. Otherwise, if this object has a value greater than zero, then Loop Dection for Path Vectors for this Peer is enabled and the Path Vector Limit is this value.

The type of the Internet address for the mplsLdpPeerTransportAddr object. The LDP specification describes this as being either an IPv4 Transport Address or IPv6 Transport Address which is used in opening the LDP session's TCP connection, or if the optional TLV is not present, then this is the IPv4/IPv6 source address for the UPD packet carrying the Hellos. This object specifies how the value of the mplsLdpPeerTransportAddr object should be interpreted.

The Internet address advertised by the peer in the Hello Message or the Hello source address. The type of this address is specified by the value of the mplsLdpPeerTransportAddrType object.

A table of Sessions between the LDP Entities and LDP Peers. Each row in this table represents a single session.

An entry in this table represents information on a single session between an LDP Entity and LDP Peer. The information contained in a row is read-only. Please note: the Path Vector Limit for the Session is the value which is configured in the corresponding mplsLdpEntityEntry. The Peer's Path Vector Limit is in the mplsLdpPeerPathVectorLimit object in the mplsLdpPeerTable. Values which may differ from those configured are noted in the objects of this table, the mplsLdpAtmSessionTable and the mplsLdpFrameRelaySessionTable. A value will differ if it was negotiated between the Entity and the Peer. Values may or may not be negotiated. For example, if the values are the same then no negotiation takes place. If they are negotiated, then they may differ.

The value of sysUpTime at the time this Session entered its current state as denoted by the mplsLdpSessionState object.

The current state of the session, all of the states 1 - 5 are based on the state machine for session negotiation behavior. Enumeration: 'initialized': 2, 'opensent': 4, 'openrec': 3, 'nonexistent': 1, 'operational': 5.

During session establishment the LSR/LER takes either the active role or the passive role based on address comparisons. This object indicates whether this LSR/LER was behaving in an active role or passive role during this session's establishment. The value of unknown(1), indicates that the role is not able to be determined at the present time. Enumeration: 'active': 2, 'unknown': 1, 'passive': 3.

The version of the LDP Protocol which this session is using. This is the version of the LDP protocol which has been negotiated during session initialization.

The keep alive hold time remaining for this session in units of hundredths of a second. This interval will change when the 'next' Keep Alive message which corresponds to this session is received. A value of zero indicates that the keep alive hold timer is not running.

The negotiated KeepAlive Time which represents the amount of seconds between keep alive messages. The mplsLdpEntityKeepAliveHoldTimer related to this Session is the value that was proposed as the KeepAlive Time for this session. This value is negotiated during session initialization between the entity's proposed value (i.e., the value configured in mplsLdpEntityKeepAliveHoldTimer) and the peer's proposed KeepAlive Hold Timer value. This value is the smaller of the two proposed values.

The value of maximum allowable length for LDP PDUs for this session. This value may have been negotiated during the Session Initialization. This object is related to the mplsLdpEntityMaxPduLength object. The mplsLdpEntityMaxPduLength object specifies the requested LDP PDU length, and this object reflects the negotiated LDP PDU length between the Entity and the Peer.

The value of sysUpTime on the most recent occasion at which any one or more of this session's counters suffered a discontinuity. The relevant counters are the specific instances associated with this session of any Counter32 or Counter64 object contained in the mplsLdpSessionStatsTable. If no such discontinuities have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value. The initial value of this object is the value of sysUpTime when the entry was created in this table. Also, a NMS(command generator) can distinguish when a session between a given Entity and Peer goes away and then a new session is established. This value would change and thus indicate to the NMS(command generator) that this is a different session.

The locally configured keepalive hold time for this session, in seconds. Note that the value of this field reflects configuration at the time of session initialization; this may differ from the configuration that would apply to a new session, if configuration has changed since this session was initialized.

The peer's advertised keepalive hold time for this session in seconds. Note that the value of this field reflects the peer's configuration at the time of session initialization; this may differ from the configuration that would apply to a new session, if the peer's configuration has changed since this session was initialized.

The keepalive hold time that is currently in use for this session, in seconds.

A table of statistics for Sessions between LDP Entities and LDP Peers. The table is read only. Counters are only incremented when the U bit is not set.

An entry in this table represents statistical information on a single session between an LDP Entity and LDP Peer. Errors are only counted if the U bit is not set in the message or TLV.

This object counts the number of Unknown Message Type Errors detected by this LSR/LER during this session. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpSessionDiscontinuityTime.

This object counts the number of Unknown TLV Errors detected by this LSR/LER during this session. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of mplsLdpSessionDiscontinuityTime.

A table of Hello Adjacencies for Sessions.

Each row represents a single LDP Hello Adjacency. An LDP Session can have one or more Hello adjacencies.

An identifier for this specific adjacency.

If the value of this object is 65535, this means that the hold time is infinite (i.e., wait forever). Otherwise, the time remaining for this Hello Adjacency to receive its next Hello Message. This interval will change when the 'next' Hello Message which corresponds to this Hello Adjacency is received unless it is infinite.

The Hello hold time which is negotiated between the Entity and the Peer. The entity associated with this Hello Adjacency issues a proposed Hello Hold Time value in the mplsLdpEntityHelloHoldTimer object. The peer also proposes a value and this object represents the negotiated value. A value of 0 means the default, which is 15 seconds for Link Hellos and 45 seconds for Targeted Hellos. A value of 65535 indicates an infinite hold time.

This adjacency is the result of a 'link' hello if the value of this object is link(1). Otherwise, it is a result of a 'targeted' hello, targeted(2). Enumeration: 'targeted': 2, 'link': 1.

The locally configured hello hold time for this adjacency, in seconds.

The peer's advertised hello hold time for this adjacency, in seconds.

A table of LDP LSPs which map to the mplsInSegmentTable in the MPLS-LSR-MIB module.

An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index for the mplsInSegmentTable (mplsInSegmentLdpLspLabelIndex) from the MPLS-LSR-MIB. The information contained in a row is read-only.

This contains the same value as the mplsInSegmentIndex in the MPLS-LSR-MIB's mplsInSegmentTable.

The Layer 2 Label Type.

The type of LSP connection.

A table of LDP LSPs which map to the mplsOutSegmentTable in the MPLS-LSR-MIB.

An entry in this table represents information on a single LDP LSP which is represented by a session's index triple (mplsLdpEntityLdpId, mplsLdpEntityIndex, mplsLdpPeerLdpId) AND the index (mplsOutSegmentLdpLspIndex) for the mplsOutSegmentTable. The information contained in a row is read-only.

This contains the same value as the mplsOutSegmentIndex in the MPLS-LSR-MIB's mplsOutSegmentTable.

The Layer 2 Label Type.

The type of LSP connection.

The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpFectTable or the most recent change in values to any objects in the mplsLdpFecTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.

This table represents the FEC (Forwarding Equivalence Class) Information associated with an LSP.

Each row represents a single FEC Element.

The index which uniquely identifies this entry.

The type of the FEC. If the value of this object is 'prefix(1)' then the FEC type described by this row is an address prefix. If the value of this object is 'hostAddress(2)' then the FEC type described by this row is a host address. Enumeration: 'prefix': 1, 'hostAddress': 2.

If the value of the 'mplsFecType' is 'hostAddress(2)' then this object is undefined. If the value of 'mplsFecType' is 'prefix(1)' then the value of this object is the length in bits of the address prefix represented by 'mplsFecAddr', or zero. If the value of this object is zero, this indicates that the prefix matches all addresses. In this case the address prefix MUST also be zero (i.e., 'mplsFecAddr' should have the value of zero).

The value of this object is the type of the Internet address. The value of this object, decides how the value of the mplsFecAddr object is interpreted.

The value of this object is interpreted based on the value of the 'mplsFecAddrType' object. This address is then further interpretted as an being used with the address prefix, or as the host address. This further interpretation is indicated by the 'mplsFecType' object. In other words, the FEC element is populated according to the Prefix FEC Element value encoding, or the Host Address FEC Element encoding.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

The value of sysUpTime at the time of the most recent addition/deletion of an entry to/from the mplsLdpLspFecTable or the most recent change in values to any objects in the mplsLdpLspFecTable. If no such changes have occurred since the last re-initialization of the local management subsystem, then this object contains a zero value.

A table which shows the relationship between LDP LSPs and FECs. Each row represents a single LDP LSP to FEC association.

An entry represents a LDP LSP to FEC association.

If the value is inSegment(1), then this indicates that the following index, mplsLdpLspFecSegmentIndex, contains the same value as the mplsInSegmentLdpLspIndex. Otherwise, if the value of this object is outSegment(2), then this indicates that following index, mplsLdpLspFecSegmentIndex, contains the same value as the mplsOutSegmentLdpLspIndex. Enumeration: 'inSegment': 1, 'outSegment': 2.

This index is interpretted by using the value of the mplsLdpLspFecSegment. If the mplsLdpLspFecSegment is inSegment(1), then this index has the same value as mplsInSegmentLdpLspIndex. If the mplsLdpLspFecSegment is outSegment(2), then this index has the same value as mplsOutSegmentLdpLspIndex.

This index identifies the FEC entry in the mplsFecTable associated with this session. In other words, the value of this index is the same as the value of the mplsFecIndex that denotes the FEC associated with this Session.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

The status of this conceptual row. If the value of this object is 'active(1)', then none of the writable objects of this entry can be modified. The Agent should delete this row when the session ceases to exist. If an operator wants to associate the session with a different FEC, the recommended procedure is (as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object) is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. This will also cause this entry to be deleted. Then, set the mplsLdpEntityAdminStatus to enable which enables a new session to be initiated. Once the session is initiated, an entry may be added to this table to associate the new session with a FEC.

This table 'extends' the mplsLdpSessionTable. This table is used to store Label Address Information from Label Address Messages received by this LSR from Peers. This table is read-only and should be updated when Label Withdraw Address Messages are received, i.e., Rows should be deleted as appropriate. NOTE: since more than one address may be contained in a Label Address Message, this table 'sparse augments', the mplsLdpSessionTable's information.

An entry in this table represents information on a session's single next hop address which was advertised in an Address Message from the LDP peer. The information contained in a row is read-only.

An index which uniquely identifies this entry within a given session.

The internetwork layer address type of this Next Hop Address as specified in the Label Address Message associated with this Session. The value of this object indicates how to interpret the value of mplsLdpSessionPeerNextHopAddr.

The next hop address. The type of this address is specified by the value of the mplsLdpSessionPeerNextHopAddrType.

This notification is generated when the value of the 'mplsLdpEntityInitSessionThreshold' object is not zero, and the number of Session Initialization messages exceeds the value of the 'mplsLdpEntityInitSessionThreshold' object.

This notification is sent when the 'mplsLdpEntityPathVectorLimit' does NOT match the value of the 'mplsLdpPeerPathVectorLimit' for a specific Entity.

If this notification is sent when the value of 'mplsLdpSessionState' enters the 'operational(5)' state.

This notification is sent when the value of 'mplsLdpSessionState' leaves the 'operational(5)' state.

Objects that apply to all MPLS LDP implementations.

These objects are for LDP implementations which interface to the Label Information Base (LIB) in the MPLS-LSR-STD-MIB. The LIB is represented in the mplsInSegmentTable, mplsOutSegmentTable and mplsXCTable.

The notification for an MPLS LDP implementation.

The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.

The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.

This table contains ATM specific information which could be used in the 'Optional Parameters' and other ATM specific information.

An entry in this table represents the ATM parameters and ATM information for this LDP entity.

This value represents either the InterfaceIndex or 0 (zero). The value of zero means that the InterfaceIndex is not known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex. If an ATM Label is being used in forwarding data, then the value of this object MUST be the InterfaceIndex.

Denotes the Merge Capability of this Entity. This is the EXACT value for the ATM Session Parameter, field M (for ATM Merge Capabilities). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, ATM Merge Capabilities Specifies the merge capabilities of an ATM switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 VP Merge supported 2 VC Merge supported 3 VP & VC Merge supported If the merge capabilities of the LSRs differ, then: - Non-merge and VC-merge LSRs may freely interoperate. - The interoperability of VP-merge-capable switches with non-VP-merge-capable switches is a subject for future study. When the LSRs differ on the use of VP-merge, the session is established, but VP merge is not used.' Please refer to the following reference for a complete description of this feature. Enumeration: 'vpAndVcMerge': 3, 'notSupported': 0, 'vcMerge': 2, 'vpMerge': 1.

Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityAtmLRTable which correspond to this entry. This is the EXACT value for the ATM Session Parameter, field N (for Number of label range components). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'N, Number of label range components Specifies the number of ATM Label Range Components included in the TLV.' Please refer to the following reference for a complete description of this feature.

If the value of this object is 'bidirectional(0)', a given VCI, within a given VPI, is used as a label for both directions independently. If the value of this object is 'unidirectional(1)', a given VCI within a VPI designates one direction. This is the EXACT value for the ATM Session Parameter, field D (for VC Directionality). The ATM Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can (within a given VPI) support the use of a given VCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning (within a given VPI) a given VCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered VCIs in the VPI/VCI range as labels. The system with the smaller LDP Identifier may assign only even-numbered VCIs in the VPI/VCI range as labels.' Please refer to the following reference for a complete description of this feature. Enumeration: 'bidirectional': 0, 'unidirectional': 1.

The peer LSR may be connected indirectly by means of an ATM VP so that the VPI values may be different on either endpoint so the label MUST be encoded entirely within the VCI field. Enumeration: 'indirect': 2, 'direct': 1.

The default VPI value for the non-MPLS connection. The default value of this is 0 (zero) but other values may be configured. This object allows a different value to be configured.

The Default VCI value for a non-MPLS connection. The default value of this is 32 but other values may be configured. This object allows a different value to be configured.

VPI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVpi', however another value may be configured.

VCI value of the VCC supporting unlabeled traffic. This non-MPLS connection is used to carry unlabeled (IP) packets. The default value is the same as the default value of the 'mplsLdpEntityAtmDefaultControlVci', however another value may be configured.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

The MPLS LDP Entity ATM Label Range (LR) Table. The purpose of this table is to provide a mechanism for configuring a contiguous range of vpi's with a contiguous range of vci's, or a 'label range' for LDP Entities. LDP Entities which use ATM must have at least one entry in this table. There must exist at least one entry in this table for every LDP Entity that has 'mplsLdpEntityLabelType' object with a value of 'atmSessionParameters'.

A row in the LDP Entity ATM Label Range Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds VPI/VCI pairs. These are the same data used in the Initialization Message. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. For example, for a specific LDP Entity index, there could be one entry having LowerBound vpi/vci == 0/32, and UpperBound vpi/vci == 0/100, and a second entry for this same interface with LowerBound vpi/vci == 0/101 and UpperBound vpi/vci == 0/200. However, there could not be a third entry with LowerBound vpi/vci == 0/200 and UpperBound vpi/vci == 0/300 because this label range overlaps with the second entry (i.e., both entries now have 0/200). A row will not become active unless a unique and non-overlapping range is specified. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table. A request to create a row with an overlapping range should result in an inconsistentValue error.

The minimum VPI number configured for this range. The value of zero is a valid value for the VPI portion of the label.

The minimum VCI number configured for this range.

The maximum VPI number configured for this range.

The maximum VCI number configured for this range.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

A table which relates sessions in the 'mplsLdpSessionTable' and their label range intersections. There could be one or more label range intersections between an LDP Entity and LDP Peer using ATM as the underlying media. Each row represents a single label range intersection. This table cannot use the 'AUGMENTS' clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.

An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer. The information contained in a row is read-only.

The minimum VPI number for this range.

The minimum VCI number for this range.

The maximum VPI number for this range.

The maximum VCI number for this range.

Objects that apply to all MPLS LDP implementations using ATM as the Layer 2.

The Module is implemented with support for read-create and read-write. In other words, both monitoring and configuration are available when using this MODULE-COMPLIANCE.

The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.

This table contains Frame Relay specific information which could be used in the 'Optional Parameters' and other Frame Relay specific information.

An entry in this table represents the Frame Relay optional parameters associated with the LDP entity.

This value represents either the InterfaceIndex of the 'ifLayer' where the Frame Relay Labels 'owned' by this entry were created, or 0 (zero). The value of zero means that the InterfaceIndex is not known. For example, if the InterfaceIndex is created subsequent to the Frame Relay Label's creation, then it would not be known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex. If an Frame Relay Label is being used in forwarding data, then the value of this object MUST be the InterfaceIndex.

This represents whether or not the Frame Relay merge capability is supported. This is the EXACT value for the Frame Relay Session Parameter, field M (for Frame Relay Merge Capabilities). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'M, Frame Relay Merge Capabilities Specifies the merge capabilities of a Frame Relay switch. The following values are supported in this version of the specification: Value Meaning 0 Merge not supported 1 Merge supported Non-merge and merge Frame Relay LSRs may freely interoperate.' Please refer to the following reference for a complete description of this feature. Enumeration: 'notSupported': 0, 'supported': 1.

Number of Label Range Components in the Initialization message. This also represents the number of entries in the mplsLdpEntityFrameRelayLRTable which correspond to this entry. This is the EXACT value for the Frame Relay Session Parameter, field N (for Number of label range components). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'N, Number of label range components Specifies the number of Frame Relay Label Range Components included in the TLV.' Please refer to the following reference for a complete description of this feature.

If the value of this object is 'bidirectional(0)', then the LSR supports the use of a given DLCI as a label for both directions independently. If the value of this object is 'unidirectional(1)', then the LSR uses the given DLCI as a label in only one direction. This is the EXACT value for the Frame Relay Session Parameter, field D (for VC Directionality). The Frame Relay Session Parameter is an optional parameter in the Initialization Message. The description from rfc3036.txt is: 'D, VC Directionality A value of 0 specifies bidirectional VC capability, meaning the LSR can support the use of a given DLCI as a label for both link directions independently. A value of 1 specifies unidirectional VC capability, meaning a given DLCI may appear in a label mapping for one direction on the link only. When either or both of the peers specifies unidirectional VC capability, both LSRs use unidirectional VC label assignment for the link as follows. The LSRs compare their LDP Identifiers as unsigned integers. The LSR with the larger LDP Identifier may assign only odd-numbered DLCIs in the range as labels. The system with the smaller LDP Identifier may assign only even-numbered DLCIs in the range as labels.' Please refer to the following reference for a complete description of this feature. Enumeration: 'bidirectional': 0, 'unidirection': 1.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

This table contains information about the Optional Parameters for the Frame Relay Session in the LDP Initialization Message, specifically it contains information about the Frame Relay Label Range Components. If the value of the object 'mplsLdpEntityLabelType' contains the value of 'frameRelaySessionParameters(3)' then there must be at least one corresponding entry in this table.

An entry in this table represents the Frame Relay Label Range Component associated with the LDP entity.

The lower bound which is supported. This value should be the same as that in the Frame Relay Label Range Component's Minimum DLCI field. The value of zero is valid for the minimum DLCI field of the label.

The upper bound which is supported. This value should be the same as that in the Frame Relay Label Range Component's Maximum DLCI field.

This object specifies the length of the DLCI bits. This is the EXACT value for the Len field of the Frame Relay Label Range Component. The description from rfc3036.txt is: 'Len This field specifies the number of bits of the DLCI. The following values are supported: Len DLCI bits 0 10 2 23 Len values 1 and 3 are reserved.' Please refer to the following reference for a complete description of this feature. Enumeration: 'tenDlciBits': 0, 'twentyThreeDlciBits': 2.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

A table of Frame Relay label range intersections between the LDP Entities and LDP Peers. Each row represents a single label range intersection. NOTE: this table cannot use the 'AUGMENTS' clause because there is not necessarily a one-to-one mapping between this table and the mplsLdpSessionTable.

An entry in this table represents information on a single label range intersection between an LDP Entity and LDP Peer. The information contained in a row is read-only.

The lower bound of DLCIs which are supported. The value of zero is a valid value for the minimum DLCI field of the label.

The upper bound of DLCIs which are supported.

This object specifies the DLCI bits. Enumeration: 'tenDlciBits': 0, 'twentyThreeDlciBits': 2.

Objects that apply to all MPLS LDP implementations using Frame Relay as the Layer 2.

The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.

The MPLS LDP Entity Generic Label Range (LR) Table. The purpose of this table is to provide a mechanism for configurating a contiguous range of generic labels, or a 'label range' for LDP Entities. LDP Entities which use Generic Labels must have at least one entry in this table. In other words, this table 'extends' the mpldLdpEntityTable for Generic Labels.

A row in the LDP Entity Generic Label Range (LR) Table. One entry in this table contains information on a single range of labels represented by the configured Upper and Lower Bounds pairs. NOTE: there is NO corresponding LDP message which relates to the information in this table, however, this table does provide a way for a user to 'reserve' a generic label range. NOTE: The ranges for a specific LDP Entity are UNIQUE and non-overlapping. A row will not be created unless a unique and non-overlapping range is specified.

The minimum label configured for this range.

The maximum label configured for this range.

This value of this object is perPlatform(1), then this means that the label space type is per platform. If this object is perInterface(2), then this means that the label space type is per Interface. Enumeration: 'perPlatform': 1, 'perInterface': 2.

This value represents either the InterfaceIndex of the 'ifLayer' where these Generic Label would be created, or 0 (zero). The value of zero means that the InterfaceIndex is not known. However, if the InterfaceIndex is known, then it must be represented by this value. If an InterfaceIndex becomes known, then the network management entity (e.g., SNMP agent) responsible for this object MUST change the value from 0 (zero) to the value of the InterfaceIndex.

The storage type for this conceptual row. Conceptual rows having the value 'permanent(4)' need not allow write-access to any columnar objects in the row.

Objects that apply to all MPLS LDP implementations using Generic Labels as the Layer 2.

The Module is implemented with support for read-only. In other words, only monitoring is available by implementing this MODULE-COMPLIANCE.