Table Of Contents
access-list rate-limit
address-family
append-after
atm-address
bgp default route-target filter
bgp scan-time
cable bundle
cable helper-address
cache
class (MPLS)
clear adjacency
clear atm vc
clear cef interface
clear cef linecard
clear ip cache
clear ip cef event-log
clear ip cef inconsistency
clear ip cef prefix-statistics
clear ip flow stats
clear ip mds
clear ip mds linecard
clear ip mds forwarding
clear ip mroute
clear ip pim interface count
clear ip route vrf
clear lane le-arp
clear lane server
clear mpoa client cache
clear mpoa server cache
clear vlan
clear vlan mapping
client-atm-address name
default-name
enabled (aggregation cache)
encapsulation dot1q
encapsulation isl
encapsulation sde
encapsulation tr-isl trbrf-vlan
exit-address-family
export destination
export map
extended-port
holding-time
import map
index
interface atm
interface fastethernet
interface XTagATM
ip cache-invalidate-delay
ip cef
access-list rate-limit
To configure an access list for use with committed access rate (CAR) policies, use the access-list rate-limit global configuration command. To remove the access list from the configuration, use the no form of this command.
access-list rate-limit acl-index {precedence | mac-address | exp | mask mask}
no access-list rate-limit acl-index {precedence | mac-address | exp | mask mask}
Syntax Description
acl-index
|
Specifies the access list number. Classification options are as follows:
• For IP precedence, use any number from 1 to 99.
• For MAC address, use any number from 100 to 199.
• For MPLS experimental field, use any number from 200 to 299.
|
precedence
|
Specifies the IP precedence. Valid values are from 0 to 7.
|
mac-address
|
Specifies the MAC address.
|
exp
|
Specifies the MPLS experimental field. Valid values are from 0 to 7.
|
mask mask
|
Specifies the mask. Use this option if you want to assign multiple IP precedences or MPLS experimental field values to the same rate-limit access list.
|
Defaults
No CAR access lists are configured.
Command Modes
Global configuration
Command History
Release
|
Modification
|
11.1 CC
|
This command was introduced.
|
12.1(5)T
|
This command now includes an access list based on the MPLS experimental field.
|
Usage Guidelines
Use this command to classify packets by the specified IP precedence, MAC address, or MPLS experimental field values for a particular CAR access list. You can then apply CAR policies, using the rate-limit command, to individual rate-limit access lists causing packets with different IP precedences, MAC addresses, or MPLS experimental field values to be treated differently by the CAR process.
You can specify only one command for each rate-limit access list. If you enter this command multiple times with the same access list number, the new command overwrites the previous command.
Use the mask keyword to assign multiple IP precedences or MPLS experimental field values to the same rate-limit list. To ascertain the mask value, perform the following steps:
Step 1
Decide which precedences you want to assign to this rate-limit access list.
Step 2
Convert the precedences or MPLS experimental field values into 8-bit numbers with each bit corresponding to one value. For example, an MPLS experimental field value of 0 corresponds to 00000001, 1 corresponds to 00000010, 6 corresponds to 01000000, and 7 corresponds to 10000000.
Step 3
Add the 8-bit numbers for the selected MPLS experimental field values. For example, the mask for MPLS experimental field values 1 and 6 is 01000010.
Step 4
The command expects hexadecimal format. Convert the binary mask into the corresponding hexadecimal number. For example, 01000010 becomes 42. This value is used in the access-list rate-limit command. Any packets that have an MPLS experimental field value of 1 or 6 will match this access list.
A mask of FF matches any precedence; a mask of 00 does not match any precedence.
Examples
In the following example, MPLS experimental fields with the value of 7 are assigned to the rate-limit access list 200:
router(config)# access-list rate-limit 200 7
You can then use the rate-limit access list in a rate-limit command so that the rate limit is applied only to packets matching the rate-limit access list:
router(config)# interface atm4/0.1 mpls
router(config-if)# rate-limit input access-group rate-limit 200 8000 8000 8000
conform-action set-mpls-exp-transmit 4 exceed-action set-mpls-exp-transmit 0
Related Commands
Command
|
Description
|
rate-limit
|
Configures CAR and DCAR policies.
|
show access-list rate-limit
|
Displays information about rate-limit access lists.
|
address-family
To enter the address family submode for configuring routing protocols such as BGP, RIP, and static routing, use the address-family command in address family configuration submode. To disable the address family submode for configuring routing protocols, use the no form of this command.
VPN-IPv4 Unicast
address-family vpnv4 [unicast]
no address-family vpnv4 [unicast]
IPv4 Unicast
address-family ipv4 [unicast]
no address-family ipv4 [unicast]
IPv4 Unicast with CE router
address-family ipv4 [unicast] vrf vrf-name
no address-family ipv4 [unicast] vrf vrf-name
Syntax Description
vpnv4
|
Configures sessions that carry customer VPN-IPv4 prefixes, each of which has been made globally unique by adding an 8-byte route distinguisher.
|
ipv4
|
Configures sessions that carry standard IPv4 address prefixes.
|
unicast
|
(Optional) Specifies unicast prefixes.
|
vrf vrf-name
|
Specifies the name of a VPN routing and forwarding instance (VRF) to associate with submode commands.
|
Defaults
Routing information for address family IPv4 is advertised by default when you configure a BGP session using the neighbor...remote-as command unless you execute the no bgp default ipv4-activate command.
Command Modes
Address family configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Using the address-family command puts the router in address family configuration submode (prompt: (config-router-af)# ). Within this submode, you can configure address-family specific parameters for routing protocols, such as BGP, that can accommodate multiple Layer 3 address families.
To leave address family configuration submode and return to router configuration mode, enter the exit-address-family or exit command.
Examples
The address-family command in the following example puts the router into address family configuration submode for the VPNv4 address family. Within the submode, you can configure advertisement of NLRI for the VPNv4 address family using neighbor activate and other related commands:
The command in the following example puts the router into address family configuration submode for the IPv4 address family. Use this form of the command, which specifies a VRF, only to configure routing exchanges between PE and CE devices. This address-family command causes subsequent commands entered in the submode to be executed in the context of VRF vrf2. Within the submode, you can use neighbor activate and other related commands to accomplish the following:
•
Configure advertisement of IPv4 NLRI between the PE and CE routers.
•
Configure translation of the IPv4 NLRI (that is, translate IPv4 into VPNv4 for NLRI received from the CE, and translate VPNv4 into IPv4 for NLRI to be sent from the PE to the CE).
•
Enter the routing parameters that apply to this VRF.
The following commands enter the address family submode:
address-family ipv4 unicast vrf vrf2
Related Commands
Command
|
Description
|
default
|
Exits from address family submode.
|
neighbor activate
|
Enables the exchange of information with a neighboring router.
|
append-after
To insert a path entry after a specified index number, use the append-after IP explicit path configuration command.
append-after index command
Syntax Description
index
|
Previous index number. Valid values are from 0 to 65534.
|
command
|
An IP explicit path configuration command that creates a path entry. (Use the next-address command to specify the next IP address in the explicit path.)
|
Defaults
No default behavior or values.
Command Modes
IP explicit path configuration
Command History
Release
|
Modification
|
12.0(5)S
|
This command was introduced.
|
Examples
In the following example, the next-address command is inserted after index 5:
Router(config-ip-expl-path)# append-after 5 next-address 3.3.27.3
Related Commands
Command
|
Description
|
index
|
Inserts or modifies a path entry at a specific index.
|
interface fastethernet
|
Enters the command mode for IP explicit paths and creates or modifies the specified path.
|
list
|
Displays all or part of the explicit paths.
|
next-address
|
Specifies the next IP address in the explicit path.
|
show ip explicit-paths
|
Displays the configured IP explicit paths.
|
atm-address
To override the control ATM address of an MPC or MPS, use the atm-address command in interface configuration mode. To revert to the default address, use the no form of this command.
atm-address atm-address
no atm-address
Syntax Description
atm-address
|
Control ATM address.
|
Defaults
The default is an automatically generated ATM address.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3(3a)WA4(5)
|
This command was introduced.
|
Usage Guidelines
This command specifies the control ATM address that an MPC or MPS should use when it comes up; that is, when it is associated with a hardware interface.
The atm-address command overrides the default operational control address of the MPC or MPS. When this address is deleted (using the no form of the command), the MPC or MPS uses an automatically generated address as its control address.
Examples
The following example specifies the ATM address for an MPC:
atm-address 47.0091810000000061705b7701.00400BFF0011.00
The following example specifies the ATM address for an MPS:
atm-address 47.0091810000000061705C2B01.00E034553024.00
bgp default route-target filter
To enable automatic BGP route-target community filtering, use the bgp default route-target filter router configuration command. To disable this feature, use the no form of this command.
bgp default route-target filter
no bgp default route-target filter
Syntax Description
This command has no arguments or keywords.
Defaults
This command is enabled by default.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
Usage Guidelines
Use the bgp default route-target filter command to control the distribution of VPN routing information through the list of VPN route-target communities.
When you use the no form of this command, all received VPN-IPv4 routes are accepted by the configured router. Accepting VPN-IPv4 routes is the desired behavior for a router configured as an autonomous system border edge router or as a CEBGP border edge router.
If you configure the router for BGP route-target community filtering, all received EBGP VPN-IPv4 routes are discarded when those routes do not contain a route-target community value that matches the import list of any configured VRFs. This is the desired behavior for a router configured as a PE router.
Note
This command is automatically disabled if a PE router is configured as a client of a common VPN-IPv4 route reflector in the autonomous system.
Examples
In the following example, BGP route-target filtering is disabled for autonomous system 120:
Router(config)# router bgp 120
Router(config-router)# no bgp default route-target filter
Related Commands
Command
|
Description
|
show tag-switching forwarding-table
|
Displays the contents of the LFIB.
|
bgp scan-time
To configure scanning intervals of BGP routers for next hop validation or to decrease import processing time of Virtual Private Network version 4 (VPNv4) routing information, use the bgp scan-time command in address family or router configuration mode. To return the scanning interval of a router to its default scanning interval of 15 seconds, use the no form of this command.
bgp scan-time [import] scanner-interval
no bgp scan-time [import] scanner-interval
Syntax Description
import
|
(Optional) Configures import processing of VPNv4 unicast routing information from BGP routers into routing tables.
|
scanner-interval
|
Specifies the scanning interval of BGP routing information. Valid values used for selecting the desired scanning interval are from 5 to 60 seconds. The default is 15 seconds.
|
Defaults
The default scanning interval is 15 seconds.
Command Modes
Address family configuration
Router configuration
Command History
Release
|
Modification
|
12.07(T)
|
This command was introduced.
|
Usage Guidelines
The import keyword is supported in address family VPNv4 unicast mode only.
Entering the no form of this command does not disable scanning, but removes it from the output of the show running-config command.
Examples
In the following router configuration example, the scanning interval for next hop validation of IPv4 unicast routes for BGP routing tables is set to 20 seconds:
In the following address family configuration example, the scanning interval for next hop validation of address family VPNv4 unicast routes for BGP routing tables is set to 45 seconds:
address-family vpn4 unicast
In the following address family configuration example, the scanning interval for importing address family VPNv4 routes into IP routing tables is set to 30 seconds:
address-family vpnv4 unicast
Related Commands
Command
|
Description
|
address-family vpnv4
|
Places the router in address family configuration mode for configuring routing sessions such as BGP, RIP, or static routing sessions that use standard VPNv4 address prefixes.
|
cable bundle
To configure a cable interface to belong to an interface bundle, use the cable bundle interface configuration command. To delete a cable interface bundle definition, use the no form of this command.
cable bundle n [master]
no cable bundle n [master]
Syntax Description
n
|
Specifies the bundle identifier. Valid range is from 1 to 255.
|
master
|
(Optional) Defines the specified interface as the master.
|
Defaults
No default behavior or values.
Command Modes
Interface configuration
Command History
Release
|
Modification
|
12.0(7)XR
|
This command was introduced.
|
Usage Guidelines
You can configure up to four interface bundles. In each bundle, specify one interface as the master interface by using the optional master keyword.
Configure only an IP address on the master interface. If an IP address is configured and the interface is not specified as the master interface, any attempt to add an interface to a bundle is rejected.
Specify all generic IP networking information (such as IP address, routing protocols, and switching modes) on the bundle master interface. Do not specify generic IP networking information on bundle slave interfaces.
If you attempt to add an interface to a bundle as nonmaster interface and an IP address is assigned to this interface, the command will fail. You must remove the IP address configuration before you can add the interface to a bundle.
If you have configured an IP address on a bundled interface and the interface is not the master interface, a warning message appears.
Specify generic (not downstream or upstream related) cable interface configurations, such as source-verify or Address Resolution Protocol (ARP) handling, on the master interface. Do not specify generic configuration on nonmaster interfaces.
If you configure an interface as a part of a bundle and it is not the master interface, all generic cable configuration for this interface is removed. The master interface configuration will then apply to all interfaces in the bundle.
If you shut down or remove the master interface in a bundle, no data packets are sent to any of the interfaces in this bundle. Packets are still physically received from nonmaster interfaces that have not been shut down, but those packets will be discarded. This means that modems connected to those interfaces will not be disconnected immediately, but modems going online will not be able to obtain an IP address, download their configuration file, or renew their IP address assignment if the DHCP lease expires.
If you shut down a slave interface, only this shut down interface is affected.
Examples
The following example configures interface 25 to be the master interface:
Router(config-if)# cable bundle 25 master
07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down
07:28:18: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to up
The following example shows the error message that appears if you try to configure an interface with an IP address that is not the master interface:
Router(config-if)# cable bundle 5
Please remove ip address config first then reenter this command
Related Commands
Command
|
Description
|
show cable bundle
|
Displays the forwarding table for the specified interface bundle.
|
cable helper-address
To specify a destination address for User Datagram Protocol (UDP) broadcast (DHCP) packets, use the cable helper-address interface configuration command.To disable this feature, use the no form of this command.
cable helper-address ip-address {cable-modem | host}
no cable helper-address ip-address {cable-modem | host}
Syntax Description
ip-address
|
The IP address of a DHCP server.
Based on whether you add the host or cable-modem keyword at the end of the cable helper-address command, it is the IP address of the MSOs CNR server or the ISPs DHCP server.
|
cable-modem
|
Specifies that only cable modem UDP broadcasts are forwarded
|
host
|
Specifies that only host UDP broadcasts are forwarded.
|
Defaults
None
Command Modes
Interface configuration
Command History
Release
|
Modification
|
11.3 NA
|
This command was introduced.
|
Usage Guidelines
If you specify a secondary interface address, the giaddr field in the DHCP requests will be sent to the primary address for DHCP requests received from cable modems, and to the secondary IP address for DHCP requests received from hosts.
Examples
The following example forwards UDP broadcasts from cable modems to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 cable-modem
The following example forwards UDP broadcasts from hosts to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 host
cache
To configure aggregation cache operational parameters, use the cache command in aggregation cache configuration mode. To disable the operational parameters, use the no form of this command.
cache {entries number | timeout [active minutes | inactive seconds]}
no cache {entries | timeout {active | inactive }}
Syntax Description
entries number
|
The number of cached entries allowed in the aggregation cache. The number of entries can be 1024 to 524288. The default is 4096.
|
timeout
|
Dissolves the session in the aggregation cache.
|
active minutes
|
(Optional) The number of minutes that an active entry is active. The range is from 1 to 60 minutes. The default is 30 minutes.
|
inactive seconds
|
(Optional) The number of seconds that an inactive entry will stay in the aggregation cache before it times out. The range is from 10 to 600 seconds. The default is 15 seconds.
|
Defaults
The default for cache entries is 4096.
The default for active cache entries is 30 minutes.
The default for inactive cache entries is 15 seconds.
Command Modes
Aggregation cache configuration
Command History
Release
|
Modification
|
12.0(3)T
|
This command was introduced.
|
Examples
The following example shows how to set the aggregation cache entry limits:
cache timeout inactive 199
Related Commands
Command
|
Description
|
default-name
|
Enables an aggregation cache.
|
ip cache-invalidate-delay
|
Enables the exporting of information from NetFlow aggregation caches.
|
ip flow-aggregation cache
|
Enables aggregation cache configuration mode.
|
show ip cache flow aggregation
|
Displays the aggregation cache configuration.
|
show mpoa client
|
Displays the statistics for the data export, including the main cache and all other enabled caches.
|
class (MPLS)
To configure a defined MPLS CoS map that specifies how classes map to label VCs (LVCs) when combined with a prefix map, use the class command in CoS map submode. To disable this option, use the no form of this command.
class class [available standard premium control]
no class class [available standard premium control]
Syntax Description
class
|
The precedence of identified traffic to classify traffic.
|
available
|
(Optional) Means low precedence (In/Out plus lower two bits = 0,4).
|
standard
|
(Optional) Means next precedence (In/Out plus lower two bits = 1,5).
|
premium
|
(Optional) Means high precedence (In/Out plus lower two bits = 2,6).
|
control
|
(Optional) Means highest precedence pair (In/Out plus lower two bits = 3,7). These bits are reserved for control traffic.
|
Defaults
No default behavior or values.
Command Modes
CoS map submode
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Examples
The following commands configure a CoS map:
Related Commands
Command
|
Description
|
access-list
|
Configures the access list mechanism for filtering frames by protocol type or vendor code.
|
show tag-switching cos-map
|
Displays the CoS map used to assign quantity of LVCs and associated CoS of those LVCs.
|
tag-switching cos-map
|
Creates a class map that specifies how classes map to LVCs when combined with a prefix map.
|
tag-switching prefix-map
|
Displays the prefix map used to assign a CoS map to network prefixes matching a standard IP access list.
|
clear adjacency
To clear the Cisco Express Forwarding (CEF) adjacency table, use the clear adjacency command in EXEC mode.
clear adjacency
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced to support the Cisco 12012 Internet router.
|
11.1 CC
|
Multiple platform support was added.
|
Usage Guidelines
When you issue this command, entries in the adjacency table that reside on the Route Processor (RP) are removed and then adjacency sources (such as ARP and Frame Relay) are requested to repopulate the adjacency tables once again. Layer 2 next hop information is reevaluated.
With distributed CEF (dCEF) mode, the adjacency tables that reside on line cards are always synchronized to the adjacency table that resides on the RP. Therefore, clearing the adjacency table on the RP using the clear adjacency command also clears the adjacency tables on the line cards; all changes are propagated to the line cards.
Clearing adjacencies cause the adjacency table to repopulate from the Layer 2 to Layer 3 mapping tables, such as ARP. To cause the mappings to be re-evaluated, the source information must be cleared by using a Cisco IOS command, such as the clear arp-cache command.
Examples
The following example clears the adjacency table:
Related Commands
Command
|
Description
|
clear arp-cache
|
Deletes all dynamic entries from the ARP cache.
|
show adjacency
|
Displays CEF adjacency table information.
|
clear atm vc
To release a specified switched virtual circuit (SVC), use the clear atm vc command in EXEC mode.
clear atm vc vcd
Syntax Description
vcd
|
Virtual channel descriptor of the channel to be released.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Usage Guidelines
For multicast or control VCCs, this command causes the LANE client to exit and rejoin an emulated LAN.
For data VCCs, this command also removes the associated LAN Emulation Address Resolution Protocol (LE ARP) table entries.
Examples
The following example releases SVC 1024:
clear cef interface
To clear the Cisco Express Forwarding (CEF) per-interface traffic policy statistics for an interface, use the clear cef interface policy-statistics command in privileged EXEC mode.
clear cef interface [interface-type interface-number] policy-statistics
Syntax Description
interface-type
|
Type of interface to clear the policy statistics for
|
interface-number
|
Port, connector, or interface card number
|
Defaults
If you do not specify an interface type and interface number the policy statistics for all interfaces are cleared.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(9)S
|
This command was introduced to support the Cisco 12000 series Internet routers.
|
12.0(17)ST
|
This command was introduced to support the Cisco 12000 series Internet routers.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
This command clears the CEF BGP traffic policy statistics counters for an interface.
Examples
The following example clears the CEF BGP traffic policy statistics counters:
R1# clear cef interface ethernet 0/0 policy-statistics
Related Commands
Command
|
Description
|
bgp-policy
|
Enables Border Gateway Protocol (BGP) policy accounting or policy propagation on an interface.
|
show cef interface policy-statistics
|
Displays detailed Cisco Express Forwarding (CEF) policy statistical information for all interfaces.
|
clear cef linecard
To clear Cisco Express Forwarding (CEF) information from line cards, use the clear cef linecard command in EXEC mode.
clear cef linecard [slot-number] [adjacency | interface | prefix]
Syntax Description
slot-number
|
(Optional) Line card slot number to clear. When you omit this argument, all line card slots are cleared.
|
adjacency
|
(Optional) Clears line card adjacency tables and rebuilds adjacency for the specified line card.
|
interface
|
(Optional) Clears line card interface information and recreates the interface information for the specified line card.
|
prefix
|
(Optional) Clears line card prefix tables and starts rebuilding the forwarding information base (FIB) table.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced to support the Cisco 12012 Internet router.
|
11.1 CC
|
Multiple platform support was added.
|
Usage Guidelines
This command is available only on distributed switching platforms running dCEF.
CEF information on the line cards is cleared, however, CEF information on the Route Processor (RP) is not affected.
Once you clear CEF information from line cards, the corresponding information from the RP is propagated to the line cards. Interprocess communications (IPC) ensures that CEF information on the RP matches the CEF information on the line cards.
Examples
The following example clears the CEF information from the line cards:
Related Commands
Command
|
Description
|
show cef linecard
|
Displays CEF-related interface information by line card.
|
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
Release
|
Modification
|
10.0
|
This command was introduced.
|
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:
The 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.0
Related Commands
Command
|
Description
|
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 cef event-log
To clear the Cisco Express Forwarding (CEF) event-log buffer, use the clear ip cef event-log command in EXEC mode.
clear ip cef event-log
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(15)S
|
This command was introduced.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
Usage Guidelines
This command clears the entire CEF table event log that holds forwarding information base (FIB) and adjacency events.
Examples
The following example clears the CEF event-log buffer:
Router# clear ip cef event-log
Related Commands
Command
|
Description
|
IP cef table consistency-check
|
Enables CEF table consistency checker types and parameters.
|
ip cef table event-log
|
Controls CEF table event-log characteristics.
|
show ip cef events
|
Displays all recorded CEF FIB and adjacency events.
|
clear ip cef inconsistency
To clear the Cisco Express Forwarding (CEF) inconsistency statistics and records found by the CEF consistency checkers, use the clear ip cef inconsistency command in EXEC mode.
clear ip cef inconsistency
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(15)S
|
This command was introduced.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
Usage Guidelines
This command clears the CEF inconsistency checker statistics and records that accumulate when the ip cef table consistency-check command is enabled.
Examples
The following example clears all CEF inconsistency checker statistics and records:
Router# clear ip cef inconsistency
Related Commands
Command
|
Description
|
ip cef table consistency-check
|
Enables CEF table consistency checker types and parameters.
|
show ip cef inconsistency
|
Displays CEF IP prefix inconsistencies.
|
clear ip cef prefix-statistics
To clear Cisco Express Forwarding (CEF) counters by resetting the packet and byte count to zero (0), use the clear ip cef prefix-statistics command in EXEC mode.
clear ip cef {network [mask] | *} prefix-statistics
Syntax Description
network
|
Clears counters for a forwarding information base (FIB) entry specified by network.
|
mask
|
(Optional) Clears counters for a FIB entry specified by network and mask.
|
*
|
Clears counters for all FIB entries.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced to support the Cisco 12012 Internet router.
|
11.1 CC
|
Multiple platform support was added.
|
Usage Guidelines
When the clear statistics flag is set, statistics are cleared as the FIB table is scanned. The time period is up to 60 seconds for all statistics to clear. However, clearing a specific prefix is completed immediately.
Examples
The following example resets the packet and byte counts to zero for all CEF entries:
clear ip cef * prefix-statistics
Related Commands
Command
|
Description
|
ip cef accounting
|
Enables CEF network accounting.
|
show adjacency
|
Displays CEF adjacency table information.
|
show ip cef
|
Displays entries or a summary of the FIB table.
|
clear ip flow stats
To clear the NetFlow accounting statistics, use the clear ip flow stats command in privileged EXEC mode.
clear ip flow stats
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1CA
|
This command was introduced.
|
Usage Guidelines
You must have NetFlow accounting configured on your router before you can use this command.
The show ip cache flow command displays the NetFlow accounting statistics. Use the clear ip flow stats command to clear the NetFlow accounting statistics.
Examples
The following example shows how to clear the NetFlow accounting statistics on the router:
Router# clear ip flow stats
Related Commands
Command
|
Description
|
show ip cache flow
|
Displays a summary of the NetFlow accounting statistics.
|
show ip cache verbose flow
|
Displays a detailed summary of the NetFlow accounting statistics.
|
show ip flow interface
|
Displays NetFlow accounting configuration on interfaces.
|
show ip interface
|
Displays the usability status of interfaces configured for IP.
|
clear ip mds
To clear multicast distributed switching (MDS) information from the router, use the clear ip mds command in privileged EXEC mode.
clear ip mds {all | [vrf vrf-name] forwarding}
Syntax Description
all
|
(Optional) Clear all IP MDS information.
|
vrf
|
(Optional) A Virtual Private Network (VPN) routing and forwarding (VRF) instance.
|
vrf-name
|
(Optional) Name assigned to the VRF.
|
forwarding
|
(Optional) Clears all linecard routes from a Multicast Forwarding Information Base (MFIB) table and resynchronizes it with the Route Processor (RP).
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.2(11)GS
|
This command was introduced.
|
Usage Guidelines
Cisco 12000 Series Internet Router
On a Cisco 12000 Series Internet Router the clear ip mds command must be run in privileged EXEC mode on a linecard.
Examples
The following example clears all line card routes in an MFIB table on a Cisco 12000 Series Internet Router:
LC-Slot1# clear ip mds forwarding
The following example clears all line card routes in an MFIB table on a Cisco 7500 Series
Router:
Router# clear ip mds forwarding
Related Commands
Command
|
Description
|
show ip mds interface
|
Displays the MFIB table and forwarding information for MDS on a line card.
|
show ip mds stats
|
Display switching statistics or line card statistics for MDS.
|
show ip mds summary
|
Displays a summary of the MFIB table for MDS.
|
show ip mds forwarding
|
Displays MDS information for all the interfaces on the line card.
|
clear ip mds linecard
To reset multicast distributed switching (MDS) line card information on the router, use the clear ip mds linecard command in privileged EXEC mode.
clear ip mds linecard {linecard-slot-number | *}
Syntax Description
linecard-slot-number
|
Slot number containing the line card to be reset.
|
*
|
Indicates that the reset should be executed on all line cards.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(19.3)S
|
This command was introduced.
|
Usage Guidelines
When the * keyword is specified instead of the linecard-slot-number argument, all MDS information on all line cards is cleared and reset.
Examples
The following example clears and resets all MDS line card information on the router:
Router# clear ip mds linecard *
Related Commands
Command
|
Description
|
show ip mds
|
Clears MDS information from the router.
|
show ip mds interface
|
Displays the MFIB table and forwarding information for MDS on a line card.
|
show ip mds stats
|
Display switching statistics or line card statistics for MDS.
|
show ip mds summary
|
Displays a summary of the MFIB table for MDS.
|
show ip mds forwarding
|
Displays MDS information for all the interfaces on the line card.
|
clear ip mds forwarding
The forwarding keyword for the clear ip mds command is no longer documented as a separate command.
The information for using the forwarding keyword for the clear ip mds command has been incorporated into the clear ip mds command documentation. See the clear ip mds command documentation for more information.
clear ip mroute
To delete entries from the IP multicast routing table, use the clear ip mroute command in EXEC mode.
clear ip mroute {* | group [source]}
Syntax Description
*
|
Deletes all entries from the IP multicast routing table.
|
group
|
Either of the following:
• Name of the multicast group, as defined in the DNS hosts table or with the ip host command.
• IP address of the multicast group. This is a multicast IP address in four-part, dotted notation.
|
source
|
(Optional) If you specify a group name or address, you can also specify a name or address of a multicast source that is sending to the group. A source need not be a member of the group.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
12.0(5) T
|
The effect of this command was modified. If IP multicast Multilayer Switching (MLS) is enabled, using this command now clears both the multicast routing table on the MMLS-RP and all multicast MLS cache entries for all MMLS-SEs that are performing multicast MLS for the MMLS-RP. That is, the original clearing occurs, and the derived hardware switching table is also cleared.
|