Supported Platforms
Configuring Chassis Redundancy for a Virtual Chassis
By default, the router uses link redundancy for aggregated Ethernet interfaces (bundles) configured with targeted traffic distribution. As an alternative to using link redundancy, you can configure chassis redundancy for an MX Series Virtual Chassis configured with targeted traffic distribution for IP demux or VLAN demux subscribers on aggregated Ethernet interfaces.
In an MX Series Virtual Chassis, chassis redundancy assigns the backup link to an MPC/MIC module in a member router other than the member router on which the primary link resides. For example, in a two-member MX Series Virtual Chassis where the primary link for the aggregated Ethernet bundle is on an MPC/MIC module in the master router, chassis redundancy assigns the backup link for the bundle to an MPC/MIC module in the backup router. Chassis redundancy provides protection if the MPC/MIC module containing the primary link fails. In this event, the subscriber connections fail over to the backup link on the MPC/MIC module in the other member router.
Unlike link redundancy and module redundancy, each of which are supported for both standalone routers and Virtual Chassis member routers, chassis redundancy is available only for member routers in an MX Series Virtual Chassis.
Before you begin:
- Configure a Virtual Chassis consisting of two MX Series routers.
- Ensure that the aggregated Ethernet bundle is configured without link protection.
To configure chassis redundancy for an MX Series Virtual Chassis:
- Log in to the console on the master router of the Virtual Chassis.
- Specify that you want to configure the demux logical interface.
- Enable targeted distribution for the interface.{master:member0-re0} [edit intefaces demux0 unit logical-unit-number]user@host# set targeted-distribution
- Specify the aggregated Ethernet bundle for which you want
to configure chassis redundancy.{master:member0-re0} [edit]user@host# edit interfaces aenumber aggregated-ether-options
- Enable module (FPC) redundancy for the specified aggregated
Ethernet bundle.{master:member0-re0} [edit interfaces aenumber aggregated-ether-options]user@host# set logical-interface-chassis-redundancy
 | Best Practice: We recommend that you do not configure both module (FPC) redundancy and chassis redundancy for the same aggregated Ethernet interface in an MX Series Virtual Chassis. If you do, module redundancy takes precedence over chassis redundancy. |
