- play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- play_arrow Understanding How a Virtual Chassis Works
- play_arrow Configuring Virtual Chassis Ports to Interconnect Member Devices
- play_arrow Configuring Locality Bias to Conserve Bandwidth on Virtual Chassis Ports
- play_arrow Configuring Class of Service for Virtual Chassis Ports
- play_arrow Configuring Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
- Configuring Module Redundancy for a Virtual Chassis
- Configuring Chassis Redundancy for a Virtual Chassis
- Multichassis Link Aggregation in a Virtual Chassis
- Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis
- Understanding Support for Targeted Distribution of Logical Interface Sets of Static VLANs over Aggregated Ethernet Logical Interfaces
- play_arrow Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
- play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Unified In-Service Software Upgrade (ISSU)
- play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Sequential Upgrade
- play_arrow Monitoring an MX Series Virtual Chassis
- Accessing the Virtual Chassis Through the Management Interface
- Verifying the Status of Virtual Chassis Member Routers or Switches
- Verifying the Operation of Virtual Chassis Ports
- Verifying Neighbor Reachability for Member Routers or Switches in a Virtual Chassis
- Verifying Neighbor Reachability for Hardware Devices in a Virtual Chassis
- Determining GRES Readiness in a Virtual Chassis Configuration
- Viewing Information in the Virtual Chassis Control Protocol Adjacency Database
- Viewing Information in the Virtual Chassis Control Protocol Link-State Database
- Viewing Information About Virtual Chassis Port Interfaces in the Virtual Chassis Control Protocol Database
- Viewing Virtual Chassis Control Protocol Routing Tables
- Viewing Virtual Chassis Control Protocol Statistics for Member Devices and Virtual Chassis Ports
- Verifying and Managing the Virtual Chassis Heartbeat Connection
- Inline Flow Monitoring for Virtual Chassis Overview
- Managing Files on Virtual Chassis Member Routers or Switches
- Virtual Chassis SNMP Traps
- Virtual Chassis Slot Number Mapping for Use with SNMP
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in the Same Subnet
- Example: Determining Member Health Using an MX Series Virtual Chassis Heartbeat Connection with Member Routers in Different Subnets
- play_arrow Tracing Virtual Chassis Operations for Troubleshooting Purposes
- Tracing Virtual Chassis Operations for MX Series 5G Universal Routing Platforms
- Configuring the Name of the Virtual Chassis Trace Log File
- Configuring Characteristics of the Virtual Chassis Trace Log File
- Configuring Access to the Virtual Chassis Trace Log File
- Using Regular Expressions to Refine the Output of the Virtual Chassis Trace Log File
- Configuring the Virtual Chassis Operations to Trace
- play_arrow Configuration Statements and Operational Commands
Switching the Global Primary and Backup Roles in a Virtual Chassis Configuration
You can change the primary role in an MX Series Virtual
Chassis by switching the global roles of the primary router and backup
router in the Virtual Chassis configuration. When you change the primary
role by issuing the request virtual-chassis routing-engine master
switch
administrative command, the current primary router in
the Virtual Chassis (also known as the Virtual Chassis protocol primary,
or VC-P) becomes the backup router, and the current backup router
(also known as the Virtual Chassis protocol backup, or VC-B) becomes
the primary router.
Before you begin:
Make sure the system configuration is synchronized between the primary router and the backup router.
If the configuration between the member routers is not synchronized when you issue the
request virtual-chassis routing-engine master switch
command, the router displays the following error message and rejects the command.content_copy zoom_out_mapError: mastership switch request NOT honored, backup not ready
Make sure the Virtual Chassis is not in a transition state (for example, the backup router is in the process of disconnecting from the Virtual Chassis) when you issue the
request virtual-chassis routing-engine master switch
command.If you attempt to issue the
request virtual-chassis routing-engine master switch
command during a transition state, the router does not process the command.
To switch the global primary and backup roles:
Issue the
request virtual-chassis routing-engine master switch
command from the Virtual Chassis primary Routing Engine in the Virtual Chassis primary router (VC-Pp):content_copy zoom_out_map{master:member0-re0} user@host> request virtual-chassis routing-engine master switch Do you want to continue ? [yes,no] (no) yes
If you attempt to issue the
request virtual-chassis routing-engine master switch
command from the backup router , the router displays the following error message and rejects the command.content_copy zoom_out_maperror: Virtual Chassis member is not the protocol master
Issuing the
request virtual-chassis routing-engine master switch
command from the VC-Pp causes the global role transitions listed in Table 1.Table 1: Virtual Chassis Global Role Transitions Before and After Primary-role Switchover Virtual Chassis Role Before Switching Primary Role
Virtual Chassis Role After Switching Primary Role
Primary Routing Engine in Virtual Chassis primary router (VC-Pp)
Standby Routing Engine in Virtual Chassis backup router (VC-Bs)
Standby Routing Engine in Virtual Chassis primary router (VC-Ps)
Primary Routing Engine in Virtual Chassis backup router (VC-Bp)
Primary Routing Engine in Virtual Chassis backup router (VC-Bp)
Primary Routing Engine in Virtual Chassis primary router (VC-Pp)
Standby Routing Engine in Virtual Chassis backup router (VC-Bs)
Standby Routing Engine in Virtual Chassis primary router (VC-Ps)