Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring Junos OS for the First Time on a Device with Dual Routing Engines

If a device has dual Routing Engines, you can create configuration groups and use the same configuration for both Routing Engines. This ensures that the configuration will not change during a failover scenario because of the identical configuration shared between the Routing Engines.

Configure the hostnames and addresses of the two Routing Engines using configuration groups at the [edit groups] hierarchy level. Use the reserved configuration group re0 for the Routing Engine in slot 0 and re1 for the Routing Engine in slot 1 to define Routing Engine-specific parameters. Configuring re0 and re1 groups enables both Routing Engines to use the same configuration file.

Use the apply-groups statement to apply the apply the configuration to the device.

The commit synchronize command commits the same configuration on both Routing Engines. The command makes the active or applied configuration the same for both Routing Engines with the exception of the groups, re0 being applied to only RE0 and re1 being applied only to RE1. If you do not synchronize the configurations between two Routing Engines and one of them fails, the router may not forward traffic correctly, because the backup Routing Engine may have a different configuration.

To initially configure a device with dual Routing Engines that have no base configuration, follow these steps:

  1. If you have not already done so, refer Configuring Junos OS for the First Time on a Device with a Single Routing Engine and follow the steps to initially configure the backup Routing Engine.
  2. Create the configuration group re0. The re0 group is a special group designator that is only used by RE0 in a redundant routing platform.
  3. Navigate to the groups re0 level of the configuration hierarchy.
  4. Specify the device hostname.
    Note:

    The hostname specified in the device configuration is not used by the DNS server to resolve to the correct IP address. This hostname is used to display the name of the Routing Engine in the CLI. For example, the hostname appears at the command-line prompt when you are logged in to the CLI:

    Note:

    Before you begin the next step, see Supported Routing Engines by Router to find the management Ethernet interface that you should use to perform this configuration.

  5. Configure the IP address and prefix length for the device management Ethernet interface. The management Ethernet interface provides a separate out-of-band management network for the device.

    • For devices using the management Ethernet interface fxp0:

    • For devices that use the management Ethernet interface em0:

  6. Set the loopback interface address for the re0 configuration group:
  7. Return to the top level of the hierarchy.

    The next steps repeat for re1 the same steps as were done for the re0 configuration group.

  8. Create the configuration group re1.
  9. Navigate to the groups re1 level of the configuration hierarchy.
  10. Specify the device hostname.
    Note:

    Before you begin the next step, see Supported Routing Engines by Router to find the management Ethernet interface that you should use to perform this configuration.

  11. Configure the IP address and prefix length for the device management Ethernet interface.

    • For devices that use the management Ethernet interface fxp0:

    • For devices that use the management Ethernet interface em0:

  12. Set the loopback interface address for re1 configuration group:
  13. Once both configuration groups have been set up, return to the top level of the hierarchy.
  14. Use the apply-groups statement to apply the configuration to the device.
  15. Configure Routing Engine redundancy:
  16. Save the configuration change on both Routing Engines:

After the configuration changes are saved, complete the management console configuration.

  1. Set the root password by choosing one of the following:

    • To enter a clear-text password, use the following command:

    • To enter a password that is already encrypted, use the following command:

    • To enter an SSH public key, use the following command:

  2. Configure the IP address of the DNS server.

  3. Configure the router domain name:

  4. Configure the IP address of a backup or default network device. A backup device is used only while the routing protocol process is not running. Choose a backup device that is directly connected to the local device by way of the management interface. The device uses this backup only when it is booting and or when the Junos routing software (the routing protocol process, rpd) is not running. For more information, see Configuring a Backup Router.

    For devices with two Routing Engines, the backup Routing Engine, RE1, uses the backup as a default gateway after the device boots. This enables you to access the backup Routing Engine. (RE0 is the default primary Routing Engine.)

    Note:

    The backup router Routing Engine does not support more than 16 backup destinations. If you configure more than 16 destinations on the backup Routing Engine, the Junos OS ignores any destination addresses after the sixteenth address and displays a commit-time warning message to this effect.

  5. Optionally, display the configuration statements:

    On devices that use management Ethernet interface em0, you will see em0 in place of fxp0 in the show command output.

  6. After you are satisfied that the configuration is successfully running, issue the request system snapshot command to back up the new configuration on both primary and backup Routing Engines.

    The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the device’s CompactFlash card, and the /altroot and /altconfig file systems are on the device’s hard drive.

    Note:

    After you issue the request system snapshot command, you cannot return to the previous configuration, because the running copy and backup copy are identical.

For information about creating configuration groups, see Junos OS CLI User Guide.

For information about configuring high availability features for redundant Routing Engine systems and the re0 group, see Junos OS High Availability User Guide.

Related Documentation