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

All rights reserved

H3CMPLS provides support for multiple incarnations of the MPLS Stack in a target. The LSR defined in the standard MIB is treated as an incarnation in this MIB. Using a local policy the Network administrator must group the LDP Entities that should be placed in an incarnation.

An entry in this table represents an LSR incarnation. All the entries in this table are created initially when the LDP is initiated. The row status of each entry will be in 'notInService' state initially. The row status must be set to 'active' after the necessary configurations are complete with respect to an incarnation. Currenlty the LSR ID of the incarnation is the only mandatory parameter that must be set before the rowStatus is set to 'active'. An LSR Incarnation Entity is uniquely indexed by its Incarnation Identifier.

The LSR's Identifier.

A indication of whether this LSR supports loop detection. A value of 'true' indicates this LSR does support loop detection. A value of 'false' indicates this LSR does not support loop detection.

To enable loop detection the value of this object should be 'enabled(1)'. Otherwise, to turn off loop detection, set this value to 'disabled(2)'. Enumeration: 'disabled': 2, 'enabled': 1.

This object only has meaning if hh3cMplsLdpLsrLoopDetectionPresent has the value of 'true'. The value of this object represents the limit of path vectors which this LSR uses to treat the message as if it had traversed a loop.

This object only has meaning if hh3cMplsLdpLsrLoopDetectionPresent has the value of 'true'. The value of this object represents the limit on the Hop Count which this LSR uses to treat the message as if it had traversed a loop.

A indication of whether this LSR supports loop prevention. A value of 'true' indicates this LSR does support loop prevention. A value of 'false' indicates this LSR does not support loop prevention. Current release of H3CMPLS does not provide support to assign this MIB object with a value 'true'.

To enable loop prevention the value of this object should be 'enabled(1)'. Otherwise, to turn off loop prevention, set this value to 'disabled(2)'. Current release of H3CMPLS does not provide support to assign this MIB object with a value 'enabled'. Enumeration: 'disabled': 2, 'enabled': 1.

The LSR 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. Current release of H3CMPLS does not provide support to assign this MIB object with a value 'liberal'. Enumeration: 'liberal': 2, 'conservative': 1.

The incarnation acts as index to all the elements in this table.

The maximum number of LDP entities that can be supported by this Incarnation.

The maximum number of Local LDP peers that can be supported by this Incarnation.

The maximum number of Remote LDP peers that can be supported by this Incarnation.

The maximum number of Label enabled Interfaces that can be supported by this Incarnation.

The maximum number of Label Switched Paths that can be supported by this Incarnation.

The maximum number of CRLSPs that can be supported by this Incarnation.

The maximum number of ER-Hops that can be supported in a CRLSP tunnel.

An object that allows entries in this table to be created and deleted using the RowStatus convention.

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

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. An LPD Entity is uniquely indexed by its LPD Identifier.

The LDP identifier which uniquely identifies the LDP Entity. This is s six octet quantity which is used to identify an Label Switch Router (LSR) label space. 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.

The type of label spaces associated with this LDP Entity. The values are 'unknown(1)' The type of label space is not known. 'perInterface(2)' The type of label space is tied to an interface. 'perPlatform(3)' The type of label space is tied to the platform. Enumeration: 'unknown': 1, 'perPlatform': 3, 'perInterface': 2.

The Default VPI value used in the label for the default VPI.

The Default VCI value used in the label for the default VCI.

VPI value of the VCC supporting unlabeled traffic.

VCI value of the VCC supporting unlabeled traffic.

Sets the merge capability for this LDP entity. Current Release of H3CMPLS does not provide support for any kind of Merge. Enumeration: 'noMerge': 0, 'vpVcMerge': 3, 'vcMerge': 2, 'vpMerge': 1.

Sets the VC directionality for this LDP entity. Enumeration: 'bidirectional': 1, 'unidirectional': 2.

The well known LDP Discovery Port.

The maximum transmission unit (MTU) that was configured for this entity.

The two octet value which is the proposed keep alive hold timer for this LDP Entity.

When attempting to establish a session with a given Peer, the given LDP Entity should send out a notification when exceeding this threshold. A value of 0 (zero) for this object indicates that the threshold is infinity. In other words, a notification will not be sent if the value of this object is 0 (zero).

For any given LDP session, the method of label distribution must be specified. Current release of H3CMPLS does not provide support for 'downstreamUnsolicited'. Enumeration: 'downstreamOnDemand': 1, 'downstreamUnsolicited': 2.

