Home
Monitor and troubleshoot
Documents under this category provide information about monitoring, diagnosing, and troubleshooting router issues.
Log Events Guide
This guide provides information about log events.
LDP

Monitor and troubleshoot
Documents under this category provide information about monitoring, diagnosing, and troubleshooting router issues.
- Log Events Guide
  This guide provides information about log events.
- OAM and Diagnostics Guide
  This guide describes how to configure features such as service mirroring and Lawful Intercept (LI), and how to use the Operations, Administration, and Maintenance (OAM) and diagnostics tools.
- 7450 and 7750 Troubleshooting Guide
- 7950 Troubleshooting Guide
- Log Events Lookup Tool
  A searchable HTML list of the SR OS events.

LDP

vRtrLdpGroupIdMismatch

Table 1. vRtrLdpGroupIdMismatch properties
Property name	Value
Application name	LDP
Event ID	2004
Event name	vRtrLdpGroupIdMismatch
SNMP notification prefix and OID	TIMETRA-LDP-MIB.tmnxLdpNotifications.5
Default severity	minor
Message format string	Apparent mismatch of group IDs - local group ID: $vRtrLdpNotifyLocalGroupID$, remote group ID: $vRtrLdpNotifyRemoteGroupID$
Cause	N/A
Effect	N/A
Recovery	N/A

vRtrLdpNgAddrFecCommMismatch

Table 2. vRtrLdpNgAddrFecCommMismatch properties
Property name	Value
Application name	LDP
Event ID	2021
Event name	vRtrLdpNgAddrFecCommMismatch
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.11
Default severity	minor
Message format string	Mismatched community - vRtrID: $vRtrID$ Community vRtrLdpNgAddrFecCommunity
Cause	A vRtrLdpNgAddrFecCommMismatch notification is generated when two or more peer routers advertising labels for the given address FEC have been assigned differing communities, or some have been assigned communities and some have not. It will also be generated if multiple LDP peer routers have been configured to advertise their local LSR-ID as a FEC, and those peer routers have been assigned differing communities. This notification is rate-limited to at most one notification every 60 seconds.
Effect	This condition indicates that the network is mis-configured, and it is likely that the affected address FEC is not being advertised to the routers which the operator intends.
Recovery	Analyze, check and fix the community configuration for all LDP session-parameters and LDP targeted-session peer-templates in the network to find the error. Start with the configuration on the router generating the notification, and if this is correct, look next at the routers advertising the labels to see if their configuration is correct.

vRtrLdpNgIfStateChange

Table 3. vRtrLdpNgIfStateChange properties
Property name	Value
Application name	LDP
Event ID	2013
Event name	vRtrLdpNgIfStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.3
Default severity	minor
Message format string	Interface instance state changed - vRtrID: $vRtrID$, $interfaceName$, administrative state: $vRtrLdpNgIfAdminState$, operational state: $vRtrLdpNgIfOperState$
Cause	The vRtrLdpNgIfStateChange notification is generated when the LDP interface changes state either administratively or operationally.
Effect	Based on the vRtrLdpNgIfOperDownReason reason code, the system may not be able to accept new requests from peers over this interface.
Recovery	Based on the vRtrLdpNgIfOperDownReason reason code, appropriate configuration changes in LDP may be required.

vRtrLdpNgInetIfStateChange

Table 4. vRtrLdpNgInetIfStateChange properties
Property name	Value
Application name	LDP
Event ID	2014
Event name	vRtrLdpNgInetIfStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.4
Default severity	minor
Message format string	Sub-interface instance state changed - vRtrID: $vRtrID$, $interfaceName$, administrative state: $vRtrLdpNgInetIfAdminState$, operational state: $vRtrLdpNgInetIfOperState$
Cause	The vRtrLdpNgInetIfStateChange notification is generated when the LDP sub-interface changes state either administratively or operationally.
Effect	Based on the vRtrLdpNgInetIfOperDownReason reason code, the system may not be able to accept new requests over this interface.
Recovery	Based on the vRtrLdpNgInetIfOperDownReason reason code, appropriate configuration changes in LDP may be required.

vRtrLdpNgIpv4InstStateChange

