- 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 Forwarding Table Filters to Efficiently Route Traffic
- play_arrow Configuring Forwarding Options for Load Balancing Traffic
- Configuring Load Balancing for Ethernet Pseudowires
- Configuring Load-Balance Groups
- Understanding the Algorithm Used to Load Balance Traffic on MX Series Routers
- Understanding Per-Packet Load Balancing
- Configuring Per-Packet Load Balancing
- Configuring Per-Flow Load Balancing
- Understanding Load Balancing for BGP Traffic with Unequal Bandwidth Allocated to the Paths
- Understanding the Default BGP Routing Policy on Packet Transport Routers (PTX Series)
- ECMP Flow-Based Forwarding on ACX Series Routers
- Per-Flow and Per-Prefix Load Balancing Overview
- Configuring Per-Prefix Load Balancing
- Configuring Per-Flow Load Balancing Based on Hash Values
- Configuring Load Balancing Based on MAC Addresses
- Load Balancing VPLS Non-Unicast Traffic Across Member Links of an Aggregate Interface
- Example: Configuring Multicast Load Balancing over Aggregated Ethernet Links
- 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
Defining a Next-Hop Group on MX Series Routers for Port Mirroring
Starting with release 14.2, on routers containing an Internet Processor II application-specific integrated circuit (ASIC) or T Series Internet Processor, you can send a copy of an IP version 4 (IPv4) or IP version 6 (IPv6) packet from the router to an external host address or a packet analyzer for analysis. This is known as port mirroring.
Port mirroring is different from traffic sampling. In traffic sampling, a sampling key based on the IPv4 header is sent to the Routing Engine. There, the key can be placed in a file, or cflowd packets based on the key can be sent to a cflowd server. In port mirroring, the entire packet is copied and sent out through a next-hop interface.
You can configure simultaneous use of sampling and port mirroring, and set an independent sampling rate and run-length for port-mirrored packets. However, if a packet is selected for both sampling and port mirroring, only one action can be performed, and port mirroring takes precedence. For example, if you configure an interface to sample every packet input to the interface and a filter also selects the packet to be port mirrored to another interface, only the port mirroring takes effect. All other packets not matching the explicit filter port-mirroring criteria continue to be sampled when forwarded to their final destination.
Next-hop groups allow you to include port mirroring on multiple interfaces.
On MX Series routers, you can mirror tunnel interface input
traffic to multiple destinations. To this form of multipacket port
mirroring, you specify two or more destinations in a next-hop group,
define a firewall filter that references the next-hop group as the
filter action, and then apply the filter to a logical tunnel interface lt-) or virtual tunnel interfaces (vt- on the MX
Series router.
To define a next-hop group for a Layer 2 port-mirroring firewall filter action:
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.
