Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Enabling Graceful Routing Engine Switchover and Nonstop Active Routing for a Virtual Chassis

Before you configure member IDs and Virtual Chassis ports, you must enable graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) on both member routers in the Virtual Chassis.

To enable graceful Routing Engine switchover and nonstop active routing:

  1. Enable graceful Routing Engine switchover and nonstop active routing on member 0 (gladius):
    1. Log in to the console on member 0.
    2. Enable graceful switchover.
      [edit chassis redundancy]user@gladius# set graceful-switchover
    3. Enable nonstop active routing.
      [edit routing-options]user@gladius# set nonstop-routing
    4. Commit the configuration on member 0.
      [edit system]user@gladius# commit synchronize
  2. Enable graceful Routing Engine switchover and nonstop active routing on member 1 (trefoil):
    1. Log in to the console on member 1.
    2. Enable graceful switchover.
      [edit chassis redundancy]user@trefoil# set graceful-switchover
    3. Enable nonstop active routing.
      [edit routing-options]user@trefoil# set nonstop-routing
    4. Commit the configuration on member 1.
      [edit system]user@trefoil# commit synchronize

    Note: When you configure nonstop active routing, you must include the commit synchronize statement at the [edit system] hierarchy level. Otherwise, the commit operation fails.

    For an MX Series Virtual Chassis, the force option is the default and only behavior when you use the commit synchronize statement. Including the commit synchronize statement for an MX Series Virtual Chassis configuration has the same effect as including the commit synchronize force statement.

Published: 2013-02-11