-
Cisco IOS Interface and Hardware Component Command Reference
-
Introduction
-
A through B
-
cable bundle through clock mode
-
clock rate through cut-through
-
D through E
-
F through H
-
I through K
-
l2 vfi manual through loopback (PA-MC-8TE1 + port adapter)
-
loopback (T1 interface) through nrzi-encoding
-
O through R
-
scramble through service-module t1 lbo
-
service-module t1 linecode through show controllers satellite
-
show controllers serial through show hw-module slot proc cpu
-
show hw-module slot tech-support through show interfaces vg-anylan
-
show interfaces vlan mapping through show scp
-
show service-module serial through standby port
-
squelch through system jumbomtu
-
t1 through tug-2 e1 unframed
-
tunnel bandwidth through yellow
-
Table Of Contents
fabric error-recovery fabric-switchover (virtual switch)
fabric switching-mode force bus-mode
facility-alarm critical exceed-action shutdown
half-duplex controlled-carrier
hw-module interface als restart
hw-module main-cpu qa error-recovery
hw-module power-supply power-cycle
hw-module pxf stall-monitoring
hw-module slot (ASR 1000 Series)
hw-module subslot ethernet vlan unlimited
hw-module subslot service-engine session
fabric buffer-reserve
To reserve ASIC buffers, use the fabric buffer-reserve command. in global configuration mode. To return to the default settings, use the no form of this command.
fabric buffer-reserve [high | low | medium | value]
[default] fabric buffer-reserve queue
no fabric buffer-reserve
Syntax Description
Defaults
The default settings are as follows:
•
Buffer reserve is set to 0x0.
•
Command Modes
Global configuration
Command History
Usage Guidelines
Note
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
The fabric buffer-reserve queue command is supported on Cisco 7600 series routers that are configured with the following modules:
•
•
•
•
Entering the default fabric buffer-reserve queue command is the same as entering the fabric buffer-reserve queue command.
You can enter the fabric buffer-reserve command to improve the system throughput by reserving ASIC buffers.
This command is supported on the following modules:
•
•
•
•
Examples
This example shows how to reserve the high (0x5050) ASIC buffer spaces:
Router(config)# fabric buffer-reserve highRouter(config)#This example shows how to reserve the low (0x3030) ASIC buffer spaces:
Router(config)# fabric buffer-reserve lowRouter(config)#fabric clear-block
To enable the clear-block congestion control for the fabric channels, use the fabric clear-block command in global configuration mode. To disable the clear-block congestion control for the fabric channels, use the no form of this command.
fabric clear-block
no fabric clear-block
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Global configuration
Command History
12.2(17d)SXB1
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Note
This command is supported only with Supervisor Engine 720 hardware revision 4.0 and later releases.
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
Examples
This example shows how to enable the clear-block congestion control for the fabric channels:
Router(config)# fabric clear-blockRouter(config)#This example shows how to disable the clear-block congestion control for the fabric channels:
Router(config)# no fabric clear-blockRouter(config)#fabric error-recovery fabric-switchover (virtual switch)
To enable a supervisor engine switchover when excessive fabric synchronization errors are detected on the fabric-enabled module, use the fabric error-recovery fabric-switchover command in global configuration mode. To disable the supervisor engine switchover for excessive fabric synchronization errors, use the no form of this command.
fabric {switch num} error-recovery fabric-switchover
no fabric {switch num} error-recovery fabric-switchover
Syntax Description
Command Default
Excessive fabric synchronization errors initiate a supervisor engine switchover, and the configuration is not saved to the configuration file.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
When a fabric-capable switching module has fabric errors, a supervisor engine switchover is initiated.
You can use the no fabric error-recovery fabric-switchover command to avoid the supervisor engine switchover. This command does not perform the supervisor engine switchover but powers down the module that is experiencing the excessive fabric errors. This command is saved to the configuration file.
Examples
The following example shows how to enable a supervisor engine switchover when excessive fabric synchronization errors are detected on the fabric-enabled module:
Router(config)# fabric switch 2 error-recovery fabric-switchoverRouter(config)#The following example shows how to disable a supervisor engine switchover when excessive fabric synchronization errors are detected on the fabric-enabled module:
Router(config)# no fabric switch 2 error-recovery fabric-switchoverRouter(config)#Related Commands
fabric lcd-banner
To specify the message-of-the-day (MOTD) banner for display on the Switch Fabric Module, use the fabric lcd-banner command in global configuration mode. To delete the MOTD banner, use the no form of this command.
fabric lcd-banner d message d
no fabric lcd-banner
Syntax Description
d
Delimiting character; see the "Usage Guidelines" section for additional guidelines.
message
Message text; see the "Usage Guidelines" section for additional guidelines.
Defaults
No MOTD banner is specified.
Command Modes
Global configuration
Command History
12.2(17d)SXB
Support for this command on the Supervisor Engine 2 was extended to Release 12.2(17d)SXB.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is supported on Cisco 7600 series routers that are configured with a Supervisor Engine 2 only.
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
You cannot use the delimiting character in the banner message. The delimiter is a character of your choice—a pound sign (#), for example.
You can replace tokens with the corresponding configuration argument.
Follow this command with one or more blank spaces and a delimiting character of your choice. Then enter one or more lines of text, terminating the message with the second occurrence of the delimiting character.
This MOTD banner is useful for displaying messages that affect all users (such as impending system shutdowns).
When you connect to the router, the MOTD banner appears before the login prompt. After you successfully log in to the router, the EXEC banner or incoming banner is displayed, depending on the type of connection. For a reverse Telnet login, the incoming banner is displayed. For all other connections, the router displays the EXEC banner.
To customize the banner, use tokens in the form $(token) in the message text. Tokens display current Cisco IOS configuration arguments, such as the router's hostname and IP address.
Table 1 describes the command tokens.
Examples
This example shows how to set a MOTD banner for display on the Switch Fabric Module LCD display; the pound sign (#) is used as a delimiting character:
Router(config)# fabric lcd-banner#Building power will be off from 7:00 AM until 9:00 AM this coming Tuesday.#This example shows how to set a MOTD banner; the percent sign (%) is used as a delimiting character:
Router(config)# fabric lcd-banner%Enter TEXT message. End with the character '%'.You have entered $(hostname).$(domain) on line $(line) ($(line-desc)) %When the MOTD banner is executed, you see the following (notice that the $(token) syntax is replaced by the corresponding configuration argument):
You have entered company.ourdomain.com on line 5 (Dialin Modem)Related Commands
fabric required
To prevent the Catalyst 6500 series switch from coming online without a Switch Fabric Module, use the fabric required command in global configuration mode. To allow the Catalyst 6500 series switch to come up without a Switch Fabric Module, use the no form of this command.
fabric required
no fabric required
Syntax Description
This command has no arguments or keywords.
Defaults
A Switch Fabric Module is not required.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
If you enter the fabric required command, when you remove or power down the last Switch Fabric Module, all modules except the supervisor engine, power down. When you insert or power on the first Switch Fabric Module, the modules that were previously powered down power up if the Switch Fabric Module configuration is not in conflict with other configurations.
If you enter the no fabric required command, the modules will also power on if a Switch Fabric Module is not present and the configuration allows for it.
Examples
This example shows how to prevent the Catalyst 6500 series switch from coming online without a Switch Fabric Module:
Router(config)# fabric requiredRouter(config)#This example shows how to allow the Catalyst 6500 series switch to come up without a Switch Fabric Module:
Router(config)# no fabric requiredRouter(config)#Related Commands
fabric switching-mode allow
To enable various switching modes in the presence of two or more fabric-enabled switching modules, use the fabric switching-mode allow command in global configuration mode. To disable the settings, use the no form of this command.
fabric switching-mode allow {bus-mode | dcef-only | truncated [threshold [mod]]}
no fabric switching-mode allow {bus-mode | truncated [threshold]}
Syntax Description
Command Default
The truncated mode is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command is not supported on Catalyst 6500 or Cisco 7600 series routers that are configured with a Supervisor Engine 32.
Ethernet ports are not disabled when this command is entered on a Supervisor Engine 720-10GE. This command is also supported with Supervisor Engine 720 starting with Release 12.2(33)SXI2. However, prior to Release 12.2(33)SXI2, if all the installed switching modules have Distributed Forwarding Cards (DFCs), enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on both supervisor engines. Entering this command ensures that all modules are operating in dCEF-only mode and simplifies switchover to the redundant supervisor engine.
With a Supervisor Engine 2 and Release 12.2(18)SXD1 and later releases, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on the redundant supervisor engine. Entering this command ensures that all modules are operating in dCEF-only mode.
Note
Bus mode—Supervisor engines use this mode for traffic between nonfabric-enabled modules and for traffic between a nonfabric-enabled module and a fabric-enabled module. In this mode, all traffic passes between the local bus and the supervisor engine bus.
dCEF-only—Supervisor engines, both active and redundant, operate as nonfabric-capable modules with their uplink ports relying on the Policy Feature Card (PFC) on the active supervisor engine for all forwarding decisions. For the Supervisor 720-10G, the uplink ports on both the active and standby routers will remain active. If all other modules are operating in dCEF-only mode, module Online Insertion and Removal (OIR) is nondisruptive.
Note
Truncated mode—Supervisor engines use this mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, line cards send a truncated version of the traffic (the first 64 bytes of the frame) over the Catalyst bus.
Compact mode—Supervisor engines use this mode for all traffic when only fabric-enabled modules are installed. In this mode, a compact version of the Desktop Bus (DBus) header is forwarded over the Catalyst bus, which provides the best possible centralized forwarding performance.
A fabric-enabled module has an additional connection directly to the switch fabric. Fabric-enabled modules forward packets in compressed mode, where only the header is sent to the Supervisor Engine and the full packet is forwarded directly from one line card to another.
To prevent use of nonfabric-enabled modules or to prevent fabric-enabled modules from using bus mode, enter the no fabric switching-mode allow bus-mode command.
Caution
The fabric switching-mode allow command affects Supervisor engines that are configured with a minimum of two fabric-enabled modules.
You can enter the fabric switching-mode allow truncated command to unconditionally allow truncated mode.
You can enter the no fabric switching-mode allow truncated command to allow truncated mode if the threshold is met.
You can enter the no fabric switching-mode allow bus-mode command to prevent any module from running in bus mode.
To return to the default truncated-mode threshold, enter the no fabric switching-mode allow truncated threshold command.
The valid value for mod is the threshold value.
Examples
The following example shows how to specify truncated mode:
Router(config)# fabric switching-mode allow truncatedRelated Commands
fabric switching-mode force bus-mode
To force fabric-enabled modules into bus switching mode, use the fabric switching-mode force bus-mode command in global configuration mode. To power cycle the module to truncated mode, use the no form of this command.
fabric switching-mode force bus-mode
no fabric switching-mode force bus-mode
Syntax Description
This command has no arguments or keywords.
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
12.2(18)SXD5
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command is not supported on Cisco 7600 series routers that are configured with a Supervisor Engine 32.
This command applies to the following modules:
•
•
•
•
•
•
•
•
After you enter the fabric switching-mode force busmode or the no fabric switching-mode force busmode command, the fabric-enabled service modules power cycle immediately. The mode change occurs as the modules come up after the power cycle.
Examples
This example shows how to force fabric-enabled modules into flow-through switching mode:
Router(config)# fabric switching-mode force bus-modeRouter(config)#Related Commands
fabric timer
To set the drop counter time-stamp and peak-utilization poll time in seconds, use the fabric timer command in global configuration mode. To remove the drop counter time-stamp and peak-utilization poll time, use the no form of this command.
fabric timer seconds
no fabric timer seconds
Syntax Description
seconds
Poll time in seconds for drop counter time-stamps and peak-utilization. Valid values are from 1 to 1800.
Command Default
The internal default timer is set to 15 seconds.
Command Modes
Global configuration (config)
Command History
12.2(14)SXF
This command was introduced on the Catalyst 6500 series switch.
12.2(5)SRB
This command was implemented on the Supervisor Engine 720.
Examples
The following example shows how to set the drop counter time-stamp and peak-utilization poll time to 200 seconds:
Router(config)# fabric timer 200Related Commands
facility-alarm
To configure threshold temperatures for minor, major, and critical alarms, use the facility-alarm command in global configuration mode. To disable alarms for the threshold and reset the threshold to the default value, use the no form of this command.
Cisco 10000 Series Router
facility-alarm {core-temperature | outlet-temperature} {major | minor | critical} [temperature]
no facility-alarm {core-temperature | outlet-temperature} {major | minor | critical} [temperature]
Cisco 7200 Series Router
facility-alarm {core-temperature | intake-temperature} temperature
Syntax Description
Command Default
If the command is not enabled, the default values are set.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
You can configure explicit threshold temperatures to override the defaults for major, minor, and critical alarms. Temperature thresholds for each alarm type and location are automatically set based on determined values that vary depending on the number and type of boards inserted in the chassis. In addition to the automatically set thresholds, you can set thresholds for minor and major temperature alarms. You can also disable the minor and major temperature alarms. You cannot, however, change the threshold for or disable critical alarms.
Cisco 10000 Series Router
On the PRE2, use the facility-alarm core-temperature command. On the PRE3, use the facility-alarm outlet-temperature command.
The default value for a threshold temperature depends on the performance routing engine (PRE) installed in the router as the following describes:
•
–
–
•
–
–
•
–
–
Examples
The following example sets a threshold temperature of 53 for major alarms on the PRE2:
Router> enableRouter# config terminalRouter(config)# facility-alarm core-temperature major 53The following example sets a threshold temperature of 50 for minor alarms on the PRE3:
Router> enableRouter# config terminalRouter(config)# facility-alarm core-temperature minor 50Related Commands
facility-alarm critical exceed-action shutdown
To allow automatic router shutdown, use the facility-alarm critical exceed-action shutdown command in global configuration mode. To disable automatic router shutdown, use the no form of this command.
facility-alarm critical exceed-action shutdown
no facility-alarm critical exceed-action shutdown
Syntax Description
This command has no arguments or keywords.
Command Default
Automatic router shutdown is not enabled.
Command Modes
Global configuration (config)
Command History
Cisco IOS XE Release 2.1
This command was introduced on the Cisco ASR 1000 Series Routers.
Usage Guidelines
If the facility-alarm critical exceed-action shutdown command is enabled, the router performs an automatic shutdown under the following conditions:
•
•
•
Examples
The following example enables automatic router shutdown:
Router(config)# facility-alarm critical exceed-action shutdownRelated Commands
facility-alarm detect
To turn on the facility alarms, use the facility-alarm detect command in global configuration mode. To turn off the alarm, use the no form of this command.
facility-alarm detect {controller controller slot-number | interface type number | rps | temperature | fan}
no facility-alarm detect {controller T1 slot-number | interface type number | rps | temperature | fan}
Syntax Description
Command Default
The facility alarm is turned off.
Command Modes
Global configuration (config)
Command History
15.0(1)M
This command was introduced in a release earlier than Cisco IOS Release 15.0(1)M on the Cisco 5400-XM series routers.
Usage Guidelines
Facility alarms monitor the following failure events:
•
•
•
•
Cisco IOS software polls every second to detect the failure events that you have configured and turns on the alarm when any one of the failure events is detected. By default, the facility alarm is off. Users have to configure a facility alarm command to enable monitoring of the failure conditions.
Examples
The following example shows how to turn on the facility alarm for RPS:
Router(config)# facility-alarm detect rpsRelated Commands
fddi burst-count
To allow the FCI card to preallocate buffers to handle bursty FDDI traffic (for example, Network File System [NFS] bursty traffic), use the fddi burst-count command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi burst-count number
no fddi burst-count
Syntax Description
Defaults
3 buffers
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command applies to the FCI card only.
Note
Examples
The following example sets the number of buffers to 5:
Router(config)# interface fddi 0Router(config-if)# fddi burst-count 5fddi c-min
To set the C-Min timer on the pulse code modulation (PCM), use the fddi c-min command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi c-min microseconds
no fddi c-min
Syntax Description
Defaults
1600 microseconds
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command applies to the processor connection management (CMT) only. You need extensive knowledge of the PCM state machine to tune this timer. Use this command when you run into PCM interoperability problems.
Examples
The following example sets the C-Min timer to 2000 microseconds:
Router(config)# interface fddi 0Router(config-if)# fddi c-min 2000Related Commands
fddi cmt-signal-bits
To control the information transmitted during the connection management (CMT) signaling phase, use the fddi cmt-signal-bits command in interface configuration mode.
fddi cmt-signal-bits signal-bits [phy-a | phy-b]
Syntax Description
signal-bits
A hexadecimal number preceded by 0x; for example, 0x208. The FDDI standard defines 10 bits of signaling information that must be transmitted, as follows:
•
•
•
•
•
•
•
•
phy-a
(Optional) Selects Physical Sublayer A. The default is 0x008 (hexadecimal) or 00 0000 1000 (binary). Bits 1 and 2 are set to 00 to select Physical A. Bit 3 is set to 1 to indicate "accept any connection."
phy-b
(Optional) Selects Physical Sublayer B. The default is 0x20c (hexadecimal) or 10 0000 1100 (binary). Bits 1 and 2 are set to 10 to select Physical B. Bit 3 is set to 1 to indicate "accept any connection." Bit 9 is set to 1 to select MAC on output. The normal data flow on FDDI is input on Physical A and output on Physical B.
Defaults
•
•
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
If neither the phy-a nor phy-b keyword is specified, the signal bits apply to both physical connections.
Caution
Table 2 lists the physical types.
Table 2 FDDI Physical Type Bit Specifications
0
0
Physical A
1
0
Physical B
0
1
Physical S
1
1
Physical M
Table 3 lists the duration bits.
This command does not have a no form.
Examples
The following example sets the CMT signaling phase to signal bits 0x208 on both physical connections:
Router(config)# interface fddi 0Router(config-if)# fddi cmt-signal-bits 0x208fddi duplicate-address-check
To enable the duplicate address detection capability on the FDDI interface, use the fddi duplicate-address-check command in interface configuration mode. To disable this function, use the no form of this command.
fddi duplicate-address-check
no fddi duplicate-address-check
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
If you use this command, the Cisco IOS software will detect a duplicate address if multiple stations are sharing the same MAC address. If the software finds a duplicate address, it will shut down the interface.
Examples
The following example enables duplicate address checking on the FDDI interface:
Router(config)# interface fddi 0Router(config-if)# fddi duplicate-address-checkfddi encapsulate
To specify encapsulating bridge mode on the CSC-C2/FCIT interface card, use the fddi encapsulate command in interface configuration mode. To turn off encapsulation bridging and return the FCIT interface to its translational, nonencapsulating mode, use the no form of this command.
fddi encapsulate
no fddi encapsulate
Syntax Description
This command has no arguments or keywords.
Defaults
By default, the FDDI interface uses the SNAP encapsulation format defined in RFC 1042, Standard for the Transmission of IP Datagrams Over IEEE 802 Networks. It is not necessary to define an encapsulation method for this interface when using the CSC-FCI interface card.
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The no fddi encapsulate command applies only to CSC-C2/FCIT interfaces, because the CSC-FCI interfaces are always in encapsulating bridge mode. The CSC-C2/FCIT interface card fully supports transparent and translational bridging for the following configurations:
•
•
•
The fddi encapsulate command puts the CSC-C2/FCIT interface into encapsulation mode when doing bridging. In transparent mode, the FCIT interface interoperates with earlier versions of the CSC-FCI encapsulating interfaces when performing bridging functions on the same ring.
Caution
from occurring. These problems include bit-order translation (or usage of MAC addresses as data), maximum transfer unit (MTU) differences, frame status differences, and multicast address usage.
Some or all of these problems might be present in a multimedia bridged LAN and might prevent communication from taking place. These problems are most prevalent when bridging between
Token Rings and Ethernets or between Token Rings and FDDI nets. This is because of the different
way Token Ring is implemented by the end nodes.
The following protocols have problems when bridged between Token Ring and other media: Novell IPX, DECnet Phase IV, AppleTalk, VINES, XNS, and IP. Furthermore, the following protocols may have problems when bridged between FDDI and other media: Novell IPX and XNS. We recommend that these protocols be routed whenever possible.
Examples
The following example sets FDDI interface 1 on the CSC-C2/FCIT interface card to encapsulating bridge mode:
Router(config)# interface fddi 1Router(config-if)# fddi encapsulatefddi frames-per-token
To specify the maximum number of frames that the FDDI interface transmits per token capture, use the fddi frames-per-token command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi frames-per-token number
no fddi frames-per-token
Syntax Description
number
Maximum number of frames to transmit per token capture. Valid values are from 1 to 10. The default is 3.
Defaults
3 frames
Command Modes
Interface configuration
Command History
11.2 P
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Changing the value will increase or decrease the maximum number of frames that the FDDI interface can transmit when it receives a token. Increasing the value does not necessarily mean more frames will be transmitted on each token capture. This is heavily dependent on the traffic load of the specific interface.
When the interface captures a token, it transmits all of the frames that are queued in the interface's transmit ring, up to a maximum value specified by the fddi frames-per-token command.
If there are no frames ready for transmission, the token is passed on, and no frames are transmitted. If there are less than the fddi frames-per-token value in the transmit ring, all frames in the transmit ring are transmitted before the token is passed on. If there are more than the fddi frames-per-token value in the transmit ring, the specified value is transmitted before the token is passed on. The remaining frames in the transmit ring remain queued until the token is captured again.
Examples
The following example shows how to configure the FDDI interface to transmit four frames per token capture:
Router(config-if)# fddi frames-per-token 4fddi smt-frames
To enable the Station Management (SMT) frame processing capability on the FDDI, use the fddi smt-frames command in interface configuration mode. To disable this function and prevent the Cisco IOS software from generating or responding to SMT frames, use the no form of this command.
fddi smt-frames
no fddi smt-frames
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use the no form of this command to turn off SMT frame processing for diagnosing purposes. Use the fddi smt-frames command to reenable the feature.
Examples
The following example disables SMT frame processing:
Router(config)# interface fddi 0Router(config-if)# no fddi smt-framesfddi tb-min
To set the TB-Min timer in the physical connection management (PCM), use the fddi tb-min command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi tb-min milliseconds
no fddi tb-min
Syntax Description
milliseconds
Number, in milliseconds, that sets the TB-Min timer value. The range is from 0 to 65535. The default is 100.
Defaults
milliseconds: 100
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command applies to the processor connection management (CMT) only. Use this command when you run into PCM interoperability problems.
Note
Examples
The following example shows how to set the TB-Min timer to 200 ms:
Router(config)# interface fddi 0Router(config-if)# fddi tb-min 200Related Commands
fddi tl-min-time
To control the TL-Min time (the minimum time to transmit a Physical Sublayer, or PHY line state, before advancing to the next physical connection management [PCM] state, as defined by the X3T9.5 specification), use the fddi tl-min-time command in interface configuration mode.
fddi tl-min-time microseconds
Syntax Description
Defaults
microseconds: 30
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Interoperability tests have shown that some implementations of the FDDI standard need more than 30 microseconds to sense a signal.
This command does not have a no form.
Examples
The following example changes the TL-Min time from 30 microseconds to 100 microseconds:
Router(config)# interface fddi 0Router(config-if)# fddi tl-min-time 100The following example changes the TL-Min time from 30 microseconds to 100 microseconds on a Cisco 7500 series router:
Router(config)# interface fddi 3/0Router(config-if)# fddi tl-min-time 100Related Commands
fddi token-rotation-time
To control ring scheduling during normal operation and to detect and recover from serious ring error situations, use the fddi token-rotation-time command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi token-rotation-time microseconds
no fddi token-rotation-time
Syntax Description
microseconds
Number, in microseconds, that specifies the token rotation time (TRT). The range is from 4000 to 165000. The default is 5000.
Defaults
microseconds: 5000
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The FDDI standard restricts the allowed time to be greater than 4000 microseconds and less than 165,000 microseconds. As defined in the X3T9.5 specification, the value remaining in the TRT is loaded into the token holding timer (THT). Combining the values of these two timers provides the means to determine the amount of bandwidth available for subsequent transmissions.
Examples
The following example sets the rotation time to 24,000 microseconds:
Router(config)# interface fddi 0Router(config-if)# fddi token-rotation-time 24000The following example sets the rotation time to 24,000 microseconds on a Cisco 7500 series router:
Router(config)# interface fddi 3/0Router(config-if)# fddi token-rotation-time 24000fddi t-out
To set the timeout timer in the physical connection management (PCM), use the fddi t-out command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi t-out milliseconds
no fddi t-out
Syntax Description
milliseconds
Number, in milliseconds, that sets the timeout timer. The range is from 0 to 65535. The default is 100.
Defaults
milliseconds: 100
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
This command applies to the processor connection management (CMT) only. Use this command when you run into PCM interoperability problems.
Note
Examples
The following example sets the timeout timer to 200 ms:
Router(config)# interface fddi 0Router(config-if)# fddi t-out 200Related Commands
fddi valid-transmission-time
To change the transmission valid timer (TVX) interval, use the fddi valid-transmission-time command in interface configuration mode. To revert to the default value, use the no form of this command.
fddi valid-transmission-time microseconds
no fddi valid-transmission-time
Syntax Description
microseconds
Number, in microseconds, that specifies the TVX interval. The range is from 2500 to 2147483647. The default is 2500.
Defaults
microseconds: 2500
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
Use this command to recover from a transient FDDI ring error by setting a longer transmission timer interval.
Examples
The following example shows how to change the transmission timer interval to 3000 microseconds:
Router(config)# interface fddi 0Router(config-if)# fddi valid-transmission-time 3000The following example shows how to change the transmission timer interval to 3000 microseconds on Cisco 7000 series routers or Cisco 7200 series routers:
Router(config)# interface fddi 3/0Router(config-if)# fddi valid-transmission-time 3000fdl
To set the Facility Data Link (FDL) exchange standard for CSU controllers or to set the FDL exchange standard for a T1 interface that uses the Extended Super Frame (ESF) framing format, use the fdl command in interface configuration mode. To disable FDL support or to specify that there is no ESF FDL, use the no form of this command.
Cisco 2600 Series and Cisco 3600 Series Routers
fdl {att | ansi | all | none}
no fdl {att | ansi | all | none}
Cisco 10000 Series Router
fdl {att | ansi}
no fdl {att | ansi}
Syntax Description
Defaults
ANSI T1.403 for ESF FDL exchange support
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is available only for T1 links. This command sets the standard to be followed for FDL messaging through a 4-kbps out-of-band channel that a service provider uses to check for errors on the facility.
You must use the same FDL exchange standard as your service provider. If the setting is not correct, the link might not come up. You can configure a different standard on each T1 interface.
Note
router, ESF framing and binary eight zero substitution (B8ZS) line encoding are supported. When
using a multiport E1 ATM IMA network module on a Cisco 2600 series or Cisco 3600 series router,
CRC4 multiframe framing and HDB3 line encoding are supported. These are the parameters
specified by the ATM Forum, and they cannot be changed.Examples
Cisco 2600 and Cisco 3600 Series Routers
The following example shows how to specify the ANSI standard and the AT&T standard for FDL exchange:
Router(config)# interface atm 0/2Router(config-if)# fdl allCisco 10000 Series Router
The following example shows how to specify the AT&T standard for FDL exchange:
Router(config)# interface atm 1/0/0Router(config-if)# fdl attflowcontrol
To set the method of data flow control between the terminal or other serial device and the router, use the flowcontrol command in line configuration mode. To disable flow control, use the no form of this command.
flowcontrol {none | software [lock] [in | out] | hardware [in | out]}
no flowcontrol {none | software [lock] [in | out] | hardware [in | out]}
Catalyst 6500 Series Switches and Cisco 7600 Series Routers
To configure a port to send or receive pause frames, use the flowcontrol command in interface configuration mode. To return to the default settings, use the no form of this command.
flowcontrol {send | receive} {desired | off | on}
no flowcontrol {send | receive} {desired | off | on}
Syntax Description
Command Default
Flow control is disabled.
Catalyst 6500 Series Switches and Cisco 7600 Routers
Flow-control defaults depend upon port speed. The defaults are as follows:
•
•
•
•
Command Modes
Line configuration
Catalyst 6500 Series Switches and Cisco 7600 Series Routers
Interface configuration
Command History
Usage Guidelines
When software flow control is set, the default stop and start characters are Ctrl-S and Ctrl-Q (XOFF and XON). You can change them using the stop-character and start-character commands.
If a remote Telnet device requires software flow control, the remote system should not be able to turn it off. Using the lock option makes it possible to refuse "dangerous" Telnet negotiations if they are inappropriate.
Catalyst 6500 Series Switches and Cisco 7600 Series Routers
The send and desired keywords are supported on Gigabit Ethernet ports only.
Pause frames are special packets that signal a source to stop sending frames for a specific period of time because the buffers are full.
Gigabit Ethernet ports on the Catalyst 6500 series switches and on the Cisco 7600 series routers use flow control to inhibit the transmission of packets to the port for a period of time; other Ethernet ports use flow control to respond to flow-control requests.
If a Gigabit Ethernet port receive buffer becomes full, the port transmits a "pause" packet that tells remote ports to delay sending more packets for a specified period of time. All Ethernet ports (1000 Mbps, 100 Mbps, and 10 Mbps) can receive and act upon "pause" packets from other devices.
You can configure non-Gigabit Ethernet ports to ignore received pause frames (disable) or to react to them (enable).
When used with receive, the on and desired keywords have the same result.
All the Gigabit Ethernet ports on the Catalyst 6500 series switches and the Cisco 7600 series routers can receive and process pause frames from remote devices.
To obtain predictable results, follow these guidelines:
•
•
•
•
Examples
The following example sets hardware flow control on line 7:
line 7flowcontrol hardwareCatalyst 6500 Series Switches and Cisco 7600 Series Routers
These examples show how to configure the local port to not support any level of flow control by the remote port:
Router(config-if)# flowcontrol receive offRouter(config-if)#Router(config-if)# flowcontrol send offRouter(config-if)#Related Commands
frame-relay
To configure Frame Relay payload compression for each Frame Relay port, use the frame-relay command in interface configuration mode. To terminate this form of payload compression over Frame Relay, use the no form of this command.
frame-relay payload-compression frf9 stac caim [element-number]
no frame-relay payload-compression
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the frame-relay payload-compression command to enable or disable payload compression on a point-to-point interface or subinterface. Use the frame-relay map command to enable or disable payload compression on a multipoint interface or subinterface.
Shut down the interface before changing encapsulation types. Although this is not required, shutting down the interface ensures the interface is reset for the new encapsulation.
Examples
The following example shows Frame Relay configured to use payload compression with the frf9 stac algorithm for CAIM hardware compression, using the installed data compression AIM daughtercard as the compression source:
Router(config-if)# frame-relay payload-compression frf9 stac caim 0Related Commands
framing
To select the frame type for the T1 or E1 data line, use the framing command in controller configuration mode.
T1 Lines
framing {sfadm | esfadm}
E1 Lines
framing {crc4adm | pcm30adm | clear e1}
Syntax Description
Defaults
Extended super frame (esf) for a T1 line
CRC4 disabled framing (pcm30adm) for an E1 lineCommand Modes
Controller configuration
Command History
Usage Guidelines
Use this command in configurations in which the router or access server is intended to communicate with T1 or E1 fractional data lines. The service provided determines which framing type is required for your T1 or E1 circuit.
This command does not have a no form.
Examples
The following example selects extended super frame as the T1 frame type:
Router(config)# controller t1 4/0Router(config-controller)# framing esfadmRelated Commands
lbo
Specifies the distance of the cable from the routers to the network equipment.
linecode
Selects the line code type for a T1 or E1 line.
framing (CEM)
To specify the framing format of a circuit emulation (CEM) T1 or E1 port, use the framing command in controller configuration mode. To reset the framing format of the port to its default value, use the no form of this command.
T1 Port
framing {sf | esf | unframed}
no framing
E1 Port
framing {crc4 | no-crc4 | unframed}
no framing
Syntax Description
Command Default
The framing format of a T1 line defaults to esf.
The framing format of an E1 line defaults to crc4.
If an unframed CEM channel is created on the port using the cem-group command, no framing structure is sought or imposed.Command Modes
Controller configuration
Command History
Usage Guidelines
Framing must be configured to match the framing format used by the attached equipment.
In order to change a line between unframed and any framed mode, you must first delete the CEM channels defined in the line.
Examples
The following example shows how to set the framing format of a CEM T1 port to be super frame format.
Router(config-controller)# framing sfThe following example shows how to set the framing format of a CEM E1 port to the G.704 standard with the optional CRC4 mechanism defined in time slot 0 disabled.
Router(config-controller)# framing no-crc4Related Commands
framing (E3 controller)
To specify the type of framing used by the E3 controller, use the framing command in controller configuration mode. To restore the default framing type, use the no form of this command.
framing {bypass | g751}
no framing
Syntax Description
bypass
Specifies that G.751 framing be bypassed.
g751
Specifies G.751 as the E3 framing type. This is the default.
Defaults
G.751 framing
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the framing command, the default, g751, is used by the E3 controller to automatically determine the framing type received from the far-end equipment.
Configure framing as G.751 when the E3 connection terminates remotely on a Digital Link or Kentrox data service unit (DSU), or when needing a subrate on an E3 connection between two T3 or E3 network modules.
Note
When G.751 framing is used, DSU bandwidth can be used to select a payload subrate from 34,010 kbps down to 22 kbps.
When framing bypass is used, DSU bandwidth of 34,010 kbps must be configured.
When G.751 framing is used, configuring the scramble command can prevent some payload data from being mistakenly interpreted as G.751 framing bits by switches placed between the DSUs. By default, the no scramble command is configured.
When framing bypass is used, the no scramble command must be configured.
When G.751 framing is used, bit 11 of the G.751 frame is reserved for national use and is set to 1 by default.
Configure national bit 1 only when required for interoperability with your telephone company.
Examples
The following example shows the framing for the E3 controller set to bypass:
Router(config)# controller e3 1/0Router(config-controller)# framing bypassRelated Commands
scramble
Specifies the type of framing used by the T1 channels on the CT3IP in Cisco 7500 series routers.
framing (SONET)
To select the frame type of the frame received on an optical line, use the framing command in controller configuration mode.
framing {sonet | sdh}
Syntax Description
sonet
Specifies the framing type as SONET.
sdh
Specifies the framing type as Synchronous Digital Hierarchy (SDH).
Defaults
SONET is the default for the PA-MC-STM-1 port adapter.
SDH is the default for the STM-1 trunk card.Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command to configure the framing type of the SONET controller. The PA-MC-STM-1 port adapter supports both the SONET and SDH framing modes. The STM-1 trunk feature card on the Cisco AS5850 supports only SDH framing.
This command does not have a no form.
Examples
The following example shows how to configure the framing type 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)# framing sonetRelated Commands
framing (T1/E1 controller)
To select the frame type for the T1 or E1 data line, use the framing command in controller configuration mode. To return to the default, use the no form of the command.
T1 Lines
framing {sf | esf}
E1 Lines
framing {crc4 | no-crc4} [australia]
T1 Shared Port Adapter
framing {sf | esf}
no framing {sf | esf}
E1 Shared Port Adapter
framing {crc4 | no-crc4 | unframed}
no framing {crc4 | no-crc4 | unframed}
Syntax Description
Defaults
sf on a T1 line
crc4 on an E1 line
Command Modes
Controller configuration
Command History
Usage Guidelines
Use this command in configurations in which the router or access server is intended to communicate with T1 or E1 fractional data lines. The service provider determines the framing type required for your T1/E1 circuit.
To return to the default mode on a T1/E1 SPA, use the no form of this command. This command does not have a no form for other T1/E1 lines.
Examples
The following example selects extended super frame as the T1 frame type:
Router(config-controller)# framing esfRelated Commands
cablelength
Specifies the distance of the cable from the routers to the network equipment.
linecode
Selects the linecode type for T1 or E1 line.
framing (T3 controller)
To choose framing mode on a T3 port, use the framing command in controller configuration mode. To return to the default mode, use the no form of this command.
T3 Controllers
framing {c-bit | m23}
no framing
Channelized T3 Shared Port Adapters and the Cisco 7500 Series Routers with CT3IP Port Adapter
framing {c-bit | m23 | auto-detect}
no framing
Syntax Description
Defaults
c-bit (for the 2-Port and 4-Port Channelized T3 SPA and most T3 controllers)
auto-detect (for the CT3IP in a Cisco 7500 series router)
Command Modes
Controller configuration
Command History
Usage Guidelines
You can set the framing for each T1 channel by using the t1 framing controller configuration command.
Cisco 7500 Series Routers with CT3IP Port Adapter
Because the CT3IP supports the Application Identification Channel (AIC) signal, the setting for the framing might be overridden by the CT3IP firmware.
Examples
The following example sets the framing mode on a T3 interface.
Router# configure terminalRouter(config)# controller t1 6/0/0Router(config-controller)# framing m23The following example sets the framing for the CT3IP to C-bit:
Router(config)# controller t3 9/0/0Router(config-controller)# framing c-bitRelated Commands
framing (T3-E3 interface)
To choose framing mode on a T3 or E3 port, use the framing command in interface configuration mode. To return to the default mode, use the no form of this command.
PA-T3 and T3 Shared Port Adapters
framing {bypass | c-bit | m13}
no framing {bypass | c-bit | m13}
PA-E3 and E3 Shared Port Adapters
framing {bypass | g751 | g832}
no framing {bypass | g751 | g832}
Syntax Description
Defaults
T3: C-bit framing
E3: g751 framing
Command Modes
Interface configuration
Command History
Usage Guidelines
The default framing is described in the ITU-T Recommendation G.751.
Note
When the framing mode is bypass, the T3 frame data is not included in the T3 frame, just the data.
When the framing mode is bypass, the E3 frame data is not included in the E3 frame, just the data.
If you use the bypass keyword, scrambling must be set to the default (disabled), the DSU mode must be set to the default (0), and the DSU bandwidth must be set to the default (44736).
The g832 keyword is not supported on Cisco 7304 routers with the 2-Port and 4-Port Clear Channel T3/E3 SPA.
Examples
The following example sets the framing mode to bypass on interface 1/0/0:
Router(config)# interface serial 1/0/0Router(config-if)# framing bypassRelated Commands
full-duplex
To specify full-duplex mode on full-duplex single-mode and multimode port adapters, use the full-duplex command in interface configuration mode. To restore the default half-duplex mode, use the no form of this command.
full-duplex
no full-duplex
Syntax Description
This command has no arguments or keywords.
Defaults
Cisco 7500 Series Router
Half-duplex; a Fast Ethernet Interface Processor (FEIP), and serial interfaces that are configured for bisynchronous tunneling
Cisco 10000 Series Router
Autonegotiation
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if the equipment on the other end is capable of full-duplex mode.
This command specifies full-duplex mode on full-duplex single-mode and multimode port adapters available on the following networking devices:
•
•
•
•
Refer to the Cisco Product Catalog for hardware compatibility information and for specific model numbers of port adapters.
To enable half-duplex mode, use the no full-duplex or half-duplex command.
Note
and half-duplex commands on a Cisco AS5300:
Router(config)# interface fastethernet 0
Router(config-if)# full-duplex
Please use duplex command to configure duplex mode
Router(config-if)#
Router(config-if)# half-duplex
Please use duplex command to configure duplex modeSupport for This Command
Use the question mark (?) command to find out which port adapters support this command. If the interface does not support full-duplex, an informational message displayed, and no changes are made to the interface. To determine if the interface supports full-duplex, use the show interfaces command. For example, the following message is displayed if the interface does not support full-duplex:
% interface does not support full-duplex.Use on FDDI
Full-duplex on the FDDI full-duplex port adapters allows an FDDI ring with exactly two stations to transform the ring into a full-duplex, point-to-point topology. For the interface to operate in full-duplex mode, there must be only two stations on the ring, the two stations must be capable of operating in full-duplex mode, and both stations must complete a full-duplex autoconfiguration protocol. There is no FDDI token in full-duplex mode. Refer to the Cisco Product Catalog for specific model numbers of port adapters.
Full-duplex autoconfiguration protocol allows an FDDI station to dynamically and automatically operate in either half-duplex (or ring) or full-duplex mode, and ensures that the stations fall back to ring mode when a configuration change occurs, such as a third station joining the ring.
After booting the router, the FDDI stations begin operation in half-duplex mode. While the station performs the full-duplex autoconfiguration protocol, the station continues to provide data-link services to its users. Under normal conditions, the transition between half-duplex mode and full-duplex mode is transparent to the data-link users. The data-link services provided by full-duplex mode are functionally the same as the services provided by half-duplex mode.
If you change the full-duplex configuration (for example, from disabled to enabled) on supported interfaces, the interface resets.
Cisco 10000 Series Router
The Fast Ethernet line card responds only to 802.3x pause frames from another device when it autonegotiates the duplex mode (the default). The line card does not support 802.3x flow control when you manually set half-duplex or full-duplex mode.
Examples
Cisco 7200 Series Router
The following example configures full-duplex mode on the Cisco 7200 series routers:
Router(config)# interface fastethernet 0/1Router(config-if)# full-duplexFull-Duplex Binary Synchronous
The following example specifies full-duplex binary synchronous communications (Bisync) mode:
Router(config)# interface serial 0Router(config-if)# encapsulation bstunRouter(config-if)# full-duplexFull-Duplex on FDDI Interface
The following example enables full-duplex mode on FDDI interface 0:
Router(config)# interface fddi 0/1/0Router(config-if)# full-duplexRelated Commands
g709 fec
To configure the forward error correction (FEC) mode for the DWDM controller, use the g709 fec command in controller configuration mode. To return to the default state, use the no form of this command.
g709 fec {disable | enhanced | standard}
no g709 fec
Syntax Description
Command Default
Standard FEC mode is enabled by default.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
The g709 fec command can be used only when the DWDM controller is in the shutdown state.
Standard FEC is the default mode; therefore, if you use the no g709 fec command, standard FEC is used.
Examples
The following example shows how to configure standard FEC mode on a DWDM controller:
Router(config)# controller dwdm 1/3Router(config-controller)# g709 fec standardRelated Commands
g709 odu report
To enable the logging of selected optical channel data unit (ODU) alarms to the console for a DWDM controller, use the g709 odu report command in controller configuration mode. To disable logging, use the no form of this command.
g709 odu report {ais | bdi | lck | oci | pm-tca | ptim | sd-ber | sf-ber | tim}
no g709 odu report {ais | bdi | lck | oci | pm-tca | ptim | sd-ber | sf-ber | tim}
Syntax Description
Command Default
Logging is enabled for all keywords.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
This command can be used only when the DWDM conroller is in the shutdown state.
Examples
The following example shows how to enable ODU reporting for OCI:
Router(config)# controller dwdm 1/2Router(config-controller)# g709 odu report ociRelated Commands
g709 odu overhead tti
To configure the Trail Trace Identifier (TTI) level for an Optical Channel Data Unit (ODU), use the g709 odu overhead tti command in DWDM configuration mode. To return to the default, use the no form of this command.
g709 odu overhead tti {expected | sent}{ascii | hex} tti-string
no g709 odu overhead tti {expected | sent}{ascii | hex} tti-string
Syntax Description
Command Default
No TTI level string is configured.
Command Modes
DWDM configuration.
Command History
Usage Guidelines
To display the TTI strings, use the show controller dwdm g709 command.
Examples
The following example shows how to configure the expected TTI string:
Router(config)# controller dwdm 0/1/0/0Router(config-dwdm)# g709 odu overhead tti expected ascii test_odu_5678Related Commands
show controller dwdm
Displays optical parameters, G.709 alarms and counters, and register and module information for a DWDM controller.
g709 odu threshold
To configure thresholds for selected optical channel data unit (ODU) bit error rate (BER) alarms, use the g709 odu threshold command in controller configuration mode. To return to the default state, use the no form of this command.
g709 odu threshold {pm-tca bit-error-rate | sd-ber bit-error-rate | sf-ber bit-error-rate}
no g709 odu threshold {pm-tca bit-error-rate | sd-ber bit-error-rate | sf-ber bit-error-rate}
Syntax Description
Command Default
sd-ber: 6
sf-ber: 3
pm-tca: 3
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
This command can be used only when the DWDM controller is in the shutdown state.
Examples
The following example shows how to set the signal fail BER rate to 5:
Router(config)# controller dwdm 1/2Router(config-controller)# g709 odu threshold sf-ber 5Related Commands
g709 otu report
To enable the logging of selected optical channel transport unit (OTU) alarms to the console for a DWDM controller, use the g709 otu report command in controller configuration mode. To disable logging, use the no form of this command.
g709 otu report {ais | bdi | iae | lof | lom | los | sm-tca | tim}
no g709 otu report {ais | bdi | iae | lof | lom | los | sm-tca | tim}
Syntax Description
Command Default
Reporting is enabled for all keywords.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
This command can be used only when the DWDM controller is in the shutdown state.
Examples
The following example shows how to enable OTU reporting for IAE:
Router(config)# controller dwdm 1/2Router(config-controller)# g709 otu report iaeRelated Commands
g709 otu threshold
To configure thresholds for selected optical channel transport unit (OTU) bit error rate (BER) alarms, use the g709 otu threshold command in controller configuration mode. To return to the default state, use the no form of this command.
g709 otu threshold sm-tca bit-error-rate
no g709 otu threshold sm-tca bit-error-rate
Syntax Description
Command Default
bit-error-rate: 3
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
This command can be used only when the DWDM controller is in the shutdown state.
Examples
The following example shows how to set the Section Monitoring Threshold Crossing Alert threshold to 5:
Router(config)# controller dwdm 1/2Router(config-controller)# g709 otu threshold sm-tca 5Related Commands
half-duplex
To specify half-duplex mode on an Synchronous Data Link Control (SDLC) interface or on the FDDI full-duplex, single-mode port adapter and FDDI full-duplex, multimode port adapter on the Cisco 7200 series and Cisco 7500 series routers, use the half-duplex command in interface configuration mode. To reset the interface to full-duplex mode, use the no form of this command.
half-duplex
no half-duplex
Syntax Description
This command has no arguments or keywords.
Defaults
Full-duplex mode is the default mode on an SDLC interface, the FDDI full-duplex, single-mode port adapter and FDDI full-duplex, multimode port adapter on the Cisco 7200 series and Cisco 7500 series routers.
Command Modes
Interface configuration
Command History
Usage Guidelines
SDLC Interfaces
The half-duplex command is used to configure an SDLC interface for half-duplex mode and is used on a variety of port adapters. Use the question mark (?) command to find out which port adapters support this command.
Note
Note
and half-duplex commands on a Cisco AS5300:
Router(config)# interface fastethernet 0
Router(config-if)# full-duplex
Please use duplex command to configure duplex mode
Router(config-if)#
Router(config-if)# half-duplex
Please use duplex command to configure duplex modeEnabling Full-Duplex Mode
To enable full-duplex mode, use the no half-duplex or full-duplex commands.
Note
the keyword half-duplex was removed from the media-type command. In Release 11.0(6), the functionality for specifying half-duplex mode is provided by the half-duplex command.Port Adapters
Refer to the Cisco Product Catalog for specific model numbers of port adapters.
Examples
The following example configures an SDLC interface for half-duplex mode:
Router(config-if)# encapsulation sdlc-primaryRouter(config-if)# half-duplexRelated Commands
full-duplex
Specifies full-duplex mode on full-duplex single-mode and multimode port adapters.
half-duplex controlled-carrier
To place a low-speed serial interface in controlled-carrier mode, instead of constant-carrier mode, use the half-duplex controlled-carrier command in interface configuration mode. To return the interface to constant-carrier mode, use the no form of this command.
half-duplex controlled-carrier
no half-duplex controlled-carrier
Syntax Description
This command has no arguments or keywords.
Defaults
Constant-carrier mode, where Data Carrier Detect (DCD) is held constant and asserted by the DCE half-duplex interface.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies only to low-speed serial DCE interfaces in half-duplex mode. Configure a serial interface for half-duplex mode by using the half-duplex command. Refer to the Cisco Product Catalog for specific model numbers of networking devices which support serial interfaces.
Controlled-carrier operation means that the DCE interface has DCD deasserted in the quiescent state. When the interface has something to transmit, it asserts DCD, waits a user-configured amount of time, then starts the transmission. When the interface has finished transmitting, it waits a user-configured amount of time and then deasserts DCD.
Examples
The following examples place the interface in controlled-carrier mode and then back into constant-carrier operation.
This example shows changing to controlled-carrier mode from the default of constant-carrier operation:
Router(config)# interface serial 2Router(config-if)# half-duplex controlled-carrierThis example shows changing to constant-carrier operation from controlled-carrier mode:
Router(config)# interface serial 2Router(config-if)# no half-duplex controlled-carrierRelated Commands
half-duplex timer
To tune half-duplex timers, use the half-duplex timer command in interface configuration mode. To return to the default parameter values, use the no form of this command.
half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}
no half-duplex timer {cts-delay value | cts-drop-timeout value | dcd-drop-delay value | dcd-txstart-delay value | rts-drop-delay value | rts-timeout value | transmit-delay value}
Syntax Description
Defaults
The default cts-delay value is 0 ms.
The default cts-drop-timeout value is 250 ms.
The default dcd-drop-delay value is 100 ms.
The default dcd-txstart-delay value is 100 ms.
The default rts-drop-delay value is 3 ms.
The default rts-timeout value is 3 ms.
The default transmit-delay value is 0 ms.Command Modes
Interface configuration
Command History
Usage Guidelines
Tuning Half-Duplex Timers
The half-duplex timer command is used to tune half-duplex timers. With these timer tuning commands you can adjust the timing of the half-duplex state machines to suit the particular needs of their half-duplex installation.
You can configure more than one option using this command, but each option must be specified as a separate command.
Note
Value Ranges
The range of values for the cts-delay and rts-timeout keywords are dependent on the serial interface hardware.
Examples
The following example set the cts-delay timer to 10 ms and the transmit-delay timer to 50 ms:
Router(config)# interface serial 2Router(config-if)# half-duplex timer cts-delay 10Router(config-if)# half-duplex timer transmit-delay 50Related Commands
history (interface)
To enable an interface to maintain utilization history, use the history command in interface configuration mode. To disable an interface, use the no form of this command.
history {bps | pps} [filter]
no history
Syntax Description
bps
Maintains history in bits per second.
pps
Maintains history in packets per second.
filter
(Optional) Interface counters. See Table 4 for details. Any number of counters can be used.
Command Default
Interface utilization history is not maintained.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
Once interface history is configured, the interface history histograms can be displayed using the show interface history command.
Some of the interface counters are interface-type-specific and cannot be specified unless they apply to the specific interface type being configured. Once interface history is configured, counters cannot be added or removed without first removing the interface history configuration.
Significant processor memory is allocated to maintain the history information. For example, if two counters are monitored, then approximately 4KB are used for the rate and counter history. If 20 counters are monitored, then approximately 19KB are used.
Table 4 lists the interface counter options for the history (interface) command.
Table 4
Interface Counter Options For Interface History
Examples
The following example shows how to configure the interface history command to maintain interface utilization history in bits per second (bps) and also the input-drop history:
Router(config-if)# history bps input-dropsRelated Commands
hold-queue
To limit the size of the IP output queue on an interface, use the hold-queue command in interface configuration mode. To restore the default values, use the no form of this command.
hold-queue length {in | out}
no hold-queue {in | out}
Syntax Description
Defaults
Input hold-queue limit is 75 packets.
Output hold-queue limit is 40 packets.
Asynchronous interfaces default is 10 packets.Command Modes
Interface configuration
Command History
Usage Guidelines
Defaults
The default limits or this command prevent a malfunctioning interface from consuming an excessive amount of memory. There is no fixed upper limit to a queue size.
Back-to-Back Routing Updates
The default of 10 packets allows the Cisco IOS software to queue a number of back-to-back routing updates. This is the default for asynchronous interfaces only; other media types have different defaults.
Hold Queues and Priority Queueing
•
•
•
•
•
•
Caution
This is generally better than having duplicate copies of the same packet within the network (which can happen with large hold queues).
Examples
The following example shows how to set a small input queue on a slow serial line:
Router(config)# interface serial 0Router(config-if)# hold-queue 30 inRelated Commands
priority-list
Establishes queueing priorities based on the protocol type.
show interfaces
Displays statistics for all interfaces configured on the router or access server.
hssi external-loop-request
To allow the router to support a CSU/DSU that uses the loopback circuit (LC) signal to request a loopback from the router, use the hssi external-loop-request command in interface configuration mode. To disable this function, use the no form of this command.
hssi external-loop-request
no hssi external-loop-request
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
The HSA applique on the High-Speed Serial Interface (HSSI) contains an LED that indicates the loopback circuit A (LA), loopback circuit B (LB), and LC signals that are transiting through the devices. The CSU/DSU uses the LC signal to request a loopback from the router. The CSU/DSU may want to do this so that its own network management diagnostics can independently check the integrity of the connection between the CSU/DSU and the router.
Use this command to enable a two-way, internal, and external loopback request on the HSSI from the CSU/DSU.
Caution
enabling this function prevents spurious line noise from accidentally tripping the external
loopback request line, which would interrupt the normal data flow.
Examples
The following example enables a CSU/DSU to use the LC signal to request a loopback from the router:
Router(config-if)# hssi external-loop-requesthssi internal-clock
To convert the High-Speed Serial Interface (HSSI) into a clock master, use the hssi internal-clock command in interface configuration mode. To disable the clock master mode, use the no form of this command.
hssi internal-clock
no hssi internal-clock
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command in conjunction with the HSSI null-modem cable to connect two Cisco routers together with HSSI. You must configure this command at both ends of the link, not just one.
Note
the type of service to which it is connected.Examples
The following example shows how to convert the HSSI interface into a clock master:
Router(config-if)# hssi internal-clockhub
To enable and configure a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router, use the hub command in global configuration mode.
hub ethernet number port [end-port]
Syntax Description
Defaults
No hub ports are configured.
Command Modes
Global configuration
Command History
Usage Guidelines
This command does not have a no form.
Examples
The following example enables port 1 on hub 0:
Router# hub ethernet 0 1Router(config-hub)# no shutdownThe following example enables ports 1 through 8 on hub 0:
Router# hub ethernet 0 1 8Router(config-hub)# no shutdownRelated Commands
shutdown (hub)
Shuts down a port on an Ethernet hub of a Cisco 2505 or Cisco 2507 router.
hw-module boot
To specify the boot options for the module through the power management bus control register, use the hw-module boot command in privileged EXEC mode.
hw-module module num boot [value] {config-register | eobc | flash image | rom-monitor}
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
12.2(18)SXF
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
The valid values for the boot value argument are as follows:
0—Specifies the module's config-register value.
1—Specifies the first image in the Flash memory.
2—Specifies the second image in the Flash memory.
3—Stays in ROM-monitor mode after the module reset.
4—Specifies the download image through EOBC.
Examples
This example shows how to reload the module in slot 6 using the module's config-register value:
Router# hw-module module 1 boot config-registerRouter#This example shows how to reload the module in slot 3 using an image downloaded through EOBC:
Router# hw-module module 1 boot eobcRouter#Related Commands
showmodule
Displays the module status and information for all modules in the chassis.
hw-module energywise level
Note
To set the energywise level on the service module (SM), internal service module (ISM), or packet voice/data module (PVDM), use the hw-module energywise level command in privileged EXEC mode.
hw-module module-type slot-number energywise level level
Syntax Description
Command Default
The energywise level is 10.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the hw-module energywise level command in privileged EXEC mode to set the energywise level on the SM, ISM, or PVDM on your router. Specify the slot, and if applicable, the sub slot number for the module.
The energywise level supported for the module is specified by the module. The following table provides a definition for each energywise level:
0
Shut
1
Hibernate
2
Sleep
3
Standby
4
Ready
5
Low
6
Frugal
7
Medium
8
Reduced
9
High
10
Full
Note
Examples
The following example shows how to set the energywise level at shut on an SM in slot 1.
Router#hw-module sm 1 energywise level 0The following example shows how to set the energywise level at full on an SM in slot 1.
Router#hw-module sm 1 energywise level 10Related Commands
hw-module fan-tray version
To set the fan-type (high or low power) version, use the hw-module fan-tray version command in privileged EXEC mode.
hw-module fan-tray version [1 | 2]
Syntax Description
1 | 2
(Optional) Specifies the version number; see the "Usage Guidelines" section for additional information.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Before you install a high-capacity fan tray, enter the hw-module fan-tray version 2 command to check for configuration problems, such as power-supply compatbility and power sufficiency. If there are no problems, a message is displayed to change the fan tray from version 1 to version 2. At this point, you can remove the old fan tray and quickly insert the new high-capacity fan tray.
The hw-module fan-tray version 2 command aplies to Cisco 7600 series routers configured with a Supervisor Engine 2. This command is not required in systems configured with a Supervisor Engine 720 or a Supervisor Engine 32.
This command is supported on the following chassis:
•
•
•
Set the version to 2 before installing higher power fan trays.
Set the version to 1 before downgrading to lower power fan trays.
Command confirmation does not change the fan power consumption or cooling capacity. It updates the backplane IDPROM. The new values take effect the next time that you insert a fan.
When you execute the command, the software checks the configurations and prompts for confirmation. Any illegal configurations (such as power-supply incompatibility) result in a warning being displayed and a command failure.
Examples
This example shows how to set the fan type for lower power fan trays:
Router# hw-module fan-tray version 1Router#Related Commands
hw-module interface als restart
To request a restart pulse when Automatic Laser Shutdown (ALS) restart mode is configured as manual, use the hw-module interface TenGigabitEthernet als restart command in Privileged EXEC mode.
hw-module interface TenGigabitEthernet slot/port als restart
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
Examples
The following example shows how to request an ALS restart pulse for the Ten Gigabit Ethernet interface on slot 6 port number 2:
Router# hw-module interface TenGigabitEthernet 6/2 als restartRelated Commands
hw-module main-cpu qa error-recovery
To enable the recovery mechanism for a QA error condition on a Cisco 7500 series router, use the hw-module main-cpu qa error-recovery command in global configuration mode. To disable the recovery mechanism for a QA error condition, use the no form of this command.
hw-module main-cpu qa error-recovery
no hw-module main-cpu qa error-recovery
Syntax Description
This command has no arguments or keywords.
Defaults
In Cisco IOS Release 12.0(24)S1, the recovery mechanism for a QA error condition is disabled; in all other releases, it is enabled.
Command Modes
Global configuration
Command History
Usage Guidelines
QA errors are sometimes seen in heavy traffic situations and may indicate a hardware failure or a software bug. In the case of a hardware failure, a Versatile Interface Processor (VIP) or a Route Switch Processor (RSP) must be replaced. It is possible, however, to recover from a QA error and not see another error for months. When the same buffer header is present in two different queues, the QA ASIC goes into an error condition and triggers a QA error interrupt. The QA error interrupt causes the RSP to dump the QA diagnostics and perform a cbus complex during which all the line cards are reloaded. Although the duplicate buffer header condition does not always indicate a hardware failure, the downtime of up to 300 seconds creates a real problem in the network.
The hw-module main-cpu qa error-recovery command has been created to enable a recovery mechanism for a QA error by allowing the router to remove the duplicate buffer header from the queue that shows the problem and requeue the buffer header. By using the QA error recovery, the downtime is reduced to less than one second under lab conditions. Three QA errors caused by buffer headers are permitted before the router performs a cbus complex and reloads all the line cards.
After three QA errors caused by duplicate queued buffer headers occur, the cbus complex is initiated and the line cards reload. Other QA errors, such as a null buffer header on any queue, can occur. Recovery is not possible in these cases, and the QA error triggers a cbus complex and subsequent line-card reloads. The QA error condition is specific to the Cisco 7500 series routers.
Examples
The following example shows how to enable the QA error recovery mechanism when a Cisco IOS Release 12.0(24)S1 image is used on a Cisco 7500 series router. In all other supported releases, the QA error recovery mechanism is enabled by default.
Router(config)# hw-module main-cpu qa error-recoveryRelated Commands
hw-module oversubscription
To administratively disable the oversubscribed ports (3, 4, 7, and 8) on a module, use the hw-module oversubscription command. Use the no form of this command to enable the oversubscribed ports.
hw-module {module num} oversubscription
no hw-module
Syntax Description
Command Default
Oversubscription is enabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is supported on the WS-X6708-10G-3C and the WS-X6708-10G-3CXL modules only.
When you disable the oversubscribed ports, the port is put into shutdown mode. In this mode, you cannot enter the no shut command on the disabled ports. If you attempt to enter the no shut command on the disabled ports, this message appears:
The current module is operating in non-oversubscription mode. To utilise this interface, enable oversubscription mode for the module.When you enter the show interfaces command on the disabled ports, the output displays "disabled for performance" to distinguish between the normal port shutdown and the shutdown for performance.
Examples
This example shows how to administratively disable the oversubscribed ports on a module:
Router # hw-module module 3 oversubscriptionRouter #This example shows how to administratively enable the oversubscribed ports on a module:
Router # no hw-module module 3 oversubscriptionRouter #Related Commands
hw-module power-supply power-cycle
To power cycle the power supplies, use the hw-module power-supply power-cycle command in privileged EXEC mode.
hw-module power-supply {1 | 2} power-cycle
Syntax Description
Command Default
This command has no default settings.
Command Modes
Privileged EXEC (#)
Command History
12.2(18)SXF
Support for this command was introduced on the Supervisor Engine 720.
12.2(33)SRA
This command was integrated into Cisco IOS Release 12.2(33)SRA.
Usage Guidelines
If you have redundant power supplies and you power cycle one of the power supplies, only that power supply is power cycled. If you power cycle both power supplies, the system goes down and comes back up in 10 seconds.
If you only have one power supply and you power cycle that power supply, the system goes down and comes back up in 10 seconds.
This command works only on routers with an 8700 watt power supply.
Examples
This example shows how to power cycle a power supply:
Router# hw-module power-supply 2 power-cyclePower-cycling the power supply may interrupt service.Proceed with power-cycling? [confirm]Power-cycling power-supply 122:10:23: %C6KPWR-SP-2-PSFAIL: power supply 1 output failed.22:10:25: %C6KENV-SP-4-PSFANFAILED: the fan in power supply 1 has failed22:10:33: %C6KPWR-SP-4-PSOK: power supply 1 turned on.22:10:33: %C6KENV-SP-4-PSFANOK: the fan in power supply 1 is OKRouter#hw-module pxf stall-monitoring
To enable the parallel express forwarding (PXF) stall monitor on the Cisco 10000 series router, and configure the default threshold values for resetting the line card (LC) and the Hyper Transport Data Protocol (HTDP), use the hw-module pxf stall-monitoring command in the global configuration mode. To disable the PXF stall monitor, use the no form of this command.
hw-module pxf stall-monitoring [HT-Reset threshold value | LC-Reset threshold value]
no hw-module pxf stall-monitoring [HT-Reset threshold value | LC-Reset threshold value]
Syntax Description
Command Default
None
Command Modes
Global configuration (config)
Command History
Usage Guidelines
Initially, use the hw-module pxf stall-monitoring command to enable the PXF stall monitor on the Cisco 10000 series router. Then use the hw-module pxf stall-monitoring command again, to configure the threshold values of LC and HTDP reset.
Examples
The following example shows how to enable the PXF stall monitor, and configure the threshold values of LC and HTDP reset, using the hw-module pxf stall-monitoring command.
Router# configure terminalEnter configuration commands, one per line. End with CNTL/Z.Router(config)# hw-module pxf stall-monitoringRouter(config)# hw-module pxf stall-monitoring HT-Reset 5Router(config)# hw-module pxf stall-monitoring LC-Reset 4Related Commands
show pxf stall-monitoring
Displays the current configuration and the operating status of the PXF stall monitor.
hw-module reset
To reset a module by turning the power off and then on, use the hw-module reset command in privileged EXEC mode.
hw-module module num reset
Syntax Description
module num
Applies the command to a specific module; see the "Usage Guidelines" section for valid values.
Command Default
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The num argument designates the module number. Valid values depend on the chassis that is used. For example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
This example shows how to reload a specific module:
Router# hw-module module 3 resethw-module sec-cpu reset
To reset and reload the standby Route Switch Processor (RSP) with the specified Cisco IOS image and to execute the image, use the hw-module sec-cpu reset command in privileged EXEC mode.
hw-module sec-cpu reset
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Before using this command, you must use the hw-module slot image global configuration command to specify a high availability Cisco IOS image to run on the standby RSP. After the high availability image is loaded in the active RSP, use the hw-module sec-cpu reset command to reset and reload the standby RSP with the specified Cisco IOS image and to execute the image. To load the standby RSP with the default micro-IOS software contained in the active RSP image instead of a high availability Cisco IOS image, use the no form of the hw-module slot image command followed by the hw-module sec-cpu reset command.
Examples
The following example shows a Cisco 7513 router with the standby RSP loaded in slot 7. The standby RSP is reset and reloaded with the rsp-pv-mz high availability Cisco IOS image. Both RSPs have slot 0 flash memory cards.
Router(config)# hw-module slot 7 image slot0:rsp-pv-mzRouter(config)# endRouter# hw-module sec-cpu resetRelated Commands
hw-module slot image
Specifies a high availability Cisco IOS image to run on an active or standby RSP.
hw-module shutdown
To shut down the module, use the hw-module shutdown command in privileged EXEC mode.
hw-module module num shutdown
Syntax Description
module num
Applies the command to a specific module; see the "Usage Guidelines" section for valid values.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is supported on the SSL Services Module and the NAM.
If you enter the hw-module shutdown command to shut down the module, you will have to enter the no power enable module command and the power enable module command to restart (power down and then power up) the module.
Examples
This example shows how to shut down and restart the module:
Router# hw-module module 3 shutdownRouter# no power enable module 3Router# power enable module 3hw-module simulate link-up
To enable softlink on a specified module, use the hw-module simulate link-up command in privileged EXEC mode. For information on disabling softlink, refer to the "Usage Guidelines" section.
hw-module module num simulate link-up
Syntax Description
module num
Applies the command to a specific module; see the "Usage Guidelines" section for valid values.
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command is supported on Ethernet modules only.
To disable softlink on a module, you must perform one of the following procedures:
•
•
When you apply this command to a module, the port LEDs on the module will glow green and simulate a link-up condition. This command can be used for testing interface configurations without cabling to the interface.
The num argument designates the module number. Valid values depend on the chassis that is used. For example, if you have a 13-slot chassis, valid values for the module number are from 1 to 13.
Examples
This example shows how to enable softlink on a module:
Router# hw-module module 3 simulate link-upRouter#Related Commands
hw-module slot
To enable the router shelf to restart a stopped Dial Shelf Controller (DSC) card, to stop a DSC card, or to cause a shutdown, reset, or reload of any specified dial shelf feature board, use the hw-module slot command in privliged EXEC mode and global configuration mode.
hw-module slot shelf-id/slot-number {reload | reset | shutdown {powered | unpowered} [dual-wide] | start | stop}
Syntax Description
Command Default
Shuts down the DSC and all of its interfaces and leaves them in an administratively down state with power enabled.
Command Modes
Global configuration (config)
Privileged EXEC (#)Command History
Usage Guidelines
The stop form of this command is issued from the router shelf console instead of by pressing the attention (ATTN) button on the target DSC. Confirmation of when the start or stop took place is displayed. Warnings are issued and confirmation input is required if a stop command will result in a loss of service when backup functionality is not available.
When a DSC card is stopped, removed, and then reinstalled, there is no need to restart the card (whether the card is the original or a replacement) because a freshly installed card reboots as the backup DSC automatically. However, if a DSC is stopped, either by using the ATTN button or by issuing the hw-module slot stop command, it must be restarted by using the start form of the same command, or the DSC must be removed and reinstalled in order to reboot.
Press the ATTN button on the DSCs to shut down a card manually before removing the card. This is equivalent to issuing an hw-module slot command for that card at the router command prompt. Use the ATTN button to shut down the card before it is swapped out or tested in place, or to restart it, if the card has not been removed after having been shut down.
Tip
OIR event in the case of a feature board failure when physical access to the feature board card is restricted.Entering the hw-module slot shelf-id/slot-number reload command initiates the feature board reload process through power cycling. The hw-module slot shelf-id/slot-number reload command cannot be used to reload DSCs.
Use the reset form of this command to reset the specified feature card and drop all active calls.
Use the shutdown form of this command to shut down the specified feature card and drop all active calls.
Cisco 10000 Series Router Usage Guidelines,
In Cisco IOS Release 12.2(33)SB, when you enter the hw-module slot slot-number reset command, the software asks you to confirm the command.
In Cisco IOS Release 12.2(31)SB, the software does not ask you to confirm the hw-module slot slot-number reset command.
Examples
The following example shows how to stop the DSC in slot 13 and start the other DSC in slot 12 (which was previously stopped):
Router# hw-module slot 1/13 stopRouter# hw-module slot 1/12 startThe following example shows how to reload the dial shelf feature board in slot 6:
Router# hw-module slot 1/6 reloadThe following example shows how to reset the card in slot 3:
Router# hw-module slot 1/3 resetThe following example shows how to shut down the PRE card located in slot 3:
Router# hw-module slot 1/3 shutdown poweredRelated Commands
hw-module slot (6500)
To enable ports on a module, use the hw-module slot command. To disable ports on a module, use the no form of this command.
hw-module slot num {clear-block | oversubscription} [port-group num]
no hw-module slot num {clear-block | oversubscription} [port-group num]
Syntax Description
Command Default
The default settings are as follows:
•
•
Command Modes
Global configuration
Command History
Usage Guidelines
This command is supported on the following modules:
•
•
•
•
When you disable the oversubscribed ports, the port is put into shutdown mode. In this mode, you cannot enter the no shut command on the disabled ports. If you enter the no shut command on the disabled ports, this message appears:
The current module is operating in non-oversubscription mode. To utilise this interface, enable oversubscription mode for the module.When you enable oversubscription for a port group, the port group is in mux mode. When you disable oversubscription, the port group is in transparent mode. When a group is in transparent mode, the first port in the group retains its administrative status and the remaining three ports are administratively shut down. You cannot enter the shut, and then the no shut commands on the disabled ports. You can enter the shut, and then the no shut commands on the enabled port in the group.
The port-group mappings for the WS-X6716-10G-3C and the WS-X6716-10G-3CXL modules are as follows:
•
•
•
•
For the WS-X6716-10G-3C and the WS-X6716-10G-3CXL modules in transparent mode, ports 2, 3, 4, 6, 7, 8, 10, 11, 12, 14, 15, 16 are disabled.
If you specify a slot number without a group number, all four groups are put into transparent/mux mode.
You cannot put the port group into oversubscription mode when any port in the port group is configured as a virtual switch link (VSL). A warning message is displayed asking you to disable the VSL link before changing to oversubscription mode.
When you enter the show interfaces command on the disabled ports, the output displays "disabled for performance" to distinguish between the normal port shutdown and the shutdown for performance.
Each 4-port group shares a common packet queue. If head-of-line blocking is enabled and one port of the four ports receives a pause frame, all packets are blocked behind this packet until the packet is delivered to the flow-controlled port. You can enter the hw-module slot clear-block [port-group num] command to drop the packets that are destined for the jammed port and continue to deliver the packets for other ports.
Examples
This example shows how to administratively disable the oversubscribed ports on a module:
Router# no hw-module slot 3 oversubscriptionRouter#This example shows how to administratively disable the oversubscribed ports on a specific port group:
Router# no hw-module slot 3 oversubscription port-group 4Router#This example shows how to administratively enable the oversubscribed ports on a module:
Router# hw-module slot 3 oversubscriptionRouter#This example shows how to drop the packets that are destined for the jammed port and continue to deliver the packets for other ports:
Router# hw-module slot 3 clear-block port-group 4Router#Related Commands
show interfaces
Displays traffic that is seen by a specific interface.
show hw-module slot
Displays information for a SPA interface processor (SIP) or other module.
hw-module slot (7300)
To prepare a line card, MSC, or PCI port adapter carrier card for online removal, use the hw-module slot command in privileged EXEC mode.
hw-module slot slot-number {stop | start}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the hw-module slot slot-number stop command to stop traffic, turn on the green OIR LED, and shut down all interfaces to remove a line card, MSC, or PCI port adapter carrier card from the Cisco 7304 router without disrupting data flow. You should not remove hardware while traffic is still running.
The stop keyword stops traffic through interfaces and deactivates the hardware. When the OIR LED turns green, the hardware has been deactivated and can be physically removed.
The hw-module slot slot-number start command restarts the line card, MSC, or PCI port adapter carrier card and shuts off the OIR LED, putting the card back online.
Use the hw-module slot slot-number start command if you issue the hw-module slot slot-number stop command, did not remove the hardware, and now want to reactivate it. If you remove and then reinsert the hardware, the hardware restarts without this command.
This command cannot be used for online removal of SPAs. For online removal of SPAs, use the hw-module subslot command.
You can also use this command to restore a line card, MSC, or PCI port adapter carrier card that has been deactivated due to some failure.
Note
Examples
The following example shows how to deactivate the line card, MSC, or PCI port adapter carrier card in slot 2. After entering this command and the green OIR LED turns on, you can remove the hardware and insert a new piece of hardware:
Router# hw-module slot 2 stopThe following example shows how to reactivate a line card, MSC, or PCI port adapter carrier card in slot 2. You only need to enter this command if you enter the hw-module slot slot-number stop command but do not remove the hardware and instead want to restart the hardware.
Router# hw-module slot 2 startRelated Commands
hw-module slot (7600)
To enable ports on a module, use the hw-module slot command in global configuration mode. To disable the ports, use the no form of this command.
hw-module slot slot-number {memory test full | oversubscription | pos | process-max-time number-of-seconds | rate-limit {fsol_rate fsol-rate | punt_rate punt-packet-rate} | srp | subslot subslot-number only}
no hw-module slot slot-number {memory test | oversubscription | pos | process-max-time | rate-limit {rate-limit {fsol_rate fsol-rate | punt_rate punt-packet-rate} | srp | subslot subslot-number only}
Syntax Description
Command Default
Ports are not enabled on a module.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
•
•
•
Examples
The following example shows how to set the FSOL rate to 50000 b/s on the Cisco 7600:
Router(config)# hw-module slot 2 rate-limit fsol_rate 50000The following sample shows how to set the punt rate to 70000 b/s on the Cisco 7600:
Router(config)# hw-module slot 2 rate-limit punt_rate 70000Related Commands
show hw-module slot tech-support
Displays system information for a SIP or another module to troubleshoot a problem.
hw-module slot (ASR 1000 Series)
To start, stop, reload, or enable logging for an Embedded Services Processor (ESP), Route Processor (RP), or Shared Port Adapter (SPA) Interface Processor (SIP) on a Cisco ASR 1000 Series Aggregation Services Router, use the hw-module slot command in privileged EXEC or global configuration or diagnostic mode.
hw-module slot slot action
Syntax Description
Command Default
The router sends and receives traffic by default, so this command is not necessary to enable any hardware on a router.
Onboard logging for all of the hardware is enabled by default.Command Modes
Diagnostic (diag)
Privileged EXEC (#)
Global configuration (config)Command History
Usage Guidelines
The hw-module slot command does not have a no form.
To start, stop, or reload a SPA, use the hw-module subslot command.
The stop and reload options cannot be used on an active RP.
All traffic to hardware that has been set to stop using the stop option will be dropped until the hardware is reenabled by either physically removing and reinserting the hardware, or entering the start option. After the hardware is modified as appropriate or the start option is entered, the hardware has to reinitialize before it is able to send and receive traffic. Note that in some cases reinitialization can take several minutes, and that the reinitialization time required depends on the hardware and the system configuration.
When a SIP is stopped, all traffic to all SPAs in the SIP is dropped. The SPAs in the SIP can begin receiving traffic after the SIP is restarted using the start option and all SPAs and the SIP finish reinitializing.
Since this is a privileged EXEC-level command, this command setting cannot be saved to the startup configuration and therefore the command setting cannot be maintained after a system reload. If you want the hardware to stay in the stop state across system reloads, use the hw-module slot slot shutdown global configuration command.
The reload option can be used to reload hardware for any reason; for example, to finish a software upgrade that requires reloading of the hardware or to reload the hardware as part of a troubleshooting step.
The contents of onboard logging logs can be displayed using the show logging onboard slot privileged EXEC and diagnostic mode commands.
Enter the show logging onboard slot slot status privileged EXEC or diagnostic command to see if onboard logging is enabled or disabled for the hardware in a particular slot.
When the hw-module slot slot logging onboard disable command is entered, onboard logging for the specified hardware component is disabled but the existing logs are preserved; if you want to erase the existing logs, enter the clear logging onboard slot command.
When the hw-module slot command is entered in global configuration mode (for ESP40 and SIP40 cards), you have a link option that allows you to choose among a set of backplane enhanced serializer/deserializer (SerDes) interconnect (ESI) links between ESP and a given SIP slot. The range of possible values for the link depends on the type of ESP and SIP cards. Only a combination of ESP40 and SIP40 cards can have more than two ESI links (link A and link B). All other cards have only link A. For example, a combination of ESP40 and SIP10 or ESP20 and SIP40 cards can have only one link (link A).
Examples
The following example shows how to stop the RP in RP slot 0:
Router# hw-module slot r0 stopThe following example shows how to disable the onboard logging for the RP in RP slot 0. The output of the show logging onboard slot r0 status command is given both before and after onboard logging is disabled to verify that onboard logging was properly disabled.
Router# show logging onboard slot r0 statusStatus: EnabledRouter# hw-module slot r0 logging onboard disableRouter# show logging onboard slot r0 statusStatus: DisabledThe following example shows how to display the available link options for ESP40 and SIP40 cards:
Router(config)# hw-module slot 0 qos input link ?A ESI Link AB ESI Link BRelated Commands
hw-module slot image
To specify a high availability Cisco IOS image to run on an active or standby Route Switch Processor (RSP), use the hw-module slot image command in global configuration mode. To remove a high availability Cisco IOS image from the running configuration, use the no form of this command.
hw-module slot slot-number image file-spec
no hw-module slot slot-number image file-spec
Syntax Description
slot-number
Specifies the number of the RSP slot.
file-spec
Specifies the flash memory card location to load the image into and the name of the image.
Defaults
No high availability Cisco IOS images are specified to run on the active or standby RSPs.
Command Modes
Global configuration
Command History
12.0(16)ST
This command was introduced.
12.3(7)T
This command was integrated into Cisco IOS Release 12.3(7)T.
Examples
The following example shows a Cisco 7513 router with the active RSP loaded in slot 6 and the standby RSP loaded in slot 7. The rsp-pv-mz high availability Cisco IOS image is specified to run on both the active and the standby RSP. Both RSPs have slot 0 flash memory cards.
Router(config)# hw-module slot 6 image slot0:rsp-pv-mzRouter(config)# hw-module slot 7 image slot0:rsp-pv-mzRelated Commands
hw-module slot subslot only
To change the mode of the Cisco 7600 SSC-400 card to allocate full buffers to the specified subslot, use the hw-module slot subslot only command in global configuration mode. If this command is not used, the total amount of buffers available is divided between the two subslots on the Cisco 7600 SSC-400.
Note
hw-module slot slot subslot subslot only
Syntax Description
Defaults
No default behavior or values.
Command Modes
Global configuration mode
Command History
Usage Guidelines
Follow these guidelines and restrictions when configuring a Cisco 7600 SSC-400 and IPSec VPN SPAs using the hw-module slot subslot only command:
•
•
Module n will be reset? Confirm [n]:
The prompt will default to "N" (no). You must type "Y" (yes) to activate the reset action.
•
Examples
The following example allocates full buffers to the SPA that is installed in subslot 0 of the SIP located in slot 1 of the router and takes a reset action of the Cisco 7600 SSC-400.
Router(config)# hw-module slot 4 subslot 1 onlyModule 4 will be reset? Confirm [no]: yNote that the prompt will default to "N" (no). You must type "Y" (yes) to activate the reset action.
Related Commands
ip multicast-routing
Enables IP multicast routing.
ip pim
Enables Protocol Independent Multicast (PIM) on an interface.
hw-module standby
To reset the standby Route Processor (RP), use the hw-module standby command in privileged EXEC mode.
hw-module standby {reset | reload}
Syntax Description
Defaults
No default behavior or values.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to reset or reload the standby RP. Use the reload keyword to cause the standby RP to reload with an upgraded image. Use this option when the standby RP is operating normally. Use the reset keyword for a hard reset of the standby RP. Use this option if the standby RP is experiencing problems and does not respond to the reload option.
Examples
The following example shows how to reset the standby RP (NSE-100):
Router# hw-module standby resetProceed with reset of standby NSE? [confirm]yThe following example shows an attempt to reset a standby RP, which is down or experiencing some other problem such as being hung.
Router# hw-module standby reloadProceed with reload of standby NSE? [confirm]y%Standby RP is not upIf there is a failure to reset a standby RP because it is in some fault condition, try performing a reload of the RP.
The following example shows how to reload the standby RP:
Router# hw-module standby reloadProceed with reload of standby NSE? [confirm]yRelated Commands
hw-module subslot
To restart, stop, or start a shared port adapter (SPA) and its interfaces, use the hw-module subslot command in privileged EXEC mode.
hw-module subslot slot/subslot {reload [force] | start | stop [force]}
Syntax Description
Command Default
The SPA and its interfaces are not started.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
The hw-module subslot command stops and starts power to the SPA. This command is useful when you want to restart all interfaces on a SPA. When the stop and reload keywords are used, you get a prompt to confirm. Enter "y" or use the return key to confirm. Power to the SPA is now stopped or reloaded. If you use the force keyword along with the reload keyword, you can proceed further without getting any prompt for confirmation. The Excalibur and Ethernet Services cards do not have the reload option.
The command is recommended to restart a SPA under the following conditions:
•
•
Examples
The following command power cycles the SPA in subslot 1 of the SIP installed in chassis slot 1:
Router# hw-module subslot 1/1 reloadProceed with reload of module? [confirm]Related Commands
hw-module subslot ethernet vlan unlimited
To remove the restriction of a maximum of 8100 IEEE 802.1Q VLANs per Ethernet shared port adapter (SPA), use the hw-module subslot ethernet vlan unlimited command in global configuration mode. To disable and return to a maximum limit of 8100 VLANs per SPA, use the no form of this command.
hw-module subslot slot/subslot ethernet vlan unlimited
no hw-module subslot slot/subslot ethernet vlan unlimited
Syntax Description
slot/
Specifies the chassis slot number where the SIP is installed.
subslot
Specifies the slot of the SIP where the SPA is installed.
Command Default
There is no default behavior or values. When this command is not configured, up to 8100 dot1q VLANs per Ethernet SPA are supported.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
For any Ethernet SPA on the Cisco ASR 1000 Series aggregation services routers, the maximum number of IEEE 802.1Q VLANs that can be configured per port is 4094. The default total maximum number of VLANs per SPA is 8100.
The limit on this total maximum number of VLANs per SPA ( which means, the default of 8100 VLANs) can be removed using the hw-module subslot ethernet vlan unlimited command. However, the limit on the maximum number of VLANs per Ethernet port or interface (i.e. 4094) still applies. Therefore, the new maximum number of supported VLANs per SPA varies by the number of ports on the SPA multiplied by 4094. On the 5-Port Gigabit Ethernet SPA, you can configure up to 20,470 dot1q (or unambiguous QinQ) VLANs. On an 8-Port Gigabit Ethernet SPA, you can configure up to 32752 dot1q (or unambiguous QinQ) VLANs.
When the hw-module subslot ethernet vlan unlimited command is configured, VLAN filtering, accounting, and classification are no longer performed by the Ethernet SPA and all 802.1Q frames and QinQ frames are processed by the Quantum Flow Processor (QFP) on the Cisco ASR1000 Series Router. Sending all of the dot1q VLAN frames to the QFP (without filtering) may reduce the QFP packet switching performance.
The default classification of CoS bits 6-7 as high priority is still supported. However, other user-defined CoS values for high and low priority classification using the plim qos input map cos queue command are not supported when this command is in use.
Examples
The following example enables support for maximum per-port dot1q VLAN configuration for the SPA located in the first subslot (0) of the SIP located in slot 1 of the Cisco ASR1000 Series Router:
Router(config)# hw-module subslot 1/0 ethernet vlan unlimitedRelated Commands
show interfaces
Displays statistics for all interfaces configured on the router.
hw-module subslot (LAN/WAN)
To configure the Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter to run in either the LAN mode or WAN mode, use the hw-module subslot slot/subslot enable {LAN | WAN} command in Global configuration mode.
hw-module subslot slot/subslot enable {LAN | WAN}
Syntax Description
Command Default
By default, the Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter operates in the WAN mode when the SPA boots-up.
Command Modes
Global configuration (config)
Command History
Cisco IOS XE Release 3.3.0S
This command was introduced on the Cisco ASR 1000 Series Routers.
Usage Guidelines
By default, the Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter initializes in the WAN mode. The Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter can operate in either the LAN mode or the WAN mode. To change the LAN mode or WAN mode, execute the hw-module subslot slot/subslot enable {LAN | WAN} command from the Global configuration mode.
Examples
The following example shows how to enable the LAN mode on a Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter:
Router# configRouter(config)# hw-module subslot 2/1 enable LANThe following example shows how to enable the WAN mode on a Cisco 1-Port 10 Gigabit Ethernet LAN/WAN-PHY Shared Port Adapter:
Router# configRouter(config)# hw-module subslot 2/1 enable WAN
Tip
Related Commands
show controllers wanphy
Displays the SPA mode (LAN mode or WAN mode), alarms, and the J1 byte string value.
hw-module subslot service-engine session
To open a console session to access the Cisco WebEx Node SPA console, use the hw-module subslot service-engine session command in privileged EXEC mode.
hw-module subslot slot/subslot service-engine session
Syntax Description
slot
Specifies the chassis slot number for the Cisco ASR 1000 Series Router SIP.
/subslot
Specifies the secondary subslot number on a Cisco ASR 1000 Series Router SIP where a SPA is installed.
Command Default
No command default.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
To open a console session on a Cisco WebEx Node SPA, the SPA must first be configured with a minimum of the following commands:
•
•
•
The service-engine ip address command must be configured before the service-engine default-gateway command.
Examples
The following example shows how to access the console for a WebEx Node SPA located in slot 1/0, and the change to the SPA console prompt (service-spa is the default hostname) when complete:
Router# hw-module subslot 1/0 service-engine sessionMontaVista(R) Linux(R) Carrier Grade Edition 5.0 (custom)Linux/mips64 2.6.21_mvlcge500-octeon-mips64_octeon_v2_beVegas Shell -- CGE 5.0 VersionCopyright (c) 1985-2008 by Cisco Systems, Inc.All rights reserved.service-spa#Related Commands
hw-module subslot shutdown
To disable a shared port adapter (SPA) with or without power, and save the configuration to the configuration file, use the hw-module subslot shutdown command in global configuration mode. To re-enable the SPA, use the no form of this command.
hw-module subslot slot/subslot shutdown [powered | unpowered]
no hw-module subslot slot/subslot shutdown [powered | unpowered]
Syntax Description
Defaults
If this command is not used, no hw-module subslot shutdown is the default behavior. When no hw-module subslot is configured, the SPA will be powered for normal operation.
If the hw-module subslot shutdown command is entered but neither powered or unpowered are specified in the CLI, powered is the default behavior.
Command Modes
Global configuration
Command History
Usage Guidelines
When you shut down a SPA using this command, you can choose to put it into one of two states:
•
•
This command is useful when a user wants all the interfaces on a SPA disabled but does not or cannot remove the SPA. Unlike the hw-module subslot stop EXEC command on the Cisco 7304 router, this command is saved in the configuration file and will keep the SPA disabled when other router events (such as a router reload or OIR) attempt to restart the SPA. All other settings and configurations of the SPA will be maintained even if the SPA itself is shutdown using this command.
As a general rule, you do not need to shut down a SPA if you are removing it and replacing it with the same exact model of SPA in an online insertion and removal (OIR) operation. However, you should shut down a SPA whenever you are replacing a SPA with a different model of SPA.
When you shut down a SPA using the hw-module subslot shutdown command, it remains shutdown even if you reset the router or install a new SPA in that subslot. To begin using the card again, you must manually re-enable the card using the no hw-module subslot shutdown command.
Note
Examples
The following example shows how to disable the SPA in subslot 4/1 while leaving the SPA in the router chassis. This command will be saved to the configuration file and no actions, outside of changing this configuration, will re-enable the SPA:
Router(config)# hw-module subslot 4/1 shutdown unpoweredThe following example shows how to configure the SPA to resume normal operation after the unpowered option has been used to disable the SPA:
Router(config)# hw-module subslot 4/1 shutdown poweredNo messages are provided on the console when you shut down or re-enable a SPA.
Related Commands
show hw-module subslot oir
Displays the operational status of a SPA.
hw-module slot1
Deactivates or reactivates a carrier card that is installed in a router slot. This command is entered in EXEC mode and is not saved to the configuration file.
1 Refer to the Cisco 7300 Series Platform-Specific Commands publication.
