Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


Configuring Preprovisioned Member Information for a Virtual Chassis

To configure a Virtual Chassis for MX Series routers, you must create a preprovisioned configuration on the primary router by including the virtual-chassis stanza at the [edit virtual-chassis] hierarchy level. The preprovisioned configuration specifies the chassis serial number, member ID, and role for both member routers in the Virtual Chassis.

When a new member router joins the Virtual Chassis, the software compares its serial number against the values specified in the preprovisioned configuration. If the serial number of a joining router does not match any of the configured serial numbers, the software prevents that router from becoming a member of the Virtual Chassis.

To configure the preprovisioned member information for an MX Series Virtual Chassis:

  1. Specify that you want to create a preprovisioned Virtual Chassis configuration.
  2. Configure the member ID (0 or 1), role (routing-engine), and chassis serial number for each member router in the Virtual Chassis.

    In a two-member MX Series Virtual Chassis configuration, you must assign the routing-engine role to each router. The routing-engine role enables the router to function either as the primary router or backup router of the Virtual Chassis.

  3. (Optional) Enable locality bias in the Virtual Chassis configuration.
    Best Practice:

    Starting in Junos OS Release 14.1, you can enable locality bias in the Virtual Chassis configuration. Locality bias can cause traffic loss and oversubscription on egress interfaces if you configure it in a network that is not designed to handle locality biasing. Make sure you understand the utilization requirements, such as total and available bandwidth, for the local links in your network before changing the locality bias configuration.

  4. (Optional) Enable tracing of Virtual Chassis operations.

    For example:

  5. 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 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 an MX Series Virtual Chassis configuration has the same effect as issuing the commit synchronize force command.

The following example shows an MX Series Virtual Chassis preprovisioned configuration for two member routers.

Release History Table
Starting in Junos OS Release 14.1, you can enable locality bias in the Virtual Chassis configuration.