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

Nonstop Active Routing Protocol and Feature Support

Table 11 lists the protocols that are supported by nonstop active routing.

Table 11: Nonstop Active Routing Protocol and Feature Support

Protocol	Software Release
Bidirectional forwarding detection (BFD) For more information about BFD support, see Nonstop Active Routing BFD Support.	JUNOS software release 8.5 or later
Border Gateway Protocol (BGP)	JUNOS software release 8.4 or later
Intermediate System-to-Intermediate System (IS-IS)	JUNOS software release 8.4 or later
Label Distribution Protocol (LDP)	JUNOS software release 8.4 or later
LDP-based virtual private LAN service (VPLS)	JUNOS software release 9.3 or later
Layer 2 circuits	JUNOS software release 9.2 or later
Layer 2 virtual private networks (VPNs)	JUNOS software release 9.1 or later
Layer 3 VPNs (see the first “Note:” after this table for restrictions)	JUNOS software release 9.2 or later
Open Shortest Path First (OSPF)/OSPFv3	JUNOS software release 8.4 or later
Protocol Independent Multicast (PIM) (for IPv4) For more information about nonstop active routing support for PIM, see Nonstop Active Routing PIM Support.	JUNOS software release 9.3 or later
Routing Information Protocol (RIP) and RIP next generation (RIPng)	JUNOS software release 9.0 or later
Virtual private LAN service (VPLS)	JUNOS software release 9.1 or later

Note: Layer 3 VPN support does not include RSVP-based tunnels, dynamic GRE tunnels, multicast VPNs, or BGP flow routes. The following OSPF features and configuration statements are also not supported:

domain-id domain-id statement at the [edit routing-instances routing-instance-name protocols (ospf | ospf3)] hierarchy level
domain-vpn-tag number statement at the [edit routing-instances routing-instance-name protocols (ospf | ospf3)] hierarchy level
metric number statement at the [edit routing-instances routing-instance-name protocols ospf area area-id sham-link-remote] hierarchy level
sham-link local address statement at the [edit routing-instances routing-instance-name protocols ospf] hierarchy levels
sham-link-remote address <metric number> statement at the [edit routing-instances routing-instance-name protocols ospf area area-id] hierarchy level

Note: If you configure a protocol that is not supported by nonstop active routing, the protocol operates as usual. When a switchover occurs, the state information for the unsupported protocol is not preserved and must be refreshed using the normal recovery mechanisms inherent in the protocol.

Note: Nonstop active routing is not supported on logical systems.

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