IS-IS purge LSP source tracing improves the efficiency in locating the fault that triggers IS-IS LSP purge.
If network-wide IS-IS LSPs are deleted, purge LSPs are flooded, which adversely affects network stability. In this case, source tracing must be implemented to locate the root cause of the fault immediately to minimize the impact. However, IS-IS itself does not support source tracing. A conventional solution is isolation node by node until the faulty node is located, but the solution is complex and time-consuming. To address this problem, enable IS-IS purge LSP source tracing.
The following steps are optional, choose them as required.
Before configuring IS-IS purge LSP source tracing, complete the following tasks:
The system view is displayed.
To disable IS-IS purge LSP source tracing globally, run the isis purge-source-trace disable command.
The interface view is displayed.
To disable this function on an interface, run the isis purge-source-trace block command.
Return to the system view.
A UDP port number is configured for IS-IS purge LSP source tracing packets.
The IS-IS purge LSP source tracing port receives and sends IS-IS purge LSP source tracing packets, and the port is identified by a UDP port ID.
Return to the user view.
IS-IS purge LSP source tracing is reset.
If a large number of IS-IS purge LSP source tracing statistics are stored on a device, you can run the reset isis purge-source-trace command to reset the statistics. After the command is run, all IS-IS purge LSP source tracing statistics are reset, and the device needs to re-negotiate the IS-IS purge LSP source tracing capability with neighboring devices.
The configuration is committed.
Run the display isis process-id purge-source-trace analysis-report [ level-1 | level-2 ] command. The command output shows information about definitely and possibly faulty nodes identified by IS-IS purge LSP source tracing.