For any given LDP session, the method of label allocation must be specified. Label can be allocated in either ordered mode or in the independent mode. Enumeration: 'independent': 2, 'ordered': 1.

The two octet value which is the proposed hello hold timer for this LDP Entity.

An object that allows entries in this table to be created and deleted using the RowStatus convention.

This table contains information about the interfaces that are associated with an LDP Entity. There should be atleast one interface associated with each LDP Entity. If the LDP Entity supports 'per interface based label space' label type then, atmost one interface can be associated with the LDP entity. If the LDP Entity supports 'per platform based label space' label type then, more than one interface can be associated with the LDP Entity.

An entry in this table represents an Interface that is associated with a LDP entity. An entry can be created by a network administrator or by an SNMP agent as instructed by LDP. An interface (row in this table) can be created/deleted only when the associted LDP Entity row status has the value notInService or notReady.

Identifier that uniquely identifies the Interface with respect to an LDP Entity. The ifIndex value corresponds to the IfIndex value of the MIB-II

The IPv4 address associated with the interface.

An object that allows entries in this table to be created and deleted using the RowStatus convention.

The MPLS LDP Entity Configurable ATM Label Range Table. The purpose of this table is to provide a mechanism for specifying 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.

A row in the LDP Entity Configurable 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. 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 ConfLowerBound vpi/vci == 0/32, and ConfUpperBound vpi/vci == 0/100, and a second entry for this same interface with ConfLowerBound vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. However, there could not be a third entry with ConfLowerBound vpi/vci == 0/200 and ConfUpperBound 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 be created unless a unique and non-overlapping range is specified. Thus, row creation implies a one-shot row creation of LDP EntityID and ConfLowerBound vpi/vci and ConfUpperBound vpi/vci. At least one label range entry for a specific LDP Entity MUST include the default VPI/VCI values denoted in the LDP Entity Table.

The minimum VPI number configured for this range.

The minimum VCI number configured for this range.

The maximum VPI number configured for this range.

The maximum VCI number configured for this range.

An object that allows entries in this table to be created and deleted using the RowStatus convention.

This table is a read-only table which augments the MplsLdpConfEntityTable. 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.

A count of the total attempted sessions for this LDP Entity.

Information about LDP peers which have been discovered by the LDP Entities that are managed by this agent.

Information about a single Peer.

An identifier for the LDP peer that is unique within the scope of this agent.

The LDP identifier of this LDP Peer.

The type of the internetwork layer address of this LDP peer. This object indicates how the value of hh3cMplsLdpPeerInternetworkAddr is to be interpreted.

The value of the internetwork layer address of this LDP peer.

The default maximum transmission unit (MTU) of the LDP Peer.

The two octet unsigned non zero INTEGER that indicates the number of seconds that this Peer proposes for the value of the KeepAlive Interval.

For any given LDP session, the method of label distribution must be specified. Enumeration: 'downstreamOnDemand': 1, 'downstreamUnsolicited': 2.

Indicates whether a peer is a local peer or a remote peer Enumeration: 'remote': 2, 'local': 1.

An object that allows entries in this table to be created and deleted using the RowStatus convention.

The MPLS LDP Peer Configurable ATM Label Range Table. The purpose of this table is to provide a mechanism for specifying a contiguous range of vpi's with a contiguous range of vci's, or a 'label range' for LDP Peers. LDP Peers which use ATM must have at least one entry in this table.

A row in the LDP Peer Configurable 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. NOTE: The ranges for a specific LDP Peer are UNIQUE and non-overlapping. For example, for a specific LDP Peer index, there could be one entry having ConfLowerBound vpi/vci == 0/32, and ConfUpperBound vpi/vci == 0/100, and a second entry for this same interface with ConfLowerBound vpi/vci == 0/101 and ConfUpperBound vpi/vci == 0/200. However, there could not be a third entry with ConfLowerBound vpi/vci == 0/200 and ConfUpperBound 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 be created unless a unique and non-overlapping range is specified. Thus, row creation implies a one-shot row creation of LDP PeerIndex and ConfLowerBound vpi/vci and ConfUpperBound vpi/vci. At least one label range entry for a specific LDP Peer MUST include the default VPI/VCI values denoted in the LDP Peer Table.

The minimum VPI number configured for this range.

