-
Cisco IOS Interface and Hardware Component Command Reference, Release 12.3
-
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
-
Interface and Hardware Component Commands: M through R
-
Interface and Hardware Component Commands: scramble through show aps
-
Interface and Hardware Component Commands: show compress through show hub
-
Interface and Hardware Component Commands: show interfaces through syscon source-interface
-
Interface and Hardware Component Commands: T through Z
-
Table Of Contents
Interface and Hardware Component Commands
channel-group (Fast EtherChannel)
clock source (SONET controller)
clock source (T1/E1 controller)
clock source (T1/E1 interface)
clock source (T3/E3 controller)
Interface and Hardware Component Commands
alarm-interface
To enter alarm-interface mode and configure the alarm interface controller (AIC), use the alarm-interface command in global configuration mode. To leave alarm interface mode, use the exit command.
alarm-interface slot-number
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
12.2(2)XG
This command was introduced for the Cisco 2600 series and the Cisco 3600 series.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Examples
The following examples show how the alarm-interface command is used in conjunction with the ip address and the reset commands:
Router(config)# alarm-interface 5Router(config-aic)# ip address 10.2.130.105A change in the AIC IP configuration might not take effect until the next time the card is started. Use the reset command to restart the card, as in the following example:
Router(config-aic)# resetAlarm Interface Card in slot 5 restartedRouter(config-aic)# endRelated Commands
ip address
Sets a primary or secondary IP address for an interface.
reset
Resets the AIC CPU.
aps authenticate
To enable authentication and specify the string that must be present to accept any packet on the out-of-band (OOB) communications channel on a Packet-over-SONET (POS) interface, use the aps authenticate command in interface configuration mode. To disable authentication, use the no form of this command.
aps authenticate string
no aps authenticate
Syntax Description
string
Text that must be present to accept the packet on a protected or working interface. A maximum of eight alphanumeric characters are accepted.
Defaults
Authentication is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps authenticate command to ensure that only valid packets are accepted on the OOB communications channel.
The aps authenticate command must be configured on both the working and protect interfaces.
Examples
The following example shows how to enable authentication on POS interface 0 in slot 4:
Router# configure terminalRouter(config)# interface pos 4/0/0Router(config-if)# aps working 1Router(config-if)# aps authenticate sanjoseRouter(config-if)# endRelated Commands
Enables a POS interface as a protect interface.
Configures a POS interface as a working interface.
aps force
To manually switch the specified circuit to a protect interface, unless a request of equal or higher priority is in effect, use the aps force command in interface configuration mode. To cancel the switch, use the no form of this command.
aps force circuit-number
no aps force circuit-number
Syntax Description
Defaults
No circuit is switched.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps force command to manually switch the interface to a protect interface when you are not using the aps revert command. For example, if you need to change the fiber connection, you can manually force the working interface to switch to the protect interface.
In a one-plus-one (1+1) configuration only, you can use the aps force 0 command to force traffic from the protect interface back onto the working interface.
The aps force command has a higher priority than any of the signal failures or the aps manual command.
The aps force command is configured only on protect interfaces.
Examples
The following example shows how to force the circuit on POS interface 0 in slot 3 (a protect interface) back onto a working interface:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps protect 10/30/1/1Router(config-if)# aps force 1Router(config-if)# endRelated Commands
Manually switches a circuit to a protect interface.
Enables a POS interface as a protect interface.
Configures a POS interface as a working interface.
aps group
To allow more than one protect and working interface to be supported on a router, use the aps group command in interface configuration mode. To remove a group, use the no form of this command.
aps group group-number
no aps group group-number
Syntax Description
Defaults
No groups exist.
Note
0 is a valid group number.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps group command to specify more than one working and protect interfaces on a router, for example, working channel for group 0 and protect channel for group 1 on one router, and working channel for group 1 and protect channel for group 0 on another router.
The default group number is 0. The aps group 0 command does not imply that no groups exist.
The aps group command must be configured on both the protect and working interfaces.
Examples
The following example shows hw to configure two working/protect interface pairs. Working interface (3/0/0) is configured in group 10 (the protect interface for this working interface is configured on another router), and protect interface (2/0/1) is configured in group 20.
Router# configure terminalRouter(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.6 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 3/0/0Router(config-if)# aps group 10Router(config-if)# aps working 1Router(config-if)# exitRouter(config)# interface pos 2/0/1Router(config-if)# aps group 20Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# endOn the second router, protect interface (4/0/0) is configured in group 10, and working interface (5/0/0) is configured in group 20 (the protect interface for this working interface is configured on another router).
Router(config)# interface ethernet 0/0Router(config-if)# ip address 10.7.7.7 255.255.255.0Router(config-if)# exitRouter(config)# interface pos 4/0/0Router(config-if)# aps group 10Router(config-if)# aps protect 1 10.7.7.6Router(config-if)# exitRouter(config)# interface pos 5/0/0Router(config-if)# aps group 20Router(config-if)# aps working 1Router(config-if)# endRelated Commands
Enables a POS interface as a protect interface.
Configures a POS interface as a working interface.
aps lockout
To prevent a working interface from switching to a protect interface, use the aps lockout command in interface configuration mode. To remove the lockout, use the no form of this command.
aps lockout circuit-number
no aps lockout circuit-number
Syntax Description
Defaults
No lockout exists.
Command Modes
Interface configuration
Command History
Usage Guidelines
The aps lockout command is configured only on protect interfaces.
Examples
The following example shows how to lock out POS interface 3/0/0 (that is, prevents the circuit from switching to a protect interface if the working circuit becomes unavailable):
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# aps lockout 1Router(config-if)# endRelated Commands
Enables a POS interface as a protect interface.
Configures a POS interface as a working interface.
aps manual
To manually switch a circuit to a protect interface, use the aps manual command in interface configuration mode. To cancel the switch, use the no form of this command.
aps manual circuit-number
no aps manual circuit-number
Syntax Description
Defaults
No circuit is switched.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps manual command to manually switch the interface to a protect interface. For example, you can use this feature when you need to perform maintenance on the working channel. If a protection switch is already up, you can also use the aps manual command to revert the communication link back to the working interface before the wait to restore (WTR) time has expired. The WTR time period is set by the aps revert command.
In a one-plus-one (1+1) configuration only, you can use the aps manual 0 command to force traffic from the protect interface back onto the working interface.
The aps manual command is a lower priority than any of the signal failures or the aps force command.
Examples
The following example shows how to force the circuit on POS interface 0 in slot 3 (a working interface) back onto the protect interface:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps working 1Router(config-if)# aps manual 1Router(config-if)# endRelated Commands
aps protect
To enable a POS interface as a protect interface, use the aps protect command in interface configuration mode. To remove the POS interface as a protect interface, use the no form of this command.
aps protect circuit-number ip-address
no aps protect circuit-number ip-address
Syntax Description
circuit-number
Number of the circuit to enable as a protect interface.
ip-address
IP address of the router that has the working POS interface.
Defaults
No circuit is protected.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps protect command to configure the POS interface used by a working interface if the working interface becomes unavailable because of a router failure, degradation or loss of channel signal, or manual intervention.
Caution
Examples
The following example shows how to configure circuit 1 on POS interface 5/0/0 as a protect interface for the working interface on the router with the IP address of 10.7.7.7. For information on how to configure the working interface, refer to the aps working command.
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# endRelated Commands
aps revert
To enable automatic switchover from the protect interface to the working interface after the working interface becomes available, use the aps revert command in interface configuration mode. To disable automatic switchover, use the no form of this command.
aps revert minutes
no aps revert
Syntax Description
minutes
Number of minutes until the circuit is switched back to the working interface after the working interface is available.
Defaults
Automatic switchover is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps revert command to return the circuit to the working interface when it becomes available.
The aps revert command is configured only on protect interfaces.
Examples
The following example shows how to enable circuit 1 on POS interface 5/0/0 to revert to the working interface after the working interface has been available for 3 minutes:
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps protect 1 10.7.7.7Router(config-if)# aps revert 3Router(config-if)# endRelated Commands
aps timers
To change the time between hello packets and the time before the protect interface process declares a working interface router to be down, use the aps timers command in interface configuration mode. To return to the default timers, use the no form of this command.
aps timers seconds1 seconds2
no aps timers
Syntax Description
Defaults
Hello time is 1 second
Hold time is 3 seconds.Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps timers command to control the time between an automatic switchover from the protect interface to the working interface after the working interface becomes available.
Normally, the hold time is greater than or equal to three times the hello time.
The aps timers command is configured only on protect interfaces.
Examples
The following example shows how to specify a hello time of 2 seconds and a hold time of 6 seconds on circuit 1 on POS interface 5/0/0:
Router# configure terminalRouter(config)# interface pos 5/0/0Router(config-if)# aps working 1Router(config-if)# aps timers 2 6Router(config-if)# endaps unidirectional
To configure a protect interface for unidirectional mode, use the aps unidirectional command in interface configuration mode. To return to the default, bidirectional mode, use the no form of this command.
aps unidirectional
no aps unidirectional
Syntax Description
This command has no arguments or keywords.
Defaults
Bidirectional mode
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the aps unidirectional command when you must interoperate with SONET network equipment, Add Drop Multiplexor(s) (ADMs) that supports unidirectional mode.
Note
The aps unidirectional command is configured only on protect interfaces.
Examples
The following example shows how to configure POS interface 3/0/0 for unidirectional mode:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps unidirectionalRouter(config-if)# aps protect 1 10.7.7.7Router(config-if)# endaps working
To configure a Packet over SONET (POS) interface as a working interface, use the aps working command in interface configuration mode. To remove the protect option from the POS interface, use the no form of this command.
aps working circuit-number
no aps working circuit-number
Syntax Description
Defaults
No circuit is configured as working.
Command Modes
Interface configuration
Command History
Usage Guidelines
When a working interface becomes unavailable because of a router failure, degradation or loss of channel signal, or manual intervention, the circuit is switched to the protect interface to maintain the connection.
To enable the circuit on the protect interface to switch back to the working interface after the working interface becomes available again, use the aps revert command in interface configuration mode.
Caution
Examples
The following example shows how to configure POS interface 0 in slot 4 as a working interface. For information on how to configure the protect interface, refer to the aps protect command.
Router# configure terminalRouter(config)# interface pos 4/0/0Router(config-if)# aps working 1Router(config-if)# endRelated Commands
Enables a POS interface as a protect interface.
Enables automatic switchover from the protect interface to the working interface after the working interface becomes available.
atm sonet
To set the mode of operation and thus control the type of the ATM cell used for cell-rate decoupling on the SONET physical layer interface module (PLIM), use the atm sonet command in interface configuration mode. To restore the default Synchronous Transport Signal level 12, concatenated (STS-12c) operation, use the no form of this command.
atm sonet [stm-4]
no atm sonet [stm-4]
Syntax Description
stm-4
(Optional) Synchronous Digital Hierarchy/Synchronous Transport Signal level 4 (SDH/STM-4) operation (ITU-T specification).
Defaults
STS-12c
Command Modes
Interface configuration
Command History
Usage Guidelines
Use STM-4 in applications in which SDH framing is required.
Use the default (STS-12c) in applications in which the ATM switch requires "unassigned cells" for rate adaptation. An unassigned cell contains 32 zeros.
Examples
The following example shows how to set the mode of operation to SONET STM-4 on ATM interface 3/0:
Router(config)# interface atm 3/0Router(config-if)# atm sonet stm-4Router(config-if)# endau-3
To configure a particular Administrative Unit type 3 (AU-3) of an E1 line that has been mapped to an AU-3, use the au-3 command in controller configuration mode.
au-3 au-3-number
Syntax Description
Defaults
No default behavior or values
Command Modes
Controller configuration
Command History
12.0(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
An administrative unit group (AUG) of an STM-1 can be derived from either AU-3s or an AU-4. Use the aug mapping au-3 configuration controller command to map the AUG to an AU-3 with the following muxing/alignment/mapping:
C-12 <--> VC-12 <--> TU-12 <--> TUG-2 <--> VC-3 <--> AU-3 <--> AUG
Configuring the au-3 command enables you to enter configuration controller au3 command mode and creates a serial interface with the following name format:
slot/port-adapter/port.au-3-number/tug-2-number/e1-number
The aug mapping au-3 and au-3 commands are available only when SDH framing is configured.
Examples
The following example shows how to configure AUG mapping to be derived from an AU-3 and selects AU-3 3 to configure as a serial interface:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-3Router(config-ctrlr-au3)# au-3 3Related Commands
au-4 tug-3
Specifies a TUG-3 for configuration.
aug mapping
Configures the AUG mapping mode of the PA-MC-STM-1 to AU-3.
au-4 tug-3
To specify the Administrative Unit type 4 (AU-4) and Tributary Unit group type 3 (TUG-3) number of an E1 line that has been mapped to an AU-4, use the au-4 tug-3 command in controller configuration mode.
au-4 au-4-number tug-3 tug-3-number
Syntax Description
au-4-number
Number in the range from 1 to N where N is the STM level. Default is 1.
tug-3-number
Number in the range from 1 to 3.
Defaults
Default au-4-number value for STM-1 card is 1.
Command Modes
Controller configuration
Command History
12.0(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
An AUG of an STM-1 can be derived from either AU-3s or an AU-4. Use the aug mapping au-4 configuration controller command to map the AUG to an TUG-3 with the following muxing/alignment/mapping:
C-12 <--> VC-12 <--> TU-12< --> TUG-2 <--> TUG-3 <--> VC-4 <--> AU-4 <--> AUG
Configuring the au-4 command enables you to enter configuration controller tug3 command mode and creates a serial interface with the following name format:
slot/port-adapter/port.au-4-number/tug-2-number/e1-number
The aug mapping au-4 and au-4 tug-3 commands are available only when SDH framing is configured.
Examples
The following example shows how to configure AUG mapping to be derived from a TUG-3 and selects TUG-3 1 of AU-4 1:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-ctrlr-tug3)# au-4 1 tug-3 1Related Commands
au-3
Specifies an AU-3 for configuration.
aug mapping
Configures the AUG mapping mode.
aug mapping
To configure administrative unit group (AUG) mapping when SDH framing is selected, use the aug mapping command in controller configuration mode.
aug mapping {au-3 | au-4}
Syntax Description
Defaults
au-4
Command Modes
Controller configuration
Command History
Usage Guidelines
In SDH, there are two possible mapping/multiplexing schemes for most payload types: ANSI and ETSI.
In ANSI mapping, the Low Order payloads are aggregated into a VC-3 High Order Path. An AU pointer is added to the VC-3 to create an AU-3. Three such AU-3s are then synchronously multiplexed into an AUG. The multiplexing scheme is as follows:
... VC-3 <-> AU-3 (x3) <-> AUG <-> STM-1
SDH ANSI mapping is very similar to the SONET frame structure.
In ETSI mapping, the Low Order payloads are aggregated into a VC-4 High Order Path. An AU pointer is added to the VC-4 to create an AU-4 (Administrative Unit type 4). One AU-4 is "multiplexed" into an AUG (AU group), which is to say, the AUG is, in fact, equivalent to an AU-4. The multiplexing scheme is as follows:
... TUG-3 (x3) <-> VC-4 <-> AU-4 (x1) <-> STM-1
This command is available only when SDH framing is configured.
This command does not have a no form because data must flow using one of the two mapping/multiplexing schemes.
Examples
The following example shows how to configure AU-3 mapping for the STM-1 trunk card:
Router(config)# controller sonet 1/0Router(config-controller)# aug mapping au-3auto-polarity
To enable automatic receiver polarity reversal on a hub port connected to an Ethernet interface of a Cisco 2505 or Cisco 2507 router, use the auto-polarity command in hub configuration mode. To disable this function, use the no form of this command.
auto-polarity
no auto-polarity
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Hub configuration
Command History
Usage Guidelines
This command applies to a port on an Ethernet hub only.
Examples
The following example shows how to enable automatic receiver polarity reversal on hub 0, ports 1 through 3:
Router(config)# hub ethernet 0 1 3Router(config-hub)# auto-polarityRelated Commands
hub
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
b2 sd-ber
To set the signal degrade bit-error rate (BER) threshold values, use the b2 sd-ber command in controller configuration mode. To return to the default setting, use the no form of this command.
b2 sd-ber rate
no b2 sd-ber
Syntax Description
rate
Bit-error rate from 3 to 9 (10-n). The value of 9 represents better quality, and the value of 3 represents lower quality. The default is 6.
Defaults
rate: 6
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the threshold for degradation of quality of signal with b2 errors.
Examples
The following example shows how to configure a signal degrade BER threshold value of 7 on the SONET controller:
Router(config)# controller sonet 1/0Router(config-controller)# b2 sd-ber 7Related Commands
b2 sf-ber
To set the signal failure bit-error rate (BER) threshold values, use the b2 sf-ber command in controller configuration mode. To return to the default setting, use the no form of this command.
b2 sf-ber rate
no b2 sf-ber rate
Syntax Description
rate
Bit-error rate from 3 to 9 (10-n). The value of 9 represents better quality, and the value of 3 represents lower quality. The default is 3.
Defaults
rate: 3
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the threshold for failure of quality of signal with b2 errors. The value of 9 represents better quality and the value of 3 represents lower quality.
Examples
The following example shows how to configure a signal failure BER threshold value of 7 on the SONET controller:
Router(config)# controller sonet 1/0Router(config-controller)# b2 sf-ber 7Related Commands
bandwidth (interface)
To set and communicate the current bandwidth value for an interface to higher-level protocols, use the bandwidth command in interface configuration mode. To restore the default values, use the no form of this command.
bandwidth {kbps | inherit [kbps]}
no bandwidth {kbps | inherit [kbps]}
Syntax Description
Defaults
Default bandwidth values are set during startup; the bandwidth values can be displayed using the show interfaces EXEC command.
Command Modes
Interface configuration
Command History
Usage Guidelines
Bandwidth Information
The bandwidth command sets an informational parameter to communicate only the current bandwidth to the higher-level protocols; you cannot adjust the actual bandwidth of an interface using this command.
Note
Changing Bandwidth
For some media, such as Ethernet, the bandwidth is fixed; for other media, such as serial lines, you can change the actual bandwidth by adjusting hardware. For both classes of media, you can use the bandwidth configuration command to communicate the current bandwidth to the higher-level protocols.
Bandwidth Inheritance
Before the introduction of the bandwidth inherit command option, when the bandwidth value was changed on the main interface, existing subinterfaces did not inherit the bandwidth value from the main interface. If the subinterface was created before the bandwidth was changed on the main interface, then the subinterface would receive the default bandwidth of the main interface, not the configured bandwidth. Additionally, if the router was subsequently reloaded, the bandwidth of the subinterface would then change to the bandwidth configured on the main interface.
The bandwidth inherit command controls how a subinterface inherits the bandwidth of its main interface. This functionality eliminates the inconsistencies related to whether or not the router has been reloaded and what the order was in entering the commands.
The no bandwidth inherit command enables all subinterfaces to inherit the default bandwidth of the main interface, regardless of the configured bandwidth. If a bandwidth is not configured on a subinterface, and you use the bandwidth inherit command, all subinterfaces will inherit the current bandwidth of the main interface. If you configure a new bandwidth on the main interface, all subinterfaces will use this new value.
If you do not configure a bandwidth on the subinterface and you configure the bandwidth inherit kbps command on the main interface, the subinterfaces will inherit the specified bandwidth.
In all cases, if an interface has an explicit bandwidth setting configured, then that interface will use that setting, regardless of whether or not the bandwidth inheritance setting is in effect.
Examples
The following example shows how to set the full bandwidth for DS3 transmissions:
Router(config)# interface serial 0Router(config-if)# bandwidth 44736Related Commands
show interfaces
Displays statistics for all interfaces configured on the router.
bert abort
To end a bit error rate testing session, use the bert abort command in privileged EXEC mode.
bert abort
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
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
Use the bert abort command to cancel bit error rate testing on each port of the Cisco AS5300 router.
The bit error rate test (BERT) feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern.
Examples
The following is sample output from the bert abort command when no bit error rate test is running:
Router# bert abortRouter#17:53:33: There is no BERT Test running ....The following is sample output from the bert abort command when a bit error rate test is running:
Router# bert abortDo you really want to abort the current BERT [confirm] Y17:56:56: %BERT-6-BERT_RESULTS: Controller T1 0 Profile default : The Test wasaborted by UserRelated Commands
Starts a bit error rate test for a particular port.
Sets up various bit error rate testing profiles.
bert controller
To start a bit error rate test (BERT) for a particular port, use the bert controller command in privileged EXEC mode.
bert controller [type-controller] {last-controller | profile [number | default]}
Syntax Description
Defaults
number: 0
Command Modes
Privileged EXEC
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
Use the bert controller command to start a bit error rate test for a particular port on a Cisco AS5300 router.
Quality Testing
The BERT feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern.
E1 Controllers
The E1 controller cannot be set in loopback mode from the Cisco AS5300. For the bert controller command to work correctly with the E1 controller, the controller must be configured as a channel group or channel-associated signaling (CAS) and the line must be configured as a remote loop from the switch side of the link.
Examples
The following is sample output from the bert controller command:
Router# bert controller T1 profile defaultPress <Return> to start the BERT [confirm] Y17:55:34: %BERT-6-BERT_START: Starting BERT on Interface 0 with Profile defaultData in current interval (10 seconds elapsed):0 Line Code Violations, 0 Path Code Violations0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail SecsTable 1 describes the significant fields shown in the display.
Related Commands
Aborts a bit error rate testing session.
Sets up various bit error rate testing profiles.
bert pattern (T1/E1)
To enable a bit error rate test (BERT) pattern on a T1 or E1 line, use the bert pattern command in controller configuration mode. To disable a BER test pattern, use the no form of this command.
bert pattern {2^23 | 2^20 | 2^20-QRSS | 2^15 | 2^11 | 1s | 0s | alt-0-1} interval time
no bert pattern {2^23 | 2^20 | 2^20-QRSS | 2^15 | 2^11 | 1s | 0s | alt-0-1} interval time
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
BER testing is supported on each of the T1 or E1 links, is done only over an unframed T1 or E1 signal, and is run on only one port at a time.
To view the BER test results, use the show controllers atm EXEC command. The BERT results include the following information:
•
•
•
•
•
•
When the T1 or E1 line has a BER test running, the line state is DOWN and the status field shows the current/last result of the test.
The bert pattern command is not written to NVRAM because this command is only used to test the T1 or E1 line for a short predefined interval, and to avoid accidentally saving the command.
Examples
The following example shows how to run a BERT pattern of all zeros on a Cisco 7200 series router for 30 minutes on the T1 controller in slot 1:
Router(config)# controller T1 1/0Router(config-if)# bert pattern 0s interval 30Related Commands
show controllers atm
Displays information about T1/E1 links in Cisco 7100 series routers, Cisco 7200 series routers, and Cisco 7500 series routers.
bert pattern (T3/E3)
To enable a bit error rate test (BERT) pattern on a T3 or E3 controller, use the bert pattern command in controller configuration mode. To disable a BER test pattern, use the no form of this command.
bert pattern {2^23 | 2^20 | 2^15 | 1s | 0s | alt-0-1} interval time
no bert pattern
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
BER testing is supported on T3/E3 links and is done only over framed T3 or E3 signals, unless E3 framing is in bypass mode.
To display the BER test results, use the show controllers t3 or show controllers e3 EXEC command. The BER test results include the following information:
•
•
•
•
•
•
When the T3 or E3 line has a BER test running, the line state is DOWN and the status field shows the current or last result of the test.
The bert pattern command is not written to NVRAM because this command is used only to test the T3 or E3 line for a short predefined interval, and to avoid accidentally saving the command.
Examples
The following example shows how to run a BERT pattern of all zeros for 30 minutes on the T3 controller in slot 1:
Router(config)# controller T3 1/0Router(config-if)# bert pattern 0s interval 30Related Commands
show controllers e3
Displays information about E3 controllers.
show controllers t3
Displays information about T3 controllers.
bert profile
To set up various bit error rate testing profiles, use the bert profile command in global configuration mode. To disable the particular bit error rate test (BERT) profile indicated by profile number, use the no form of this command.
bert profile number pattern pattern threshold threshold error-injection err-inj duration time
no bert profile number pattern pattern threshold threshold error-injection err-inj duration time
Syntax Description
Defaults
The default profile created internally by the system has parameters that cannot be changed. This profile has been defined so that you can execute BERT on a line without having to configure a new profile. The default profile is displayed when the running configuration is displayed and is not stored in NVRAM:
bert profile number pattern 220-0151QRSS threshold 10^-6 error-injection none duration 10
Command Modes
Global 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
Use the bert profile command to set up bit error rate testing profiles for the Cisco AS5300 router.
The bit error rate test (BERT) feature enables you to test the quality of the connected PRI links by direct comparison of a pseudorandom or repetitive test pattern with an identical locally generated test pattern. A BERT profile is a set of parameters related to a BERT test and is stored as part of the configuration in NVRAM. You can define up to 15 BERT profiles on the system. By setting up the BERT profiles in this way, you do not have to enter the parameters each time you want to run a BERT—just select the number of the BERT profile that you want to run.
Examples
The following example shows a configured BERT profile number 1 to have a 0s test pattern, with a 10-2 threshold, no error injection, and a duration of 125 minutes:
Router(config)# bert profile 1 pattern 0s threshold 10^-2 error-injection none duration 125Related Commands
Aborts a bit error rate testing session.
Starts a bit error rate test for a particular port.
cablelength
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
224 feet for a CT3IP interface processor and Clear Channel T3/E3 network module
49 feet for PA-T3 and PA-2T3 port adaptersCommand Modes
Controller configuration
Command History
Usage Guidelines
The default cable length of 224 feet is used by the CT3IP interface processor and the Clear Channel T3/E3 network module.
The default cable length of 49 feet is used by the PA-T3 and PA-2T3 port adapters.
Note
Examples
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 300cablelength (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
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.
carrier-delay
To set the carrier delay on a serial 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.
carrier-delay [seconds | msec milliseconds]
no carrier-delay [seconds | msec milliseconds]
Syntax Description
seconds
(Optional) Time, in seconds, to wait for the system to change states. The range is from 0 to 60. The default is 2.
msec milliseconds
(Optional) Time, in milliseconds. The default is 50.
Defaults
seconds: 2
milliseconds: 50Command Modes
Interface configuration
Command History
Usage Guidelines
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 switch 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.
Examples
The following example shows how to change the carrier delay to 5 seconds:
Router(config)# interface serial 0Router(config-if)# carrier-delay 5channel-group (EtherChannel)
To assign a Fast Ethernet 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.
Cisco 2600 Series, Cisco 3600 Series, and Cisco 3700 Series Routers
channel-group port-channel-number mode on
no channel-group
Cisco Catalyst Switches
channel-group port-channel-number mode {on | auto [non-silent] | desirable [non-silent]}
no channel-group
Syntax Description
Defaults
No channel groups are assigned.
Command Modes
Interface configuration
Command History
Usage Guidelines
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 port-channel-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.
Caution
Examples
The following example shows how to add EtherChannel interface 1/0 to the EtherChannel group specified by port-channel 1:
Router(config-if)# channel-group 1 mode on
Related Commands
interface port-channel
Accesses or creates the IDB port channel.
show interfaces port-channel
Displays statistics for all interfaces configured.
channel-group (Fast EtherChannel)
To assign a Fast Ethernet interface to a Fast EtherChannel group, use the channel-group command in interface configuration mode. To remove a Fast Ethernet interface from a Fast EtherChannel group, use the no form of this command.
channel-group channel-number
no channel-group channel-number
Syntax Description
channel-number
Port-channel number previously assigned to the port-channel interface using the interface port-channel global configuration command. The range is from 1 to 4.
Defaults
No channel group is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
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
To display information about the Fast EtherChannel, use the show interfaces port-channel EXEC command.
Examples
The following example shows how to add 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/0/Router(config-if)# channel-group 1Related Commands
channelized
To configure the T3 controller for channelized mode, use the channelized command in configuration controller 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
The T3 controller is channelized.
Channelized: maximum transmission unit (MTU) size is set to 1500.
Unchannelized: MTU size is set to 4470.Command Modes
Configuration controller
Command History
Usage Guidelines
Use the no channelized configuration controller 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 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.
Examples
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^Zclear 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 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 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
Syntax Description
interface-type
(Optional) Specifies the interface type; one of the keywords listed in Table 2.
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.
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command clears all the current interface counters from the interface unless the optional arguments type and number are specified to clear only a specific interface type (serial, Ethernet, Token Ring, and so on). Table 2 lists the command keywords and their descriptions.
Note
Protocol (SNMP), but only those seen with the show interface EXEC 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.
Examples
The following example clears all interface counters:
Router# clear countersThe following example clears 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 clears 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 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 IPC 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 privileged EXEC command.
Examples
The following example shows how to clear the DSIP tracing counters (including data, control, and IPC counters):
Router# clear dsip tracingRelated 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 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 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
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 3.
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 3 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#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 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 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
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.
clock rate
To configure the clock rate for the hardware connections on serial interfaces such as network interface modules (NIMs) and interface processors to an acceptable bit rate, use the clock rate command in interface configuration mode. To remove the clock rate if you change the interface from a DCE to a DTE device, use the no form of this command. Using the no form of this command on a DCE interface sets the clock rate to the hardware-dependent default value.
clock rate bps
no clock rate
Syntax Description
Defaults
No clock rate is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Cable Length
Be aware that the fastest speeds might not work if your cable is too long, and that speeds faster than 148,000 bits per second are too fast for EIA/TIA-232 signaling. It is recommended that you only use the synchronous serial EIA/TIA-232 signal at speeds up to 64,000 bits per second. To permit a faster speed, use EIA/TIA-449 or V.35.
Synchronous Serial Port Adapters
For the synchronous serial port adapters (PA-8T-V35, PA-8T-X21, PA-8T-232, and PA-4T+) on Cisco 7200 series routers, and on second-generation Versatile Interface Processors (VIP2s) in Cisco 7500 series routers, the clock rate you enter is rounded (if needed) to the nearest value that your hardware can support. To display the clock rate value for the port adapter, use the show running-config command.
If you plan to netboot your router over a synchronous serial port adapter interface and have a boot image prior to Cisco IOS Release 11.1(9)CA that does not support nonstandard (rounded) clock rates for the port adapters, you must use one of the following standard clock rates:
•
•
•
•
•
•
•
•
Examples
The following example shows how to set the clock rate on the first serial interface to 64,000 bps:
Router(config)# interface serial 0Router(config-if)# clock rate 64000The following example shows how to set the clock rate on a synchronous serial port adapter in slot 5, port 0 to 1,234,567 bps. In this example, the clock rate is adjusted to 1,151,526 bps.
Router(config)# interface serial 5/0Router(config-if)# clock rate 1234567%clock rate rounded to nearest value that your hardware can support.The following example shows how to determine the exact clock rate that the serial interface was rounded to by using the show running-config command.
Router# show running-configBuilding configuration......!interface Serial5/0no ip addressclock rate 1151526!...clock rate line
To configure the line clock rate for serial ports 0 or 1 in DTE mode, use the clock rate line command in interface configuration mode. To cancel the clock rate line value, use the no form of this command.
clock rate line rate
no clock rate line rate
Syntax Description
Defaults
No clock rate is set.
Command Modes
Interface configuration
Command History
11.3(1)MA
This command was introduced on the Cisco MC3810 multiservice access concentrator.
Usage Guidelines
This command specifies the rate of the incoming clock so that the appropriate internal clock scaling can be performed.
To configure the clock rate for a serial port in DTE mode, use the clock rate network-clock command.
Examples
The following example show how to configure the clock rate on serial 1 in DTE mode:
Router(config)# interface serial 1Router(config-if)# clock rate line 2048Related Commands
clock rate network-clock
To configure the network clock rate (speed) for serial ports 0 or 1 in DCE mode, use the clock rate network-clock command in interface configuration mode. To cancel the network clock rate value, use the no form of this command.
clock rate network-clock rate
no clock rate network-clock rate
Syntax Description
rate
Network clock rate, in kbps per second. The range is from 56 to 2048. The value entered should be a multiple of the value set for the network-clock base-rate command. There is no default rate.
Defaults
No clock rate is set.
Command Modes
Interface configuration
Command History
11.3(1)MA
This command was introduced on the Cisco MC3810 multiservice access concentrator.
Usage Guidelines
This command uses a synchronized clock on the serial port. The use of this command allows the clock on the serial port to be synchronized with the clock source of controller T1 0.
To configure the clock rate for a serial port in DTE mode, use the clock rate line command.
Examples
The following example shows how to configure the clock rate on serial port 1 in DCE mode:
Router(config)# interface serial 1Router(config-if)# clock rate network-clock 2048Related Commands
clock source (controller)
To set the T1-line clock source for the Multichannel Interface Processor (MIP) in the Cisco 7200 series and Cisco 7500 series, a T3 interface, or a PA-T3 serial port adapter, use the clock source command in controller configuration mode. To restore the clock source to its default setting, use the no form of this command.
clock source {line {primary | secondary} | internal}
no clock source
Syntax Description
Defaults
The default primary TDM clock source is from the T0 controller.
The default secondary TDM clock source is from the T1 controller.
The default clock for the interface's transmitted data is from a clock recovered from the line's receive data stream from the PA-T3 serial port adapter.Command Modes
Controller configuration
Command History
10.3
This command was introduced.
11.1 CA
This command was modified to include the T3 serial port adapter and PA-T3 serial port adapter.
Usage Guidelines
This command applies to a Cisco 4000, Cisco 7000 series, Cisco 7200 series, or Cisco 7500 series router. A T3 interface on a PA-T3 serial port adapter can clock its transmitted data either from its internal clock or from a clock recovered from the line's receive data stream.
To use the clocking coming in from a T1 line, configure the clock source line primary command on the controller that has the most reliable clocking. Configure the clock source line secondary command on the controller that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Examples
The following example shows how to configure the Cisco AS5300 to use the T0 controller as the primary clocking source and the T1 controller as the secondary clocking source:
AS5200(config)# controller t1 0AS5200(config-controller)# clock source line primaryAS5200(config-controller)# exitAS5200(config)# controller t1 1AS5200(config-controller)# clock source line secondaryRelated Commands
framing
Selects the frame type for the T1 or E1 data line.
linecode
Selects the line code type for T1 or E1 line.
clock source (CT3IP)
To specify where the clock source is obtained for use by the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the clock source command in controller configuration mode. To restore the default clock source, use the no form of this command.
clock source {internal | line | loop-timed}
no clock source
Syntax Description
Defaults
The internal clock source is used.
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the clock source command, the default internal clock source is used by the CT3IP.
You can also set the clock source for each T1 channel by using the t1 clock source controller configuration command.
Note
Examples
The following example sets the clock source for the CT3IP to line:
Router(config)# controller t3 9/0/0Router(config-controller)# clock source lineRelated Commands
clock source (interface)
To control the clock from which a G.703-E1 interface, an E1-G.703/G.704 serial port adapter, or a PA-E3 serial port adapter clocks its transmitted data, use the clock source command in interface configuration mode. To restore the default clock source, use the no form of this command.
Cisco 7000, Cisco 7200, and Cisco 7500 Series
clock source {line | internal}
no clock source
Cisco AS5300 Access Servers
clock source {line {primary | secondary} | internal}
no clock source line {primary | secondary}
Syntax Description
Defaults
Cisco 7000, Cisco 7200, and Cisco 7500 Series
The clock source is obtained from the receive data stream of the line.
Cisco AS5300 Access Servers
The primary TDM clock source is from the T0 controller.
The secondary TDM clock source is from the T1 controller.Command Modes
Interface configuration
Command History
Usage Guidelines
Cisco 7000, Cisco 7200, and Cisco 7500 Series
A G.703-E1 interface, E1-G.703/G.704 serial port adapter, or a PA-E3 serial port adapter can clock its transmitted data from either its internal clock or from a clock recovered from the line's receive data stream.
Cisco AS5300 Access Servers
To use the clocking coming in from a T1 line, configure the clock source line primary command on the controller that has the most reliable clocking. Configure the clock source line secondary command on the controller that has the next best known clocking. With this configuration, the primary line clocking is backed up to the secondary line if the primary clocking shuts down.
Examples
Cisco 7000, Cisco 7200, and Cisco 7500 Series
The following example shows how to configure the G.703-E1 interface to clock its transmitted data from its internal clock:
Router(config)# interface serial 0/1Router(config-if)# clock source internalCisco AS5300 Access Servers
The following example shows how to configure the Cisco AS5300 to use serial interface 1/0 as the primary clocking source and the serial interface 2/0 as the secondary clocking source:
AS5300(config)# interface serial 1/0AS5300(config-if)# clock source line primaryAS5300(config-if)# exitAS5300(config)# interface serial 2/0AS5300(config-if)# clock source line secondaryThe following example shows how to specify the T3 interface to clock its transmitted data from its internal clock:
Router(config)# interface serial 1/0Router(config-if)# clock source internalclock source (J1 controller)
To configure the clock source for a J1 controller, use the clock source command in controller configuration mode. To restore the clock source to its default setting, use the no form of this command.
clock source {line | internal}
no clock source
Syntax Description
Defaults
Clock source is line for the J1 controller.
Command Modes
Controller configuration
Command History
11.1 T
This command was introduced.
12.2(8)T
The command was introduced as a J1 controller configuration command for the Cisco 2600 and Cisco 3600 series.
Usage Guidelines
If multiple network modules are present in the router, then each J1 controller must be given a separate priority by configuration of the network-clock-select command. The controller having the highest priority will drive the internal clock.
Examples
The following example configures the clock source for line:
Router(config)# controller j1 3/0Router(config-controller)# clock source lineRelated Commands
clock source (SONET controller)
To specify the clock source of a SONET controller, use the clock source command in controller configuration mode. To restore the clock source to its default setting, use the no form of this command.
clock source {internal | line | loop}
no clock source
Syntax Description
Defaults
Internal
Command Modes
Controller configuration
Command History
10.3
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Examples
The following example shows how to specify line timing as the clock source on a SONET controller of an STM-1 card in physical slot number 2 on a Cisco AS5850:
Router(config)# controller sonet 2/0Router(config-controller)# clock source lineclock source (T1/E1 controller)
To set clocking for individual T1 or E1 links, use the clock source command in controller configuration mode. To return to the default, use the no form of this command.
clock source {line [primary] | internal | free-running}
no clock source
Syntax Description
Defaults
line
Command Modes
Controller configuration
Command History
Usage Guidelines
For a detailed discussion of clock sources on individual ports, see the "Clock Sources on Digital T1/E1 Voice Ports" section in the "Voice Port Configuration" chapter in the Cisco IOS Voice Configuration Library.
Examples
The following example shows the router providing clock source to two controllers:
controller E1 1/0framing crc4linecoding hdb3clock source internalds0-group timeslots 1-15 type e&m-wink-start!controller E1 1/1framing esflinecoding b8zsclock source internalds0-group timeslots 1-15 type e&m-wink-startThe following example shows the digital voice hardware receiving clocking for the PLL from E1 1/0 and using this clock as a reference to clock E1 1/1. If controller E1 1/0 fails, the PLL internally generates the clock reference to drive E1 1/1.
controller E1 1/0framing crc4linecoding hdb3clock source lineds0-group timeslots 1-15 type e&m-wink-start!controller E1 1/1framing crc4linecoding hdb3clock source internalds0-group timeslots 1-15 type e&m-wink-startRelated Commands
controller
Configures a T1 or E1 controller and enters controller configuration mode.
clock source (T1/E1 interface)
To configure the clock source of a DS1 link, use the clock source command in interface configuration or ATM interface configuration mode. To restore the default line setting, use the no form of this command.
clock source {line | internal | loop-timed}
no clock source
Syntax Description
Defaults
line
Command Modes
Interface configuration
ATM interface configuration for the Cisco 2600 and Cisco 3600 series routers.Command History
Usage Guidelines
This command sets clocking for individual T1/E1 links.
Make sure that you specify the clock source correctly for each link, even if you are planning to specify that a certain link will provide clocking for all the links in an IMA group. Because links may be taken in and out of service, requiring that the system select another link for common clocking, any link in an IMA group may provide the common clock.
If the ATM interface is part of an IMA group, you can use the loop-timed keyword to specify that the clock source is the same as the IMA group clock source.
Examples
On a Cisco 2600 or Cisco 3600 series router, the following example specifies an internal clock source for the link:
Router(config)# interface atm 0/2Router(config-if)# clock source internalRelated Commands
clock source (T3/E3 controller)
To specify where the clock source is obtained for use by a T3 or E3 controller, use the clock source command in controller configuration mode. To restore the default clock source, use the no form of this command.
clock source {internal | line}
no clock source
Syntax Description
internal
Specifies that the internal clock source is used. This is the default for T3.
line
Specifies that the network clock source is used. This is the default for E3.
Defaults
The internal clock source is used for T3 controllers.
The line clock source is used for E3 controllers.Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the clock source command, the default clock source is used.
Configure the clock source line command if your telephone company or the remote data service unit provides the master clock of the T3 or E3 connection.
Configure the clock source internal command if your router provides the master clock of the T3 or E3 connection.
Note
Examples
The following example shows how to set the clock source to line:
Router(config)# controller t3 1/0Router(config-controller)# clock source lineRelated Commands
controller
Configures a T1 or E1 controller and enters controller configuration mode.
cmt connect
To start the processes that perform the connection management (CMT) function and to allow the ring on one fiber to be started, use the cmt connect command in user EXEC or privileged EXEC mode.
cmt connect [fddi [port | slot/port] [phy-a | phy-b]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
In normal operation, the FDDI interface is operational once the interface is connected and configured. The cmt connect command allows the operator to start the processes that perform the CMT function.
The cmt connect command is not needed in the normal operation of FDDI; this command is used mainly in interoperability tests.
This command does not have a no form. To stop the CMT processes, use the cmt disconnect command.
Examples
The following examples demonstrate use of the cmt connect command for starting the CMT processes on the FDDI ring.
The following command starts all FDDI interfaces:
Router# cmt connect fddiThe following command starts both fibers on FDDI interface unit 0:
Router# cmt connect fddi 0The following command on the Cisco 7200 series or Cisco 7500 series starts both fibers on FDDI interface unit 0:
Router# cmt connect fddi 1/0The following command starts only Physical Sublayer A on FDDI interface unit 0:
Router# cmt connect fddi 0 phy-aRelated Commands
cmt disconnect
To stop the processes that perform the connection management (CMT) function and to allow the ring on one fiber to be stopped, use the cmt disconnect command in user EXEC or privileged EXEC mode.
cmt disconnect [fddi [port | slot/port] [phy-a | phy-b]]
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
In normal operation, the FDDI interface is operational once the interface is connected and configured, and is turned on using the no shutdown command in interface configuration mode. The cmt disconnect command allows the operator to stop the processes that perform the CMT function and allow the ring on one fiber to be stopped.
The cmt disconnect command is not needed in the normal operation of FDDI; this command is used mainly in interoperability tests.
This command does not have a no form. To start the CMT processes, use the cmt connect command.
Examples
The following examples demonstrate use of the cmt disconnect command for stopping the CMT processes on the FDDI ring.
The following command stops all FDDI interfaces:
Router# cmt disconnect fddiThe following command stops both fibers on FDDI interface unit 0:
Router# cmt disconnect fddi 0The following command on the Cisco 7200 series or Cisco 7500 series stops both fibers on FDDI interface unit 0:
Router# cmt disconnect fddi 1/0The following command stops only Physical Sublayer A on the FDDI interface unit 0. This command causes the FDDI media to go into a wrapped state so that the ring will be broken.
Router# cmt disconnect fddi 0 phy-aThe following command on the Cisco 7500 series stops only Physical Sublayer A on FDDI interface unit 0 in slot 1. This command causes the FDDI media to go into a wrapped state so that the ring will be broken.
Router# cmt disconnect fddi 1/0 phy-aRelated Commands
compress
To configure software compression for Link Access Procedure, Balanced (LAPB), PPP, and High-Level Data Link Control (HDLC) encapsulations, use the compress command in interface configuration mode. To disable compression, use the no form of this command.
compress {predictor | stac}
no compress {predictor | stac}
Cisco VIP2 Cards
compress {predictor | stac [distributed | software]}
[no] compress {predictor | stac [distributed | software]}
Cisco 7200 Series and Cisco 7500 Series
compress {predictor | stac [csa slot | software]}
[no] compress {predictor | stac [csa slot | software]}
PPP Encapsulation
compress [predictor | stac | mppc [ignore-pfc]]
[no] compress [predictor | stac | mppc [ignore-pfc]]
Syntax Description
Defaults
Compression is disabled.
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
11.3 P
The following keywords were added:
•
•
•
11.3 T
The following keywords were added:
•
•
Note
Usage Guidelines
Point-to-Point Compression
Compression reduces the size of frames through lossless data compression. You can configure point-to-point software compression for all LAPB, PPP, and HDLC encapsulations. The compression algorithm used is a predictor algorithm (the RAND compression algorithm), which uses a compression dictionary to predict what the next character in the frame will be.
End-point devices must be configured to use the same compression method (predictor, Stacker or MPPC).
HDLC encapsulations supports the Stacker compression algorithm. PPP and LAPB encapsulations support both predictor and Stacker compression algorithms.
MPPC Compression
The compress command using the mppc and ignore-pfc options support compression between Cisco routers and access servers and Microsoft clients, such as Windows 95 and Windows NT. MPPC implements an LZ-based compression algorithm that uses a compression dictionary to compress PPP packets. The ignore-pfc keyword instructs the router to ignore the protocol field compression flag negotiated by LCP. For example, the standard protocol field value for IP is 0x0021 when compression is disabled and 0x21 when compression is enabled. When the ignore-pfc option is enabled, the router will continue to use the uncompressed value (0x0021). Using the ignore-pfc option is helpful for some asynchronous driver devices that use an uncompressed protocol field (0x0021), even though the pfc is negotiated between peers. If protocol rejects are displayed when the debug ppp negotiation command is enabled, setting the ignore-pfc option may remedy the problem.
HDLC Encapsulations
For HDLC encapsulations, you can specify a Stacker compression algorithm by using the stac keyword. PPP and LAPB encapsulations support both predictor and Stacker compression algorithms.
Public Data Network Connections
Compression requires that both ends of the serial link be configured to use compression. You should never enable compression for connections to a public data network.
Cisco 7200 and Cisco 7500 Series
Using CSA hardware compression on Cisco 7200 series routers and Cisco 7500 series routers removes the compression and decompression responsibilities from the VIP2 or the main processor installed in the router. By using the compress stac command, the router determines the fastest compression method available on the router.
On Cisco 7200 series routers and Cisco 7500 series routers, hardware compression on the compression service adapter (CSA) is supported for PPP links. When using hardware compression on Cisco 7200 series routers with multiple CSAs, you can optionally specify which CSA is used by the interface to perform compression. If no CSA is specified, the router determines which CSA is used. On Cisco 7500 series routers, the router uses the CSA on the same VIP2 as the interface.
System Performance
Caution
If the majority of your traffic is already compressed files, we recommend that you not use compression. If the files are already compressed, the additional processing time spent in attempting unsuccessfully to compress them again will slow system performance.
Table 4 provides general guidelines for deciding which compression type to select.
Software compression makes heavy demands on the router's processor. The maximum compressed serial line rate depends on the type of Cisco router that you are using and which compression algorithm you specify. Table 5 shows a summary of the compressed serial line rates for software compression. The maximums shown in Table 5 apply to the "combined" serial compressed load on the router. For example, a Cisco 4000 series router could handle four 64-kbps lines using Stacker compression or one 256-kbps line. These maximums also assume that there is very little processor load on the router aside from compression. Lower these numbers when the router is required to do other processor-intensive tasks.
Hardware compression can support a combined line rate of 16 Mbps.
Cisco recommends that you do not adjust the maximum transmission unit (MTU) for the serial interface and the LAPB maximum bits per frame (N1) parameter.
Note
Note
Examples
The following example enables hardware compression and PPP encapsulation on serial interface 3/1/0.
Router(config)# interface serial 3/1/0Router(config-if)# encapsulate pppRouter(config-if)# compress stacThe following example enables predictor compression on serial interface 0 for a LAPB link:
Router(config)# interface serial 0Router(config-if)# encapsulation lapbRouter(config-if)# compress predictorRouter(config-if)# mtu 1509Router(config-if)# lapb n1 12072The following example enables Stacker compression on serial interface 0 for a LAPB link. This example does not set the MTU size and the maximum bits per frame (N1); we recommend that you do not change those LAPB parameters for Stacker compression:
Router(config)# interface serial 0Router(config-if)# encapsulation lapbRouter(config-if)# compress predictorThe following example configures BRI interface 0 to perform MPPC:
Router(config)# interface BRI0Router(config-if)# ip unnumbered ethernet0Router(config-if)# encapsulation pppRouter(config-if)# isdn spid1 5551234Router(config-if)# dialer map ip 172.21.71.74 5551234Router(config-if)# dialer-group 1Router(config-if)# compress mppcThe following example configures asynchronous interface 1 to implement MPPC and ignore the protocol field compression flag negotiated by LCP:
Router(config)# interface async1Router(config-if)# ip unnumbered ethernet0Router(config-if)# encapsulation pppRouter(config-if)# async default routingRouter(config-if)# async dynamic routingRouter(config-if)# async mode interactiveRouter(config-if)# peer default ip address 172.21.71.74Router(config-if)# compress mppc ignore-pfcRelated Commands
compress mppc
To configure compression using the Microsoft Point-to-Point Compression (MPPC) algorithm on your data compression Advanced Interface Module (AIM) for the Cisco 2600 series router, use the compress mppc command in interface configuration mode. To disable MPPC compression, use the no form of this command.
compress mppc
no compress mppc
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The MPPC compression algorithm is used to exchange compressed information with a Microsoft NT remote access server.
When configuring PPP on a serial interface, you can use hardware compression on the data compression AIM daughter card for MPPC if one is installed; otherwise you can use software compression.
Examples
The following example shows how to configure the data compression AIM daughtercard for MPPC:
Router(config-if)# encapsulate pppRouter(config-if)# compress mppcRelated Commands
compress stac caim
To specify the hardware compression, use the compress stac caim command in interface configuration mode. To disable compression, use the no form of this command.
compress stac caim interface-number
no compress stac caim interface-number
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Hardware Compression
If the router contains a data compression Advanced Interface Module (CAIM), compression is performed in the CAIM hardware.
Using hardware compression in the AIM frees the main processor of the router for other tasks. You can also configure the router to use the Compression Port Module to perform compression by using the distributed option or to use the router's main processor by using the software option. If the Compression Port Module compression is performed in the main processor of the router.
Software Compression
If the CAIM is not available, compression is performed in the main processor of the router.
When compression is performed by the software installed in the router's main memory, system performance might be affected significantly. It is recommended that you disable compression in the main processor if the router CPU load exceeds 40 percent. To display the CPU load, use the show process cpu command in EXEC mode.
Examples
The following example specifies that hardware compression should be activated for CAIM interface 0:
Router(config-if)# encapsulation pppRouter(config-if)# compress stac caim 0Related Commands
controller
To configure a T1, E1, or J1 controller and enter controller configuration mode, use the controller command in global configuration mode.
Cisco 2600 and 3600 Series Routers
controller {t1 | e1 | j1} slot/port
Cisco 7200 Series and Cisco 7500 Series Routers
controller {t1 | e1} slot/port
Cisco AS5300 Access Servers
controller {t1 | e1} number
Cisco AS5800 Access Servers
controller t1 dial-shelf/slot/t3-port:t1-num
Syntax Description
Defaults
No T1, E1, or J1 controller is configured.
Command Modes
Global configuration
Command History
Usage Guidelines
T1 or E1 Fractional Data Lines
This command is used in configurations where the router or access server is intended to communicate with a T1 or E1 fractional data line. Additional parameters for the T1 or E1 line must be configured for the controller before the T1 or E1 circuits can be configured by means of the interface global configuration command.
To view the status of the controllers use the show controllers command.
Examples
Cisco 7500 Series Router As a T1 Controller
The following example configures the MIP in slot 4, port 0 of a Cisco 7500 series router as a T1 controller:
Router(config)# controller t1 4/0Router(config-controller)#Cisco AS5800 Access Server with Dial Shelf
The following example configures the T1 controller in shelf 1, slot 0, port 0:
Router(config)# controller t1 1/0/0:1Router(config-controller)#Cisco 3660 As a J1 Controller
The following example configures the Cisco IOS interface card in slot 3, port 0 of a Cisco 3660 as a J1 controller:
Router(config)# controller j1 3/0Router(config-controller)#Related Commands
controller e3
To configure an E3 controller and enter controller configuration mode, use the controller e3 command in global configuration mode.
controller e3 slot/port
Syntax Description
slot/port
Number of the slot and port being configured. Refer to the appropriate hardware manual for slot and port information. The slash mark is required.
Defaults
No E3 controller is configured.
Command Modes
Global configuration
Command History
Examples
The following example shows the E3 controller configured in slot 0, port 0:
Router(config)# controller e3 0/0Router(config-controller)#Related Commands
controller sonet
To configure a SONET controller and enter controller configuration mode, use the controller sonet command in global configuration mode.
controller sonet slot/port
Syntax Description
Defaults
port: 0
Command Modes
Global configuration
Command History
12.0(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
This command does not have a no form because the SONET controller is created automatically when the STM-1 trunk card is detected by the Cisco AS5850. Use this command to specify which slot number the STM-1 card is plugged into and to configure different attributes under controller configuration mode.
Examples
The following example shows how to specify that the SONET controller is in slot number 2:
Router(config)# controller sonet 2/0Router(config-controller)#Related Commands
controller t3
To configure the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers or the CT3 feature board in Cisco AS5800 access servers, use the controller t3 command in global configuration mode. To delete the defined controller, use the no form of this command.
Cisco 7500 Series
controller t3 slot/port-adapter/port
no controller t3 slot/port-adapter/port
Cisco AS5800 Access Server
controller t3 dial-shelf/slot/t3-port
no controller t3 dial-shelf/slot/t3-port
Syntax Description
Defaults
Cisco 7500 Series
No T3 controller is configured.
Cisco AS5800 Access Server
No default behavior or values.
Command Modes
Global configuration
Command History
11.3
This command was introduced.
12.0(3)T
This command was implemented on the Cisco AS5800 access server.
Usage Guidelines
This command is used to configure the CT3IP and the 28 T1 channels. After the T1 channels are configured, continue to configure each T1 channel as a serial interface by using the interface serial global configuration command
Examples
Cisco 7500 Series
The following example configures the CT3IP in slot 3:
Router(config)# controller t3 3/0/0Cisco AS5800 Access Server
The following example configures the T3 controller in shelf 3, slot 0, port 0 and T1 time slot 1:
Router(config)# controller t3 3/0/0Related Commands
crc
To set the length of the cyclic redundancy check (CRC) on a Fast Serial Interface Processor (FSIP) or HSSI Interface Processor (HIP) of the Cisco 7500 series routers or on a 4-port serial adapter of the Cisco 7200 series routers, use the crc command in interface configuration mode. To set the CRC length to 16 bits, use the no form of this command.
crc size
no crc
Syntax Description
Defaults
16 bits
Command Modes
Interface configuration
Command History
Usage Guidelines
All interfaces use a 16-bit CRC by default, but also support a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead. Both the sender and receiver must use the same setting.
CRC-16, the most widely used throughout the United States and Europe, is used extensively with WANs. CRC-32 is specified by IEEE 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.
Examples
The following example enables the 32-bit CRC on serial interface 3/0:
Router(config)# interface serial 3/0Router(config-if)# crc 32crc4
To enable generation of CRC4 (per ITU Recommendation G.704 and G.703) to improve data integrity, use the crc4 command in interface configuration mode. To disable this function, use the no form of this command.
crc4
no crc4
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
11.1 CA
This command was implemented on the Cisco 7200 series router and the E1-G.703/G.704 serial port adapter.
Usage Guidelines
This command applies to the Cisco 7200 series, Cisco 7000 series, and Cisco 7500 series routers. This command is supported on the Fast Serial Interface Processor (FSIP) and the E1-G.703/G.704 serial port adapter.
This command is useful for checking data integrity while operating in framed mode. CRC4 provides additional protection for a frame alignment signal under noisy conditions. For data transmission at E1 (2.048 Mbps), the G.704 standard suggests 4 bits CRC. Refer to CCITT Recommendation G.704 for a definition of CRC4.
You can also use the crc command to set the CRC size for the High-Level Data Link Control (HDLC) controllers.
Examples
The following example enables CRC4 generation on the E1-G.703/G.704 serial port adapter and also sets the CRC size to 32 bits:
Router(config)# interface serial 0/0Router(config-if)# crc 32Router(config-if)# crc4Related Commands
crc bits 5
To enable generation of CRC5 (per ITU Recommendation G.704 and G.703) to improve data integrity, use the crc bits 5 command in interface configuration mode. To disable this function, use the no form of this command.
crc bits 5
no crc bits 5
Syntax Description
This command has no arguments or keywords.
Defaults
CRC5 checking is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is available for the JT2 6.3-MHz serial port adapter (PA-2JT2) on the second-generation Versatile Interface Processor (VIP2), in Cisco 7500 series routers, and in Cisco 7000 series routers with the Cisco 7000 series Route Switch Processor (RSP7000) and the Cisco 7000 series Chassis Interface (RSP7000CI).
This command is useful for checking data integrity while operating in framed mode. CRC5 provides additional protection for a frame alignment signal under noisy conditions. For data transmission at JT2 (6.312 Mbps), the G.704 standard suggests 5 bits CRC. Refer to ITU Recommendation G.704 for a definition of CRC5.
You can also use the crc command to set the CRC size for the High-Level Data Link Control (HDLC) controllers.
Examples
The following example enables CRC5 generation on the PA-2JT2 port adapter and also sets the CRC size to 32 bits:
Router(config)# interface serial 0/0Router(config-if)# crc 32Router(config-if)# crc bits 5Related Commands
cut-through
To configure the interfaces on the PA-12E/2FE port adapter to use cut-through switching technology between interfaces within the same bridge group, use the cut-through command in interface configuration mode. To return each interface to store-and-forward switching, use the no form of this command.
cut-through [receive | transmit]
no cut-through
Syntax Description
receive
(Optional) Selects cut-through switching technology on received data.
transmit
(Optional) Selects cut-through switching technology on transmitted data.
Defaults
Store-and-forward switching technology (that is, no cut-through)
Command Modes
Interface configuration
Command History
Usage Guidelines
Cut-through mode allows switched packets to be transmitted after 64 bytes are received. The transmission of the packets can start before the end of the packet arrives. This reduces the time spent in the switch, but allows packets to be transmitted with bad cyclical redundancy checks (CRCs), because the transmission is initiated before the CRC is received or checked. Store-and-forward mode waits for the entire packet to be received before that packet is forwarded, but will check the CRC before starting transmission.
The PA-12E/2FE port adapter offloads Layer 2 switching from the host CPU by using store-and-forward or cut-through switching technology between interfaces within the same VLAN on the PA-12E/2FE port adapter. The PA-12E/2FE port adapter supports up to four VLANs (bridge groups).
Examples
The following example configures interface 3/0 for cut-through switching:
Router(config)# interface fastethernet 3/0Router(config-if)# bridge-group 10Router(config-if)# cut-throughRouter(config-if)# no shutdownRouter(config-if)# exit
