ldp

Application name

ldp

Event name

ldpInterfaceDown

Default severity

warning

Message format string

In network-instance network_instance, LDP has changed oper-state to DOWN on interface subinterface. The reason is oper_down_reason

Cause

This event is generated when LDP ceases to be functional on a subinterface.

Effect

LDP drops its adjacencies and sessions with other routers reachable through this subinterface.

Application name

ldp

Event name

ldpInterfaceUp

Default severity

notice

Message format string

In network-instance network_instance, LDP is now up and functional on interface subinterface.

Cause

This event is generated when LDP becomes functional on a suinterface.

Effect

LDP can form adjacencies and sessions with other routers reachable through this subinterface.

Application name

ldp

Event name

ldpIpv4InstanceDown

Default severity

warning

Message format string

In network-instance network_instance, LDP-IPv4 has changed oper-state to DOWN. The reason is oper_down_reason

Cause

This event is generated when LDP ceases to becomes functional for IPv4 adjacencies, FECs and addresses.

Effect

LDP cannot form IPv4 adjacencies and sessions with other such routers.

Application name

ldp

Event name

ldpIpv4InstanceUp

Default severity

notice

Message format string

In network-instance network_instance, LDP-IPv4 is now up and functional.

Cause

This event is generated when LDP becomes functional for IPv4 adjacencies, FECs and addresses.

Effect

LDP can form IPv4 adjacencies and sessions with other such routers reachable through LDP interfaces that are operational.

Application name

ldp

Event name

ldpSessionDown

Default severity

warning

Message format string

In network-instance network_instance, the LDP session with peer peer_ldp_id has changed to non-existent.

Cause

This event is generated when an LDP session transitions into the non-existent state from a higher state.

Effect

LDP immediately deletes FEC-label and address bindings received from this peer.

Application name

ldp

Event name

ldpSessionFecLimitReached

Default severity

warning

Message format string

The number of FECs received from the LDP peer peer_ldp_id has reached the configured limit of fec_limit.

Cause

The number of FECs accepted from the peer has reached the configured limit. If the number of FECs go below the limit and again start to increase and hit the limit a second time, a new event is generated if 2 or more minutes have elapsed since the previous event. If the FEC limit is changed and the current number of FECs is equal to or higher than the limit then the event is generated immediately.

Effect

If the peer supports the overload capability then the session will go into overload. If the peer doesn't support the overload capability then excess FECs will trigger the sending of label release messages back to the peer.

Application name

ldp

Event name

ldpSessionLocalIPv4Overload

Default severity

warning

Message format string

The LDP session with peer peer_ldp_id has entered overload for IPv4 FECs because this router sent an overload TLV to the peer.

Cause

The local router has received too many IPv4 FECs.

Effect

The local router is requesting the peer to stop sending further IPv4 FECs.

Application name

ldp

Event name

ldpSessionPeerIPv4Overload

Default severity

warning

Message format string

The LDP session with peer peer_ldp_id has entered overload for IPv4 FECs because the peer sent an overload TLV.

Cause

The peer router has received too many IPv4 FECs.

Effect

The local router stops sending further IPv4 FECs to the peer.

Application name

ldp

Event name

ldpSessionUp

Default severity

notice

Message format string

In network-instance network_instance, an LDP session is now up and operational with peer peer_ldp_id.

Cause

This event is generated when an LDP session transitions into the operational state from a lower state.

Effect

LDP can exchange FEC-label and address bindings with this peer.