|
|
To specify or replace the ring number of the emulated LAN 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
Syntax Description
elan-name Name of the emulated LAN. The maximum length of the name is 32 characters. segment-number Segment number to be assigned to the emulated LAN. The number ranges from 1 to 4095.
Defaults
No emulated LAN name or segment number is provided.
Command Modes
Database configuration
Command History
11.3 This command was introduced.
Release
Modification
Usage Guidelines
This command is ordinarily used for Token Ring LANE.
The same LANE ring number cannot be assigned to more than one emulated LAN.
The no form of this command deletes the relationships.
Examples
The following example specifies a ring number of 1024 for the emulated LAN red:
name red local-seg-id 1024
Related Commands
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.
Command
Description
To set the 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
Syntax Description
elan-name Specifies the name of the ELAN.
Defaults
Preemption is off by default.
Command Modes
LANE database configuration
Command History
11.3 This command was introduced.
Release
Modification
Usage Guidelines
In prior releases, when the primary LES failed, 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. In this release, 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 MYELAN preempt
To specify or replace the ATM address of the LANE server for the emulated LAN 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]
Syntax Description
elan-name Name of the emulated LAN. Maximum length is 32 characters. atm-address LANE server's ATM address. restricted | un-restricted (Optional) Membership in the named emulated LAN is restricted to the LANE clients explicitly defined to the emulated LAN 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
11.0 This command was introduced. 11.2 The following keywords were added:
Release
Modification
Usage Guidelines
Emulated LAN names must be unique within one named LANE configuration database.
Specifying an existing emulated LAN name with a new LANE server ATM address adds the LANE server ATM address for that emulated LAN 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 emulated LANs. The clients that can be assigned to the eng and mkt emulated LANs are specified using the client-atm-address commands. All other clients are assigned to the man emulated LAN.
lane database example3 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 default-name man
Related Commands
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.
Command
Description
To enable the exchange of information with a neighboring router, use the neighbor activate command in address family submode or router configuration mode. To disable the exchange of an address with a neighboring router, use the no form of this command.
neighbor {ip-address| peer-group-name} activate
Syntax Description
ip-address IP address of the neighboring router. peer-group-name Name of BGP peer group.
Defaults
For all other address families, address exchange is disabled by default. You can explicitly activate the default command using the appropriate address family submode.
Command Modes
Address family submode
Router configuration
Command History
12.0(5)T This command was introduced.
Release
Modification
Usage Guidelines
Use this command to enable or disable the exchange of addresses with a neighboring router.
Examples
The following example activates advertisement of NLRI for address family VPN IPv4 for all neighbors in the BGP peer group PEPEER and for the neighbor 144.0.0.44:
address-family vpnv4 neighbor PEPEER activate neighbor 144.0.0.44 activate exit-address-family
Related Commands
Enters the address family submode for configuring routing protocols, such as BGP, RIP, and static routing. exit-address-family Exits from the address family submode.
Command
Description
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
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
12.0(7)T This command was introduced.
Release
Modification
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:
1. One VRF receives prefixes with ASNs from all PE routers and then advertises them to neighboring PE routers.
2. 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:
router bgp 100 address-family ipv4 vrf vrf1 neighbor 192.168.255.255 allowas-in 6
Related Commands
address-family Enters the address family submode used to configure routing protocols including BGP, OSPF, RIP, and static routing.
Command
Description
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
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
12.0(7)T This command was introduced.
Release
Modification
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.
router bgp 100 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
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.
Command
Description
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 for network-id is 1), use the no form of this command.
network-id id
Syntax Description
id Specifies the network ID of the MPOA server.
Defaults
The default value for network-id is 1.
Command Modes
MPS configuration
Command History
11.3(3a)WA4(5) This command was introduced.
Release
Modification
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:
network-id 5
To specify the next IP address in the explicit path, use the next-address command in IP explicit path subcommand mode.
next-address A.B.C.D
Syntax Description
A.B.C.D Specifies the IP address in the explicit path.
Defaults
No default behavior or values.
Command Modes
IP explicit path subcommand
Command History
12.0(5)S This command was introduced.
Release
Modification
Examples
The following commands assign the number 60 to the IP explicit path, set the state of the path to be enabled, and specify 3.3.27.3 as the next IP address in the list of IP addresses.
configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
mpls traffic-eng tunnels
ip explicit-path identifier 60 enable
next-address 3.3.27.3
Explicit Path identifier 60:
1: next-address 3.3.27.3
Related Commands
append-after Inserts a path entry after a specific index number. index Inserts or modifies a path entry at a specific index. ip explicit-path Enters the subcommand mode for IP explicit paths to create or modify the named path. list Displays all or part of the explicit path or paths. show ip explicit-paths Displays configured IP explicit paths.
Command
Description
To create routing and forwarding tables for a VRF, use the rd command in VRF submode.
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. An RD must be configured for a VRF to be functional.
Command Modes
VRF submode
Command History
12.0(5)T This command was introduced.
Release
Modification
Usage Guidelines
A route distinguisher (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.
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:
ip vrf vrf_blue rd 100:3 ip vrf vrf_red 173.13.0.12:200
Related Commands
Configures a VRF routing table. Displays the set of defined VRFs and associated interfaces.
Command
Description
To create a route-target extended community for a VRF, use the route-target command in VRF submode. 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
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 submode
Command History
12.0(5)T This command was introduced.
Release
Modification
Usage Guidelines
The route-target command creates lists of import and export route-target extended communities for the specified VRF. Execute 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:
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 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).
ip vrf vrf_blue route-target both 1000:1 route-target export 1000:2 route-target import 173.27.0.130:200
Related Commands
ip vrf Configures a VRF routing table. import map Configures an import route map for a VRF.
Command
Description
To configure policy routing to verify if the next hop(s) of a route map is a CDP neighbor(s) before policy routing to that next hop, use the set ip next-hop verify-availability route-map configuration command.
set ip next-hop verify-availabilitySyntax Description
This command has no arguments or keywords.
Command Modes
Route-map configuration
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
This command might be used in a case such as you have some traffic traveling via a satellite to a next hop. It might be prudent to verify that the next hop is reachable before trying to policy route to it.
This command has the following restrictions:
If the router is policy routing packets to the next hop and the next hop happens to be down, the router will try unsuccessfully to use Address Resolution Protocol (ARP) for the next hop (which is down). This behavior will continue forever.
To prevent this situation from occurring, use this command to configure the router to first verify that the next hop(s) of the route map is the router's CDP neighbor(s) before routing to that next hop.
This command is optional because some media or encapsulations do not support CDP, or it may not be a Cisco device that is sending the router traffic.
If this command is set and the next hop is not a CDP neighbor, the router looks to the subsequent next hop, if there is one. If there is none, the packets simply are not policy routed.
If this command is not set, the packets either are successfully policy routed or remain forever unrouted.
If you want to selectively verify availability of only some next hops, you can configure different route-map entries (under the same route-map name) with different criteria (using access list matching or packet size matching), and use the set ip next-hop verify-availability command selectively.
Examples
The following example configures CEF, NetFlow, and NetFlow with flow acceleration. It also configures policy routing to verify that next hop 50.0.0.8 of route map test is a CDP neighbor before the router tries to policy route to it.
If the first packet is being policy routed via route map test sequence 10, the subsequent packets of the same flow always take the same route map test sequence 10, not route map test sequence 20, because they all match or pass access list 1 check. Therefore, policy routing can be flow-accelerated by bypassing the access list check.
ip cef ip flow-cache feature-accelerate interface ethernet0/0/1 ip route-cache flow ip policy route-map test route-map test permit 10 match ip address 1 set ip precedence priority set ip next-hop 50.0.0.8 set ip next-hop verify-availability route-map test permit 20 match ip address 101 set interface Ethernet0/0/3 set ip tos max-throughput
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-idSyntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Route-map configuration
Command History
12.0(7)T This command was introduced.
Release
Modification
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 router bgp 100 neighbor 172.19.89. 62 remote-as 100 access-list 1 permit 192.168.0.0 route-map vpn1-site1-map permit 10 match ip address 1 set ospf router-id
Related Commands
router ospf Enables OSPF routing, which places you in the router configuration mode.
Command
Description
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
Syntax Description
count Shortcut-setup frame count. The default is 10 frames.
Defaults
The default is 10 frames.
Command Modes
MPC configuration mode.
Command History
11.3(3a)WA4(5) This command was introduced.
Release
Modification
Examples
The following example sets the shortcut-setup frame count to 5 for the MPC:
shortcut-frame-count 5
Related Commands
Overrides the control ATM address of an MPC or MPS. Defines an MPC with a specified name. Sets the shortcut-setup frame time (in seconds) for the MPC.
Command
Description
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
Syntax Description
time (Optional) Shortcut-setup frame time in seconds.
Defaults
The default is 1 second.
Command Modes
MPC configuration
Command History
11.3(3a)WA4(5) This command was introduced.
Release
Modification
Examples
The following example sets the shortcut-setup frame time to 7 for the MPC:
shortcut-frame-time 7
Related Commands
Overrides the control ATM address of an MPC or MPS. Defines an MPC with a specified name. 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.
Command
Description
To display Cisco Express Forwarding (CEF) adjacency table information, use the show adjacency command in EXEC mode.
show adjacency [detail]
Syntax Description
detail (Optional) Displays detailed adjacency information, including Layer 2 information.
Command Modes
EXEC
Command History
11.2 GS This command was introduced to support the Cisco 12012 Gigabit Switch Router. 11.1 CC Multiple platform support was added.
Release
Modification
Usage Guidelines
This command is available only on routers that have RP cards.
Examples
The following is sample output from the show adjacency detail command:
show adjacency detail Protocol Interface Address IP Tunnel0 point2point(3) (incomplete) 0 packets, 0 bytes FIB 00:02:45 IP Ethernet1/0/0 192.168.177.15(6) 0 packets, 0 bytes 0060837BEFA0 Protocol Interface Address 0060836FA7000800 ARP 03:59:44 igrp 622 00:04:14 IP Ethernet0/0 192.168.233.88(5) 0 packets, 0 bytes 0060837BEFA0 0060836FA7000800 ARP 03:59:36 IP FastEthernet2/0/0 172.16.1.106 (11) (incomplete) 0 packets, 0 bytes IP FastEthernet2/0/0 172.26.1.106 (11) (incomplete) 0 packets, 0 bytes
Table 3 describes the fields shown in the output.
| Field | Description |
|---|---|
Protocol | The routing protocol configured on the interface. |
Interface | The type of interface configured. |
Address | The address of the interface. |
Routing protocol | The method by which the adjacency was learned. |
Adjacent next hop | The MAC address of the adjacent router. |
Time stamp | The time left before the adjacency rolls out of the adjacency table. Once it rolls out, a packet must use the same next hop to the destination. |
Related Commands
clear adjacency Clears CEF adjacency table.
Command
Description
To display information about private ATM virtual circuits (VCs), use the show atm vc command in privileged EXEC mode.
show atm vc [vcd]Private VCs exist on the control interface of a LSC to support corresponding VCs on an extended label ATM interface.
Syntax Description
vcd (Optional) Specifies the virtual circuit about which to display information.
Command Modes
Privileged EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
VCs on the extended label ATM interfaces do not show up in the show atm vc command output. Instead, the show xtagatm vc command provides a similar output that shows information only on extended label ATM VCs.
Examples
In the following example, no VCD is specified and private VCs are present.
show atm vc
AAL / Peak Avg. Burst
Interface VCD VPI VCI Type Encapsulation Kbps Kbps Cells Status
ATM1/0 1 0 40 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 2 0 41 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 3 0 42 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 4 0 43 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 5 0 44 PVC AAL5-SNAP 0 0 0 ACTIVE
ATM1/0 15 1 32 PVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 17 1 34 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 26 1 43 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 28 1 45 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 29 1 46 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE
Table 4 lists the significant fields in this display.
When you specify a VCD value and the VCD corresponds to that of a private VC on a control interface, the display output appears as follows:
show atm vc 15 ATM1/0 33 1 50 TVC AAL5-XTAGATM 0 0 0 ACTIVE
ATM1/0: VCD: 15, VPI: 1, VCI: 32, etype:0x8, AAL5 - XTAGATM, Flags: 0xD38 PeakRate: 0, Average Rate: 0, Burst Cells: 0, VCmode: 0x0
XTagATM1, VCD: 1, VPI: 0, VCI: 32
OAM DISABLED, InARP DISABLED
InPkts: 38811, OutPkts: 38813, InBytes: 2911240, OutBytes: 2968834
InPRoc: 0, OutPRoc: 0, Broadcasts: 0
InFast: 0, OutFast: 0, InAS: 0, OutAS: 0
OAM F5 cells sent: 0, OAM cells received: 0
Status: ACTIVE
Table 4 describes the fields shown in the output.
| Field | Description |
|---|---|
ATM1/0 | Interface slot and number. |
VCD | Virtual circuit descriptor (virtual circuit number). |
VPI | Virtual path identifier. |
VCI | Virtual circuit identifier. |
etype | Ethernet type. |
AAL5- XTAGATM | Type of ATM adaptation layer (AAL) and encapsulation. A private VC has AAL5 and encapsulation XTAGATM. |
Flags | Bit mask describing virtual circuit information. The flag values are summed to result in the displayed value. 0x10000 ABR VC |
|
|
| 0x6 AAL5-ILMI |
PeakRate | Number of packets transmitted at the peak rate. |
Average Rate | Number of packets transmitted at the average rate. |
Burst Cells | Value that, when multiplied by 32, equals the maximum number of ATM cells the virtual circuit can transmit at the peak rate of the virtual circuit. |
VCmode | AIP-specific or NPM-specific register describing the usage of the virtual circuit. Contains values such as rate queue, peak rate, and AAL mode, which are also displayed in other fields. |
xtagatm1 | Interface of corresponding extended label ATM VC. |
VCD | Virtual circuit descriptor (virtual circuit number) of the corresponding extended label ATM VC. |
VPI | Virtual path identifier of the corresponding extended label ATM VC. |
VCI | Virtual channel identifier of the corresponding extended label ATM VC. |
OAM frequency | Seconds between OAM loopback messages or DISABLED if OAM is not in use on this VC. |
InARP frequency | Minutes between InARP messages, or DISABLED if InARP is not in use on this VC. |
InPkts | Total number of packets received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets. |
OutPkts | Total number of packets sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets. |
InBytes | Total number of bytes received on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets. |
OutBytes | Total number of bytes sent on this virtual circuit. This number includes all silicon-switched, fast-switched, autonomous-switched, and process-switched packets. |
InPRoc | Number of process-switched input packets. |
OutPRoc | Number of process-switched output packets. |
Broadcasts | Number of process-switched broadcast packets. |
InFast | Number of fast-switched input packets. |
OutFast | Number of fast-switched output packets. |
InAS | Number of autonomous-switched or silicon-switched input packets. |
OutAS | Number of autonomous-switched or silicon-switched output packets. |
OAM F5 cells sent | Number of OAM cells sent on this virtual circuit. |
OAM cells received | Number of OAM cells received on this virtual circuit. |
Status | Displays the current state of the specified ATM interface. |
To display which packets the line cards dropped or to display which packets were not express forwarded, use the show cef command in 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
EXEC
Command History
11.2 GS This command was introduced to support the Cisco 12012 Gigabit Switch Router. 11.1 CC Multiple platform support was added.
Release
Modification
Usage Guidelines
This command is available only on routers that have RP cards.
A line card might drop packets because of encapsulation failure, absence route information, or absence of adjacency information.
A packet is sent to a different switching path because Cisco Express Forwarding (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.
Examples
The following is sample output from the show cef drop command:
show cef drop CEF Drop Statistics Slot Encap_fail Unresolved Unsupported No_route No_adj ChksumErr RP 4 89 0 4 0 0 1 0 0 0 0 0 0 2 0 0 5 0 0 5
Table 5 describes the fields shown in the output.
| Field | Description |
|---|---|
Slot | The slot number on which the packets were received. |
Encap_fail | Indicates the number of packets dropped after the limit was reached for incomplete packets with no adjacency route. |
Unresolved | Indicates the number of packets dropped because the route for the prefix was not resolved. |
Unsupported | Indicates the number of packets received for which the adjacency route information was dropped due to unsupported features. |
No_route | No route definition is included in the prefix table. |
No_adj | The prefix is resolved, but the adjacent route is not indicated. |
ChksumErr | Indicates the number of packets received with a checksum error. |
The following is sample output from the show cef not-cef-switched command:
show cef not-cef-switched CEF Packets passed on to next switching layer Slot No_adj No_encap Unsuppted Redirect Receive Bad_ttl Options Access RP 0 0 0 0 91584 0 0 0 1 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0
Table 6 describes the fields shown in the output.
| Field | Meaning |
|---|---|
No_adj | Indicates the number of packets sent to the line card to ARP for the adjacent route. |
No_encap | Number of encapsulated packets received. |
Unsupported Redirect | Number of packets with unsupported features and redirected to another switching layer or location for processing. |
Related Commands
show cef interface Displays CEF-related interface information. show cef linecard Displays CEF-related interface information by line card.
Command
Description
To display Cisco Express Forwarding (CEF) related interface information, use the show cef interface command in EXEC mode.
show cef interface type number [detail]
Syntax Description
type number Interface type and number about which to display CEF-related information. detail (Optional) Displays detailed CEF information for the specified interface type and number.
Command Modes
EXEC
Command History
11.2 GS This command was introduced to support the Cisco 12012 Gigabit Switch Router. 11.1 CC Multiple platform support was added.
Release
Modification
Usage Guidelines
This command is available on routers that have RP cards and line cards.
The detail keyword displays more CEF-related information for the specified interface.
You can use this command to show the CEF state on an individual interface.
Examples
The following is sample output from the show cef interface detail command for Ethernet interface 0:
show cef interface E0 detail Ethernet1/0/0 is up (if_number 6) Internet address is 172.19.177.20/24 ICMP redirects are always sent Per-packet load balancing is disabled Inbound access list is 10 Outbound access list is not set Hardware idb is Ethernet1/0/0 Fast switching type 1, interface type 5 IP Distributed CEF switching enabled IP Feature CEF switching turbo vector Fast flags 0x4. ifindex 5(5) Slot 1 Slot unit 0 VC -1 Hardware transmit queue ptr 0x48001A00 (0x48001A00) >- debugging purposes Transmit limit accumulator 0x48001A02 (0x48001A02) IP MTU 1500
Table 7 describes the fields shown in the output.
| Field | Description |
|---|---|
interface type number is {up | down} | Indicates status of the interface. |
Internet address | Internet address of the interface. |
ICMP packets are {always sent | never sent} | Indicates how packet forwarding is configured. |
Per-packet load balancing | Status of load balancing in use on the interface (enabled or disabled). |
Inbound access list {# | Not set} | Number of access lists defined for the interface. |
Outbound access list | Number of access lists defined for the interface. |
Hardware idb is type number | Interface type and number configured. |
Fast switching type | Used for troubleshooting; indicates switching mode in use. |
IP Distributed CEF switching {enabled | disabled} | Indicates the switching path used. |
Slot n Slot unit n | The slot number. |
Hardware transmit queue | Indicates the number of packets in the transmit queue. |
Transmit limit accumulator | Indicates the maximum number of packets allowed in the transmit queue. |
IP MTU | The value of the MTU size set on the interface. |
Related Commands
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.
Command
Description
To display Cisco Express Forwarding (CEF) related interface information by line card, use the show cef linecard command in EXEC mode.
show cef linecard [slot-number] [detail]
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.
Command Modes
EXEC
Command History
11.2 GS This command was introduced to support the Cisco 12012 Gigabit Switch Router. 11.1 CC Multiple platform support was added.
Release
Modification
Usage Guidelines
This command is available only on routers that have RP cards.
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 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 command. The command displays information for the line cards.
show cef linecard CEF table version 115705, 45877 routes Slot CEF-ver MsgSent XdrSent Seq MaxSeq LowQ HighQ Flags 1 238 668 9641 616 616 0 0 up, sync 2 238 683 10782 619 629 0 0 up, sync
Table 8 describes the fields shown in the output.
| Field | Description |
|---|---|
CEF table version | The FIB table version. |
XdrSent | IPC information elements (xdrs) packed into IPC messages sent from the RP to the line card. |
MsgSent | Number of IPC messages sent. |
Seq | Sequence number for the line card. |
MaxSeq | Maximum sequence expected by the line card. |
LowQ/HighQ | Number of xdr elements in LowQ and HighQ. |
Flags | Indicates the status of the line card. Possible states are the following:
|
The following is sample output from the show cef linecard detail command for the line card in slot number 2:
show cef linecard 2 detail CEF line card slot number 2, status up, sync, disabled line card CEF version number 238 Sequence number 616, Maximum sequence number expected 616 Send failed 0, Out Of Sequence 0 line card CEF reset 2, reloaded 2 92299/15/91 prefix/adjacency/interface elements queued 49641 elements packed in 668 messages(1341286 bytes) sent 0/0 xdr elements in LowQ/HighQ Input packets 0, bytes 0 <--- line card stats Output packets 0, bytes 0, drops 0
Related Commands
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.
Command
Description
To display information about an ATM interface that is configured with the tag-control-protocol vsi command to control an external switch, or, if an interface is not specified, 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) Interface number.
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Examples
The following is sample output from the show controllers vsi control-interface command:
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 LSC through VSI over the control interface.
Related Commands
tag-control-protocol vsi Configures the use of VSI on a particular master control port.
Command
Description
To display information about a switch interface discovered by the LSC through VSI, or, if no descriptor is specified, about all such discovered interfaces, use the show controllers vsi descriptor command in EXEC mode. You specify an interface by its (switch-supplied) physical descriptor.
show controllers vsi descriptor [descriptor]
Syntax Description
descriptor (Optional) Physical descriptor. For the BPX, the physical descriptor has the following form:
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
Per-interface information includes the interface name, the physical descriptor, the interface status, the physical interface state (supplied by the switch), acceptable VPI/VCI ranges, maximum cell rate, available cell rate (forward/backward), and available channels.
Similar information is displayed when you enter the show controllers XTagATM command. However, you must specify an IOS interface name instead of a physical descriptor.
Examples
The following is sample output from the show controllers vsi descriptor command:
show controllers vsi descriptor 12.2.0 Phys desc: 12.2.0 Log intf: 0x000C0200 (0.12.2.0) Interface: XTagATM0 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 9 lists the significant fields in this display.
| Field | Description |
|---|---|
Phys desc | Physical descriptor. A string learned from the switch that identifies the interface. |
Log intf | Logical interface ID. This 32-bit quantity, learned from the switch, uniquely identifies the interface. |
Interface | The (IOS) interface name. |
IF Status | The overall interface status. May 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 | The operational state of the interface, according to the switch. One of FAILED_EXT (that is, in external alarm), FAILED_INT (indicates the inability of the LSC to communicate with the VSI slave controlling the interface, or another internal failure), or REMOVED administratively (removed on the switch). |
Maximum cell rate | The 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) | The cell rate that is currently available in the forward (that is, ingress) direction for new cross-connects on the interface. |
Available cell rate (backward) | The cell rate that is currently available in the backward (that is, egress) direction for new cross-connects on the interface. |
Related Commands
show controllers XTagATM Displays information about an extended label ATM interface or, if an interface is not specified, about all extended label ATM interfaces, that are controlled through the VSI protocol.
Command
Description
To display information about all sessions with VSI slaves, use the show controllers vsi session command in EXEC mode.
 |
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 may 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 Session number. interface interface VSI control interface.
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
If a session number and an interface are specified, detailed information about the individual session is presented. If the session number is specified but the interface is omitted, detailed information about all sessions having that number is presented. (Only one session can have a given number in the first release, as multiple control interfaces are not supported.)
Examples
The following is sample output from the show controllers vsi session command:
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 10 lists the significant fields in this display.
| 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 that carries the VSI protocol between the master and the slave for this session. |
VPI/VCI | Virtual path identifier/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:
|
In this example, session number 9 is specified with the show controllers vsi session command:
show controllers vsi session 9 Interface: ATM1/0 Session number: 9 VCD: 10 VPI/VCI: 0/49 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 11 lists the significant fields in this display.
| 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 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/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 with the id option of the label-control-protocol vsi command, and also configured on the switch. |
Slave id | Slave identifier (supplied by the switch). |
Keepalive timer | VSI master keepalive timeout period, in seconds. Configured on the LSC through the keepalive option of the tag-control-protocol vsi command. If no valid message is received by the LSC within this period of time, the LSC sends a keepalive message to the slave. |
Powerup session id | The session id (supplied by the slave) that it used at power-up 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 | The session ID for the currently active session (supplied by the slave). |
Max retries | The 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 LSC through the retry option of the tag-control-protocol vsi command. |
Ctrl port log intf | The logical interface identifier for the control port, as supplied by the switch. |
Trap window | The maximum number of outstanding trap messages permitted by the master. This is advertised, but not enforced, by the LSC. |
Max/actual cmd wndw | The 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 actual command window is the maximum number of outstanding commands that are permitted by the master, before it waits for acknowledgments. This number is always less than the maximum command window. |
Trap filter | This is always "all" for the LSC, indicating that it wishes to receive all traps from the slave. This is communicated to the slave by the master. |
Max checksums | The maximum number of checksum blocks supported by the slave. (In this release, the LSC uses only one checksum block.) |
Current VSI version | The VSI protocol version currently in use by the master for this session. (In the first release, this is always 1.) |
Min/max VSI version | The 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 | The number of commands sent to the slave. |
Inter-Slave timer | The 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. Note that in order for the LSC VSI implementation to function properly, the value of its retry timer is forced to be at least twice the value of the inter-slave timer. (See "Cfg/act retry timer"). |
Messages received | The number of responses and traps received by the master from the slave for this session. |
Messages outstanding | The current number of outstanding messages (that is, commands sent by the master for which responses have not yet been received). |
Related Commands
tag-control-protocol vsi Configures the use of VSI on a particular master control port.
Command
Description
To display a one-line summary of each VSI-controlled interface, use the show controllers vsi status command in EXEC mode.
show controllers vsi statusSyntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
If an interface has been discovered by the LSC, but no extended label 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:
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 12 lists the significant fields in this display.
| Field | Description |
|---|---|
Interface Name | The (IOS) interface name. |
IF Status | The overall interface status. May be "up", "down", or "administratively down." |
IFC State | The operational state of the interface, according to the switch. One of FAILED_EXT (that is, in external alarm), FAILED_INT (indicates the inability of the LSC to communicate with the VSI slave controlling the interface, or another internal failure), or REMOVED (administratively removed on the switch). |
Physical Descriptor | A string learned from the switch that identifies the interface. |
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 |
Syntax Description
descriptor descriptor (Optional) Specifies the interface. session session-num (Optional) Specifies session number. vpi (Optional) Virtual path identifier. vci (Optional) Virtual circuit identifier.
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
If none of the optional command parameters is specified, traffic for all interfaces is displayed. You can specify a single interface by its (switch-supplied) physical descriptor. For the BPX, the physical descriptor has the form:
slot.port. 0
If a session number is specified, VSI protocol traffic counts by message type are displayed. The VC traffic display is the same as the one produced by the show xtagatm vc cross-connect traffic descriptor command.
Examples
The following is sample output from the show controllers vsi traffic command:
show controllers vsi traffic
Phys desc: 10.1.0
Interface: switch control port
IF status: n/a
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
Phys desc: 10.2.0
Interface: XTagATM0
IF status: up
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
Phys desc: 10.3.0
Interface: XTagATM1
IF status: up
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 13 lists the significant fields in this display.
| Field | Description |
|---|---|
Phys desc: | The physical descriptor of the interface. |
Interface: | The (IOS) interface name. |
Rx cells: | The number of cells received on the interface. |
Tx cells | The number of cells transmitted on the interface. |
Tx cells discarded: | The number of cells that could not be transmitted on the interface because of traffic management and that were therefore discarded. |
Rx header errors: | The number of cells which were discarded due to ATM header errors. |
Rx cells discarded: | The number of cells received on the interface that were discarded because of traffic management. |
Rx invalid addresses: | The number of cells received with an invalid address (that is, an unexpected VPI/VCI combination). With the BPX, this count is of all such cells received on all interfaces in the port group of this interface. |
Last invalid address: | The number of cells received on this interface having ATM cell header errors. |
The following sample output is displayed when you enter the show controllers vsi traffic session 9 command:
show controllers vsi traffic session 9
Sent Received
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
unused: 0 unused: 0
unknown: 0 unknown: 0
TOTAL: 3795 TOTAL: 3795
Table 14 lists the significant fields in this display.
| 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 LSC, and consequently are not expected to be received or sent. "Unknown" messages have function codes that the LSC does not recognize as part of the VSI protocol. |
TOTAL | Total number of VSI messages sent or received. |
To display information about an extended label ATM interface or, if an interface is not specified, about all extended label ATM interfaces, that are controlled through the VSI protocol, use the show controllers XTagATM command in EXEC mode.
show controllers XTagATM if-num
Syntax Description
if-num Interface number.
Command Modes
EXEC
Command History
12.0(3)T This command was introduced.
Release
Modification
Usage Guidelines
Per-interface information includes the interface name, the physical descriptor, the interface status, the physical interface state (supplied by the switch), acceptable VPI/VCI ranges, maximum cell rate, available cell rate (forward/backward), and available channels.
Similar information is displayed when you enter the show controllers vsi descriptor command However, you must specify an interface by its (switch-supplied) physical descriptor, instead of its IOS interface name. For the BPX, 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.
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 15 lists the significant fields in this display.
| Field | Description |
|---|---|
Interface XTagATM is up | Indicates the overall status of the interface. May be "up", "down", or "administratively down." |
Hardware is Label-Controlled ATM Port | Indicates the hardware type. If the XTagATM interface has been 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 "name" is an identifying string learned from the switch. If the XTagATM interface has not been 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 has been 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 ... | The physical descriptor is a string identifying the interface that has been learned from the switch. |
Logical interface | This 32-bit quantity, learned from the switch uniquely identifies the interface. It is displayed in both hexadecimal and dotted quad notation. |
Oper state | The operational state of the interface, according to the switch. One of ACTIVE, FAILED_EXT (that is, in external alarm), FAILED_INT (indicates the inability of the LSC to communicate with the VSI slave controlling the interface, or another internal failure), or REMOVED (administratively removed on the switch). |
admin state | The administrative state of the interface, according to the switch---UP or DOWN. |
VPI range 1-255 | Indicates the allowable VPI range for the interface that has been configured on the switch. |
VCI range 32-65535 | Indicates the allowable VCI range for the interface that has been configured on or determined by the switch. |
Label control VC need not be strictly in VPI/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: | The maximum cell rate for the interface, which has been configured on the switch. |
Available cell rate: | The cell rate that is currently available for new cross-connects on the interface. |
Endpoints in use: | The number of endpoints (channels) in use on the interface, broken down by anticipated traffic flow:
|
Rx cells | The number of cells received on the interface. |
rx cells discarded | The number of cells received on the interface that were discarded on account of traffic management actions. rx header errors. |
rx header errors | The number of cells received on the interface having cell header errors. |
rx invalid addresses (per card) | The number of cells received with invalid addresses (that is, unexpected VPI/VCI.) On the BPX, this counter is maintained per port group (not per interface.) |
last invalid address | The address of the last cell received on the interface with an invalid address (for example, 0/32). |
Tx cells | The number of cells transmitted out the interface. |
tx cells discarded | The number of cells intended for transmission out the interface that were discarded due to traffic management actions. |
Related Commands
show controllers vsi descriptor Displays information about a switch interface discovered by the LSC through VSI, or, if no descriptor is specified, about all such discovered interfaces.
Command
Description
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
11.0 This command was introduced.
Release
Modification
Usage Guidelines
Use this command on the RP.
Examples
The following is sample output from the show interface stats command:
show interface fddi 3/0/0 stats
Fddi3/0/0 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 16 describes the fields in the display.
| 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. |
Posted: Sun Mar 19 13:34:36 PST 2000
Copyright 1989 - 2000©Cisco Systems Inc.