Tracking Graceful Restart Events - Juniper EX9200 Features Manual

High Availability Feature Guide for EX9200 Switches

Tracking Graceful Restart Events

Release History Table
Related
Documentation
82
pim {
graceful-restart {
disable;
restart-duration seconds;
}
}
}
routing-options {
graceful-restart;
}
To disable PIM sparse mode graceful restart capability, include the
at the
[edit protocols pim graceful-restart]
NOTE: Multicast forwarding can be interrupted in two ways. First, if the
underlying routing protocol is unstable, multicast reverse-path-forwarding
(RPF) checks can fail and cause an interruption. Second, because the
forwarding table is not updated during the graceful restart period, new
multicast streams are not forwarded until graceful restart is complete.
To track the progress of a graceful restart event, you can configure graceful restart trace
options flags for IS-IS and OSPF/OSPFv3. To configure graceful restart trace options,
include the
graceful-restart
hierarchy level:
[edit protocols]
isis {
traceoptions {
flag graceful-restart;
}
}
(ospf | ospf3) {
traceoptions {
flag graceful-restart;
}
}
Release Description
12.3 Starting with Junos OS Release 12.3, if adjacencies between the Routing Engine
and the neighboring peer 'helper' routers time out, graceful restart protocol
extensions are unable to notify the peer 'helper' routers about the impending
restart.
Graceful Restart Concepts on page 65
Graceful Restart System Requirements on page 73
Graceful Restart and Routing Protocols on page 66
hierarchy level.
statement at the
[edit protocols protocol traceoptions flag]
disable statement
Copyright © 2017, Juniper Networks, Inc.