Table Of Contents
name local-seg-id
name preempt
name server-atm-address
neighbor activate
neighbor allowas-in
neighbor as-override
neighbor send-label
network-id
next-address
oam-ac emulation-enable
rd
route-target
set mpls experimental
set mpls experimental imposition
set mpls experimental topmost
set mpls-label
set ospf router-id
set port flowcontrol
set vlan
set vlan mapping
shortcut-frame-count
shortcut-frame-time
show adjacency
show cable bundle
show cef
show cef interface
show cef interface policy-statistics
show cef linecard
show controllers vsi control-interface
show controllers vsi descriptor
show controllers vsi session
show controllers vsi status
show controllers vsi traffic
show controllers xmplsatm
show controllers XTagATM
show interface stats
name local-seg-id
To specify or replace the ring number of the emulated LAN (ELAN) in the configuration server's configuration database, use the name local-seg-id command in database configuration mode. To remove the ring number from the database, use the no form of this command.
name elan-name local-seg-id segment-number
no name elan-name local-seg-id segment-number
Syntax Description
elan-name
|
Name of the ELAN. The maximum length of the name is 32 characters.
|
segment-number
|
Segment number to be assigned to the ELAN. The number ranges from 1 to 4095.
|
Defaults
No ELAN name or segment number is provided.
Command Modes
Database configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
This command is ordinarily used for Token Ring LANE.
The same LANE ring number cannot be assigned to more than one ELAN.
The no form of this command deletes the relationships.
Examples
The following example specifies a ring number of 1024 for the ELAN named red:
name red local-seg-id 1024
Related Commands
Command
|
Description
|
default-name
|
Provides an ELAN name in the database of the configuration server for those client MAC addresses and client ATM addresses that do not have explicit ELAN name bindings.
|
lane database
|
Creates a named configuration database that can be associated with a configuration server.
|
mac-address
|
Sets the MAC-layer address of the Cisco Token Ring.
|
name preempt
To set the emulated LAN (ELAN) preempt, use the name preempt command in LANE database configuration mode. To disable preemption, use the no form of this command.
name elan-name preempt
no name elan-name preempt
Syntax Description
elan-name
|
Specifies the name of the ELAN.
|
Defaults
Preemption is off by default.
Command Modes
LANE database configuration
Command History
Release
|
Modification
|
11.3
|
This command was introduced.
|
Usage Guidelines
In prior releases, when the primary LES failed, the Cisco SSRP protocol switched over to a secondary LES. But when a LES that is ranked higher in the list came back up, the SSRP protocol switched the active LES to the new LES, which had a higher priority. This forced the network to flap multiple times. We have prevented the network flapping by staying with the currently active master LES regardless of the priority. If a higher priority LES comes back online, SSRP will not switch to that LES.
LES preemption is off by default. The first LES that comes on becomes the master. Users can revert to the old behavior (of switching to the higher-priority LES all the time) by specifying the name elan-name preempt command in the LECS database.
Examples
The following example sets the ELAN preempt for the ELAN named MYELAN:
name server-atm-address
To specify or replace the ATM address of the LANE server for the emulated LAN (ELAN) in the configuration server's configuration database, use the name server-atm-address command in database configuration mode. To remove it from the database, use the no form of this command.
name elan-name server-atm-address atm-address [restricted | un-restricted] [index number]
no name elan-name server-atm-address atm-address [restricted | un-restricted] [index number]
Syntax Description
elan-name
|
Name of the ELAN. Maximum length is 32 characters.
|
atm-address
|
LANE server's ATM address.
|
restricted | un-restricted
|
(Optional) Membership in the named ELAN is restricted to the LANE clients explicitly defined to the ELAN in the configuration server's database.
|
index number
|
(Optional) Priority number. When specifying multiple LANE servers for fault tolerance, you can specify a priority for each server. 0 is the highest priority.
|
Defaults
No emulated LAN name or server ATM address is provided.
Command Modes
Database configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
11.2
|
The following keywords were added:
• un-restricted
• index
|
Usage Guidelines
ELAN names must be unique within one named LANE configuration database.
Specifying an existing ELAN name with a new LANE server ATM address adds the LANE server ATM address for that ELAN for redundant server operation or simple LANE service replication. This command can be used multiple times.
The no form of this command deletes the relationships.
Examples
The following example configures the example3 database with two restricted and one unrestricted ELANs. The clients that can be assigned to the eng and mkt ELANs are specified using the client-atm-address commands. All other clients are assigned to the man ELAN.
name eng server-atm-address 39.000001415555121101020304.0800.200c.1001.02 restricted
name man server-atm-address 39.000001415555121101020304.0800.200c.1001.01
name mkt server-atm-address 39.000001415555121101020304.0800.200c.4001.01 restricted
client-atm-address 39.000001415555121101020304.0800.200c.1000.02 name eng
client-atm-address 39.0000001415555121101020304.0800.200c.2000.02 name eng
client-atm-address 39.000001415555121101020304.0800.200c.3000.02 name mkt
client-atm-address 39.000001415555121101020304.0800.200c.4000.01 name mkt
Related Commands
Command
|
Description
|
client-atm-address name
|
Adds a LANE client address entry to the configuration database of the configuration server.
|
default-name
|
Provides an ELAN name in the database of the configuration server for those client MAC addresses and client ATM addresses that do not have explicit ELAN name bindings.
|
lane database
|
Creates a named configuration database that can be associated with a configuration server.
|
mac-address
|
Sets the MAC-layer address of the Cisco Token Ring.
|
neighbor activate
To enable the exchange of information with a Border Gateway Protocol (BGP) neighbor, use the neighbor activate command in address family configuration mode or router configuration mode. To disable the exchange of an address with a BGP neighbor, use the no form of this command.
neighbor {ip-address | peer-group-name | ipv6-address} activate
no neighbor {ip-address | peer-group-name | ipv6-address} activate
Syntax Description
ip-address
|
IP address of the neighboring router.
|
peer-group-name
|
Name of BGP peer group.
|
ipv6-address
|
IPv6 address of the BGP neighbor.
This argument must be in the form documented in RFC 2373 where the address is specified in hexadecimal using 16-bit values between colons.
|
Defaults
The exchange of addresses with BGP neighbors is enabled for the IPv4 address family. Enabling address exchange for all other address families is disabled.
Note
Address exchange for address family IPv4 is enabled by default for each BGP routing session configured with the neighbor remote-as command unless you configure the no bgp default ipv4-activate command before configuring the neighbor remote-as command, or you disable address exchange for address family IPv4 with a specific neighbor by using the no form of the neighbor activate command.
Command Modes
Address family configuration
Router configuration
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
12.0(5)T
|
Support for address family configuration mode and the IPv4 address family were added.
|
12.2(2)T
|
The ipv6-address argument and support for the IPv6 address family were added.
|
12.0(21)ST
|
This command was integrated into Cisco IOS Release 12.0(21)ST.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Usage Guidelines
Use this command to advertise address information in the form of an IP or IPv6 prefix. The address prefix information is known as Network Layer Reachability Information (NLRI) in BGP.
Examples
The following example shows how to enable address exchange for address family vpnv4 for all neighbors in the BGP peer group named PEPEER and for the neighbor 144.0.0.44:
Router(config)# address-family vpnv4
Router(config-router-af)# neighbor PEPEER activate
Router(config-router-af)# neighbor 144.0.0.44 activate
Router(config-router-af)# exit-address-family
The following example shows how to enable address exchange for address family IPv4 unicast for all neighbors in the BGP peer group named group1 and for the BGP neighbor 172.16.1.1:
Router(config)# address-family ipv4 unicast
Router(config-router-af)# neighbor group1 activate
Router(config-router-af)# neighbor 172.16.1.1 activate
The following example shows how to enable address exchange for address family IPv6 for all neighbors in the BGP peer group named group2 and for the BGP neighbor 7000::2:
Router(config)# address-family ipv6
Router(config-router-af)# neighbor group2 activate
Router(config-router-af)# neighbor 7000::2 activate
Related Commands
Command
|
Description
|
address-family ipv4
|
Places the router in address family configuration mode for configuring routing sessions, such as BGP, that use standard IPv4 address prefixes.
|
address-family ipv6
|
Places the router in address family configuration mode for configuring routing sessions, such as BGP, that use standard IPv6 address prefixes.
|
address-family vpnv4
|
Places the router in address family configuration mode for configuring routing sessions, such as BGP, that use standard VPNv4 address prefixes.
|
exit-address-family
|
Exits from the address family submode.
|
neighbor allowas-in
To configure PE routers to allow readvertisement of all prefixes containing duplicate ASNs, use the neighbor allowas-in command in router configuration mode. To disable the readvertisement of a PE router's ASN, use the no form of this command.
neighbor allowas-in number
no neighbor allowas-in number
Syntax Description
number
|
Specifies the number of times to allow the advertisement of a PE router's ASN. Valid values are from 1 to 10 times.
|
Defaults
No default behavior or values.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
Usage Guidelines
In a hub and spoke configuration, a PE router readvertises all prefixes containing duplicate autonomous system numbers. Use the neighbor allowas-in command to configure two VRFs on each PE router to receive and readvertise prefixes are as follows:
•
One VRF receives prefixes with ASNs from all PE routers and then advertises them to neighboring PE routers.
•
The other VRF receives prefixes with ASNs from the CE router and readvertises them to all PE routers in the hub and spoke configuration.
You control the number of times an ASN is advertised by specifying a number from 1 to 10.
Examples
In the following example, the PE router with ASN 100 is configured to allow prefixes from the VRF address family VPN IPv4 vrf1. The neighboring PE router with the IP address 192.168.255.255 is set to be readvertised to other PE routers with the same ASN six times.
address-family ipv4 vrf vrf1
neighbor 192.168.255.255 allowas-in 6
Related Commands
Command
|
Description
|
address-family
|
Enters the address family configuration submode used to configure routing protocols such as BGP, OSPF, RIP, and static routing.
|
neighbor as-override
To configure a PE router to override the ASN of a site with the ASN of a provider, use the neighbor as-override command in router configuration mode. To remove VPN IPv4 prefixes from a specified router, use the no form of this command.
neighbor ip-address as-override
no neighbor ip-address as-override
Syntax Description
ip-address
|
Specifies the IP address of the router that is to be overridden with the ASN provided.
|
Defaults
No default behavior or values.
Command Modes
Router configuration
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
Usage Guidelines
This command is used in conjunction with the site-of-origin feature, identifying the site where a route originated, and preventing routing loops between routers within a VPN.
Examples
In the following example, the router's ASN of 100 overrides the neighboring routers' IP address 192.168.255.255:
neighbor 192.168.255.255 remote-as 100
neighbor 192.168.255.255 update-source loopback0
address-family ipv4 vrf vpn1
neighbor 192.168.255.255 activate
neighbor 192.168.255.255 as-override
Related Commands
Command
|
Description
|
neighbor activate
|
Enables the exchange of information with a BGP neighboring router.
|
neighbor remote-as
|
Allows a neighboring router's IP address to be included in the BGP routing table.
|
neighbor update-source
|
Allows internal BGP sessions to use any operational interface for TCP/IP connections.
|
route-map
|
Redistributes routes from one routing protocol to another.
|
neighbor send-label
To enable a Border Gateway Protocol (BGP) router to send Multiprotocol Label Switching (MPLS) labels with BGP routes to a neighboring BGP router, use the neighbor send-label command in address family configuration mode or router configuration mode. To disable this feature, use the no form of this command.
neighbor ip-address send-label
no neighbor ip-address send-label
Syntax Description
ip-address
|
IP address of the neighboring router.
|
Defaults
By default, BGP routers distribute only BGP routes.
Command Modes
Address family configuration
Router configuration
Command History
Release
|
Modification
|
12.0(21)ST
|
This command was introduced.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Usage Guidelines
This command enables a router to use BGP to distribute MPLS labels along with the IPv4 routes to a peer router. You must issue this command on both the local router and the neighboring router.
This command has the following restrictions:
•
If a BGP session is running when you issue the neighbor send-label command, the command does not take effect until the BGP session is restarted.
•
In router configuration mode, only IPv4 addresses are distributed.
Use this command in IPv6 address family configuration mode to bind and advertise IPv6 prefix MPLS labels. Using this command in conjunction with the mpls ipv6 source-interface global configuration command allows IPv6 traffic to run over an IPv4 MPLS network without any software or hardware configuration changes in the backbone. Edge routers configured to run both IPv4 and IPv6 forward IPv6 traffic using MPLS and multiprotocol internal BGP (MP-iBGP).
Examples
The following example shows how to enable a router in the autonomous system 65000 to send MPLS labels with BGP routes to the neighbor BGP router at 192.168.0.1:
Router(config)# router bgp 65000
Router(config-router)# neighbor 192.168.0.1 remote-as 65001
Router(config-router)# neighbor 192.168.0.1 send-label
The following example shows how to enable a router in the autonomous system 65000 to bind and advertise IPv6 prefix MPLS labels and send the labels with BGP routes to the neighbor BGP router at 192.168.99.70:
Router(config)# router bgp 65000
Router(config-router)# neighbor 192.168.99.70 remote-as 65000
Router(config-router)# address-family ipv6
Router(config-router-af)# neighbor 192.168.99.70 activate
Router(config-router-af)# neighbor 192.168.99.70 send-label
Related Commands
Command
|
Description
|
neighbor activate
|
Enables the exchange of information with a neighboring router.
|
mpls ipv6 source-interface
|
Specifies the IPv6 address of an interface to be used as the source address for locally generated IPv6 packets to be sent over a network running MPLS.
|
network-id
To specify the network ID of an MPS, use the network-id command in MPS configuration mode. To revert to the default value (default value is 1), use the no form of this command.
network-id id
no network-id
Syntax Description
id
|
Specifies the network ID of the MPOA server.
|
Defaults
The default value for the network id is 1.
Command Modes
MPS configuration
Command History
Release
|
Modification
|
11.3(3a)WA4(5)
|
This command was introduced.
|
Usage Guidelines
Specifies the network ID of this MPS. This value is used in a very similar way the NHRP network ID is used. It is for partitioning NBMA clouds artificially by administration.
Examples
The following example sets the network ID to 5:
next-address
To specify the next IP address in the explicit path, use the next-address command in IP explicit path configuration mode. To disable this feature, use the no form of this command.
next-address A.B.C.D
no next-address A.B.C.D
Syntax Description
A.B.C.D
|
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 number 60 is assigned to the IP explicit path, the path is enabled, and 3.3.27.3 is specified as the next IP address in the list of IP addresses:
Router(config)# ip explicit-path identifier 60 enable
Router(cfg-ip-expl-path)# next-address 3.3.27.3
Explicit Path identifier 60:
Router(cfg-ip-exp1-path)#
Related Commands
Command
|
Description
|
append-after
|
Inserts the new path entry after the specified index number. Commands might be renumbered as a result.
|
index
|
Inserts or modifies a path entry at a specified index.
|
ip explicit-path
|
Enters the subcommand mode for IP explicit paths and creates or modifies the specified path.
|
list
|
Displays all or part of the explicit paths.
|
show ip explicit-paths
|
Displays configured IP explicit paths.
|
oam-ac emulation-enable
To enable Operation, Administration, and Maintenance (OAM) cell emulation on ATM adaptation layer 5 (AAL5) over Multiprotocol Label Switching (MPLS), use the oam-ac emulation-enable command in the ATM VC configuration mode on both provider edge (PE) routers. To disable OAM cell emulation, use the no form of this command on both routers.
oam-ac emulation-enable [ais-rate]
no oam-ac emulation-enable [ais-rate]
Syntax Description
ais-rate
|
(Optional) The rate (in seconds) at which the alarm indication signal (AIS) cells should be sent. The range is 0 to 60 seconds. If you specify 0, no AIS cells are sent. The default is 1 second, which means that one AIS cell is sent every second.
|
Defaults
By default OAM cell emulation is disabled. If you enable OAM cell emulation without specifying an AIS rate, the default is to send one AIS cell every second.
Command Modes
ATM VC configuration mode
Command History
Release
|
Modification
|
12.0(23)S
|
This command was introduced.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
12.2(15)T
|
This command was integrated into Cisco IOS Release 12.2(15)T.
|
Usage Guidelines
This command is only applicable to AAL5 over MPLS and is not supported with ATM Cell Relay over MPLS.
This command is only available when you specify the pvc vpi/vci l2transport command.
Examples
The following example shows how to enable OAM cell emulation on an ATM PVC:
Router# interface ATM 1/0/0
Router(config-if)# pvc 1/200 l2transport
Router(config-atm-vc)# oam-ac emulation-enable
The following example sets the rate at which an AIS cell is sent to every 30 seconds:
Router (config-atm-vc)# oam-ac emulation-enable 30
Related Commands
Command
|
Description
|
show atm pvc
|
Displays all ATM PVCs and traffic information.
|
rd
To create routing and forwarding tables for a VRF, use the rd command in VRF configuration mode.
rd route-distinguisher
Syntax Description
route-distinguisher
|
Adds an 8-byte value to an IPv4 prefix to create a VPN IPv4 prefix.
|
Defaults
There is no default. A route distinguisher (RD) must be configured for a VRF to be functional.
Command Modes
VRF configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
A RD creates routing and forwarding tables and specifies the default route distinguisher for a VPN. The RD is added to the beginning of the customer's IPv4 prefixes to change them into globally unique VPN-IPv4 prefixes.
Either RD is an ASN-relative RD, in which case it is composed of an autonomous system number and an arbitrary number, or it is an IP-address-relative RD, in which case it is composed of an IP address and an arbitrary number.
You can enter an RD in either of these formats:
16-bit AS number: your 32-bit number
For example, 101:3.
32-bit IP address: your 16-bit number
For example, 192.168.122.15:1.
Examples
The following example configures a default RD for two VRFs. It illustrates the use of both AS-relative and IP-address-relative RDs:
Related Commands
Command
|
Description
|
ip vrf
|
Configures a VRF routing table.
|
show ip vrf
|
Displays the set of defined VRFs and associated interfaces.
|
route-target
To create a route-target extended community for a VRF, use the route-target command in VRF configuration mode. To disable the configuration of a route-target community option, use the no form of this command.
route-target {import | export | both} route-target-ext-community
no route-target {import | export | both} route-target-ext-community
Syntax Description
import
|
Imports routing information from the target VPN extended community.
|
export
|
Exports routing information to the target VPN extended community.
|
both
|
Imports both import and export routing information to the target VPN extended community.
|
route-target-ext-community
|
Adds the route-target extended community attributes to the VRF's list of import, export, or both (import and export) route-target extended communities.
|
Defaults
There are no defaults. A VRF has no route-target extended community attributes associated with it until specified by the route-target command.
Command Modes
VRF configuration
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
The route-target command creates lists of import and export route-target extended communities for the specified VRF. Enter the command one time for each target community. Learned routes that carry a specific route-target extended community are imported into all VRFs configured with that extended community as an import route target. Routes learned from a VRF site (for example, by BGP, RIP, or static route configuration) contain export route targets for extended communities configured for the VRF added as route attributes to control the VRFs into which the route is imported.
The route target specifies a target VPN extended community. Like a route-distinguisher, an extended community is composed of either an autonomous system number and an arbitrary number or an IP address and an arbitrary number. You can enter the numbers in either of these formats:
16-bit AS number:your 32-bit number
For example, 101:3.
32-bit IP address:your 16-bit number
For example, 192.168.122.15: 1.
Examples
The following example shows how to configure route-target extended community attributes for a VRF. The result of the command sequence is that VRF named vrf_blue has two export extended communities (1000:1 and 1000:2) and two import extended communities (1000:1 and 173.27.0.130:200).
route-target export 1000:2
route-target import 173.27.0.130:200
Related Commands
Command
|
Description
|
ip vrf
|
Configures a VRF routing table.
|
import map
|
Configures an import route map for a VRF.
|
set mpls experimental
Note
Effective with release 12.2(13)T, the set mpls experimental command is replaced by the set mpls experimental imposition command. See the set mpls experimental imposition command for more information.
To configure a policy to set the Multiprotocol Label Switching (MPLS) experimental field within the modular quality of service (QoS) CLI, use the set mpls experimental command in policy map configuration mode. To disable the policy map, use the no form of this command.
set mpls experimental value
no set mpls experimental value
Syntax Description
value
|
Specifies the value used to set MPLS experimental field bits defined by the policy map. Valid values are 0 to 7; these values can be space-delimited (for example, 3 4 7).
|
Defaults
No policy map is enabled.
Command Modes
Policy map configuration
Command History
Release
|
Modification
|
12.1(5)T
|
This command was introduced.
|
12.2(2)T
|
This command was integrated into Cisco IOS Release 12.2(2)T.
|
12.2(13)T
|
This command was replaced by the set mpls experimental imposition command.
|
Usage Guidelines
Use the policy map to set the MPLS experimental field when you do not want to change the IP precedence field.
Examples
The following example specifies a policy map named out_pmap. The policy map comprises class maps. Class map mpls_2 matches packets with MPLS experimental field 2 and resets the MPLS experimental field to 3.
Router(config)# class-map mpls_2
Router(config-cmap)# match mpls experimental 2
Router(config-cmap)# exit
Router(config)# policy-map out_pmap
Router(config-pmap)# class mpls_2
Router(config-pmap-c)# set mpls experimental 3
Router(config-pmap-c)# exit
Router(config-pmap)# exit
Related Commands
Command
|
Description
|
class-map
|
Creates a class map to be used for matching packets to the class specified.
|
policy-map
|
Creates a policy map that can be attached to one or more interfaces to specify a service policy.
|
service-policy
|
Attaches a policy map to an input interface or an output interface to be used as the service policy for that interface.
|
set mpls experimental imposition
To set the value of the Multiprotocol Label Switching (MPLS) experimental (EXP) field on all imposed label entries, use the set mpls experimental imposition command in QoS policy-map class configuration mode. To disable the setting, use the no form of this command.
set mpls experimental imposition {mpls-exp-value | from-field [table table-map-name]}
no set mpls experimental imposition {mpls-exp-value | from-field [table table-map-name]}
Syntax Description
mpls-exp-value
|
Specifies the value used to set MPLS EXP bits defined by the policy map. Valid values are numbers from 0 to 7.
|
from-field
|
Specific packet-marking category to be used to set the MPLS EXP imposition value. If you are using a table map for mapping and converting packet-marking values, this establishes the "map from" packet-marking category. Packet-marking category keywords are as follows:
• precedence
• dscp
|
table
|
(Optional) Used in conjunction with the from-field argument. Indicates that the values set in a specified table map will be used to set the MPLS EXP imposition value.
|
table-map-name
|
(Optional) Used in conjunction with the table keyword. Name of the table map used to specify the MPLS EXP imposition value. The name can be a maximum of 64 alphanumeric characters.
|
Defaults
No MPLS EXP value is set.
Command Modes
QoS policy-map class configuration
Command History
Release
|
Modification
|
12.2(13)T
|
This command replaces (renames) the set mpls experimental command, introduced in 12.1(5)T. The set mpls experimental imposition command was modified for the Enhanced Packet Marking feature. A mapping table (table map) can now be used to convert and propagate packet-marking values.
|
Usage Guidelines
The set mpls experimental imposition command is supported only on input interfaces. Use this command during label imposition. This command sets the MPLS EXP field on all imposed label entries.
Using This Command with the Enhanced Packet Marking Feature
If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the "from-field" packet-marking category to be used for mapping and setting the class of service (CoS) value. The "from-field" packet-marking categories are as follows:
•
Precedence
•
Differentiated services code point (DSCP)
If you specify a "from-field" category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the "from-field" category as the MPLS EXP imposition value. For instance, if you configure the set mpls experimental imposition precedence command, the precedence value will be copied and used as the MPLS EXP imposition value.
You can configure the set mpls experimental imposition dscp command, and the DSCP value will be copied and used as the MPLS EXP imposition value.
Note
If you configure the set mpls experimental imposition dscp command, only the first three bits (the class selector bits) of the DSCP field are used.
Examples
In the following example, the MPLS EXP value is set to 3 on all imposed label entries:
Router(config-pmap)# set mpls experimental imposition 3
In the following example, the policy map named policy1 is created to use the packet-marking values defined in a table map named table-map1. The table map was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.
In this example, the MPLS EXP imposition value will be set according to the DSCP value defined in table-map1.
Router(config)# policy-map policy1
Router(config-pmap)# class class-default
Router(config-pmap-c)# set mpls experimental imposition dscp table table-map1
Router(config-pmap-c)# exit
Related Commands
Command
|
Description
|
set dscp
|
Marks a packet by setting the Layer 3 DSCP value in the ToS byte.
|
set mpls experimental topmost
|
Sets the MPLS EXP field value in the topmost label on either an input or an output interface.
|
set precedence
|
Sets the precedence value in the packet header.
|
show table-map
|
Displays the configuration of a specified table map or all table maps.
|
table-map (value mapping)
|
Creates and configures a mapping table for mapping and converting one packet-marking value to another.
|
set mpls experimental topmost
To set the Multiprotocol Label Switching (MPLS) experimental (EXP) field value in the topmost label on either an input or an output interface, use the set mpls experimental topmost command in QoS policy-map class configuration mode. To disable the setting, use the no form of this command.
set mpls experimental topmost {mpls-exp-value | qos-group [table table-map-name]}
no set mpls experimental topmost {mpls-exp-value | qos-group [table table-map-name]}
Syntax Description
mpls-exp-value
|
Specifies the value used to set MPLS experimental bits defined by the policy map. Valid values are numbers from 0 to 7.
|
qos-group
|
Specifies that the qos-group packet-marking category is used to set the MPLS EXP imposition value. If you are using a table map for mapping and converting packet-marking values, this establishes the "map from" packet-marking category.
|
table
|
(Optional) Used in conjunction with the qos-group keyword. Indicates that the values set in a specified table map will be used to set the MPLS EXP value.
|
table-map-name
|
(Optional) Used in conjunction with the table keyword. Name of the table map used to specify the MPLS EXP value. The name can be a maximum of 64 alphanumeric characters.
|
Defaults
No MPLS EXP value is set.
Command Modes
QoS policy-map class configuration
Command History
Release
|
Modification
|
12.2(13)T
|
This command was introduced.
|
Usage Guidelines
This command sets the MPLS EXP value only in the topmost label. This command does not affect an IP packet. The MPLS field in the topmost label header is not changed.
Using This Command with the Enhanced Packet Marking Feature
If you are using this command as part of the Enhanced Packet Marking feature, you can use this command to specify the qos-group packet-marking category to be used for mapping and setting the differentiated services code point (DSCP) value.
If you specify the qos-group category but do not specify the table keyword and the applicable table-map-name argument, the default action will be to copy the value associated with the qos-group category as the MPLS EXP topmost value. For instance, if you configure the set mpls experimental topmost qos-group command, the QoS group value will be copied and used as the MPLS EXP topmost value.
The valid value range for the MPLS EXP topmost value is a number from 0 to 7. The valid value range for the QoS group is a number from 0 to 99. Therefore, when configuring the set mpls experimental topmost qos-group command, note the following points:
•
If a QoS group value falls within both value ranges (for example, 6), the packet-marking value will be copied and the packets will be marked.
•
If a QoS group value exceeds the MPLS EXP topmost range (for example, 10), the packet-marking value will not copied and the packet will not be marked. No action is taken.
Examples
In the following example the MPLS EXP value is set to 3 in the topmost label of an input or output interface:
Router(config-pmap)# set mpls experimental topmost 3
In the following example, the policy map named policy1 is created to use the packet-marking values defined in a table map named table-map1. The table map was created earlier with the table-map (value mapping) command. For more information about the table-map (value mapping) command, see the table-map (value mapping) command page.
In this example, the MPLS EXP value will be set according to the QoS group value defined in table-map1.
Router(config)# policy-map policy1
Router(config-pmap)# class class-default
Router(config-pmap-c)# set mpls experimental topmost qos-group table table-map1
Router(config-pmap-c)# exit
Related Commands
Command
|
Description
|
match mpls experimental topmost
|
Matches the MPLS EXP field value in the topmost label.
|
set mpls experimental imposition
|
Sets the value of the MPLS EXP field on all imposed label entries.
|
set qos-group
|
Sets a group ID that can be used later to classify packets.
|
show table-map
|
Displays the configuration of a specified table map or all table maps.
|
table-map (value mapping)
|
Creates and configures a mapping table for mapping and converting one packet-marking value to another.
|
set mpls-label
To enable a route to be distributed with a Multiprotocol Label Switching (MPLS) label if the route matches the conditions specified in the route map, use the set mpls-label command in route map configuration mode. To disable this function, use the no form of this command.
set mpls-label
no set mpls-label
Syntax Description
This command has no arguments or keywords.
Defaults
No route with an MPLS label is distributed.
Command Modes
Route map configuration
Command History
Release
|
Modification
|
12.0(21)ST
|
This command was introduced.
|
12.0(22)S
|
This command was integrated into Cisco IOS Release 12.0(22)S.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
This command can be used only with the neighbor route-map out command to manage outbound route maps for a Border Gateway Protocol (BGP) session.
Use the route-map global configuration command with match and set route-map configuration commands to define the conditions for redistributing routes from one routing protocol into another. Each route-map command has a list of match and set commands associated with it. The match commands specify the match criteria—the conditions under which redistribution is allowed for the current route-map command. The set commands specify the set actions—the particular redistribution actions to perform if the criteria enforced by the match commands are met. The no route-map command deletes the route map.
Examples
The following example creates a route map that enables the route to be distributed with a label if the IP address of the route matches an IP address in ACL 1.
Router(config-router)# route-map incoming permit 10
Router(config-route-map)# match ip address 1
Router(config-route-map)# set mpls-label
Related Commands
Command
|
Description
|
match ip address
|
Distributes any routes that have a destination network number address that is permitted by a standard or extended access list.
|
match mpls-label
|
Redistributes routes that contain MPLS labels and match the conditions specified in the route map.
|
route-map (IP)
|
Defines the conditions for redistributing routes from one routing protocol into another, or enables policy routing.
|
set ospf router-id
To set a separate OSPF router ID for each interface or subinterface on a PE router for each directly attached CE router, use the set ospf router-id command in route-map configuration mode.
set ospf router-id
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Route-map configuration
Command History
Release
|
Modification
|
12.0(7)T
|
This command was introduced.
|
Usage Guidelines
To use this command, you must enable OSPF and create a routing process.
Examples
In the following example, the PE router IP address 192.168.0.0 is matched against the interface in access list 1 and set to the OSPF router ID:
router ospf 2 vrfvpn1-site1
redistribute bgp 100 metric-type 1 subnets
network 202.0.0.0 0.0.0.255 area 1
neighbor 172.19.89. 62 remote-as 100
access-list 1 permit 192.168.0.0
route-map vpn1-site1-map permit 10
Related Commands
Command
|
Description
|
router ospf
|
Enables OSPF routing, which places the router in router configuration mode.
|
set port flowcontrol
To set the receive flow-control value for a particular Gigabit Ethernet switching module port, use the set port flowcontrol command in privileged EXEC mode. To reset the receive flow-control value to the default, use the no form of this command.
set port flowcontrol {receive | send} [module-number | port-number] {off | on | desired}
no set port flowcontrol {receive | send} [module-number | port-number] {off | on | desired}
Syntax Description
receive
|
Indicates whether the port can receive administrative status from a remote device.
|
send
|
Indicates whether the local port can send administrative status to a remote device.
|
module-number
|
(Optional) Number of the module.
|
port-number
|
(Optional) Number of the port on the module.
|
off
|
When used with receive, it turns off an attached device's ability to send flow-control packets to a local port.
When used with send, it turns off the local port's ability to send administrative status to a remote device.
|
on
|
When used with receive, it requires that a local port receive administrative status from a remote device.
When used with send, the local port sends administrative status to a remote device.
|
desired
|
When used with receive, it allows a local port to operate with an attached device that is required to send flow-control packets or with an attached device that is not required to, but may send flow-control packets.
When used with send, the local port sends administrative status to a remote device if the remote device supports it.
|
Defaults
receive—off
send—desired
Default on multiplexed ports is on. The exception to these defaults applies to the 18-port Gigabit Ethernet switching module. For this module, the defaults are shown below:
•
Ports 1-2—send is off and receive is desired
•
Ports 3-18—send is on and receive is desired
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.2(11)T
|
This command was introduced and implemented on the Cisco 2600 series, Cisco 3600 series, and Cisco 3700 series routers
|
Usage Guidelines
This command is supported on Gigabit Ethernet switching modules only.
Examples
The following examples show how to use the set port flowcontrol command set:
The port 5/1 flow-control receive administration status is set to on (port will require far end to send flowcontrol packets):
router# (enable) set port flowcontrol receive 5/1 on
The port 5/1 flow-control receive administration status is set to desired (port will allow far end to send flowcontrol packets if far end supports it):
router# (enable)
router# (enable) set port flowcontrol receive 5/1 desired
The port 5/1 flow-control receive administration status is set to off (port will not allow far end to send flowcontrol packets):
router# (enable)
router# (enable) set port flowcontrol receive 5/1 off
The port 5/1 flow-control send administration status is set to on (port will send flowcontrol packets to far end):
router# (enable)
router# (enable) set port flowcontrol send 5/1 on
The port 5/1 flow-control send administration status is set to desired (port will send flowcontrol packets to far end if far end supports it):
router# (enable)
router# (enable) set port flowcontrol send 5/1 desired
The port 5/1 flow-control send administration status is set to off (port will not send flowcontrol packets to far end):
router# (enable)
router# (enable) set port flowcontrol send 5/1 off
Related Commands
Command
|
Description
|
show port flowcontrol
|
Displays per-port status information and statistics related to flow control.
|
set vlan
To group ports into a virtual LAN (VLAN), use the set vlan command in privileged EXEC mode.
set vlan vlan-number module/port
set vlan vlan-number [name name] [type {ethernet | fddi | fddinet | trcrf | trbrf}]
[state {active | suspend}] [said said] [mtu mtu] [ring hex-ring-number]
[decring decimal-ring-number] [bridge bridge-number] [parent vlan-number] [mode {srt |
srb}] [stp {ieee | ibm | auto}] [translation vlan-number] [backupcrf {off | on}]
[aremaxhop hop-count] [stemaxhop hop-count]
Syntax Description
vlan-number
|
Number identifying the VLAN.
|
module
|
Number of the module. This argument is not valid when defining or configuring Token Ring Bridge Relay Functions (TRBRFs).
|
port
|
Number of the port on the module belonging to the VLAN; this argument does not apply to TRBRFs.
|
name name
|
(Optional) Defines a text string used as the name of the VLAN (1 to 32 characters).
|
type {ethernet | fddi | fddinet | trcrf | trbrf}
|
(Optional) Identifies the VLAN type. The default type is Ethernet.
|
state {active | suspend}
|
(Optional) Specifies whether the state of the VLAN is active or suspended. VLANs in suspended state do not pass packets. The default state is active.
|
said said
|
(Optional) Specifies the security association identifier. Possible values are 1 to 4294967294. The default is 100001 for VLAN1, 100002 for VLAN 2, 100003 for VLAN 3, and so on. This argument does not apply to Token Ring Concentrator Relay Functions (TRCRFs) or TRBRFs.
|
mtu mtu
|
(Optional) Specifies the maximum transmission unit (packet size, in bytes) that the VLAN can use. Possible values are 576 to 18190. The default is 1500 bytes.
|
ring hex-ring-number
|
(Optional) Specifies the logical ring number for Token Ring VLANs. Possible values are hexadecimal numbers 0x1 to 0xFFF. This argument is valid and required only when defining a TRCRF.
|
decring decimal-ring-number
|
(Optional) Specifies the logical ring number for Token Ring VLANs. Possible values are decimal numbers 1 to 4095. This argument is valid and required only when defining a TRCRF.
|
bridge bridge-number
|
(Optional) Specifies the identification number of the bridge. Possible values are hexadecimal numbers 0x1 to 0xF. For Token Ring VLANs, the default is 0F. This argument is not valid for TRCRFs.
|
parent vlan-number
|
(Optional) Sets a parent VLAN. The range for vlan-number is 2 to 1005. This argument identifies the TRBRF to which a TRCRF belongs and is required when defining a TRCRF.
|
mode {srt | srb}
|
(Optional) Specfifies the TRCRF bridging mode.
|
stp {ieee | ibm | auto}
|
(Optional) Specifies the Spanning Tree Protocol version for a TRBRF to use: source-routing transparent (ieee), source-route bridging (ibm), or automatic source selection (auto).
|
translation vlan-number
|
(Optional) Specifies a translational VLAN used to translate FDDI to Ethernet. Valid values are from 1 to 1005. This argument is not valid for defining or configuring Token Ring VLANs.
|
backupcrf {off | on}
|
(Optional) Specifies whether the TRCRF is a backup path for traffic.
|
aremaxhop hop-count
|
(Optional) Specifies the maximum number of hops for All-Routes Explorer frames. Possible values are 1 to 14. The default is 7. This argument is only valid when defining or configuring TRCRFs.
|
stemaxhop hop-count
|
(Optional) Specifies the maximum number of hops for Spanning-Tree Explorer frames. Possible values are 1 to 14. The default is 7. This argument is only valid when defining or configuring TRCRFs.
|
Defaults
The default configuration has all switched Ethernet ports and Ethernet repeater ports in VLAN 1. The default SAID is 100001 for VLAN 1, 100002 for VLAN 2, 100003 for VLAN 3, and so on. The default type is Ethernet. The default MTU is 1500 bytes. The default state is active.
The default TRBRF is 1005, the default TRCRF is 1003, and the default MTU for TRBRFs and TRCRFs is 4472. The default state is active. The default aremaxhop is 7; the default stemaxhop is 7.
Command Modes
Privileged EXEC
Usage Guidelines
You cannot use the set vlan command until the networking device is either in VTP transparent mode (set vtp mode) or until a VTP domain name has been set (set vtp).
Valid MTU values for Token Ring VLAN are 1500 or 4472. While you can enter any value for the MTU value, the value you enter defaults to the next lowest valid value.
You cannot set multiple VLANs for Inter-Switch Link (ISL) ports using this command. The VLAN name can be from 1 to 32 characters in length. If adding a new VLAN, the VLAN number must be within the range 2 to 1001. When modifying a VLAN, the valid range for the VLAN number is 2 to 1005.
On a new Token Ring VLAN, if you do not specify the parent parameter for a TRCRF, the default TRBRF (1005) is used.
Examples
The following example shows how to set VLAN 850 to include ports 4 through 7 on module 3. Because ports 4 through 7 were originally assigned to TRCRF 1003, the message reflects the modification of VLAN 1003.
Router# set vlan 850 3/4-7
---- -----------------------
Related Commands
Command
|
Description
|
clear vlan
|
Deletes an existing VLAN from a management domain.
|
show vlans
|
Displays VLAN subinterfaces.
|
set vlan mapping
To map 802.1Q virtual LANs (VLANs) to Inter-Switch Link (ISL) VLANs, use the set vlan mapping command in privileged EXEC mode.
set vlan mapping dot1q 1q-vlan-number isl isl-vlan-number
Syntax Description
dot1q
|
Specifies the 802.1Q VLAN.
|
1q-vlan-number
|
Number identifying the 802.1Q VLAN; valid values are 1001 to 4095.
|
isl
|
Specifies the ISL VLAN.
|
isl-vlan-number
|
Number identifying the ISL VLAN; valid values are 1 to 1000.
|
Defaults
No 802.1Q-to-ISL mappings are defined.
Command Modes
Privileged EXEC
Usage Guidelines
IEEE 802.1Q VLAN trunks support VLANs 1 through 4095. ISL VLAN trunks support VLANs 1 through 1000. The switch automatically maps 802.1Q VLANs 1000 and lower to ISL VLANs with the same number.
The native VLAN of the 802.1Q trunk cannot be used in the mapping.
Use this feature to map 802.1Q VLANs above 1000 to ISL VLANs. Note that if you map a 802.1Q VLAN over 1000 to an ISL VLAN, the corresponding 802.1Q VLAN will be blocked. For example, if you map 802.1Q VLAN 2000 to ISL VLAN 200, then 802.1Q VLAN 200 will be blocked.
You can map up to seven VLANs. Only one 802.1Q VLAN can be mapped to an ISL VLAN. For example, if 802.1Q VLAN 800 has been automatically mapped to ISL VLAN 800, do not manually map any other 802.1Q VLANs to ISL VLAN 800.
You cannot overwrite existing 802.1Q VLAN mapping. If the 802.1Q VLAN number is in the mapping table, the command is aborted. You must first clear that mapping.
If vlan-number does not exist, then either of the following occurs:
•
If the switch is in server or transparent mode, the VLAN is created with all default values.
•
If the switch is in client mode, then the command proceeds without creating the VLAN. A warning will be given indicating that the VLAN does not exist.
If the table is full, the command is aborted with an error message indicating the table is full.
Examples
The following example shows how to map VLAN 1022 to ISL VLAN 850:
Router# set vlan mapping dot1q 1022 isl 850
Vlan 850 configuration successful
The following example shows the display if you enter a VLAN that does not exist:
Router# set vlan mapping dot1q 1017 isl 999
Warning: vlan 999 non-existent
Vlan 999 configuration successful
The following example shows the display if you enter an existing mapping:
Router# set vlan mapping dot1q 1033 isl 722
722 exists in the mapping table. Please clear the mapping first.
The following example shows the display if the mapping table is full:
Router# set vlan mapping dot1q 1099 isl 917
Related Commands
Command
|
Description
|
clear vlan mapping
|
Deletes existing 802.1Q VLAN to ISL VLAN-mapped pairs.
|
show vlans
|
Displays VLAN subinterfaces.
|
shortcut-frame-count
To specify the maximum number of times a packet can be routed to the default router within shortcut-frame time before an MPOA resolution request is sent, use the shortcut-frame-count command in MPC configuration mode. To restore the default shortcut-setup frame count value, use the no form of this command.
shortcut-frame-count count
no shortcut-frame-count
Syntax Description
count
|
Shortcut-setup frame count. The default is 10 frames.
|
Defaults
The default is 10 frames.
Command Modes
MPC configuration
Command History
Release
|
Modification
|
11.3(3a)WA4(5)
|
This command was introduced.
|
Examples
The following example sets the shortcut-setup frame count to 5 for the MPC:
Related Commands
Command
|
Description
|
atm-address
|
Overrides the control ATM address of an MPC or MPS.
|
mpoa client config name
|
Defines an MPC with a specified name.
|
shortcut-frame-time
|
Sets the shortcut-setup frame time (in seconds) for the MPC.
|
shortcut-frame-time
To set the shortcut-setup frame time (in seconds) for the MPC, use the shortcut-frame-time command in MPC configuration mode. To restore the default shortcut-setup frame-time value, use the no form of this command.
shortcut-frame-time time
no shortcut-frame-time
Syntax Description
time
|
Shortcut-setup frame time (in seconds).
|
Defaults
The default is 1 second.
Command Modes
MPC configuration
Command History
Release
|
Modification
|
11.3(3a)WA4(5)
|
This command was introduced.
|
Examples
The following example sets the shortcut-setup frame time to 7 for the MPC:
Related Commands
Command
|
Description
|
atm-address
|
Overrides the control ATM address of an MPC or MPS.
|
mpoa client config name
|
Defines an MPC with a specified name.
|
shortcut-frame-count
|
Specifies the maximum number of times a packet can be routed to the default router within shortcut-frame time before an MPOA resolution request is sent.
|
show adjacency
To display Cisco Express Forwarding (CEF) adjacency table information, use the show adjacency command in EXEC mode.
show adjacency [type number] [detail] [summary]
Syntax Description
type number
|
(Optional) Displays CEF adjacency information for the specified interface type and number.
|
detail
|
(Optional) Displays detailed adjacency information, including Layer 2 information.
|
summary
|
(Optional) Displays CEF adjacency table summary information.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2 GS
|
This command was introduced.
|
11.1 CC
|
Multiple platform support was added.
|
12.2(8)T
|
The detail keyword output was modified to show the epoch value for each entry of the adjacency table.
The summary keyword output was modified to show the table epoch for the adjacency table.
|
Usage Guidelines
This command is used to verify that an adjacency exists for a connected device, that the adjacency is valid, and that the MAC header rewrite string is correct.
Examples
The following is sample output from the show adjacency detail command:
Router# show adjacency detail
Protocol Interface Address
IP Serial5/0/0/1:1 point2point(7)
IP Serial5/0/1/1:1 point2point(7)
The following is sample output from the show adjacency summary command:
Router# show adjacency summary
Adjacency Table has 2 adjacencies
Table epoch: 14 (2 entries at this epoch)
Interface Adjacency Count
Table 1 describes the significant fields shown in the displays.
Table 1 show adjacency Field Descriptions
Field
|
Description
|
Protocol
|
Routed protocol to which the adjacency is related.
|
Interface
|
Outgoing interface associated with the adjacency.
|
Address
|
The address can represent one of these addresses:
• Next-hop address
• Point-to-point address
The number (in parentheses) that follows this field indicates the number of internal references to the adjacency.
|
Epoch
|
Table epoch value at the time when the adjacency was last modified.
|
Related Commands
Command
|
Description
|
clear adjacency
|
Clears the CEF adjacency table.
|
show cable bundle
To display the forwarding table for the specified interface, use the show cable bundle command in privileged EXEC mode.
show cable bundle bundle-number forwarding-table
Syntax Description
bundle-number
|
Specifies the bundle identifier. Valid range is from 1 to 255.
|
forwarding-table
|
Displays the forwarding table for the specified interface.
|
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
12.0(7)XR
|
This command was introduced.
|
Examples
In the following example, a cable bundle of 25 is specified:
Router# show cable bundle 25 forwarding-table
The fields in the display are described as follows:
•
MAC address—Media Access Control ID for each interface in the bundle.
•
Interface—The cable interface slot and port number.
Related Commands
Command
|
Description
|
cable bundle
|
Creates an interface bundle.
|
show cef
To display which packets the line cards dropped or to display which packets were not express forwarded, use the show cef command in privileged EXEC mode or user EXEC mode.
show cef [drop | not-cef-switched]
Syntax Description
drop
|
(Optional) Displays which packets were dropped by each line card.
|
not-cef-switched
|
(Optional) Displays which packets were sent to a different switching path.
|
Command Modes
Privileged EXEC
User 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.
|
12.0(22)S
|
The display output for this command was modified to include support for Cisco Express Forwarding for IPv6 (CEFv6) and distributed CEF for IPv6 (dCEFv6) packets.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Usage Guidelines
A line card might drop packets because of encapsulation failure, absence of route information, or absence of adjacency information.
A packet is sent to a different switching path (punted) because CEF does not support the encapsulation or feature, the packet is destined for the router, or the packet has IP options, such as time stamp and record route. IP options are process switched.
Note
If CEFv6 or dCEFv6 is enabled globally on the router, the drop and not-cef-switched keywords used with the show cef command display IPv6 CEF counter information and IPv4 CEF counter information. If CEFv6 or dCEFv6 is not enabled globally on the router, the drop and not-cef-switched keywords used with the show cef command display only IPv4 CEF counter information.
Examples
The following is sample output from the show cef drop command:
Slot Encap_fail Unresolved Unsupported No_route No_adj ChksumErr
Slot Encap_fail Unresolved Unsupported No_route No_adj
Table 2 describes the significant fields shown in the display.
Table 2 show cef drop Field Descriptions
Field
|
Description
|
Slot
|
The slot number on which the packets were received.
|
Encap_fail
|
Indicates the number of packets dropped after exceeding the limit for packets punted to the processor due to missing adjacency information. (CEF throttles packets passed up to the process level at a rate of one packet per second.)
|
Unresolved
|
Indicates the number of packets dropped due to an unresolved prefix in the Forwarding Information Base (FIB) table.
|
Unsupported
|
Indicates the number of packets fast-dropped by CEF (drop adjacency).
|
No_route
|
Indicates the number of packets dropped due to a missing prefix in the FIB table.
|
No_adj
|
Indicates the number of packets dropped due to incomplete adjacency.
|
ChksumErr
|
Indicates the number of IPv4 packets received with a checksum error.
Note This field is not supported for IPv6 packets.
|
The following is sample output from the show cef not-cef-switched command:
Router# show cef not-cef-switched
CEF Packets passed on to next switching layer
Slot No_adj No_encap Unsupp'ted Redirect Receive Options Access Frag
IPv6 CEF Packets passed on to next switching layer
Slot No_adj No_encap Unsupp'ted Redirect Receive Options Access MTU
Table 3 describes the significant fields shown in the display.
Table 3 show cef not-cef-switched Field Descriptions
Field
|
Meaning
|
Slot
|
The slot number on which the packets were received.
|
No_adj
|
Indicates the number of packets sent to the processor due to incomplete adjacency.
|
No_encap
|
Indicates the number of packets sent to the processor for Address Resolution Protocol (ARP) resolution.
|
Unsupp'ted
|
Indicates the number of packets punted to the next switching level due to unsupported features.
|
Redirect
|
Records packets that are ultimately destined to the router, and packets destined to a tunnel endpoint on the router. If the decapsulated tunnel is IP, it is CEF switched; otherwise, packets are process switched.
|
Receive
|
Indicates the number of packets ultimately destined to the router, or packets destined to a tunnel endpoint on the router. If the decapsulated tunnel packet is IP, the packet is CEF switched. Otherwise, packets are process switched.
|
Options
|
Indicates the number of packets with options. Packets with IP options are handled only at the process level.
|
Access
|
Indicates the number of packets punted due to an access list failure.
|
Frag
|
Indicates the number of packets punted due to fragmentation failure.
Note This field is not supported for IPv6 packets.
|
MTU
|
Indicates the number of packets punted due to maximum transmission unit (MTU) failure.
Note This field is not supported for IPv4 packets.
|
Related Commands
Command
|
Description
|
show cef interface
|
Displays CEF-related interface information.
|
show cef linecard
|
Displays CEF-related interface information by line card.
|
show cef interface
To display detailed Cisco Express Forwarding (CEF) information for all interfaces, use the show cef interface command in privileged EXEC mode or user EXEC mode.
show cef interface [type number] [statistics] [detail]
Syntax Description
type number
|
(Optional) Interface type and number.
|
statistics
|
(Optional) Displays switching statistics for the line card.
|
detail
|
(Optional) Displays detailed CEF information for the specified interface type and number.
|
Command Modes
Privileged EXEC
User 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.
|
12.0(14)ST
|
Documentation for the statistics keyword was updated.
|
12.2(2)T
|
Documentation for the statistics and detail keywords was updated.
|
12.0(22)S
|
The display output for this command was modified to include support for CEF for IPv6 (CEFv6) and distributed (dCEFv6) interface information.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Usage Guidelines
You can use this command to display the detailed CEF status for all of the interfaces.
Values entered for the type and number arguments display CEF status information for the specified interface type and number.
Examples
The following is sample output from the show cef interface detail command for Ethernet interface 1/0/0:
Router# show cef interface Ethernet 1/0/0 detail
Ethernet1/0/0 is up (if_number 9)
Corresponding hwidb fast_if_number 9
Corresponding hwidb firstsw->if_number 9
Internet address is 10.2.61.8/24
ICMP redirects are always sent
Per packet load-sharing is disabled
IP unicast RPF check is disabled
Inbound access list is not set
Outbound access list is not set
IP policy routing is disabled
Hardware idb is Ethernet1/0/0
Fast switching type 1, interface type 5
IP Distributed CEF switching enabled
IP Feature Fast switching turbo vector
IP Feature CEF switching turbo vector
Input fast flags 0x0, Output fast flags 0x0
Transmit limit accumulator 0x48001A82 (0x48001A82)
The following is sample output from the show cef interface Null 0 detail command:
Router# show cef interface Null 0 detail
Null0 is up (if_number 1)
Corresponding hwidb fast_if_number 1
Corresponding hwidb firstsw->if_number 1
Internet Protocol processing disabled
Interface is marked as nullidb
Packets switched to this interface on linecard are dropped to next slow path
Fast switching type 13, interface type 0
IP Feature CEF switching turbo vector
Input fast flags 0x0, Output fast flags 0x0
Slot -1 Slot unit -1 VC -1
Transmit limit accumulator 0x0 (0x0)
Table 4 describes the significant fields shown in the displays.
Table 4 show cef interface Field Descriptions
Field
|
Description
|
Ethernet1/0/0 is up
|
Indicates type, number, and status of the interface.
|
Internet address is
|
Internet address of the interface.
|
ICMP redirects are always sent
|
Indicates how packet forwarding is configured.
|
Per packet load-sharing is disabled
|
Indicates status of load sharing on the interface.
|
IP unicast RPF check is disabled
|
Indicates status of IP unicast Reverse Path Forwarding (RPF) check on the interface.
|
Inbound access list is not set
|
Indicates the number or name of the inbound access list if one is applied to this interface.
|
Outbound access list is not set
|
Indicates the number or name of the outbound access list if one is applied to this interface.
|
IP policy routing is disabled
|
Indicates the status of IP policy routing on the interface.
|
Hardware idb is Ethernet1/0/0
|
Interface type and number configured.
|
Fast switching type
|
Used for troubleshooting; indicates switching mode in use.
|
interface type 5
|
Indicates interface type.
|
IP Distributed CEF switching enabled
|
Indicates whether distributed CEF is enabled on this interface. (Cisco 7500 and 12000 series Internet routers only.)
|
IP Feature Fast switching turbo vector
|
Indicates IP fast switching type configured.
|
IP Feature CEF switching turbo vector
|
Indicates IP feature CEF switching type configured.
|
Input fast flags
|
Indicates the input status of various switching features, as follows:
• 0x0001 (input Access Control List [ACL] enabled)
• 0x0002 (policy routing enabled)
• 0x0004 (input rate limiting)
• 0x0008 (MAC/Prec accounting)
• 0x0010 (DSCP/PREC/QOS GROUP)
• 0x0020 (input named access lists)
• 0x0040 (NAT enabled on input)
• 0x0080 (crypto map on input)
• 0x0100 (QPPB classification)
• 0x0200 (inspect on input)
• 0x0400 (input classification)
• 0x0800 (casa input enable)
• 0x1000 (Virtual Private Network [VPN] enabled on a swidb)
• 0x2000 (input idle timer enabled)
• 0x4000 (unicast Reverse Path Forwarding [RPF] check)
• 0x8000 (per-address ACL enabled)
• 0x10000 (deaggregating a packet)
• 0x20000 (GPRS enabled on input)
• 0x40000 (URL RenDezvous)
• 0x80000 (QoS classification)
• 0x100000 (FR switching on interface)
• 0x200000 (WCCP redirect on input)
• 0x400000 (input classification)
|
Output fast flags
|
Indicates the output status of various switching features, as follows:
• 0x0001 (output ACL enabled)
• 0x0002 (IP accounting enabled)
• 0x0004 (WCC redirect enabled interface)
• 0x0008 (rate limiting)
• 0x0010 (MAC/Prec accounting)
• 0x0020 (DSCP/PREC/QOS GROUP)
• 0x0040 (D-QOS classification)
• 0x0080 (output named access lists)
• 0x0100 (NAT enabled on output)
• 0x0200 (TCP intercept enabled)
• 0x0400 (crypto map set on output)
• 0x0800 (output firewall)
• 0x1000 (RSVP classification)
• 0x2000 (inspect on output)
• 0x4000 (QoS classification)
• 0x8000 (QoS pre-classification)
• 0x10000 (output stile)
|
ifindex 7/(7)
|
Indicates the SNMP ifindex for this interface.
|
Slot 1 Slot unit 0 VC -1
|
The slot number and slot unit.
|
Transmit limit accumulator
|
Indicates the maximum number of packets allowed in the transmit queue.
|
IP MTU
|
The MTU size set on the interface.
|
Related Commands
Command
|
Description
|
show cef
|
Displays which packets the line cards dropped, or displays which packets were not express forwarded.
|
show cef linecard
|
Displays CEF-related interface information by line card.
|
show cef interface policy-statistics
To display detailed Cisco Express Forwarding (CEF) policy statistical information for all interfaces, use the show cef interface policy-statistics command in EXEC mode.
show cef interface [type number] policy-statistics
Syntax Description
type number
|
(Optional) Interface type and number.
|
Command Modes
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 integrated into Cisco IOS Release 12.0(17)ST.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
Usage Guidelines
This command is available only on distributed switching platforms.
The type and number arguments display CEF status information for the specified interface type and number.
Examples
The following is sample output from the show cef interface policy-statistics command:
Router# show cef interface policy-statistics
POS7/0 is up (if_number 8)
The following is sample output from the show cef interface policy-statistics command showing policy statistics for Ethernet interface 1/0:
Router# show cef interface ethernet 1/0 policy-statistics
Ethernet1/0 is up (if_number 3)
Corresponding hwidb fast_if_number 3
Corresponding hwidb firstsw->if_number 3
Table 5 describes the significant fields shown in the display.
Table 5 show cef interface policy-statistics Field Descriptions
Field
|
Description
|
Index
|
Traffic index set with the route-map command.
|
Packets
|
Number of packets switched matching the index definition.
|
Bytes
|
Number of bytes switched matching the index definition.
|
Related Commands
Command
|
Description
|
show cef
|
Displays which packets the line cards dropped, or displays which packets were not express forwarded.
|
show cef linecard
|
Displays CEF-related interface information by line card.
|
show cef linecard
To display Cisco Express Forwarding (CEF)-related information by line card, use the show cef linecard command in privileged EXEC mode or user EXEC mode.
show cef linecard [slot-number] [detail] [internal]
Syntax Description
slot-number
|
(Optional) Slot number containing the line card about which to display CEF-related information. When you omit this argument, information about all line cards is displayed.
|
detail
|
(Optional) Displays detailed CEF information for the specified line card.
|
internal
|
(Optional) Displays internal CEF information for the specified line card.
|
Command Modes
Privileged EXEC
User 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.
|
12.0(10)S
|
Output display was changed.
|
12.1(2)T
|
This command was integrated into Cisco IOS Release 12.1(2)T.
|
12.0(22)S
|
The display output for this command was modified to include support for CEF for IPv6 (CEFv6) and distributed CEFv6 (dCEFv6) line card information.
|
12.2(13)T
|
This command was integrated into Cisco IOS Release 12.2(13)T.
|
12.2(14)S
|
This command was integrated into Cisco IOS Release 12.2(14)S.
|
Usage Guidelines
This command is available only on distributed switching platforms.
When you omit the slot-number argument, information about all line cards is displayed. When you omit the slot-number argument and include the detail keyword, detailed information is displayed for all line cards. When you omit the slot-number argument and include the internal keyword, detailed internal information is displayed for all line cards. When you omit all keywords and arguments, the show cef linecard command displays important information about all line cards in table format.
Examples
The following is sample output from the show cef linecard detail command for all line cards:
Router# show cef linecard detail
CEF linecard slot number 0, status up
Sequence number 4, Maximum sequence number expected 28, Seq Epoch 2
Send failed 0, Out Of Sequence 0, drops 0
Linecard CEF reset 0, reloaded 1
95 elements packed in 6 messages(3588 bytes) sent
linecard in sync after reloading
0/0/0 xdr elements in LowQ/MediumQ/HighQ
11/9/69 peak elements on LowQ/MediumQ/HighQ
Output packets 0, bytes 0, drops 0
Table name Version Prefix-xdr Status
Default-table 7 4 Active, up, sync
CEF linecard slot number 1, status up
Sequence number 4, Maximum sequence number expected 28, Seq Epoch 2
Send failed 0, Out Of Sequence 0, drops 0
Linecard CEF reset 0, reloaded 1
95 elements packed in 6 messages(3588 bytes) sent
linecard in sync after reloading
0/0/0 xdr elements in LowQ/MediumQ/HighQ
11/9/69 peak elements on LowQ/MediumQ/HighQ
Output packets 0, bytes 0, drops 0
Table name Version Prefix-xdr Status
Default-table 7 4 Active, up, sync
The following is sample output from the show cef linecard internal command for all line cards:
Router# show cef linecard internal
CEF linecard slot number 0, status up
Sequence number 11, Maximum sequence number expected 35
Send failed 0, Out Of Sequence 0
Linecard CEF reset 2, reloaded 2
flow features deactivate 2
4574 elements packed in 4495 messages(90286 bytes) sent
flow features deactivate 1
linecard disabled - failed a reload
0/0/0 xdr elements in LowQ/MediumQ/HighQ
Output packets 0, bytes 0, drops 0
Table name Version Prefix-xdr Status
Default-table 8 4 Active, sync
The following is sample output from the show cef linecard command. The command displays information for all line cards in table format.
Router# show cef linecard
Slot MsgSent XDRSent Window LowQ MedQ HighQ Flags
VRF Default-table, version 8, 6 routes
Slot Version CEF-XDR I/Fs State Flags
Table 6 describes the significant fields shown in the displays.
Table 6 show cef linecard Field Descriptions
Field
|
Description
|
Table name
|
Name of the CEF table.
|
Version
|
Number of the Forwarding Information Base (FIB) table version.
|
Prefix-xdr
|
Number of prefix IPC information elements XDRs processed.
|
Status
|
State of the CEF table.
|
Slot
|
Slot number of the line card.
|
MsgSent
|
Number of IPC messages sent.
|
XDRSent
|
XDRs packed into IPC messages sent from the Route Processor (RP) to the line card.
|
Window
|
Size of the IPC window between the line card and the RP.
|
LowQ/MedQ/HighQ
|
Number of XDR elements in the Low, Medium, and High priority queues.
|
Flags
|
Indicates the status of the line card. States are
• up—Line card is up.
• sync—Line card is in synchronization with the main FIB.
• reset—Line card FIB is reset.
• reloading—Line card FIB is being reloaded.
• disabled—Line card is disabled.
|
CEF-XDR
|
Number of CEF XDR messages processed.
|
I/Fs
|
Interface numbers.
|
Related Commands
Command
|
Description
|
show cef
|
Displays which packets the line cards dropped, or displays which packets were not express forwarded.
|
show cef interface
|
Displays CEF-related interface information.
|
show ipv6 cef
|
Displays entries in the IPv6 FIB.
|
show controllers vsi control-interface
To display information about an ATM interface configured with the tag-control-protocol vsi EXEC command to control an external switch (or if an interface is not specified, to display information about all VSI control interfaces), use the show controllers vsi control-interface command in EXEC mode.
show controllers vsi control-interface [interface]
Syntax Description
interface
|
(Optional) Specifies the interface number.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Examples
The following is sample output from the show controllers vsi control-interface command:
Router# show controllers vsi control-interface
Interface: ATM2/0 Connections: 14
The display shows the number of cross-connects currently on the switch that were established by the MPLS LSC through the VSI over the control interface.
Related Commands
Command
|
Description
|
tag-control-protocol vsi
|
Configures the use of VSI on a control port.
|
show controllers vsi descriptor
To display information about a switch interface discovered by the MPLS LSC through VSI, or if no descriptor is specified, about all such discovered interfaces, use the show controllers vsi descriptor command in EXEC mode.
show controllers vsi descriptor [descriptor]
Syntax Description
descriptor
|
(Optional) Physical descriptor. For the Cisco BPX switch, the physical descriptor has the following form: slot.port.0
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Specify an interface by its (switch-supplied) physical descriptor.
Per-interface information includes the following:
•
Interface name
•
Physical descriptor
•
Interface status
•
Physical interface state (supplied by the switch)
•
Acceptable VPI and VCI ranges
•
Maximum cell rate
•
Available cell rate (forward/backward)
•
Available channels
Similar information is displayed when you enter the show controllers XTagATM EXEC command. However, you must specify a Cisco IOS interface name instead of a physical descriptor.
Examples
The following is sample output from the show controllers vsi descriptor command:
Router# show controllers vsi descriptor 12.2.0
Log intf: 0x000C0200 (0.12.2.0)
IF status: up IFC state: ACTIVE
Min VPI: 1 Maximum cell rate: 10000
Max VPI: 259 Available channels: 2000
Min VCI: 32 Available cell rate (forward): 10000
Max VCI: 65535 Available cell rate (backward): 10000
Table 7 describes the significant fields in the output.
Table 7 show controllers vsi descriptor Field Descriptions
Field
|
Description
|
Phys desc
|
Physical descriptor. A string learned from the switch that identifies the interface.
|
Log intf
|
Logical interface ID. This 32-bit entity, learned from the switch, uniquely identifies the interface.
|
Interface
|
The (Cisco IOS) interface name.
|
IF status
|
Overall interface status. Can be "up," "down," or "administratively down."
|
Min VPI
|
Minimum virtual path identifier. Indicates the low end of the VPI range configured on the switch.
|
Max VPI
|
Maximum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
Min VCI
|
Minimum virtual path identifier. Indicates the high end of the VPI range configured on the switch.
|
Max VCI
|
Maximum virtual channel identifier. Indicates the high end of the VCI range configured on, or determined by, the switch.
|
IFC state
|
Operational state of the interface, according to the switch. Can be one of the following:
• FAILED_EXT (that is, an external alarm)
• FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
• REMOVED (administratively removed from the switch)
|
Maximum cell rate
|
Maximum cell rate for the interface, which has been configured on the switch (in cells per second).
|
Available channels
|
Indicates the number of channels (endpoints) that are currently free to be used for cross-connects.
|
Available cell rate (forward)
|
Cell rate that is currently available in the forward (that is, ingress) direction for new cross-connects on the interface.
|
Available cell rate (backward)
|
Cell rate that is currently available in the backward (that is, egress) direction for new cross-connects on the interface.
|
Related Commands
Command
|
Description
|
show controllers XTagATM
|
Displays information about an extended MPLS ATM interface.
|
show controllers vsi session
To display information about all sessions with VSI slaves, use the show controllers vsi session command in EXEC mode.
show controllers vsi session [session-num [interface interface]]
Note
A session consists of an exchange of VSI messages between the VSI master (the LSC) and a VSI slave (an entity on the switch). There can be multiple VSI slaves for a switch. On the BPX, each port or trunk card assumes the role of a VSI slave.
Syntax Description
session-num
|
(Optional) Specifies the session number.
|
interface interface
|
(Optional) Specifies the VSI control interface.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
If a session number and an interface are specified, detailed information on the individual session is presented. If the session number is specified, but the interface is omitted, detailed information on all sessions with that number is presented. (Only one session can contain a given number, because multiple control interfaces are not supported.)
Examples
The following is sample output from the show controllers vsi session command:
Router# show controllers vsi session
Interface Session VCD VPI/VCI Switch/Slave Ids Session State
ATM0/0 0 1 0/40 0/1 ESTABLISHED
ATM0/0 1 2 0/41 0/2 ESTABLISHED
ATM0/0 2 3 0/42 0/3 DISCOVERY
ATM0/0 3 4 0/43 0/4 RESYNC-STARTING
ATM0/0 4 5 0/44 0/5 RESYNC-STOPPING
ATM0/0 5 6 0/45 0/6 RESYNC-UNDERWAY
ATM0/0 6 7 0/46 0/7 UNKNOWN
ATM0/0 7 8 0/47 0/8 UNKNOWN
ATM0/0 8 9 0/48 0/9 CLOSING
ATM0/0 9 10 0/49 0/10 ESTABLISHED
ATM0/0 10 11 0/50 0/11 ESTABLISHED
ATM0/0 11 12 0/51 0/12 ESTABLISHED
Table 8 describes the significant fields in the output.
Table 8 show controllers vsi session Field Descriptions
Field
|
Description
|
Interface
|
Control interface name.
|
Session
|
Session number (from 0 to <n-1>), where n is the number of sessions on the control interface.
|
VCD
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC carrying the VSI protocol between the master and the slave for this session.
|
VPI/VCI
|
Virtual path identifier or virtual channel identifier (for the VC used for this session).
|
Switch/Slave Ids
|
Switch and slave identifiers supplied by the switch.
|
Session State
|
Indicates the status of the session between the master and the slave.
• ESTABLISHED is the fully operational steady state.
• UNKNOWN indicates that the slave is not responding.
Other possible states include the following:
• CONFIGURING
• RESYNC_STARTING
• RESYNC_UNDERWAY
• RESYNC_ENDING
• DISCOVERY
• SHUTDOWN_STARTING
• SHUTDOWN_ENDING
• INACTIVE
|
In the following example, session number 9 is specified with the show controllers vsi session command:
Router# show controllers vsi session 9
Interface: ATM1/0 Session number: 9
Switch type: BPX Switch id: 0
Controller id: 1 Slave id: 10
Keepalive timer: 15 Powerup session id: 0x0000000A
Cfg/act retry timer: 8/8 Active session id: 0x0000000A
Max retries: 10 Ctrl port log intf: 0x000A0100
Trap window: 50 Max/actual cmd wndw: 21/21
Trap filter: all Max checksums: 19
Current VSI version: 1 Min/max VSI version: 1/1
Messages sent: 2502 Inter-slave timer: 4.000
Messages received: 2502 Messages outstanding: 0
Table 9 describes the significant fields in the output.
Table 9 show controllers vsi session Field Descriptions
Field
|
Description
|
Interface
|
Name of the control interface on which this session is configured.
|
Session number
|
A number from 0 to <n-1>, where n is the number of slaves. Configured on the MPLS LSC with the slaves option of the tag-control-protocol vsi command.
|
VCD
|
Virtual circuit descriptor (virtual circuit number). Identifies the VC that carries VSI protocol messages for this session.
|
VPI/VCI
|
Virtual path identifier or virtual channel identifier for the VC used for this session.
|
Switch type
|
Switch device (for example, the BPX).
|
Switch id
|
Switch identifier (supplied by the switch).
|
Controller id
|
Controller identifier. Configured on the LSC, and on the switch, with the id option of the tag-control-protocol vsi command.
|
Slave id
|
Slave identifier (supplied by the switch).
|
Keepalive timer
|
VSI master keepalive timeout period (in seconds). Configured on the MPLS LSC through the keepalive option of the tag-control-protocol-vsi command. If no valid message is received by the MPLS LSC within this time period, it sends a keepalive message to the slave.
|
Powerup session id
|
Session ID (supplied by the slave) used at powerup time.
|
Cfg/act retry timer
|
Configured and actual message retry timeout period (in seconds). If no response is received for a command sent by the master within the actual retry timeout period, the message is resent. This applies to most message transmissions. The configured retry timeout value is specified through the retry option of the tag-control-protocol vsi command. The actual retry timeout value is the larger of the configured value and the minimum retry timeout value permitted by the switch.
|
Active session id
|
Session ID (supplied by the slave) for the currently active session.
|
Max retries
|
Maximum number of times that a particular command transmission will be retried by the master. That is, a message may be sent up to <max_retries+1> times. Configured on the MPLS LSC through the retry option of the tag-control-protocol vsi command.
|
Ctrl port log intf
|
Logical interface identifier for the control port, as supplied by the switch.
|
Trap window
|
Maximum number of outstanding trap messages permitted by the master. This is advertised, but not enforced, by the LSC.
|
Max/actual cmd wndw
|
Maximum command window is the maximum number of outstanding (that is, unacknowledged) commands that may be sent by the master before waiting for acknowledgments. This number is communicated to the master by the slave.
The command window is the maximum number of outstanding commands that are permitted by the master, before it waits for acknowledgments. This is always less than the maximum command window.
|
Trap filter
|
This is always "all" for the LSC, indicating that it wants to receive all traps from the slave. This is communicated to the slave by the master.
|
Max checksums
|
Maximum number of checksum blocks supported by the slave.
|
Current VSI version
|
VSI protocol version currently in use by the master for this session.
|
Min/max VSI version
|
Minimum and maximum VSI versions supported by the slave, as last reported by the slave. If both are zero, the slave has not yet responded to the master.
|
Messages sent
|
Number of commands sent to the slave.
|
Inter-slave timer
|
Timeout value associated by the slave for messages it sends to other slaves.
On a VSI-controlled switch with a distributed slave implementation (such as the BPX), VSI messages may be sent between slaves to complete their processing.
For the MPLS LSC VSI implementation to function properly, the value of its retry timer is forced to be at least two times the value of the interslave timer. (See "Cfg/act retry timer" in this table.)
|
Messages received
|
Number of responses and traps received by the master from the slave for this session.
|
Messages outstanding
|
Current number of outstanding messages (that is, commands sent by the master for which responses have not yet been received).
|
Related Commands
Command
|
Description
|
tag-control-protocol vsi
|
Configures the use of VSI on a control port.
|
show controllers vsi status
To display a one-line summary of each VSI-controlled interface, use the show controllers vsi status command in EXEC mode.
show controllers vsi status
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Related Commands
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
If an interface has been discovered by the LSC, but no extended MPLS ATM interface has been associated with it through the extended-port interface configuration command, then the interface name is marked <unknown>, and interface status is marked n/a.
Examples
The following is sample output from the show controllers vsi status command:
Router# show controllers vsi status
Interface Name IF Status IFC State Physical Descriptor
switch control port n/a ACTIVE 12.1.0
XTagATM0 up ACTIVE 12.2.0
XTagATM1 up ACTIVE 12.3.0
<unknown> n/a FAILED-EXT 12.4.0
Table 10 describes the significant fields in the output.
Table 10 show controllers vsi status Field Descriptions
Field
|
Description
|
Interface Name
|
The (Cisco IOS) interface name.
|
IF Status
|
Overall interface status. Can be "up," "down," or "administratively down."
|
IFC State
|
The operational state of the interface, according to the switch. Can be one of the following:
• FAILED_EXT (that is, an external alarm)
• FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
• REMOVED (administratively removed from the switch)
|
Physical Descriptor
|
A string learned from the switch that identifies the interface.
|
show controllers vsi traffic
To display traffic information about VSI-controlled interfaces, VSI sessions, or VCs on VSI-controlled interfaces, use the show controllers vsi traffic command in EXEC mode.
show controllers vsi traffic {descriptor descriptor | session session-num | vc [descriptor
descriptor [vpi vci]]}
Syntax Description
descriptor descriptor
|
Specifies the interface.
|
session session-num
|
Specifies a session number.
|
vpi
|
Virtual path identifier (0 to 4095).
|
vci
|
Virtual circuit identifier (0 to 65535).
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(4)T
|
The VPI range of values was extended to 4095.
|
Usage Guidelines
If none of the keywords is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX switch, the physical descriptor has the form
slot.port. 0
If a session number is specified, the output displays VSI protocol traffic by message type. The VC traffic display is also displayed by the show xmplsatm vc cross-connect traffic descriptor command.
Examples
The following is sample output from the show controllers vsi traffic command:
Router# show controllers vsi traffic
Interface: switch control port
Rx cells: 304250 Rx cells discarded: 0
Tx cells: 361186 Tx cells discarded: 0
Rx header errors: 4294967254 Rx invalid addresses (per card): 80360
Last invalid address: 0/53
Rx cells: 202637 Rx cells discarded: 0
Tx cells: 194979 Tx cells discarded: 0
Rx header errors: 4294967258 Rx invalid addresses (per card): 80385
Last invalid address: 0/32
Rx cells: 182295 Rx cells discarded: 0
Tx cells: 136369 Tx cells discarded: 0
Rx header errors: 4294967262 Rx invalid addresses (per card): 80372
Last invalid address: 0/32
Table 11 describes the significant fields shown in the display.
Table 11 show controllers vsi traffic Field Descriptions
Field
|
Description
|
Phys desc
|
Physical descriptor of the interface.
|
Interface
|
The Cisco (IOS) interface name.
|
Rx cells
|
Number of cells received on the interface.
|
Tx cells
|
Number of cells transmitted on the interface.
|
Rx cells discarded
|
Number of cells received on the interface that were discarded due to traffic management.
|
Tx cells discarded
|
Number of cells that could not be transmitted on the interface due to traffic management and which were therefore discarded.
|
Rx header errors
|
Number of cells that were discarded due to ATM header errors.
|
Rx invalid addresses
|
Number of cells received with an invalid address (that is, an unexpected VPI/VCI combination). With the Cisco BPX switch, this count is of all such cells received on all interfaces in the port group of this interface.
|
Last invalid address
|
Number of cells received on this interface with ATM cell header errors.
|
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
Router# show controllers vsi traffic session 9
Sw Get Cnfg Cmd: 3656 Sw Get Cnfg Rsp: 3656
Sw Cnfg Trap Rsp: 0 Sw Cnfg Trap: 0
Sw Set Cnfg Cmd: 1 Sw Set Cnfg Rsp: 1
Sw Start Resync Cmd: 1 Sw Start Resync Rsp: 1
Sw End Resync Cmd: 1 Sw End Resync Rsp: 1
Ifc Getmore Cnfg Cmd: 1 Ifc Getmore Cnfg Rsp: 1
Ifc Cnfg Trap Rsp: 4 Ifc Cnfg Trap: 4
Ifc Get Stats Cmd: 8 Ifc Get Stats Rsp: 8
Conn Cmt Cmd: 73 Conn Cmt Rsp: 73
Conn Del Cmd: 50 Conn Del Rsp: 0
Conn Get Stats Cmd: 0 Conn Get Stats Rsp: 0
Conn Cnfg Trap Rsp: 0 Conn Cnfg Trap: 0
Conn Bulk Clr Stats Cmd: 0 Conn Bulk Clr Stats Rsp: 0
Gen Err Rsp: 0 Gen Err Rsp: 0
Table 12 describes the significant fields shown in the display.
Table 12 show controllers vsi traffic session Field Descriptions
Field
|
Description
|
Sw Get Cnfg Cmd
|
Number of VSI "get switch configuration command" messages sent.
|
Sw Cnfg Trap Rsp
|
Number of VSI "switch configuration asynchronous trap response" messages sent.
|
Sw Set Cnfg Cmd
|
Number of VSI "set switch configuration command" messages sent.
|
Sw Start Resync Cmd
|
Number of VSI "set resynchronization start command" messages sent.
|
Sw End Resync Cmd
|
Number of VSI "set resynchronization end command" messages sent.
|
Ifc Getmore Cnfg Cmd
|
Number of VSI "get more interfaces configuration command" messages sent.
|
Ifc Cnfg Trap Rsp
|
Number of VSI "interface configuration asynchronous trap response" messages sent.
|
Ifc Get Stats Cmd
|
Number of VSI "get interface statistics command" messages sent.
|
Conn Cmt Cmd
|
Number of VSI "set connection committed command" messages sent.
|
Conn Del Cmd
|
Number of VSI "delete connection command" messages sent.
|
Conn Get Stats Cmd
|
Number of VSI "get connection statistics command" messages sent.
|
Conn Cnfg Trap Rsp
|
Number of VSI "connection configuration asynchronous trap response" messages sent.
|
Conn Bulk Clr Stats Cmd
|
Number of VSI "bulk clear connection statistics command" messages sent.
|
Gen Err Rsp
|
Number of VSI "generic error response" messages sent or received.
|
Sw Get Cnfg Rsp
|
Number of VSI "get connection configuration command response" messages received.
|
Sw Cnfg Trap
|
Number of VSI "switch configuration asynchronous trap" messages received.
|
Sw Set Cnfg Rsp
|
Number of VSI "set switch configuration response" messages received.
|
Sw Start Resync Rsp
|
Number of VSI "set resynchronization start response" messages received.
|
Sw End Resync Rsp
|
Number of VSI "set resynchronization end response" messages received.
|
Ifc Getmore Cnfg Rsp
|
Number of VSI "get more interfaces configuration response" messages received.
|
Ifc Cnfg Trap
|
Number of VSI "interface configuration asynchronous trap" messages received.
|
Ifc Get Stats Rsp
|
Number of VSI "get interface statistics response" messages received.
|
Conn Cmt Rsp
|
Number of VSI "set connection committed response" messages received.
|
Conn Del Rsp
|
Number of VSI "delete connection response" messages received.
|
Conn Get Stats Rsp
|
Number of VSI "get connection statistics response" messages received.
|
Conn Cnfg Trap
|
Number of VSI "connection configuration asynchronous trap" messages received.
|
Conn Bulk Clr Stats Rsp
|
Number of VSI "bulk clear connection statistics response" messages received.
|
unused, unknown
|
"Unused" messages are those whose function codes are recognized as being part of the VSI protocol, but which are not used by the MPLS LSC and, consequently, are not expected to be received or sent.
"Unknown" messages have function codes that the MPLS LSC does not recognize as part of the VSI protocol.
|
TOTAL
|
Total number of VSI messages sent or received.
|
show controllers xmplsatm
To display information about an extended MPLS ATM (XmplsATM) interface controlled through the VSI protocol, use the show controllers xmplsatm command in EXEC mode.
show controllers xmplsatm interface-number
Syntax Description
interface-number
|
Interface number of the XmplsATM.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
12.2(4)T
|
This command was updated to reflect the MPLS IETF terminology.
|
Usage Guidelines
Per-interface information includes the following:
•
Interface name
•
Physical descriptor
•
Interface status
•
Physical interface state (supplied by the switch)
•
Acceptable VPI and VCI ranges
•
Maximum cell rate
•
Available cell rate (forward/backward)
•
Available channels
Examples
The following is sample output from the show controllers xmplsatm command specifying interface 0:
Router# show controllers xmplsatm 0
Interface XTagATM0 is up
Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI1)
Control interface ATM1/0 is up
Physical descriptor is 10.2.0
Logical interface 0x000A0200 (0.10.2.0)
Oper state ACTIVE, admin state UP
VPI range 1-255, VCI range 32-65535
VPI is not translated at end of link
Tag control VC need not be strictly in VPI/VCI range
Available channels: ingress 30, egress 30
Maximum cell rate: ingress 300000, egress 300000
Available cell rate: ingress 300000, egress 300000
Endpoints in use: ingress 7, egress 8, ingress/egress 1
Rx cells 134747
rx cells discarded 0, rx header errors 0
rx invalid addresses (per card): 52994
last invalid address 0/32
Tx cells 132564
tx cells discarded: 0
Table 13 describes the significant fields shown in the display.
Table 13 show controllers xmplsatm Field Descriptions
Field
|
Description
|
Interface XTagATM0 is up
|
The overall status of the interface, which can be "up," "down," or "administratively down."
|
Hardware is Tag-Controlled ATM Port
|
The hardware type.
If the XmplsATM interface is assigned to a switch port, the following text is displayed as well:
on switch-type switch switch-name
The string indicates the type of switch and the switch name learned from the switch.
If the XmplsATM interface not assigned to a switch interface, the following text is displayed:
Not bound to a control interface and switch port
If the XmplsATM interface is assigned to a switch interface, but the target switch interface has not been discovered by the LSC, the following text is displayed:
Bound to undiscovered switch port (id number)
The variable number is the logical interface ID in hexadecimal notation.
|
Control interface ATM1/0 is up
|
The XmplsATM interface was assigned to the VSI master, whose control interface is ATM1/0. This control interface is up.
|
Physical descriptor is...
|
A string identifying the interface that was learned from the switch.
|
Logical interface
|
A 32-bit entity, learned from the switch, that identifies the interface. It appears in both hexadecimal and dotted quad notation.
|
Oper state
|
Operational state of the interface, according to the switch. The state can be one of the following:
• ACTIVE
• FAILED_EXT (that is, an external alarm)
• FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
• REMOVED (administratively removed from the switch)
|
admin state
|
Administrative state of the interface, which can be either Up or Down.
|
VPI range 1 to 4095
|
The allowable VPI range for the interface that was configured on the switch.
|
VCI range 32 to 65535
|
Allowable VCI range for the interface that was configured on, or determined by, the switch.
|
LSC control VC need not be strictly in VPI or VCI range
|
Label control VC does not need to be within the range specified by VPI range, but may be on VPI 0 instead.
|
Available channels
|
Number of channels (endpoints) that are currently free to be used for cross-connects.
|
Maximum cell rate
|
Maximum cell rate for the interface, which was configured on the switch.
|
Available cell rate
|
Cell rate that is currently available for new cross-connects on the interface.
|
Endpoints in use
|
Number of endpoints (channels) in use on the interface, broken down by anticipated traffic flow, as follows:
• Ingress—Endpoints carry traffic into the switch
• Egress—Endpoints carry traffic away from the switch
• Ingress/egress—Endpoints carry traffic in both directions
|
Rx cells
|
Number of cells received on the interface.
|
rx cells discarded
|
Number of cells received on the interface that were discarded due to traffic management actions (rx header errors).
|
rx header errors
|
Number of cells received on the interface with cell header errors.
|
rx invalid addresses (per card)
|
Number of cells received with invalid addresses (that is, unexpected VPI or VCI). On the BPX switch, this counter is maintained per port group (not per interface).
|
last invalid address
|
Address of the last cell received on the interface with an invalid address (for example, 0/32).
|
Tx cells
|
Number of cells transmitted from the interface.
|
tx cells discarded
|
Number of cells intended for transmission from the interface that were discarded due to traffic management actions.
|
Related Commands
Command
|
Description
|
show controllers vsi descriptor
|
Displays information about a switch interface discovered by the MPLS LSC through the VSI.
|
show controllers XTagATM
To display information about an extended MPLS ATM interface controlled through the VSI protocol (or, if an interface is not specified, to display information about all extended MPLS ATM interfaces controlled through the VSI protocol), use the show controllers XTagATM command in EXEC mode.
show controllers XTagATM if-num
Syntax Description
if-num
|
Specifies the interface number.
|
Defaults
No default behavior or values.
Command Modes
EXEC
Command History
Release
|
Modification
|
12.0(5)T
|
This command was introduced.
|
Usage Guidelines
Per-interface information includes the following:
•
Interface name
•
Physical descriptor
•
Interface status
•
Physical interface state (supplied by the switch)
•
Acceptable VPI and VCI ranges
•
Maximum cell rate
•
Available cell rate (forward/backward)
•
Available channels
Similar information appears if you enter the show controllers vsi descriptor EXEC command. However, you must specify an interface by its (switch-supplied) physical descriptor, instead of its Cisco IOS interface name. For the Cisco BPX switch, the physical descriptor has the form slot.port.0.
Examples
In this example, the sample output is from the show controllers XTagATM command specifying interface 0:
Router# show controllers XTagATM 0
Interface XTagATM0 is up
Hardware is Tag-Controlled ATM Port (on BPX switch BPX-VSI1)
Control interface ATM1/0 is up
Physical descriptor is 10.2.0
Logical interface 0x000A0200 (0.10.2.0)
Oper state ACTIVE, admin state UP
VPI range 1-255, VCI range 32-65535
VPI is not translated at end of link
Tag control VC need not be strictly in VPI/VCI range
Available channels: ingress 30, egress 30
Maximum cell rate: ingress 300000, egress 300000
Available cell rate: ingress 300000, egress 300000
Endpoints in use: ingress 7, egress 8, ingress/egress 1
Rx cells 134747
rx cells discarded 0, rx header errors 0
rx invalid addresses (per card): 52994
last invalid address 0/32
Tx cells 132564
tx cells discarded: 0
Table 14 describes the significant fields in the output.
Table 14 show controllers XTagATM Field Descriptions
Field
|
Description
|
Interface XTagATM0 is up
|
Indicates the overall status of the interface. May be "up," "down," or "administratively down."
|
Hardware is Tag-Controlled ATM Port
|
Indicates the hardware type.
If the XTagATM was successfully associated with a switch port, a description of the form (on <switch_type> switch <name>) follows this field, where <switch_type> indicates the type of switch (for example, BPX), and the name is an identifying string learned from the switch.
If the XTagATM interface was not bound to a switch interface (with the extended-port interface configuration command), then the label "Not bound to a control interface and switch port" appears.
If the interface has been bound, but the target switch interface has not been discovered by the LSC, then the label "Bound to undiscovered switch port (id <number>)" appears, where <number> is the logical interface ID in hexadecimal notation.
|
Control interface ATM1/0 is up
|
Indicates that the XTagATM interface was bound (with the extended-port interface configuration command) to the VSI master whose control interface is ATM1/0 and that this control interface is up.
|
Physical descriptor is...
|
A string identifying the interface that was learned from the switch.
|
Logical interface
|
This 32-bit entity, learned from the switch, uniquely identifies the interface. It appears in both hexadecimal and dotted quad notation.
|
Oper state
|
Operational state of the interface, according to the switch. Can be one of the following:
• ACTIVE
• FAILED_EXT (that is, an external alarm)
• FAILED_INT (indicates the inability of the MPLS LSC to communicate with the VSI slave controlling the interface, or another internal failure)
• REMOVED (administratively removed from the switch)
|
admin state
|
Administrative state of the interface, according to the switch—either "Up" or "Down."
|
VPI range 1 to 255
|
Indicates the allowable VPI range for the interface that was configured on the switch.
|
VCI range 32 to 65535
|
Indicates the allowable VCI range for the interface that was configured on, or determined by, the switch.
|
LSC control VC need not be strictly in VPI or VCI range
|
Indicates that the label control VC does not need to be within the range specified by VPI range, but may be on VPI 0 instead.
|
Available channels
|
Indicates the number of channels (endpoints) that are currently free to be used for cross-connects.
|
Maximum cell rate
|
Maximum cell rate for the interface, which was configured on the switch.
|
Available cell rate
|
Cell rate that is currently available for new cross-connects on the interface.
|
Endpoints in use
|
Number of endpoints (channels) in use on the interface, broken down by anticipated traffic flow, as follows:
• Ingress—Endpoints carry traffic into the switch
• Egress—Endpoints carry traffic away from the switch
• Ingress/egress—Endpoints carry traffic in both directions
|
Rx cells
|
Number of cells received on the interface.
|
rx cells discarded
|
Number of cells received on the interface that were discarded due to traffic management actions (rx header errors).
|
rx header errors
|
Number of cells received on the interface with cell header errors.
|
rx invalid addresses (per card)
|
Number of cells received with invalid addresses (that is, unexpected VPI or VCI.). On the BPX, this counter is maintained per port group (not per interface).
|
last invalid address
|
Address of the last cell received on the interface with an invalid address (for example, 0/32).
|
Tx cells
|
Number of cells sent from the interface.
|
tx cells discarded
|
Number of cells intended for transmission from the interface that were discarded due to traffic management actions.
|
Related Commands
Command
|
Description
|
show controllers vsi descriptor
|
Displays information about a switch interface discovered by the MPLS LSC through the VSI.
|
show interface stats
To display numbers of packets that were process switched, fast switched, and distributed switched, use the show interface stats command in EXEC mode.
show interface type number stats
Syntax Description
type number
|
Interface type and number about which to display statistics.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.0
|
This command was introduced.
|
Usage Guidelines
Use this command on the RP.
Note
When fast switching is configured on the outbound interface, and RSP optimum, RSP flow, and VIP DFS switching modes are all specified on the incoming interface, the interface on which RSP optimum, RSP flow, and VIP DFS switching modes is not enabled can still show packets switched out via those switching paths when packets are received from other interfaces with RSP optimum, RSP flow, and VIP DES switching modes enabled.
Examples
The following is sample output from the show interface stats command:
Router# show interface fddi 3/0/0 stats
Switching path Pkts In Chars In Pkts Out Chars Out
Processor 3459994 1770812197 4141096 1982257456
Route cache 10372326 3693920448 439872 103743545
Distributed cache 19257912 1286172104 86887377 1184358085
Total 33090232 2455937453 91468345 3270359086
Table 15 describes the significant fields in the display.
Table 15 show interface stats Field Descriptions
Field
|
Description
|
Fddi3/0/0
|
Interface for which information is shown.
|
Switching path
|
Column heading for the various switching paths below it.
|
Pkts In
|
Number of packets received in each switching mechanism.
|
Chars In
|
Number of characters received in each switching mechanism.
|
Pkts Out
|
Number of packets sent out each switching mechanism.
|
Chars Out
|
Number of characters sent out each switching mechanism.
|