vRtrLdpSessMaxFecLimitReached
TIMETRA-LDP-MIB ·
.1.3.6.1.4.1.6527.3.1.3.8.0.8
Object
notification
obsolete
[CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when
the number of FECs accepted from the peer has reached the value
specified by vRtrLdpPeerMaxFec.
If the current number of FECs go below the limit but higher than the
configured threshold and again start to increase and hit the limit a
second time, we will raise a trap if 2 or more minutes have elapsed
since the first vRtrLdpSessMaxFecLimitReached trap was sent.
If any parameter in FEC limit configuration changes and the current
number of FECs are equal to or higher than the limit specified by
vRtrLdpPeerMaxFec, then we would always raise the
vRtrLdpSessMaxFecLimitReached trap.
[EFFECT] When the number of FECs exceed the configured maximum
(vRtrLdpPeerMaxFec) it results in any of the following:
(1) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
Capability is supported, then Overload procedure will take place.
(2) If vRtrLdpPeerMaxFecLogOnly is set to 'false' and LSR Overload
Capability is not supported, Label Mapping Message will be returned
with Label Release Message.
(3) If vRtrLdpPeerMaxFecLogOnly is set to 'true', no action will be
taken.
[RECOVERY] Appropriate Configuration changes in local or peer LSR will
be required.
This notification was obsoleted in release 13.0.
Context
- MIB
- TIMETRA-LDP-MIB
- OID
.1.3.6.1.4.1.6527.3.1.3.8.0.8- Type
- notification
- Status
- obsolete
- Parent
- tmnxLdpNotifications
- Siblings
- 7
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vRtrLdpStateChange The vRtrLdpStateChange notification is generated when the LDP protocol
is created or deleted in the router. | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.1 |
| vRtrLdpInstanceStateChange obsolete [CAUSE] The vRtrLdpInstanceStateChange notification may be triggered
for the following reasons:
1) The LDP instance changes state operationally.
2) vRtrLdpGenOperState … | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.2 |
| vRtrLdpIfStateChange obsolete The vRtrLdpIfStateChange notification is generated when the LDP
interface changes state either administratively or operationally.
This notification was obsoleted in rel… | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.3 |
| vRtrLdpSvcIdMismatch obsolete The vRtrLdpSvcIdMismatch notification is generated when there is a
mismatch of local and remote service IDs. | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.4 |
| vRtrLdpGroupIdMismatch The vRtrLdpGroupIdMismatch notification is generated when there is a
mismatch of local and remote group IDs. | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.5 |
| vRtrLdpSessionStateChange obsolete [CAUSE] The vRtrLdpSessionStateChange notification is generated when
an Overload Notification is sent to or received from the peer
vRtrLdpPeerLdpId for a fec type of vRtrLdpSessOv… | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.6 |
| vRtrLdpSessMaxFecThresChanged obsolete [CAUSE] A vRtrLdpSessMaxFecThresChanged notification is generated when
the number of FECs accepted from the peer has exceeded or drops below
vRtrLdpPeerMaxFecThreshold percent of … | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.7 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vRtrLdpPeerMaxFec obsolete The value of vRtrLdpPeerMaxFec specifies the maximum number of FECs
that will be accepted from this peer LSR.
A value of zero specifies there is no limit to the num… | column | Unsigned32 | .1.3.6.1.4.1.6527.3.1.2.8.16.1.22 |
| vRtrLdpSessOperMaxFecThreshold obsolete The value of vRtrLdpSessOperMaxFecThreshold indicates the operational
percentage of vRtrLdpPeerMaxFec.
This object was obsoleted in release 13.0. | column | percent SNMPv2-SMIUnsigned32 | .1.3.6.1.4.1.6527.3.1.2.8.9.1.39 |