Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Configuring Nonstop Active Routing on Switches

Requirements

• An EX Series with multiple Routing Engines or on an EX Series or a QFX series switch in a Virtual Chassis or Virtual Chassis Fabric configuration
• Junos OS Release 10.4 or later for EX Series switches
• Junos OS Release 13.2X51-D20 or later for QFX Series switches

Overview and Topology

Configure nonstop active routing on any EX Series with multiple Routing Engines or on an EX Series or a QFX series switch in a Virtual Chassis or Virtual Chassis Fabric configuration. Nonstop active routing is advantageous in networks where neighbor routing devices do not support graceful restart protocol extensions.

The topology used in this example consists of an EX8200 switch with redundant Routing Engines connected to neighbor routing devices that are not configured to support graceful restart of protocols.

Configuration

CLI Quick Configuration

To quickly configure nonstop active routing, copy the following commands and paste them into the switch terminal window:

Step-by-Step Procedure

1. Enable graceful Routing Engine switchover (GRES):
   [edit chassis redundancy]
user@switch# set graceful-switchover
2. Enable nonstop active routing (by default, nonstop active routing is disabled):
   [edit routing-options]
user@switch# set nonstop-routing
3. Synchronize configuration changes between the Routing Engines:
   [edit system]
user@switch# set commit synchronize

   If you try to commit the nonstop active routing configuration without including the commit synchronize statement, the commit fails.

   Note: If the backup Routing Engine is down when you issue the commit, a warning is displayed and the candidate configuration is committed in the master Routing Engine. When the backup Routing Engine comes up, its configuration is automatically synchronized with that of the master. If you subsequently insert or bring up a backup Routing Engine, it automatically synchronizes its configuration with the master Routing Engine configuration.

Results

Check the results of the configuration:

Verification

To confirm that the configuration is working properly, perform these tasks:

• Verifying That Nonstop Active Routing Is Working Correctly on the Switch

Verifying That Nonstop Active Routing Is Working Correctly on the Switch

Purpose

Verify that nonstop active routing is enabled.

Action

Stateful Replication: Enabled
RE mode: Master

 Protocol                Synchronization Status
 OSPF                    Complete
 RIP                     Complete
 PIM                     Complete
 RSVP                    Complete 

Meaning

This output shows that nonstop active routing (Stateful Replication) is enabled on master routing engine. If nonstop routing is not enabled, instead of the output shown above:

• On the backup routing engine the following error message is displayed: “error: the routing subsystem is not running.”
• On the master routing engine, the following output is displayed if nonstop routing is not enabled:

  Stateful Replication: Disabled
  RE mode: Master

Troubleshooting

To troubleshoot nonstop active routing, perform these tasks:

• Investigating Problems with Synchronization of Routing Engines When NSR Is Enabled

Investigating Problems with Synchronization of Routing Engines When NSR Is Enabled

Problem

A protocol loses connectivity with neighbors after a graceful Routing Engine switchover (GRES) occurs with nonstop active routing (NSR) enabled.

Solution

Use trace options to help isolate the problem and gather troubleshooting information. Using the information gathered from trace options, you can confirm or eliminate the synchronization of the Routing Engines as the cause of the loss of connectivity for the protocol. See Tracing Nonstop Active Routing Synchronization Events.