- 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
Configuring Passive Flow Monitoring
On routing platforms containing the Monitoring Services PIC or the Monitoring Services II PIC, you can configure flow monitoring for traffic passing through the routing platform. This type of monitoring method is passive monitoring.
To configure flow monitoring, include the monitoring
statement at the [edit forwarding-options
hierarchy level:
[edit forwarding-options] monitoring group-name { family inet { output { cflowd hostname { port port-number; } export-format cflowd-version-5; flow-active-timeout seconds; flow-export-destination { cflowd-collector; } flow-inactive-timeout seconds; interface interface-name { engine-id number; engine-type number; input-interface-index number; output-interface-index number; source-address address; } } } }
To configure a passive monitoring group, include the monitoring
statement and specify a group name. To configure monitoring on a
specified address family, include the family
statement
and specify an address family. To specify an interface to monitor
incoming traffic, include the input
statement. To configure
the monitoring information that is sent out, include the output
statement. To configure the output flow aggregation, include the cflowd
statement. For more information about flow aggregation,
see Directing Traffic Sampling Output
to a Server Running the cflowd Application. To specify
the format of the monitoring information sent out, include the export-format
statement and specify a version number. To configure
the interval before exporting an active flow, include the flow-active-timeout
statement. The default value for flow-active-timeout is
1800 seconds. To enable flow collection, include the flow-export-destination
statement. To configure the interval before a flow is considered
inactive, include the flow-inactive-timeout
statement.
The default value for flow-inactive-timeout is 60 seconds.
To configure the interface that sends out the monitored information,
include the interface
statement. Flow monitoring is supported
for Monitoring Services PIC interfaces only.
When you apply a firewall filter to a loopback interface, the filter might block responses from the Monitoring Services PIC. To allow responses from the Monitoring Services PIC to pass through for monitoring purposes, configure a term in the firewall filter to include the Monitoring Services PIC’s IP address. For more detailed information about configuring firewall filters, see Guidelines for Configuring Firewall Filters and Guidelines for Applying Standard Firewall Filters.