-
Cisco IOS Switching Services Command Reference, Release 12.1
-
About the Cisco IOS Software Documentation
-
Using Cisco IOS Software
-
Switching Commands: Introduction
-
Commands: address-family through ip cef
-
Commands: ip cef accounting through lane fssrp
-
Commands: lane global-lecs-address through name elan-id
-
Commands: name local-seg-id through show interface stats
-
Commands: show interface XTagATM through show ip mds summary
-
Commands: show ip mroute through show lane client
-
Commands: show lane config through show mpoa client cache
-
Commands: show mpoa client statistics through show tag-switching tdp bindings
-
Commands: show tag-switching tdp discovery through tunnel tsp-hop
-
Table Of Contents
clear ip cef prefix-statistics
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
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 submode
Command History
Usage Guidelines
Using the address-family command puts you 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, type exit-address-family, or simply exit.
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:
router bgp 100address-family vpnv4The 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.
•
•
Entered the address family submode as follows:
router bgp 100address-family ipv4 unicast vrf vrf2Related Commands
Exits from the address family submode.
Enables the exchange of information with a neighboring router.
append-after
To insert a path entry after a specific index number, use the append-after command in IP explicit path subcommand mode.
append-after index command
Syntax Description
index
Previous index number. Valid range is 0 to 65534.
command
One of the IP explicit path configuration commands that create a path entry. (Currently, only the next-address command can be used.)
Defaults
No default behavior or values.
Command Modes
IP explicit path subcommand
Command History
Examples
The following command inserts the next-address subcommand after the specific index:
append-after 5 next-address 3.3.27.3Related Commands
atm-address
To override the control ATM address of an MPC or MPS, use the atm-address command in interface configuration mode. Use the no form of this command to revert to the default address.
atm-address atm-address
no atm-address
Syntax Description
Defaults
The default is an auto-generated ATM address.
Command Modes
Interface configuration
Command History
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 auto-generated address as its control address.
Examples
The following example specifies the ATM address for an MPC:
atm-address 47.0091810000000061705b7701.00400BFF0011.00The following example specifies the ATM address for an MPS:
atm-address 47.0091810000000061705C2B01.00E034553024.00bgp 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 60 seconds, use the no form of this command.
bgp scan-time [import] scanner-interval
no bgp scan-time [import] scanner-interval
Syntax Description
Defaults
The default scanning interval is 60 seconds.
Command Modes
Address family configuration
Router configuration
Command History
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:
router bgp 100no synchronizationbgp scan-time 20In 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:
router bgp 150address-family vpn4 unicastbgp scan-time 45In the following address family configuration example, the scanning interval for importing address family VPNv4 routes into IP routing tables is set to 30 seconds:
router bgp 150address-family vpnv4 unicastbgp scan-time import 30Related Commands
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 number | timeout [active minutes | inactive seconds]}
Syntax Description
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
Examples
The following example shows how to set the aggregation cache entry limits:
cache entries 2046cache timeout inactive 199Related Commands
class (MPLS)
To configure a defined MPLS CoS map which 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
Defaults
No default behavior or values.
Command Modes
CoS map submode
Command History
Examples
The following commands configure a CoS map:
tag-switching cos-map 55class 1 premiumexitRelated Commands
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
11.2 GS
This command was introduced to support the Cisco 12012 Gigabit Switch Router.
11.1 CC
Multiple platform support was added.
Usage Guidelines
When you issue this command, entries in the adjacency table that resides on the route processor are removed and then repopulated. During repopulation, 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 route processor. Therefore, clearing the adjacency table on the route processor using the clear adjacency command also clears the adjacency tables on the line cards; all changes are propagated to the line cards.
Examples
The following example clears the adjacency table:
clear adjacencyRelated Commands
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
Command Modes
EXEC
Command History
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 LANE Address Resolution Protocol (LE ARP) table entries.
Examples
The following example releases SVC 1024:
clear atm vc 1024clear 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
Command Modes
EXEC
Command History
11.2 GS
This command was introduced to support the Cisco 12012 Gigabit Switch Router.
11.1 CC
Multiple platform support was added.
Usage Guidelines
This command is available only on routers with line cards. This command clears CEF information only on the line cards; CEF information on the route processor is not affected.
Once you clear CEF information from line cards, the corresponding information from the route processor is propagated to the line cards. Inter Process Communication (IPC) ensures that CEF information on the route processor matches the CEF information on the line cards.
Examples
The following example clears the CEF information from the line cards:
clear cef linecardRelated Commands
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 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 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
11.2 GS
This command was introduced to support the Cisco 12012 Gigabit Switch Router.
11.1 CC
Multiple platform support was added.
Examples
The following example resets the CEF packet and byte count to zero:
clear ip cef prefix-statisticsRelated Commands
show adjacency
Displays CEF adjacency table information.
show ip cef
Displays entries in the FIB that are unresolved or displays a FIB summary.
clear ip flow stats
To clear the NetFlow switching statistics, use the clear ip flow stats command in EXEC mode.
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 switching statistics. Use the clear ip flow stats command to clear the NetFlow switching statistics.
Examples
The following example clears the NetFlow switching statistics on the router:
clear ip flow statsRelated Commands
clear ip mds forwarding
To clear all routes from a line card's MFIB table and resynchronize it with the RP, use the clear ip mds forwarding command in EXEC mode.
clear ip mds forwarding
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command on a line card of a Cisco 7500 or Cisco 12000.
Examples
The following example clears the line card's MFIB table:
clear ip mds forwardingRelated Commands
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
Command Modes
EXEC
Command History
Examples
The following example deletes all entries from the IP multicast routing table:
clear ip mroute *The following example deletes from the IP multicast routing table all sources on the 10.3.0.0 subnet that are sending to the multicast group 224.2.205.42. Note that this example deletes all sources on network 10.3, not individual sources.
clear ip mroute 224.2.205.42 10.3.0.0Related Commands
clear ip pim interface count
To clear all line card counts or packet counts, use the clear ip pim interface count command in EXEC mode.
clear ip pim interface count
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command on an RP to delete all multicast distributed switching (MDS) statistics for the entire router.
Examples
The following example clears all the line card packets counts:
clear ip pim interface countRelated Commands
Clears all routes from the MFIB table of a line card and resynchronizes it with the RP.
clear ip route vrf
To remove routes from the VRF routing table, use the clear ip route vrf command in EXEC mode.
clear ip route vrf vrf-name {* | network [mask]}
Syntax Description
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Usage Guidelines
Use this command to clear routes from the routing table. Use the asterisk (*) to delete all routes from the forwarding table for a specified VRF, or enter the address and mask of a particular network to delete the route to that network.
Examples
The following command removes the route to the network 10.13.0.0 in the vpn1 routing table:
clear ip route vrf vpn1 10.13.0.0Related Commands
clear lane le-arp
To clear the dynamic LANE Address Resolution Protocol (LE ARP) table or a single LE ARP entry of the LANE client configured on the specified subinterface or emulated LAN, use the clear lane le-arp command in EXEC mode.
Cisco 7500 series
clear lane le-arp [interface slot/port[.subinterface-number] | name elan-name] [mac-address mac-address | route-desc segment segment-number bridge bridge-number]
Cisco 4500 and 4700 routers
clear lane le-arp [interface number[.subinterface-number] | name elan-name] [mac-address mac-address | route-desc segment segment-number bridge bridge-number]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command removes dynamic LE ARP table entries only. It does not remove static LE ARP table entries.
If you do not specify an interface or an emulated LAN, this command clears all the LE ARP tables of any LANE client in the router.
If you specify a major interface (not a subinterface), this command clears all the LE ARP tables of every LANE client on all the subinterfaces of that interface.
This command also removes the fast-cache entries built from the LE ARP entries.
Examples
The following example clears all the LE ARP tables for all clients on the router:
clear lane le-arpThe following example clears all the LE ARP tables for all LANE clients on all the subinterfaces of interface 1/0:
clear lane le-arp interface 1/0The following example clears the entry corresponding to MAC address 0800.AA00.0101 from the LE ARP table for the LANE client on the emulated LAN red:
clear lane le-arp name red 0800.aa00.0101The following example clears all dynamic entries from the LE ARP table for the LANE client on the emulated LAN red:
clear lane le-arp name redThe following example clears the dynamic entry from the LE ARP table for the LANE client on segment number 1, bridge number 1 in the emulated LAN red:
clear lane le-arp name red route-desc segment 1 bridge 1
Note
clear lane server
To force a LANE server to drop a client and allow the LANE configuration server to assign the client to another emulated LAN, use the clear lane server command in EXEC mode.
Cisco 7500 Series
clear lane server {interface slot/port [.subinterface-number] | name elan-name} [mac-address mac-address | client-atm-address atm-address | lecid lane-client-id | route-desc segment segment-number bridge bridge-number]
Cisco 4500 and 4700 Routers
clear lane server {interface number [.subinterface-number] | name elan-name} [mac-address mac-address | client-atm-address atm-address | lecid lecid | route-desc segment segment-number bridge bridge-number]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
After changing the bindings on the configuration server, use this command on the LANE server to force the client to leave one emulated LAN. The LANE server will drop the Control Direct and Control Distribute VCCs to the LANE client. The client will then ask the LANE configuration server for the location of the LANE server of the emulated LAN it should join.
If no LANE client is specified, all LANE clients attached to the LANE server are dropped.
Examples
The following example forces all the LANE clients on the emulated LAN red to be dropped. The next time they try to join, they will be forced to join a different emulated LAN.
clear lane server name redRelated Commands
clear mpoa client cache
To clear the ingress and egress cache entries of one or all MPCs, use the clear mpoa client cache command in EXEC mode.
clear mpoa client [name mpc-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Defaults
The system defaults are:
•
•
•
Command Modes
EXEC
Command History
Examples
The following example clears the ingress and egress cache entries for the MPC named ip_mpc:
clear mpoa client name ip_mpc cacheRelated Commands
Displays the ingress or egress cache entries matching the IP addresses for the MPCs.
clear mpoa server cache
To clear the ingress and egress cache entries, use the clear mpoa server cache command in EXEC mode.
clear mpoa server [name mps-name] cache [ingress | egress] [ip-address ip-address]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
This command clears cache entries.
Examples
The following example clears all cache entries:
clear mpoa server cacheRelated Commands
show mpoa server cache
Displays ingress and egress cache entries associated with a server.
clear vlan
To delete an existing virtual LAN (VLAN) from a management domain, use the clear vlan command in privileged EXEC mode.
clear vlan vlan
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Follow these guidelines for deleting VLANs:
•
•
•
Caution
Examples
The following example shows how to clear an existing VLAN (VLAN 4) from a management domain:
Router# clear vlan 4 This command will deactivate all ports on vlan 4 in the entire management domain Do you want to continue(y/n) [n]? y VLAN 4 deletedRelated Commands
clear vlan mapping
To delete existing 802.1Q virtual LAN (VLAN) to Inter-Switch Link (ISL) VLAN-mapped pairs, use the clear vlan mapping command in privileged EXEC mode.
clear vlan mapping dot1q {1q-vlan | all}
Syntax Description
dot1q
Specifies the 802.1Q VLAN.
1q-vlan
Number of the 802.1Q VLAN for which to remove the mapping.
all
Clears the mapping table of all entries.
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to clear an existing mapped 802.1Q VLAN (VLAN 1044) from the
mapping table:Router# clear vlan mapping dot1q 1044Vlan Mapping 1044 Deleted.The following example shows how to clear all mapped 802.1Q VLANs from the mapping table:
Router# clear vlan mapping dot1q allAll Vlan Mapping Deleted.Related Commands
set vlan mapping
Maps 802.1Q VLANs to ISL VLANs.
show vlan mapping
Displays VLAN mapping table information.
client-atm-address name
To add a LANE client address entry to the configuration server's configuration database, use the client-atm-address command in database configuration mode. To remove a client address entry from the table, use the no form of this command.
client-atm-address atm-address-template name elan-name
no client-atm-address atm-address-template
Syntax Description
Defaults
No address and no emulated LAN name are provided.
Command Modes
Database configuration
Command History
Usage Guidelines
The effect of this command is to bind any client whose address matches the specified template into the specified emulated LAN. When a client comes up, it consults the LANE configuration server, which responds with the ATM address of the LANE server for the emulated LAN. The client then initiates join procedures with the LANE server.
Before this command is used, the emulated LAN specified by the elan-name argument must have been created in the configuration server's database by use of the name server-atm-address command.
If an existing entry in the configuration server's database binds the LANE client ATM address to a different emulated LAN, the new command is rejected.
This command affects only the bindings in the named configuration server database. It has no effect on the LANE components themselves.
See the lane database command for information about creating the database, and the name server-atm-address command for information about binding the emulated LAN's name to the server's ATM address.
The client-atm-address name command is a subcommand of the global lane database command.
ATM Addresses
A LANE ATM address has the same syntax as a network service access point (NSAP), but it is not a network-level address. It consists of the following:
•
–
•
•
Address Templates
LANE ATM address templates can use two types of wildcards: an asterisk (*) to match any single character (nibble), and an ellipsis (...) to match any number of leading, middle, or trailing characters. The values of the characters replaced by wildcards come from the automatically assigned ATM address.
In LANE, a prefix template explicitly matches the prefix but uses wildcards for the ESI and selector fields. An ESI template explicitly matches the ESI field but uses wildcards for the prefix and selector.
In our implementation of LANE, the prefix corresponds to the switch, the ESI corresponds to the ATM interface, and the selector field corresponds to the specific subinterface of the interface.
Examples
The following example uses an ESI template to specify the part of the ATM address corresponding to the interface. This example allows any client on any subinterface of the interface that corresponds to the displayed ESI value, no matter to which switch the router is connected, to join the engineering emulated LAN:
client-atm-address ...0800.200C.1001.** name engineeringThe following example uses a prefix template to specify the part of the ATM address corresponding to the switch. This example allows any client on a subinterface of any interface connected to the switch that corresponds to the displayed prefix to join the marketing emulated LAN:
client-atm-address 47.000014155551212f.00.00... name marketingRelated Commands
default
To enable a default aggregation cache, use the default command in aggregation cache configuration mode.
default [cache | enabled | export]
Syntax Description
cache
(Optional) Configure NetFlow cache parameters.
enabled
(Optional) Enable the aggregation cache.
export
(Optional) Specify host/port to send flow statistics.
Defaults
No default behavior or values.
Command Modes
Aggregation cache configuration
Command History
Examples
The following example shows how to use the default command:
ip flow-aggregation cache asdefault enabledRelated Commands
default-name
To provide an emulated LAN name in the configuration server's database for those client MAC addresses and client ATM addresses that do not have explicit emulated LAN name bindings, use the default-name command in database configuration mode. To remove the default name, use the no form of this command.
default-name elan-name
no default-name
Syntax Description
elan-name
Default emulated LAN name for any LANE client MAC address or LANE client ATM address not explicitly bound to any emulated LAN name. Maximum length is 32 characters.
Defaults
No name is provided.
Command Modes
Database configuration
Command History
Usage Guidelines
This command affects only the bindings in the configuration server's database. It has no effect on the LANE components themselves.
The named emulated LAN must already exist in the configuration server's database before this command is used. If the default name-to-emulated LAN name binding already exists, the new binding replaces it.
The default-name command is a subcommand of the global lane database command.
Examples
The following example specifies the emulated Token Ring LAN man as the default emulated LAN. Because none of the emulated LANs are restricted, clients are assigned to whichever emulated LAN they request. Clients that do not request a particular emulated LAN will be assigned to the man emulated LAN.
lane database example2name eng server-atm-address 39.000001415555121101020304.0800.200c.1001.02name eng local-seg-id 1000name man server-atm-address 39.000001415555121101020304.0800.200c.1001.01name man local-seg-id 2000name mkt server-atm-address 39.000001415555121101020304.0800.200c.4001.01name mkt local-seg-id 3000default-name manRelated Commands
enabled
To enable an aggregation cache, use the enabled command in aggregation cache configuration mode.
enabled
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Aggregation cache configuration
Command History
Examples
The following example shows how to use the enabled command:
enabledRelated Commands
encapsulation dot1q
To enable IEEE 802.1Q encapsulation of traffic on a specified subinterface in virtual LANs, use the encapsulation dot1q command in subinterface configuration mode. IEEE 802.1Q is a standard protocol for interconnecting multiple switches and routers and for defining VLAN topologies.
encapsulation dot1q vlan-id
Syntax Description
Defaults
Disabled
Command Modes
Subinterface configuration
Command History
Usage Guidelines
IEEE 802.1Q encapsulation is configurable on Fast Ethernet interfaces.
Examples
The following example encapsulates VLAN traffic using the IEEE 802.1Q protocol for VLAN 100:
interface fastethernet 4/1.100encapsulation dot1q 100Related Commands
encapsulation isl
To enable the Inter-Switch Link (ISL), use the encapsulation isl command in subinterface configuration mode. 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
To enable IEEE 802.10 encapsulation of traffic on a specified subinterface in virtual LANs, use the encapsulation sde command in subinterface configuration mode. 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
To enable TRISL, use the encapsulation tr-isl command in subinterface configuration mode. TRISL is 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 bridge-number
Keyword that specifies the identification number of the bridge number on the ISL trunk. Possible values are from 1 to 4095.
Defaults
Disabled.
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
exit
To leave aggregation cache mode, use the exit command in aggregation cache configuration mode.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Aggregation cache configuration
Command History
Examples
The following example shows how to use the exit command:
exitRelated Commands
exit-address-family
To exit from the address family submode, use the exit-address-family command in address family submode.
exit-address-family
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Address family submode
Command History
Usage Guidelines
This command can be abbreviated to exit.
Examples
The following example shows how to exit the address-family command mode:
(config-router-af)# exit-address-familyRelated Commands
Enters the address family submode for configuring routing protocols, such as BGP, RIP, and static routing.
export destination
To enable the exporting of information from NetFlow aggregation caches, use the export destination command in aggregation cache configuration mode.
To disable the exporting of NetFlow aggregation cache information, use the no form of this command.
export destination ip-address port
no export destination ip-address port
Syntax Description
Defaults
An export destination is not set.
Command Modes
Aggregation cache configuration
Command History
Usage Guidelines
For version 8 data exports, the maximum number of aggregated flow records and the maximum size in bytes of each UDP datagram are as follows:
Examples
The following example shows how to configure an export destination for an aggregation cache:
export destination 10.41.41.1 9992Related Commands
export map
To configure an export route map for a Virtual Private Network (VPN) routing/forwarding instance (VRF), use the export map command in VRF configuration submode. To remove an export route map, use the no form of this command.
export map route-map
no export map route-map
Syntax Description
Defaults
This command has no default behavior or values. A VRF has no export map unless one is configured using the export map command.
Command Modes
VRF configuration submode
Command History
Usage Guidelines
Use an export route map when an application requires finer control over the routes exported by a VRF than provided by the import and export extended communities configured for the importing and exporting VRF.
The export map command associates a route map with the specified VRF. You can use a route map to filter target routes for a target VPN export by a VRF, based on the route target extended community attributes of the route. The route map might deny export to selected routes from a community on the export list.
An export map command with a set extcommunity rt command takes precedence over configured route targets (RTs), unless the additive keyword is specified. If the export map has a set community rt1 rt2 additive command, the previous RT list is kept and rt1 and rt2 are added to the RT list.
Examples
The following example shows how to configure an export map for VRF vpn1:
Router(config)# ip vrf vpn1Router(config-vrf)# export map export1Related Commands
extended-port
To associate the currently selected extended label ATM (XTagATM) interface with a particular external interface on the remotely controlled ATM switch, use the extended-port command in interface configuration mode.
extended-port ctrl-if {bpx bpx-port-number | descriptor vsi-descriptor | vsi vsi-port-number}
Syntax Description
Defaults
None
Command Modes
Interface configuration
Command History
Usage Guidelines
The extended-port interface configuration command associates an XTagATM interface with a particular external interface on the remotely controlled ATM switch. The three alternate forms of the command permit the external interface on the controlled ATM switch to be specified in three different ways.
Examples
The following example shows you how to create an extended label ATM interface and bind it to the BPX port 2.3.
interface XTagATM0extended-port atm0/0 bpx 2.3Related Commands
interface XTagATM
Enters interface configuration mode for the extended MPLS ATM (XTagATM) interface.
holding-time
To specify the holding time value for the MPS-p7 variable of an MPS, use the holding-time command in MPS configuration mode. To revert to the default value, use the no form of this command.
holding-time time
no holding-time time
Syntax Description
Defaults
The default holding time is 1200 seconds (20 minutes).
Command Modes
MPS configuration
Command History
Examples
The following example sets the holding time to 600 seconds (10 minutes):
holding-time 600import map
To configure an import route map for a VRF, use the import map command in VRF submode.
import map route-map
Syntax Description
Defaults
There is no default. A VRF has no import route map unless one is configured using the import map command.
Command Modes
VRF submode
Command History
Usage Guidelines
Use an import route map when an application requires finer control over the routes imported into a VRF than provided by the import and export extended communities configured for the importing and exporting VRF.
The import map command associates a route map with the specified VRF. You can filter routes that are eligible for import into a VRF, based on the route target extended community attributes of the route, through the use of a route map. The route map might deny access to selected routes from a community that is on the import list.
The import map command does not replace the need for a route-target import in the VRF configuration. You use the import map command to further filter prefixes that match a route-target import statement in that VRF.
Examples
The following example shows how to configure an import route map for a VRF:
ip vrf vrf_blueimport map blue_import_mapRelated Commands
index
To insert or modify a path entry at a specific index, use the index command in IP explicit path subcommand mode.
index index command
Syntax Description
Defaults
No default behavior or values.
Command Modes
IP explicit path subcommand
Command History
Examples
The following command specifies where the next-address command should be inserted in the list:
index 6 next-address 3.3.29.3Explicit Path identifier 6:6: next-address 3.3.29.3Related Commands
interface XTagATM
To enter interface configuration mode for the extended label ATM (XTagATM) interface, use the interface XTagATM command in global configuration mode. The interface is created the first time this command is issued for a particular interface number.
interface XTagATM if-num
Syntax Description
Defaults
None
Command Modes
Global configuration
Command History
Usage Guidelines
Extended label ATM interfaces are virtual interfaces that are created on first reference like tunnel interfaces. They are similar to ATM interfaces except that they only support TC-ATM encapsulation.
Examples
The following example shows you how to create the extended label ATM interface with the interface number 62:
interface XTagATM62Related Commands
extended-port
Associates the currently selected extended MPLS ATM (XTagATM) interface with a particular external interface on the remotely controlled ATM switch.
ip cache-invalidate-delay
To control the invalidation rate of the IP route cache, use the ip cache-invalidate-delay command in global configuration mode. 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 cef
To enable Cisco Express Forwarding (CEF) on the route processor card, use the ip cef command in global configuration mode. To disable CEF, use the no form of this command.
ip cef [distributed]
no ip cef [distributed]
Syntax Description
distributed
(Optional) Enables distributed CEF (dCEF) operation. Distributes CEF information to line cards. Line cards perform express forwarding.
Defaults
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not available on the Cisco 12000 series GSR because that router series operates only in distributed CEF mode.
CEF is advanced Layer 3 IP switching technology. CEF optimizes network performance and scalability for networks with dynamic, topologically dispersed traffic patterns, such as those associated with Web-based applications and interactive sessions.
If you enable CEF and then create an access list that uses the log keyword, the packets that match the access list are not CEF switched. They are fast switched. Logging disables CEF.
Examples
The following example enables standard CEF operation:
ip cefThe following example enables dCEF operation:
ip cef distributedRelated Commands