The minimum VCI number configured for this range.

The maximum VPI number configured for this range.

The maximum VCI number configured for this range.

A table of Sessions between the LDP Entities and LDP Peers.

An entry in this table represents information on a single session between an LDP Entity and LDP Peer.

An unique identifier for this entry such that it identifies a specific LDP Session.

The LDP Session identifier.

The version of the LDP Protocol which this session is using.

The keep alive hold time remaining for this session.

An indication of whether the LDP Entity associated with this session is acting in an 'active' role or a 'passive' role. Enumeration: 'active': 1, 'passive': 2.

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.

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.

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 the adjacency.

The time remaining for this Hello Adjacency.

The hh3cMplsLdpCrlspTnlTable allows new CRLSP MPLS tunnels to be created. The ER hops associated with a CRLSP tunnel are to be configured using the hh3cMplsLdpCrlspErHopTable.

An entry in this table represents an CRLSP MPLS tunnel. An entry can be created by a network administrator.

Uniquely identifies this row.

The 'canonical' name assigned to the tunnel that can be used to refer to it on the 'console' port.

Whether this tunnel is unidirectional-incoming, unidirectional-outgoing, or bidirectional. Enumeration: 'out': 2, 'inOut': 3, 'in': 1.

The signaling protocol, if any, that set up this tunnel. Enumeration: 'none': 1, 'ldp': 2, 'rsvp': 3.

The setup priority of this tunnel.

The holding priority for this tunnel.

The peak rate - the maximum rate at which traffic will be sent on the CRLSP.

The peak burst size - the maximum burst size of the traffic that can occur in the established CRLSP.

The committed rate - the committed rate at which traffic will be sent on the CRLSP.

The committed burst size - the committed burst size of the traffic that will be handled in the established CRLSP.

The Excess burst size - the excess burst size limit to be used for traffic conditioning at the ingress of the CRLSP.

Indicates whether the loose-routed hops of this tunnel are to be pinned.

Indicates the frequency of usage of the established CRLSP.

Indicates the weight that is the established CRLSP.

For controlling the state of this row. The status can be set to 'active' only when atleast one ERHOP is created in the hh3cMplsLdpErHopTable, associated with this tunnel.

The hh3cMplsLdpCrlspErHopTable is used to indicate the hops, strict or loose, for an MPLS CRLSP tunnel defined in hh3cMplsLdpCrlspTnlTable. There must be atleast one entry in this table for each CRLSP tunnel that is supported in the hh3cMplsLdpCrlspTnlTable. The first row in the table is the first hop after the origination point of the tunnel.

An entry in this table represents a tunnel hop. An entry is created by a network administrator for signalled ERLSP set up by LDP or RSVP.

Secondary index into this table identifying the particular hop.

Address type of this hop. Enumeration: 'ipV4': 1.

If hh3cMplsLdpCrlspErHopAddrType is ipV4(1), IPv4 address of this hop. This object is not significant otherwise and should return a value of 0.

If hh3cMplsLdpCrlspErHopAddrType is ipV4(1), prefix length for this hop's IPv4 address. This object is not significant otherwise and should return a value of 0.

Whether this is a strict or loose hop. Enumeration: 'strict': 1, 'loose': 2.

For creating, modifying and deleting this row.

This notification is generated whenever the value of hh3cMplsLdpEntityFailedInitSessionThreshold is exceeded.

This notification is generated by the Ingress LSR of the CRLSP tunnel on the receipt of Label mapping message from the downstream LSR for the LAbel request sent for the CRLSP tunnel.

This notification is generated when a CRLSP Row status is modified to destroy the CRLSP tunnel. - due to pre-emption etc.,

This notification is generated by the Ingress LSR of the CRLSP tunnel on the receipt of Nak message from the downstream LSR for the Label request sent for the CRLSP tunnel. This can occur due to improper ER hop values being set, or Traffic resources not available etc.,

This notification is generated by LDP to notify the Incarnation UP Event failure

This notification is generated by LDP to notify the Incarnation DOWN Event failure

This notification is generated by LDP to notify the ENTITY UP Event failure

This notification is generated by LDP to notify the ENTITY DOWN Event failure

Generation of this trap occurs when the value of 'hh3cMplsLdpSessionState' enters the 'operational(5)' state.

Generation of this trap occurs when the value of 'hh3cMplsLdpSessionState' leaves the 'operational(5)' state.