Tracing Nonstop Active Routing Synchronization Events - Juniper JUNOS OS 10.4 - FOR EX REV 1 Manual

Related
Documentation

Tracing Nonstop Active Routing Synchronization Events

Copyright © 2010, Juniper Networks, Inc.
NOTE: There is no requirement to start the two Routing Engines
simultaneously. If the backup Routing Engine is not up when you
synchronize , the candidate configuration is committed in the master Routing
Engine and when the backup Routing Engine is inserted or comes online, its
configuration is automatically synchronized with that of the master.
BEST PRACTICE: After a graceful Routing Engine switchover, we recommend
that you issue the
reset the cumulative values for local statistics on the new master Routing
Engine.
To disable nonstop active routing:
[edit routing-options]
user@switch# delete nonstop-routing
Example: Configuring Nonstop Active Routing on EX Series Switches on page 1183
Tracing Nonstop Active Routing Synchronization Events on page 1191
Understanding Nonstop Active Routing on EX Series Switches on page 1175
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
hierarchy level and optionally specify one or more of the
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 {
Chapter 52: Configuring High Availability
clear interface statistics (interface-name | all)
[edit protocols protocol-name traceoptions flag]
commit
command to
, , , and
detail disable receive send
1191