Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configuring an MX2020 Member Router in an Existing MX Series Virtual Chassis

Starting in Junos OS Release 15.1, in an existing two-member MX Series Virtual Chassis that includes an MX960 router or an MX2010 router, you can replace one or both of these routers with an MX2020 router. If you replace either the MX960 router or MX2010 router with an MX2020 router, you must follow this procedure to ensure that the new Virtual Chassis forms properly and that any configurations you use reflect the correct Flexible PIC Concentrator (FPC) slot numbering for interfaces configured on the MX2020 member router.

Before you begin:

To configure an MX2020 member router in an existing MX Series Virtual Chassis with either an MX960 router or an MX2010 router:

  1. Replace either the MX960 router or MX2010 router with an MX2020 router.

    Install the interface modules in the same physical slots in the MX2020 router as they were when installed in the MX960 or MX2010 router.

  2. Upgrade all four Routing Engines in the Virtual Chassis (two Routing Engines in each member router) to the current Junos OS software release.
    Note:

    All four Routing Engines in the Virtual Chassis must be the same model and running the same Junos OS software release. For a Virtual Chassis that includes an MX2020 router, all four Routing Engines must have at least 16 gigabytes of memory.

  3. Set the member ID and slot count of the MX960 router or MX2010 router.

    To ensure that a Virtual Chassis configuration with an MX2020 router and either an MX960 router or MX2010 router forms properly, you must set the slot-count value of the MX960 router or MX2010 router to 20 to match the slot-count of the MX2020 router.

    For example, assume that the MX960 router or MX2010 router is member 1 in the preprovisioned Virtual Chassis configuration. To set the member ID and slot count for member 1:

    The router reboots in preparation for forming the Virtual Chassis. After the reboot, the FPC slots are renumbered and all MPCs remain powered off until the Virtual Chassis port connection is configured.

  4. Edit your Junos OS configuration to rename any interfaces configured on member 1 to reflect how the FPC slots are renumbered when the Virtual Chassis includes an MX2020 member router.

    Before you add the MX2020 router to the Virtual Chassis, member 0 uses FPC slot numbers 0 through 11 with no offset, and member 1 uses slot numbers 12 through 23 with an offset of 20. After you set the slot count of the MX960 or MX2010 router to 20 and reboot the MX2020 member router, member 0 uses slot numbers 0 through 19 with no offset, and member 1 uses slot numbers 20 through 39 with an offset of 20.

    For example, in the following partial configuration, ge-0/0/0 is an aggregated Ethernet link configured on FPC slot 0 in member 0, and ge-12/0/0 is an aggregated Ethernet link configured on FPC slot 0 in member 1.

    If you replace member 1 with an MX2020 member router, FPC slot 0 in member 1 is renumbered as FPC slot 20 on member 1. As a result, you must edit the configuration to change ge-12/0/0 to ge-20/0/0, as follows:

Release History Table
Release
Description
15.1
Starting in Junos OS Release 15.1, in an existing two-member MX Series Virtual Chassis that includes an MX960 router or an MX2010 router, you can replace one or both of these routers with an MX2020 router.