- 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
Inline Flow Monitoring for Virtual Chassis Overview
Inline flow monitoring enables you to monitor the flow of traffic by means of a router or switch participating in a network.
Inline flow monitoring for an MX Series Virtual Chassis or an EX9200 Virtual Chassis supports the following features:
Active sampling and exporting of both IPv4 and IPv6 traffic flows. Active (inline) sampling occurs on an inline data path without the need for a services DPC.
Sampling traffic flows in both the ingress and egress directions.
Configuring flow collection on either IPv4 or IPv6 devices.
Using the IPFIX flow collection template for traffic sampling. The IPFIX template supports both IPv4 and IPv6 export records.
Sampling and exporting of VPLS flows
Exporting of data in Version-IPFIX and Version 9 formats
Consider the following guidelines when you configure Virtual Chassis for inline flow monitoring.
Syntax of the sampling-instance Statement
To associate a sampling instance with an FPC in the Virtual
Chassis primary router (member ID 0), use the sampling-instance instance-name statement at the [edit chassis
member member-number fpc slot slot-number] hierarchy level, where member-number is 0 (zero) and slot-number is a number in the range 0 through 11. For example, the following
statement associates a sampling instance named sample1 to the FPC
in slot 1 of a Virtual Chassis primary router:
[edit chassis member 0 fpc slot 1]user@host# set sampling-instance sample1
To associate a sampling instance with an FPC in the Virtual
Chassis backup router (member ID 1), use the sampling-instance instance-name statement at the [edit chassis
member member-number fpc slot slot-number] hierarchy level, where member-number is 1 and slot-number is a
number in the range 0 through 11. For example, the following statement
associates a sampling instance named sample2 to the FPC in slot 2
of Virtual Chassis backup router:
[edit chassis member 1 fpc slot 2]user@host# set sampling-instance sample2
FPC Slot Numbers for the Virtual Chassis
After you configure the member ID and, optionally, slot count for each router that you want to add to the Virtual Chassis, the Routing Engines in that chassis reboot and the slots for line cards (FPCs) are renumbered. The FPC slot numbering used for each member router is based on the slot count and offsets used in the Virtual Chassis instead of the physical slot numbers where the line card is actually installed.
For example, assume that in your Virtual Chassis configuration,
member 0 is an MX960 router and member 1 is an MX2010 router,
with the default slot count (12) in effect on both routers. In this
topology, a 10-Gigabit Ethernet interface that appears as xe-14/2/2
(FPC slot 14, PIC slot 2, port 2) in the show services accounting
status inline-jflow command output or the show interfaces command output is actually physical interface xe-2/2/2 (FPC slot
2, PIC slot 2, port 2) on member 1 after deducting the offset
of 12 for member 1.
Platform support and associated slots depend on the Junos OS release in your installation.
For more information about how slot count and slot numbering work in an MX Series Virtual Chassis, see Virtual Chassis Components Overview.
