In an LDP multi-instance scenario, a device can be enabled to trigger trap messages only for public LDP session, which prevents a failure to distinguish trap messages for both the private and public network sessions with the same ID.
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 trap messages 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.
The system view is displayed.
The MPLS-LDP view is displayed.
A device is enabled to generate trap messages only for public LDP sessions.
The configuration is committed.