close
keyboard_arrow_left
Table of Contents
- play_arrow Overview
- play_arrow Collecting Traffic Samples for Network Monitoring
- Traffic Sampling Configuration
- Minimum Traffic Sampling Configuration
- Configuring Traffic Sampling
- Disabling Traffic Sampling
- Collecting Traffic Sampling Output in a File
- Directing Traffic Sampling Output to a Server Running the cflowd Application
- Collecting Traffic Sampling Output in the Cisco Systems NetFlow Services Export Version 9 Format
- Example: Sampling a Single SONET/SDH Interface
- Example: Sampling All Traffic from a Single IP Address
- Example: Sampling All FTP Traffic
- Tracing Traffic-Sampling Operations
- play_arrow Configuring Traffic Forwarding for Network Monitoring
- Configuring Traffic Forwarding and Monitoring
- Configuring IPv4 and IPv6 Accounting
- Configuring Discard Accounting
- Configuring Active Flow Monitoring on PTX Series Packet Transport Routers
- Configuring Passive Flow Monitoring
- Configuring Port Mirroring
- Example: Configuring Local Port Mirroring on PTX Routers
- Example: Configuring Remote Port Mirroring on PTX Routers
- Configuring Next-Hop Groups to Use Multiple Interfaces to Forward Packets Used in Port Mirroring
- Defining a Port-Mirroring Firewall Filter
- Defining a Next-Hop Group on MX Series Routers for Port Mirroring
- play_arrow Configuring Forwarding Table Filters to Efficiently Route Traffic
- play_arrow Configuring Other Forwarding Options
- Configuring Routers, Switches, and Interfaces as DHCP and BOOTP Relay Agents
- Configuring DNS and TFTP Packet Forwarding
- Configuring Port-based LAN Broadcast Packet Forwarding
- Preventing DHCP Spoofing on MX Series 5G Universal Routing Platforms
- Understanding the Hyper Mode Feature on Enhanced MPCs for MX Series Routers and EX9200 Switches
- Configuring Hyper Mode on Enhanced MPCs to Speed Up Packet Processing
- Unsupported Features and CLI Commands When Hyper Mode Is Enabled
- play_arrow Configuration Statements and Operational Commands
list Table of Contents
Per-Flow and Per-Prefix Load Balancing Overview
date_range
24-Nov-23
By default, when there are multiple equal-cost paths to the same destination, Junos OS chooses one of the next-hop addresses at random.
On all M Series Multiservice Edge Routers, MX Series 5G Universal Routing Platforms, and T Series Core Routers, you have the additional option of configuring per-prefix load balancing based on a specified hash value that enables the router to elect a next hop independently of the route chosen by other routers.
On the M120, M320, and MX Series routers only, you have the additional option of enabling per-flow load balancing based on a unique, load-balance hash value for each Packet Forwarding Engine slot.
