Graceful Routing Engine Switchover System Requirements

Graceful Routing Engine Switchover Platform Support

To enable graceful Routing Engine switchover, your system must meet these minimum requirements:

• MX960 router—Junos OS Release 8.3 or later

• MX480 router—Junos OS Release 8.4 or later (8.4R2 recommended)

• MX240 router—Junos OS Release 9.0 or later

• PTX5000 router—Junos OS Release 12.1X48 or later

• EX Series switches with dual Routing Engines or in a Virtual Chassis — Junos OS Release 9.2 or later for EX Series switches

• QFX Series switches in a Virtual Chassis —Junos OS Release 13.2 or later for the QFX Series

• EX Series or QFX Series switches in a Virtual Chassis Fabric —Junos OS Release 13.2X51-D20 or later for the EX Series and QFX Series switches

For more information about support for graceful Routing Engine switchover, see the sections that follow.

Graceful Routing Engine Switchover Feature Support

Graceful Routing Engine switchover supports most Junos OS features in Release 5.7 and later. Particular Junos OS features require specific versions of Junos OS. See Table 1.

The following constraints apply to graceful Routing Engine switchover feature support:

• When graceful Routing Engine switchover and aggregated Ethernet interfaces are configured in the same system, the aggregated Ethernet interfaces must not be configured for fast-polling LACP. When fast polling is configured, the LACP polls time out at the remote end during the Routing Engine primary-role switchover. When LACP polling times out, the aggregated link and interface are disabled. The Routing Engine primary role change is fast enough that standard and slow LACP polling do not time out during the procedure.

  Note:

  MACSec sessions will flap upon Graceful Routing Engine switchover.

  Starting with Junos OS Release 13.2, when a graceful Routing Engine switchover occurs, the VRRP state does not change. VRRP is supported by graceful Routing Engine switchover only in the case that PPM delegation is enabled (which the default).

Graceful Routing Engine Switchover and Subscriber Access

Graceful Routing Engine switchover currently supports most of the features directly associated with dynamic DHCP and dynamic PPPoE subscriber access. Graceful Routing Engine switchover also supports the unified in-service software upgrade (ISSU) for the DHCP access model and the PPPoE access model used by subscriber access.

Graceful Routing Engine Switchover PIC Support

Graceful Routing Engine switchover is supported on most PICs, except for the services PICs listed in this section. The PIC must be on a supported routing platform running the appropriate version of Junos OS. For information about FPC types, FPC/PIC compatibility, and the initial Junos OS Release in which an FPC supported a particular PIC, see the PIC guide for your router platform.

The following constraints apply to graceful Routing Engine switchover support for services PICs:

• You can include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level on a router with Adaptive Services, Multiservices, and Tunnel Services PICs configured on it and successfully commit the configuration. However, all services on these PICs—except the Layer 2 service packages and extension-provider and SDK applications on Multiservices PICs—are reset during a switchover.

• Graceful Routing Engine switchover is not supported on any Monitoring Services PICs or Multilink Services PICs. If you include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level on a router with either of these PIC types configured on it and issue the commit command, the commit fails.

• Graceful Routing Engine switchover is not supported on Multiservices 400 PICs configured for monitoring services applications. If you include the graceful-switchover statement, the commit fails.