Table 5. vRtrLdpNgIpv4InstStateChange properties
Property name	Value
Application name	LDP
Event ID	2011
Event name	vRtrLdpNgIpv4InstStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.1
Default severity	minor
Message format string	IPv4 Instance state changed - vRtrID: $vRtrID$, administrative state: $vRtrLdpNgGenAdminState$, operational state: $vRtrLdpNgGenIPv4OperState$, reason: $vRtrLdpNgGenIPv4OperDownReason$
Cause	The vRtrLdpNgIpv4InstStateChange is generated when the IPv4 LDP instance changes state operationally as specified by vRtrLdpNgGenIPv4OperState.
Effect	Based on the vRtrLdpNgGenIPv4OperDownReason reason code, the system may not be able to accept new requests from peers.
Recovery	Based on the vRtrLdpNgGenIPv4OperDownReason reason code, appropriate configuration changes in LDP may be required.

vRtrLdpNgIpv6InstStateChange

Table 6. vRtrLdpNgIpv6InstStateChange properties
Property name	Value
Application name	LDP
Event ID	2012
Event name	vRtrLdpNgIpv6InstStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.2
Default severity	minor
Message format string	IPv6 Instance state changed - vRtrID: $vRtrID$, administrative state: $vRtrLdpNgGenAdminState$, operational state: $vRtrLdpNgGenIPv6OperState$, reason: $vRtrLdpNgGenIPv6OperDownReason$
Cause	The vRtrLdpNgIpv6InstStateChange is generated when the IPv6 LDP instance changes state operationally as specified by vRtrLdpNgGenIPv6OperState.
Effect	Based on the vRtrLdpNgGenIPv6OperDownReason reason code, the system may not be able to accept new requests from peers.
Recovery	Based on the vRtrLdpNgGenIPv6OperDownReason reason code, appropriate configuration changes in LDP may be required.

vRtrLdpNgResourceExhaustion

Table 7. vRtrLdpNgResourceExhaustion properties
Property name	Value
Application name	LDP
Event ID	2019
Event name	vRtrLdpNgResourceExhaustion
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.9
Default severity	minor
Message format string	Instance resource exhausted - vRtrID: $vRtrID$
Cause	The vRtrLdpNgResourceExhaustion notification is generated when a CPM or data path resource required for FEC resolution is exhausted. The new notification will not be generated if multiple internal event changes occur within a 10 minute interval.
Effect	The system may not be able to accept new requests from peers.
Recovery	Appropriate configuration changes in LDP may be required.

vRtrLdpNgSessionStateChange

Table 8. vRtrLdpNgSessionStateChange properties
Property name	Value
Application name	LDP
Event ID	2016
Event name	vRtrLdpNgSessionStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.6
Default severity	minor
Message format string	Session state is $vRtrLdpNgSessState$. Overload Notification message is $vRtrLdpNgSessOverloadDirection$ to/from peer $vRtrLdpNgPeerLdpId$ with overload state $vRtrLdpNgSessOverloadState$ for fec type $vRtrLdpNgSessOverloadFecType$ and sub type fec $vRtrLdpNgSessOvldFecTypeSubTyp$
Cause	The vRtrLdpNgSessionStateChange notification is generated when the LDP Overload Notification message is sent to or received from the peer vRtrLdpNgPeerLdpId for the combination of vRtrLdpNgSessOverloadFecType and vRtrLdpNgSessOvldFecTypeSubTyp while vRtrLdpNgSessState remains 'operational'.
Effect	Once the Local LSR has sent the LDP Overload Notification message to the peer vRtrLdpNgPeerLdpId for fec and sub type fec indicated by vRtrLdpNgSessOverloadFecType and vRtrLdpNgSessOvldFecTypeSubTyp and vRtrLdpNgSessOverloadState has the value of 'true', then new Label Mapping Messages received for this peer for the given combination of fec and sub type fec is returned with a Label Release Message. If the Local LSR has received an LDP Overload Notification message from the peer vRtrLdpNgPeerLdpId for fec and sub type fec indicated by vRtrLdpNgSessOverloadFecType and vRtrLdpNgSessOvldFecTypeSubTyp and vRtrLdpNgSessOverloadState has the value of 'true', no new Label Mapping Message for the given combination of fec and sub type fec will be sent to this peer. If the Local LSR has received an LDP Overload Notification message from the peer vRtrLdpNgPeerLdpId for fec and sub type fec indicated by vRtrLdpNgSessOverloadFecType and vRtrLdpNgSessOvldFecTypeSubTyp and vRtrLdpNgSessOverloadState has the value of 'false', then the Local LSR will send all pending and any new Label Mapping Message for the given combination of fec and sub type fec to this peer.
Recovery	In case the Local LSR sent the LDP Overload Notification message to the peer vRtrLdpNgPeerLdpId and vRtrLdpNgSessOverloadState has the value of 'true' for fec and sub type fec indicated by vRtrLdpNgSessOverloadFecType and vRtrLdpNgSessOvldFecTypeSubTyp, then appropriate LDP configuration changes may be required on the Local and/or Remote LSR. Once the Local LSR is not overloaded anymore, an LDP Overload Notification message is sent to the peer vRtrLdpNgPeerLdpId and vRtrLdpNgSessOverloadState has the value of 'false' for given fec and sub type fec.

