-
Access and Communication Servers Command Reference
-
About This Manual
-
Access Server and Communication Server Product Overview
-
User Interface Commands
-
System Image and Configuration File Load Commands
-
Configuring Terminal Lines and Modem Support
-
System Management Commands
-
User Interface Config Commands
-
Dial on Demand Routing Commands
-
X.25 Configuration Commands
-
Frame Relay Commands
-
SMDS Commands
-
Telnet Configuration Commands
-
LAT Configuration Commands
-
TN3270 Configuration
-
AppleTalk Remote Access Commands
-
SLIP and PPP Configuration Commands
-
XRemote Configuration Commands
-
AppleTalk Routing Commands
-
IP Commands
-
IP Routing Protocols Commands
-
Novell IPX Commands
-
Protocol Translation Configuration Commands
-
Appendix A, ASCII Character Set
-
Appendix B, Modem and Chat Script Configuration
-
Appendix C, Regular Expressions
-
Appendix D, Refs and Reading
-
Appendix E, X.3 PAD Parameters
-
Table Of Contents
Interface Configuration Commands
half-duplex controlled-carrier
Interface Configuration Commands
This chapter contains the commands used to configure nonprotocol-specific features. The commands are in alphabetical order. For hardware technical descriptions and for information about installing the access server interfaces, refer to the hardware installation and maintenance publication for your product.
For interface configuration tasks and examples, refer to the Access and Communication Servers Configuration Guide.
backup delay
To define how much time should elapse before a secondary line is set up or taken down after a primary line transition, use the backup delay interface configuration command. Use the no form of this command to remove the definition.
backup delay {enable-delay | never} {disable-delay | never}
no backup delay {enable-delay | never} {disable-delay | never}Syntax Description
Default
A secondary line is never activated nor deactivated.
Command Mode
Interface configuration
Usage Guidelines
When a primary line goes down, the access server delays the number of seconds defined by the enable-delay argument before enabling the secondary line. If, after the delay period, the primary line is still down, the secondary line is activated.
When a primary line comes back up, the access server will delay by the number of seconds defined by the disable-delay argument.
In cases where there are spurious signal disruptions that might appear as intermittent lost carrier signals, it is recommended that some delay be enabled before activating and deactivating a secondary.
Example
The following example sets a 10-second delay on deactivating the secondary line; however, the line is activated immediately:
interface serial 0backup delay 0 10backup interface
To configure the serial interface as a secondary, or dial backup line, use the backup interface interface configuration command. Use the no form of this command with the appropriate serial port designation to turn this feature off.
backup interface interface-name
no backup interface interface-nameSyntax Description
Default
None
Command Mode
Interface configuration
Example
The following example sets serial interface 1 as the backup line to serial interface 0:
interface serial 0backup interface serial 1Related Command
backup load
To set the traffic load thresholds for dial backup service, use the backup load interface configuration command. Use the no form of this command to remove the setting.
backup load {enable-threshold | never} {disable-load | never}
no backup load {enable-threshold | never} {disable-load | never}Syntax Description
Default
The secondary line is never activated due to load.
Command Mode
Interface configuration
Usage Guidelines
When the transmitted or received load on the primary line is greater than the value assigned to the enable-threshold argument, the secondary line is enabled.
When the transmitted load on the primary line plus the transmitted load on the secondary line is less than the value entered for the disable-load argument, and the received load on the primary line plus the received load on the secondary line is less than the value entered for the disable-load argument, the secondary line is disabled.
If the never keyword is used instead of an enable-threshold value, the secondary line is never activated because of load. If the never keyword is used instead of an disable-load value, the secondary line is never deactivated because of load.
Example
The following example sets the traffic load threshold to 60 percent on the primary line. When that load is exceeded, the secondary line is activated, and will not be deactivated until the combined load is less than 5 percent of the primary bandwidth.
interface serial 0backup load 60 5bandwidth
To set a bandwidth value for an interface, use the bandwidth interface configuration command. Use the no form of this command to restore the default values.
bandwidth kilobits
no bandwidthSyntax Description
kilobits
Intended bandwidth in kilobits per second. For a full bandwidth DS3, enter the value 44736.
Default
Default bandwidth values are set during startup.
Command Mode
Interface configuration
Usage Guidelines
Bandwidth values can be displayed with the EXEC command show interfaces.
The bandwidth command sets an informational parameter only; you cannot adjust the actual bandwidth of an interface with this command. For some media, such as Ethernet, the bandwidth is fixed; for other media, such as serial lines, you can change the actual bandwidth by adjusting hardware. For both classes of media, you can use the bandwidth configuration command to communicate the current bandwidth to the higher-level protocols.
Additionally, IGRP uses the minimum path bandwidth to determine a routing metric. The TCP protocol adjusts initial retransmission parameters based on the apparent bandwidth of the outgoing interface.
At higher bandwidths, the value you configure with the bandwidth command is not what is displayed by the show interface command. The value shown is that used in IGRP updates and also used in computing load.
Note
This is a routing parameter only; it does not affect the physical interface.
Example
The following example sets the full bandwidth for DS3 transmissions:
interface serial 0 bandwidth 44736clear counters
To clear the interface counters, use the clear counters EXEC command.
clear counters [type number]
Syntax Description
type
(Optional) Specifies the interface type; it is one of the keywords listed in .
number
(Optional) Specifies the interface counter displayed with the show interfaces command.
Table 6-1 Clear Counters Interface Type Keywords
Command Mode
EXEC
Usage Guidelines
This command clears all the current interface counters from the interface unless the optional arguments type-keyword and number are specified to clear only a specific interface type (serial, Ethernet, Token Ring, and so on).
Note
Example
The following example illustrates how to clear all interface counters:
Router# clear countersRelated Command
clear interface
To reset the hardware logic on an interface, use the clear interface EXEC command.
clear interface type number
Syntax Description
type
Specifies the interface type; it is one of the keywords listed in .
number
Specifies the port, connector, or interface card number.
Table 6-2 Clear Interface Type Keywords
Command Mode
EXEC
Usage Guidelines
Under normal circumstances, you do not need to clear the hardware logic on interfaces.
Example
Router# clear interface async 1clear line
To return a line to its idle state, enter the clear line privileged EXEC command at the system prompt.
clear line line-number
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
Normally, this command returns the line to its conventional function as a terminal line, with the interface left in a "down" state.
Example
The following example shows how to use the clear line command to return serial interface 5 to its idle state:
clear line 5clockrate
To configure the clock rate for appliques (connector hardware) on the serial interface of the MCI and SCI cards to an acceptable bit rate, use the clockrate interface configuration command. Use the no form of this command to remove the clock rate if you change the interface from a DCE to a DTE device.
clockrate bps
no clockrateSyntax Description
bps
Desired clock rate in bits per second: 1200, 2400, 4800, 9600, 19200, 34800, 56000, 64000, 72000, 125000, 148000, 500000, 800000, 1000000, 1300000, 2000000, or 4000000
Default
No clock rate
Command Mode
Interface configuration
Usage Guidelines
Be aware that the fastest speeds might not work if your cable is too long, and that speeds faster than 148,000 bits per second are too fast for RS-232 signaling. It is recommended that you only use the synchronous serial RS-232 signal at speeds up to 64,000 bits per second. To permit a faster speed, use an RS-449 or V.35 applique.
Example
The following example sets the clock rate on the first serial interface to 64,000 bits per second:
interface serial 0 clockrate 64000compress
To configure point-to-point software compression for a LAPB, PPP, and HDLC, use the compress interface configuration command. To disable compression, use the no form of this command.
compress [predictor | stac]
no compress [predictor | stac]Syntax Description
Default
Compression is disabled.
Command Mode
Interface configuration
Usage Guidelines
You can configure point-to-point software compression for all LAPB, point-to-point (PPP), and HDLC encapsulations. Compression reduces the size of frames via lossless data compression. The compression algorithm used is a predictor algorithm (the RAND compression algorithm), which uses a compression dictionary to predict what the next character in the frame will be.
For HDLC encapsulations, you can specify a Stacker compression algorithm by using the stac keyword. PPP and LAPB encapsulations support both predictor and Stacker compression algorithms.
Compression is performed in software and may significantly affect system performance. We recommend that you disable compression if CPU load exceeds 65%. To display the CPU load, use the show process cpu EXEC command.
Compression requires that both ends of the serial link be configured to use compression. You should never enable compression for connections to a public data network.
Note
If the majority of your traffic is already compressed files, it is recommended that you not use compression. If the files are already compressed, the additional processing time spent in attempting unsuccessfully to compress them again will slow system performance.
provides general guidelines for deciding which compression type to select for LAPB encapsulations.
Table 6-3 Compression Guidelines for LAPB Encapsulations
Predictor
The bottleneck is the load on the access server.
Stacker
The bottleneck is line bandwidth.
None
Most files are already compressed.
Stacker compression for LAPB encapsulations reaches its performance ceiling on T1lines; it is not recommended for faster lines because the added processing will slow their performance.
When using predictor compression, you should adjust the MTU for the serial interface and the LAPB N1 parameter as shown in the first example to avoid informational diagnostics regarding excessive MTU or N1 sizes. However, you should not change those parameters when you use Stacker compression.
Example
The following example enables predictor compression on serial interface 0 for a LAPB link:
interface serial 0encapsulation lapbcompress predictormtu 1509lapb n1 12072The following example enables Stacker compression on serial interface 0 for a LAPB link. This example does not set the MTU size and the maximum bits per frame (N1); it is recommended that you do not change those LAPB parameters for Stacker compression:
interface serial 0encapsulation lapbcompress predictorRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
encapsulation lapb†
encapsulation lapb-dce
encapsulation multi-lapb
encapsulation multi-lapb-dce
encapsulation x25 †
show compress
show processes†delay
To set a delay value for an interface, use the delay interface configuration command. Use the no form of this command to restore the default delay value.
delay tens-of-microseconds
no delaySyntax Description
tens-of-microseconds
Integer that specifies the delay in tens of microseconds for an interface or network segment
Default
You can display default delay values with the EXEC command show interfaces.
Command Mode
Interface configuration
Example
The following example sets a 30,000-microsecond delay on serial interface 3:
interface serial 3 delay 30000Related Command
description
To add a description to an interface configuration, use the description interface configuration command. Use the no form of this command to remove the description.
description string
no descriptionSyntax Description
Default
None
Command Mode
Interface configuration
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember what certain interfaces are used for. The description appears in the output of the following EXEC commands: show startup-config, show interfaces, and show running-config.
Example
The following example describes a 3174 controller on serial interface 0:
interface serial 0 description 3174 Controller for test labRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
show interfaces
show running-config †
show startup-config †
down-when-looped
To configure an interface to inform the system it is down when loopback is detected, use the
down-when-looped interface configuration command.down-when-looped
Syntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command is valid for PPP encapsulation on serial and HSSI interfaces.
When an interface has a backup interface configured, it is often desirable that the backup interface be enabled when the primary interface is either down or in loopback. By default, the backup is only enabled if the primary interface is down. By using the down-when-looped command, the backup interface will also be enabled if the primary interface is in loopback.
If testing an interface with the loopback command, or by placing the DCE into loopback, down-when-looped should not be configured; otherwise packets will not be transmitted out the interface that is being tested.
Example
In the following example, serial interface 0 is configured for PPP encapsulation. It is then configured to let the system know that it is down when in loopback mode.
interface serial 0encapsulation pppdown-when-loopedRelated Commands
backup interface
loopbackearly-token-release
To enable early token release, use the early-token-release interface configuration command. Use the no form of this command to disable this feature.
early-token-release
no early-token-releaseSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This feature helps to increase the total bandwidth of the Token Ring. Early token release is a method whereby the Token Ring interfaces can release the token back onto the ring immediately after transmitting rather than waiting for the frame to return.
The CSC-R16M, CSC-2R, and CSC-1R cards support early token release.
Example
The following example enables the use of early token release on Token Ring interface 1:
interface tokenring 1early-token-releaseencapsulation
To set the encapsulation method used by the interface, use the encapsulation interface configuration command.
encapsulation encapsulation-type
Syntax Description
Table 6-4 Encapsulation Type Keywords
Default
The default depends on the type of interface. For example, an Ethernet interface defaults to ARPA.
Command Mode
Interface configuration
Examples
The following example reenables standard Ethernet Version 2.0 encapsulation on Ethernet interface 0:
interface ethernet 0encapsulation arpaThe following example sets IEEE 802.3 encapsulation on Ethernet interface 1:
interface ethernet 1 encapsulation sapThe following example enables PPP encapsulation on serial interface 0:
interface serial 0encapsulation pppThe following example sets IEEE 802.2 encapsulation on Ethernet interface 1:
interface ethernet 1 encapsulation snapRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
keepalive
ppp †
physical-layer
slip †error-threshold
To set the mechanism that protects against packet overload and resulting recount errors on the MCI interface cards, use the error-threshold interface configuration command.
error-threshold milliseconds
Syntax Description
Default
1000 milliseconds
Command Mode
Interface configuration
Example
The following commands set the error recount threshold on Ethernet interface 2 to 10,000 milliseconds:
interface ethernet 2 error-threshold 10000group-range
To create a list of member asynchronous interfaces (associated with a group interface), use the group-range command. Use the no form of the command to remove an interface from the member list.
group-range low-end-of-range high-end-of-range
no group-number interfaceSyntax Description
Default
No interfaces are designated as members of a group.
Command Mode
Interface configuration
Usage Guidelines
Using the group-range command, you create a group of asynchronous interfaces that are associated with a group asynchronous interface on the same device. This group interface is configured by using the interface group-async command. This one-to-many structure allows you to configure all associated member interfaces by entering one command on the group interface, rather than entering this command on each interface. You can customize the configuration on a specific interface by using the member command.
Examples
The following example defines interfaces 2, 3, 4, 5, 6, and 7 as members of asynchronous group interface 0:
interface group-async 0 group range 2 7Related Commands
half-duplex controlled-carrier
To place a low-speed serial interface in controlled-carrier mode, instead of constant-carrier mode, use the half-duplex controlled-carrier interface configuration command. Use the no form of this command to return the interface to constant-carrier mode.
half-duplex controlled-carrier
no half-duplex controlled-carrierSyntax Description
This command has no arguments or keywords.
Default
Constant-carrier mode, where DCD is held constant and asserted by the DCE half-duplex interface.
Command Mode
Interface Configuration
Usage Guidelines
This command applies only to low-speed serial DCE interfaces in half-duplex mode. Configure a serial interface for half-duplex mode by using the media-type half-duplex command. These interfaces are available on Cisco 2520 through 2523 routers.
Controlled-carrier operation means that the DCE interface will have DCD de-asserted in the quiescent state. When the interface has something to transmit, it will assert DCD, wait a user-configured amount of time, then start the transmission. When the interface has finished transmitting, it will again wait a user configured amount of time, then deassert DCD.
An interface placed in controlled-carrier mode can be returned to constant-carrier mode by using the no form of the command.
Examples
The following examples show how to place the interface in controlled-carrier mode and back into constant-carrier operation.
Changing to controlled-carrier mode from the default of constant-carrier operation:
Router(config)# interface serial 2Router(config-if)# half-duplex controlled-carrierChanging to constant-carrier operation from controlled-carrier mode:
Router(config)# interface serial 2Router(config-if)# no half-duplex controlled-carrierRelated Commands
half-duplex timer
physical-layerhalf-duplex timer
To tune half-duplex timers, use the half-duplex timer interface configuration command. The half-duplex timer cts-delay command replaces the sdlc cts-delay command. The half-duplex timer rts-timeout command replaces the sdlc rts-timeout command. Use the no form of this command, along with the appropriate keyword, to return to the default value for that parameter.
You can configure more than one of these options, but each option must be specified as a separate command.
half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}
no half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}
Syntax Description
cts-delay value
Specifies the delay introduced by the DCE interface between the time it detects RTS to the time it asserts CTS in response. The range is dependent on the serial interface hardware. The default value is 0 ms.
cts-drop-timeout value
Determines the amount of time a DTE interface waits for CTS to be de-asserted after it has de-asserted RTS. If CTS is not de-asserted during this time, an error counter is incremented to note this event. The range is 0 to 1140000 ms (1140 seconds). The default value is 250 ms.
dcd-drop-delay value
Applies to DCE half-duplex interfaces operating in controlled-carrier mode (see the half-duplex controlled-carrier command). This timer determines the delay between the end of transmission by the DCE and the de-assertion of DCD. The range is 0 to 4400 ms (4.4 seconds). The default value is 100 ms.
dcd-txstart-delay value
Applies to DCE half-duplex interfaces operating in controlled-carrier mode. This timer determines the time delay between the assertion of DCD and the start of data transmission by the DCE interface. The range is 0 to 1140000 ms (1140 seconds). The default value is 100 ms.
rts-drop-delay value
Specifies the time delay between the end of transmission by the DTE interface and de-assertion of RTS. The range is 0 to 1140000 ms (1140 seconds). The default value is 3 ms.
rts-timeout value
Determines the number of ms the DTE waits for CTS to be asserted after the assertion of RTS before giving up on its transmission attempt. If CTS is not asserted in the specified amount of time, an error counter is incremented. The range is dependent on the serial interface hardware. The default value is 3 ms.
transmit-delay value
Specifies the number of ms a half-duplex interface will delay the start of transmission. In the case of a DTE interface, this delay specifies how long the interface waits after something shows up in the transmit queue before asserting RTS. For a DCE interface, this dictates how long the interface waits after data is placed in the transmit queue before starting transmission. If the DCE interface is in controlled-carrier mode, this delay shows up as a delayed assertion of DCD.
This timer enables the transmitter to be adjusted if the receiver is a little slow and is not able to keep up with the transmitter. The range is 0 to 4400 ms (4.4 seconds). The default value is 0 ms.
Default
The default cts-delay value is 0 ms.
The default cts-drop-timeout value is 250 ms.
The default dcd-drop-delay value is 100 ms.
The default dcd-txstart-delay value is 100 ms.
The default rts-drop-delay value is 3 ms.
The default rts-timeout value is 3 ms.
The default transmit-delay value is 0 ms.
Command Mode
Interface configuration
Usage Guidelines
The half-duplex timer command is used to tune half-duplex timers. These timer tuning commands permit you to adjust the timing of the half-duplex state machines to suit the particular needs of their half-duplex installation.
The range of values for the cts-delay and rts-timeout keywords are dependent on the serial interface hardware.
Examples
The following examples show how to set the cts-delay timer to 10 ms and the transmit-delay timer to 50 ms.
Cobra(config)# interface serial 2Cobra(config-if)# half-duplex timer cts-delay 10Cobra(config-if)# half-duplex timer transmit-delay 50Related Commands
half-duplex controlled-carrier
physical-layerhold-queue
To specify the hold-queue limit of an interface, use the hold-queue interface configuration command. Use the no form of this command with the appropriate keyword to restore the default values for an interface.
hold-queue length {in | out}
no hold-queue {in | out}Syntax Description
length
An integer that specifies the maximum number of packets in the queue
in
A keyword that specifies the input queue
out
A keyword that specifies the output queue
Default
The default input hold-queue limit is 75 packets. The default output hold-queue limit is 40 packets. These limits prevent a malfunctioning interface from consuming an excessive amount of memory. There is no fixed upper limit to a queue size.
Command Mode
Interface configuration
Usage Guidelines
The input hold queue prevents a single interface from flooding the network server with too many input packets. Further input packets are discarded if the interface has too many input packets outstanding in the system.
If priority output queueing is being used, the length of the four output queues is set using the priority-list global configuration command. The hold-queue command cannot be used to set an output hold queue length in this situation.
For slow links, use a small output hold-queue limit. This approach prevents storing packets at a rate that exceeds the transmission capability of the link. For fast links, use a large output hold-queue limit. A fast link may be busy for a short time (and thus require the hold queue), but can empty the output hold queue quickly when capacity returns.
To display the current hold queue setting and the number of packets discarded because of hold queue overflows, use the EXEC command show interfaces.
Note
Example
The following example illustrates how to set a small input queue on a slow serial line:
interface serial 0 hold-queue 30 inRelated Command
ignore-dcd
Use the ignore-dcd interface configuration command to configure the serial interface to monitor the DSR signal (instead of the DCD signal) as the line up/down indicator. Use the no form of this command to restore the default behavior.
ignore-dcd
no ignore-dcdSyntax Description
This command has no arguments or keywords.
Default
The serial interface, operating in DTE mode, monitors the DCD signal as the line up/down indicator.
Command Mode
Interface configuration
Usage Guidelines
This command applies to Quad Serial NIM interfaces on the Hitachi-based serial interfaces on the Cisco 2500 series.
When the serial interface is operating in DTE mode, it monitors the Data Carrier Detect (DCD) signal as the line up/down indicator. By default, the attached DCE device sends the DCD signal. When the DTE interface detects the DCD signal, it changes the state of the interface to up.
In some configurations, such as an SDLC multidrop environment, the DCE device sends the Data Set Ready (DSR) signal instead of the DCD signal, which prevents the interface from coming up. Use this command to tell the interface to monitor the DSR signal instead of the DCD signal as the line up/down indicator.
Example
The following example configures serial interface 0 to monitor the DSR signal as the line up/down indicator:
interface serial 0ignore-dcdinterface
To configure an interface type and enter interface configuration mode, use the interface global configuration command.
interface type number
To configure a subinterface, use the interface global configuration command.
interface type number.subinterface-number [multipoint | point-to-point]
Syntax Description
type
number
Port, connector, or interface card number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command.
.subinterface-number
Subinterface number in the range 1 to 4294967293. The number that precedes the period (.) must match the number to which this subinterface belongs.
multipoint | point-to-point
(Optional) Specifies a multipoint or point-to-point subinterface. There is no default.
Table 6-5 Interface Type Keywords
async
Line used as an asynchronous interface.
dialer
Refer to the interface dialer command.
ethernet
Ethernet IEEE 802.3 interface.
group-async
Refer to the interface group-async command.
loopback
Software-only loopback interface that emulates an interface that is always up. It is a virtual interface supported on all platforms. The interface-number is the number of the loopback interface that you want to create or configure.There is no limit on the number of loopback interfaces you can create.
null
Null interface.
serial
Serial interface.
tokenring
Token Ring interface.
tunnel
Tunnel interface; a virtual interface. The interface-number is the number of the tunnel interface that you want to create or configure. There is no limit on the number of tunnel interfaces you can create.
Default
The default mode for subinterfaces is multipoint.
Command Mode
Global configuration
Usage Guidelines
Subinterfaces can be configured to support partially meshed Frame Relay networks and multiple IPX encapsulations on LAN media (refer to the Access and Communication Servers Configuration Guide).
Examples
In the following example, serial interface 0 is configured with PPP encapsulation:
interface serial 0 encapsulation pppThe following example enables loopback mode and assigns an IP network address and network mask to the interface. The loopback interface established here will always appear to be up:
interface loopback 0 ip address 172.30.1.1 255.255.255.0The following example shows how a partially meshed Frame Relay network can be configured. In this example, subinterface serial 0.1 is configured as a multipoint subinterface with three Frame Relay PVCs associated, and subinterface serial 0.2 is configured as a point-to-point subinterface.
interface serial 0encapsulation frame-relayinterface serial 0.1 multipointip address 172.30.10.1 255.255.255.0frame-relay interface-dlci 42 broadcastframe-relay interface-dlci 53 broadcastinterface serial 0.2 point-to-pointip address 172.30.11.1 255.255.0frame-relay interface-dlci 59 broadcastRelated Commands
Two daggers (††) indicate that the command is documented in the Cisco Access Connection Guide.
ppp ††
show interfaces
slip ††interface dialer
To designate a dialer rotary group leader, use the interface dialer global configuration command.
interface dialer interface-number
Syntax Description
Default
None
Command Mode
Global configuration
Usage Guidelines
Dialer rotary groups allow you to apply a single interface configuration to a set of interfaces. Once the interface configuration is propagated to a set of interfaces, those interfaces can be used to place calls using the standard dial-on-demand criteria. When many destinations are configured, any of these interfaces can be used for outgoing calls.
Dialer rotary groups are useful in environments that require many calling destinations. Only the rotary group needs to be configured with all of the dialer map commands. The only configuration required for the interfaces is the dialer rotary-group command indicating that each interface is part of a dialer rotary group.
Although a dialer rotary group is configured as an interface, it is not a physical interface. Instead it represents a group of interfaces. Any number of dialer groups can be defined.
Interface configuration commands entered after the interface dialer command will be applied to all physical interfaces assigned to specified rotary group.
Example
The following example identifies dialer interface 1 as the dialer rotary group leader. Dialer interface 1 is not a physical interface, but represents a group of interfaces. The interface configuration commands that follow apply to all interfaces included in this group.
interface dialer 1encapsulation pppdialer in-banddialer map ip 172.30.2.5 username YYY 14155553434dialer map ip 172.30.4.5 username ZZZRelated Command
A dagger (†) indicates that the command is documented in another chapter.
dialer rotary-group †
interface group-async
To create a group interface that will serve as master, to which asynchronous interfaces can be associated as members, use the interface group-async command. Use the no form of the command to restore the default.
interface group-async unit-number
no interface group-async unit-numberSyntax Description
Default
No interfaces are designated as group masters.
Command Mode
Global configuration
Usage Guidelines
Using the interface group-async command, you create a single asynchronous interface to which other interfaces are associated as members using the group-range command. This one-to-many configuration allows you to configure all associated member interfaces by entering one command on the group master interface, rather than entering this command on each individual interface. You can create multiple group masters on a device; however, each member interface can only be associated with one group.
Examples
The following example defines asynchronous group master interface 0:
interface group-async 0Related Commands
ip address-pool
To enable the global default address-pooling mechanism used to supply IP addresses on dial-in asynchronous, synchronous, or ISDN point-to-point interfaces, use the ip address-pool global configuration command. To disable IP address pooling globally on all interfaces with the default configuration, use the no form of the command.
ip address-pool [dhcp-proxy-client | local]
no ip address-poolSyntax Description
Default
IP address pooling is disabled.
Command Mode
Global configuration
Usage Guidelines
The Global Default Mechanism applies to all interfaces that have been left in their default setting of peer default ip address pool.
If any peer default ip address command (other than peer default ip address pool, the default) is configured, then the interface uses that mechanism and not the Global Default Mechanism. Thus all interfaces can be independently configured or left unconfigured so that the Global Default Mechanism setting will apply. This flexibility minimizes the configuration effort on the part of the administrator.
Examples
The following example specifies the DHCP proxy client mechanism as the Global Default Mechanism for assigning peer IP addresses:
ip address-pool dhcp-proxy-clientThe following example specifies a local IP address pool called default as the Global Default Mechanism for all interfaces that are left in the default setting:
ip address-pool localRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
encapsulation ppp
encapsulation slip
ip dhcp-server
ip local pool
member peer default ip address
peer default ip address
peer default ip address pool
ppp†
show dhcp
show ip local pool
slip†ip dhcp-server
To specify which DHCP (Dynamic Host Configuration Protocol) servers to use on your network, specify the IP address of one or more DHCP servers available on the network by using the ip dhcp-server command. Use the no form of the command to remove a DHCP server's IP address.
ip dhcp-server [ip-address | name]
no ip dhcp-server [ip-address | name]Syntax Description
ip-address
IP address of a DHCP server. You can specify up to ten servers on the network.
name
Name of a DHCP server. You can specify up to ten servers on the network.
Default
The IP limited broadcast address of 255.255.255.255 is used for transactions if no DHCP server is specified. This allows autodetection of DHCP servers.
Command Mode
Global configuration
Usage Guidelines
A DHCP server temporarily allocates network addresses to clients through the access server on an as-needed basis. While the client is active, the address is automatically renewed in a minimum of 20-minute increments. When the user terminates the session, the interface connection is terminated so that network resources can be quickly reused.
In normal situations, if a user's SLIP/PPP session fails (for example if a modem line disconnects), the allocated address will be temporarily reserved in an attempt to preserve the same IP address for the client when dialed back into the server. This way, the session that was accidentally terminated can often be resumed.
To use the DHCP proxy-client feature, enable your access server to be a proxy-client on asynchronous interfaces by using the ip address-pool dhcp-proxy-client command. If you wish to specify which DHCP servers are used on your network, use the ip dhcp-server command to define up to ten specific DHCP servers.
Note
The ip address-pool dhcp-proxy-client command initializes proxy-client status to all interfaces on the access server defined as asynchronous. To selectively disable proxy-client status on a single asynchronous interface, use the no peer default ip address interface command.
Example
The following command specifies a DHCP server with the IP address of 172.30.13.81:
ip dhcp-server 172.30.13.81Related Commands
A dagger (†) indicates that the command is documented in another chapter.
ip address-pool
ip helper address †
peer default ip address
show dhcp
ip local pool
To configure a local pool of IP addresses to be used when a remote peer connects to a point-to-point interface, use the ip local pool global configuration command. To delete an address pool, use the no form of this command.
ip local pool {default | poolname low-ip-address [high-ip-address]}
no ip local pool {default | poolname}Syntax Description
Default
No address pools are preconfigured.
Command Mode
Global configuration
Usage Guidelines
Use the ip local pool command to create one or more local address pools from which IP addresses are assigned when a peer connects. The default address pool is then used on all point-to-point interfaces after the ip address-pool local global configuration command has been issued. To use a specific named address pool on an interface, use the peer default ip address pool interface configuration command.
These pools can also be used with the translate command for one-step VTY asynchronous connections and in certain AAA/TACACS+ authorization functions. Refer to the chapters "Protocol Translation" and "System Management" of the Access and Communication Configuration Guide for more information. Pools can be displayed with the show ip local pool command.
Example
The following command creates a local IP address pool by the name of quark, which contains all local IP addresses from 172.16.23.0 to 172.16.23.255:
ip local pool quark 172.16.23.0 172.16.23.255Related Commands
ip address-pool
show ip local poolkeepalive
Use the keepalive interface configuration command to set the keepalive timer for a specific interface. Use the no form of the command to turn off keepalives entirely.
keepalive [seconds]
no keepalive [seconds]Syntax Description
Default
Enabled and set to 10 seconds on most interfaces; disabled on asynchronous interfaces.
Command Mode
Interface configuration
Usage Guidelines
Asynchronous interfaces do not send and do not expect keepalives from the remote end of a point-to-point connection. To enable keepalives on asynchronous interfaces, use the keepalive command and set a specific interval.
You can configure the keepalive interval, which is the frequency at which the access server sends messages to itself (Ethernet and Token Ring) or to the other end (serial), to ensure a network interface is alive. The interval in previous software versions was 10 seconds; it is now adjustable in 1-second increments down to 1 second. An interface is declared down after three update intervals have passed without receiving a keepalive packet.
Setting the keepalive timer to a low value is very useful for rapidly detecting Ethernet interface failures (transceiver cable disconnecting, cable unterminated, and so on).
A typical serial line failure involves losing Carrier Detect (CD). Since this sort of failure is typically noticed within a few milliseconds, adjusting the keepalive timer for quicker routing recovery is generally not useful.
Note
Example
The following example sets the keepalive interval to 3 seconds:
interface ethernet 0keepalive 3loopback remote (interface)
To loop packets through a CSU/DSU, over a DS-3 link or a channelized T1 link, to the remote CSU/DSU and back, use the loopback remote interface configuration command. To remove the loop, use the no form of this command.
loopback remote
no loopback remoteSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command applies only when the remote CSU/DSU device supports the function. It is used for testing the data communication channels. The loopback usually is performed at the line port, rather than the DTE port, of the remote CSU/DSU.
For a multiport interface processor (MIP) connected to a network via a channelized T1 link, the loopback remote interface configuration command applies if the remote interface is served by a DDS line (56 Kbps or 64 Kbps), and the device at the remote end is a CSU/DSU. In addition, the CSU/DSU at the remote end must react to latched DDS CSU loopback codes. Destinations that are served by other types of lines or that have CSU/DSUs that do not react to latched DDS CSU codes cannot participate in an interface remote loopback. Latched DDS CSU loopback code requirements are described in AT&T specification TR-TSY-000476, "OTGR Network Maintenance Access and Testing."
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures a remote loopback test:
interface serial 0 loopback remoteRelated Command
loopback dte
To loop packets to DTE internally within the CSU/DSU at the DTE interface, use the loopback interface configuration command. Use the no form of this command to remove the loop.
loopback dte
no loopback dteSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Example
The following example configures the loopback test on the DTE interface:
interface serial 1 loopback dteloopback line
To loop packets completely through the CSU/DSU to configure the CSU loop, use the loopback line interface configuration command. Use the no form of this command to remove the loop.
loopback line
no loopback lineSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command is useful for testing the DCE device (CSU/DSU) itself.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures the loopback test on the DCE device:
interface serial 1 loopback lineRelated Command
loopback remote
To loop packets completely through the CSU/DSU, over the DS3 link, to the remote CSU/DSU and back, use the loopback remote interface configuration command. Use the no form of this command to remove the loop.
loopback remote
no loopback remoteSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command is useful for testing the DCE device (CSU/DSU) itself.
This command applies only when the device supports the remote function. It is used for testing the data communication channels. The loopback usually is performed at the line port, rather than the DTE port, of the remote CSU/DSU.
To show interfaces currently in loopback operation, use the show interfaces loopback EXEC command.
Example
The following example configures a remote loopback test:
interface serial 0 loopback remoteRelated Command
media-type
Use the media type command to specify one of the following configurations:
•
•
•
Use the no form of this command to restore the default value. The media-type full-duplex command replaces the bsc fdx command. The media-type half-duplex command replaces the sdlc hdx command.
media-type {aui | 10baset | 100baset | mii | full-duplex | half-duplex}
Syntax Description
Defaults
AUI 15-pin physical connection is the default setting on the Cisco 4000 series.
100BaseT physical connection is the default setting on the Cisco 7000 series.
Full-duplex the default mode for serial interfaces.
Half-duplex is the default mode for serial interfaces that are configured for bisynchronous tunneling.
Command Mode
Interface configuration
Examples
The following example specifies an RJ45 10BaseT physical connection to Ethernet interface 1:
interface ethernet 1media-type 10basetThe following example specifies a media-independent interface physical connection to Fast Ethernet slot 0, port 1 on the Cisco 7000:
interface fastethernet 0/1media-type miiThe following example specifies full duplex binary synchronous communications (BSC) mode:
interface serial 0encapsulation bstunmedia-type full-duplexThe following example specifies an SDLC interface as half-duplex mode:
interface serial 0encapsulation sdlc-primarymedia-type half-duplexmember
To alter the configuration of an asynchronous interface that is a member of a group, use the member interface configuration command. Use the no form of the command to restore defaults set at the group master interface.
member number interface-command
no member number interface commandSyntax Description
number
Number of the asynchronous interface to be altered.
interface-command
One or more commands entered for this specific interface. Valid commands are:
•
•
Default
No individual configurations are set for member interfaces.
Command Mode
Interface configuration
Usage Guidelines
You can customize a member interface by using the member command. (Interfaces are designated as members of a group by using the interface group-async and group-range commands). To restore the defaults set at the group master interface, use the no form of this command.
Examples
The following example defines interface 3 as having a description of line 3, attached to a Hayes Optima modem:
interface group-async 0 member 3 description line #3 Hayes OptimaRelated Commands
group-range
interface group-asyncmop enabled
To enable an interface to support the Maintenance Operation Protocol (MOP), use the mop enabled interface configuration command. Use the no form of this command to disable MOP on an interface.
mop enabled
no mop enabledSyntax Description
This command has no arguments or keywords.
Default
Enabled by default on Ethernet interfaces and disabled on all other interfaces.
Command Mode
Interface configuration
Example
In the following example, MOP is enabled for serial interface 0:
interface serial 0mop enabledRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
mop sysid
mop restransmit-timer †
mop retries †mop sysid
To enable an interface to send out periodic Maintenance Operation Protocol (MOP) system identification messages, use the mop sysid interface configuration command. Use the no form of this command to disable MOP message support on an interface.
mop sysid
no mop sysidSyntax Description
This command has no arguments or keywords.
Default
Enabled
Command Mode
Interface configuration
Usage Guidelines
You can run MOP without having the background system ID messages sent. This lets you use the MOP remote console, but does not generate messages used by the configurator.
Example
In the following example, serial interface 0 is enabled to send MOP system identification messages:
interface serial0mop sysidRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
mop device-code †
mop enabledmtu
To adjust the maximum packet size or maximum transmission unit (MTU) size, use the mtu interface configuration command. Use the no form of this command to restore the MTU value to its original default value.
mtu bytes
no mtuSyntax Description
Default
lists default MTU values according to media type.
Table 6-6
Default Media MTU Values
Command Mode
Interface configuration
Usage Guidelines
Each interface has a default maximum packet size or maximum transmission unit (MTU) size. This number generally defaults to the largest size possible for that type interface. On serial interfaces, the MTU size varies, but cannot be set smaller than 64 bytes.
Note
Example
The following example specifies an MTU of 1000 bytes:
interface serial 1 mtu 1000Related Commands
A dagger (†) indicates that the command is documented in another chapter.
encapsulation
ip mtu †peer default ip address
Use the peer default ip address command to specify an IP address, an address from a specific IP address pool, or an address from the DHCP mechanism to be returned to a remote peer connecting to this interface. Use the no form of the command to disable a prior peer IP address pooling configuration on an interface.
peer default ip address {ip-address | dhcp | pool [poolname]}
no peer default ip addressSyntax Description
Default
pool
Command Mode
Interface configuration
Usage Guidelines
This command applies to point-to-point interfaces that support the PPP or SLIP encapsulation.
This command allows an administrator to configure all possible address pooling mechanisms on a interface-by-interface basis.
The peer default ip address command can be used to override on an interface-by-interface basis the Global Default Mechanism defined by the ip address-pool command.
•
•
•
•
Examples
The following command specifies that this interface will use a local IP address pool called shazam:
peer default ip address pool shazamThe following command specifies that this interface will use the IP address 172.140.34.21:
peer default ip address 172.140.34.21The following command reenables the Global Default Mechanism to be used on this interface:
peer default ip address poolRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
encapsulation ppp
encapsulation slip
ip address-pool
ip dhcp-server
ip local pool
ppp †
slip†
show dhcpphysical-layer
To specify the mode of a slow-speed serial interface on a router as either synchronous or asynchronous, use the physical-layer interface configuration command. Use the no form of this command to return the interface to its default mode, which is synchronous.
physical-layer {sync | async}
no physical-layerSyntax Description
Default
Synchronous mode.
Command Mode
Interface Configuration
Usage Guidelines
This command applies only to low-speed serial interfaces available on Cisco 2520 through 2523 routers.
If you specify the no physical-layer command, you return the interface to its default mode (synchronous).
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
•
•
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces.
When you enter this command, it does not appear in the output of show running config and show startup config commands, because the command is a physical layer command.
Examples
The following examples show different uses of this command.
The following example shows how to change a low-speed serial interface from synchronous asynchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncThe following examples show how to change a low-speed serial interface from asynchronous mode back to its default synchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer syncorRouter(config)# interface serial 2Router(config-if)# no physical-layerThe following example shows some typical asynchronous interface configuration commands:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncRouter(config-if)# ip address 1.0.0.2 255.0.0.0Router(config-if)# async default ip address 1.0.0.1Router(config-if)# async mode dedicatedRouter(config-if)# async default routingThe following example shows some typical synchronous serial interface configuration commands available when the interface is in synchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer syncRouter(config-if)# ip address 1.0.0.2 255.0.0.0Router(config-if)# no keepaliveRouter(config-if)# ignore-dcdRouter(config-if)# nrzi-encodingRouter(config-if)# no shutdownRelated Commands
half-duplex controlled-carrier
half-duplex timerppp authentication
To enable Challenge Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP), and to enable a TACACS+ authorization method on a serial interface, use the ppp authentication interface configuration command. Use the no form of the command to disable this authentication.
ppp authentication {chap | pap} [if-needed] [listname]
no ppp authenticationSyntax Description
Default
PPP authentication is not enabled.
Command Mode
Interface configuration
Usage Guidelines
Once you have enabled CHAP or PAP, the local access server requires a password from remote devices. If the remote device does not support CHAP or PAP, no traffic will be passed to that device.
If you are using autoselect on a tty line, you will probably want to use the ppp authentication command to turn on PPP authentication for the corresponding interface.
When you specify the if-needed option, PPP authentication is not required when the user has already provided authentication. This option is useful in conjunction with the autoselect command, but cannot be used with AAA/TACACS+.
The list-name keyword can only be used when AAA/TACACS+ has been initialized and cannot be used with the if-needed argument.
CautionIf you use a list-name that has not been configured with the aaa authentication ppp command, you disable PPP on this line.
Example
The following example enables CHAP on asynchronous interface 4:
interface async 4 encapsulation ppp ppp authentication chapRelated Commands
A dagger (†) indicates that the command is documented in another chapter.
aaa authentication ppp†
aaa new-model†
autoselect†
encapsulation
ppp use-tacacs†
username†ppp quality
To enable Link Quality Monitoring (LQM) on a serial interface, use the ppp quality interface configuration command. Use the no form of this command to disable LQM.
ppp quality percentage
no ppp qualitySyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
The percentages are calculated for both incoming and outgoing directions. The outgoing quality is calculated by comparing the total number of packets and bytes sent to the total number of packets and bytes received by the peer. The incoming quality is calculated by comparing the total number of packets and bytes received to the total number of packets and bytes sent by the peer.
If the link quality percentage is not maintained, the link is deemed to be of poor quality and is taken down. The policy implements a time lag so that the link does not bounce up and down.
Example
The following example enables LQM on serial interface 0:
interface serial 0 encapsulation ppp ppp quality 80Related Commands
pulse-time
To enable pulsing DTR signal intervals on the serial interfaces, use the pulse-time interface configuration command. Use the no form of this command to restore the default interval.
pulse-time seconds
no pulse-timeSyntax Description
Default
0 seconds
Command Mode
Interface configuration
Usage Guidelines
When the serial line protocol goes down (for example, because of loss of synchronization) the interface hardware is reset and the DTR signal is held inactive for at least the specified interval. This function is useful for handling encrypting or other similar devices that use the toggling of the DTR signal to resynchronize.
Example
The following example enables DTR pulse signals for three seconds on serial interface 0:
interface serial 0 pulse-time 3ring-speed
To set the ring speed for the CSC-1R and CSC-2R Token Ring interfaces, use the ring-speed interface configuration command.
ring-speed speed
Syntax Description
Default
16-Mbps operation
Command Mode
Interface configuration
Usage Guidelines
CautionConfiguring a ring speed that is wrong or incompatible with the connected Token Ring will cause the ring to beacon, which effectively takes the ring down and makes it nonoperational.
Example
The following example sets a Token Ring interface ring speed to 4 Mbps:
interface tokenring 0 ring-speed 4scheduler-interval
To control the maximum amount of time that can elapse without running the lowest priority system processes, use the scheduler-interval global configuration command. Use the no form of this command to restore the default.
scheduler-interval milliseconds
no scheduler-intervalSyntax Description
milliseconds
An integer that specifies the interval in milliseconds. The minimum interval that you can specify is 500 milliseconds; there is no maximum value.
Default
The default is to allow high-priority operations to use as much of the central processor as needed.
Command Mode
Global configuration
Usage Guidelines
The normal operation of the network server allows the switching operations to use as much of the central processor as is required. If the network is running unusually heavy loads that do not allow the processor the time to handle the routing protocols, give priority to the system process scheduler.
Example
The following example changes the low-priority process schedule to an interval of 750 milliseconds:
scheduler-interval 750show async status
To list the status of asynchronous interfaces, use the show async status EXEC command:
show async status
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
This command shows all asynchronous sessions, whether they are using SLIP or PPP encapsulation.
Sample Display
The following is sample output from the show async status command:
Router> show async statusAsync protocol statistics:Rcvd: 5448 packets, 7682760 bytes1 format errors, 0 checksum errors, 0 overrun, 0 no bufferSent: 5455 packets, 7682676 bytes, 0 droppedInt Local Remote Qd InPack OutPac Inerr Drops MTU Qsz1 192.31.7.84 Dynamic 0 0 0 0 0 1500 10describes significant fields shown in the display.
Table 6-7 Asynchronous Statistics Display Field Descriptions
Related Command
interface async
show compress
To display compression statistics on a serial interface, use the show compress EXEC command.
show compress
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following is sample output from the show compress command:
Router# show compressSerial0uncompressed bytes xmt/rcv 10710562/113768351 min avg ratio xmt/rcv 2.773/2.4745 min avg ratio xmt/rcv 4.084/3.79310 min avg ratio xmt/rcv 4.125/3.873no bufs xmt 0 no bufs rcv 0resets 0describes the fields shown in the display.
Table 6-8 Show Compress Field Descriptions
Related Command
show controllers ethernet
Use the show controllers ethernet EXEC command to display information on the Cisco 2500.
show controllers ethernet interface-number
Syntax Description
Command Mode
EXEC
Sample Display
The following is sample output from the show controllers ethernet command:
Router# show controllers ethernet 0LANCE unit 0, NIM slot 1, NIM type code 4, NIM version 1Media Type is 10BaseT, Link State is Up, Squelch is Normalidb 0x4060, ds 0x5C80, regaddr = 0x8100000IB at 0x600D7AC: mode=0x0000, mcfilter 0000/0001/0000/0040station address 0000.0c03.a14f default station address 0000.0c03.a14fbuffer size 1524RX ring with 32 entries at 0xD7E8Rxhead = 0x600D8A0 (12582935), Rxp = 0x5CF0(23)00 pak=0x60336D0 ds=0x6033822 status=0x80 max_size=1524 pak_size=9801 pak=0x60327C0 ds=0x6032912 status=0x80 max_size=1524 pak_size=9802 pak=0x6036B88 ds=0x6036CDA status=0x80 max_size=1524 pak_size=9803 pak=0x6041138 ds=0x604128A status=0x80 max_size=1524 pak_size=9804 pak=0x603FAA0 ds=0x603FBF2 status=0x80 max_size=1524 pak_size=9805 pak=0x600DC50 ds=0x600DDA2 status=0x80 max_size=1524 pak_size=9806 pak=0x6023E48 ds=0x6023F9A status=0x80 max_size=1524 pak_size=150607 pak=0x600E3D8 ds=0x600E52A status=0x80 max_size=1524 pak_size=150608 pak=0x6020990 ds=0x6020AE2 status=0x80 max_size=1524 pak_size=38609 pak=0x602D4E8 ds=0x602D63A status=0x80 max_size=1524 pak_size=9810 pak=0x603A7C8 ds=0x603A91A status=0x80 max_size=1524 pak_size=9811 pak=0x601D4D8 ds=0x601D62A status=0x80 max_size=1524 pak_size=9812 pak=0x603BE60 ds=0x603BFB2 status=0x80 max_size=1524 pak_size=9813 pak=0x60318B0 ds=0x6031A02 status=0x80 max_size=1524 pak_size=9814 pak=0x601CD50 ds=0x601CEA2 status=0x80 max_size=1524 pak_size=9815 pak=0x602C5D8 ds=0x602C72A status=0x80 max_size=1524 pak_size=9816 pak=0x60245D0 ds=0x6024722 status=0x80 max_size=1524 pak_size=9817 pak=0x6008328 ds=0x600847A status=0x80 max_size=1524 pak_size=9818 pak=0x601EB70 ds=0x601ECC2 status=0x80 max_size=1524 pak_size=9819 pak=0x602DC70 ds=0x602DDC2 status=0x80 max_size=1524 pak_size=9820 pak=0x60163E0 ds=0x6016532 status=0x80 max_size=1524 pak_size=9821 pak=0x602CD60 ds=0x602CEB2 status=0x80 max_size=1524 pak_size=9822 pak=0x6037A98 ds=0x6037BEA status=0x80 max_size=1524 pak_size=9823 pak=0x602BE50 ds=0x602BFA2 status=0x80 max_size=1524 pak_size=9824 pak=0x6018988 ds=0x6018ADA status=0x80 max_size=1524 pak_size=9825 pak=0x6033E58 ds=0x6033FAA status=0x80 max_size=1524 pak_size=9826 pak=0x601BE40 ds=0x601BF92 status=0x80 max_size=1524 pak_size=9827 pak=0x6026B78 ds=0x6026CCA status=0x80 max_size=1524 pak_size=9828 pak=0x6024D58 ds=0x6024EAA status=0x80 max_size=1524 pak_size=7429 pak=0x602AF40 ds=0x602B092 status=0x80 max_size=1524 pak_size=9830 pak=0x601FA80 ds=0x601FBD2 status=0x80 max_size=1524 pak_size=9831 pak=0x6038220 ds=0x6038372 status=0x80 max_size=1524 pak_size=98TX ring with 8 entries at 0xDA20, tx_count = 0tx_head = 0x600DA58 (12582919), head_txp = 0x5DC4 (7)tx_tail = 0x600DA58 (12582919), tail_txp = 0x5DC4 (7)00 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11801 pak=0x000000 ds=0x602126A status=0x03 status2=0x0000 pak_size=6002 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11803 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11804 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11805 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11806 pak=0x000000 ds=0x600CF12 status=0x03 status2=0x0000 pak_size=11807 pak=0x000000 ds=0x6003ED2 status=0x03 status2=0x0000 pak_size=1260 missed datagrams, 0 overruns, 2 late collisions, 2 lost carrier events0 transmitter underruns, 0 excessive collisions, 0 tdr, 0 babbles0 memory errors, 0 spurious initialization done interrupts0 no enp status, 0 buffer errors, 0 overflow errors10 one_col, 10 more_col, 22 deferred, 0 tx_buff0 throttled, 0 enabledLance csr0 = 0x73show controllers mci
Use the show controllers mci privileged EXEC command to display all information about the Multiport Communications Interface card. This command displays information the system uses for bridging and routing that is specific to the interface hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
show controllers mci
Syntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Sample Display
The following is sample output from the show controllers mci command:
Router# show controllers mciMCI 0, controller type 1.1, microcode version 1.8128 Kbytes of main memory, 4 Kbytes cache memory22 system TX buffers, largest buffer size 1520Restarts: 0 line down, 0 hung output, 0 controller errorInterface 0 is Ethernet0, station address 0000.0c00.d4a615 total RX buffers, 11 buffer TX queue limit, buffer size 1520Transmitter delay is 0 microsecondsInterface 1 is Serial0, electrical interface is V.35 DTE15 total RX buffers, 11 buffer TX queue limit, buffer size 1520Transmitter delay is 0 microsecondsHigh speed synchronous serial interfaceInterface 2 is Ethernet1, station address aa00.0400.3be415 total RX buffers, 11 buffer TX queue limit, buffer size 1520Transmitter delay is 0 microsecondsInterface 3 is Serial1, electrical interface is V.35 DCE15 total RX buffers, 11 buffer TX queue limit, buffer size 1520Transmitter delay is 0 microsecondsHigh speed synchronous serial interfacedescribes significant fields shown in the display.
Table 6-9 Show Controllers MCI Field Descriptions
Note
Related Command
show controllers serial
Use the show controllers serial privileged EXEC command to display information that is specific to the interface hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
show controllers serial
Syntax Description
This command has no arguments or keywords.
Command Mode
Privileged EXEC
Sample Display
Sample output of the show controllers serial command:
Router# show controllers serialMK5 unit 0, NIM slot 1, NIM type code 7, NIM version 1idb = 0x6150, driver structure at 0x34A878, regaddr = 0x8100300IB at 0x6045500: mode=0x0108, local_addr=0, remote_addr=0N1=1524, N2=1, scaler=100, T1=1000, T3=2000, TP=1buffer size 1524DTE V.35 serial cable attachedRX ring with 32 entries at 0x45560 : RLEN=5, Rxhead 000 pak=0x6044D78 ds=0x6044ED4 status=80 max_size=1524 pak_size=001 pak=0x60445F0 ds=0x604474C status=80 max_size=1524 pak_size=002 pak=0x6043E68 ds=0x6043FC4 status=80 max_size=1524 pak_size=003 pak=0x60436E0 ds=0x604383C status=80 max_size=1524 pak_size=004 pak=0x6042F58 ds=0x60430B4 status=80 max_size=1524 pak_size=005 pak=0x60427D0 ds=0x604292C status=80 max_size=1524 pak_size=006 pak=0x6042048 ds=0x60421A4 status=80 max_size=1524 pak_size=007 pak=0x60418C0 ds=0x6041A1C status=80 max_size=1524 pak_size=008 pak=0x6041138 ds=0x6041294 status=80 max_size=1524 pak_size=009 pak=0x60409B0 ds=0x6040B0C status=80 max_size=1524 pak_size=010 pak=0x6040228 ds=0x6040384 status=80 max_size=1524 pak_size=011 pak=0x603FAA0 ds=0x603FBFC status=80 max_size=1524 pak_size=012 pak=0x603F318 ds=0x603F474 status=80 max_size=1524 pak_size=013 pak=0x603EB90 ds=0x603ECEC status=80 max_size=1524 pak_size=014 pak=0x603E408 ds=0x603E564 status=80 max_size=1524 pak_size=015 pak=0x603DC80 ds=0x603DDDC status=80 max_size=1524 pak_size=016 pak=0x603D4F8 ds=0x603D654 status=80 max_size=1524 pak_size=017 pak=0x603CD70 ds=0x603CECC status=80 max_size=1524 pak_size=018 pak=0x603C5E8 ds=0x603C744 status=80 max_size=1524 pak_size=019 pak=0x603BE60 ds=0x603BFBC status=80 max_size=1524 pak_size=020 pak=0x603B6D8 ds=0x603B834 status=80 max_size=1524 pak_size=021 pak=0x603AF50 ds=0x603B0AC status=80 max_size=1524 pak_size=022 pak=0x603A7C8 ds=0x603A924 status=80 max_size=1524 pak_size=023 pak=0x603A040 ds=0x603A19C status=80 max_size=1524 pak_size=024 pak=0x60398B8 ds=0x6039A14 status=80 max_size=1524 pak_size=025 pak=0x6039130 ds=0x603928C status=80 max_size=1524 pak_size=026 pak=0x60389A8 ds=0x6038B04 status=80 max_size=1524 pak_size=027 pak=0x6038220 ds=0x603837C status=80 max_size=1524 pak_size=028 pak=0x6037A98 ds=0x6037BF4 status=80 max_size=1524 pak_size=029 pak=0x6037310 ds=0x603746C status=80 max_size=1524 pak_size=030 pak=0x6036B88 ds=0x6036CE4 status=80 max_size=1524 pak_size=031 pak=0x6036400 ds=0x603655C status=80 max_size=1524 pak_size=0TX ring with 8 entries at 0x45790 : TLEN=3, TWD=7tx_count = 0, tx_head = 7, tx_tail = 700 pak=0x000000 ds=0x600D70C status=0x38 max_size=1524 pak_size=2201 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=202 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=203 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=204 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=205 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=206 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=207 pak=0x000000 ds=0x6000000 status=0x38 max_size=1524 pak_size=0XID/Test TX desc at 0xFFFFFF, status=0x30, max_buffer_size=0, packet_size=0XID/Test RX desc at 0xFFFFFF, status=0x0, max_buffer_size=0, packet_size=0Status Buffer at 0x60459C8: rcv=0, tcv=0, local_state=0, remote_state=0phase=0, tac=0, currd=0x00000, curxd=0x00000bad_frames=0, frmrs=0, T1_timeouts=0, rej_rxs=0, runts=00 missed datagrams, 0 overruns, 0 bad frame addresses0 bad datagram encapsulations, 0 user primitive errors0 provider primitives lost, 0 unexpected provider primitives0 spurious primitive interrupts, 0 memory errors, 0 tr%LINEPROTO-5-UPDOWN: Linansmitter underrunsmk5025 registers: csr0 = 0x0E00, csr1 = 0x0302, csr2 = 0x0704csr3 = 0x5500, csr4 = 0x0214, csr5 = 0x0008show controllers token
To display information about memory management, error counters, and the CSC-1R, CSC-2R, and or CSC-R16M Token Ring interface cards, use the show controllers token privileged EXEC command.
show controllers token
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Usage Guidelines
Depending on the board being used, the output can vary. This command also displays information that is proprietary to Cisco Systems. Thus, the information that show controllers token displays is of primary use to Cisco technical personnel. Information that is useful to users can be obtained using the show interfaces tokenring command, described later in this chapter.
Sample Display
The following is sample output of the show controllers token command:
Router# show controllers tokenTR Unit 0 is board 0 - ring 0state 3, dev blk: 0x1D2EBC, mailbox: 0x2100010, sca: 0x2010000current address: 0000.3080.6f40, burned in address: 0000.3080.6f40current TX ptr: 0xBA8, current RX ptr: 0x800Last Ring Status: noneStats: soft:0/0, hard:0/0, sig loss:0/0tx beacon: 0/0, wire fault 0/0, recovery: 0/0only station: 0/0, remote removal: 0/0Bridge: local 3330, bnum 1, target 3583max_hops 7, target idb: 0x0, not localInterface failures: 0 -- Bkgnd Ints: 0TX shorts 0, TX giants 0Monitor state: (active)flags 0xC0, state 0x0, test 0x0, code 0x0, reason 0x0f/w ver: 1.0, chip f/w: '000000.ME31100', [bridge capable]SMT versions: 1.01 kernel, 4.02 fastmacring mode: F00, internal enables: SRB REM RPS CRS/NetMgrinternal functional: 0000011A (0000011A), group: 00000000 (00000000)if_state: 1, ints: 0/0, ghosts: 0/0, bad_states: 0/0t2m fifo purges: 0/0t2m fifo current: 0, t2m fifo max: 0/0, proto_errs: 0/0ring: 3330, bridge num: 1, target: 3583, max hops: 7Packet counts:receive total: 298/6197, small: 298/6197, large 0/0runts: 0/0, giants: 0/0local: 298/6197, bridged: 0/0, promis: 0/0bad rif: 0/0, multiframe: 0/0ring num mismatch 0/0, spanning violations 0transmit total: 1/25, small: 1/25, large 0/0runts: 0/0, giants: 0/0, errors 0/0bad fs: 0/0, bad ac: 0congested: 0/0, not present: 0/0Unexpected interrupts: 0/0, last unexp. int: 0Internal controller counts:line errors: 0/0, internal errors: 0/0burst errors: 0/0, ari/fci errors: 0/0abort errors: 0/0, lost frame: 0/0copy errors: 0/0, rcvr congestion: 0/0token errors: 0/0, frequency errors: 0/0dma bus errors: -/-, dma parity errors: -/-Internal controller smt state:Adapter MAC: 0000.3080.6f40, Physical drop: 00000000NAUN Address: 0000.a6e0.11a6, NAUN drop: 00000000Last source: 0000.a6e0.11a6, Last poll: 0000.3080.6f40Last MVID: 0006, Last attn code: 0006Txmit priority: 0006, Auth Class: 7FFFMonitor Error: 0000, Interface Errors: FFFFCorrelator: 0000, Soft Error Timer: 00C8Local Ring: 0000, Ring Status: 0000Beacon rcv type: 0000, Beacon txmit type: 0000Beacon type: 0000, Beacon NAUN: 0000.a6e0.11a6describes the fields shown in the following line of sample output.
TR Unit 0 is board 0 - ring 0Table 6-10 Show Controllers Token Field Descriptions
—Part 1
In the following output line, state 3 indicates the state of the board. The rest of this output line displays memory mapping that is of primary use to Cisco engineers.
state 3, dev blk: 0x1D2EBC, mailbox: 0x2100010, sca: 0x2010000The following line also appears in show interface token output as the address and burned-in address, respectively:
current address: 0000.3080.6f40, burned in address: 0000.3080.6f40The following line of output displays buffer management pointers that change by board:
current TX ptr: 0xBA8, current RX ptr: 0x800The following line of output indicates the ring status from the controller chip set. This information is used by LAN Network Manager:
Last Ring Status: noneThe following lines of output show Token Ring statistics. See the Token Ring specification for more information.
Stats: soft:0/0, hard:0/0, sig loss:0/0tx beacon: 0/0, wire fault 0/0, recovery: 0/0only station: 0/0, remote removal: 0/0The following line of output indicates that Token Ring communication has been enabled on the interface. If this line of output appears, the message "Source Route Bridge capable" should appear in the show interfaces tokenring display.
Bridge: local 3330, bnum 1, target 3583describes the fields shown in the following line of sample output.
max_hops 7, target idb: 0x0, not localTable 6-11 Show Controllers Token Field Descriptions
max_hops 7
Maximum number of bridges.
target idb: 0x0
Destination interface definition.
not local
Indicates whether the interface has been defined as a local or remote bridge.
—Part 2
The following line of output is specific to the hardware:
Interface failures: 0 -- Bkgnd Ints: 0In the following line of output, TX shorts are the number of packets the interface transmits that are discarded because they are smaller than the medium's minimum packet size. TX giants are the number of packets the interface transmits that are discarded because they exceed the medium's maximum packet size.
TX shorts 0, TX giants 0The following line of output indicates the state of the controller. Possible values include active, failure, inactive, and reset:
Monitor state: (active)The following line of output displays detailed information relating to the monitor state shown in the previous line of output. This information relates to the firmware on the controller. This information is relevant to Cisco engineers only if the monitor state is something other than active.
flags 0xC0, state 0x0, test 0x0, code 0x0, reason 0x0describes the fields in the following line of output:
f/w ver: 1.0 expr 0, chip f/w: '000000.ME31100', [bridge capable]Table 6-12 Show Controllers Token Field Descriptions
—Part 3
The following line of output displays the version numbers for the kernel and the accelerator microcode of the Madge firmware on the board; this firmware is the LLC interface to the chip set:
SMT versions: 1.01 kernel, 4.02 fastmacThe following line of output displays LAN Network Manager information that relates to ring status:
ring mode: F00, internal enables: SRB REM RPS CRS/NetMgrThe following line of output corresponds to the functional address and the group address shown in show interfaces tokenring output:
internal functional: 0000011A (0000011A), group: 00000000 (00000000)The following line of output displays interface board state information that is proprietary to Cisco Systems:
if_state: 1, ints: 0/0, ghosts: 0/0, bad_states: 0/0The following output lines display information that is proprietary to Cisco Systems. Cisco engineers use this information for debugging purposes.
t2m fifo purges: 0/0t2m fifo current: 0, t2m fifo max: 0/0, proto_errs: 0/0Each of the fields in the following line of output maps to a field in the show source bridge display, as follows: ring maps to srn; bridge num maps to bn; target maps to trn; and max hops maps to max:
ring: 3330, bridge num: 1, target: 3583, max hops: 7In the following lines of output, the number preceding the slash (/) indicates the count since the value was last displayed; the number following the slash (/) indicates count since the system was last booted:
Packet counts:receive total: 298/6197, small: 298/6197, large 0/0In the following line of output, the number preceding the slash (/) indicates the count since the value was last displayed; the number following the slash (/) indicates count since the system was last booted. The runts and giants values that appear here correspond to the runts and giants values that appear in show interfaces tokenring output.
runts: 0/0, giants: 0/0The following lines of output are receiver-specific information that Cisco engineers can use for debugging purposes:
local: 298/6197, bridged: 0/0, promis: 0/0bad rif: 0/0, multiframe: 0/0ring num mismatch 0/0, spanning violations 0transmit total: 1/25, small: 1/25, large 0/0runts: 0/0, giants: 0/0, errors 0/0The following output lines include very specific statistics that are not relevant in most cases, but exist for historical purposes. In particular, the internal errors, burst errors, ari/fci, abort errors, copy errors, frequency errors, dma bus errors, and dma parity errors fields are not relevant.
Internal controller counts:line errors: 0/0, internal errors: 0/0burst errors: 0/0, ari/fci errors: 0/0abort errors: 0/0, lost frame: 0/0copy errors: 0/0, rcvr congestion: 0/0token errors: 0/0, frequency errors: 0/0dma bus errors: -/-, dma parity errors: -/-The following lines of output are low-level Token Ring interface statistics relating to the state and status of the Token Ring with respect to all other Token Rings on the line:
Internal controller smt state:Adapter MAC: 0000.3080.6f40, Physical drop: 00000000NAUN Address: 0000.a6e0.11a6, NAUN drop: 00000000Last source: 0000.a6e0.11a6, Last poll: 0000.3080.6f40Last MVID: 0006, Last attn code: 0006Txmit priority: 0006, Auth Class: 7FFFMonitor Error: 0000, Interface Errors: FFFFCorrelator: 0000, Soft Error Timer: 00C8Local Ring: 0000, Ring Status: 0000Beacon rcv type: 0000, Beacon txmit type: 0000show dhcp
Use the show dhcp command to display the current DHCP settings on the access server's asynchronous interfaces.
show dhcp [interface number]
Syntax Description
Command Mode
Privileged EXEC
Usage Guidelines
If you omit the optional argument, the show dhcp command displays information about all interfaces.
Sample Display
Router# show dhcp serverIP address pooling for Point to Point clients is: DHCP Proxy ClientDHCP Proxy Client Status:DHCP server: ANY (255.255.255.255)Leases: 0Offers: 0 Requests: 0 Acks: 0 Naks: 0Declines: 0 Releases: 0 Bad: 0describes the fields shown in the display.
Table 6-13 Show DHCP Field Descriptions
Related Commands
ip address-pool
ip dhcp-server
peer default ip address
show interfaces
Use the show interfaces EXEC command to display statistics for all interfaces configured on the access server. The resulting output varies, depending on the network for which an interface has been configured.
show interfaces [type number] [accounting]
Syntax Description
Command Mode
EXEC
Usage Guidelines
The show interfaces command displays statistics for the network interfaces. If you enter a show interfaces command for an interface type that has been removed from the access server, interface statistics will be displayed accompanied by the following text: "Hardware has been removed."
You will use the show interfaces command frequently while configuring and monitoring access servers. The various forms of the show interfaces commands are described in detail in the sections immediately following this command.
To display the number of packets of each protocol type that have been sent through all configured interfaces, use the show interfaces accounting EXEC command. When you use the accounting option, only the accounting statistics are displayed.
lists the protocols for which per-packet accounting information is kept.
Table 6-14 Per-Packet Counted Protocols
Sample Display
The following is sample output from the show interfaces command. Because your display will depend on the type and number of interface cards in your access server, only a portion of the display is shown.
Router# show interfacesEthernet 0 is up, line protocol is upHardware is MCI Ethernet, address is 0000.0c00.750c (bia 0000.0c00.750c)Internet address is 172.30.28.8, subnet mask is 255.255.255.0MTU 1500 bytes, BW 10000 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, ARP Timeout 4:00:00Last input 0:00:00, output 0:00:00, output hang neverLast clearing of "show interface" counters 0:00:00Output queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 2000 bits/sec, 4 packets/sec1127576 packets input, 447251251 bytes, 0 no bufferReceived 354125 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort5332142 packets output, 496316039 bytes, 0 underruns0 output errors, 432 collisions, 0 interface resets, 0 restarts---More---Sample Display with Accounting Option
The following is sample output from the show interfaces accounting command:
Router# show interfaces accountingEthernet0Protocol Pkts In Chars In Pkts Out Chars OutIP 873171 735923409 34624 9644258Novell 163849 12361626 57143 4272468DEC MOP 0 0 1 77ARP 69618 4177080 1529 91740When the output indicates an interface is "disabled," the access server has received excessive errors (over 5000 in a keepalive period).
show interfaces async
Use the show interfaces async EXEC command to display information about the serial interface.
show interfaces async [unit] [accounting]
Syntax Description
unit
(Optional) Must be 1.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
Sample Display
The following is sample output from the show interfaces async command:
Router# show interfaces async 1Async 1 is up, line protocol is upHardware is Async SerialInternet address is 172.30.0.1, subnet mask is 255.0.0.0MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 56/255Encapsulation SLIP, keepalive set (0 sec)Last input 0:00:03, output 0:00:03, output hang neverLast clearing of "show interface" counters neverOutput queue 0/3, 2 drops; input queue 0/0, 0 dropsFive minute input rate 0 bits/sec, 1 packets/secFive minute output rate 2000 bits/sec, 1 packets/sec273 packets input, 13925 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort221 packets output, 41376 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restarts0 carrier transitions
Note
The following is a sample display from the show interfaces async accounting command:
Router# show interfaces async 0 accountingAsync 0Protocol Pkts In Chars In Pkts Out Chars OutIP 7344 4787842 1803 1535774DEC MOP 0 0 127 9779ARP 7 420 39 2340The show line and show slip commands can also be useful in monitoring asynchronous interfaces.
describes the fields shown in the two sample displays.
Table 6-15 Show Interfaces Async Field Descriptions
show interfaces dialer
Use the show interfaces dialer EXEC command to display information about the dialer interface.
show interfaces dialer unit [accounting]
Syntax Description
unit
Must match a port number on the selected interface.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
show interfaces ethernet
Use the show interfaces ethernet EXEC command to display information about an Ethernet interface on the access server.
show interfaces ethernet unit [accounting]
Syntax Description
unit
Must match a port number on the selected interface.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
Usage Guidelines
If you do not provide values for the argument unit, the command will display statistics for all network interfaces. The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.
Sample Display
The following is sample output from the show interfaces command for the Ethernet 0 interface:
Router# show interfaces ethernet 0Ethernet 0 is up, line protocol is upHardware is MCI Ethernet, address is aa00.0400.0134 (bia 0000.0c00.4369)Internet address is 172.30.1.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 10000 Kbit, DLY 1000 usec, rely 255/255, load 1/255Encapsulation ARPA, loopback not set, keepalive set (10 sec)ARP type: ARPA, PROBE, ARP Timeout 4:00:00Last input 0:00:00, output 0:00:00, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 2 dropsFive minute input rate 61000 bits/sec, 4 packets/secFive minute output rate 1000 bits/sec, 2 packets/sec2295197 packets input, 305539992 bytes, 0 no bufferReceived 1925500 broadcasts, 0 runts, 0 giants3 input errors, 3 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort3594664 packets output, 436549843 bytes, 0 underruns8 output errors, 1790 collisions, 10 interface resets, 0 restartsdescribes significant fields shown in the display.
Table 6-16 Show Interfaces Ethernet Field Descriptions
show interfaces ip-brief
To list a brief summary of an interface IP information and status, use the show interfaces ip-brief EXEC command.
show interfaces ip-brief
Syntax Description
This command has no arguments or keywords.
Command Mode
EXEC
Sample Display
The following provides sample output from the show interfaces ip-brief command:
Router# show interfaces ip-briefAny interface listed with OK? value "NO" does not have a valid configurationInterface IP-Address OK? Method Status ProtocolEthernet0 172.30.160.22 YES NVRAM up upshow interfaces loopback
Use the show interfaces loopback EXEC command to display information about the dialer interface.
show interfaces loopback [unit] [accounting]
Syntax Description
unit
(Optional) Must match a port number on the selected interface.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
Sample Displays
The following is sample output from the show interfaces loopback command:
Router# show interfaces loopback 0Loopback0 is up, line protocol is upHardware is LoopbackMTU 1500 bytes, BW 1 Kbit, DLY 50 usec, rely 255/255, load 1/255Encapsulation UNKNOWN, loopback not set, keepalive set (10 sec)Last input never, output never, output hang neverLast clearing of "show interface" counters neverOutput queue 0/0, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 input packets with dribble condition detected0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restartsThe following is sample when the accounting keyword is included:
Router# show interfaces loopback 0 accountingLoopback0Protocol Pkts In Chars In Pkts Out Chars OutNo traffic sent or received on this interface.describes significant fields shown in the displays.
Table 6-17 Show Interfaces Loopback Descriptions
show interfaces serial
Use the show interfaces serial privileged EXEC command to display information about a serial interface.
show interfaces serial number [accounting]
Syntax Description
number
(Optional) Must match the interface port number.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
Privileged EXEC
Sample Display
The following is sample output from the show interfaces command for a synchronous serial interface:
Router# show interfaces serialSerial 0 is up, line protocol is upHardware is MCI SerialInternet address is 172.30.190.203, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Last input 0:00:07, output 0:00:00, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec16263 packets input, 1347238 bytes, 0 no bufferReceived 13983 broadcasts, 0 runts, 0 giants2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 2 abort1 carrier transitions22146 packets output, 2383680 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restartsdescribes significant fields shown in the display.
Table 6-18 Show Interfaces Serial Field Descriptions
Sample Display with Frame Relay Encapsulation
When using the Frame Relay encapsulation, use the show interfaces command to display information on the multicast DLCI, the DLCI of the interface, and the LMI DLCI used for the local management interface.
The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and the frame-relay local-dlci configuration commands, or provided through the local management interface. The status information is taken from the LMI, when active.
The following is a sample display from the show interfaces serial output when using Frame Relay encapsulation:
Router# show interfaces serialSerial 2 is up, line protocol is upHardware type is MCI SerialInternet address is 172.30.122.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)multicast DLCI 1022, status defined, activesource DLCI 20, status defined, activeLMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2Last input 7:21:29, output 0:00:37, output hang neverOutput queue 0/100, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec47 packets input, 2656 bytes, 0 no bufferReceived 5 broadcasts, 0 runts, 0 giants5 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 57 abort518 packets output, 391205 bytes0 output errors, 0 collisions, 0 interface resets, 0 restarts1 carrier transitionsIn this display, the multicast DLCI has been changed to 1022 with the frame-relay multicast-dlci interface configuration command.
The display shows the statistics for the LMI are the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). See the Frame Relay Interface specification for additional explanations of this output.
Sample Display with ANSI LMI
For a serial interface with the ANSI LMI enabled, use the show interfaces command to determine the LMI type implemented.
The following is a sample display from the show interfaces output for a serial interface with the ANSI LMI enabled.
Router# show interfaces serialSerial 1 is up, line protocol is upHardware is MCI SerialInternet address is 172.30.121.1, subnet mask is 255.255.255.0MTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec, rely 255/255, load 1/255Encapsulation FRAME-RELAY, loopback not set, keepalive setLMI DLCI 0, LMI sent 10, LMI stat recvd 10LMI type is ANSI Annex DLast input 0:00:00, output 0:00:00, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 1 packets/secFive minute output rate 1000 bits/sec, 1 packets/sec261 packets input, 13212 bytes, 0 no bufferReceived 33 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort238 packets output, 14751 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restartsNotice that the show interfaces output for a serial interface with ANSI LMI is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. describes the differences that exist.
Table 6-19 Show Interfaces Field Description
with ANSI LMI
Sample Display with LAPB Encapsulation
Use the show interfaces command to display operation statistics for an interface using LAPB encapsulation.
The following is sample output from the show interfaces command for a serial interface using LAPB encapsulation:
Router# show interfacesLAPB state is DISCONNECT, T1 3000, N1 12000, N2 20, K7, TH 3000Window is closedIFRAMEs 12/28 RNRs 0/1 REJs 13/1 SABMs 1/13 FRMRs 3/0 DISCs 0/11shows the fields relevant to all LAPB connections.
Table 6-20 Show Interfaces Serial Fields and Descriptions When LAPB Is Enabled
Show Interfaces Serial with PPPAn interface configured for synchronous PPP encapsulation differs from the standard show interface serial output in the fourth and fifth lines displayed. An interface configured for PPP might include the following information:
Encapsulation PPP, loopback not set, keepalive set (10 sec)PPP: No valid link quality reports received.The output line that reads "PPP: No valid link quality reports received" indicates that no reports have been received. If link quality monitoring is not negotiated, then that line will indicate the following:
PPP: LQM not negotiated.If LQM has been negotiated, and if link quality reports have been received, it will display the following:
PPP: LQR transmit interval 10 sec, receive interval 10 seclocal tx/remote rx: packets 50/50 bytes 147/147 success 16/16remote tx/local rx: packets 49/50 bytes 753/790 success 16/16This display contrasts the number of packets and bytes transmitted with the number received by the remote end, and the number of successful link quality reports received.
show interfaces tokenring
Use the show interfaces tokenring EXEC command to display information about the Token Ring interface and the state of source route bridging.
show interfaces tokenring unit [accounting]
Syntax Description
unit
Must match the interface port line number.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
Usage Guidelines
The optional keyword accounting displays the number of packets of each protocol type that have been sent through the interface.
Sample Display
The following is sample output from the show interfaces tokenring command.
Router# show interfaces tokenringTokenRing 0 is up, line protocol is upHardware is 16/4 Token Ring, address is 5500.2000.dc27 (bia 0000.3000.072b)Internet address is 172.30.230.203, subnet mask is 255.255.255.0MTU 8136 bytes, BW 16000 Kbit, DLY 630 usec, rely 255/255, load 1/255Encapsulation SNAP, loopback not set, keepalive set (10 sec)ARP type: SNAP, ARP Timeout 4:00:00Ring speed: 16 MbpsSingle ring node, Source Route Bridge capableGroup Address: 0x00000000, Functional Address: 0x60840000Last input 0:00:01, output 0:00:01, output hang neverOutput queue 0/40, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec16339 packets input, 1496515 bytes, 0 no bufferReceived 9895 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort32648 packets output, 9738303 bytes, 0 underruns0 output errors, 0 collisions, 2 interface resets, 0 restarts5 transitionsdescribes significant fields shown in the display.
Table 6-21 Show Interfaces Tokenring Field Descriptions
show interfaces tunnel
To list tunnel interface information, use the show interfaces tunnel EXEC command.
show interfaces tunnel unit [accounting]
Syntax Description
unit
Must match the interface port line number.
accounting
(Optional) Displays the number of packets of each protocol type that have been sent through the interface.
Command Mode
EXEC
Sample Display
The following example provides sample output from the show interface tunnel command:
Router# show interfaces tunnel 4Tunnel4 is up, line protocol is downHardware is Routing TunnelMTU 1500 bytes, BW 9 Kbit, DLY 500000 usec, rely 255/255, load 1/255Encapsulation TUNNEL, loopback not set, keepalive set (10 sec)Tunnel source 0.0.0.0, destination 0.0.0.0Tunnel protocol/transport GRE/IP, key disabled, sequencing disabledLast input never, output never, output hang neverLast clearing of "show interface" counters neverOutput queue 0/0, 0 drops; input queue 0/75, 0 dropsFive minute input rate 0 bits/sec, 0 packets/secFive minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 input packets with dribble condition detected0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restartsdescribes significant fields shown in the display.
Table 6-22 Show Interfaces Tunnel Field Descriptions
Related Commands
A dagger (†) indicates that the command is documented in another chapter.
show ip route †
show route †show interfaces vty
Use the show interfaces vty EXEC command to display information about virtual asynchronous interfaces.
show interfaces vty number
Syntax Description
Command Mode
EXEC
Sample Display
The following is sample output from the show interfaces vty command:
Router# sh int vty17VTY-Async17 is up, line protocol is upHardware is Virtual Async SerialInterface is unnumbered. Using address of Ethernet0 (172.30.60.44)MTU 1500 bytes, BW 9 Kbit, DLY 100000 usec, rely 255/255, load 1/255Encapsulation SLIP, loopback not setDTR is pulsed for 5 seconds on resetLast input never, output never, output hang neverLast clearing of "show interface" counters neverOutput queue 0/10, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets, 0 restarts0 carrier transitionsdescribes the fields shown in the sample display.
Table 6-23 Show Interfaces VTY Field Descriptions
show ip interface
To list a summary of an interface's IP information and status, use the show ip interface privileged EXEC command.
show ip interface [brief] [type] [number]
Syntax Description
Command Mode
Privileged EXEC
Sample Displays
The following is sample output from the show ip interface command:
Router# show ip interfaceEthernet0 is administratively down, line protocol is downInternet address is 172.30.46.10, subnet mask is 255.0.0.0Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is enabledMulticast groups joined: 224.0.0.1 224.0.0.2Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP SSE switching is disabledRouter Discovery is disabledIP accounting is disabledTCP/IP header compression is disabledProbe proxy name replies are disabledGateway Discovery is disabledPCbus0 is administratively down, line protocol is downInternet address is 172.30.1.43, subnet mask is 255.255.255.0Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is enabledMulticast groups joined: 224.0.0.1 224.0.0.2Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP SSE switching is disabledRouter Discovery is disabledIP accounting is disabledTCP/IP header compression is disabledProbe proxy name replies are disabledGateway Discovery is disabledSerial0 is administratively down, line protocol is downInternet address is 172.30.2.49, subnet mask is 255.255.255.0Broadcast address is 255.255.255.255Address determined by setup commandMTU is 1500 bytesHelper address is not setDirected broadcast forwarding is enabledMulticast groups joined: 224.0.0.1 224.0.0.2Outgoing access list is not setInbound access list is not setProxy ARP is enabledSecurity level is defaultSplit horizon is enabledICMP redirects are always sentICMP unreachables are always sentICMP mask replies are never sentIP fast switching is enabledIP fast switching on the same interface is disabledIP SSE switching is disabledRouter Discovery is disabledIP accounting is disabledTCP/IP header compression is disabledProbe proxy name replies are disabledGateway Discovery is disabledThe following is sample output from the show ip interface brief command:
Router# show ip interface briefInterface IP-Address OK? Method Status ProtocolEthernet0 172.30.46.10 YES manual administratively down downPCbus0 172.30.1.43 YES manual administratively down downSerial0 172.30.2.49 YES manual administratively down downThe following is sample output from the show ip interface brief pcbus 0 command:
Router# show ip interface brief pcbus 0Interface IP-Address OK? Method Status ProtocolPCbus0 172.30.1.43 YES manual administratively down downRelated Command
show ip local pool
To display statistics for any defined IP address pools, use the show ip local pool privileged EXEC command.
show ip local pool [name]
Syntax Description
Command Mode
Privileged EXEC
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.
Sample Display
Router# show ip local poolScope Begin End Free InUseDialin 172.30.228.11 172.30.228.26 16 0Available addresses:172.30.228.12172.30.228.13172.30.228.14172.30.228.15172.30.228.16172.30.228.17172.30.228.18172.30.228.19172.30.228.20172.30.228.21172.30.228.22172.30.228.23172.30.228.24172.30.228.25172.30.228.26172.30.228.11 Async5Inuse addresses:Nonedescribes the fields shown in the display.
Table 6-24 Show IP Local Pool Field Descriptions
Related Commands
shutdown
To disable an interface, use the shutdown interface configuration command. Use the no form of this command to restart a disabled interface.
shutdown
no shutdownSyntax Description
This command has no arguments or keywords.
Default
Enabled
Command Mode
Interface configuration
Usage Guidelines
The shutdown command disables all functions on the specified interface. On serial interfaces, this command causes the DTR signal to be dropped. On Token Ring interfaces, this command causes the interface to be deinserted from the ring.
This command also marks the interface as unavailable. To check whether an interface is disabled, use the EXEC command show interfaces. An interface that has been shut down is shown as administratively down in the display from this command.
Examples
The following example turns off Ethernet interface 0:
interface ethernet 0 shutdownThe following example turns the interface back on:
interface ethernet 0 no shutdownRelated Command
transmitter-delay
To specify a minimum dead-time after transmitting a packet, use the transmitter-delay interface configuration command. Use the no form of this command to restore the default.
transmitter-delay microseconds
no transmitter-delaySyntax Description
microseconds
Approximate number of microseconds of minimum delay after transmitting a packet on the MCI and SCI interface cards
Default
0 microseconds
Command Mode
Interface configuration
Usage Guidelines
This command is especially useful for serial interfaces that can send back-to-back data packets over serial interfaces faster than some hosts can receive them.
The transmitter delay feature is implemented for the following Token Ring cards: CSC-R16M, CSC-1R, and CSC-2R. For the first four cards, the command syntax is the same as the existing command and specifies the number of milliseconds to delay between sending frames that are generated by the access server. Transmitter delay for the CSC-CTR uses the same syntax, but specifies a relative time interval to delay between transmission of all frames.
Example
The following example specifies a delay of 300 microseconds on interface serial interface 0:
interface serial 0 transmitter-delay 300tunnel checksum
To enable encapsulator-to-decapsulator checksumming of packets on a tunnel interface, use the tunnel checksum interface configuration command. Use the no form of this command to disable checksumming.
tunnel checksum
no tunnel checksumSyntax Description
This command has no arguments or keywords.
Default
No tunnel checksumming
Command Mode
Interface configuration
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. Some passenger protocols rely on media checksums to provide data integrity. By default, the tunnel does not guarantee packet integrity. By enabling end-to-end checksums, the access servers will drop corrupted packets.
Example
In the following example, all protocols will have encapsulator-to-decapsulator checksumming of packets on the tunnel interface:
tunnel checksumtunnel destination
To specify a tunnel interface's destination, use the tunnel destination interface configuration command. Use the no form of this command to remove the destination.
tunnel destination {hostname | ip-address}
no tunnel destinationSyntax Description
Default
No tunnel interface destination is specified.
Command Mode
Interface configuration
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface.
Example
In the following example, the tunnel destination is 172.30.111.234:
tunnel destination 172.30.111.234Related Command
tunnel key
To enable an ID key for a tunnel interface, use the tunnel key interface configuration command. Use the no form of this command to remove the ID key.
tunnel key key-number
no tunnel keySyntax Description
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. Tunnel ID keys can be used as a form of weak security to prevent misconfiguration or injection of packets from a foreign source.
Note
Example
In the following example, the tunnel key is set to 3:
tunnel key 3tunnel mode
To set the encapsulation mode for the tunnel interface, use the tunnel mode interface configuration command. To set to the default, use the no form of this command.
tunnel mode {aurp | cayman | eon | gre ip | mbone | nos}
no tunnel modeSyntax Description
Default
GRE tunneling
Command Mode
Interface configuration
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface.
Cayman tunneling implements tunneling as designed by Cayman Systems. This enables our routers and access servers to interoperate with Cayman GatorBoxes. With Cayman tunneling, you can establish tunnels between two routers or between our router and a GatorBox. When using Cayman tunneling, you must not configure the tunnel with an AppleTalk network address. This means that there is no way to ping the other end of the tunnel.
Use DVMRP when a router connects to a mrouted router to run DVMRP over a tunnel. It is required to configure Protocol-Independent Multicast (PIM) and an IP address on a DVMRP tunnel.
Generic route encapsulation (GRE) tunneling can be done between our routers only. When using GRE tunneling for AppleTalk, you configure the tunnel with an AppleTalk network address. This means that you can ping the other end of the tunnel.
Examples
The following example enables Cayman tunneling:
interface tunnel0tunnel source ethernet0tunnel destination 172.30.164.19tunnel mode caymanThe following example enables GRE tunneling:
interface tunnel0appletalk cable-range 4160-4160 4160.19appletalk zone Engineeringtunnel source ethernet0tunnel destination 172.30.164.19tunnel mode gre ipRelated Commands
tunnel destination
tunnel sourcetunnel sequence-datagrams
To configure a tunnel interface to drop datagrams that arrive out of order, use the tunnel sequence-datagrams interface configuration command. Use the no form of this command to disable this function.
tunnel sequence-datagrams
no tunnel sequence-datagramsSyntax Description
This command has no arguments or keywords.
Default
Disabled
Command Mode
Interface configuration
Usage Guidelines
This command currently applies to generic route encapsulation (GRE) only. This command is useful when carrying passenger protocols that behave poorly when they receive packets out of order (for example, LLC2-based protocols).
Example
In the following example, the tunnel is configured to drop datagrams that arrive out of order:
tunnel sequence-datagramstunnel source
To set a tunnel interface's source address, use the tunnel source interface configuring command. Use the no form of this command to remove the source address.
tunnel source {ip-address | interface-type interface-number}
no tunnel sourceSyntax Description
ip-address
IP address to use as the source address for packets in the tunnel.
interface-type
All types.
interface-number
Specifies the port, connector, or interface card number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command.
Default
No tunnel interface's source address is set.
Command Mode
Interface configuration
Usage Guidelines
You cannot have two tunnels using the same encapsulation mode with exactly the same source and destination address. The workaround is to create a loopback interface and source packets off of the loopback interface.
When using tunnels to Cayman boxes, you must set the tunnel source to an explicit IP address on the same subnet as the Cayman box, not the tunnel itself.
Examples
In the following example, the tunnel source is set to the IP address assigned to Ethernet interface 0:
tunnel source ethernet 0The following example enables Cayman tunneling:
interface tunnel0tunnel source ethernet0tunnel destination 172.30.164.19tunnel mode caymanThe following example enables GRE tunneling:
interface tunnel0appletalk cable-range 4160-4160 4160.19appletalk zone Engineeringtunnel source ethernet0tunnel destination 172.30.164.19tunnel mode gre ipRelated Commands
tx-queue-limit
To control the number of transmit buffers available to a specified interface on the MCI and SCI cards, use the tx-queue-limit interface configuration command.
tx-queue-limit number
Syntax Description
Default
Defaults depend on the total transmit buffer pool size and the traffic patterns of all the interfaces on the card. Defaults and specified limits are displayed with the show controllers mci EXEC command.
Command Mode
Interface configuration
Usage Guidelines
Only use this command under the guidance of a technical support representative.
Example
The following example sets the maximum number of transmit buffers on the interface to 5:
interface ethernet 0 tx-queue-limit 5Related Command
