- 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 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
Targeted Traffic Distribution on Aggregated Ethernet Interfaces in a Virtual Chassis
By default, member routers or switches in an EX9200 or MX Series Virtual Chassis use hash-based traffic distribution for subscriber interfaces in aggregated Ethernet bundles configured without link protection. The hash-based model distributes subscriber interface traffic over multiple links in the bundle, enabling you to load balance multiple traffic flows through the logical subscriber interface.
Starting in Junos OS Release 13.2, as an alternative to using hash-based distribution in an EX9200 or MX Series Virtual Chassis, you can configure targeted traffic distribution for IP demultiplexing (demux) or VLAN demux subscriber interfaces in an aggregated Ethernet bundle that is configured without link protection.
Targeted Distribution in a Virtual Chassis
Targeted distribution enables you to configure the Virtual Chassis to send (target) all egress data traffic for a logical subscriber interface across a single member link in an aggregated Ethernet bundle, also referred to as an IEEE 802.3ad link aggregation group (LAG) bundle. You configure targeted distribution for a demux subscriber interface on the Virtual Chassis primary router or switch.
With targeted distribution, the router or switch in a Virtual Chassis assigns the primary member link and backup member link for the aggregated Ethernet bundle across all Virtual Chassis port links that belong to the aggregated Ethernet bundle. To accomplish load balancing, the router or switch evenly distributes the demux subscriber interfaces over these member links.
Benefits of Targeted Distribution
Targeted distribution is especially useful in a Virtual Chassis configuration in which subscriber traffic enters through a Virtual Chassis port on one member router or switch and exits through a Virtual Chassis port on a different member router or switch. By combining Virtual Chassis ports from different member router or switches as member links of the aggregated Ethernet bundle, targeted distribution provides increased redundancy in the event of a chassis or link failure.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.
