- 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 IPv4 and IPv6 Accounting
IPv4 and
IPv6 accounting are disabled by default. But you can enable
the
accounting by including the route-accounting
statements
at the
[edit
forwarding-options family inet4]
and [edit
forwarding-options family inet6]
hierarchy level, as shown here:
[edit] forwarding-options { family inet4 { route-accounting; } ]
[edit] forwarding-options { family inet6 { route-accounting; } ]
To view the IPv4 or
IPv6 statistics for a given physical or logical interface, run the
operational command
show
interfaces extensive interface | find IPv4
or
show interfaces extensive interface |
find IPv6
. Note that the output displays packet and byte counts for transit
traffic only. Locally generated packets are not included in the metrics.
show interfaces ge-2/0/9 detail | find IPv6 IPv6 transit statistics: Input bytes : 8576802312 Output bytes : 8991637500 Input packets: 5787313 Output packets: 5994425
Follow the guidelines given below to configure IPv4 and IPv6 statistics accounting:
The transit rate is calculated in software and not in hardware. So, you can expect some deviation from the line rate. You do not receive the expected rate with lower fps (for example, 5 fps).
The traffic must be IPv4 or IPv6 at both ingress and egress. Any form of encapsulated traffic or traffic translating to IPv4 is not supported on PTX routers.
If the GRE tunnel is IPv4 or IPv6 based, this traffic is not accounted in ingress statistics.
Statistics accounting is supported only for
et
andae
interfaces on PTX routers.The virtual, software, pseudo, Layer 2, and special type Layer 3 virtual interfaces are not supported. For example, interfaces such as the following:
irb
rvi
lsi
fti
vtep
vt
IPv4 transit statistics is not displayed on Routine Engine show commands.
No interoperability between SCU and IPv4 statistics accounting on PTX routers.
The following functionalities are not supported:lo0 traffic
IPv4 statistics query over SNMP
Aggregated Ethernet child link IPv4 statistics accounting