Table Of Contents
show interfaces bri
show interfaces serial bchannel
show interfaces virtual-access
show ip interface virtual-access
show ip local pool
show ip route
show ipx compression
show ipx nasi connections
show ipx spx-protocol
show isdn
show isdn nfas group
show isdn service
show keymap
show lat advertised
show lat groups
show lat nodes
show lat services
show lat sessions
show lat traffic
show line
show interfaces bri
To display information about the BRI D channel or about one or more B channels, use the show interfaces bri command in privileged EXEC mode.
show interfaces bri number[[:bchannel] | [first] [last]] [accounting]
Cisco 7200 series router
show interfaces bri slot/port
Syntax Description
number
|
Interface number. The value is 0 through 7 if the router has one 8-port BRI NIM, or 0 through 15 if the router has two 8-port BRI NIMs. Interface number values will vary, depending on the hardware platform used. The Cisco 3600 series router for example, can have up to 48 interfaces.
Specifying just the number will display the D channel for that BRI interface.
|
slot/port
|
On the Cisco 7200 series, slot location and port number of the interface.
|
:bchannel
|
(Optional) Colon (:) followed by a specific B channel number.
|
first
|
(Optional) Specifies the first of the B channels; the value can be either 1 or 2.
|
last
|
(Optional) Specifies the last of the B channels; the value can only be 2, indicating B channels 1 and 2.
|
accounting
|
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
10.3
|
This command was introduced.
|
11.2P
|
This command was modified to include slot/port syntax for the PA-8B-ST and PA-4B-U port adapters on Cisco 7200 series routers.
|
Usage Guidelines
Use either the :bchannel-number argument or the first or last arguments to display information about specified B channels.
Use the show interfaces bri number form of the command (without the optional :bchannel, or first and last arguments) to obtain D channel information.
Use the command syntax sample combinations in Table 52 to display the associated output.
Table 52 Sample show interfaces bri Command step Combinations
Command Syntax
|
Displays
|
show interfaces
|
All interfaces in the router
|
show interfaces bri 2
|
Channel D for BRI interface 2
|
show interfaces bri 2:1
|
Channel B1 on BRI interface 2
|
show interfaces bri 2:2
|
Channel B2 on BRI interface 2
|
show interfaces bri 4 1
|
Channel B1 on BRI interface 4
|
show interfaces bri 4 2
|
Channel B2 on BRI interface 4
|
show interfaces bri 4 1 2
|
Channels B1 and B2 on BRI interface 4
|
show interfaces bri
|
Error message: "% Incomplete command."
|
Examples
The following is an output example from the show interfaces bri command:
Router# show interfaces bri 0:1
BRI0:1 is down, line protocol is down
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
Last input never, output never, output hang never
Last clearing of "show interface" counters never
Output queue 0/40, 0 drops; input queue 0/75, 0 drops
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 7 interface resets
0 output buffer failures, 0 output buffers swapped out
The following is an output example from the show interfaces bri command on a Cisco 7200 series router:
Router# show interfaces bri 2/0
BRI2/0 is up, line protocol is up (spoofing)
Internet address is 11.1.1.3/27
MTU 1500 bytes, BW 64 Kbit, DLY 20000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set
Last input 00:00:01, output 00:00:01, output hang never
Last clearing of "show interface" counters never
Input queue: 0/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
609 packets input, 2526 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
615 packets output, 2596 bytes, 0 underruns
0 output errors, 0 collisions, 5 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 53 describes the fields shown in the display.
Table 53 show interfaces bri Field Descriptions
Field
|
Description
|
BRI... is {up | down | administratively down}
|
Indicates whether the interface hardware is currently active (whether line signal is present) and if it has been taken down by an administrator.
|
line protocol
is {up | down |
administratively down}
|
Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful).
|
Hardware is
|
Hardware type.
|
Internet address is
|
IP address and subnet mask, followed by packet size.
|
MTU
|
Maximum transmission unit of the interface.
|
BW
|
Bandwidth of the interface in kilobits per second.
|
DLY
|
Delay of the interface in microseconds.
|
rely
|
Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.
|
load
|
Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.
|
Encapsulation
|
Encapsulation method assigned to interface.
|
loopback
|
Indicates whether loopback is set or not.
|
keepalive
|
Indicates whether keepalives are set or not.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by an interface. Useful for knowing when a nonfunctioning interface failed.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks (**) are printed.
|
Output queue, drops
Input queue, drops
|
Number of packets in output and input queues. Each number is followed by a slash (/), the maximum size of the queue, and the number of packets dropped due to a full queue.
|
Five minute input rate
Five minute output rate
|
Average number of bits and packets transmitted per second in the last 5 minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and media access control (MAC) encapsulation, in the error-free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the interface.
|
runts
|
Number of packets that are discarded because they are smaller than the medium's minimum packet size.
|
giants
|
Number of packets that are discarded because they exceed the medium's maximum packet size.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so this sum may not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can increase the ignored count.
|
abort
|
Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.
|
packets output
|
Total number of messages sent by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, sent by the system.
|
underruns
|
Number of times that the transmitter has been running faster than the router can handle. This may never be reported on some interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this may not balance with the sum of the enumerated output errors, because some datagrams may have more than one error, and others may have errors that do not fall into any of the specifically tabulated categories.
|
collisions
|
Number of collisions. These can occur when you have several devices connected on a multiport line.
|
interface resets
|
Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system recognizes that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.
|
restarts
|
Number of times the controller was restarted because of errors.
|
carrier transitions
|
Number of times the carrier detect signal of a serial interface has changed state. Check for modem or line problems if the carrier detect line is changing state often.
|
show interfaces serial bchannel
To display information about the physical attributes of the ISDN PRI over channelized E1 or channelized T1 B and D channels, use the show interfaces serial bchannel command in EXEC mode.
show interfaces serial slot/port bchannel channel-number
show interfaces serial number bchannel channel-number
Syntax Description
slot/port
|
Backplane slot number and port number on the interface. See your hardware installation manual for the specific slot and port numbers.
|
number
|
Network processor module (NPM) number, in the range 0 through 2.
|
channel-number
|
E1 channel number in the range 1 to 31 or T1 channel number in the range 1 to 23; 1-24 if using NFAS.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2F
|
This command was introduced.
|
show interfaces virtual-access
To display status, traffic data, and configuration information about a specified virtual access interface, use the show interfaces virtual-access command in EXEC mode.
show interfaces virtual-access number [configuration]
Syntax Description
number
|
Number of the virtual access interface.
|
configuration
|
(Optional) Restricts output to configuration information.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2F
|
This command was introduced.
|
11.3
|
The configuration keyword was added.
|
Usage Guidelines
To identify the number of the virtual terminal line on which the virtual access interface was created, enter the show users EXEC command included in this feature chapter.
Examples
The following is an output example from the show interfaces virtual-access command:
router# show interface virtual-access 2
Virtual-Access2 is up, line protocol is up
Hardware is Virtual Access interface
Interface is unnumbered. Using address of Ethernet0 (10.0.21.14)
MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 1/255
Encapsulation PPP, loopback not set, keepalive not set
DTR is pulsed for 0 seconds on reset
Last input 00:00:06, output 00:00:05, output hang never
Last clearing of "show interface" counters 00:14:58
Input queue: 1/75/0 (size/max/drops); Total output drops: 0
Queueing strategy: weighted fair
Output queue: 0/64/0 (size/threshold/drops)
Conversations 0/1 (active/max active)
Reserved Conversations 0/0 (allocated/max allocated)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
4 packets input, 76 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
8 packets output, 330 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 output buffer failures, 0 output buffers swapped out
Table 54 describes the fields shown in the output example.
Table 54 show interfaces virtual-access Field Descriptions
Field
|
Description
|
Virtual-Access ... is {up | down |
administratively down}
|
Indicates whether the interface is currently active (whether carrier detect is present), inactive, or has been taken down by an administrator.
|
line protocol is {up | down |
administratively down}
|
Indicates whether the software processes that handle the line protocol think the line is usable (that is, whether keepalives are successful).
|
Hardware is Virtual Access interface
|
Type of interface. In this case, the interface is a dynamically created virtual access interface existing on a VTY line.
|
Internet address | interface is unnumbered
|
IP address, or IP unnumbered for the line. If unnumbered, the output lists the interface and IP address to which the line is assigned (Ethernet0 at 10.0.21.14 in this example).
|
MTU
|
Maximum transmission unit for packets on the virtual access interface.
|
BW
|
Bandwidth of the virtual access interface in kilobits per second.
|
DLY
|
Delay of the virtual access interface in microseconds.
|
rely
|
Reliability of the virtual access interface as a fraction of 255 (255/255 is 100% reliability), calculated as an exponential average over five minutes.
|
load
|
Load on the virtual access interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over five minutes. The calculation uses the value from the bandwidth interface configuration command.
|
Encapsulation
|
Encapsulation method assigned to the virtual access interface.
|
loopback
|
Test in which signals are sent and then directed back toward the source at some point along the communication path. Used to test network interface usability.
|
keepalive
|
Interval set for keepalive packets on the interface. If keepalives have not been enabled, the message is "keepalive not set."
|
DTR
|
Data Terminal Ready. An RS232-C circuit that is activated to let the DCE know when the DTE is ready to send and receive data.
|
LCP open | closed | req sent
|
Link control protocol (for PPP only; not for SLIP). LCP must come to the open state before any useful traffic can cross the link.
|
Open IPCP | IPXCP | ATCP
|
IPCP is IP control protocol for PPP, IPXCP is IPX control protocol for PPP, ATCP is AppleTalk control protocol for PPP. Network control protocols (NCPs) for the PPP suite. The NCP is negotiated after the LCP opens. The NCP must come into the open state before useful traffic can cross the link.
|
Last input
|
Number of hours, minutes, and seconds since the last packet was successfully received by a virtual access interface. Useful for knowing when a dead interface failed.
|
output
|
Number of hours, minutes, and seconds since the last packet was successfully transmitted by a virtual access interface.
|
output hang
|
Number of hours, minutes, and seconds (or never) since the virtual access interface was last reset because of a transmission that took too long. When the number of hours in any of the "last" fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.
|
Last clearing
|
Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.
*** indicates the elapsed time is too large to be displayed.
0:00:00 indicates the counters were cleared more than 231ms (and less than 232ms) ago.
|
Input queue, drops
|
Number of packets in input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
|
Queueing strategy
|
Type of queueing selected to prioritize network traffic. The options are first-come-first-serve (FCFS) queueing, weighted fair queueing, priority queueing, and custom queueing.
|
Output queue
|
Number of packets in output queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped due to a full queue.
|
Conversations
|
Number of weighted fair queueing conversations.
|
Reserved Conversations
|
Number of reserved weighted fair queueing conversations. The example shows the number of allocated conversations divided by the number of maximum allocated conversations. In this case, there have been 0 reserved conversations.
|
Five minute input rate,
Five minute output rate
|
Average number of bits and packets transmitted per second in the last five minutes.
|
packets input
|
Total number of error-free packets received by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, in the error free packets received by the system.
|
no buffer
|
Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.
|
broadcasts
|
Total number of broadcast or multicast packets received by the virtual access interface.
|
runts
|
Number of packets that are discarded because they are smaller than the medium's minimum packet size.
|
giants
|
Number of packets that are discarded because they exceed the medium's maximum packet size.
|
input errors
|
Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.
|
CRC
|
Cyclic redundancy checksum generated by the originating LAN station or far end device does not match the checksum calculated from data received. On a LAN, this often indicates noise or transmission problems on the LAN interface or the LAN bus. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs often indicate noise, gain hits or other transmission problems on the data link.
|
frame
|
Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.
|
overrun
|
Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver's ability to handle the data.
|
ignored
|
Number of received packets ignored by the virtual access interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.
|
abort
|
Illegal sequence of one bits on a virtual access interface. This usually indicates a clocking problem between the virtual access interface and the data link equipment.
|
packets output
|
Total number of messages transmitted by the system.
|
bytes
|
Total number of bytes, including data and MAC encapsulation, transmitted by the system.
|
underruns
|
Number of times that the far-end transmitter has been running faster than the near-end communication server's receiver can handle. This might never be reported on some virtual access interfaces.
|
output errors
|
Sum of all errors that prevented the final transmission of datagrams out of the virtual access interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams might have more than one error, and others might have errors that do not fall into any of the tabulated categories.
|
collisions
|
Number of packets colliding.
|
interface resets
|
Number of times a virtual access interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds. This can be caused by a malfunctioning modem that is not supplying the transmit clock signal, or by a cable problem. If the system notices that the carrier detect line of a virtual access interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when a virtual access interface is looped back or shut down.
|
restarts
|
Number of times the controller was restarted because of errors.
|
carrier transitions
|
Number of times the carrier detect (CD) signal of a virtual access interface has changed state. Indicates modem or line problems if the CD line changes state often. If data carrier detect (DCD) goes down and comes up, the carrier transition counter increments two times.
|
output buffer failures
|
Number of outgoing packets dropped from the output buffer.
|
output buffers swapped out
|
Number of times the output buffer was swapped out.
|
show ip interface virtual-access
To display network layer IP information about a specified virtual access interface, use the show ip interface virtual-access command in EXEC mode.
show ip interface virtual-access number
Syntax Description
number
|
Number of the virtual access interface.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.2F
|
This command was introduced.
|
Examples
The following is output from the show ip interface virtual-access command. This virtual access interface has been configured with a virtual template interface that applies the ip unnumbered ethernet 0 command.
Router# show ip interface virtual-access 1
Virtual-Access1 is up, line protocol is up
Interface is unnumbered. Using address of Ethernet0 (172.21.114.132)
Broadcast address is 255.255.255.255
Helper address is not set
Directed broadcast forwarding is enabled
Outgoing access list is not set
Inbound access list is Virtual-Access1#0
Security level is default
ICMP redirects are always sent
ICMP unreachables are always sent
ICMP mask replies are never sent
IP fast switching is disabled
Table 55 describes only the output fields that are significant to virtual access interfaces and not described in other IP commands.
Table 55 show ip interface virtual-access Field Descriptions
Field
|
Description
|
Virtual-Access1 is up, line protocol is up
|
Virtual access interface is up and the upper layers consider the line usable.
|
Interface is unnumbered. Using the address of Ethernet0 (172.21.114.132)
|
The ip unnumbered ethernet 0 command was included in the virtual template interface cloned on this interface.
|
show ip local pool
To display statistics for any defined IP address pools, use the show ip local pool command in privileged EXEC mode.
show ip local pool [name]
Syntax Description
name
|
(Optional) Name of a specific IP address pool.
|
Command Modes
Privileged EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
If you omit the variable name, the software will display a generic list of all defined address pools and the IP addresses that belong to them. If you specify a name, the software displays more detailed information for that pool.
Examples
The following is an output example from the show ip local pool command:
Router# show ip local pool
Scope Begin End Free InUse
Dialin 172.30.228.11 172.30.228.26 16 0
Table 56 describes the fields shown in the display.
Table 56 show ip local pool Field Descriptions
Field
|
Description
|
Scope
|
The type of access.
|
Begin
|
The first IP address in the defined range of addresses in this pool.
|
End
|
The last IP address in the defined range of addresses in this pool.
|
Free
|
The number of addresses currently available.
|
InUse
|
The number of addresses currently in use.
|
Related Commands
Command
|
Description
|
ip address-pool
|
Enables an address pooling mechanism used to supply IP addresses to dial-in asynchronous, synchronous, or ISDN point-to-point interfaces.
|
ip local pool
|
Configures a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface.
|
show ip route
To display all static IP routes, or those installed using the AAA (authentication, authorization, and accounting) route download function, use the show ip route command in EXEC mode.
show ip route [address [network-mask] [longer-prefixes]] | [protocol [process-id]] | [static
[download]]
Syntax Description
address
|
(Optional) The IP address about which routing information should be displayed.
|
network-mask
|
(Optional) Network mask that lets you mask network and subnetwork bits.
|
longer-prefixes
|
(Optional) The address and mask pair becomes a prefix, and any routes that match that prefix are displayed.
|
protocol
|
(Optional) Name of a routing protocol; or the keyword connected, static, or summary. If you specify a routing protocol, use one of the following keywords: bgp, egp, eigrp, hello, igrp, isis, ospf, or rip.
|
process-id
|
(Optional) Arbitrary number assigned to identify a process of the specified protocol.
|
static
|
(Optional) All static routes.
|
download
|
(Optional) The route installed using the AAA route download function.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
10.0
|
This command was introduced.
|
10.3
|
The process-id argument was introduced.
|
11.0
|
The longer-prefixes keyword was introduced.
|
12.0(3)T
|
The folowing keywords were introduced:
• static
•download
|
Usage Guidelines
The show ip route static download command provides a way to display all dynamic static routes with name and distance information, including active and inactive ones. You can display all active dynamic static routes with both the show ip route and show ip route static commands after these active routes are added in the main routing table.
Examples
The following examples display all downloaded static routes. A P designates which route was installed using AAA route download.
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate default
U - per-user static route, o - ODR, P - periodic downloaded static route
T - traffic engineered route
Gateway of last resort is 172.21.17.1 to network 0.0.0.0
172.31.0.0/32 is subnetted, 1 subnets
P 172.31.229.41 is directly connected, Dialer1 20.0.0.0/24 is subnetted, 3 subnets
P 20.1.1.0 [200/0] via 172.31.229.41, Dialer1
P 20.1.3.0 [200/0] via 172.31.229.41, Dialer1
P 20.1.2.0 [200/0] via 172.31.229.41, Dialer1
router# show ip route static
103.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
P 103.1.1.1/32 is directly connected, BRI0
P 103.0.0.0/8 [1/0] via 103.1.1.1, BRI0
S 172.31.0.0/16 [1/0] via 172.21.114.65, Ethernet0
S 18.0.0.0/8 is directly connected, BRI0
P 20.0.0.0/8 is directly connected, BRI0
172.21.0.0/16 is variably subnetted, 5 subnets, 2 masks
S 172.21.114.201/32 is directly connected, BRI0
S 172.21.114.205/32 is directly connected, BRI0
S 172.21.114.174/32 is directly connected, BRI0
S 172.21.114.12/32 is directly connected, BRI0
P 10.0.0.0/8 is directly connected, BRI0
P 11.0.0.0/8 is directly connected, BRI0
P 12.0.0.0/8 is directly connected, BRI0
S* 0.0.0.0/0 [1/0] via 172.21.114.65, Ethernet0
S 198.92.0.0/16 [1/0] via 172.21.114.65, Ethernet0
The following example shows how to use the show ip route static download command to see all active and inactive routes installed using the AAA route download feature:
router# show ip route static download
Connectivity: A - Active, I - Inactive
A 10.0.0.0 255.0.0.0 BRI0
A 11.0.0.0 255.0.0.0 BRI0
A 12.0.0.0 255.0.0.0 BRI0
A 20.0.0.0 255.0.0.0 BRI0
I 21.0.0.0 255.0.0.0 172.21.1.1
I 22.0.0.0 255.0.0.0 Serial0
I 30.0.0.0 255.0.0.0 Serial0
I 31.0.0.0 255.0.0.0 Serial1
I 32.0.0.0 255.0.0.0 Serial1
A 103.0.0.0 255.0.0.0 103.1.1.1
A 103.1.1.1 255.255.255.255 BRI0 200 name remote1
I 104.21.69.0 255.255.255.0 104.21.69.1
Related Commands
Command
|
Description
|
show dialer
|
Displays general diagnostic information for interfaces configured for DDR.
|
show ipx compression
To show the current status and statistics of Internetwork Packet Exchange (IPX) header compression during PPP sessions, use the show ipx compression command in EXEC mode.
show ipx compression [detail int-spec]
Syntax Description
detail
|
(Optional) Shows detailed link-state database information for NLSP.
|
int-spec
|
(Optional) Interface type, as listed in Table 57.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Usage Guidelines
Table 57 lists the supported interface types.
Table 57 Interface Types
Keyword
|
Description
|
Async
|
Asynchronous interface.
|
Ethernet
|
Ethernet IEEE 802.3 interface.
|
Null
|
Null interface.
|
Serial
|
WAN serial interface.
|
Related Commands
Command
|
Description
|
ipx compression cipx
|
Enables compression of IPX packet headers in a PPP session.
|
show ipx interface
|
Displays the status of the IPX interfaces configured in the Cisco IOS software and the parameters configured on each interface.
|
show ipx nasi connections
To show the status of NetWare Asynchronous Services Interface (NASI) connections, use the show ipx nasi connections command in EXEC mode.
show ipx nasi connections
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is an example of output from the show ipx nasi connections command:
router# show ipx nasi connections
NASI Remote: A001500::0020.afe5.3ec5:626C Local: ACBB::0000.0000.0001:2010
NASI Remote: A001500::0020.afe5.3ec5:6E6C Local: ACBB::0000.0000.0001:20D0
Connected to line 2 incount 0 outcount 0 OVF 0
The following output example shows an incoming NASI connection on tty line 2:
Line User Host(s) Idle Location
2 tty 2 chris incoming 1 A001500.0020.afe5.3ec5
Table 58Table 58 describes fields from the show ipx nasi connections output example.
Table 58 show ipx nasi connections Field Descriptions
Field
|
Description
|
NASI Remote
|
•xxxxxxx::yyyyyyyyy:zzzz is the address for the remote NASI client connected to the router.
•xxxx is the IPX network number.
•yyyyyyy is the IPX host node (MAC address) for the client.
•zzzz is the SPX connection number.
|
Local
|
xxxxxxx::yyyyyyyyyy:zzzz is the local address associated to this connection on the router end of the link.
|
flags
|
A status bit that is used internally to allow and close connections.
|
Connected to line 2
|
Appears only when the connection is associated with a tty port. Indicates that this NASI connection is attached to tty 2.
|
incount 0
|
Data from the remote client.
|
outcount 0
|
Data to be sent to the remote client.
|
OVF 0
|
Refers to the number of times data could not be written to the tty line, because the buffers were full. Ideally, this counter should stay at 0.
|
Related Commands
show ipx spx-protocol
To view the status of the Sequenced Packet Exchange (SPX) protocol stack and related counters, use the show ipx spx-protocol command.
show ipx spx-protocol
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is an output example from the show ipx spx-protocol command:
router> show ipx spx-protocol
SPX Remote: A001500::0000.c047.ed5a:3A80 Local: ACBB::0000.0000.0001:2010
Queue counts: inq 0, outQ 0, unackedQ 0
Sequence: 34, Ack: 34, local-alloc: 39, remote-alloc: 35
Abort Timer fires in 24 secs
Verify Watchdog Timer fires in 3 secs
SPX Remote: A001500::0000.c047.ed5a:C980 Local: ACBB::0000.0000.0001:2900
Queue counts: inq 0, outQ 0, unackedQ 0
Sequence: 111, Ack: 55, local-alloc: 60, remote-alloc: 112
Abort Timer fires in 27 secs
Verify Watchdog Timer fires in 0 secs
Table 59Table 59 describes significant fields from this output example.
Table 59 show ipx spx-protocol Field Descriptions
Field
|
Description
|
SPX socket:
|
IPX/SPX socket number.
|
state
|
Internal state.
|
connections:
|
Number of open connections for this IPX/SPX socket.
|
SPX Remote: xxxxxxx::yyyy:zzzz
|
The SPX client address for each SPX connection on this IPX/SPX socket, where xxxx is the client IPX network number, yyyy is the client IPX MAC address, and zzzz is the client SPX connection number.
|
SPX Local xxxxxxx::yyyy:zzzz
|
The local SPX address, where xxxx is local IPX network number, yyyy is the local IPX MAC address, and zzzz is the local SPX connection number.
|
state
|
Internal state.
|
flags
|
A status bit that is used internally to allow and close connections.
|
Queue counts
|
inQ, outQ, and unackedQ, as specified in the following three rows.
|
inq
|
Number of SPX packets available for the SPX application to read.
|
outQ
|
Number of SPX packets that must be sent to the remote client.
|
unackedQ
|
Number of SPX packets sent, but no packet was received by the client, so far.
|
Sequence:
|
SPX sequence number. Represents the sequence number of next packet of data to be sent by the router.
|
Ack:
|
SPX acknowledgment number. Represents the sequence number of the client's packet that the router has received, so far.
|
local-alloc:
|
Maximum packet sequence number that is acceptable from the client. This is a method of imposing flow control on the NASI client.
|
remote-alloc:
|
Maximum packet sequence number that the NASI client can accept from the router. This is the NASI client's way of imposing flow control on the router.
|
Purge Timer
|
Time in seconds until this SPX connection is closed and deleted from the list.
|
Abort Timer
|
Time in seconds until this SPX connection is closed and deleted if a watchdog packet is not received.
|
Verify Watchdog Timer fires in X secs
|
Indicates the time when you last sent a watchdog packet to the client.
|
Related Commands
Command
|
Description
|
aaa authentication nasi
|
Specifies AAA authentication for NASI clients connecting through the access server.
|
ipx nasi-server enable
|
Enables NASI clients to connect to asynchronous devices attached to a router.
|
nasi authentication
|
Enables AAA authentication for NASI clients connecting to a router.
|
show ipx nasi connections
|
Displays the status of NASI connections
|
show isdn
To display the information about memory, Layer 2 and Layer 3 timers, and the status of PRI channels, use the show isdn command in EXEC mode.
show isdn {active [dsl | serial number] | history [dsl | serial number] | memory | service [dsl |
serial number] | status [dsl | serial number] | timers [dsl | serial number]}
Syntax Description
active [dsl | serial number]
|
Displays current call information of all ISDN interfaces or, optionally, a specific digital subscriber line (DSL) or a specific ISDN PRI interface (created and configured as a serial interface). Values of dsl range from 0 to 15. Information displayed includes the called number, the remote node name, the seconds of connect time, the seconds of connect time remaining, the seconds idle, and Advice of Charge (AOC) charging time units used during the call.
|
history [dsl | serial number]
|
Displays historic and current call information of all ISDN interfaces or, optionally, a specific DSL or a specific ISDN PRI interface (created and configured as a serial interface). Values of dsl range from 0 to 15. Information displayed includes the called number, the remote node name, the seconds of connect time, the seconds of connect time remaining, the seconds idle, and AOC charging time units used during the call.
|
memory
|
Displays ISDN memory pool statistics. This keyword is for use by technical development staff only.
|
service [dsl | serial number]
|
Displays the service status of all ISDN interfaces or, optionally, a specific DSL or a specific ISDN PRI interface (created and configured as a serial interface). Values of dsl range 0 to 15.
|
status [dsl | serial number]
|
Displays the status of all ISDN interfaces or, optionally, a specific DSL or a specific ISDN PRI interface (created and configured as a serial interface). Values of dsl range 0 to 15.
|
timers [dsl | serial number]
|
Displays the values of Layer 2 and Layer 3 timers for all ISDN interfaces or, optionally, a specific DSL or a specific ISDN PRI interface (created and configured as a serial interface). Values of dsl range from 0 to 15.
|
Command Modes
EXEC
Command History
Release
|
Modification
|
11.1
|
This command was introduced.
|
Examples
The following is an output example from the show isdn command with the active keyword:
---------------------------------------------------------------------------------
---------------------------------------------------------------------------------
History Table MaxLength = 100 entries
History Retain Timer = 15 Minutes
---------------------------------------------------------------------------------
Call Calling and Called Remote Node Seconds Seconds Seconds Recorded Charges
Type Phone Number Name Used Left Idle Units/Currency
---------------------------------------------------------------------------------
In +---Not Available---- aerocore 684802 +499598 401
In +---Not Available---- pmg 363578 +499503 496
In +---Not Available---- solpro 253232 +499325 674
In +---Not Available---- 194047 +499965 34
In +---Not Available---- taber 189165 +499841 158
In +---Not Available---- newt 110342 0
In +---Not Available---- 2603 +499997 2
In +---Not Available---- 1310 +499798 201
