The session-state-trap public-only command enables a device to generate trap messages only for public LDP sessions.
The undo session-state-trap public-only command enables a device to generate trap messages for both public and private LDP sessions.
The session-state-trap remote-lfa-disable command disables a device from generating traps when LDP sessions go down due to RLFA route deletion.
The undo session-state-trap remote-lfa-disable command enables a device to generate traps when LDP sessions go down due to RLFA route deletion.
By?default,?the?device?is?enabled?to?generate?trap?messages?for?both?public?and?private?LDP?sessions.
Usage Scenario
In an LDP multi-instance scenario, multiple LDP instances contain sessions of the same ID. Since trap messages do not contain VPN instance information, these trap messages carrying the same session ID cannot be differentiated based on VPN instances. To distinguish traps for public and private sessions with the same ID in public and private instances, run the session-state-trap public-only command to enable a device to generate trap messages only for public LDP sessions.
In an RLFA FRR scenario, after an ingress uses the RLFA algorithm to calculate a PQ node, the ingress runs LDP to automatically establish a remote LDP session with the destination IP address set to the PQ node's IP address. After the corresponding RLFA route is deleted, the LDP session will go down. If you want the device to generate traps when LDP sessions go down due to RLFA route deletion, run the session-state-trap remote-lfa-disable command.<HUAWEI> system-view [~HUAWEI] mpls ldp [*HUAWEI-mpls-ldp] session-state-trap remote-lfa-disable
<HUAWEI> system-view [~HUAWEI] mpls [*HUAWEI-mpls] quit [*HUAWEI] mpls ldp [*HUAWEI-mpls-ldp] session-state-trap public-only