-
Cisco IOS Interface and Hardware Component Command Reference, Release 12.3 T
-
Introduction
-
Interface and Hardware Component Commands: A through C
-
Interface and Hardware Component Commands: D through H
-
Interface and Hardware Component Commands: I through L
-
int_m1gt_1
-
Interface and Hardware Component Commands: M through R
-
Interface and Hardware Component Commands: scramble through show chassis
-
Interface and Hardware Component Commands: show compress through show hub
-
Interface and Hardware Component Commands: show interfaces through show interfaces vg-anylan
-
Interface and Hardware Component Commands: show ipc through syscon source-interface
-
Interface and Hardware Component Commands: T through Y
-
Table Of Contents
main-fiber port
To specify the port number to use for the optical link connection on the SDH/STM-1 trunk card on a Cisco AS5850, use the main-fiber port command in controller configuration mode.
main-fiber port {0 | 1}
Syntax Description
0
Specifies use of port 0 as the optical link connection. This is the default.
1
Specifies use of port 1 as the optical link connection.
Defaults
Port 0
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the main-fiber controller configuration command if you need to use optical port 1 during installation of the SDH/STM-1 trunk card on a Cisco AS5850 or if you suspect some problem with optical port 0.
This command does not have a no form. To restore the default value, use the main-fiber port 0 command.
Examples
The following example selects port 1 as the port with the optical connection:
Router(config)# controller sonet 1/0Router(config-controller)# main-fiber port 1mdl
To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification, use the mdl command in controller configuration mode. To remove the message, use the no form of this command.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
no mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port | generator} string}
Syntax Description
Defaults
No MDL message is configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
Use the show controllers t3 command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.
Note
MDL is supported only when the DS3 framing is C-bit parity.
Examples
The following example shows the mdl commands on a T3 controller in slot 1, port 0:
Router(config)# controller t3 1/0Router(config-controller)# clock source lineRouter(config-controller)# mdl string eic IDRouter(config-controller)# mdl string fic Building BRouter(config-controller)# mdl string unit ABCRouter(config-controller)# mdl string pfi Facility ZRouter(config-controller)# mdl string port Port 7Router(config-controller)# mdl transmit pathRouter(config-controller)# mdl transmit idle-signalRelated Commands
media-type
To specify the physical connection on an interface, use the media-type command in interface configuration mode. To restore the default value, use the no form of this command.
media-type {aui | 10baset | 100baset | mii}
no media-type {aui | 10baset | 100baset | mii}
Syntax Description
Defaults
An AUI 15-pin physical connection is the default setting on Cisco 4000 series routers.
A 100BASE-T physical connection is the default setting on Cisco 7000 series and Cisco 7200 series routers.Command Modes
Interface configuration
Command History
Usage Guidelines
To specify the physical connection on an interface, use the following interface configuration:
•
•
•
Examples
The following example selects an RJ-45 10BASE-T physical connection on Ethernet interface 1:
Router(config)# interface ethernet 1Router(config-if)# media-type 10basetThe following example specifies a media-independent interface physical connection to Fast Ethernet slot 0, port 1 on the Cisco 7000 or Cisco 7200 series:
Router(config)# interface fastethernet 0/1Router(config-if)# media-type miiThe following example specifies a media-independent interface physical connection to Fast Ethernet slot 0, port adapter 1, port 1 on the Cisco 7500 series:
Router(config)# interface fastethernet 0/1/1Router(config-if)# media-type miimicrocode reload controller
To reload the firmware and field programmable gate array (FPGA) without reloading the Cisco IOS image, use the microcode reload controller command in privileged EXEC mode.
microcode reload controller j1 slot/port
Syntax Description
Defaults
No microcode reload activity is initiated.
Command Modes
Privileged EXEC
Command History
12.1(2)XH
This command was introduced.
12.1(3)T
This command was integrated into Cisco IOS Release 12.1(3)T.
12.2(8)T
The j1 keyword was added.
Usage Guidelines
Configurations such as loopbacks in the running configuration are restored after this command is entered. If the controller is in a looped state before this command is issued, the looped condition is dropped. You have to re-initiate the loopbacks from the remote end by doing no loop from the controller configuration.
Examples
The following example show how to start the microcode reload activity:
Router# microcode reload controller j1 3/0TDM-connections and network traffic will be briefly disrupted.Proceed with reload microcode?[confirm]Router#*Mar 3 209.165.200.225: clk_src_link_up_down: Status of this CLK does not matter*Mar 3 209.165.200.226: clk_src_link_up_down: Status of this CLK does not matter*Mar 3 209.165.200.227: %CONTROLLER-5-UPDOWN: Controller J1 3/0, changed state to) *Mar 3 209.165.200.227: clk_src_link_up_down: Status of this CLK does not matter*Mar 3 209.165.200.228: clk_src_link_up_down: Status of this CLK does not matter*Mar 3 209.165.200.229: %CONTROLLER-5-UPDOWN: Controller J1 3/0, changed state top *Mar 3 209.165.200.229: clk_src_link_up_down: Status of this CLK does not matter*Mar 3 209.165.200.229: clk_src_link_up_down: Status of this CLK does not mattermode (ATM/T1/E1 controller)
To set the DSL controller into ATM mode and create an ATM interface or to set the T1 or E1 controller into T1 or E1 mode and create a logical T1/E1 controller, use the mode command in controller configuration mode. To disable the current mode and prepare to change modes, use the no form of this command.
Cisco 3700 Series, Cisco 2800 Series, Cisco 3800 Series
mode atm
no mode atm
Cisco 1700 Series, Cisco 2600XM Platform,
mode {atm | t1 | e1}
no mode {atm | t1 | e1}
Cisco IAD2430
mode {atm [aim aim-slot] | cas | t1 | e1}
no mode {atm [aim aim-slot] | cas | t1 | e1}
Syntax Description
Defaults
The controller mode is disabled.
Command Modes
Controller configuration
Command History
Usage Guidelines
When a DSL controller is configured in ATM mode, the mode must be configured identically on both the CO and CPE sides. Both sides must be set to ATM mode.
Note
When configuring a DSL controller in T1 or E1 mode, the mode must be configured identically on the CPE and CO sides.
Examples
ATM Mode Example
The following example configures ATM mode on the DSL controller.
Router(config)# controller dsl 3/0Router(config-controller)# mode atmT1 Mode Example
The following example configures T1 mode on the DSL controller.
Router(config)# controller dsl 3/0Router(config-controller)# mode t1Related Commands
mode download
To enable operational code download mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the mode download command in satellite initial configuration mode. To disable operational code download mode, use the no form of this command.
mode download
no mode download
Syntax Description
This command has no arguments or keywords.
Defaults
Operational code download mode is enabled.
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to disable operational code download mode:
Router(sat-init-config)# no mode downloadmode (HSA redundancy)
To configure the redundancy mode, use the mode command in redundancy configuration mode. To configure the default redundancy mode, use the no form of this command.
mode {hsa | rpr | rpr-plus}
no mode {hsa | rpr | rpr-plus}
Syntax Description
hsa
Selects High System Availability (HSA) redundancy mode. This is the default.
rpr
Selects Route Processor Redundancy (RPR) mode.
rpr-plus
Selects RPR Plus (RPR+) redundancy mode.
Defaults
HSA redundancy mode
Command Modes
Redundancy configuration
Command History
Usage Guidelines
The mode selected by the mode command in redundancy configuration mode must be fully supported by the image that has been installed in both the active and standby Route Switch Processors (RSPs). A high availability image must be installed in the RSPs before RPR+ can be configured. Use the hw-module slot image command to specify a high availability image to run on the standby RSP.
If the mode cannot be set on both RSPs, HSA is the default mode. A Cisco 7507 or Cisco 7513 router that has only one RSP installed operates in single Route Processor mode.
Examples
The following example enters redundancy configuration mode and sets RPR+ as the redundancy mode for a Cisco 7500 series router.
Router(config)# redundancyRouter(config-r)# mode rpr-plusRouter(config-r)# endRelated Commands
mode (RSC redundancy)
To choose between classic-split mode (maximum throughput with no load sharing) and handover-split mode (maximum availability with load sharing), use the mode command in redundancy configuration mode. To reset to the default mode, use the no form of this command.
mode {classic-split | handover-split}
no mode
Syntax Description
Defaults
Classic-split mode
Command Modes
Redundancy configuration
Command History
12.2(2)XB1
This command was introduced.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
You must be connected to an RSC card on your Cisco AS5850 to use this command.
Examples
The following example selects handover-split mode:
Router(config)# redundancyRouter(config-r)# mode handover-splitRelated Commands
mode (T1/E1 controller)
To set the T1 or E1 controller into asynchronous transfer mode (ATM) and create an ATM interface, to set the T1 or E1 controller into T1 or E1 mode and create a logical T1 or E1 controller, or to set the T1 or E1 controller into channel-associated signaling (CAS) mode, use the mode command in controller configuration mode. To disable the current mode and prepare to change modes, use the no form of this command.
mode {atm [aim aim-slot] | cas | t1 | e1}
no mode {atm [aim aim-slot] | cas | t1 | e1}
Syntax Description
Defaults
No controller mode is configured.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command has the following platform-specific usage guidelines:
Cisco 2600 Series, Cisco 3660 Routers, or Cisco 3700 Series Rotuers That Use AIM for ATM Processing
You must use the mode atm aim aim-slot command.
Cisco 2600 Series Routers: For AIM for DSP Processing and That Specify DS0 Groups
You must use the mode cas command if using WIC slots for voice. This command does not apply if network modules are being used.
Cisco 3660 Routers or Cisco 3700 Series That Use an AIM Only for DSP Resources
Do not use this command.
On Cisco 2600 Series Routers That Use WIC Slots for Voice
The mode atm command without the aim keyword specifies software ATM segmentation and reassembly. When the aim keyword is used with the mode atm command, the AIM performs ATM segmentation and reassembly.
On Cisco 2600 Series and Cisco 3700 Series Routers That Configure a DSL Controller in ATM Mode,
The mode must be set to the same mode on both the CO and CPE sides. Both sides must be set to ATM mode.
If the no mode atm command is used to leave ATM mode, the router must be rebooted immediately to clear the mode.
On Cisco 2600 Series and Cisco 3700 Series RoutersWith a DSL Controller in T1 or E1 Mode
The mode must be configured identically on the CO and CPE sides.
Examples
ATM Mode for Voice Over ATM
The following example configures ATM mode on controller T1 0. This step is required for Voice over ATM.
Router(config)# controller t1 0Router(config-controller)# mode atmATM Mode on Cisco 2600 Series Router with AIM
The following example configures ATM mode on controller T1 1/ 0 on a Cisco 2600 series router using an AIM in slot 0 for ATM segmentation and reassembly:
Router(config)# controller t1 1/0Router(config-controller)# mode atm aim 0ATM Mode on DSL Controller
The following example configures ATM mode on the DSL controller.
Router(config)# controller dsl 3/0Router(config-controller)# mode atmCAS Mode on T1 Controller
The following example configures CAS mode on controller T1 1 on a Cisco 2600 series router:
Router(config)# controller t1 1Router(config-controller)# mode casT1 Mode on DSL Controller
The following example configures T1 mode on the DSL controller.
Router(config)# controller dsl 3/0Router(config-controller)# mode t1Related Commands
mode two-way
To enable two-way operational mode for the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the mode two-way command in satellite initial configuration mode. To revert to one-way operational mode, use the no form of this command.
mode two-way
no mode two-way
Syntax Description
This command has no arguments or keywords.
Defaults
Two-way mode is enabled.
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify two-way operational mode:
Router(sat-init-config)# mode two-wayThe following example shows how to specify one-way operational mode:
Router(sat-init-config)# no mode two-waymodem dtr-delay
To control the time that a data terminal ready (DTR) signal is held down when a line clears, use the modem dtr-delay command in line configuration mode. To restore the default hold down time, use the no form of this command.
modem dtr-delay seconds
no modem dtr-delay seconds
Syntax Description
Defaults
The default DTR signal hold down time is 5 seconds.
Command Modes
Line configuration
Command History
Usage Guidelines
Use this command to reduce the time that a DTR signal is held down after an asynchronous line clears and before the DTR signal is raised again to accept new calls. Incoming calls may be rejected in heavily loaded systems even when modems are unused because the default DTR hold down interval may be too long. The modem dtr-delay command is designed for lines used for an unframed asynchronous session such as Telnet. Lines used for a framed asynchronous session such as PPP should use the pulse-time interface command.
Examples
The following example shows how to specify a DTR hold down interval of 2 seconds:
Router(config)# line 7Router(config-line)# modem dtr-delay 2Related Commands
mop enabled
To enable an interface to support the Maintenance Operation Protocol (MOP), use the mop enabled command in interface configuration mode. To disable MOP on an interface, use the no form of this command.
mop enabled
no mop enabled
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled on Ethernet interfaces and disabled on all other interfaces.
Command Modes
Interface configuration
Command History
Examples
The following example enables MOP for serial interface 0:
Router(config)# interface serial 0Router(config-if)# mop enabledRelated Commands
mop sysid
To enable an interface to send out periodic Maintenance Operation Protocol (MOP) system identification messages, use the mop sysid command in interface configuration mode. To disable MOP message support on an interface, use the no form of this command.
mop sysid
no mop sysid
Syntax Description
This command has no arguments or keywords.
Defaults
Enabled
Command Modes
Interface configuration
Command History
Usage Guidelines
You can still run MOP without having the background system ID messages sent. This command lets you use the MOP remote console, but does not generate messages used by the configurator.
Examples
The following example enables serial interface 0 to send MOP system identification messages:
Router(config)# interface serial 0Router(config-if)# mop sysidRelated Commands
mop device-code
Identifies the type of device sending MOP sysid messages and request program messages.
Enables an interface to support the MOP.
mtu
To adjust the maximum packet size or maximum transmission unit (MTU) size, use the mtu command in interface configuration mode. To restore the MTU value to its original default value, use the no form of this command.
mtu bytes
no mtu
Syntax Description
Defaults
Table 12 lists default MTU values according to media type.
Table 12 Default Media MTU Values
Ethernet
1500
Serial
1500
Token Ring
4464
ATM
4470
FDDI
4470
HSSI (HSA)
4470
Command Modes
Interface configuration
Command History
Usage Guidelines
Each interface has a default maximum packet size or MTU size. This number generally defaults to the largest size possible for that interface type. On serial interfaces, the MTU size varies, but cannot be set smaller than 64 bytes.
Note
resetting of all interfaces. The following message is displayed:
%RSP-3-Restart:cbus complex.Protocol-Specific Versions of the mtu Command
Changing the MTU value with the mtu interface configuration command can affect values for the protocol-specific versions of the command (the ip mtu command, for example). If the value specified with the ip mtu interface configuration command is the same as the value specified with the mtu interface configuration command, and you change the value for the mtu interface configuration command, the ip mtu value automatically matches the new mtu interface configuration command value. However, changing the values for the ip mtu configuration commands has no effect on the value for the mtu interface configuration command.
ATM and LANE Interfaces
ATM interfaces are not bound by what is configured on the major interface. By default, MTU on a subinterface is equal to the default MTU (4490); if a client is configured the default is 1500. MTU can be changed on subinterfaces, but it may result in recarving of buffers to accommodate the new maximum MTU on the interface.
Examples
The following example specifies an MTU of 1000 bytes:
Router(config)# interface serial 1Router(config-if)# mtu 1000Related Commands
encapsulation smds
Enables SMDS service on the desired interface.
ip mtu
Sets the MTU size of IP packets sent on an interface.
national bit (controller)
To set the E3 national bit in the G.751 frame used by the E3 controller, use the national bit command in controller configuration mode. To return to the default E3 controller national bit, use the no form of this command.
national bit {0 | 1}
no national bit
Syntax Description
0
Sets the E3 national bit in the G.751 frame to 0.
1
Sets the E3 national bit in the G.751 frame to 1. This is the default.
Defaults
The default value is 1.
Command Modes
Controller configuration
Command History
Usage Guidelines
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.
To verify the national bit configured on the interface, use the show controllers serial EXEC command.
Examples
The following example sets the national bit to 1 on an E3 controller in slot 1, port 0:
Router(config)# controller e3 1/0Router(config-controller)# national bit 1Related Commands
national bit (interface)
To set the E3 national bit in the G.751 frame used by the PA-E3 port adapter, use the national bit command in interface configuration mode. To return to the default E3 interface national bit, use the no form of this command.
national bit {0 | 1}
no national bit
Syntax Description
0
Sets the E3 national bit in the G.751 frame to 0. This is the default.
1
Sets the E3 national bit in the G.751 frame to 1.
Defaults
The default value is 0.
Command Modes
Interface configuration
Command History
Usage Guidelines
The national bit command sets bit 12 in the E3 frame.
To verify the national bit configured on the interface, use the show controllers serial EXEC command.
Examples
The following example sets the national bit to 1 on the PA-E3 port adapter in slot 1, port adapter slot 0, interface 0:
Router(config)# interface serial 1/0/0Router(config-if)# national bit 1Related Commands
national reserve
To set the E1 national bit, use the national reserve command in interface configuration mode. To return to the default E1 national bit, use the no form of this command.
national reserve {0 | 1}{0 | 1}{0 | 1}{0 | 1}{0 | 1}{0 | 1}
no national reserve
Syntax Description
0
Sets any of the six required E1 national bits in the G.751 frame to 0.
1
Sets any of the six required E1 national bits in the G.751 frame to 1. This is the default.
Defaults
111111
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies only for E1. This command not only sets the national reserve bits but also sets the international bit as well. The far left digit represents the international bit. All six digits must be present for the pattern to be valid.
Examples
On Cisco 7100 series routers, the following example sets the E1 national bit on interface 1 on the port adapter in slot 0 to no scrambling:
Router(config)# interface atm 1/0Router(config-if)# national reserve 011011negotiation
To configure speed, duplex, and flow control on the Gigabit Ethernet port of the Cisco 7200-I/O-GE+E, use the negotiation command in interface configuration mode. To disable automatic negotiation, use the no negotiation auto command.
negotiation {forced | auto}
no negotiation auto
Syntax Description
Defaults
auto
Command Modes
Interface configuration
Command History
Usage Guidelines
The negotiation command is applicable only to the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E. The negotiation auto command is used instead of the duplex and speed commands (which are used on Ethernet and Fast Ethernet interfaces) to automatically configure the duplex and speed settings of the interfaces. The negotiation forced command is used to configure the Gigabit Ethernet interface to be 1000/full-duplex only and to disable flow control. The Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E is restricted to 1000 Mbps/full duplex only. Autonegotiation negotiates only to these values.
Examples
The following example configures the Gigabit Ethernet interface of the Cisco 7200-I/O-GE +E to autonegotiate:
Router(config)# interface gigabitethernet 0/0Router(config-if)# negotiation autoRelated Commands
show interfaces gigabitethernet
Displays the status and configuration settings of the Gigabit Ethernet interface of the Cisco 7200-I/O-GE+E.
nrzi-encoding
To enable nonreturn-to-zero inverted (NRZI) line-coding format, use the nrzi-encoding command in interface configuration mode. To disable this capability, use the no form of this command.
nrzi-encoding [mark]
no nrzi-encoding
Syntax Description
Defaults
Disabled
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
11.3
The mark keyword was added for the Cisco 7200 series routers and Cisco 7500 series routers.
Usage Guidelines
All FSIP, PA-8T, and PA-4T+ interface types support nonreturn-to-zero (NRZ) and NRZI format. This is a line-coding format that is required for serial connections in some environments. NRZ encoding is most common. NRZI encoding is used primarily with EIA/TIA-232 connections in IBM environments.
Examples
The following example configures serial interface 1 for NRZI encoding:
Router(config)# interface serial 1Router(config-if)# nrzi-encodingThe following example configures serial interface 3/1/0 for NRZI mark encoding:
Router(config)# interface serial 3/1/0Router(config-if)# nrzi-encoding markoutbound data-pid
Note
To specify the outbound data packet identification (PID) number, use the outbound data-pid command in satellite initial configuration mode. To remove the PID number configuration, use the no form of this command.
outbound data-pid number
no outbound data-pid
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
12.3(14)T
This command was introduced.
12.4(2)T
This command was superseded by the outbound pid management command.
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the outbound data PID number:
Router(sat-init-config)# outbound data-pid 3000outbound data-rate
To specify the VSAT data rate, use the outbound data-rate command in satellite initial configuration mode. To remove the data rate configuration, use the no form of this command.
outbound data-rate rate
no outbound data-rate
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to specify the VSAT data rate:
Router(sat-init-config)# outbound data-rate 450000outbound frequency
To specify the VSAT outbound frequency, use the outbound frequency command in satellite initial configuration mode. To remove the outbound frequency configuration, use the no form of this command.
outbound frequency frequency
no outbound frequency
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound frequency:
Router(sat-init-config)# outbound frequency 950000outbound id
To specify the VSAT outbound ID, use the outbound id command in satellite initial configuration mode. To remove the outbound ID configuration, use the no form of this command.
outbound id number
no outbound id
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT outbound ID:
Router(sat-init-config)# outbound id 95outbound modulation-type
To specify the VSAT modulation type, use the outbound modulation-type command in satellite initial configuration mode. To remove the VSAT modulation type configuration, use the no form of this command.
outbound modulation-type {DVB | TURBO_QPSK | 8PSK}
no outbound modulation-type
Syntax Description
DVB
Digital Video Broadcasting for satellite.
TURBO_QPSK
Turbo-coded quadrature Phase Shift Keying.
8PSK
Phase Shift Keying.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT modulation type:
Router(sat-init-config)# outbound modulation-type DVBoutbound sync ip address
To specify the outbound synchronization IP address, use the outbound sync ip address command in satellite initial configuration mode. To remove the outbound synchronization IP address configuration, use the no form of this command.
outbound sync ip address address
no outbound sync ip address
Syntax Description
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the outbound synchronization IP address:
Router(sat-init-config)# outbound sync ip address 10.2.2.2outbound viterbi-rate
To specify the VSAT Viterbi code rate, use the outbound viterbi-rate command in satellite initial configuration mode. To return to the default rate, use the no form of this command.
outbound viterbi-rate rate
no outbound viterbi-rate
Syntax Description
rate
Viterbi code rate. It can be one of the following values:
•
•
•
•
•
•
•
•
•
•
•
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
This command is typically used by an installation technician. Do not use this command unless your satellite service provider instructs you to perform the satellite initial configuration and provides all necessary parameter values.
Examples
The following example shows how to configure the VSAT Viterbi code rate:
Router(sat-init-config)# outbound viterbi-rate 3/4(2.6)overhead j0
To specify the Regenerator Section (RS) Trace identifier (J0), use the overhead j0 command in controller configuration mode. To restore the default value, use the no form of this command.
overhead j0 {transmit | receive} string
no overhead j0 {transmit | receive} string
Syntax Description
Defaults
The default value is 1, and no peer authentication is performed.
Command Modes
Controller configuration
Command History
12.0(17)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T, and the transmit and receive keywords were added.
Usage Guidelines
RS trace is a maintenance feature of SONET. One byte (J0) of the Section overhead associated with each SONET frame is used to carry information identifying the transmitting equipment.
Use this command for peer authentication and continuity testing between two STM-1 optical peers. If the authentication string sent by the originating peer does not match the configured string on the receiving peer, the SONET controller will not come up on the receiving peer. Alarm logs on the originating peer will show that it has RS-Trace Identifier Mismatch (RS-TIM).
Examples
The following example shows how to configure J0 overhead in both the transmit and receive directions on a STM-1 trunk card:
Router(config)# controller sonet 2/0Router(config-controller)# overhead j0 transmit 22Router(config-controller)# overhead j0 receive 34The following example shows how to set the RS Trace identifier to 82:
Router(config-controller)# overhead j0 transmit 82overhead j1
To configure the message length and the message text of the High Order Path Trace identifier (J1), use the overhead j1 command in controller configuration or path configuration mode. To restore the default value, use the no form of this command.
overhead j1 length {16 | 64} {transmit-message | receive-message} string
no overhead j1 length {16 | 64} {transmit-message | receive-message} string
Syntax Description
Defaults
The default message length is 16 for SDH framing and 64 for SONET framing.
No peer authentication is performed.Command Modes
SDH Framing with AU-4 Mapping
Controller configuration
SDH Framing with AU-3 Mapping, or SONET Framing
Path configuration
Command History
12.0(17)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T, and the transmit-message and receive-message keywords were added.
Usage Guidelines
Path trace is a maintenance feature of SONET/SDH. One byte (J1) of the Path overhead associated with each path in the SONET/SDH frame is used to carry information identifying the originating Path Terminating Equipment (PTE).
Where you configure the Path Trace identifier depends on the framing (SDH or SONET) and the AUG mapping. In SDH with AU-4 mapping, the Path Trace identifier is configured at the SONET controller level. In SDH with AU-3 mapping or in SONET framing, the Path Trace identifier is configured at the path level.
In accordance with SONET and SDH standard requirements, the Path Trace message you enter is manipulated as follows:
•
•
Use this command for peer authentication and continuity testing between two STM-1 optical peers. If the authentication string sent by the originating peer does not match the configured string on the receiving peer, the Path (and all E1 controllers within the path) will not come up on the receiving peer. Alarm logs on the originating peer will show that it has High Order Path-Trace Identifier Mismatch (HP-TIM).
Examples
The following example shows J1 configuration in SDH framing with AU-4 AUG mapping. The overhead j1 command sets the message length to 16, and specifies the message text as metro_SF:
Router(config-controller)# au-4 1Router(config-ctrlr-au4)# overhead j1 length 16 transmit-message metro_SFThe following example shows J1 configuration in SDH framing with AU-3 AUG mapping. The overhead j1 command sets the message length to 16, and specifies the message text as metro_LA:
Router(config)# controller sonet 4/0Router(config-controller)# au-3 3Router(config-ctrlr-au3)# overhead j1 length 16 receive-message metro_LThe following example shows J1 configuration in SONET framing in STS-1 mode. The overhead j1 command sets the message length to 64, and specifies the message text:
Router(config)# controller sonet 4/0Router(config-controller)# sts-1 3Router(config-ctrlr-sts1)# overhead j1 length 64 transmit-message metro_washington gsr_0057/4/3The following example shows how to configure j1 overhead in both the transmit and receive directions:
Router(config)# controller sonet 2/0Router(config-controller)# overhead j1 length 2 transmit-message 22Router(config-controller)# overhead j1 length 2 receive-message 34payload-compression
To enable payload compression, use the payload-compression command in CEM configuration mode. To disable payload compression, use the no form of this command.
payload-compression
no payload-compression
Syntax Description
This command has no arguments or keywords.
Defaults
Payload compression is disabled.
Command Modes
CEM configuration
Command History
Usage Guidelines
Payload compression can be enabled only for a maximum of 3 Mbps per network module.
Examples
The following example demonstrates how to enable payload compression.
Router(config-cem)# payload-compression
Related Commands
cem
Enters circuit emulation configuration mode.
payload-size
Configures payload size.
show cem
Displays CEM statistics.
payload-size
To configure the payload size of a circuit emulation (CEM) over IP (CEoIP) packet, use the payload-size command in CEM configuration mode. To restore the default payload size, use the no form of this command.
payload-size size
no payload-size
Syntax Description
Defaults
The default payload size for a serial channel is 32 bytes. Defaults for T1 and E1 channels are shown in Table 13 and Table 14.
Table 13 Default Payload Size for N*64 kbps T1/E1 Channels
Table 14 Default Payload Size for N*56 kbps T1 Channels
Command Modes
CEM configuration
Command History
Usage Guidelines
Use this command to configure the size of each CEoIP packet. Smaller sizes reduce delay but diminish efficiency.
Note
by the user will be automatically changed to match the above requirement, and a console message
will inform the user of this change.Examples
The following example demonstrates how to configure a payload size of 224.
Router(config-cem)# payload-size 224Related Commands
cem
Enters circuit emulation configuration mode.
payload-compression
Enables payload compression.
show cem
Displays CEM channel statistics.
physical-layer
To specify the mode of a slow-speed serial interface on a router as either synchronous or asynchronous, use the physical-layer command in interface configuration mode. To return the interface to the default mode of synchronous, use the no form of this command.
physical-layer {sync | async}
no physical-layer
Syntax Description
sync
Places the interface in synchronous mode. This is the default.
async
Places the interface in asynchronous mode.
Defaults
Synchronous mode
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies only to low-speed serial interfaces available on Cisco 2520 through Cisco 2523 series routers.
In synchronous mode, low-speed serial interfaces support all interface configuration commands available for high-speed serial interfaces, except the following two commands:
•
•
When placed in asynchronous mode, low-speed serial interfaces support all commands available for standard asynchronous interfaces.
When you enter this command, it does not appear in the output of more system:running-config and more nvram:startup-config commands because the command is a physical-layer command.
Examples
The following example shows how to change a low-speed serial interface from synchronous to asynchronous mode:
Router(config)# interface serial 2Router(config-if)# physical-layer asyncRelated Commands
port (interface)
To enable an interface on a PA-4R-DTR port adapter to operate as a concentrator port, use the port command in interface configuration mode. To restore the default station mode, use the no form of this command.
port
no port
Syntax Description
This command has no arguments or keywords.
Defaults
Station mode
Command Modes
Interface configuration
Command History
Usage Guidelines
By default, the interfaces of the PA-4R-DTR operate as Token Ring stations. Station mode is the typical operating mode. Use this command to enable an interface to operate as a concentrator port.
Examples
The following example configures the PA-4R-DTR ports to operate in concentrator mode on a Cisco 7000 series router:
Router(config)# interface tokenring 3/0/0Router(config-if)# portpos ais-shut
To send the line alarm indication signal (LAIS) when the Packet-over-SONET (POS) interface is placed in any administrative shutdown state, use the pos ais-shut command in interface configuration mode.
pos ais-shut
Syntax Description
This command has no arguments or keywords.
Defaults
No LAIS is sent.
Command Modes
Interface configuration
Command History
Usage Guidelines
In Automatic Protection Switching (APS) environments, LAIS can be used to force a protection switch. This command forces an APS switch when the interface is placed in the administrative shutdown state.
For more information on APS, refer to the "Configuring Serial Interfaces" chapter in the Cisco IOS Interface and Hardware Component Configuration Guide.
This command does not have a no form.
Examples
The following example forces the alarm indication on POS OC-3 interface 0 in slot 3:
Router(config)# interface pos 3/0Router(config-if)# shutdownRouter(config-if)# pos ais-shutpos flag
To set the SONET overhead bytes in the frame header to meet a specific standards requirement or to ensure interoperability with the equipment of another vendor, use the pos flag command in interface configuration mode. To remove the setting of the SONET overhead bytes, use the no form of this command.
pos flag {c2 | j0 | s1s0} value
no pos flag {c2 | j0 | s1s0} value
Syntax Description
Defaults
The default c2 value is 0xCF.
The default sls0 value is 0.Command Modes
Interface configuration
Command History
11.2 GS
This command was introduced to support the Cisco 12000 series Internet routers.
Usage Guidelines
Use the following values to tell the SONET transmission equipment the payload type:
•
•
•
•
Examples
The following example sets the path signal identifier used to identify the payload content type to ATM on the pos interface in slot 9:
Router(config)# interface pos 9/0Router(config-if)# pos flag c2 0x13Router(config-if)# endpos framing
To specify the framing used on the POS (Packet-over-SONET) interface, use the pos framing command in interface configuration mode. To return to the default SONET STS-3c framing mode, use the no form of this command.
pos framing {sdh | sonet}
no pos framing
Syntax Description
sdh
Selects SDH STM-1 framing. This framing mode is typically used in Europe.
sonet
Selects SONET STS-3c framing. This is the default.
Defaults
SONET STS-3c framing
Command Modes
Interface configuration
Command History
Examples
The following example configures the interface for SDH STM-1 framing:
Router(config)# interface pos 3/0Router(config-if)# pos framing sdhRouter(config-if)# no shutdownRelated Commands
clock source (interface)
Controls the clock used by a G.703-E1 interface.
interface
Configures an interface type, and enters interface configuration mode.
pos report
To permit selected SONET alarms to be logged to the console for a POS (Packet-over-SONET) interface, use the pos report command in interface configuration mode. To disable logging of select SONET alarms, use the no form of this command.
pos report {b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
no pos report {b1-tca | b2-tca | b3-tca | lais | lrdi | pais | plop | prdi | rdool | sd-ber | sf-ber | slof | slos}
Syntax Description
Defaults
The following alarms are reported by default:
•
•
•
•
•
•
•
Command Modes
Interface configuration
Command History
Usage Guidelines
Reporting an alarm means that the alarm can be logged to the console. Just because an alarm is permitted to be logged does not guarantee that it is logged. SONET alarm hierarchy rules dictate that only the most severe alarm of an alarm group is reported. Whether an alarm is reported or not, you can view the current state of a defect by checking the "Active Defects" line from the show controllers pos command output. A defect is a problem indication that is a candidate for an alarm.
For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the bit interleaved parity error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
PAIS is sent by line terminating equipment (LTE) to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.
PLOP is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF) enabled indications.
SLOF is detected when a severely error framing (SEF) defect on the incoming SONET signal persists for 3 milliseconds.
SLOS is detected when an all-zeros pattern on the incoming SONET signal lasts 19 plus or minus 3 microseconds or longer. This defect might also be reported if the received signal level drops below the specified threshold.
To determine the alarms that are reported on the interface, use the show controllers pos command.
Examples
The following example enables reporting of SD-BER and LAIS alarms on the interface:
Router(config)# interface pos 3/0/0Router(config-if)# pos report sd-berRouter(config-if)# pos report laisRouter(config-if)# endRelated Commands
interface
Configures an interface type, and enters interface configuration mode.
show controllers pos
Displays information about the POS controllers.
pos scramble-atm
To enable SONET payload scrambling on a POS (Packet-over-SONET) interface, use the pos scramble-atm command in interface configuration mode. To disable scrambling, use the no form of this command.
pos scramble-atm
no pos scramble-atm
Syntax Description
This command has no arguments or keywords.
Defaults
Scrambling is disabled.
Command Modes
Interface configuration
Command History
Usage Guidelines
SONET payload scrambling applies a self-synchronous scrambler (x43+1) to the Synchronous Payload Envelope (SPE) of the interface to ensure sufficient bit transition density. Both ends of the connection must use the same scrambling algorithm. When enabling POS scrambling on a VIP2 POSIP on the Cisco 7500 series router that has a hardware revision of 1.5 or higher, you can specify CRC 16 only (that is, CRC 32 is currently not supported).
To determine the hardware revision of the POSIP, use the show diag command.
To determine whether scrambling is enabled on the interface, use the show interface pos command or the show running-config command.
Note
Examples
The following example enables scrambling on the interface:
Router(config)# interface pos 3/0Router(config-if)# pos scramble-atmRouter(config-if)# no shutdownRouter(config-if)# endRelated Commands
pos threshold
To set the bit-error rate (BER) threshold values of the specified alarms for a POS (Packet-Over-SONET) interface, use the pos threshold command in interface configuration mode. To return to the default setting, use the no form of this command.
pos threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate
no pos threshold {b1-tca | b2-tca | b3-tca | sd-ber | sf-ber} rate
Syntax Description
Defaults
The default rate is 6 for b1-tca, b2-tca, b3-tca, and sd-ber.
The default rate is 3 (10e-3) for sf-ber.Command Modes
Interface configuration
Command History
Usage Guidelines
For B1, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame. Differences indicate that section level bit errors have occurred.
For B2, the bit interleaved parity error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line level bit errors have occurred.
For B3, the bit interleaved parity error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame. Differences indicate that path level bit errors have occurred.
SF-BER and SD-BER are sourced from B2 BIP-8 error counts (as is B2-TCA). However, SF-BER and SD-BER feed into the automatic protection switching (APS) machine and can lead to a protection switch (if APS is configured).
B1-TCA, B2-TCA, and B3-TCA do nothing more than print a log message to the console (if reports for them are enabled).
To determine the BER thresholds configured on the interface, use the show controllers pos command.
Examples
The following example configures thresholds on the interface:
Router(config)# interface pos 3/0/0Router(config-if)# pos threshold sd-ber 8Router(config-if)# pos threshold sf-ber 4Router(config-if)# pos threshold b1-tca 4Router(config-if)# endRelated Commands
power inline
To determine how inline power is applied to the device on the specified Fast Ethernet port, use the power inline command in interface configuration mode. To return the setting to its default, use the no form of this command.
power inline {auto | never}
no power inline
Syntax Description
auto
Automatically detects and powers inline devices. This is the default.
never
Never applies inline power.
Defaults
Power is applied when a telephone is detected on the port (auto).
Command Modes
Interface configuration
Command History
Examples
The following example shows how to always apply power to the port:
Router(config-if)# power inline auto
Related Commands
pulse-time
To enable pulsing data terminal ready (DTR) signal intervals on the serial interfaces, use the pulse-time command in interface configuration mode. To restore the default interval, use the no form of this command.
pulse-time [msec] seconds
no pulse-time
Syntax Description
Defaults
0 seconds
Command Modes
Interface configuration
Command History
10.0
This command was introduced.
12.1(5)T
The optional msec keyword was added to configure the interval in milliseconds.
Usage Guidelines
When the serial line protocol goes down (for example, because of loss of synchronization), the interface hardware is reset and the DTR signal is held inactive for at least the specified interval. This function is useful for handling encrypting or other similar devices that use the toggling of the DTR signal to resynchronize.
Use the optional msec keyword to specify the DTR signal interval in milliseconds. A signal interval set to milliseconds is recommended on High-Speed Serial Interfaces (HSSIs).
Examples
The following example enables DTR pulse signals for 3 seconds on serial interface 2:
Router(config)# interface serial 2Router(config-if)# pulse-time 3The following example enables DTR pulse signals for 150 milliseconds on HSSI interface 2/1/0:
Router(config)# interface hssi 2/1/0Router(config-if)# pulse-time msec 150redundancy handover
To hand over control of resources (slots and cards) from a route-switch-controller (RSC) card to its peer RSC card, use the redundancy handover command in privileged EXEC mode.
redundancy handover {cancel | {peer-resources | shelf-resources}
[busyout-period mins] [at hh:mm [{day month | month day} year]]}Syntax Description
Defaults
Control remains with the assigned RSC.
Command Modes
Privileged EXEC
Command History
12.2(2)XB1
This command was introduced.
12.2(11)T
This command was integrated into Cisco IOS Release 12.2(11)T.
Usage Guidelines
To use this command, you must have two RSC cards installed on your Cisco AS5850 and you must be connected to one of them in handover-split mode. This command can be run from either RSC and can specify that slots be handed over to the peer RSC.
After handover and subsequent restoration of the failed RSC, connect to the active RSC and use this command to return control of cards to the previously failed but now restored RSC.
Note that when you enter the command with the shelf-resources option, the RSC reloads.
Examples
The following example hands over control, to the peer RSC, of the slots and cards on the corresponding side of the chassis. Note the prompt to confirm clearing of calls, handover, and reload on the last line.
Router# redundancy handover shelf-resources busyout-period 10 at 22:00 3 Sep 2005Newly entered handover schedule:Busyout period at 22:00:00 PDT Sat Sep 3 2005 for a duration of 10 minutesHandover pending at 22:10:00 PDT Sat Sep 3 2005Clear calls, handover and reload as specified above? yRelated Commands
redundancy stateful
To configure stateful failover for tunnels using IP Security (IPSec), use the redundancy stateful command in crypto map configuration mode. To disable stateful failover for tunnel protection, use the no form of this command.
redundancy standby-group-name stateful
no redundancy standby-group-name stateful
Syntax Description
Defaults
Stateful failover is not enabled for IPSec tunnels.
Command Modes
Crypto map configuration
Command History
Usage Guidelines
The redundancy stateful command uses an existing IPSec profile (which is specified via the crypto ipsec profile command) to configure IPSec stateful failover for tunnel protection. (You do not configure the tunnel interface as you would with a crypto map configuration.) IPSec stateful failover enables you to define a backup IPSec peer (secondary) to take over the tasks of the active (primary) router if the active router is deemed unavailable.
The tunnel source address must be a VIP address, and it must not be an interface name.
Examples
The following example shows how to configure stateful failover for tunnel protection:
crypto ipsec profile peer-profileredundancy HA-out statefulinterface Tunnel1ip unnumbered Loopback0tunnel source 209.165.201.3tunnel destination 10.0.0.5tunnel protection ipsec profile peer-profile!interface Ethernet0/0ip address 209.165.201.1 255.255.255.224standby 1 ip 209.165.201.3standby 1 name HA-outRelated Commands
crypto ipsec profile
Defines the IPSec parameters that are to be used for IPSec encryption between two routers and enters crypto map configuration mode.
reset (alarm-interface)
To reset the CPU in the alarm interface controller (AIC), use the reset command in alarm-interface mode.
reset
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Alarm-interface
Command History
12.2(2)XG
This command was introduced on the Cisco 2600 series and Cisco 3600 series.
12.2(8)T
This command was integrated into Cisco IOS Release 12.2(8)T.
Usage Guidelines
A change in the AIC IP configuration might not take effect until the next time the card is started. Use the reset command to restart the card. This command does not have a no form.
Examples
The following example shows a message that might be returned after the reset command is entered:
Router(alarm-aic)# resetSelected card in slot 1 restartedRelated Commands
ring-speed
To set the ring speed for the CSC-1R and CSC-2R Token Ring interfaces, use the ring-speed command in interface configuration mode.
ring-speed speed
Syntax Description
speed
Integer that specifies the ring speed, either 4 for 4-Mbps operation or 16 for 16-Mbps operation. The default is 16.
Defaults
16-Mbps operation
Caution
Command Modes
Interface configuration
Command History
Usage Guidelines
This command does not have a no form.
Examples
The following example shows how to sets the ring speed to 4 Mbps on a Token Ring interfaces:
Router(config)# interface tokenring 0Router(config-if)# ring-speed 4
