-
Cisco IOS Interface and Hardware Component Command Reference, Release 12.3 T
-
Introduction
-
Interface and Hardware Component Commands: A through C
-
Interface and Hardware Component Commands: D through H
-
Interface and Hardware Component Commands: I through L
-
int_m1gt_1
-
Interface and Hardware Component Commands: M through R
-
Interface and Hardware Component Commands: scramble through show chassis
-
Interface and Hardware Component Commands: show compress through show hub
-
Interface and Hardware Component Commands: show interfaces through show interfaces vg-anylan
-
Interface and Hardware Component Commands: show ipc through syscon source-interface
-
Interface and Hardware Component Commands: T through Y
-
Table Of Contents
Interface and Hardware Component Commands
apply (satellite initial configuration)
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.
analysis-module monitoring
To enable Network Analysis Module (NAM) packet monitoring on an interface, use the analysis-module monitoring command in interface configuration mode. To disable NAM packet monitoring, use the no form of this command.
analysis-module monitoring
no analysis-module monitoring
Syntax Description
This command has no arguments or keywords.
Defaults
NAM packet monitoring is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
When you enable NAM packet monitoring on an interface, Cisco Express Forwarding (CEF) sends an extra copy of each IP packet that is received or sent on that interface to the NAM through the analysis module interface on the router and then through the internal NM-NAM interface.
Note
Traffic sent through the internal NAM interface—and the router's analysis module interface—uses router resources such as CPU, SDRAM bandwidth, and backplane Peripheral Component
Interconnect (PCI) bandwidth. Therefore, Cisco recommends that you use the internal NAM interface
to monitor WAN interfaces and that you use the external NAM interface to monitor LAN interfaces.Examples
The following example shows how to enable NAM packet monitoring on a serial interface:
Router(config)# interface serial 0/0Router(config-if)# analysis-module monitoring
apply (satellite initial configuration)
To save new or changed satellite initial configuration parameters and to reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the apply command in satellite initial configuration mode.
apply
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration mode
Command History
Usage Guidelines
The apply command saves any new or changed satellite initial configuration parameters to the nonvolatile memory of the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), and initiates a network module software reset. Commands entered in satellite initial configuration mode do not appear in the router configuration.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module's nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Note
Examples
The following example shows what appears when you enter the apply command after changing some initial configuration parameters:
Router(sat-init-config)# applyApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router(sat-init-config)#The following example shows what appears when you enter the apply command when no parameters have been changed:
Router(sat-init-config)# apply% No new or changed parameters to apply.Router(sat-init-config)#Related Commands
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
aps manual sonet
Enables a POS interface as a protect interface.
aps working
Configures a POS interface as a working interface.
aps clear sonet
To remove all externally initiated SONET automatic protection switching (APS) commands configured on a Cisco AS5850, use the aps clear sonet command in privileged EXEC mode.
aps clear sonet slot/port
Syntax Description
slot
Slot number on an STM-1 trunk card.
/port
SONET port number on an STM-1 trunk card. The slash mark is required between the slot argument and the port argument.
Defaults
No APS switch commands are removed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the aps clear sonet command to remove any SONET APS commands, such as the aps force sonet command, that could switch the working fiber to the protect fiber on an STM-1 trunk card.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to remove all externally initiated SONET APS switch commands:
Router# aps clear sonet 1/0Related Commands
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
aps force sonet
To force a specified port to switch to the alternate port within a redundant pair unless a request of equal or higher priority is in effect, use the aps force sonet command in privileged EXEC mode.
aps force sonet slot/port from {protection | working}
Syntax Description
Defaults
No port is switched.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Forced is a defined APS request priority level. The request succeeds if no higher priority request (lockout is the only higher priority request) is posted. The aps force sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface on which you want to issue the aps force sonet command. The aps force sonet command has a higher priority than any of the signal failures or the aps manual sonet command.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to force the protect port in the SONET controller to become an active port:
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps force sonet 1/0 from workingRelated Commands
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
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
aps manual sonet
Enables a POS interface as a protect interface.
aps working
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
aps manual sonet
Enables a POS interface as a protect interface.
aps working
Configures a POS interface as a working interface.
aps lockout sonet
To prevent a working port from switching to a protect port unless a request of equal or higher priority is in effect, use the aps lockout sonet command in privileged EXEC mode.
aps lockout sonet slot/port
Syntax Description
slot
Slot number on an STM-1 trunk card.
/port
SONET port number on an STM-1 trunk card. The slash mark is required between the slot argument and the port argument.
Defaults
No lockout exists; that is, a working port is not prevented from switching to a protect port.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Lockout is defined as the highest APS request priority level.
The aps lockout sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface from which the protect port is to be locked out. When the specified port is locked out, SONET APS switching from the working port is not allowed.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to lock out SONET port 1/0 (prevents SONET APS switching to a protect interface if the working circuit becomes unavailable):
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps lockout sonet 1/0Related Commands
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 manual sonet
To manually switch to the alternate port within a redundant pair unless a request of equal or higher priority is in effect, use the aps manual sonet command in privileged EXEC mode.
aps manual sonet slot/port from {protection | working}
Syntax Description
Defaults
No port is switched.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the aps manual sonet command to manually switch the active port to the alternate port. For example, you can use this command when you need to perform maintenance on the working port.
Manual is a defined APS request priority level. The request succeeds if no higher priority request is posted. The aps manual sonet command does not persist after a system restart. The slot and port arguments indicate the SONET interface on which you want to issue the aps manual sonet command. The aps manual sonet command has a lower priority than any of the signal failures or the aps force sonet command.
For more information about APS priority requests, see the ITU-T G.841 standard.
This command applies to the Cisco AS5850 universal gateway only.
Examples
The following example shows how to manually switch the working port, SONET port 1/0, to the protect port:
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRouter# aps manual sonet 1/0 from workingRelated 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
interface from becoming the active circuit and disabling the working circuit when it is finally discovered.
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 protect (SONET)
To enable automatic protection switching (APS) on a SONET port in an STM-1 trunk card, use the aps protect command in controller configuration mode. To disable APS on the SONET port, use the no form of this command.
aps protect
no aps protect
Syntax Description
This command has no arguments or keywords.
Defaults
APS is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the aps protect command to enable APS on a protect SONET port as a working port if the working port becomes unavailable because of a fiber failure, degradation or loss of channel signal, or manual intervention.
Examples
The following example shows how to enable APS on SONET port 0/1 in an STM-1 trunk card.
Router# configure terminalRouter(config)# controller sonet 1/0Router(config-controller)# aps protectRouter(config-controller)# endRelated Commands
aps unidirectional
Configures a protect SONET port for unidirectional mode.
show controllers sonet
Displays information about SONET controllers.
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 controller configuration or 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
Controller configuration
Interface configurationCommand History
11.1 CC
This command was introduced.
12.3(11)T
Support for SONET APS using an STM-1 card was added on the Cisco AS5850.
Usage Guidelines
The aps unidirectional command is configured only on protect interfaces.
Use the aps unidirectional command when you must interoperate with SONET network equipment, add/drop multiplexors (ADMs) that supports unidirectional mode.
Note
happens automatically when the SONET network equipment is in bidirectional mode.Examples
The following example shows how to configure POS interface 3/0/0 for unidirectional mode on a Cisco 12000 series router:
Router# configure terminalRouter(config)# interface pos 3/0/0Router(config-if)# aps unidirectionalRouter(config-if)# aps protect 1 10.7.7.7Router(config-if)# endThe following example shows how to configure SONET port 0/0 for unidirectional mode on a Cisco AS5850 universal gateway using an STM-1 trunk card:
Router# configure terminalRouter(config)# controller sonet 0/0Router(config-controller)# aps protectRouter(config-controller)# aps unidirectionalRouter(config-controller)# 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
association
To configure an association between current node and a remote node, use the association command in interprocess communication (IPC) zone configuration mode. To disable this functionality, use the no form of this command.
association association-ID
no association association-ID
Syntax Description
association-ID
Association ID assignment. The value range is from 1 through 255. The association ID must be unique within a specific zone.
Command Default
No association between a current node and a remote node exists.
Command Modes
IPC zone configuration
Command History
Usage Guidelines
Use the association command to configure an association between current node and a remote node. There can be multiple associations within a zone.
Examples
The following example configures an association with an ID of 1:
Router(config-ipczone)# association 1Related Commands
ipc zone default
Enters IPC zone configuration mode.
show ipc
Displays IPC statistics.
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
no bandwidth
Syntax Description
kbps
Intended bandwidth, in kilobits per second. For a full bandwidth DS3 line, enter the value 44736.
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.
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
bert controller
Starts a bit error rate test for a particular port.
bert pattern (T1/E1)
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 with the profile set at the default for the bit rate:
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
bert abort
Aborts a bit error rate testing session.
bert pattern (T1/E1)
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
bert abort
Aborts a bit error rate testing session.
bert controller
Starts a bit error rate test for a particular port.
cable bundle
To configure a cable interface to belong to an interface bundle, use the cable bundle command in interface configuration mode. To delete a cable interface bundle definition, use the no form of this command.
cable bundle number [master]
no cable bundle number [master]
Syntax Description
number
Specifies the bundle identifier. Valid range is from 1 to 255.
master
(Optional) Defines the specified interface as the master.
Defaults
No cable interface bundle is defined.
Command Modes
Interface configuration
Command History
Usage Guidelines
You can configure up to four interface bundles. In each bundle, specify one interface as the master interface by using the optional master keyword.
Configure only an IP address on the master interface. If an IP address is configured and the interface is not specified as the master interface, any attempt to add an interface to a bundle is rejected.
Specify all generic IP networking information (such as IP address, routing protocols, and switching modes) on the bundle master interface. Do not specify generic IP networking information on bundle slave interfaces.
If you attempt to add an interface to a bundle as nonmaster interface and an IP address is assigned to this interface, the command will fail. You must remove the IP address configuration before you can add the interface to a bundle.
If you have configured an IP address on a bundled interface and the interface is not the master interface, a warning message appears.
Specify generic (not downstream or upstream related) cable interface configurations, such as source-verify or Address Resolution Protocol (ARP) handling, on the master interface. Do not specify generic configuration on nonmaster interfaces.
If you configure an interface as a part of a bundle and it is not the master interface, all generic cable configuration for this interface is removed. The master interface configuration will then apply to all interfaces in the bundle.
If you shut down or remove the master interface in a bundle, no data packets are sent to any of the interfaces in this bundle. Packets are still physically received from nonmaster interfaces that have not been shut down, but those packets will be discarded. Modems connected to those interfaces will not be disconnected immediately, but modems going online will not be able to obtain an IP address, download their configuration file, or renew their IP address assignment if the Dynamic Host Configuration Protocol (DHCP) lease expires.
If you shut down a slave interface, only this shut down interface is affected.
Examples
The following example shows how to configure interface 25 to be the master interface:
Router(config-if)# cable bundle 25 masterRouter(config-if)#07:28:17: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to down07:28:18: %UBR7200-5-UPDOWN: Interface Cable3/0 Port U0, changed state to upThe following example shows the error message that appears if you try to configure an interface with an IP address that is not the master interface:
Router(config-if)# cable bundle 5Please remove ip address config first then reenter this commandRelated Commands
show cable bundle
Displays the forwarding table for the specified interface bundle.
cable helper-address
To specify a destination address for User Datagram Protocol (UDP) broadcast Dynamic Host Configuration Protocol (DHCP) packets, use the cable helper-address command in interface configuration mode. To remove the specified destination address for UDP DHCP packets, use the no form of this command.
cable helper-address ip-address {cable-modem | host}
no cable helper-address ip-address {cable-modem | host}
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
If you specify a secondary interface address, the giaddr field in the DHCP requests will be sent to the primary address for DHCP requests received from cable modems, and to the secondary IP address for DHCP requests received from hosts.
Examples
The following example shows how to forward UDP broadcasts from cable modems to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 cable-modemThe following example shows how to forward UDP broadcasts from hosts to the DHCP server at 172.23.66.44:
Router(config-if)# cable helper-address 172.23.66.44 hostcablelength
To specify the distance of the cable from the routers to the network equipment, use the cablelength command in controller configuration mode. To restore the default cable length, use the no form of this command.
cablelength feet
no cablelength
Syntax Description
Defaults
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
ranges: 0 to 49 and 50 to 450. For example, entering 35 feet uses the 0 to 49 range. If you later
change the cable length to 40 feet, there is no change because 40 is still within the 0 to 49 range. However, if you change the cable length to 50, the 50 to 450 range is used. The actual number you
enter is stored in the configuration file.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
The cablelength long command can be used only on CSU interfaces.A pulse equalizer regenerates a signal that has been attenuated and filtered by a cable loss. Pulse equalization does not produce a simple gain, but it filters the signal to compensate for complex cable loss. A gain26 receiver gain compensates for a long cable length equivalent to 26 dB of loss, whereas a gain36 compensates for 36 dB of loss.
The lengthening or building out of a line is used to control far-end crosstalk. Line build-out attenuates the stronger signal from the customer installation transmitter so that the transmitting and receiving signals have similar amplitudes. A signal difference of less than 7.5 dB is ideal. Line build-out does not produce simple flat loss (also known as resistive flat loss). Instead, it simulates a cable loss of 7.5 dB, 15 dB, or 22.5 dB so that the resulting signal is handled properly by the receiving equalizer at the other end.
Cisco 2600 and Cisco 3600 Series Routers
This command is supported on T1 long-haul links only. If you enter the cablelength long command on a DSX-1 (short-haul) interface, the command is rejected.
The transmit attenuation value is best obtained by experimentation. If the signal received by the far-end equipment is too strong, reduce the transmit level by entering additional attenuation.
Examples
Cisco AS5800 and Cisco MC3810
The following example shows how to increase the receiver gain by 36 decibels and decreases the transmitting pulse by 15 decibels for a long cable on a Cisco AS5800:
AS5800(config)# controller t1 0AS5800(config-controller)# cablelength long gain36 -15dbThe following example shows how to configure the cable length for controller T1 0 on a Cisco MC3810 to a decibel pulse gain of 36 decibels and a decibel pulse rate of -22.5 decibels:
MC3810(config)# controller t1 0MC3810(config-controller)# cablelength long gain36 -22.5dbCisco 2600 and Cisco 3600 Series Routers
On a Cisco 2600 or Cisco 3600 series router, the following example shows how to specify a pulse gain of 36 decibels and a decibel pulse rate of -7.5 decibels:
Router(config)# interface atm 0/2Router(config-if)# cablelength long gain36 -7.5dbRelated Commands
cablelength short
To set a cable length of 655 feet or shorter for a DS1 link on the Cisco MC3810 or Cisco 2600 and Cisco 3600 series routers, use the cablelength short command in controller configuration or interface configuration mode. To delete the cablelength short value, use the no form of this command.
cablelength short length
no cablelength short
Syntax Description
Defaults
The default is 133 feet for the Cisco AS5200 access server, Cisco AS5800 universal access server, and Cisco MC3810 multiservice access concentrator.
There is no default cable length for the Cisco 2600 and Cisco 3600 series routers.
Command Modes
Controller configuration for the Cisco AS5200 access server, Cisco AS5800 universal access server, and Cisco MC3810 multiservice access concentrator.
Interface configuration for the Cisco 2600 and Cisco 3600 series routers.Command History
Usage Guidelines
Cisco AS5200 Access Server, Cisco AS5800 Universal Access Server, and Cisco MC3810 Multiservice Access Concentrator
On the Cisco MC3810, the cablelength short command is used to configure DSX-1 links when the cable length is 655 feet or less than 655 feet. On the Cisco MC3810, this command is supported on T1 controllers only.
Note
Cisco 2600 and Cisco 3600 Series Routers
This command is supported on T1 short-haul links only. If you enter the cablelength short command on a long-haul interface, the command is rejected.
To set cable lengths longer than 655 feet, use the cablelength long command.
This command is supported on T1 controllers only.
Cisco AS5200 Access Server, Cisco AS5800 Universal Access Server, and Cisco MC3810 Multiservice Access Concentrator
The following example shows how to set the cable length to 266 for the T1 controller in slot 1 on dial shelf 0:
Router# configure terminalRouter(config)# controller t1 1/1/0Router(config-controller)# cablelength short 266Router(config-controller)# endCisco 2600 and Cisco 3600 Series Routers
On a Cisco 2600 or Cisco 3600 series router, the following example shows how to specify a cable length from 0 to 133 feet:
Router(config)# interface atm 0/2Router(config-if)# cablelength short 133Related Commands
cablelength long
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 5cem
To enter circuit emulation (CEM) configuration mode, use the cem command in global configuration mode.
cem slot/port/channel
Syntax Description
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
Use this command to enter CEM configuration mode to allow the configuration of all CEM options.
Examples
The following example shows how to enter CEM configuration mode:
Router(config)# cem 1/2/0
Router(config-cem)#Related Commands
cem-group
To create a circuit emulation (CEM) channel from one or more time slots of a T1 or E1 line of an NM-CEM-4TE1 network module, use the cem-group command in controller configuration mode. To remove a CEM group and release the associated time slots, use the no form of this command.
cem-group group-number {unframed | timeslots time-slot-range [speed {56 | 64}]}
no cem-group group-number
Syntax Description
Defaults
No CEM groups are defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to create CEM channels on the T1 or E1 network module, NM-CEM-4TE1. A maximum of 64 channels may be created on an NM-CEM-4TE1.
Examples
The following example shows how to create circuit emulation group number 0 with a single CEM channel including all time slots and the framing structure of the line on an NM-CEM-4TE1.
Router(config-controller)# cem-group 0 unframedThe following example shows how to create circuit emulation channel number 6 with T1 channel time slots one through four, nine, and ten using all eight bits of each time slot on an NM-CEM-4TE1.
Router(config-controller)# cem-group 6 timeslots 1-4,9,10 speed 64Related Commands
channel-group (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
groups on the physical EtherChannel interfaces because loops will result.
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
Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces
because it creates loops. Also, you must disable spanning tree.
To display information about the Fast EtherChannel, use the show interfaces port-channel EXEC command.
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 cem
To clear circuit emulation (CEM) statistics, use the clear cem command in privileged EXEC mode.
clear cem {slot | slot/port/channel | all}
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
The following example shows how to clear CEM statistics for CEM channel number 10 on the card installed in slot 1, port 1.
Router# clear cem 1/1/10
Related Commands
clear controller
To reset the T1 or E1 controller, use the clear controller command in user EXEC or privileged EXEC mode.
Cisco 7200 Series and Cisco 7500 Series Routers
clear controller {t1 | e1} slot/port
Cisco AS5200 Series and Cisco AS5300 Series Routers
clear controller {t1 | e1} number
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example resets the T1 controller at slot 4, port 0 on a Cisco 7500 series router:
Router# clear controller t1 4/0The following example resets the E1 controller at NIM 0:
Router# clear controller e1 0Related Commands
controller
Configures a T1, E1, or J1 controller and enters controller configuration mode.
clear 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
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
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 hub
To reset and reinitialize the hub hardware connected to an interface of a Cisco 2505 or Cisco 2507 router, use the clear hub command in user EXEC or privileged EXEC mode.
clear hub ethernet number
Syntax Description
ethernet
Hub in front of an Ethernet interface.
number
Hub number to clear, starting with 0. Because there is only one hub, this number is 0.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example clears hub 0:
Router# clear hub ethernet 0Related Commands
hub
Enables and configures a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
clear hub counters
To set the hub counters on an interface of a Cisco 2505 or Cisco 2507 router to zero, use the clear hub counters command in user EXEC or privileged EXEC mode.
clear hub counters [ether number [port [end-port]]]
Syntax Descriptionn
Defaults
If no port numbers are specified, counters for all ports are cleared.
Command Modes
User EXEC
Privileged EXECCommand History
Examples
The following example shows how to clear the counters displayed by a show hub command for all ports on hub 0:
Router# clear hub counters ether 0Related Commands
show hub
Displays information about the hub (repeater) on an Ethernet interface of a Cisco 2505 or Cisco 2507 router.
clear interface
To reset the hardware logic on an interface, use the clear interface command in user EXEC or privileged EXEC mode.
clear interface type number [name-tag]
Cisco 7200 Series and Cisco 7500 Series with a Packet OC-3 Interface Processor
clear interface type slot/port
Cisco 7500 Series with Ports on VIP Cards
clear interface type slot/port-adapter/port
Cisco 7500 Series
clear interface type slot/port[:channel-group]
Cisco 7500 Series with a CT3IP Port Adapter
clear interface type slot/port-adapter/port[:t1-channel]
Syntax Description
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#02:49:52: rlm 1: [State_Up, rx UP_RECOVERED_MIN_TIMEOUT]02:49:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] requests activation02:49:52: rlm 1: [State_Switch, rx SWITCH_ACK] over link [10.1.1.1(Loopback1), 10.1.4.1]02:49:52: rlm 1: link [10.1.1.2(Loopback2), 10.1.4.2] is deactivated02:49:52: rlm 1: link [10.1.1.1(Loopback1), 10.1.4.1] is activatedRelated Commands
clear interface fastethernet
To reset the controller for a specified Fast Ethernet interface, use the clear interface fastethernet command in privileged EXEC mode.
Cisco 4500 and Cisco 4700 Series
clear interface fastethernet interface-number
Cisco 7200 and Cisco 7500 Series
clear interface fastethernet slot/port
Cisco 7500 Series with a VIP
clear interface fastethernet slot/port-adapter/port
Syntax Description
Command Modes
Privileged EXEC
Command History
Examples
Cisco 4500 Series
The following example resets the controller for Fast Ethernet interface 0 on a Cisco 4500:
Router# clear interface fastethernet 0Cisco 7200 and Cisco 7500 Series
The following example resets the controller for the Fast Ethernet interface located in slot 1, port 0 on a Cisco 7200 series router or Cisco 7500 series router:
Router# clear interface fastethernet 1/0Cisco 7500 Series with a VIP
The following example resets the controller for the Fast Ethernet interface located in slot 1, port adapter 0, port 0 on a Cisco 7500 series router with a virtual interface processor (VIP):
Router# clear interface fastethernet 1/0/0Related Commands
clear interface 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 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 rbscp
To reset and restart a Rate Based Satellite Control Protocol (RBSCP) tunnel, use the clear rbscp command in privileged EXEC mode.
clear rbscp [tunnel tunnel-number]
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The clear rbscp command resets the tunnel interface to its initial state and this clears RBSCP statistical information. Use this command for troubleshooting issues with RBSCP tunnels.
Examples
The following example shows how to clear the RBSCP statistics. A show rbscp statistics command is issued first to display the current RBSCP counters for tunnel interface 0. The clear rbscp command is then entered to reset and restart tunnel interface 0. All the counters for tunnel interface 0 are reset to zero. A final show rbscp statistics command is issued to show that all the counters, except those counters that show the packets sent since the clearing, are reset to zero.
Router# show rbscp statistics tunnel 0Tunnel0 is up, line protocol is upRBSCP protocol statistics:Init FWD-TSNs sent 15, received 11TUNNEL-UPs sent 10, received 5CLOSEDs sent 3, received 2TSNs sent 40, resent 2, lost by sender 1TSNs received 36 (duplicates 2)FWD-TSNs sent 144 (heartbeats 2)FWD-TSNs received 120 (ignored 1)FWD-TSNs caused 3 packet drops, 0 whole window dropsSACKs sent 10, received 6 (ignored 1)Recovered with RTX 1Received with delay 2Most released at once 5Failed sends into the: tunnel 1, network 0Dropped due to: excess delay 0, tmit queue full 0Max on any queue: num packets: 12, num bytes: 0Max outstanding: 0Router# clear rbscp tunnel 0Tunnel0: cleared statisticsRouter# show rbscp statistics tunnel 0Tunnel0 is up, line protocol is upRBSCP protocol statistics:Init FWD-TSNs sent 0, received 0TUNNEL-UPs sent 0, received 0CLOSEDs sent 0, received 0TSNs sent 0, resent 0, lost by sender 0TSNs received 0 (duplicates 0)FWD-TSNs sent 26 (heartbeats 0)FWD-TSNs received 0 (ignored 0)FWD-TSNs caused 0 packet drops, 0 whole window dropsSACKs sent 0, received 0 (ignored 0)Recovered with RTX 0Received with delay 0Most released at once 0Failed sends into the: tunnel 0, network 0Dropped due to: excess delay 0, tmit queue full 0Max on any queue: num packets: 0, num bytes: 0Max outstanding: 0Related Commands
clear service-module serial
To reset an integrated CSU/DSU, use the clear service-module serial command in privileged EXEC mode.
clear service-module serial number
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command only in severe circumstances (for example, when the router is not responding to a CSU/DSU configuration command).
This command terminates all DTE and line loopbacks that are locally or remotely configured. It also interrupts data transmission through the router for up to 15 seconds. The software performs an automatic software reset in case of two consecutive configuration failures.
The CSU/DSU module is not reset with the clear interface command.
Caution
refrain from using this command. This command erases the router's past CSU/DSU performance statistics. To clear only the CSU/DSU performance statistics, issue the clear counters command.
Examples
The following example show how to reset the CSU/DSU on a router:
Router# clear service-module serial 0Related Commands
clear counters
Clears the interface counters.
test service-module
Performs self-tests on an integrated CSU/DSU serial interface module, such as a 4-wire, 56/64-kbps CSU/DSU.
clock mode
To configure the clock mode of a serial circuit emulation (CEM) channel, use the clock mode command in CEM configuration mode. To reset the clock mode to its default, use the no form of this command.
clock mode {normal | split}
no clock mode
Syntax Description
Defaults
The clock mode command defaults to normal mode.
Command Modes
CEM configuration
Command History
Usage Guidelines
This command applies only to serial ports.
Examples
The following example shows how to configure the CEM clock for normal mode.
Router(config-cem)# clock mode normal
Related Commands
clock rate (interface ATM)
To configure the clock rate between a WAN interface card (WIC) and the serial communication controllers (SCCs) that are used by the WIC, use the clock rate command in interface ATM configuration mode. To disable the clock rate setting, use the no form of this command.
clock rate [aal2 | aal5] clock-rate-value
no clock rate [aal2 | aal5] clock-rate-value
Syntax Description
Command Modes
Interface ATM configuration
Command History
Usage Guidelines
The communication between digital subscriber line (DSL) WICs and a host in a router occurs through a device called the SCC. If a host wants to forward data or send any control traffic to a DSL WIC, it uses SCCs. In the same way, if a DSL WIC wants to forward incoming data from a line to the host, it also uses SCCs. Each DSL WIC installed in the router uses two SCCs. One SCC (SCC-A) is used for AAL5 data traffic, and the other SCC (SCC-B) is used for AAL2 and control traffic. The speed at which the SCC transfers data between a host and a WIC depends on the clock rate with which it has been configured. You can configure this clock rate on the basis of the DSL line rate. Even though the DSL upstream and downstream line rate may vary, the clock rate between the SCC and the DSL WIC is the same for both the transmitting and receiving direction. That is, the communication between the SCC and the DSL WIC is synchronous. Therefore, you need to configure only one clock rate for an SCC that will be used for both transmitting and receiving between an SCC and a DSL WIC.
We always recommend that you configure the SCC clock rate slightly higher than the DSL line rate to accommodate overhead between the SCC and the DSL WIC. For an asynchronous DSL WIC (for example, ADSL), the SCC clock rate depends on either the downstream or the upstream line rate, whichever is the maximum rate. For a synchronous DSL WIC (for example, G.SHDSL), the bandwidth for upstream and downstream is the same. Therefore, the SCC clock rate configuration can be based on either the upstream or the downstream line rate.
Because the maximum line rate for G.SHDSL is 2.312 Mbps, the default SCC clock rate of 2.6 Mbps for AAL5 and 1 Mbps for AAL2 should be sufficient. However, for ADSL, the clock rate may need to be configured on the basis of the current line rate. If AAL2 is used for voice traffic, the AAL2 SCC must be configured to the appropriate clock rate: 1 Mbps for ADSL and 2.6 Mbps for G.SHDSL.
The maximum data rate between an SCC and a DSL WIC depends primarily on the maximum clock rate that the SCC can support. For example, on the Cisco 2600 series mainboard, which supports two DSL WICs, the total SCC clock rate that can be configured for both WICs is 8 Mbps. Therefore, if only one DSL WIC is present on the mainboard, AAL5 and AAL2 clock rates can be configured to 7 Mbps and 1 Mbps, respectively. If two DSL WICs are supported on the mainboard, the total of 8 Mbps should be distributed among the four SCCs.
Network module SCCs also pose similar limitations. That is, on the Cisco 2600 series, the total clock rate for all four SCCs is 8 Mbps. The maximum AAL5 clock rate that may be configured on a network module is 5.3 Mbps. On the Cisco 1700 series, the maximum configurable SCC clock rate for both AAL5 and AAL2 is 8 Mbps.
If the clock rate is not configured, the SCC is reset to the default values.
The clock rate can be configured independently for each SCC. To verify the clock rate setting, use the show running-config command.
Examples
The following example shows how to set the clock rate to 2 Mbps for AAL5 and to 1.3 Mbps for AAL2 for a Cisco 2600 or Cisco 3600 series router:
Router (config)# interface atm1/0Router (config-if)# no ip addressRouter (config-if)# no atm ilmi-keepaliveRouter (config-if)# pvc 6/65Router (config-if)# clock rate aal5 2000000Router (config-if)# clock rate aal2 1300000Router (config-if)# vbr-nrt 640 640 128Router (config-if)# tx-ring-limit 3Related Commands
clock rate (interface serial)
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 {line | rate}
no clock rate
Syntax Description
Defaults
No clock rate is configured.
Command Modes
Interface configuration
Command History
Usage Guidelines
Using the no form of this command on a DCE interface sets the clock rate to the hardware-dependent default value.
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 use the synchronous serial EIA/TIA-232 signal at speeds up to 64,000 bits per second only. 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 that 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 boot from a network (TFTP) server 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 to use the network as the clock source:
Router(config)# interface serial 0Router(config-if)# clock rate lineThe 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!...Related 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 save interval
To preserve recent date and time information in NVRAM for when a Cisco IOS device without a battery-backed calendar is power-cycled or reloaded, use the clock save interval command in global configuration mode. To return to the default disabled state, use the no form of this command.
clock save interval hours
no clock save interval hours
Syntax Description
hours
Interval at which the time will be stored in NVRAM. Accepted intervals range from 8 to 24 hours.
Defaults
This function is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
The benefit of using this command is that upon returning from a system reload or power cycle, the system clock will be set to a time and date near the current time and date instead of being reset to the system default time and date. In the absence of better information, Cisco IOS devices will initially set their system clocks to epoch start, which will typically be midnight (UTC) March 1, 1993 or 2002.
When this command is entered, the date and time are saved to NVRAM at the interval specified by this command, and also during any shutdown process. When the system starts up, the system clock is set to the last time and date saved to NVRAM.
All Cisco IOS devices support Network Time Protocol (NTP) or Simple Network Time Protocol (SNTP) to learn the time from the network, and some Cisco IOS devices have built-in battery-backed clocks to maintain that time. The clock save interval command is for those Cisco IOS devices that do not have battery-backed clocks and need to know the time and date before they can start communicating with a network. Because the March 1 system default date will likely occur before the valid date of any recently issued certificate, communications attempted with almost any certificate will fail because it is not yet valid according to the local clock.
Saving the time at a 24-hour interval should work well for most networks, unless there is a certificate that maintains a shorter life span.
Being aware of the time and date is critical for networking devices, and it becomes an issue when communication to a network requires use of a time-based credential, such as a certificate that has start and end dates and times. NTP and SNTP are the proper ways to set the time of a network device. The clock save interval command is intended to complement use of NTP and SNTP, so this command is useful only when a certificate is required to initiate communication to an NTP server, and the Cisco IOS device does not have a battery-back hardware clock, but does have NVRAM.
The system time will only be saved to NVRAM when set by an authoritative source such as NTP or SNTP; the system will not save the time entered through the set clock command. Additionally, a clock is considered valid only when the following criteria apply:
•
•
Through a confluence of events, there is no means to authoritatively declare a user-entered time as valid unless the calendar (battery-backed date and time) is declared valid. Since there is no actual calendar in a system with this command, the clock calendar-valid command is unavailable, and therefore a user-entered time can never be considered authoritative on platforms without a battery-backed calendar. This state is intentional because a battery-backed clock continues to run, and an NVRAM clock will stay the same. And again, for these reasons the clock save interval command must complement the use of NTP and SNTP.
Examples
The following example shows how to configure a Cisco IOS device to save the time at 24-hour intervals:
Router(config)# clock save interval 24clock source (CEM)
To configure the clock source of a circuit emulation (CEM) network module port, use the clock source command in CEM configuration mode or controller configuration mode. To return to the default clock source, use the no form of this command.
Cisco NM-CEM-4SER
clock source {internal | loop | adaptive}
no clock source {internal | loop | adaptive}
Cisco NM-CEM-4TE1
clock source {internal | line | adaptive channel-number}
no clock source {internal | line | adaptive channel-number}
Syntax Description
Defaults
Cisco NM-CEM-4SER
The clock source defaults to internal.
Cisco NM-CEM-4TE1
The clock source defaults to line.
Command Modes
Cisco NM-CEM-4SER
CEM configuration
Cisco NM-CEM-4TE1
Controller configuration
Command History
Usage Guidelines
When clock source internal is specified, the clocks provided by the network module are derived from either of the following source:
•
•
When the adaptive keyword is specified, the clocks provided by the network module are derived from the same source as in the clock source internal case. However, the derived frequency is further adjusted up or down on the basis of the measured average fill of the egress dejitter buffer of the connection. If the dejitter buffer is perceived to be slowly filling, the frequency is adjusted slightly upward. If the dejitter buffer is perceived to be slowly depleting, the frequency is adjusted slightly downward.
Cisco NM-CEM-4SER
When the loop keyword is specified, the clock provided by the NM-CEM-4SER is the same as the clock provided to the NM-CEM-4SER from the attached CPE. The specification of clock source loop is only valid when the clock mode split command is specified. The clock mode command is used only during configuration of the NM-CEM-4SER.
Examples
The following example shows how to configure the clock source for the serial CEM network module, NM-CEM-4SER:
Router(config-cem)# clock source loopThe following example shows how to configure the clock source for the T1/E1 CEM network module, NM-CEM-4TE1:
Router(config-controller)# clock source adaptive 6Related Commands
cem
Enters circuit emulation configuration mode.
clock mode
Configures the clock mode on an NM-CEM-4SER network module.
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 | bits] | internal | free-running}
no clock source
Syntax Description
Defaults
The default is line.
Command Modes
Controller configuration
Command History
Usage Guidelines
For a detailed discussion of clock sources on individual ports, refer to "Clock Sources on Digital T1/E1 Voice Ports" in the "Configuring Voice Ports" chapter of the Cisco IOS Voice, Video, and Fax Configuration Guide, Release 12.3.
Examples
The following example shows the router providing clock source to two controllers:
Router(config)# controller E1 1/0Router(config-controller)# framing crcRouter(config-controller)# linecoding hdb3Router(config-controller)# clock source internalRouter(config-controller)# ds0-group timeslots 1-15 type e&m-wink-start!Router(config)# controller E1 1/1Router(config-controller)# framing esfRouter(config-controller)# linecoding b8zsRouter(config-controller)# clock source internalRouter(config-controller)# ds0-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.
Router(config)# controller E1 1/0Router(config-controller)# framing crcRouter(config-controller)# linecoding hdb3Router(config-controller)# clock source lineRouter(config-controller)# ds0-group timeslots 1-15 type e&m-wink-start!Router(config)# controller E1 1/1Router(config-controller)# framing crc4Router(config-controller)# linecoding hdb3Router(config-controller)# clock source internalRouter(config-controller)# ds0-group timeslots 1-15 type e&m-wink-startThe following example shows the router being configured to receive clocking from the BITS.
Router(config)# network-clock-participate slot 1Router(config)# network-clock-select 1 E1 1/1Router(config)# controller E1 1/1Router(config-controller)# clock source line bitsRelated 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
</
