Table Of Contents
Cisco IOS Switching Commands
This chapter documents commands used to configure switching and NetFlow features in Cisco IOS software. For guidelines on configuring switching and NetFlow features, refer to the Cisco IOS Switching Services Configuration Guide.
Note
Beginning with Cisco IOS Release 11.3, all commands supported on the Cisco 7500 series routers are also supported on Cisco 7000 series routers.
clear ip cache
To delete entries in the routing table cache used to fast switch IP traffic, use the clear ip cache command in the privileged EXEC mode.
clear ip cache [prefix mask]
Syntax Description
prefix mask
(Optional) Deletes only the entries in the cache that match the prefix and mask combination.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear routes from the routing table cache. You can remove all entries in the routing cache or you can remove only those entries associated with a specified prefix and mask.
Examples
The following command shows how to delete entire in the routing table cache:
Router# clear ip cacheThe following command show how to delete entries in the router table associated with the prefix and mask 192.168.32.0 255.255.255.0:
Router# clear ip cache 192.168.32.0 255.255.255.0Related Commands
ip route-cache
Controls the use of high-speed switching caches for IP routing.
show ip cache
Displays the routing table cache used to fast switch IP traffic.
clear ip flow stats
To clear the NetFlow statistics, use the clear ip flow stats EXEC command.
clear ip flow stats
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
The show ip cache flow command displays the NetFlow statistics. Use the clear ip flow stats command to clear the NetFlow statistics.
Examples
The following example clears the NetFlow statistics on the router:
clear ip flow statsRelated Commands
encapsulation isl
Use the encapsulation isl subinterface configuration command to enable the Inter-Switch Link (ISL). ISL is a Cisco protocol for interconnecting multiple switches and routers, and for defining VLAN topologies.
encapsulation isl vlan-identifier
Syntax Description
Defaults
Disabled
Command Modes
Subinterface configuration
Command History
Usage Guidelines
ISL encapsulation is configurable on Fast Ethernet interfaces.
ISL encapsulation adds a 26-byte header to the beginning of the Ethernet frame. The header contains a 10-bit VLAN identifier that conveys VLAN membership identities between switches.
Examples
The following example enables ISL on Fast Ethernet subinterface 2/1.20:
interface FastEthernet 2/1.20encapsulation isl 400Related Commands
encapsulation sde
Use the encapsulation sde subinterface configuration command to enable IEEE 802.10 encapsulation of traffic on a specified subinterface in virtual LANs. IEEE 802.10 is a standard protocol for interconnecting multiple switches and routers, and for defining VLAN topologies.
encapsulation sde said
Syntax Description
said
Security association identifier. This value is used as the virtual LAN identifier. The valid range is 0 through 0xFFFFFFFE.
Defaults
Disabled
Command Modes
Subinterface configuration
Command History
Usage Guidelines
SDE encapsulation is configurable only on the following interface types:
•
•
•
•
•
•
Examples
The following example enables SDE on FDDI subinterface 2/0.1 and assigns a VLAN identifier of 9999:
interface fddi 2/0.1encapsulation sde 9999Related Commands
encapsulation tr-isl
Use the encapsulation tr-isl subinterface configuration command to enable TRISL, a Cisco proprietary protocol for interconnecting multiple routers and switches and maintaining VLAN information as traffic goes between switches.
encapsulation tr-isl trbrf-vlan vlan-id bridge-num bridge-number
Syntax Description
vlan-id
Number identifying the VLAN.
bridge-num
Keyword that specifies the identification number of the bridge number on the ISL trunk. Possible values are 01 to 4095.
Command Modes
Subinterface configuration
Command History
Examples
In the following example, TRISL is enabled on a Fast Ethernet interface:
interface FastEthernet4/0.2 encapsulation tr-isl trbrf-vlan 999 bridge-num 14Related Commands
ip cache-invalidate-delay
To control the invalidation rate of the IP route cache, use the ip cache-invalidate-delay global configuration command. To allow the IP route cache to be immediately invalidated, use the no form of this command.
ip cache-invalidate-delay [minimum maximum quiet threshold]
no ip cache-invalidate-delay
Syntax Description
Defaults
minimum = 2 seconds
maximum = 5 seconds, and 3 seconds with no more than zero invalidation requestsCommand Modes
Global configuration
Command History
Usage Guidelines
All cache invalidation requests are honored immediately.
This command should typically not be used except under the guidance of technical support personnel. Incorrect settings can seriously degrade network performance.
The IP fast-switching and autonomous-switching features maintain a cache of IP routes for rapid access. When a packet is to be forwarded and the corresponding route is not present in the cache, the packet is process-switched and a new cache entry is built. However, when routing table changes occur (such as when a link or an interface goes down), the route cache must be flushed so that it can be rebuilt with up-to-date routing information.
This command controls how the route cache is flushed. The intent is to delay invalidation of the cache until after routing has settled down. Because route table changes tend to be clustered in a short period of time, and the cache may be flushed repeatedly, a high CPU load might be placed on the router.
When this feature is enabled, and the system requests that the route cache be flushed, the request is held for at least minimum seconds. Then the system determines whether the cache has been "quiet" (that is, less than threshold invalidation requests in the last quiet seconds). If the cache has been quiet, the cache is then flushed. If the cache does not become quiet within maximum seconds after the first request, it is flushed unconditionally.
Manipulation of these parameters trades off CPU utilization versus route convergence time. Timing of the routing protocols is not affected, but removal of stale cache entries is affected.
Examples
The following example sets a minimum delay of 5 seconds, a maximum delay of 30 seconds, and a quiet threshold of no more than 5 invalidation requests in the previous 10 seconds:
ip cache-invalidate-delay 5 30 10 5Related Commands
Configures the router to export the flow cache entry to a workstation when a flow expires.
Displays the routing table cache used to fast switch IP traffic.
ip flow-export
To enable the exporting of information in NetFlow cache entries, use the ip flow-export global configuration command. To disable the exporting of information, use the no form of this command.
ip flow-export ip-address udp-port [version 1 | version 5 [origin-as | peer-as]]
no ip flow-export
Syntax Description
Defaults
Disabled
Command Modes
Global configuration
Command History
Usage Guidelines
There is a lot of information in a NetFlow cache entry. When NetFlow is enabled with the ip route-cache flow command, you can use the ip flow-export command to configure the router to export the flow cache entry to a workstation when a flow expires. This feature can be useful for purposes of statistics, billing, and security.
Version 5 format includes the source and destination AS addresses, source and destination prefix masks, and a sequence number. Because this change may appear on your router as a maintenance release, support for version 1 format is maintained with the version 1 keyword.
Caution
For more information on version 1 and version 5 data format, refer to the "NetFlow Data Format" section in the "Configuring NetFlow" chapter of the Cisco IOS Switching Services Configuration Guide.
Examples
The following example configures the router to export the NetFlow cache entry to UDP port 125 on the workstation at 134.22.23.7 when the flow expires using version 1 format:
ip flow-export 134.22.23.7 125The following example configures the router to export the NetFlow cache entry to UDP port 2048 on the workstation at 134.22.23.7 when the flow expires using version 5 format and including the peer AS information:
ip flow-export 134.22.23.7 2048 version 5 peer-asRelated Commands
ip flow-export source
To specify the source interface IP address used in the NetFlow export datagram, use the ip flow-export source command in global configuration mode. To remove the source address, use the no form of this command.
ip flow-export source interface
no ip flow-export source
Syntax Description
Defaults
No source interface is specified.
Command Modes
Global configuration
Command History
Usage Guidelines
After you configure NetFlow data export, you can also specify the source interface used in the UDP datagram containing the export data. The NetFlow Collector on the workstation uses the IP address of the source interface to determine which router sent the information. The NetFlow Collector also performs SNMP queries to the router using the IP address of the source interface. Because the IP address of the source interface can change (for example, the interface might flap so a different interface is used to send the data), we recommend you configure a loopback source interface. A loopback interface is always up and can respond to SNMP queries from the NetFlow Collector on the workstation.
Examples
The following example shows the configuration for a loopback source interface. The loopback interface has the IP address 4.0.0.1 and is used by the serial interface in slot 5, port 0.
Router# configure terminalRouter(config)# interface loopback0Router(config-if)# ip address 4.0.0.1 255.0.0.0Router(config-if)# exitRouter(config)# interface serial 5/0:0Router(config-if)# ip unnumbered loopback0Router(config-if)# no ip mroute-cacheRouter(config-if)# encapsulation pppRouter(config-if)# ip route-cache flowRouter(config-if)# exitRouter(config)# ip flow-export source loopback0Router(config)# exitRelated Commands
ip route-cache
Use the ip route-cache interface configuration command to control the use of high-speed switching caches for IP routing. To disable any of these switching modes, use the no form of this command.
ip route-cache [cbus]
no ip route-cache [cbus]
ip route-cache same-interface
no ip route-cache same-interface
ip route-cache [flow]
no ip route-cache [flow]
ip route-cache distributed
no ip route-cache distributed
Syntax Description
Defaults
IP autonomous switching is disabled.
Fast switching varies by interface and media.
Distributed switching is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Using the route cache is often called fast switching. The route cache allows outgoing packets to be load-balanced on a per-destination basis.
The ip route-cache command with no additional keywords enables fast switching.
Cisco routers generally offer better packet transfer performance when fast switching is enabled, with one exception. On networks using slow serial links (64K and below), disabling fast switching to enable the per-packet load sharing is usually the best choice.
You can enable IP fast switching when the input and output interfaces are the same interface, using the ip route-cache same-interface command. This normally is not recommended, though it is useful when you have partially meshed media, such as Frame Relay or you are running Web Cache Communication Protocol (WCCP) redirection. You could use this feature on other interfaces, although it is not recommended because it would interfere with redirection of packets to the optimal path.
On Cisco 7500 series routers with RSP and Versatile Interface Processor (VIP) controllers, the VIP hardware can be configured to switch packets received by the VIP with no per-packet intervention on the part of the RSP. When VIP distributed switching is enabled, the input VIP interface tries to switch IP packets instead of forwarding them to the RSP for switching. Distributed switching helps decrease the demand on the RSP.
Not all switching methods are available on all platforms. Refer to the Cisco Product Catalog for information about features available on the platform you are using.
Examples
The following example enables both fast switching and autonomous switching:
ip route-cache cbusThe following example disables both fast switching and autonomous switching:
no ip route-cacheThe following example turns off autonomous switching only:
no ip route-cache cbusThe following example enables VIP distributed switching and NetFlow on the interface:
interface ethernet 0/5/0ip address 17.252.245.2 255.255.255.0ip route-cache distributedip route-cache flowThe following example returns the system to its defaults (fast switching enabled; autonomous switching disabled):
ip route-cacheRelated Commands
Controls the invalidation rate of the IP route cache.
Displays the routing table cache used to fast switch IP traffic.
ip route-cache flow
To enable NetFlow for IP routing, use the ip route-cache flow interface configuration command. To disable NetFlow, use the no form of this command.
ip route-cache flow
no ip route-cache flow
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
NetFlow captures a rich set of traffic statistics. These traffic statistics include user, protocol, port, and type of service information that can be used for a wide variety of purposes such as network analysis and planning, accounting, and billing. To export NetFlow data, use the ip flow-export global configuration command.
NetFlow is supported on IP and IP encapsulated traffic over all interface types and encapsulations except for ISL/VLAN, ATM and Frame Relay interfaces when more than one input access control list is used on the interface, and ATM LANE.
A network flow is identified as a unidirectional stream of packets between a source and destination—both defined by a network-layer IP address and transport-layer port number. Specifically, a flow is identified as the combination of the following fields:
•
•
•
•
•
•
•
NetFlow operates by creating a flow cache. The cache includes entries for traffic statistics. Flow information is maintained within the NetFlow cache for all active flows.
NetFlow does not involve any connection-setup protocol either between routers or to any other networking device or end station and does not require any change externally—either to the traffic or packets themselves or to any other networking device. Thus, NetFlow is completely transparent to the existing network, including end stations and application software and network devices like LAN switches. Also, because NetFlow is performed independently on each internetworking device, it does not need to be operational on each router in the network. Network planners can selectively invoke NetFlow (and NetFlow data export) on a router/interface basis to gain traffic performance, control, or accounting benefits in specific network locations.
Note
Examples
The following example enables NetFlow on the interface:
interface ethernet 0/5/0ip address 17.252.245.2 255.255.255.0ip route-cache flowThe following example returns the interface to its defaults (fast switching enabled; autonomous switching disabled):
interface ethernet 0/5/0ip route-cacheRelated Commands
Enables the exporting of information in NetFlow cache entries.
Displays the routing table cache used to fast switch IP traffic.
ip route-cache policy
To enable fast-switch Policy Based Routing (PBR), use the ip route-cache policy command in interface configuration mode. To disable fast-switched PBR, use the no form of this command.
[no] ip route-cache policy
Syntax Description
This command has no arguments or keywords.
Defaults
Not enabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
1.
2.
3.
–
–
Also, at the process level, the routing table is consulted to determine if the interface is on a reasonable path to the destination. During fast switching, the software does not make this check. Instead, if the packet matches, the software blindly forwards the packet to the specified interface.Examples
The following example enables fast-switch Policy Based Routing on an Ethernet interface:
Router# config tEnter configuration commands, one per line. End with CNTL/Z.Router(config)# int e 1/3Router(config-if)# ip route-cache policyRouter(config-if)# endRelated Commands
show ip cache
To display the routing table cache used to fast switch IP traffic, use the show ip cache EXEC command.
show ip cache [prefix mask] [type number]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show ip cache display shows MAC headers up to 92 bytes.
Examples
The following is sample output from the show ip cache command:
Router# show ip cacheIP routing cache version 4490, 141 entries, 20772 bytes, 0 hash overflowsMinimum invalidation interval 2 seconds, maximum interval 5 seconds,quiet interval 3 seconds, threshold 0 requestsInvalidation rate 0 in last 7 seconds, 0 in last 3 secondsLast full cache invalidation occurred 0:06:31 agoPrefix/Length Age Interface MAC Header131.108.1.1/32 0:01:09 Ethernet0/0 AA000400013400000C0357430800131.108.1.7/32 0:04:32 Ethernet0/0 00000C01281200000C0357430800131.108.1.12/32 0:02:53 Ethernet0/0 00000C029FD000000C0357430800131.108.2.13/32 0:06:22 Fddi2/0 00000C05A3E000000C035753AAAA030000000800131.108.2.160/32 0:06:12 Fddi2/0 00000C05A3E000000C035753AAAA030000000800131.108.3.0/24 0:00:21 Ethernet1/2 00000C026BC600000C03574D0800131.108.4.0/24 0:02:00 Ethernet1/2 00000C026BC600000C03574D0800131.108.5.0/24 0:00:00 Ethernet1/2 00000C04520800000C03574D0800131.108.10.15/32 0:05:17 Ethernet0/2 00000C025FF500000C0357450800131.108.11.7/32 0:04:08 Ethernet1/2 00000C010E3A00000C03574D0800131.108.11.12/32 0:05:10 Ethernet0/0 00000C01281200000C0357430800131.108.11.57/32 0:06:29 Ethernet0/0 00000C01281200000C0357430800Table 92 describes significant fields shown in the display.
The following is sample output from the show ip cache command with a prefix and mask specified:
Router# show ip cache 131.108.5.0 255.255.255.0IP routing cache version 4490, 119 entries, 17464 bytes, 0 hash overflowsMinimum invalidation interval 2 seconds, maximum interval 5 seconds,quiet interval 3 seconds, threshold 0 requestsInvalidation rate 0 in last second, 0 in last 3 secondsLast full cache invalidation occurred 0:11:56 agoPrefix/Length Age Interface MAC Header131.108.5.0/24 0:00:34 Ethernet1/2 00000C04520800000C03574D0800The following is sample output from the show ip cache command with an interface specified:
Router# show ip cache e0/2IP routing cache version 4490, 141 entries, 20772 bytes, 0 hash overflowsMinimum invalidation interval 2 seconds, maximum interval 5 seconds,quiet interval 3 seconds, threshold 0 requestsInvalidation rate 0 in last second, 0 in last 3 secondsLast full cache invalidation occurred 0:06:31 agoPrefix/Length Age Interface MAC Header131.108.10.15/32 0:05:17 Ethernet0/2 00000C025FF500000C0357450800show ip cache flow
To display a summary of the NetFlow statistics, use the show ip cache flow command in EXEC mode.
show ip cache [prefix mask] [type number] [verbose] flow
Syntax Description
Command Modes
EXEC
Command History
11.1
This command was introduced.
11.1 CA
The information display for the command was updated.
Displaying NetFlow Cache Information on a Distributed Cisco 7500 Series Platform
To display NetFlow cache information using the show ip cache flow command on a Cisco 7500 series router that is running dCEF, enter the following sequence of commands:
Router# if-con slot-numberLC-slot-number# show ip cache [prefix mask] [type number] [verbose] flowDisplaying NetFlow Cache Information on a Distributed Cisco 12000 Series Platform
To display NetFlow cache information using the show ip cache flow command on a Cisco 12000 Series Internet router, you enter the following sequence of commands:
Router# attach slot-numberLC-slot-number# show ip cache [prefix mask] [type number] [verbose] flowExamples
The following is an example display of a main cache using the show ip cache flow command:
Router# show ip cache flowIP packet size distribution (230151 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.999 .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 .000 .000 .000 .000 .000 .000 .000The output above shows the percentage distribution of packets by size range. In this display, 99.9 percent of the packets fall in the size range from 1 to 33 bytes.
IP Flow Switching Cache, 4456448 bytes65509 active, 27 inactive, 820628747 added955454490 ager polls, 0 flow alloc failuresExporting flows to 1.1.15.1 (2057)820563238 flows exported in 34485239 udp datagrams, 0 failedlast clearing of statistics 00:00:03Protocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowTCP-BGP 71 0.0 1 49 0.0 2.5 15.8UDP-other 17 0.0 1 328 0.0 0.0 15.7ICMP 18966 6.7 10 28 72.9 0.1 22.9Total: 19054 6.7 10 28 72.9 0.1 22.9SrcIf SrcIPaddress DstIf DstIPaddress Pr TOS Flgs PktsPort Msk AS Port Msk AS NextHop B/Pk ActiveEt1/1 52.52.52.1 Fd4/0 42.42.42.1 01 55 10 37480000 /8 50 0000 /8 40 202.120.130.2 28 17.8Et1/2 52.52.52.1 Fd4/0 42.42.42.1 01 CC 10 35680000 /8 50 0000 /8 40 202.120.130.2 28 17.8Et1/2 10.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11240000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 11.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11570000 /0 0 0000 /8 40 202.120.130.2 28 17.7Et1/2 14.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11490000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 15.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11270000 /0 0 0000 /8 40 202.120.130.2 28 17.7Et1/2 12.1.3.2 Fd4/0 42.42.42.1 01 C0 10 12040000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 13.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11590000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 18.1.3.2 Fd4/0 42.42.42.1 01 C0 10 12230000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 19.1.3.2 Fd4/0 42.42.42.1 01 C0 10 12640000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 16.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11700000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 17.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11670000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 22.1.3.2 Fd4/0 42.42.42.1 01 C0 10 11930000 /0 0 0000 /8 40 202.120.130.2 28 17.8Et1/2 23.1.3.2 Fd4/0 42.42.42.1 01 C0 10 12120000 /0 0 0000 /8 40 202.120.130.2 28 17.7Et1/1 50.50.50.1 Local 31.31.31.1 06 C0 18 200B3 /32 0 2AF8 /32 0 0.0.0.0 49 10.1The following shows sample output from the show ip cache prefix mask flow command:
Router# show ip cache 10.0.0.1 256.0.0.0 flowIP packet size distribution (25 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 1.00 .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 .000 .000 .000 .000 .000 .000 .000The output above shows the percentage distribution of packets by size range. In this display, 100 percent of the packets fall in the128 byte range.
IP Flow Switching Cache, 4456704 bytes1 active, 65535 inactive, 5 added68 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondslast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 4 0.0 5 100 0.0 0.0 15.2Total: 4 0.0 5 100 0.0 0.0 15.2SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsEt1/2 10.0.0.2 Local 10.0.0.1 01 0000 0800 5The following shows sample output from the show ip cache type number flow command:
Router# show ip cache e1/2 flowIP packet size distribution (30 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 1.00 .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 .000 .000 .000 .000 .000 .000 .000IP Flow Switching Cache, 4456704 bytes1 active, 65535 inactive, 6 added85 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondslast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 5 0.0 5 100 0.0 0.0 15.1Total: 5 0.0 5 100 0.0 0.0 15.1SrcIf SrcIPaddress DstIf DstIPaddress Pr SrcP DstP PktsEt1/2 10.0.0.2 Local 10.0.0.1 01 0000 0800 5The following shows sample output from the show ip cache verbose flow command for interface e1/2 on 10.0.0.1 255.0.0.0:
Router# show ip cache 10.0.0.1 255.0.0.0 e1/2 verbose flowIP packet size distribution (35 total packets):1-32 64 96 128 160 192 224 256 288 320 352 384 416 448 480.000 .000 .000 1.00 .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 .000 .000 .000 .000 .000 .000 .000The output above show the percentage distribution of packets by size range. In this display,100 percent of the packets fall in the 138 byte size range.
IP Flow Switching Cache, 4456704 bytes1 active, 65535 inactive, 7 added99 ager polls, 0 flow alloc failuresActive flows timeout in 30 minutesInactive flows timeout in 15 secondslast clearing of statistics neverProtocol Total Flows Packets Bytes Packets Active(Sec) Idle(Sec)-------- Flows /Sec /Flow /Pkt /Sec /Flow /FlowICMP 6 0.0 5 100 0.0 0.0 15.2Total: 6 0.0 5 100 0.0 0.0 15.2SrcIf SrcIPaddress DstIf DstIPaddress Pr TOS Flgs PktsPort Msk AS Port Msk AS NextHop B/Pk ActiveEt1/2 10.0.0.2 Local 10.0.0.1 01 00 10 50000 /8 0 0800 /8 0 0.0.0.0 100 0.0Table 93 describes the significant fields shown in the flow switching cache lines of the displays.
Table 94 describes the significant fields shown in the activity by protocol lines of the display.
Table 95 describes the significant fields from the source to destination of the packets shown in the display.
Related Commands
clear ip flow stats
Clears the NetFlow statistics.
ip route-cache
Configures the router to export the flow cache entry to a workstation when a flow expires.
