mplsLdpEntityTable

1.3.6.1.2.1.10.166.4.1.2.3.1.1

mplsLdpEntityLdpId

OCTET STRING{(6,6)}

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

Unsigned32{(1,4294967295)}

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 is dependant

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.

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

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.

The actually supported 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 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).

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

Unsigned32{(0,65535)}

read-create

The TCP Port for

LDP. The default value is the well-known

value of this port.

The actually supported access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.7

mplsLdpEntityUdpDscPort

Unsigned32{(0,65535)}

read-create

The UDP Discovery Port for

LDP. The default value is the

well-known value for this port.

The actually supported 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 (i.e., 4096),

or some other value.

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.

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

1.3.6.1.2.1.10.166.4.1.2.3.1.9

mplsLdpEntityKeepAliveHoldTimer

Unsigned32{(1,65535)}

read-create

The actually supported value range is 30-65535.

RO(Size list:3--65535)

1.3.6.1.2.1.10.166.4.1.2.3.1.10

mplsLdpEntityHelloHoldTimer

Unsigned32{(0,65535)}

read-create

The actually supported value range is 3-65535.

RO(Size list:3--65535)

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.

The actually supported access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.12

mplsLdpEntityLabelDistMethod

INTEGER{downstreamOnDemand(1),downstreamUnsolicited(2)}

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

INTEGER{conservative(1),liberal(2)}

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,

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.

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

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

The actually supported 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.

The actually supported 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.

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

1.3.6.1.2.1.10.166.4.1.2.3.1.17

mplsLdpEntityTargetPeer

INTEGER{true(1),false(2)}

read-create

If this LDP entity uses targeted peer then set

this to true.

The actually supported access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.18

mplsLdpEntityTargetPeerAddrType

INTEGER{unknown(0),ipv4(1),ipv6(2),ipv4z(3),ipv6z(4),dns(16)}

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.

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

1.3.6.1.2.1.10.166.4.1.2.3.1.19

mplsLdpEntityTargetPeerAddr

OCTET STRING{(0,255)}

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.

The actually supported access is read-only.

1.3.6.1.2.1.10.166.4.1.2.3.1.20

mplsLdpEntityLabelType

INTEGER{generic(1),atm(2),frameRelay(3)}

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.

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

1.3.6.1.2.1.10.166.4.1.2.3.1.21

mplsLdpEntityDiscontinuityTime

TimeTicks

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

INTEGER{other(1),volatile(2),nonVolatile(3),permanent(4),readOnly(5)}

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.

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

1.3.6.1.2.1.10.166.4.1.2.3.1.23

mplsLdpEntityRowStatus

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

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, then set

the mplsLdpEntityAdminStatus to enable,

which enables a new session to be initiated.

The actually supported access is read-only.