Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
keyboard_arrow_right

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

date_range 06-Dec-23

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.

      content_copy zoom_out_map
      [edit chassis redundancy]
      user@gladius# set graceful-switchover
      
    3. Enable nonstop active routing.

      content_copy zoom_out_map
      [edit routing-options]
      user@gladius# set nonstop-routing
      
    4. Configure the commit command to automatically result in a commit synchronize action between the dual Routing Engines in member 0.

      content_copy zoom_out_map
      [edit system]
      user@gladius# set commit synchronize
      
    5. Commit the configuration.

  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.

      content_copy zoom_out_map
      [edit chassis redundancy]
      user@trefoil# set graceful-switchover
      
    3. Enable nonstop active routing.

      content_copy zoom_out_map
      [edit routing-options]
      user@trefoil# set nonstop-routing
      
    4. Configure the commit command to automatically result in a commit synchronize action between the dual Routing Engines in member 1.

      content_copy zoom_out_map
      [edit system]
      user@trefoil# set 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.

    5. Commit the configuration.

    Note:

    After enabling GRES, if you are using the ephemeral database, make sure to apply the allow-commit-synchronize-with-gres statement at the [edit system configuration-database ephemeral] hierarchy level. This enables the MX Series Virtual Chassis to synchronize ephemeral configuration data when a commit synchronize operation is requested.

    Note:

    When you perform a GRES switchover while using enhanced subscriber management, the backup RE will reboot.

footer-navigation