- play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- play_arrow Understanding How a Virtual Chassis Works
- play_arrow Configuring a Virtual Chassis
- Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a Virtual Chassis
- Preparing for a Virtual Chassis Configuration
- Creating and Applying Configuration Groups for a Virtual Chassis
- Configuring Preprovisioned Member Information for a Virtual Chassis
- Configuring Enhanced IP Network Services for a Virtual Chassis
- Configuring Enhanced LAN Mode for a Virtual Chassis
- Enabling Graceful Routing Engine Switchover and Nonstop Active Routing for a Virtual Chassis
- Configuring Member IDs for a Virtual Chassis
- Configuring an MX2020 Member Router in an Existing MX Series Virtual Chassis
- Switching the Global Primary and Backup Roles in a Virtual Chassis Configuration
- Deleting Member IDs in a Virtual Chassis Configuration
- Example: Replacing a Routing Engine in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms
- Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2
- 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 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
Accessing the Virtual Chassis Through the Management Interface
The management Ethernet interface (fxp0) on an MX Series router or EX9200 switch is an out-of-band management interface, also referred to as a management port, that enables you to use Telnet or SSH to access and manage the device remotely. You typically configure the management interface with an IP address and prefix length when you first install Junos OS.
You can configure a management Ethernet interface in one of two ways to access a Virtual Chassis:
To access the Virtual Chassis as a whole, configure a consistent IP address for the management interface using the master-only option. You can use this management IP address to consistently access the primary (primary) Routing Engine in the primary router or switch (protocol primary) for the Virtual Chassis.
To access a specific Routing Engine in an individual member router or switch of the Virtual Chassis, configure an IP address for one of the following configuration groups:
member0-re0
member0-re1
member1-re0
member1-re1
For most management tasks, we recommend that you access the Virtual Chassis as a whole through a consistent management IP address. For troubleshooting purposes, however, accessing a specific Routing Engine in an individual member router or switch may be useful.
To access a Virtual Chassis through the management Ethernet interface, do one of the following:
Configure a consistent management IP address that accesses the entire Virtual Chassis through the primary Routing Engine in the Virtual Chassis primary router or switch.
content_copy zoom_out_map{master:member0-re0}[edit] user@host# set interfaces fxp0 unit 0 family inet address ip-address/prefix-length primary-onlyFor example, to access the entire Virtual Chassis via management IP address 10.4.5.33/16:
content_copy zoom_out_map{master:member0-re0}[edit] user@host# set interfaces fxp0 unit 0 family inet address 10.4.5.33/16 primary-onlyConfigure a management IP address that accesses a specified Routing Engine in an individual member router or switch in the Virtual Chassis.
content_copy zoom_out_map{master:member0-re0}[edit groups] user@host# set membern-ren interfaces fxp0 unit 0 family inet address ip-address/prefix-lengthFor example, to access the Routing Engine installed in slot 1 of member router 1 (member1-re1) in the Virtual Chassis:
content_copy zoom_out_map{master:member0-re0}[edit groups] user@host# set member1-re1 interfaces fxp0 unit 0 family inet address 10.4.3.145/32
