-
This documentation has been moved
-
Cisco IOS NetFlow Overview
-
Cisco IOS NetFlow Features Roadmap
-
Getting Started with Configuring NetFlow and NetFlow Data Export
-
Part 1: Cisco IOS NetFlow Configuration Guides
-
Configuring NetFlow and NetFlow Data Export
-
Using NetFlow Filtering or Sampling to Select the Network Traffic to Track
-
Configuring NetFlow Aggregation Caches
-
Configuring NetFlow BGP Next Hop Support for Accounting and Analysis
-
Configuring MPLS Egress NetFlow Accounting and Analysis
-
Configuring NetFlow Multicast Accounting
-
Configuring NetFlow Top Talkers using Cisco IOS CLI Commands or SNMP Commands
-
Configuring Netflow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
-
-
Table Of Contents
Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
Information About NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
NetFlow Accounting on GRE IP Tunnel Interfaces
How to Configure NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
Verifying the Status of the GRE IP Tunnel
Configuring NetFlow Accounting on a GRE IP Tunnel Interface
Configuring NetFlow Accounting on the Physical Interfaces
Configuring NetFlow Data Export Using the Version 9 Export Format
Verifying That NetFlow Data Export Is Operational
Configuration Examples for NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
Configuring a GRE IP Tunnel: Example
Configuring NetFlow Accounting on a GRE IP Tunnel: Example
Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
First Published: November 13, 2008Last Updated: November 13, 2008This document contains information about and instructions for configuring NetFlow Accounting for Unicast and Multicast on generic routing encapsulation (GRE) IP Tunnel Interfaces. NetFlow multicast accounting allows you to capture multicast-specific data (both packets and bytes) for multicast flows.
NetFlow is a Cisco IOS application that provides statistics on packets flowing through a router. It is emerging as a primary network accounting and security technology.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "Feature Information for Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces" section.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn. An account on Cisco.com is not required.
Contents
•
Information About NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
•
•
Prerequisites for Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
•
•
•
Restrictions for Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
•
•
•
•
Information About NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
•
GRE Tunneling
Generic routing encapsulation (GRE) tunneling is defined in RFC 2784. GRE is a carrier protocol that can be used with a variety of underlying transport protocols and that can carry a variety of passenger protocols. RFC 2784 also covers the use of GRE with IPv4 as the transport protocol and the passenger protocol. For more information on GRE tunnels, see the Cisco IOS Interface and Hardware Component Configuration Guide. Figure 1 is an example of a typical implementation of a GRE IP tunnel.
Figure 1 Sample Network with a GRE IPv4 Tunnel
GRE Tunnel Keepalive
Keepalive packets can be configured to be sent over IP-encapsulated GRE tunnels. You can specify the rate at which keepalives will be sent and the number of times that a device will continue to send keepalive packets without a response before the interface becomes inactive. GRE keepalive packets may be sent from both sides of a tunnel or from just one side.
Tunnel Interfaces
A tunnel interface is used to pass protocol traffic across a network that does not normally support the protocol. To build a tunnel requires defining a tunnel interface on each of two routers. The tunnel interfaces must reference each other. At each router, the tunnel interface must be configured with a Layer 3 address. The tunnel endpoints, tunnel source, and tunnel destination must be defined, and the type of tunnel must be selected. Optional steps can be performed to customize the tunnel.
Remember to configure the router at each end of the tunnel. If only one side of a tunnel is configured, the tunnel interface may still come up and stay up (unless keepalive is configured), but packets going into the tunnel will be dropped.
In Cisco IOS Release 12.2(8)T and later releases, Cisco express forwarding (CEF) switching over multipoint GRE tunnels was introduced. Previously, only process switching was available for multipoint GRE tunnels.
NetFlow Accounting on GRE IP Tunnel Interfaces
To analyze traffic that is sent from c3825 to c3745 in Figure 1, NetFlow accounting is configured as shown in Table 1. The flows in the "Flows" column are shown in Figure 2 through Figure 5.
When you configure NetFlow accounting for IPv4 unicast traffic on a GRE tunnel interface, the traffic that is encapsulated or de-encapsulated on the router results in the creation of two flows. See Figure 2 and Figure 3. When you configure NetFlow accounting for IPv4 multicast traffic on a GRE tunnel interface, the traffic that is encapsulated or de-encapsulated on the router results in the creation of three flows. See Figure 4 and Figure 5. The increase in the number of flows created results in an increase in the usage of the hardware NetFlow table. You must monitor the hardware NetFlow table on your router to ensure that it is not oversubscribed.
If you are using NetFlow data export, the number of exported flows is also increased. Flows from the hardware table are converted to the Version 9 export format and then exported. Because the number of flows is doubled when you configure NetFlow Data Export, twice as much memory is required to convert the flows to Version 9 export format and then export them.
Table 2 provides the definitions of the terms used in Figure 2 through Figure 5.
Figure 2 shows the packet encapsulation process for unicast IPv4 traffic that is received on interface Gigabit Ethernet 3/1 on c65002 in Figure 1. The first flow is the result of NetFlow accounting for the traffic after it is received on physical interface 3/1 (ingress NetFlow). The second flow is the result of NetFlow accounting for the traffic as it is being transmitted on the GRE tunnel interface T0 (egress NetFlow).
Figure 2 Unicast IPv4 Traffic over an IPv4 Unicast GRE Tunnel (Encapsulation)
Figure 3 shows the packet de-encapsulation process for unicast IPv4 traffic that is received on interface Gigabit Ethernet 3/1 on c65002 in Figure 1. The first flow is the result of NetFlow accounting for the traffic after it is received on the physical interface 5/2 (ingress NetFlow). The second flow is the result of NetFlow accounting for the traffic as it is being received and de-encapsulated on the tunnel interface T0 (ingress NetFlow).
Figure 3 Unicast IPv4 Traffic over an IPv4 Unicast GRE Tunnel (De-encapsulation)
During de-encapsulation, only ingress features of the tunnel are applied on the packets, and during encapsulation, only egress features of the tunnel are applied.
Multicast replication can happen in either ingress or egress mode. GRE encapsulation of multicast flows is done on the line card on which the ingress physical interface resides, irrespective of the ingress or egress replication mode. So in the case of both ingress and egress multicast replication modes, egress flows are created on the ingress line card.
The examples in Figure 4 and Figure 5 show how and why multiple flows are created during GRE handling of packets. In Figure 4, Flow 1 is created when packets are received by physical interface 3/1. Flows 2 and 3 are created as part the multicast replication process using the internal virtual local area networks (VLANs) that are required for NetFlow accounting to keep track of the multicast traffic.
Figure 4 Multicast IPv4 Traffic over an IPv4 Unicast GRE Tunnel (Encapsulation)
In Figure 5, Flow 1 is created when packets are received over physical interface 5/2. Flow 2 is created as part of the de-encapsulation process. Flow 3 is created as the multicast traffic is replicated and forwarded on interface 1/1.
Figure 5 Multicast IPv4 Traffic over an IPv4 Unicast GRE Tunnel (De-encapsulation)
How to Configure NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
•
•
•
•
•
•
Sample Network
The tasks in this section use the sample network shown in Figure 6.
Figure 6 Sample Network with a GRE IPv4 Tunnel
Configuring a GRE IP Tunnel
To configure a GRE IP tunnel as shown in Figure 6, perform the task in this section.
Prerequisites
Ensure that the physical interface to be used as the tunnel source in this task is up and configured with the appropriate IP address. For hardware technical descriptions and information about installing interfaces, see the hardware installation and configuration documentation for your product.
Restrictions
GRE tunnel keepalive is not supported in cases where virtual route forwarding (VRF) is applied to a GRE tunnel.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
DETAILED STEPS
Step 1
enable
Example:Router> enable
Enables privileged EXEC mode.
•
Step 2
configure terminal
Example:Router# configure terminal
Enters global configuration mode.
Step 3
interface type number
Example:Router(config)# interface tunnel 0
Specifies the interface type and number and enters interface configuration mode.
•
Step 4
bandwidth kbps
Example:Router(config-if)# bandwidth 1000
Sets the current bandwidth value for an interface and communicates it to higher-level protocols. Specifies the tunnel bandwidth to be used to transmit packets.
•
Note
Step 5
ip address address mask
Example:Router(config-if)# ip address 192.168.3.1 255.255.255.0
Specifies an IP address for the interface.
Step 6
keepalive [period [retries]]
Example:Router(config-if)# keepalive 3 7
(Optional) Specifies the number of times that the device will continue to send keepalive packets without response before bringing the tunnel interface protocol down.
•
•
Note
Note
Step 7
tunnel source {ip-address | interface-type interface-number}
Example:Router(config-if)# tunnel source GigabitEthernet6/2
Configures the tunnel source.
•
•
Note
Step 8
tunnel destination {hostname | ip-address}
Example:Router(config-if)# tunnel destination 10.5.9.62
Configures the tunnel destination.
•
•
Note
Step 9
tunnel key key-number
Example:Router(config-if)# tunnel key 1000
(Optional) Enables an ID key for a tunnel interface.
•
•
Note
Step 10
tunnel mode gre ip
Example:Router(config-if)# tunnel mode gre ip
Specifies GRE IP as the encapsulation protocol to be used in the tunnel.
Step 11
ip mtu bytes
Example:Router(config-if)# ip mtu 1400
(Optional) Set the maximum transmission unit (MTU) size of IP packets sent on an interface.
•
•
Note
Step 12
ip tcp mss mss-value
Example:Router(config-if)# ip tcp mss 250
(Optional) Specifies the maximum segment size (MSS) for TCP connections that originate or terminate on a router.
•
Step 13
tunnel path-mtu-discovery [age-timer {aging-mins | infinite}]
Example:Router(config-if)# tunnel path-mtu-discovery
(Optional) Enables Path MTU Discovery (PMTUD) on a GRE or IP-in-IP tunnel interface.
•
Step 14
end
Example:Router(config-if)# end
Exits interface configuration mode and returns to privileged EXEC mode.
Step 15
Repeat steps 1-14 on the router that hosts the other end of the GRE tunnel
—
Verifying the Status of the GRE IP Tunnel
To verify the tunnel configuration and operation, perform the following optional task:
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Step 1
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
To verify that each router has IP connectivity to the tunnel endpoint on the other router, ping the IP address of the remote tunnel endpoint from the local router.
c65002# ping 192.168.3.2Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.3.2, timeout is 2 seconds:!!!!!Success rate is 100 percent (5/5), round-trip min/avg/max = 20/20/20 msStep 3
To verify that each router has IP connectivity to the tunnel endpoint on the other router, ping the IP address of the remote tunnel endpoint from the local router.
c65003# ping 192.168.3.1Type escape sequence to abort.Sending 5, 100-byte ICMP Echos to 192.168.3.1, timeout is 2 seconds:!!!!!Step 4
Displays the status and statistics of the tunnel interface
c65002# show interface tunnel 0Tunnel0 is up, line protocol is upHardware is TunnelInternet address is 192.168.3.1/24MTU 1514 bytes, BW 1000 Kbit, DLY 50000 usec,reliability 255/255, txload 115/255, rxload 57/255Encapsulation TUNNEL, loopback not setKeepalive not setTunnel source 10.4.9.62 (GigabitEthernet6/2), destination 10.5.9.62Tunnel protocol/transport GRE/IPKey disabled, sequencing disabledChecksumming of packets disabledTunnel TTL 255, Fast tunneling enabledPath MTU Discovery, ager 10 mins, min MTU 92Last input 00:07:35, output 00:00:00, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1Queueing strategy: fifoOutput queue: 0/0 (size/max)5 minute input rate 4139000 bits/sec, 659 packets/sec5 minute output rate 4117000 bits/sec, 669 packets/secL2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytesL3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcastL3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes245049 packets input, 192533770 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicasts)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort251500 packets output, 196216398 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out
Configuring NetFlow Accounting on a GRE IP Tunnel Interface
To configure NetFlow on a GRE IP tunnel interface, perform the following task:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
DETAILED STEPS
Configuring NetFlow Accounting on the Physical Interfaces
To configure NetFlow accounting on one or more physical interfaces, perform the following task:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
Verifying NetFlow Accounting
To verify that NetFlow accounting for the tunnel interface is working, perform the following task.
Note
SUMMARY STEPS
1.
2.
3.
DETAILED STEPS
Step 1
Enables privileged EXEC mode. Enter your password if prompted.
Router> enableStep 2
The show ip cache flow command displays the NetFlow statistics in the cache. The tunnel interface (Tu0) appears in several rows of the statistics, indicating that NetFlow accounting is operational for the tunnel interface.
c65003# show ip cache flow-------------------------------------------------------------------------------Displaying software-switched flow entries on the MSFC in Module 5:IP packet size distribution (3721891 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 1.00 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 278544 bytes2 active, 4094 inactive, 6 added5394 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondsIP Sub Flow Cache, 33992 bytes0 active, 1024 inactive, 0 added, 0 added to flow0 alloc failures, 0 force free1 chunk, 0 chunks addedlast clearing of statistics 05:58:56Protocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 4 0.0 406293 1499 75.4 626.5 12.3Total: 4 0.0 406293 1499 75.4 626.5 12.3SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsFa3/1 192.168.22.2 Tu0* 192.168.10.2 01 0000 0000 1052KFa3/1 192.168.22.2 Tu0 192.168.10.2 01 0000 0000 1052K-------------------------------------------------------------------------------Displaying hardware-switched flow entries in the PFC (Active) Module 5:SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsTu0 10.4.9.62 Gi6/2 10.5.9.62 2F 0000 0000 155K-- 0.0.0.0 --- 0.0.0.0 00 0000 0000 1764KFa3/1 192.168.22.2 Tu0 192.168.10.2 01 0000 0000 65KTu0 192.168.10.2 Fa3/1 192.168.22.2 01 0000 0000 695KTu0 192.168.10.2 Fa3/1 192.168.22.2 01 0008 0000 66KTu0 192.168.10.2 Fa3/1 192.168.22.2 11 F378 F566 90KFa3/1 192.168.22.2 Tu0 192.168.10.2 11 F566 F378 90KStep 3
The show mls net ip mod number command displays information about the hardware-switched NetFlow flows. The tunnel interface (Tu0) appears in several rows of the statistics, indicating that NetFlow accounting is operational for the tunnel interface.
c65003# show mls net ip module 5Displaying NetFlow entries in Active Supervisor EARL in module 5DstIP SrcIP Prot:SrcPort:DstPort Src i/f :AdjPtr-----------------------------------------------------------------------------Pkts Bytes Age LastSeen Attributes---------------------------------------------------224.0.0.2 10.4.9.254 udp :646 :646 Gi6/2 :0x046 2852 200 00:30:28 Multicast0.0.0.0 0.0.0.0 0 :0 :0 -- :0x0238 17450 203 00:30:28 L3 - Dynamic224.0.0.13 172.31.0.2 103 :0 :0 Gi6/2 :0x07 378 189 00:30:21 Multicast224.0.0.5 192.168.255.254 89 :0 :0 Fa3/1 :0x0204 16320 204 00:30:31 Multicast224.0.0.1 172.31.0.2 2 :0 :0 Gi6/2 :0x03 138 174 00:29:38 Multicast10.4.9.255 10.4.9.2 udp :138 :138 Fa3/1 :0x00 0 143 00:28:09 L3 - Dynamic224.0.0.13 192.168.3.2 103 :0 :0 Tu0 :0x06 372 153 00:30:28 Multicast224.192.16.1 172.31.0.1 icmp:0 :0 Fa3/1 :0x020435 940010 205 00:30:32 Multicast224.0.0.1 192.168.3.2 2 :0 :0 Tu0 :0x02 64 103 00:29:49 Multicast10.4.9.255 10.4.9.2 udp :137 :137 Fa3/1 :0x00 0 79 00:30:10 L3 - Dynamic
Configuring NetFlow Data Export Using the Version 9 Export Format
To configure NetFlow Data Export using the Version 9 data export format, perform the following task:
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
Verifying That NetFlow Data Export Is Operational
To verify that NetFlow data export is operational, perform the following optional task.
SUMMARY STEPS
1.
2.
DETAILED STEPS
Step 1
Use this command to display the statistics for the NetFlow data export, including statistics for the main cache and for all other enabled caches. The following is sample output from this command:
Router# show ip flow exportFlow export v9 is enabled for main cacheExport source and destination details :VRF ID : DefaultSource(1) 10.4.9.62 (GigabitEthernet6/2)Source(2) 10.4.9.62 (GigabitEthernet6/2)Destination(1) 172.16.10.2 (99)Destination(2) 172.16.10.3 (99)Version 9 flow records11 flows exported in 11 udp datagrams0 flows failed due to lack of export packet0 export packets were sent up to process level0 export packets were dropped due to no fib0 export packets were dropped due to adjacency issues0 export packets were dropped due to fragmentation failures0 export packets were dropped due to encapsulation fixup failures0 export packets were dropped enqueuing for the RP0 export packets were dropped due to IPC rate limiting0 export packets were dropped due to Card not being able to exportStep 2
Use this command to display the statistics for the NetFlow data export (such as the template timeout rate and the refresh rate) for the template-specific configurations. The following is sample output from this command:
Router# show ip flow export templateTemplate Options Flag = 1Total number of Templates added = 1Total active Templates = 1Flow Templates active = 0Flow Templates added = 0Option Templates active = 1Option Templates added = 1Template ager polls = 0Option Template ager polls = 388Main cache version 9 export is enabledTemplate export informationTemplate timeout = 90Template refresh rate = 15Option export informationOption timeout = 120Option refresh rate = 25
Configuration Examples for NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
The following example shows you how to configure data export for NetFlow:
•
•
Configuring a GRE IP Tunnel: Example
The following example shows how to configure a GRE IP tunnel:
interface Tunnel0tunnel mode gre ipbandwidth 1000ip address 192.168.3.1 255.255.255.0tunnel source GigabitEthernet6/2tunnel destination 10.5.9.62tunnel path-mtu-discoveryThe following display output shows that the GRE IP tunnel is operational because the tunnel is transmitting and receiving traffic:
c65002# show interface tunnel 0Tunnel0 is up, line protocol is upHardware is TunnelInternet address is 192.168.3.1/24MTU 1514 bytes, BW 1000 Kbit, DLY 50000 usec,reliability 255/255, txload 90/255, rxload 98/255Encapsulation TUNNEL, loopback not setKeepalive not setTunnel source 10.4.9.62 (GigabitEthernet6/2), destination 10.5.9.62Tunnel protocol/transport GRE/IPKey disabled, sequencing disabledChecksumming of packets disabledTunnel TTL 255, Fast tunneling enabledPath MTU Discovery, ager 10 mins, min MTU 92Last input 00:11:44, output 00:11:44, output hang neverLast clearing of "show interface" counters neverInput queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 1Queueing strategy: fifoOutput queue: 0/0 (size/max)5 minute input rate 380000 bits/sec, 125 packets/sec5 minute output rate 347000 bits/sec, 125 packets/secL2 Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytesL3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcastL3 out Switched: ucast: 0 pkt, 0 bytes mcast: 0 pkt, 0 bytes3344121 packets input, 2452613051 bytes, 0 no bufferReceived 0 broadcasts (0 IP multicasts)0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort3399211 packets output, 2431569783 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped outConfiguring NetFlow Accounting on a GRE IP Tunnel: Example
The following example shows how to configure NetFlow Accounting on a GRE IP Tunnel and a FastEthernet interface:
mls flow ip interface-fullinterface tunnel 0ip flow egressip flow ingressinterface FastEthernet3/1no shutip address 192.168.22.1 255.255.255.0ip flow ingressip flow egressThe following display output shows that NetFlow accounting is operational because the flow cache has NetFlow statistics data in it:
c65002# show ip cache flow-------------------------------------------------------------------------------Displaying software-switched flow entries on the MSFC in Module 5:IP packet size distribution (3721891 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000 .000512 544 576 1024 1536 2048 2560 3072 3584 4096 4608.000 .000 .000 .000 1.00 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 278544 bytes2 active, 4094 inactive, 6 added5394 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondsIP Sub Flow Cache, 33992 bytes0 active, 1024 inactive, 0 added, 0 added to flow0 alloc failures, 0 force free1 chunk, 0 chunks addedlast clearing of statistics 05:58:56Protocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 4 0.0 406293 1499 75.4 626.5 12.3Total: 4 0.0 406293 1499 75.4 626.5 12.3SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsFa3/1 192.168.22.2 Tu0* 192.168.10.2 01 0000 0000 1052KFa3/1 192.168.22.2 Tu0 192.168.10.2 01 0000 0000 1052K-------------------------------------------------------------------------------Displaying hardware-switched flow entries in the PFC (Active) Module 5:SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsTu0 10.4.9.62 Gi6/2 10.5.9.62 2F 0000 0000 155K-- 0.0.0.0 --- 0.0.0.0 00 0000 0000 1764KFa3/1 192.168.22.2 Tu0 192.168.10.2 01 0000 0000 65KTu0 192.168.10.2 Fa3/1 192.168.22.2 01 0000 0000 695KTu0 192.168.10.2 Fa3/1 192.168.22.2 01 0008 0000 66KTu0 192.168.10.2 Fa3/1 192.168.22.2 11 F378 F566 90KFa3/1 192.168.22.2 Tu0 192.168.10.2 11 F566 F378 90KThe following display output shows that NetFlow accounting is operational because there are statistics for the hardware-switched NetFlow flows.
c65003# show mls net ip mod 5Displaying NetFlow entries in Active Supervisor EARL in module 5DstIP SrcIP Prot:SrcPort:DstPort Src i/f :AdjPtr-----------------------------------------------------------------------------Pkts Bytes Age LastSeen Attributes---------------------------------------------------224.0.0.2 10.4.9.254 udp :646 :646 Gi6/2 :0x046 2852 200 00:30:28 Multicast0.0.0.0 0.0.0.0 0 :0 :0 -- :0x0238 17450 203 00:30:28 L3 - Dynamic224.0.0.13 172.31.0.2 103 :0 :0 Gi6/2 :0x07 378 189 00:30:21 Multicast224.0.0.5 192.168.255.254 89 :0 :0 Fa3/1 :0x0204 16320 204 00:30:31 Multicast224.0.0.1 172.31.0.2 2 :0 :0 Gi6/2 :0x03 138 174 00:29:38 Multicast10.4.9.255 10.4.9.2 udp :138 :138 Fa3/1 :0x00 0 143 00:28:09 L3 - Dynamic224.0.0.13 192.168.3.2 103 :0 :0 Tu0 :0x06 372 153 00:30:28 Multicast224.192.16.1 172.31.0.1 icmp:0 :0 Fa3/1 :0x020435 940010 205 00:30:32 Multicast224.0.0.1 192.168.3.2 2 :0 :0 Tu0 :0x02 64 103 00:29:49 Multicast10.4.9.255 10.4.9.2 udp :137 :137 Fa3/1 :0x00 0 79 00:30:10 L3 - DynamicAdditional References
Related Documents
Configuring Cisco IOS 12.2SX on Cisco Catalyst 6500 series switches
Catalyst 6500 Release 12.2SXH and Later Software Configuration Guide
Standards
MIBs
RFCs
Technical Assistance
Feature Information for Configuring NetFlow Accounting for Unicast and Multicast on GRE IP Tunnel Interfaces
Table 3 lists the features in this module and provides links to specific configuration information. Only features that were introduced or modified in Cisco IOS Release 12.2(1) or 12.0(3)S or a later release appear in the table.
Not all commands may be available in your Cisco IOS software release. For details on when support for a specific command was introduced, see the command reference documentation.
For information on a feature in this technology that is not documented here, see the "Cisco IOS NetFlow Features Roadmap".
Cisco IOS software images are specific to a Cisco IOS software release, a feature set, and a platform. Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://www.cisco.com/go/fn. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.
Note
Table 3 Feature Information for Flexible NetFlow
Configuring NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces
12.2(33)SXI
The Configuring NetFlow Accounting for Unicast and Multicast on GRE Tunnel Interfaces feature allows NetFlow statistics to be gathered on traffic that is transmitted over a GRE IP tunnel interface.
The following section provides information for configuring this feature:
•
•
No commands were introduced or modified for this feature.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
