Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Creating and Applying Configuration Groups for a Virtual Chassis

For a Virtual Chassis configuration consisting of two MX Series routers or two EX9200 switches, each of which supports dual Routing Engines, you must create and apply on the primary device of the Virtual Chassis the following configuration groups, instead of using the standard re0 and re1 configuration groups:

  • member0-re0

  • member0-re1

  • member1-re0

  • member1-re1


The membern-ren naming format for configuration groups is reserved for exclusive use by member routers or switches in EX9200 or MX Series Virtual Chassis configurations.

Using configuration group names of the form membern-ren in an existing non-Virtual Chassis configuration or configuration script could interfere with Virtual Chassis operation. This misconfiguration could cause the router or switch to assign no IP address or an incorrect IP address to the fxp0 management Ethernet interface, and could result in a display of the Amnesiac prompt during login.

To create and apply configuration group information from the router or switch to be configured as the primary of the Virtual Chassis:

  1. In the console window on the primary router or switch (member 0 in this procedure), create and apply the member0-re0 configuration group.
  2. Delete the standard re0 configuration group from the global configuration on member 0.
  3. Create and apply the member0-re1 configuration group.
  4. Delete the standard re1 configuration group from the global configuration on member 0.
  5. Create and apply the member1-re0 configuration information.

    The commands in Steps 5 and 6 set the IP address for the fxp0 management interface and add an IP route for it in the event that routing becomes inactive.

  6. Create and apply the member1-re1 configuration information.
  7. Commit the configuration.
    Best Practice:

    We recommend that you use the commit synchronize command to save any configuration changes to the Virtual Chassis.

    For an EX9200 or MX Series Virtual Chassis, the force option is the default and only behavior when you issue the commit synchronize command. Issuing the commit synchronize command for a Virtual Chassis configuration has the same effect as issuing the commit synchronize force command.