- 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 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 Configuration Statements and Operational Commands
Configuring Characteristics of the Virtual Chassis Trace Log File
You can optionally configure the following characteristics of the trace log file for a Virtual Chassis:
Maximum number of trace files—When a trace file named trace-file reaches its maximum size, it is renamed trace-file.0, then trace-file.1, and so on, until the maximum number of trace files is reached. Then the oldest trace file is overwritten. You can optionally specify the maximum number of trace files to be from 2 through 1000. If you specify a maximum number of files with the files option, you must also specify a maximum file size with the size option.
Maximum trace file size—You can configure the maximum trace file size to be from 10 KB through 1 gigabyte (GB) If you specify a maximum file size with the size option, you must also specify a maximum number of files with the files option.
Timestamp—By default, timestamp information is placed at the beginning of each line of trace output. You can optionally prevent placement of a timestamp on any trace log file.
Appending or replacing the trace file—By default, the router or switch appends new information to an existing trace file. You can optionally specify that the router or switch replace an exisiting trace file instead of appending information to it.
To configure the maximum number and maximum size of trace files:
On the router or switch to be designated as the primary of the Virtual Chassis, specify the maximum number and maximum size of the trace file.
content_copy zoom_out_map[edit virtual-chassis] user@host# set traceoptions file filename files number size maximum-file-size
For example, to set the maximum number of files to 20 and the maximum file size to 2 MB for a trace file named vccp:
content_copy zoom_out_map[edit virtual-chassis] user@host# set traceoptions file vccp files 20 size 2097152
When the vccp trace file for this example reaches 2 MB, vccp is renamed vccp.0, and a new file named vccp is created. When the new vccp file reaches 2 MB, vccp.0 is renamed vccp.1 and vccp is renamed vccp.0. This process repeats until there are 20 trace files. Then the oldest file (vccp.19) is overwritten by the newest file (vccp.0).
To prevent the router or switch from the placing a timestamp on the trace log file:
On the router or switch to be designated as the primary of the Virtual Chassis, specify that a timestamp not appear on the trace log file:
content_copy zoom_out_map[edit virtual-chassis] user@host# set traceoptions file filename no-stamp
To replace an exisiting trace file instead of appending information to it:
On the router or switch to be designated as the primary of the Virtual Chassis, specify that the router or switch replaces an existing trace file:
content_copy zoom_out_map[edit virtual-chassis] user@host# set traceoptions file filename replace
