No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

S12700 V200R011C10 MIB Reference

This document provides the function overview, relationships between tables, description of single objects, description of MIB tables, and description of alarm objects.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
mplsLdpEntityTable

mplsLdpEntityTable

This table contains information about the MPLS Label Distribution Protocol Entities which exist on this 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 indexes of this table are mplsLdpEntityLdpId and mplsLdpEntityIndex.

OID

Object Name

Syntax

Max Access

Description

Implemented Specifications

1.3.6.1.2.1.10.166.4.1.2.3.1.1

mplsLdpEntityLdpId

MplsLdpIdentifier

Not-accessible

The LDP identifier.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.10.166.4.1.2.3.1.2

mplsLdpEntityIndex

IndexInteger

Not-accessible

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 depends on the implementation.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.10.166.4.1.2.3.1.3

mplsLdpEntityProtocolVersion

Unsigned32(1..65535)

Read-create

The version number of the LDP protocol which will be used in the session initialization message.

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.4

mplsLdpEntityAdminStatus

INTEGER {enable(1),disable(2)}

Read-create

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, 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 operator 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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.5

mplsLdpEntityOperStatus

INTEGER {unknown(1),enabled(2),disabled(3)}

Read-only

The operating status of this LDP Entity.

The value of unknown(1) indicates that the operating status cannot be determined at this time.

The value of unknown(1) should be a transient condition before changing to enabled(2) or disabled(3).

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.10.166.4.1.2.3.1.6

mplsLdpEntityTcpPort

InetPortNumber

Read-create

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

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.7

mplsLdpEntityUdpDscPort

InetPortNumber

Read-create

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

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.8

mplsLdpEntityMaxPduLength

Unsigned32 (256..65535)

Read-create

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 operator should explicitly choose the default value (that is 4096), or some other value.

The receiving LSR MUST calculate the maximum PDU length for the session by using the smaller of its proposals and its peer's proposals for Max PDU Length.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.9

mplsLdpEntityKeepAliveHoldTimer

Unsigned32 (1..65535)

Read-create

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

This object indicates the keepalive timer of the LDP.

Huawei implements the value from 30 to 65535 seconds.

By default, the value is 45 seconds.

Currently, the maximum access is read-only; the value range of 3 to 65535 is supported.

1.3.6.1.2.1.10.166.4.1.2.3.1.10

mplsLdpEntityHelloHoldTimer

Unsigned32 (0..65535)

Read-create

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 (that is, 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 (that is, the default Hold time for Targeted Hellos is 45 seconds).

A value of 65535 means infinite (that is, 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.

This object indicates the hello timer of the LDP.

Huawei implements the value from 3 to 65535 seconds.

By default, the hello timer for the link 15 seconds, and the hello timer for the destination is 45 seconds.

Currently, the maximum access is read-only; the value range of 3 to 65535 is supported.

1.3.6.1.2.1.10.166.4.1.2.3.1.11

mplsLdpEntityInitSessionThreshold

Integer32(0..100)

Read-create

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.12

mplsLdpEntityLabelDistMethod

MplsLabelDistributionMethod

Read-create

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

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.10.166.4.1.2.3.1.13

mplsLdpEntityLabelRetentionMode

MplsRetentionMode

Read-create

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, that is, 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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.14

mplsLdpEntityPathVectorLimit

Integer32 (0..255)

Read-create

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 Detection 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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.15

mplsLdpEntityHopCountLimit

Integer32 (0..255)

Read-create

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.16

mplsLdpEntityTransportAddrKind

INTEGER {interface(1),loopback(2)}

Read-create

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.17

mplsLdpEntityTargetPeer

TruthValue

Read-create

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

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.18

mplsLdpEntityTargetPeerAddrType

InetAddressType

Read-create

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

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.19

mplsLdpEntityTargetPeerAddr

InetAddress

Read-create

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

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.20

mplsLdpEntityLabelType

MplsLdpLabelType

Read-create

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.21

mplsLdpEntityDiscontinuityTime

TimeStamp

Read-only

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.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.10.166.4.1.2.3.1.22

mplsLdpEntityStorageType

StorageType

Read-create

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.

Currently, the maximum access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.23

mplsLdpEntityRowStatus

RowStatus

Read-create

The status of this conceptual row. All writable objects in this row may be modified at any time, however, as described in detail in the section entitled, 'Changing Values After Session Establishment', and again described in the DESCRIPTION clause of the mplsLdpEntityAdminStatus object, if a session has been initiated with a Peer, changing objects in this table will wreak havoc with the session and interrupt traffic.

To repeat again: the recommended procedure is to set the mplsLdpEntityAdminStatus to down, thereby explicitly causing a session to be torn down. Then, change objects in this entry, and enable the mplsLdpEntityAdminStatus, which enables a new session to be initiated.

Currently, the maximum access is read-only.

Creation Restriction

The entries in this table cannot be created.

Modification Restriction

The entries in this table cannot be modified.

Deletion Restriction

The entries in this table cannot be deleted.

Access Restriction

The LDP must be enabled on the interface.

Translation
Download
Updated: 2019-03-29

Document ID: EDOC1000178122

Views: 734428

Downloads: 36

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next