-
Cisco IOS Interface and Hardware Component Command Reference, Release 12.3 T
-
Introduction
-
Interface and Hardware Component Commands: A through C
-
Interface and Hardware Component Commands: D through H
-
Interface and Hardware Component Commands: I through L
-
int_m1gt_1
-
Interface and Hardware Component Commands: M through R
-
Interface and Hardware Component Commands: scramble through show chassis
-
Interface and Hardware Component Commands: show compress through show hub
-
Interface and Hardware Component Commands: show interfaces through show interfaces vg-anylan
-
Interface and Hardware Component Commands: show ipc through syscon source-interface
-
Interface and Hardware Component Commands: T through Y
-
Table Of Contents
dsl-mode shdsl symmetric annex
end (satellite initial configuration)
exit (satellite initial configuration)
half-duplex controlled-carrier
hw-module main-cpu qa error-recovery
data-protection
To enable data protection for a circuit emulation (CEM) channel, use the data-protection command in CEM configuration mode. To disable data protection, use the no form of this command.
data-protection
no data-protection
Syntax Description
This command has no arguments or keywords.
Defaults
Data protection is disabled.
Command Modes
CEM configuration
Command History
Examples
The following example demonstrates how to enable data protection.
Router(config-cem)# data-protectionRelated Commands
cem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
data-strobe
To specify an input control lead to be monitored as an indicator of valid data, use the data-strobe command in CEM configuration mode. To disable the monitoring of an input control lead, use the no form of this command.
data-strobe input-lead {on | off}
no data-strobe
Syntax Description
Defaults
No input control lead is monitored.
Command Modes
CEM configuration
Command History
Usage Guidelines
Any input control signal on a serial data port may be configured as a "data strobe" to indicate to the NM-CEM-4SER network module whether ingress data on the port should be encapsulated for transmission or ignored. If the data strobe command is specified with the on keyword, data packets are created and sent when the input lead is asserted. If the data strobe is off (either intentionally, or as a result of the failure of the customer premises equipment [CPE]), no data packets are created, and this results in preservation of bandwidth in the IP network.
This command applies only to serial ports.
Examples
The following example demonstrates how to specify that packets are to be created and sent to the far end only when the DTR input control lead is asserted.
Router(config-cem)# data-strobe dtr on
Related Commands
dce-terminal-timing enable
To prevent phase shifting of the data with respect to the clock when running the line at high speeds and long distances, use the dce-terminal-timing enable command in interface configuration mode. If serial clock transmit external (SCTE) terminal timing is not available from the DTE, use the no form of this command; the DCE will use its own clock instead of SCTE from the DTE.
dce-terminal-timing enable
no dce-terminal-timing enable
Syntax Description
This command has no arguments or keywords.
Defaults
The DCE uses its own clock.
Command Modes
Interface configuration
Command History
Usage Guidelines
On the Cisco 4000 router, you can specify the serial Network Interface Module timing signal configuration. When the board is operating as a DCE and the DTE provides terminal timing (SCTE or TT), the dce-terminal-timing enable command causes the DCE to use SCTE from the DTE.
Examples
The following example shows how to prevent phase shifting of the data with respect to the clock:
Router(config)# interface serial 0Router(config-if)# dce-terminal-timing enabledefault (CEM)
To reset channel options to their default values, use the default command in CEM configuration mode.
default {data-protection | dejitter-buffer | idle-pattern | ip dscp | ip tos | ip precedence | payload-compression | payload-size | signaling}
Syntax Description
Defaults
The CEM channel options are set at their configured values.
Command Modes
CEM configuration
Command History
Examples
The following example demonstrates how to reset CEM channel data protection to its default value.
Router(config-cem)# default data-protectionRelated Commands
dejitter-buffer
To configure the size of the dejitter buffer, use the dejitter-buffer command in CEM configuration mode. To restore the dejitter buffer to its default size, use the no form of this command.
dejitter-buffer size
no dejitter-buffer
Syntax Description
Defaults
The dejitter buffer defaults to 60 milliseconds.
Command Modes
CEM configuration
Command History
Examples
The following example shows how to set the dejitter buffer to 200 milliseconds.
Router(config-cem)# dejitter-buffer 200
Related Commands
cem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
delay (interface)
To set a delay value for an interface, use the delay command in interface configuration mode. To restore the default delay value, use the no form of this command.
delay tens-of-microseconds
no delay
Syntax Description
tens-of-microseconds
Integer that specifies the delay in tens of microseconds for an interface or network segment. To see the default delay, use the show interfaces command.
Defaults
Default delay values may be displayed with the show interfaces EXEC command.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set a delay of 30,000 microseconds on serial interface 3:
Router(config)# interface serial 3Router(config-if)# delay 3000Related Commands
show interfaces
Displays the statistical information specific to a serial interface.
description (controller)
To add a description to an E1 or T1 controller or the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the description command in controller configuration mode. To remove the description, use the no form of this command.
description string
no description
Syntax Description
string
Comment or description (up to 80 characters) to help you remember what is attached to an interface.
Defaults
No description is added.
Command Modes
Controller configuration
Command History
10.3
This command was introduced.
11.3
This command was modified to include the CT3IP controller.
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember what certain controllers are used for. The description affects the CT3IP and Multichannel Interface Processor (MIP) interfaces only and appears in the output of the show controller e1, show controller t1, show controller t3, and show running-config EXEC commands.
Examples
The following example shows how to add a description for a 3174 controller:
Router(config)# controller t1Router(config-controller)# description 3174 Controller for test labRelated Commands
dot1q tunneling ethertype
To define the Ethertype field type used by peer devices when implementing Q-in-Q VLAN tagging, use the dot1q tunneling ethertype command in interface configuration mode. To remove the VLAN tag Ethertype, use the no form of this command.
dot1q tunneling ethertype ethertype
no dot1q tunneling ethertype ethertype
Syntax Description
Defaults
The Ethertype field used by peer devices when implementing Q-in-Q VLAN tagging is 0x8100.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the dot1q tunneling ethertype command if the peer switching devices are using an Ethertype field value of 0x9100. All Cisco switching devices use the default Ethertype field value of 0x8100.
This command is used with the IEEE 802.1Q-in-Q VLAN Tag Termination feature in which double VLAN tagging is configured using the encapsulation dot1q command. 802.1q double tagging allows a service provider to use a single VLAN to support customers who have multiple VLANs.
Examples
The following example shows how to configure an Ethertype field as 0x9100:
Router(config)# interface gigabitethernet 1/0/0Router(config-if)# dot1q tunneling ethertype 0x9100Related Commands
down-when-looped
To configure an interface to inform the system that it is down when loopback is detected, use the down-when-looped command in interface configuration mode.
down-when-looped
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid for High-Level Data Link Control (HDLC) or PPP encapsulation on serial and High-Speed Serial Interface (HSSI) interfaces.
This command does not have a no form.
Backup 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 enabled only 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.
Testing an Interface with the Loopback Command
If testing an interface with the loopback command, or by placing the DCE into loopback, the down-when-looped command should not be configured; otherwise, packets will not be transmitted out the interface that is being tested.
Examples
The following example shows how to configure interface serial 0 for HDLC encapsulation. The interface is then configured to let the system know that it is down when in loopback mode.
Router(config)# interface serial0Router(config-if)# encapsulation hdlcRouter(config-if)# down-when-loopedRelated Commands
backup interface
Configures an interface as a secondary or dial backup interface.
loopback (E3 controller)
Diagnoses equipment malfunctions between an interface and a device.
ds0-group (J1 controller)
To configure channelized J1 time slots, use the ds0-group command in controller configuration mode. To remove the DS0 group, use the no form of this command.
ds0-group ds0-group-no timeslots timeslot-list type external-signaling
no ds0-group ds0-group-no timeslots timeslot-list type external-signaling
Syntax Description
Defaults
No DS0 group is defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
The ds0-group command replaces the existing cas-group command. Making the command generic allows flexibility and scalability. It is not restricted to channel associated signaling (CAS) or channel bundling.
The ds0-group command automatically creates a logical voice port that is numbered as follows on Cisco 2600 and Cisco 3600 series routers: slot/port:ds0-group-no. Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following example is sample output from the show controllers j1 command on the Cisco 3660 series after channelized J1 time slots have been configured:
Router(config-controller)# ds0-group 1 timeslots 1-15,17-31 type e&m-wink-startRouter(config-controller)# endRouter# show controllers j1*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(1), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(2), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(3), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(4), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(5), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(6), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(7), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(8), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(9), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(10), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(11), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(12), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(13), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(14), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(15), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(17), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(18), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(19), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(20), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(21), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(22), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(23), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(24), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(25), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(26), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(27), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(28), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(29), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(30), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(31), pRelated Commands
dsl-mode shdsl symmetric annex
To specify the operating mode of the digital subscriber line (DSL) controller, use the dsl-mode shdsl symmetric annex command in controller configuration mode. To return the DSL to the default Annex A, use the no form of this command.
dsl-mode shdsl symmetric annex mode
Syntax Description
Defaults
The annex defaults to A for North America.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is used to configure the DSL controller interface to operate in a specified DSL mode and to set regional operating parameters. The shdsl keyword is used to set the mode to SHDSL and configures multirate, high-speed DSL per ITU G.991.2. The symmetric keyword configures the controller to symmetric mode. The annex keyword configures the controller to use regional operating parameters. The regional operating parameters default to North America.
Examples
The following example displays the use of the controller dsl 0/0 command to configure the controller in the router configured on the central office (CO) side. Use the dsl-mode shdsl symmetric annex b command to configure the controller for multirate, high-speed DSL with symmetric mode for European operating parameters.
Router# configure terminalRouter(config)# controller dsl 0/0Router(config-controller)# line-term coRouter(config-controller)# dsl-mode shdsl symmetric annex bRouter(config-controller)# mode atmRouter(config-controller)#00:22:07: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to downRouter(config-controller)# line-mode 4-wire00:23:25: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to up00:23:31: %LINK-3-UPDOWN: Interface ATM0/0, changed state to up00:23:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, changed state to upRelated Commands
dsu bandwidth
To specify the maximum allowable bandwidth used by a T3 or E3 controller or the PA-T3 and PA-E3 port adapters, use the dsu bandwidth command in interface configuration mode. To return to the default bandwidth, use the no form of this command.
dsu bandwidth kbps
no dsu bandwidth
Syntax Description
kbps
Maximum bandwidth, in kbps. Range is from 22 to 44736. Default values are as follows:
•
34010 for E3 or PA-E3
•
•
Defaults
34010 kbps for E3 or PA-E3
44210 kbps for T3
44736 kbps for PA-T3Command Modes
Interface configuration
Command History
Usage Guidelines
The local interface configuration must match the remote interface configuration. For example, if you reduce the maximum bandwidth to 16000 on the local port, you must also do the same on the remote port.
The dsu bandwidth command reduces the bandwidth by padding the E3 and T3 frame.
To verify the data service unit (DSU) bandwidth configured on the interface, use the show interfaces serial EXEC command.
When G.751 framing is used, DSU bandwidth can be used to select a payload subrate from 34010 kbps down to 22 kbps. Before framing bypass can be used, a DSU bandwidth of 34010 kbps must be configured.
Even though software allows the user to configure a continuous range of bandwidths in subrate modes, vendors support bandwidths only in quantums (for example, in an E3 digital link, bandwidth must be in multiples of 358 kbps). Therefore, the software sets the user-configured bandwidth to the closest vendor-supported bandwidth. Use the show interfaces serial slot/port command to display the actual bandwidth that is configured.
The user-configured subrate mode, subrate bandwidth, actual subrate bandwidth configured, and scramble configuration are displayed near the end of the show interfaces serial command output.
The following table shows DSU modes and vendor-supported bandwidths.
Examples
The following example sets the maximum allowable DSU bandwidth to 16,000 kbps on interface 1/0/0:
Router(config)# interface serial 1/0/0Router(config-if)# dsu bandwidth 16000The following example shows the user-configured subrate bandwidth and the actual configured subrate bandwidth as displayed in the output of the show interfaces serial command:
Router# show interfaces serialSerial1/0 is up, line protocol is upHardware is DSXPNM SerialMTU 1500 bytes, BW 44210 Kbit, DLY 20000 usec,reliability 253/255, txload 1/255, rxload 1/255Encapsulation HDLC, crc 16, loopback not setKeepalive not setDTR is pulsed for 0 seconds on reset, Restart-Delay is 1637167 secsLast input 04:59:04, output 04:59:04, output hang neverLast clearing of "show interface" counters 00:00:02Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 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 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDSU mode 0, bandwidth 34010, real bandwidth 34010, scramble 0Related Commands
show interfaces serial
Displays information that is specific to the interface hardware.
dsu mode
To specify the interoperability mode used by a T3 or E3 controller or the PA-T3 and PA-E3 port adapters, use the dsu mode command in interface configuration mode. To return to the default mode, use the no form of this command.
dsu mode {0 | 1 | 2 | 3 | 4}
no dsu mode
Syntax Description
Defaults
0
Command Modes
Interface configuration
Command History
Usage Guidelines
Scrambling Support on T3 and E3 Serial Interfaces in DSU Mode 1
DSU mode 1 refers to Kentrox mode. If DSU mode is used on a T3 serial interface and the bandwidth is = > 35,000 bps, the scrambling option is not supported. Likewise, if DSU mode 1 is used for an E3 serial interface and the bandwidth is = > 24,510 bps, scrambling is not supported.
Match Local and Remote DSU Configurations
The local interface configuration must match the remote interface configuration. For example, if you define the data service unit (DSU) interoperability mode as 1 on the local port, you must also do the same on the remote port.
Know the DSU Type
You must know what type of DSU is connected to the remote port to determine if it interoperates with an E3 or T3 controller or a PA-E3 or PA-T3 port adapter. The dsu mode command enables and improves interoperability with other DSUs.
Verify DSU Mode
To verify the DSU mode configured on the interface, use the show controllers serial or show interfaces serial EXEC commands.
Examples
The following example sets the DSU mode to 1 on interface 1/0/0:
Router(config)# interface serial 1/0/0Router(config-if)# dsu mode 1The following example shows the configuration for a serial interface configured in DSU mode 1. The bandwidth is set higher than that supported by the Kentrox firmware allows for scrambling. therefore, the scrambling option is not supported in this configuration.
Router(config)# interface serial 1/0/0Router(config-if)# mtu 4474Router(config-if)# ip address 216.186.93.114 255.255.255.252Router(config-if)# ip mtu 4470Router(config-if)# dsu mode 1Router(config-if)# dsu bandwidth 44210Related Commands
show controllers serial
Displays information that is specific to the serial controllers.
show interfaces serial
Displays information that is specific to the interface hardware.
dte-invert-txc
To invert the transmit external clock (TXC) signal received from the DCE when the device is operating as a DTE, use the dte-invert-txc command in interface configuration mode. If the DCE accepts serial clock transmit external (SCTE) signal when the device is operating as a DTE, use the no form of this command.
dte-invert-txc
no dte-invert-txc
Syntax Description
This command has no arguments or keywords.
Defaults
The TXC signal is not inverted.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if the DCE cannot receive SCTE from the DTE, the data is running at high speeds, and the transmission line is long. The dte-invert-txc command prevents phase shifting of the data with respect to the clock.
On the Cisco 4000 series, you can specify the serial Network Processor Module timing signal configuration. When the board is operating as a DTE, the dte-invert-txc command inverts the TXC clock signal it gets from the DCE that the DTE uses to transmit data.
If the DCE accepts SCTE from the DTE, use no dte-invert-txc.
Examples
The following example inverts the TXC on serial interface 0:
Router(config)# interface serial 0Router(config-if)# dte-invert-txcduplex
To configure duplex operation on an interface, use the duplex command in interface configuration mode. To return the system to half-duplex mode, the system default, use the no form of this command.
duplex {full | half | auto}
no duplex
Syntax Description
Defaults
Half-duplex mode
Command Modes
Interface configuration
Command History
Usage Guidelines
To use the autonegotiation capability (that is, detect speed and duplex modes automatically), you must set both speed and duplex to auto.
Table 7 describes the access server's performance for different combinations of the duplex and speed modes. The specified duplex command configured with the specified speed command produces the resulting system action.
For the Cisco AS5300, the duplex {full | half | auto} command syntax replaces the following two earlier duplex commands:
•
•
You will get the following error messages if you try to use these commands on a Cisco AS5300:
Router(config)# interface fastethernet 0Router(config-if)# full-duplexPlease use duplex command to configure duplex modeRouter(config-if)#Router(config-if)# half-duplexPlease use duplex command to configure duplex modeExamples
The following example shows how to configure full- duplex operation on a Cisco AS5300:
Router(config)# interface fastethernet 0Router(config-if)# duplex fullRelated Commands
e2-clockrate
To configure serial interface 0 for E2 (8 MHz full duplex) and to shut down the other three serial interfaces (1 to 3), use the e2-clockrate command in interface configuration mode. To disable the full duplex E2, use the no form of this command.
e2-clockrate
no e2-clockrate
Syntax Description
This command has no arguments or keywords.
Defaults
All interfaces are running.
Command Modes
Interface configuration
Command History
12.0(2)XD
This command was introduced.
12.0(3)T
This command was integrated into Cisco IOS Release 12.0(3)T.
Usage Guidelines
The e2-clockrate command is an interface configuration command and is seen only with interface serial0. When this command is used, serial interface 0 supports speeds up to E2 (8 MHz full duplex) and the other three serial interfaces (1 to 3) are put in the "shutdown" state. Also, running this command displays the following warning message:
Serial interface 0 is configured to support E2 rates and serial ports "1-3" are moved to shutdown state.Examples
The following example shows sample display output for the e2-clockrate EXEC command.
Router(config-if)# e2-clockrateInterface Serial 0 is configured to support clockrates up to E2 (8Mbps)Interfaces serial 1-3 will not be operationalRelated Commands
clock rate
Configures the clock rate for the hardware connections on serial interfaces such as NIMs and interface processors to an acceptable bit rate.
early-token-release
To enable early token release on Token Ring interfaces, use the early-token-release command in interface configuration mode. To disable this function, use the no form of this command.
early-token-release
no early-token-release
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
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. This feature helps increase the total bandwidth of the Token Ring.
The Token Ring Interface Processor (TRIP) on the Cisco 7500 series routers and the Token Ring adapters on the Cisco 7200 series routers all support early token release.
Examples
The following example enables the use of early token release on Token Ring interface 1:
Router(config)# interface tokenring 1Router(config-if)# early-token-releaseThe following example enables the use of early token release on the Token Ring interface processor in slot 4 on port 1 on the Cisco 7500 series routers:
Router(config)# interface tokenring 4/1Router(config-if)# early-token-releaseencapsulation
To set the encapsulation method used by the interface, use the encapsulation command in interface configuration mode. To remove the encapsulation, use the no form of this command.
encapsulation encapsulation-type
no encapsulation encapsulation-type
Syntax Description
Defaults
The default depends on the type of interface. For example, synchronous serial interfaces default to HDLC and asynchronous interfaces default to SLIP.
Command Modes
Interface configuration