-
Cisco IOS Interface and Hardware Component Command Reference
-
Introduction
-
A through B
-
cable bundle through clock mode
-
clock rate through cut-through
-
D through E
-
F through H
-
I through K
-
l2 vfi manual through loopback (PA-MC-8TE1 + port adapter)
-
loopback (T1 interface) through nrzi-encoding
-
O through R
-
scramble through service-module t1 lbo
-
service-module t1 linecode through show controllers satellite
-
show controllers serial through show hw-module slot proc cpu
-
show hw-module slot tech-support through show interfaces vg-anylan
-
show interfaces vlan mapping through show scp
-
show service-module serial through standby port
-
squelch through system jumbomtu
-
t1 through tug-2 e1 unframed
-
tunnel bandwidth through yellow
-
Table Of Contents
clear catalyst6000 traffic-meter
clear interface gigabitethernet
clear top counters interface report
cable bundle
To configure a cable interface to belong to an interface bundle, use the cable bundle command in interface configuration mode. To delete a cable interface bundle definition, use the no form of this command.
cable bundle number [master]
no cable bundle number [master]
Syntax Description
number
Specifies the bundle identifier. Valid range is from 1 to 255.
master
(Optional) Defines the specified interface as the master.
Defaults
No cable interface bundle is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure up to four interface bundles. In each bundle, specify one interface as the master interface by using the optional master keyword.
Configure only an IP address on the master interface. If an IP address is configured and the interface is not specified as the master interface, any attempt to add an interface to a bundle is rejected.
Specify all generic IP networking information (such as IP address, routing protocols, and switching modes) on the bundle master interface. Do not specify generic IP networking information on bundle slave interfaces.
If you attempt to add an interface to a bundle as nonmaster interface and an IP address is assigned to this interface, the command will fail. You must remove the IP address configuration before you can add the interface to a bundle.
If you have configured an IP address on a bundled interface and the interface is not the master interface, a warning message appears.
Specify generic (not downstream or upstream related) cable interface configurations, such as source-verify or Address Resolution Protocol (ARP) handling, on the master interface. Do not specify generic configuration on nonmaster interfaces.
If you configure an interface as a part of a bundle and it is not the master interface, all generic cable configuration for this interface is removed. The master interface configuration will then apply to all interfaces in the bundle.
If you shut down or remove the master interface in a bundle, no data packets are sent to any of the interfaces in this bundle. Packets are still physically received from nonmaster interfaces that have not been shut down, but those packets will be discarded. Modems connected to those interfaces will not be disconnected immediately, but modems going online will not be able to obtain an IP address, download their configuration file, or renew their IP address assignment if the Dynamic Host Configuration Protocol (DHCP) lease expires.
If you shut down a slave interface, only this shut down interface is affected.
Examples
The following example shows how to configure interface 25 to be the master interface:
Router(config-if)# cable bundle 25 masterRouter(config-if)#07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down07:28:18: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to upThe following example shows the error message that appears if you try to configure an interface with an IP address that is not the master interface:
Router(config-if)# cable bundle 5Please remove ip address config first then reenter this commandRelated Commands
show cable bundle
Displays the forwarding table for the specified interface bundle.
cable helper-address
To specify a destination address for User Datagram Protocol (UDP) broadcast Dynamic Host Configuration Protocol (DHCP) packets, use the cable helper-address command in interface configuration mode. To remove the specified destination address for UDP DHCP packets, use the no form of this command.
cable helper-address ip-address {cable-modem | host}
no cable helper-address ip-address {cable-modem | host}
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you specify a secondary interface address, the giaddr field in the DHCP requests will be sent to the primary address for DHCP requests received from cable modems, and to the secondary IP address for DHCP requests received from hosts.
Examples
The following example shows how to forward UDP broadcasts from cable modems to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 cable-modemThe following example shows how to forward UDP broadcasts from hosts to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 hostcablelength
To specify the distance of the cable from the routers to the network equipment, use the cablelength command in controller configuration mode. To restore the default cable length, use the no form of this command.
cablelength feet
no cablelength
Syntax Description
Defaults
Channelized T3 Interface Processor
224 feet for a CT3IP interface processor and Clear Channel T3/E3 network module
PA-T3 and PA-2T3 Port Adapters
49 feet for PA-T3 and PA-2T3 port adapters
Cisco 10000 Series Router
450 feet for an interface cable between the near and far-end CSU/DSU device
Command Modes
Controller configuration
Command History
Usage Guidelines
CT3IP Interface Processor and Clear Channel T3/E3 Network Module
The default cable length of 224 feet is used by the CT3IP interface processor and the Clear Channel T3/E3 network module.
PA-T3 and PA-2T3 Port Adapters
The default cable length of 49 feet is used by the PA-T3 and PA-2T3 port adapters.
Note
Although you can specify a cable length from 0 to 450 feet, the hardware recognizes only two
ranges: 0 to 49 and 50 to 450. For example, entering 35 feet uses the 0 to 49 range. If you later
change the cable length to 40 feet, there is no change because 40 is still within the 0 to 49 range. However, if you change the cable length to 50, the 50 to 450 range is used. The actual number you enter is stored in the configuration file.Cisco 1000 Series Router
Table 2 lists the cable length distances and their relationships to line buildout for E3 and T3 controllers on Cisco 1000 Series Routers:
Note
Examples
Cable Length to 300 Feet Example
The following example shows how to set the cable length for the router to 300 feet:
Router(config)# controller t3 9/0/0Router(config-controller)# cablelength 300Cisco 10000 Series Router Example
The following example sets the cable length to 120 feet:
Router(config)# controller dsx3 4/0/6Router(config-controller)# cablelength 120Related Commands
cablelength (E1 controller)
To fine-tune the pulse of a signal at the receiver for an E1 cable on a Cisco AS5300 or Cisco AS5400, use the cablelength command in controller configuration mode. To restore the default receiver sensitivity, use the no form of this command.
cablelength {custom gain-value [squelch-on] | long [squelch-on] | medium [squelch-on] | short [squelch-on]}
no cablelength
Syntax Description
Command Default
Default receiver sensitivity for E1 cables is applied.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is supported on E1 controllers only.
Note
Examples
The following example shows how to fine-tune the receiver sensitivity for an E1 cable on a Cisco AS5300 to support a long-haul configuration:
Router(config-controller)# cablelength long squelch-oncablelength long
To increase the pulse of a signal at the receiver and to decrease the pulse from the transmitter using pulse equalization and line build-out for a T1 cable, use the cablelength long command in controller configuration or interface configuration mode. To return the pulse equalization and line build-out values to their default settings, use the no form of this command.
cablelength long db-gain-value db-loss-value
no cablelength long
Syntax Description
Defaults
db-gain-value: gain26
db-loss-value: 0dbCommand Modes
Controller configuration for the Cisco AS5800 and Cisco MC3810.
Interface configuration for the Cisco 2600 and Cisco 3600 series routers.Command History
Usage Guidelines
Cisco AS5800 and Cisco MC3810
Use this command for configuring the controller T1 interface on the Cisco AS5200 access server, on the Cisco AS5800 universal access server, or on the Cisco MC3810 multiservice access concentrator. The cablelength long command is used to configure DS1 links (meaning, to build CSU/DSU links) when the cable length is no longer than 655 feet.
On the Cisco MC3810, this command is supported on T1 controllers only and applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC.
Note
The cablelength long command can be used only on CSU interfaces.A pulse equalizer regenerates a signal that has been attenuated and filtered by a cable loss. Pulse equalization does not produce a simple gain, but it filters the signal to compensate for complex cable loss. A gain26 receiver gain compensates for a long cable length equivalent to 26 dB of loss, whereas a gain36 compensates for 36 dB of loss.
The lengthening or building out of a line is used to control far-end crosstalk. Line build-out attenuates the stronger signal from the customer installation transmitter so that the transmitting and receiving signals have similar amplitudes. A signal difference of less than 7.5 dB is ideal. Line build-out does not produce simple flat loss (also known as resistive flat loss). Instead, it simulates a cable loss of 7.5 dB, 15 dB, or 22.5 dB so that the resulting signal is handled properly by the receiving equalizer at the other end.
Cisco 2600 and Cisco 3600 Series Routers
This command is supported on T1 long-haul links only. If you enter the cablelength long command on a DSX-1 (short-haul) interface, the command is rejected.
The transmit attenuation value is best obtained by experimentation. If the signal received by the far-end equipment is too strong, reduce the transmit level by entering additional attenuation.
Examples
Cisco AS5800 and Cisco MC3810
The following example shows how to increase the receiver gain by 36 decibels and decreases the transmitting pulse by 15 decibels for a long cable on a Cisco AS5800:
AS5800(config)# controller t1 0AS5800(config-controller)# cablelength long gain36 -15dbThe following example shows how to configure the cable length for controller T1 0 on a Cisco MC3810 to a decibel pulse gain of 36 decibels and a decibel pulse rate of -22.5 decibels:
MC3810(config)# controller t1 0MC3810(config-controller)# cablelength long gain36 -22.5dbCisco 2600 and Cisco 3600 Series Routers
On a Cisco 2600 or Cisco 3600 series router, the following example shows how to specify a pulse gain of 36 decibels and a decibel pulse rate of -7.5 decibels:
Router(config)# interface atm 0/2Router(config-if)# cablelength long gain36 -7.5dbRelated Commands
cablelength short
To set a cable length of 655 feet or shorter for a DS1 link on the Cisco MC3810 or Cisco 2600 and Cisco 3600 series routers, use the cablelength short command in controller configuration or interface configuration mode. To delete the cablelength short value, use the no form of this command.
cablelength short length
no cablelength short
Syntax Description
Defaults
The default is 133 feet for the Cisco AS5200 access server, Cisco AS5800 universal access server, and Cisco MC3810 multiservice access concentrator.
There is no default cable length for the Cisco 2600 and Cisco 3600 series routers.
Command Modes
Controller configuration for the Cisco AS5200 access server, Cisco AS5800 universal access server, and Cisco MC3810 multiservice access concentrator.
Interface configuration for the Cisco 2600 and Cisco 3600 series routers.Command History
Usage Guidelines
Cisco AS5200 Access Server, Cisco AS5800 Universal Access Server, and Cisco MC3810 Multiservice Access Concentrator
On the Cisco MC3810, the cablelength short command is used to configure DSX-1 links when the cable length is 655 feet or less than 655 feet. On the Cisco MC3810, this command is supported on T1 controllers only.
Note
Cisco 2600 and Cisco 3600 Series Routers
This command is supported on T1 short-haul links only. If you enter the cablelength short command on a long-haul interface, the command is rejected.
To set cable lengths longer than 655 feet, use the cablelength long command.
This command is supported on T1 controllers only.
Cisco AS5200 Access Server, Cisco AS5800 Universal Access Server, and Cisco MC3810 Multiservice Access Concentrator
The following example shows how to set the cable length to 266 for the T1 controller in slot 1 on dial shelf 0:
Router# configure terminalRouter(config)# controller t1 1/1/0Router(config-controller)# cablelength short 266Router(config-controller)# endCisco 2600 and Cisco 3600 Series Routers
On a Cisco 2600 or Cisco 3600 series router, the following example shows how to specify a cable length from 0 to 133 feet:
Router(config)# interface atm 0/2Router(config-if)# cablelength short 133Related Commands
Increases the pulse of a signal at the receiver and decreases the pulse from the sender using pulse equalization and line build-out.
card
To preprovision a line card slot in the Cisco 10000 series router, use the card command in global configuration mode. To remove preprovisioning from a line card slot, use the no form of this command.
card slot/subslot {lchoc12-1 | lgigethernet-l | 1gigethernet-hh-1 | loc12atm-1 | loc12pos-1 | 1oc48dpt-pos-1 | 24che1t1-1 | 4chstm-1 | 4cht3-hh-1| 4oc3atm-1 | 4oc3atm_lr-1 | 6cht3-1 | 6oc3pos-1 | 8e3ds3-1 | 8e3ds3atm-1 | 8fastethernet-1 [ mode {e1 | t1}]}
no card slot/subslot
Syntax Description
Command Default
The default mode of operation for the 24-Port Channelized E1/T1 line card is E1.
Command Modes
Global configuration
Command History
Usage Guidelines
You must specify a line card slot and subslot, and the line card for which you want to preprovision the line card slot.
If you insert a line card into a line card slot that has been preprovisioned for a different line card, the line card reports a boot failure in an error message to the console. Output from the show ip interface brief command indicates that the line card remains in an initialized state.
You can specify a mode of operation for the 24-Port Channelized E1/T1 line card. If you do not, the line card operates in the E1 mode.
In Cisco IOS releases earlier than 12.0(28)S, 12.2(16)BX, and 12.3(7)XI1, you used only the card command to change the provisioning of a line card slot. It was not necessary to remove the old line card before using the card command to change the line card provisioning.
In Cisco IOS releases after 12.0(28)S, 12.2(16)BX, and 12.3(7)XI1, you must deactivate the installed line card using the hw-module and no card commands before using the card command to provision the line card slot for a different line card.
Examples
The following example preprovisions line card slot 2 to accept a 24-Port Channelized E1/T1 line card operating in E1 mode:
Router(config)# card 2/0 24che1t1-1 mode e1The following example shows how to change the provisioning for line card slot 5 from the 1-Port Gigabit Ethernet Half-Height line card to the 4-Port OC-3/STM-1 ATM line card.
Router(config)# hw-module subslot 5/0 shutAug 22 21:52:19.619 UTC: %IPCOIR-3-TIMEOUT: Timeout waiting for a response from slot 5/0.Aug 22 21:52:19.619 UTC: %IPCOIR-2-CARD_UP_DOWN: Card in slot 5/0 is down. Notifying 1gigethernet-hh-1 driver.Aug 22 21:52:21.627 UTC: %LINK-3-UPDOWN: Interface GigabitEthernet5/0/0, changed state to downAug 22 21:52:22.627 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet5/0/0, changed state to downRouter(config)# no card 5/0 1gigethernet-hh-1Aug 22 21:53:20.008 UTC: %C10K-3-DEACTIVATED: card in slot [5/0] disabled.Router(config)# card 5/0 4oc3atm-1[ Remove the 1-Port Gigabit Ethernet Half-Height line card andinsert the 4-Port OC-3/STM-1 ATM line card ]card type (T1-E1)
To configure a T1 or E1 card type, use the card type command in global configuration mode. To deselect the card type on non-SPA platforms, use the no form of this command. The no form of this command is not available on the SPA platforms.
card type {t1 | e1} slot [bay]
no card type {t1 | e1} slot [bay]
Channelized T/E1 Shared Port Adapters
card type {t1 | e1} slot subslot
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Changes made using this command on non-SPA platforms, do not take effect unless the reload command is used or the router is rebooted.
Channelized T1/E1 Shared Port Adapters
There is no card type when the SPA is inserted for first time. The user must configure this command before they can configure individual ports.
The no form of this command is not available on the SPA platforms. To change an existing card type on SPA platforms, perform the following steps:
1.
2.
3.
4.
5.
Examples
The following example configures T1 data transmission on slot 1 of the router:
Router(config)# card type t1 1The following example configures all ports of an 8-Port Channelized T1/E1 SPA, seated in slot 5, subslot 2, in T1 mode:
Router(config)# card type t1 5 2Related Commands
card type (T3-E3)
To configure a T3 or E3 card type, use the card type command in global configuration mode. To deselect the card type, use the no form of this comand. The no form of this command is not supported on the 2-Port and 4-Port Clear Channel T3/E3 SPA on Cisco 12000 series routers.
T3 or E3 Controllers
card type {t3 | e3} slot
no card type {t3 | e3} slot
Clear Channel T3/E3 Shared Port Adapters
card type {t3 | e3} slot subslot
no card type {t3 | e3} slot subslot
Clear Channel T3/E3 Shared Port Adapters on Cisco 12000 Series Routers
card type {t3 | e3} slot subslot
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Usage Guidelines
Usage guidelines vary slightly from platform to platform as follows:
T3 or E3 Controllers
Once a card type is issued, you enter the no card type command and then another card type command to configure a new card type. You must save the configuration to the NVRAM and reboot the router in order for the new configuration to take effect.
When the router comes up, the software comes up with the new card type. Note that the software will reject the configuration associated with the old controller and old interface. You must configure the new controller and serial interface and save it.
Clear Channel T3/E3 Shared Port Adapters
To change all the SPA ports from T3 to E3, or vice versa, you enter the no card type command and then another card type command to configure a new card type.
When the router comes up, the software comes up with the new card type. Note that the software will reject the configuration associated with the old controller and old interface. You must configure the new controller and serial interface and save it.
Clear Channel T3/E3 Shared Port Adapters on Cisco 12000 Series Routers
The no form of this command is not available on the 2-Port and 4-Port Clear Channel T3/E3 SPA on Cisco 12000 series routers. To change an existing card type on Cisco 12000 series routers, perform the following steps:
1.
2.
3.
4.
5.
Examples
The following example shows T3 data transmission configured in slot 1:
Router(config)# card type t3 1The following example configures all ports of 2-Port and 4-Port Clear Channel T3/E3 SPA, seated in slot 5, subslot 2, in T3 mode:
Router(config)# card type t3 5 2Related Commands
carrier-delay
To set the carrier delay on a main physical interface, use the carrier-delay command in interface configuration mode. To return to the default carrier delay value, use the no form of this command.
Conventional Carrier Delay
carrier-delay {seconds | msec milliseconds}
no carrier-delay
Asymmetric Carrier Delay for SIP-200- and SIP-400-Based WAN Cards
carrier-delay [up | down] {seconds | msec milliseconds}
no carrier-delay
Syntax Description
Command Default
Conventional Carrier Delay
The default carrier delay is 2 seconds or 50 milliseconds.
Asymmetric Carrier Delay
In SIP-200- and SIP-400-based WAN cards, an asymmetric carrier delay of 4 seconds is applied to the up state transitions.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Catalyst 6000 Series Switches
The default carrier transition delay is 10 milliseconds on all Ethernet interfaces. This enables the carrier-delay time to ensure fast link detection.
Conventional Carrier Delay
If a link goes down and comes back up before the carrier delay timer expires, the down state is effectively filtered, and the rest of the software on the router is not aware that a link-down event occurred. Therefore, a large carrier delay timer results in fewer link-up/link-down events being detected. On the other hand, setting the carrier delay time to 0 means that every link-up/link-down event is detected.
In most environments a lower carrier delay is better than a higher one. The exact value that you choose depends on the nature of the link outages that you expect to see in your network and how long you expect those outages to last.
If data links in your network are subject to short outages, especially if those outages last less than the time it takes for your IP routing to converge, you should set a relatively long carrier delay value to prevent these short outages from causing unnecessary churn in your routing tables. If outages in your network tend to be longer, you might want to set a shorter carrier delay so that the outages are detected sooner and the IP route convergence begins and ends sooner.
The following restrictions apply to carrier delay configuration:
•
•
Asymmetric Carrier Delay
Cisco IOS releases that support the up and down keywords allow asymmetric carrier delay (ACD) configuration. ACD allows you to configure separate delay times for link-up and link-down event notification on physical interfaces that support ACD, such as the SIP-200- and SIP-400-based interfaces. With ACD, link-down events can be notified quickly while link-up events can be notified after a delay of sufficient time to ensure that a rebooted port is ready to forward packets.
The following restrictions apply to ACD configuration:
•
•
Link-up carrier delay time must be 4 seconds or more.
Examples
Conventional Carrier Delay
The following example shows how to change the carrier delay to 5 seconds:
Router(config)# interface serial2/3/0Router(config-if)# carrier-delay 5Asymmetric Carrier Delay
The following example shows how to configure a carrier delay of 8 seconds for link-up transitions and 50 milliseconds for link-down transitions:
Router(config)# interface GigabitEthernet2/0/0Router(config-if)# carrier-delay up 8Router(config-if)# carrier-delay down msec 50cem
To enter circuit emulation (CEM) configuration mode, use the cem command in global configuration mode.
cem slot/port/channel
Syntax Description
Command Default
CEM configuration mode is not available.
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enter CEM configuration mode to allow the configuration of all CEM options.
Examples
The following example shows how to enter CEM configuration mode:
Router(config)# cem 1/2/0
Router(config-cem)#Related Commands
cem-group
To create a circuit emulation (CEM) channel from one or more time slots of a T1 or E1 line of an NM-CEM-4TE1 network module, use the cem-group command in controller configuration mode. To remove a CEM group and release the associated time slots, use the no form of this command.
cem-group group-number {unframed | timeslots time-slot-range [speed kbps]}
no cem-group group-number
Syntax Description
Command Default
No CEM groups are defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to create CEM channels on the T1 or E1 network module, NM-CEM-4TE1. A maximum of 64 channels may be created on an NM-CEM-4TE1.
Examples
The following example shows how to create circuit emulation group number 0 with a single CEM channel including all time slots and the framing structure of the line on an NM-CEM-4TE1.
Router(config-controller)# cem-group 0 unframedThe following example shows how to create circuit emulation channel number 6 with T1 channel time slots one through four, nine, and ten using all eight bits of each time slot on an NM-CEM-4TE1.
Router(config-controller)# cem-group 6 timeslots 1-4,9,10 speed 64Related Commands
channel-group
To configure serial WAN on a T1 or E1 interface, use the channel-group command in controller configuration mode. To clear a channel group, use the no form of this command.
Cisco 2600 Series
channel-group channel-group-number timeslots range [speed] [aim aim-slot-number]
no channel-group channel-group-number
Cisco 2611 (Cisco Signaling Link Terminal [SLT])
channel-group channel-number
no channel-group channel-number
Cisco 2600XM Series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745
channel-group channel-group-number {timeslots range [speed] | unframed}
[aim aim-slot-number]no channel-group [channel-group-number timeslots range]
Cisco AS5350 and Cisco AS5400 Series
channel-group channel-group-number
no channel-group channel-group-number
Cisco MC3810
channel-group channel-number timeslots range [speed]
no channel-group [channel-number timeslots range]
Syntax Description
Command Default
The T1/E1 line is connected to the Motorola MPC-860x processor serial communication controller (SCC) or network module with two voice or WAN interface card (VIC or WIC) slots and 0/1/2 FastEthernet ports DSCC4 by default on Cisco 2600 series, Cisco 2600XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 routers.
There is no default behavior or values on the Cisco SLT (Cisco 2611).
The serial interface object encapsulation is set to HDLC on a network access server (NAS) (Cisco AS5350 and Cisco AS5400 series routers).
The default line speed is 64 kbps when a T1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
The default line speed is 64 kbps when an E1 controller is configured on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, Cisco 3745, and the Cisco MC3810.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to direct HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card. A channel group is created using Advanced Integration Module (AIM) HDLC resources when a channel-group command with the aim keyword is parsed during system initialization or when the command is entered during configuration. You must specify the aim keyword under a T1/E1 controller port to direct HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card on the Cisco 2600 series, Cisco 2600XM series, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745.
Note
If previous channel-group commands are configured with the aim keyword, subsequent channel-group commands without the aim keyword are rejected. Similarly, if a regular channel-group command is followed by another channel-group command with the aim keyword implemented, the second command is rejected on the Cisco 2600 and Cisco 2600XM.
A channel group using AIM HDLC resources is deleted only when a no channel-group command is entered.
By default, the channel-group command on a NAS sets the serial interface object encapsulation to HDLC. You must override the default by entering the encapsulation ss7 command for that serial interface object. Once you override the default, encapsulation cannot be changed again for that object. The SS7 encapsulation option is new to the Integrated Signaling Link Terminal feature and is available only for interface serial objects created by the channel-group command. The Integrated Signaling Link Terminal feature added SLT functionality on Cisco AS5350 and Cisco AS5400 platforms.
A digital SS7 link can be deleted by entering the no channel-group channel-group-number command on the associated T1/E1 controller. The link must first be stopped using the no shutdown command. It is not necessary to remove the channel ID association first.
Use the channel-group command in configurations where the router or access server must communicate with a T1 or E1 fractional data line. The channel group number may be arbitrarily assigned and must be unique for the controller. The time-slot range must match the time slots assigned to the channel group. The service provider defines the time slots that comprise a channel group.
Note
The channel group number can be 0 or 1 on the Cisco SLT (Cisco 2611).
The channel-group command also applies to Voice over Frame Relay, Voice over ATM, and Voice over HDLC on the Cisco MC3810.
Examples
The following example shows basic configuration directing HDLC traffic from the T1/E1 interface to the AIM-ATM-VOICE-30 DSP card, starting in global configuration mode:
Router(config)# controller e1 1/0Router(config-controller)# clock source internalRouter(config-controller)# channel-group 0 timeslots 1-31 aim 0The following example explicitly sets the encapsulation type to PPP to override the HDLC default:
Router# configure terminalRouter(config)# controller t1 6/0Router(config-controller)# channel-group 2 timeslots 3 aim 0Router(config-controller)# exitRouter(config)# interface serial 6/0:2Router(config-if)# encapsulation pppRouter(config-if)# ip address 10.0.0.1 255.0.0.0Router(config-if)# no shutdownRouter(config-if)# endThe following example shows how to explicitly set the encapsulation type to SS7 to override the HDLC default using the Integrated Signaling Link Terminal feature. This example uses an 8PRI DFC card inserted into slot 7, and DS0-timeslot 3 on trunk 5 of that card is used as an SS7 link:
Router# configure terminalRouter(config)# controller t1 7/5Router(config-controller)# channel-group 2 timeslots 3Router(config-controller)# exitRouter(config)# interface serial 7/5:2Router(config-if)# encapsulation ss7Router(config-if)# channel-id 0Router(config-if)# no shutdownRouter(config-if)# endThe following example defines three channel groups. Channel-group 0 consists of a single time slot, channel-group 8 consists of seven time slots and runs at a speed of 64 kbps per time slot, and channel-group 12 consists of two time slots.
Router(config-controller)# channel-group 0 timeslots 1Router(config-controller)# channel-group 8 timeslots 5,7,12-15,20 speed 64Router(config-controller)# channel-group 12 timeslots 2The following example configures a channel group on controller T1 0 on a Cisco MC3810:
Router(config)# controller T1 0Router(config-controller)# channel-group 10 timeslots 10-64The following example configures a channel group on controller E1 1 and specifies that all time slots are used for data:
controller e1 1 channel-group 1 unframed
Note
Related Commands
channel-group (interface)
To assign and configure an EtherChannel interface to an EtherChannel group, use the channel-group command in interface configuration mode. To remove the channel-group configuration from the interface, use the no form of this command.
channel-group channel-group-number mode {active | on | passive}
no channel-group channel-group-number
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
channel-group channel-group-number mode on
no channel-group channel-group-number
Cisco Catalyst Switches
channel-group channel-group-number mode {active | on | auto [non-silent] | desirable [non-silent] | passive}
no channel-group channel-group-number
Syntax Description
Command Default
No channel groups are assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
OSMs are not supported on Catalyst 6000 family switches that are configured with a Supervisor Engine 32.
IP Address for the Physical Interface
You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but Cisco highly recommends doing so.
Layer 2 and Layer 3 Port Channels
You can create both Layer 2 and Layer 3 port channels by entering the interface port-channel command or, when the channel-group gets its first physical interface assignment. The port channels are not created at run time, nor are they created dynamically.
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is automatically created when the channel group gets its first physical interface, if it is not already created.
Propagation of Configuration and Attribute Changes
Any configuration or attribute changes you make to the port-channel interface are propagated to all interfaces within the same channel group as the port channel. (for example, configuration changes are also propagated to the physical interfaces that are not part of the port-channel, but are part of the channel group.)
The on Keyword
When you use the on keyword, a usable EtherChannel exists only when a port group in on mode is connected to another port group in the on mode.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
Cisco Catalyst Switches
The number of valid values for number depends on the software release. For software releases prior to Cisco IOS Release 12.1(3a)E3, valid values are from 1 to 256; for Cisco IOS Release 12.1(3a)E3, 12.1(3a)E4, and 12.1(4)E1, valid values are from 1 to 64. Cisco IOS Release 12.1 E and later releases support a maximum of 64 values ranging from 1 to 256.
The channel-group number is global and is shared between all the channeling protocols. If a specific channel number is used for the PAgP-enabled interfaces of a channel group, that same channel number cannot be used for configuring a channel that has LACP-enabled interfaces or vice versa.
Entering the auto or desirable keyword enables PAgP on the specified interface; the command will be rejected if it is issued on an LACP-enabled interface.
The active and passive keywords are valid on PAgP-disabled interfaces only.
You can change the mode for an interface only if it is the only interface that is designated to the specified channel group.
The on keyword forces the bundling of the interface on the channel without any negotiation.
You can manually configure a switch with PAgP on one side and LACP on the other side in the on mode.
With the on mode, a usable EtherChannel exists only when a port group in on mode is connected to another port group in on mode.
If you enter the channel group command on an interface that is added to a channel with a different protocol than the protocol you are entering, the command is rejected.
If the interface belongs to a channel, the no form of this command is rejected.
All ports in the same channel group must use the same protocol; you cannot run two protocols on one channel group.
PAgP and LACP are not compatible; both ends of a channel must use the same protocol.
You can change the protocol at any time, but this change causes all existing EtherChannels to reset to the default channel mode for the new protocol.
Configure all ports in an EtherChannel to operate at the same speed and duplex mode (full duplex only for LACP mode).
All ports in a channel must be on the same DFC-equipped module. You cannot configure any of the ports to be on other modules.
On systems that are configured with nonfabric-enabled modules and fabric-enabled modules, you can bundle ports across all modules, but those bundles cannot include a DFC-equipped module port.
You do not have to create a port-channel interface before assigning a physical interface to a channel group. A port-channel interface is created automatically when the channel group gets its first physical interface, if it is not already created.
You do not have to disable the IP address that is assigned to a physical interface that is part of a channel group, but it is highly recommended.
You can create both Layer 2 and Layer 3 port channels by entering the interface port-channel command or when the channel group gets its first physical interface assignment. The port channels are not created at runtime or dynamically.
Any configuration or attribute changes that you make to the port-channel interface are propagated to all interfaces within the same channel group as the port channel (for example, configuration changes are also propagated to the physical interfaces that are not part of the port channel but are part of the channel group).
When configuring Layer 2 EtherChannels, you cannot put Layer 2 LAN ports into manually created port-channel logical interfaces.
Only the on mode is supported when using this command with GE-WAN ports on the OSM-2+4GE-WAN+ OSM to create QinQ link bundles for advanced QinQ translation. Also, you cannot use the channel-group command on GE-WAN interfaces if MPLS is configured. You must remove all IP, MPLS, and other Layer 3 configuration commands before using the channel-group command with GE-WAN interfaces.
Note
Caution
For a complete list of guidelines, see the "Configuring EtherChannel" section of the Cisco 7600 Series Router Cisco IOS Software Configuration Guide.
Fast EtherChannel
Before you assign a Fast Ethernet interface to a Fast EtherChannel group, you must first create a port-channel interface. To create a port-channel interface, use the interface port-channel global configuration command.
If the Fast Ethernet interface has an IP address assigned, you must disable it before adding the Fast Ethernet interface to the Fast EtherChannel. To disable an existing IP address on the Fast Ethernet interface, use the no ip address command in interface configuration mode.
The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. Fast EtherChannel can be configured between Cisco 7500 series routers and Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI) or between a Cisco 7500 series router or a Cisco 7000 series router with the RSP7000 and RSP700CI and a Cisco Catalyst 5000 switch.
A maximum of four Fast Ethernet interfaces can be added to a Fast EtherChannel group.
Caution
Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces
because it creates loops. Also, you must disable spanning tree.
To display information about the Fast EtherChannel, use the show interfaces port-channel EXEC command.
For more guidelines see the "Configuring EtherChannel" section of the Cisco 7600 Series Router Cisco IOS Software Configuration Guide and the "Configuring EtherChannel" section of the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide.
Examples
This example shows how to add EtherChannel interface 1/0 to the EtherChannel group that is specified by port-channel 1:
Router(config-if)# channel-group 1 mode onRouter(config-if)#The following example shows how to add interface Fast Ethernet 1/0 to the Fast EtherChannel group specified by port-channel 1:
Router(config)# interface port-channel 1Router(config-if)# exitRouter(config)# interface fastethernet 1/0Router(config-if)# channel-group 1Related Commands
channel-protocol (interface)
To enable Port Aggretation Control Protocol (PAgP) or Link Aggregation Control Protocol (LACP) on an interface to manage channeling, use the channel-protocol command in interface configuration mode. Use the no form of this command to deselect the protocol.
channel-protocol {lacp | pagp}
no channel-protocol
Syntax Description
Defaults
pagp
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid on multiple interfaces (for example, Fast Ethernet) and routers and switches including the Cisco 2900, 4500/4000, 6500/6000, and 7600 series.
Examples
The following example shows how to set the lacp.
(config-if)# channel-protocol lacpchannelized
To configure the T3 controller for channelized mode, use the channelized command in controller configuration mode. To configure the T3 controller for unchannelized mode, use the no form of this command.
channelized
no channelized
Syntax Description
This command has no arguments or keywords.
Defaults
T3 Controller
The T3 controller is channelized.
Channelized
Maximum transmission unit (MTU) size is set to 1500.
Unchannelized
MTU size is set to 4470.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the no channelized controller configuration command to configure the T3 controller for unchannelized mode. When you configure the PA-MC-2T3+ port adapter on a Cisco 7500 series router with the no channelized command, the MTU size is set to 4470. In channelized mode, the default MTU size is 1500. The change in MTU sizes will cause a memory recarve and CBus complex to occur, disrupting all traffic on the router for several minutes.
The following message will be displayed when commands initiate switching between channelized and unchannelized modes on a Cisco 7500 series router:
Change to subrate mode will cause cbus complex reset. Proceed? [yes/no]: YType Y for "yes" at the end of the warning. At the prompt, type ^Z to exit. You will exit configuration mode and enter unchannelized mode.
Caution
Examples
Cisco 7500 Series Router
The following example shows how to configure unchannelized mode on a PA-MC-2T3+ port adapter in slot 1 of a Versatile Interface Processor version 2 (VIP2) or VIP4 in a Cisco 7500 series router:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# controller T3 1/1/0Router(config-controller)# no channelizedChange to subrate mode will cause cbus complex reset. Proceed? [yes/no]: Y^ZCisco 10000 Series Router
The following example eliminates the T1 interfaces to create a full-rate T3 interface:
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# controller T3 2/0/0Router(config-controller)# no channelizedRouter(config-controller)# exitRouter(config)#clear aim
To clear the data compression Advanced Interface Module (AIM) daughter card registers and reset the hardware, use the clear aim command in privileged EXEC mode.
clear aim element-number
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear aim command is used to reset the data compression AIM hardware. This command is used if the compression Advanced Interface Module (CAIM) hardware becomes "stuck" or hangs for some reason. The CAIM registers are cleared, and the hardware is reset upon execution. All compression history is lost when the CAIM is reset.
This command is supported only on Cisco 2600 series routers.
Examples
The following example shows how to use the clear aim command. This command will reset the hardware, flushing the buffers and history for all compression tasks currently under operation:
Router# clear aim 0Router#1w0d: %CAIM-6-SHUTDOWN: CompressionAim0 shutting down1w0d: %CAIM-6-STARTUP: CompressionAim0 starting upRelated Commands
clear cable-diagnostics tdr
To clear a specific interface or clear all interfaces that support Time Domain Reflectometry (TDR), use the clear cable-diagnostics tdr command in privileged EXEC mode.
clear cable-diagnostics tdr [interface interface interface-number]
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The valid values for interface include the ge-wan, atm, and pos keywords that are supported on Catalyst 6000 family switches that are configured with a Supervisor Engine 2.
See the Release Notes for Cisco IOS Release 12.2 SX on the Catalyst 6500 and Cisco 7600 Supervisor Engine 720, Supervisor Engine 32, and Supervisor Engine 2 for the list of modules that support TDR
Examples
This example shows how to clear a specific interface:
Router# clear cable-diagnostics tdr interface gigabitethernet 4/1Router#Related Commands
clear catalyst6000 traffic-meter
To clear the traffic meter counters, use the clear catalyst6000 traffic-meter command in privileged EXEC mode.
clear catalyst6000 traffic-meter
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the traffic meter counters:
Router# clear catalyst6000 traffic-meterRouter#clear cem
To clear circuit emulation (CEM) statistics, use the clear cem command in privileged EXEC mode.
clear cem {slot | slot/port/channel | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to clear CEM statistics for CEM channel number 10 on the card installed in slot 1, port 1.
Router# clear cem 1/1/10
Related Commands
clear controller
To reset the T1 or E1 controller, use the clear controller command in user EXEC or privileged EXEC mode.
Cisco 7200 Series and Cisco 7500 Series Routers
clear controller {t1 | e1} slot/port
Cisco AS5200 Series and Cisco AS5300 Series Routers
clear controller {t1 | e1} number
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example resets the T1 controller at slot 4, port 0 on a Cisco 7500 series router:
Router# clear controller t1 4/0The following example resets the E1 controller at NIM 0:
Router# clear controller e1 0Related Commands
controller
Configures a T1, E1, or J1 controller and enters controller configuration mode.
clear controller lex
To reboot the LAN Extender chassis and restart its operating software, use the clear controller lex command in privileged EXEC mode.
clear controller lex number [prom]
Cisco 7500 Series
clear controller lex slot/port [prom]
Cisco 7200 Series and 7500 Series with a Packet over SONET Interface Processor
clear controller lex [type] slot/port
Cisco 7500 Series with Ports on VIP Cards
clear controller lex [type] slot/port-adapter/port
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear controller lex command halts operation of the LAN Extender and performs a cold restart.
Without the prom keyword, if an image exists in Flash memory, and that image has a newer software version than the PROM image, and that image has a valid checksum, then this command runs the Flash image. If any one of these three conditions is not met, this command reloads the PROM image.
With the prom keyword, this command reloads the PROM image, regardless of any Flash image.
Examples
The following example halts operation of the LAN Extender bound to LAN Extender interface 2 and causes the LAN Extender to perform a cold restart from Flash memory:
Router# clear controller lex 2reload remote lex controller? [confirm] yesThe following example halts operation of the LAN Extender bound to LAN Extender interface 2 and causes the LAN Extender to perform a cold restart from PROM:
Router# clear controller lex 2 promreload remote lex controller? [confirm] yesclear counters
To clear the interface counters, use the clear counters command in user EXEC or privileged EXEC mode.
clear counters [interface-type interface-number]
Cisco 7200 Series and 7500 Series with a Packet over SONET Interface Processor
clear counters [interface-type] slot/port
Cisco 7500 Series with Ports on VIP Cards
clear counters [interface-type] slot/port-adapter/port
Cisco 7600 Series
clear counters [interface interface-number | null interface-number | port-channel number | vlan vlan-id]
Syntax Description
interface-type
(Optional) Specifies the interface type; one of the keywords listed in Table 3.
interface-number
(Optional) Specifies the interface number displayed with the show interfaces command.
slot
Slot number. Refer to the appropriate hardware manual for slot and port information.
port
Port number. Refer to the appropriate hardware manual for slot and port information.
port-adapter
Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.
interface
(Optional) Interface type; possible valid values are ethernet, fastethernet, gigabitethernet, and tengigabitethernet. See the "Usage Guidelines" section for additional valid values.
interface-number
(Optional) Module and port number; see the "Usage Guidelines" section for valid values.
null interface-number
(Optional) Specifies the null interface; the valid value is 0.
port-channel number
(Optional) Specifies the channel interface; valid values are a maximum of 64 values ranging from 1 to 256.
vlan vlan-id
(Optional) Specifies the VLAN ID; valid values are from 1 to 4094.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command clears all the current interface counters from the interface unless the optional arguments interface-type and interface-number are specified to clear only a specific interface type (serial, Ethernet, Token Ring, and so on). Table 3 lists the command keywords and their descriptions.
Note
Protocol (SNMP), but only those seen with the show interface command. However, variables seen with the show interface command that could affect routing, such as load and reliability, or non-cumulative variables, such as input or output rates, are not cleared.The interface-number argument designates the module and port number. Valid values for interface-number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.
Examples
The following example shows how to clear all interface counters:
Router# clear countersThe following example shows how to clear the Packet OC-3 interface counters on a POSIP card in slot 1 on a Cisco 7500 series router:
Router# clear counters pos 1/0The following example shows how to clear the interface counters on a Fast EtherChannel interface:
Router# clear counter port-channel 1Clear "show interface" counters on all interfaces [confirm] Y%CLEAR-5-COUNTERS: Clear counter on all interfaces by console 1Related Commands
clear diagnostic event-log
To clear the diagnostic event logs for a specific module or event type, use the clear diagnostic event-log command in Privileged EXEC mode.
clear diagnostic event-log {event-type {error | info | warning} | module {num | slot subslot | all}}
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The clear diagnostic event-log command clears all the events for all the modules.
The clear diagnostic event-log module num command clears events only for a specific module.
The clear diagnostic event-log event-type command clears only specific event types such as error, informative, or warning events.
Examples
This example shows how to clear error event logs:
Router# clear diagnostic event-log event-type errorThis example shows how to clear event logs on module 3:
Router# clear diagnostic event-log module 3This example shows how to clear error event logs on all the modules:
Router# clear diagnostic event-log module allRelated Commands
clear dsip tracing
To clear Distributed System Interconnect Protocol (DSIP) tracing statistics (trace logging), use the clear dsip tracing command in privileged EXEC mode.
clear dsip tracing {counters | tracing} [control | data | ipc]
Syntax Description
Defaults
If no option is specified, all control, data, and inter-process communication counters or tracing buffers are cleared.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to clear the counters displayed with the show dsip tracing EXEC command.
Examples
In the following example, the DSIP counters are cleared (including data, control, and ipc counters):
Router# clear dsip tracingRelated Commands
show dsip tracing
Displays DSIP tracing buffer information.
show dsip version
Displays DSIP version information.
clear facility-alarm
To clear alarm conditions and reset the alarm contacts, use the clear facility-alarm command in privileged EXEC mode.
clear facility-alarm [critical | major | minor | source pem {0 | 1}]
Syntax Description
Command Default
Cisco ASR 1000 Series Routers
If specified without any options, clears all facility alarms with the exception of:
•
•
Cisco uBR10012 Universal Broadband Router
If specified without any options, clears all facility alarms.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Cisco ASR 1000 Series Routers
The clear facility-alarm command clears audible alarms. A recurrence of the original alarm source after the original alarm condition is removed restarts the audible alarm.
The clear facility-alarm command does not clear an alarm that illuminates the CRIT, MIN, or MAJ LED. This command does not turn off a visual alarm (DC light bulb) that is wired to the DB-25 connector on a power supply.
To clear a CRIT, MIN, or MAJ alarm LED or a visual alarm, you must resolve the alarm condition. For example, if a critical alarm LED is illuminated because an active SPA was removed without a graceful deactivation of the SPA, the only way to resolve that alarm is to replace the SPA.
Cisco uBR10012 Universal Broadband Router
The clear facility-alarm command clears the contacts to an external alarm panel. Only a recurrence of the original alarm source after the original alarm condition is removed can restart the audible alarm. These alarms are displayed by the show facility-alarm status command.
The alarm LEDs remain lit on the Performance Routing Engine (PRE) as long as the alarm condition continues and is not cleared by the clear facility-alarm command. An alarm can only be removed from the list by correcting the issue that is triggering the alarm.
Examples
The following example shows how to clear all facility alarms on the router:
Router# clear facility-alarmClearing all alarmsThe following example shows how to clear all critical facility alarms on the router:
Router# clear facility-alarm criticalClearing critical alarmsThe following example shows how to clear minor facility alarms only:
Router# clear facility-alarm minorClearing minor alarmsCisco uBR10012 Universal Broadband Router
The following example shows how to clear all alarms for both PEM modules on a Cisco uBR10012 universal broadband router:
Router# clear facility-alarm source pem 0Router# clear facility-alarm source pem 1Related Commands
clear hub
To reset and reinitialize the hub hardware connected to an interface of a Cisco 2505 or Cisco 2507 router, use the clear hub command in user EXEC or privileged EXEC mode.
clear hub ethernet number
Syntax Description
ethernet
Hub in front of an Ethernet interface.
number
Hub number to clear, starting with 0. Because there is only one hub, this number is 0.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example clears hub 0:
Router# clear hub ethernet 0Related Commands
hub
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
clear hub counters
To set the hub counters on an interface of a Cisco 2505 or Cisco 2507 router to zero, use the clear hub counters command in user EXEC or privileged EXEC mode.
clear hub counters [ether number [port [end-port]]]
Syntax Descriptionn
Defaults
If no port numbers are specified, counters for all ports are cleared.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows how to clear the counters displayed by a show hub command for all ports on hub 0:
Router# clear hub counters ether 0Related Commands
show hub
Displays information about the hub (repeater) on an Ethernet interface of a Cisco 2505 or Cisco 2507 router.
clear interface
To reset the hardware logic on an interface, use the clear interface command in user EXEC or privileged EXEC mode.
clear interface type number [name-tag]
Cisco 7200 Series and Cisco 7500 Series with a Packet OC-3 Interface Processor
clear interface type slot/port
Cisco 7500 Series with Ports on VIP Cards
clear interface type slot/port-adapter/port
Cisco 7500 Series
clear interface type slot/port[:channel-group]
Cisco 7500 Series with a CT3IP Port Adapter
clear interface type slot/port-adapter/port[:t1-channel]
Syntax Description
type
Interface type; it is one of the keywords listed in Table 4.
number
Port, connector, or interface card number.
name-tag
(Optional for use with the Redundant Link Manager (RLM) feature) Logic name to identify the server configuration so that multiple server configurations can be entered.
slot
Number of the slot being configured. Refer to the appropriate hardware manual for slot and port information.
port
Number of the port being configured. Refer to the appropriate hardware manual for slot and port information.
port-adapter
Number of the port adapter being configured. Refer to the appropriate hardware manual for information about port adapter compatibility.
:channel-group
(Optional) On Cisco 7500 series routers that support channelized T1, specifies the channel number from 0 to 23. This number is preceded by a colon.
:t1-channel
(Optional) For the CT3IP port adapter, the T1 channel is a number between 1 and 28. T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco numbering schemes for T1 channels within channelized T3 equipment.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
Under normal circumstances, you do not need to clear the hardware logic on interfaces.
This command clears all the current interface hardware logic unless the type and number arguments are specified to clear only a specific interface type (serial, Ethernet, Token Ring, and so on). Table 4 lists the command keywords and their descriptions.
Examples
The following example shows how to reset the interface logic on HSSI interface 1:
Router# clear interface hssi 1The following example shows how to reset the interface logic on Packet OC-3 interface 0 on the POSIP in slot 1:
Router# clear interface pos 1/0The following example shows how to reset the interface logic on T1 0 on the CT3IP port adapter in slot 9:
Router# clear interface serial 9/0/0:0The following example shows how to reset the interface logic on Fast EtherChannel interface 1:
Router# clear interface port-channel 1The following example shows how to reset demonstrates the use of the clear interface command with the RLM feature:
Router# clear interface loopback 1Router#02:48:52: rlm 1: [State_Up, rx ACTIVE_LINK_BROKEN] over link [10.1.1.1(Loopback1), 10.1.4.1]02:48:52: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] requests activation02:48:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is deactivated02:48:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] = socket[10.1.1.1, 10.1.4.1]02:48:52: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.1(Loopback1), 10.1.4.1] for user RLM_MGR02:48:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is opened02:48:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.5.1] = socket[10.1.1.1, 10.1.5.1]02:48:52: rlm 1: [State_Recover, rx USER_SOCKET_OPENED] over link [10.1.1.1(Loopback1), 10.1.5.1] for user RLM_MGR02:48:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.5.1] is opened02:48:52: rlm 1: [State_Recover, rx START_ACK] over link [10.1.1.2(Loopback2), 10.1.4.2]02:48:52: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] is activated02:48:52: rlm 1: [State_Up, rx LINK_OPENED] over link [10.1.1.1(Loopback1), 10.1.4.1]Router# show rlm group 1 statusRLM Group 1 StatusUser/Port: RLM_MGR/3000Link State: Up Last Link Status Reported: Up_RecoveredNext tx TID: 4 Last rx TID: 0Server Link Group[r1-server]:link [10.1.1.1(Loopback1), 10.1.4.1] = socket[standby, 10.1.1.1, 10.1.4.1]link [10.1.1.2(Loopback2), 10.1.4.2] = socket[active, 10.1.1.2, 10.1.4.2]Server Link Group[r2-server]:link [10.1.1.1(Loopback1), 10.1.5.1] = socket[opening, 10.1.1.1, 10.1.5.1]link [10.1.1.2(Loopback2), 10.1.5.2] = socket[opening, 10.1.1.2, 10.1.5.2]Router#02:49:52: rlm 1: [State_Up, rx UP_RECOVERED_MIN_TIMEOUT]02:49:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] requests activation02:49:52: rlm 1: [State_Switch, rx SWITCH_ACK] over link [10.1.1.1(Loopback1), 10.1.4.1]02:49:52: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] is deactivated02:49:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is activatedRelated Commands
clear interface fastethernet
To reset the controller for a specified Fast Ethernet interface, use the clear interface fastethernet command in privileged EXEC mode.
Cisco 4500 and Cisco 4700 Series
clear interface fastethernet interface-number
Cisco 7200 and Cisco 7500 Series
clear interface fastethernet slot/port
Cisco 7500 Series with a VIP
clear interface fastethernet slot/port-adapter/port
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Cisco 4500 Series
The following example resets the controller for Fast Ethernet interface 0 on a Cisco 4500:
Router# clear interface fastethernet 0Cisco 7200 and Cisco 7500 Series
The following example resets the controller for the Fast Ethernet interface located in slot 1, port 0 on a Cisco 7200 series router or Cisco 7500 series router:
Router# clear interface fastethernet 1/0Cisco 7500 Series with a VIP
The following example resets the controller for the Fast Ethernet interface located in slot 1, port adapter 0, port 0 on a Cisco 7500 series router with a virtual interface processor (VIP):
Router# clear interface fastethernet 1/0/0Related Commands
clear interface gigabitethernet
To clear the hardware logic on a Gigabit Ethernet IEEE 802.3z interface, use the clear interface gigabitethernet command in privileged EXEC mode.
clear interface gigabitethernet number
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The number argument designates the module and port number. Valid values for number depend on the specified interface type and the chassis and module that are used. For example, if you specify a Gigabit Ethernet interface and have a 48-port 10/100BASE-T Ethernet module that is installed in a 13-slot chassis, valid values for the module number are from 1 to 13 and valid values for the port number are from 1 to 48.
Examples
This example shows how to clear the hardware logic on a Gigabit Ethernet IEEE 802.3z interface:
Router# clear interface gigabitethernet 5Router#Related Commands
show interfaces status
Displays the interface status or a list of interfaces in an error-disabled state on LAN ports only.
clear interface serial
To reset the statistical information specific to a serial interface, use the clear interface serial command in user EXEC or privileged EXEC mode.
clear interface serial dial-shelf/slot/t3-port:t1-num:chan-group
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
The clear interface serial command clears the interface hardware. To reset the counters for an interface, use the clear counters command with the serial keyword specified. To confirm at the prompt, use the show interfaces serial command.
Examples
The following example clears the interface hardware, disconnecting any active lines:
Router# clear interface serial 1/4/0:2:23Related Commands
clear interface vlan
To clear the hardware logic on a virtual local area network (VLAN), use the clear interface vlan command in privileged EXEC mode.
clear interface vlan vlan-id
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the hardware logic on a specific VLAN:
Router# clear interface vlan 5Router#Related Commands
show interfaces status
Displays the interface status or a list of interfaces in an error-disabled state on LAN ports only.
clear ipc statistics
To clear all interprocess communication (IPC) statistics, use the clear ipc statistics command in privileged EXEC mode.
clear ipc statistics
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear ipc statistics command clears all the IPC statistics and is useful for troubleshooting issues with IPC services.
Examples
The following example shows how to clear all of the statistics used by IPC services. A show ipc status command is issued first to display the current IPC counters for a local IPC server. The clear ipc statistics command is then entered to clear and reset the counters. A final show ipc status command is issued to show that all the counters, except those counters that show the packets sent since the clearing, are reset to zero.
Router# show ipc statusIPC System StatusTime last IPC stat cleared : neverThis processor is the IPC master server.Do not drop output of IPC frames for test purposes.1000 IPC Message Headers Cached.Rx Side Tx SideTotal Frames 189 140Total from Local Ports 189 70Total Protocol Control Frames 70 44Total Frames Dropped 0 0Service UsageTotal via Unreliable Connection-Less Service 145 0Total via Unreliable Sequenced Connection-Less Svc 0 0Total via Reliable Connection-Oriented Service 44 70IPC Protocol Version 0Total Acknowledgements 70 44Total Negative Acknowledgements 0 0Device DriversTotal via Local Driver 0 0Total via Platform Driver 0 70Total Frames Dropped by Platform Drivers 0 0Reliable Tx StatisticsRe-Transmission 0Re-Tx Timeout 0Rx Errors Tx ErrorsUnsupp IPC Proto Version 0 Tx Session Error 0Corrupt Frame 0 Tx Seat Error 0Duplicate Frame 0 Destination Unreachable 0Out-of-Sequence Frame 0 Tx Test Drop 0Dest Port does Not Exist 0 Tx Driver Failed 0Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0Unable to Deliver Msg 0Buffer Errors Misc ErrorsIPC Msg Alloc 0 IPC Open Port 0Emer IPC Msg Alloc 0 No HWQ 0IPC Frame PakType Alloc 0 Hardware Error 0IPC Frame MemD Alloc 0Tx Driver ErrorsNo Transport 0MTU Failure 0Dest does not Exist 0Router# clear ipc statisticsRouter# show ipc statusIPC System StatusTime last IPC stat cleared : 00:00:03This processor is the IPC master server.Do not drop output of IPC frames for test purposes.1000 IPC Message Headers Cached.Rx Side Tx SideTotal Frames 26 0Total from Local Ports 26 0Total Protocol Control Frames 0 0Total Frames Dropped 0 0Service UsageTotal via Unreliable Connection-Less Service 26 0Total via Unreliable Sequenced Connection-Less Svc 0 0Total via Reliable Connection-Oriented Service 0 0IPC Protocol Version 0Total Acknowledgements 0 0Total Negative Acknowledgements 0 0Device DriversTotal via Local Driver 0 0Total via Platform Driver 0 0Total Frames Dropped by Platform Drivers 0 0Reliable Tx StatisticsRe-Transmission 0Re-Tx Timeout 0Rx Errors Tx ErrorsUnsupp IPC Proto Version 0 Tx Session Error 0Corrupt Frame 0 Tx Seat Error 0Duplicate Frame 0 Destination Unreachable 0Out-of-Sequence Frame 0 Tx Test Drop 0Dest Port does Not Exist 0 Tx Driver Failed 0Rx IPC Msg Alloc Failed 0 Ctrl Frm Alloc Failed 0Unable to Deliver Msg 0Buffer Errors Misc ErrorsIPC Msg Alloc 0 IPC Open Port 0Emer IPC Msg Alloc 0 No HWQ 0IPC Frame PakType Alloc 0 Hardware Error 0IPC Frame MemD Alloc 0Tx Driver ErrorsNo Transport 0MTU Failure 0Dest does not Exist 0Related Commands
clear lacp counters
To clear the statistics for all interfaces belonging to a specific channel group, use the clear lacp counters command in privileged EXEC mode.
clear lacp [channel-group] counters
Syntax Description
Command Default
None
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If you do not specify a channel-group, all channel groups are cleared.
If you enter this command for a channel group that contains members in PAgP mode, the command is ignored.
Examples
This example shows how to clear the statistics for a specific group:
Router# clear lacp 1 countersRouter#Related Commands
clear platform netint
To clear the interrupt-throttling counters for the platform, use the clear platform netint command in privileged EXEC mode.
clear platform netint
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Examples
This example shows how to clear the interrupt-throttling counters for the platform:
Router# clear platform netintRouter#Related Commands
clear rbscp
To reset and restart a Rate Based Satellite Control Protocol (RBSCP) tunnel, use the clear rbscp command in privileged EXEC mode.
clear rbscp [tunnel tunnel-number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear rbscp command resets the tunnel interface to its initial state and this clears RBSCP statistical information. Use this command for troubleshooting issues with RBSCP tunnels.
Examples
The following example shows how to clear the RBSCP statistics. A show rbscp statistics command is issued first to display the current RBSCP counters for tunnel interface 0. The clear rbscp command is then entered to reset and restart tunnel interface 0. All the counters for tunnel interface 0 are reset to zero. A final show rbscp statistics command is issued to show that all the counters, except those counters that show the packets sent since the clearing, are reset to zero.
Router# show rbscp statistics tunnel 0Tunnel0 is up, line protocol is upRBSCP protocol statistics:Init FWD-TSNs sent 15, received 11TUNNEL-UPs sent 10, received 5CLOSEDs sent 3, received 2TSNs sent 40, resent 2, lost by sender 1TSNs received 36 (duplicates 2)FWD-TSNs sent 144 (heartbeats 2)FWD-TSNs received 120 (ignored 1)FWD-TSNs caused 3 packet drops, 0 whole window dropsSACKs sent 10, received 6 (ignored 1)Recovered with RTX 1Received with delay 2Most released at once 5Failed sends into the: tunnel 1, network 0Dropped due to: excess delay 0, tmit queue full 0Max on any queue: num packets: 12, num bytes: 0Max outstanding: 0Router# clear rbscp tunnel 0Tunnel0: cleared statisticsRouter# show rbscp statistics tunnel 0Tunnel0 is up, line protocol is upRBSCP protocol statistics:Init FWD-TSNs sent 0, received 0TUNNEL-UPs sent 0, received 0CLOSEDs sent 0, received 0TSNs sent 0, resent 0, lost by sender 0TSNs received 0 (duplicates 0)FWD-TSNs sent 26 (heartbeats 0)FWD-TSNs received 0 (ignored 0)FWD-TSNs caused 0 packet drops, 0 whole window dropsSACKs sent 0, received 0 (ignored 0)Recovered with RTX 0Received with delay 0Most released at once 0Failed sends into the: tunnel 0, network 0Dropped due to: excess delay 0, tmit queue full 0Max on any queue: num packets: 0, num bytes: 0Max outstanding: 0Related Commands
clear service-module serial
To reset an integrated CSU/DSU, use the clear service-module serial command in privileged EXEC mode.
clear service-module serial number
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command only in severe circumstances (for example, when the router is not responding to a CSU/DSU configuration command).
This command terminates all DTE and line loopbacks that are locally or remotely configured. It also interrupts data transmission through the router for up to 15 seconds. The software performs an automatic software reset in case of two consecutive configuration failures.
The CSU/DSU module is not reset with the clear interface command.
Caution
refrain from using this command. This command erases the router's past CSU/DSU performance statistics. To clear only the CSU/DSU performance statistics, issue the clear counters command.
Examples
The following example show how to reset the CSU/DSU on a router:
Router# clear service-module serial 0Related Commands
clear counters
Clears the interface counters.
test service-module
Performs self-tests on an integrated CSU/DSU serial interface module, such as a 4-wire, 56/64-kbps CSU/DSU.
clear top counters interface report
To clear the TopN reports, use the clear top counters interface report command in privileged EXEC mode.
clear top counters interface report number
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.2(18)SXE
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is supported on Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet ports only. LAN ports on the OSMs are also supported.
The clear top interface report command clears all the completed reports. It does not clear the pending TopN reports. When you specify a report number, the TopN task is cleared regardless of its status.
Examples
This example shows how to clear all TopN tasks:
Router# clear top counters interface report 100004:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 1 deleted by the console04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 2 deleted by the console04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 3 deleted by the console04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 4 deleted by the console1/24/Router#This example shows the output if you attempt to clear a pending TopN task:
Router# clear top counters interface report 404:52:12: %TOPN_COUNTERS-5-KILLED: TopN report 4 killed by the sattili onvty0 (9.10.69.9)Router#Related Commands
collect top counters interface
Lists the TopN processes and specific TopN reports.
show top counters interface report
Displays TopN reports and information.
clock
To configure the port clocking mode for the 1000BASE-T transceivers, use the clock command in interface configuration mode. To return to the default settings,use the no form of this command.
clock {auto | active [prefer] | passive [prefer]}
no clock
Syntax Description
Defaults
auto
Command Modes
Interface configuration
Command History
12.2(17a)SX
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is supported on the 1000BASE-T transceivers only.
If the clock mode of the near end of a link does not match the clock mode of the far end, the line protocol does not come up.
The active and passive clock status is determined during the auto negotiation process before the transmission link is established.
The clock command supports the following configurations:
•
•
•
•
•
Enter the show running-config interface command to display the current clock mode.
Enter the show interfaces command to display the clock mode that is negotiated by the firmware.
Examples
This example shows how to enable the active-clock operation:
Router(config-if)# clock activeRouter(config-if)#Related Commands
show interfaces
Displays traffic that is seen by a specific interface.
show running-config interface
Displays the status and configuration of the module or Layer 2 VLAN.
clock mode
To configure the clock mode of a serial circuit emulation (CEM) channel, use the clock mode command in CEM configuration mode. To reset the clock mode to its default, use the no form of this command.
clock mode {normal | split}
no clock mode
Syntax Description
Command Default
The serial CEM channel clock defaults to normal mode.
Command Modes
CEM configuration
Command History
Usage Guidelines
This command applies only to serial ports.
Examples
The following example shows how to configure the CEM clock for normal mode.
Router(config-cem)# clock mode normal
Related Commands
