[Contents] [Prev] [Next] [Index] [Report an Error]

PIM and Nonstop Active Routing

Nonstop active routing configurations include two Routing Engines that share information so that routing is not interrupted during Routing Engine failover. When nonstop active routing is configured on a dual Routing Engine platform, the PIM control state is replicated on both Routing Engines.

This PIM state information includes:

Neighbor relationships
Join and prune information
RP-set information
Synchronization between routes and next hops and the forwarding state between the two Routing Engines

The PIM control state is maintained on the backup Routing Engine by the replication of state information from the master to the backup Routing Engine and having the backup Routing Engine react to route installation and modification in the [instance].inet.1 routing table on the master Routing Engine. The backup Routing Engine does not send or receive any PIM protocol packets directly. In addition, the backup Routing Engine uses the dynamic interfaces created by the master Routing Engine. These dynamic interfaces include PIM encapsulation, de-encapsulation, and multicast tunnel interfaces.

Note: The clear pim join, clear pim register, and clear pim statistics operational mode commands are not supported on the backup Routing Engine when nonstop active routing is enabled.

To enable nonstop active routing for PIM (in addition to the PIM configuration on the master Routing Engine), you must include the following statements at the [edit] hierarchy level:

chassis redundancy graceful-switchover
routing-options nonstop-routing
system commit synchronize

For more information about PIM and nonstop active routing, see IGMP and Nonstop Active Routing and the JUNOS High Availability Configuration Guide.

[Contents] [Prev] [Next] [Index] [Report an Error]