Technical Documentation

Tracing Nonstop Active Routing Synchronization Events

To track the progress of nonstop active routing synchronization between Routing Engines, you can configure nonstop active routing trace options flags for each supported protocol and for BFD sessions and record these operations to a log file.

To configure nonstop active routing trace options for supported routing protocols, include the nsr-synchronization statement at the [edit protocols protocol-name traceoptions flag] hierarchy level and optionally specify one or more of the detail, disable, receive, and send options:

[edit protocols]bgp {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}isis {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}ldp {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}mpls {traceoptions {flag nsr-synchronization;flag nsr-synchronization-detail;}}(ospf | ospf3) {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}(rip | ripng) {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}pim {traceoptions {flag nsr-synchronization <detail> <disable> <receive> <send>;}}

To configure nonstop active routing trace options for BFD sessions, include the nsr-synchronization and nsr-packet statements at the [edit protocols bfd traceoptions flag] hierarchy level.

[edit protocols]bfd {traceoptions {flag nsr-synchronization;flag nsr-packet;}}

To trace the Layer 2 VPN signaling state replicated from routes advertised by BGP, include the nsr-synchronization statement at the [edit routing-options traceoptions flag] hierarchy level. This flag also traces the label and logical interface association that VPLS receives from the kernel replication state.

[edit routing-options]traceoptions {flag nsr-synchronization;}

Published: 2010-04-28