vRtrLdpSessMaxFecThresChanged
TIMETRA-LDP-MIB ·
.1.3.6.1.4.1.6527.3.1.3.8.0.7
Object
notification
obsolete
[CAUSE] A vRtrLdpSessMaxFecThresChanged notification is generated when
the number of FECs accepted from the peer has exceeded or drops below
vRtrLdpPeerMaxFecThreshold percent of the value specified by
vRtrLdpPeerMaxFec.
New notification will not be generated if multiple internal event
change occurs for the same level indicated by
vRtrLdpSessOperThresLevel during a 2 minute interval.
If any parameter in FEC limit configuration changes then we would
always raise this trap if current number of FECs are above the
configured threshold or has crossed the threshold downwards. If we
remain on or below the configured threshold before and after the
configuration changes then no trap would be generated.
[EFFECT] No direct effect but if the peer LSR continues to send
further Label Mapping Message, then the number of FECs may exceed the
configured maximum (vRtrLdpPeerMaxFec) resulting in the generation of
vRtrLdpSessMaxFecLimitReached notification.
[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.7- 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 |
| vRtrLdpSessMaxFecLimitReached obsolete [CAUSE] A vRtrLdpSessMaxFecLimitReached notification is generated when
the number of FECs accepted from the peer has reached the value
specified by vRtrLdpPeerMaxFec.
I… | notification | - | .1.3.6.1.4.1.6527.3.1.3.8.0.8 |
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 |
| vRtrLdpSessOperThresLevel obsolete The value of vRtrLdpSessOperThresLevel indicates whether the number of
fec-bindings has exceeded or is below the configured fec threshold or
has reached the configured fec limit. | scalar | Enumeration | .1.3.6.1.4.1.6527.3.1.2.8.17.10 |
| 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 |