vRtrLdpNgSessMaxFecLimitReached

Table 9. vRtrLdpNgSessMaxFecLimitReached properties
Property name	Value
Application name	LDP
Event ID	2018
Event name	vRtrLdpNgSessMaxFecLimitReached
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.8
Default severity	major
Message format string	Number of FECs received from the peer $vRtrLdpNgPeerAddress$ has reached the maximum value of $vRtrLdpNgSessParamMaxFec$. The current operational threshold is $vRtrLdpNgSessOperMaxFecThreshold$ percent.
Cause	A vRtrLdpNgSessMaxFecLimitReached notification is generated when the number of FEC's accepted from the peer has reached the value specified by vRtrLdpNgSessParamMaxFec. If the current number of FEC's 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 vRtrLdpNgSessMaxFecLimitReached trap was sent. If any parameter in FEC limit configuration changes and the current number of FEC's are equal to or higher than the limit specified by vRtrLdpPeerMaxFec, then we would always raise the vRtrLdpNgSessMaxFecLimitReached trap.
Effect	When the number of FECs exceed the configured maximum (vRtrLdpNgSessParamMaxFec) it results in any of the following: (1) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is supported, then Overload procedure will take place. (2) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'false' and LSR Overload Capability is not supported, Label Mapping Message will be returned with Label Release Message. (3) If vRtrLdpNgSessParamMaxFecLogOnly is set to 'true', no action will be taken.
Recovery	Appropriate Configuration changes in local or peer LSR will be required.

vRtrLdpNgSessMaxFecThresChanged

Table 10. vRtrLdpNgSessMaxFecThresChanged properties
Property name	Value
Application name	LDP
Event ID	2017
Event name	vRtrLdpNgSessMaxFecThresChanged
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.7
Default severity	warning
Message format string	Number of FECs received from the peer $vRtrLdpNgPeerAddress$ has gone $vRtrLdpNgSessOperThresLevel$ the configured threshold of the maximum value $vRtrLdpNgSessParamMaxFec$. The current operational threshold is $vRtrLdpNgSessOperMaxFecThreshold$ percent.
Cause	A vRtrLdpNgSessMaxFecThresChanged notification is generated when the number of FECs accepted from the peer has exceeded or drops below vRtrLdpNgSessOperMaxFecThreshold percent of the value specified by vRtrLdpNgSessParamMaxFec. New notification will not be generated if multiple internal event change occurs for the same level indicated by vRtrLdpNgSessOperThresLevel during a 2 minute interval. If any parameter in FEC limit configuration changes then we would always raise this trap if current number of FEC's 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 (vRtrLdpNgSessParamMaxFec) resulting in the generation of vRtrLdpNgSessMaxFecLimitReached notification.
Recovery	Appropriate Configuration changes in local or peer LSR will be required.

vRtrLdpNgTargPeerStateChange

Table 11. vRtrLdpNgTargPeerStateChange properties
Property name	Value
Application name	LDP
Event ID	2015
Event name	vRtrLdpNgTargPeerStateChange
SNMP notification prefix and OID	TIMETRA-LDP-NG-MIB.tmnxLdpNgNotifications.5
Default severity	minor
Message format string	Targeted peer state changed - vRtrID: $vRtrID$, $vRtrLdpNgPeerAddress$, administrative state: $vRtrLdpNgTargPeerAdminState$, operational state: $vRtrLdpNgTargPeerOperState$
Cause	The vRtrLdpNgTargPeerStateChange notification is generated when the LDP peer changes state either administratively or operationally.
Effect	Based on the vRtrLdpNgTargPeerOperDownReason reason code, the system may not be able to accept new requests from this peer.
Recovery	Based on the vRtrLdpNgTargPeerOperDownReason reason code, appropriate configuration changes in LDP may be required.

vRtrLdpStateChange

Table 12. vRtrLdpStateChange properties
Property name	Value
Application name	LDP
Event ID	2001
Event name	vRtrLdpStateChange
SNMP notification prefix and OID	TIMETRA-LDP-MIB.tmnxLdpNotifications.1
Default severity	minor
Message format string	LDP protocol $vRtrLdpStatus$d
Cause	The vRtrLdpStateChange notification is generated when the LDP protocol is created or deleted in the router
Effect	N/A
Recovery	N/A