-
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
dsl-mode shdsl symmetric annex
end (satellite initial configuration)
exit (satellite initial configuration)
data-protection
To enable data protection for a circuit emulation (CEM) channel, use the data-protection command in CEM configuration mode. To disable data protection, use the no form of this command.
data-protection
no data-protection
Syntax Description
This command has no arguments or keywords.
Command Default
Data protection is disabled for a CEM channel.
Command Modes
CEM configuration
Command History
Examples
The following example demonstrates how to enable data protection.
Router(config-cem)# data-protectionRelated Commands
cem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
data-strobe
To specify an input control lead to be monitored as an indicator of valid data, use the data-strobe command in CEM configuration mode. To disable the monitoring of an input control lead, use the no form of this command.
data-strobe input-lead {on | off}
no data-strobe
Syntax Description
Command Default
No input control lead is monitored.
Command Modes
CEM configuration
Command History
Usage Guidelines
Any input control signal on a serial data port may be configured as a "data strobe" to indicate to the NM-CEM-4SER network module whether ingress data on the port should be encapsulated for transmission or ignored. If the data-strobe command is specified with the on keyword, data packets are created and sent when the input lead is asserted. If the data strobe is off (either intentionally or as a result of the failure of the customer premises equipment [CPE]), no data packets are created, and this results in preservation of bandwidth in the IP network.
This command applies only to serial ports.
Examples
The following example demonstrates how to specify that packets are to be created and sent to the far end only when the DTR input control lead is asserted.
Router(config-cem)# data-strobe dtr on
Related Commands
dce-terminal-timing enable
To prevent phase shifting of the data with respect to the clock when running the line at high speeds and long distances, use the dce-terminal-timing enable command in interface configuration mode. If serial clock transmit external (SCTE) terminal timing is not available from the DTE, use the no form of this command; the DCE will use its own clock instead of SCTE from the DTE.
dce-terminal-timing enable
no dce-terminal-timing enable
Syntax Description
This command has no arguments or keywords.
Defaults
The DCE uses its own clock.
Command Modes
Interface configuration
Command History
Usage Guidelines
On the Cisco 4000 router, you can specify the serial Network Interface Module timing signal configuration. When the board is operating as a DCE and the DTE provides terminal timing (SCTE or TT), the dce-terminal-timing enable command causes the DCE to use SCTE from the DTE.
Examples
The following example shows how to prevent phase shifting of the data with respect to the clock:
Router(config)# interface serial 0Router(config-if)# dce-terminal-timing enabledebug platform link-dc
To display debugging messages for SFP and XFP transceivers, use the debug platform link-dc command in privileged EXEC mode. To disable debugging output, use the no form of this command.
debug platform link-dc {interrupt | transceiver}
no debug platform link-dc {interrupt | transceiver}
Syntax Description
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRD
This command was introduced.
Note
This command applies only to the Cisco 7600 series Ethernet Services Plus (ES+) line card.
Usage Guidelines
Use this command with the remote command command or the attach command in privileged EXEC mode.
Examples
The following examples show the output for both the debug platform link-dc tranceiver command and the debug platform link-dc interrupt command. Notice that the show platform hardware transceiver command shows the status for the port.
Router# remote command module 1 debug platform link-dc tranceiverLink-DC transceiver debugging is onRouter# remote command module 1 debug platform link-dc interruptLink-DC interrupt debugging is onRouter# remote command module 1 show debugx40g subsystem:Link-DC transceiver debugging is onLink-DC interrupt debugging is onRouter# remote command module 1 show platform hardware transceiver status 1Show status info for port 1:TenGigabitEthernet1/1:State: EnabledEnvironmental Information - raw valuesTemperature: 7616Tx voltage: 0 in units of 100uVoltTx bias: 28722 uATx power: -2 dBm (5441 in units of 0.1 uW)Rx power: 0 dBm (7712 in units of 0.1 uW)(AUX1) Laser Temperature: 8704(AUX2) +3.3V Supply Voltage: 32928XFP TX is enabled.XFP TX is soft enabled.XFP is ready.XFP is not power down.XFP is not soft power down.XFP doesn't have interrupt(s).XFP is not LOS.XFP data is ready.XFP TX path is ready.XFP TX laser is not in fault condition.XFP TX path CDR is locked.XFP RX path is ready.XFP RX path CDR is locked.No active alarmsNo active warningRouter-dfc1#*Aug 15 11:20:26.436 PDT: DFC1: TenGigabitEthernet1/1 XFP: show status*Aug 15 11:20:26.436 PDT: DFC1: TenGigabitEthernet1/1 XFP: show environmental monitoring*Aug 15 11:20:26.436 PDT: DFC1: pluggable optics read - addr: 50, offset: 60, len: 14, dataptr: 2377A668*Aug 15 11:20:26.448 PDT: DFC1: pluggable optics read - addr: 50, offset: 6E, len: 2, dataptr: 21AA028E*Aug 15 11:20:26.452 PDT: DFC1: pluggable optics read - addr: 50, offset: 50, len: 2, dataptr: 2377A6A0*Aug 15 11:20:26.456 PDT: DFC1: pluggable optics read - addr: 50, offset: 52, len: 2, dataptr: 2377A6A2
Note
Router-dfc1#*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.127 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.127 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.131 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.131 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 6, msg_num 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:23:52.135 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x4000*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_xcvr_isr: intr_st 0x2, start 0, end 4, type 2,port_offset 0x0*Aug 15 11:23:52.135 PDT: DFC1: Link xcvr port 1: Rx LOS interrupt*Aug 15 11:23:52.135 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 2, msg_num 1*Aug 15 11:23:52.135 PDT: DFC1: Port 2: transceiver Rx LOS event*Aug 15 11:23:52.147 PDT: DFC1: x40g_link_dc_process: xcvr oir timer timeout00:12:37: %LINEPROTO-DFC1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2, changed state to downRecommended Action Router-dfc1#
*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x4000*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_xcvr_isr: intr_st 0x2, start 0, end 4, type 2,port_offset 0x0*Aug 15 11:24:46.576 PDT: DFC1: Link xcvr port 1: Rx LOS interrupt*Aug 15 11:24:46.576 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 2, msg_num 1*Aug 15 11:24:46.576 PDT: DFC1: Port 2: transceiver Rx LOS recovered*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:24:46.580 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:24:46.580 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 0*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_dc_interrupt_handler: intr_status 0x8000*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_xphy_isr: xphy intr intr_st 0x80000*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_xphy_isr: xphy intr port 1*Aug 15 11:24:46.584 PDT: DFC1: x40g_xphy_link_status_callout: port 1 link status 1*Aug 15 11:24:46.584 PDT: DFC1: x40g_link_dc_process: interrupt msg_id 6, msg_num 1*Aug 15 11:24:46.600 PDT: DFC1: x40g_link_dc_process: xcvr oir timer timeout00:13:31: %LINEPROTO-DFC1-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2, changed state to upRelated Commands
debug snmp tunnel-mib
To enable the debugging for configuring the IP Tunnel Management Information Base (MIB) through Simple Network Management Protocol (SNMP), use the debug snmp tunnel-mib command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug snmp tunnel-mib
no debug snmp tunnel-mib
Syntax Description
This command has no arguments or keywords.
Command Modes
Privileged EXEC (#)
Command History
Usage Guidelines
Use the debug snmp tunnel-mib command to verify whether a tunnel is created or deleted.
Examples
The following is sample output from the debug snmp tunnel-mib command. The output shows that a tunnel is created through SNMP.
Router# debug snmp tunnel-mibSNMP TUNNEL-MIB debugging is onk_tunnelInetConfigEntry_get: Enteringk_tunnelInetConfigEntry_get: Exact searchtim_client_tunnel_endpoint_data_get: Enteringtim_client_tunnel_endpoint_data_get: Exact searchtim_client_tunnel_endpoint_data_get: No element foundk_tunnelInetConfigEntry_get: Client service failedk_tunnelInetConfigEntry_test: Enteringk_tunnelInetConfigEntry_test: Completedk_tunnelInetConfigEntry_set: Enteringtim_client_tunnel_endpoint_data_get: Enteringtim_client_tunnel_endpoint_data_get: Exact searchtim_client_tunnel_endpoint_data_get: No element foundk_tunnelInetConfigEntry_set: Calling tunnel createtim_client_tunnel_create: Enteringtim_client_tunnel_create: Completedinterface vmi
To create a virtual multipoint interface (VMI) that can be configured and applied dynamically, use the interface vmi command in global configuration mode. Use the no form of this command to remove a VMI interface.
interface vmi interface-number
no interface vmi
Syntax Description
interface-number
Number assigned to the VMI. The value range for VMI interface numbers is from 1 to 2147483647
Defaults
No virtual template number is defined.
Command Modes
Global configuration
Command History
12.4(15)XF
This command was introduced.
12.4(15)T
This command was integrated into Cisco IOS Release 12.4(15)T.
Usage Guidelines
VMI Interface -Aggregation Point
The VMI interface acts as an aggregation point for multiple PPPoE connections from one or more radios over one or more physical interfaces.
OSPFv3 and EIGRP Route Advertisements
All OSPFv3, EIGRPv4, and EIGRPv6 route advertisements that are received over the PPPoE connections are reported to the routing protocol as coming from a single interface, thus simplifying the routing protocol topology table and providing scalability benefits of each of the routing protocols.
Examples
The following example shows how to create a VMI interface:
interface vmi 1ip address 10.2.1.1 255.255.255.0no ip redirectsno ip split-horizon eigrp 1load-interval 30ipv6 address 2001:0DB8:1:1:FFFF:FFFF:FFFF:FFFE/64ipv6 enableno ipv6 redirectsipv6 eigrp 1no ipv6 split-horizon eigrp 1physical-interface GigabitEthernet 0/0endRelated Commands
default (CEM)
To reset channel options to their default values, use the default command in CEM configuration mode.
default {data-protection | dejitter-buffer | idle-pattern | ip dscp | ip tos | ip precedence | payload-compression | payload-size | signaling}
Syntax Description
Defaults
The CEM channel options are set at their configured values.
Command Modes
CEM configuration
Command History
Examples
The following example demonstrates how to reset CEM channel data protection to its default value.
Router(config-cem)# default data-protectionRelated Commands
default (interface)
To reset the configuration of an interface back to its default values, use the default command in global configuration mode.
default interface-type interface-number
Syntax Description
Defaults
Existing interface configuration values are not reset.
Command Modes
Global configuration
Command History
Usage Guidelines
The default command is a general-purpose command that is not limited to interfaces; it resets defaults based on the command name that follows it. Use the default (interface) command when you need to remove any configuration for a specified interface and reset the interface to its default values.
When the default command is executed on a port that is already in its default port mode, only the `default port mode' configuration is removed. If this command is executed on a port that is not in default port mode, only the 'non-default port mode' configuration is removed. The 'default port mode' configuration is retained.
EXAMPLE:
Cat6000 Series
If the default command is executed on a routed port (routed port is the default port mode in Cat6000 series), only the routed port configuration is removed.
If the port has any switchport (non-default port mode) configuration, the configuration is retained, but is invisible to you. When a switchport is issued after defaulting the interface, all the switchport configurations reappear.
If the default command is executed on a switchport, both switchport configuration and routed port configuration are removed.
Examples
The following example demonstrates how to reset serial interface 0 to its default values.
Router(config)# default serial 0Related Commands
define interface-range
To create an interface-range macro, use the define interface-range command in global configuration mode.
define interface-range macro-name interface-range
Syntax Description
Defaults
This command has no default settings.
Command Modes
Global configuration
Command History
Usage Guidelines
The macro name is a 32-character maximum character string.
Amn interface range for a macro can contain up to five ranges. An interface range cannot span slots. Use this format when entering the interface-range:
•
Valid values for card-type are as follows:
•
•
•
•
•
•
•
•
•
•
•
Examples
This example shows how to create a multiple-interface macro:
Router(config)# define interface-range macro1 ethernet 1/2 - 5, fastethernet 5/5 - 10Router(config)#Related Commands
dejitter-buffer
To configure the size of the dejitter buffer, use the dejitter-buffer command in CEM configuration mode. To restore the dejitter buffer to its default size, use the no form of this command.
dejitter-buffer size
no dejitter-buffer
Syntax Description
Command Default
The dejitter buffer defaults to 60 milliseconds.
Command Modes
CEM configuration
Command History
Examples
The following example shows how to set the dejitter buffer to 200 milliseconds.
Router(config-cem)# dejitter-buffer 200
Related Commands
cem
Enters circuit emulation configuration mode.
clear cem
Clears CEM channel statistics.
show cem
Displays CEM channel statistics.
delay (interface)
To set a delay value for an interface, use the delay command in interface configuration mode. To restore the default delay value, use the no form of this command.
delay tens-of-microseconds
no delay
Syntax Description
tens-of-microseconds
Integer that specifies the delay in tens of microseconds for an interface or network segment. To see the default delay, use the show interfaces command.
Defaults
Default delay values may be displayed with the show interfaces EXEC command.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to set a delay of 30,000 microseconds on serial interface 3:
Router(config)# interface serial 3Router(config-if)# delay 3000Related Commands
show interfaces
Displays the statistical information specific to a serial interface.
description (controller)
To add a description to an E1 or T1 controller or the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the description command in controller configuration mode. To remove the description, use the no form of this command.
description string
no description
Syntax Description
string
Comment or description (up to 80 characters) to help you remember what is attached to an interface.
Defaults
No description is added.
Command Modes
Controller configuration
Command History
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember what certain controllers are used for. The description affects the CT3IP and Multichannel Interface Processor (MIP) interfaces only and appears in the output of the show controller e1, show controller t1, show controller t3, and show running-config EXEC commands.
Examples
The following example shows how to add a description for a 3174 controller:
Router(config)# controller t1Router(config-controller)# description 3174 Controller for test labRelated Commands
description (interface)
To add a description to an interface configuration, use the description command in interface configuration mode. To remove the description, use the no form of this command.
description string
no description
Syntax Description
string
Comment or a description to help you remember what is attached to this interface. This string is limited to 238 characters.
Defaults
No description is added.
Command Modes
Interface configuration
Command History
Usage Guidelines
The description command is meant solely as a comment to be put in the configuration to help you remember what certain interfaces are used for. The description appears in the output of the following EXEC commands: more nvram:startup-config, show interfaces, and more system:running-config.
Examples
The following example shows how to add a description for a T1 interface:
interface serial 0description Fractional T1 line to remote office -- 128 kbpsRelated Commands
diagnostic level
To turn on power-on diagnostic tests for the network service engines (NSEs) installed in a Cisco 7300 series router, use the diagnostic level command in privileged EXEC configuration mode. There is no no form of this command.
diagnostic level {power-on | bypass}
Syntax Description
power-on
Power-on diagnostic tests are performed at system bootup on the NSEs.
bypass
No diagnostic tests are performed. This is the default.
Defaults
No diagnostic tests are performed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use this command to enable power-on diagnostic tests to run on the installed NSEs of a Cisco 7300 series router when the system is booted. It is recommended that you issue this command only if you are experiencing problems with an NSE and are planning on rebooting the router. Issuing this command causes an increase in the boot time.
Examples
The following example shows how to enable diagnostic power-on tests:
diagnostic level power-onThe following sample output shows the output that is displayed upon system bootup after a power cycle or router crash:
...System Power On DiagnosticsDRAM Size ....................128 MBTesting DRAM..................PassedLevel2 Cache .................PresentTesting Level2 Cache (256 KB)PassedLevel3 Cache .................PresentTesting Level3 Cache (1024 KB)PassedSystem Power On Diagnostics Complete
Note
Related Commands
dial-tdm-clock
To configure the clock source and priority of the clock source used by the time-division multiplexing (TDM) bus on the dial shelf of the Cisco AS5800, use the dial-tdm-clock command in global configuration mode. To return the clock source and priority to the default values, use the no form of this command.
dial-tdm-clock priority number {external {e1 | t1} [120ohm] | freerun | trunk-slot slot port port} [line {0 | 1}]
no dial-tdm-clock priority number {external {e1 | t1} [120ohm] | freerun | trunk-slot slot port port} [line {0 | 1}]
Syntax Description
Defaults
If no clock sources are specified, the software selects the first available good clock source on a trunk port.
Command Modes
Global configuration
Command History
Usage Guidelines
The TDM bus in the backplane on the dial shelf must be synchronized to the T1/E1 clocks on the trunk cards. The DSC card on the dial shelf provides hardware logic to accept multiple clock sources as input and use one of them as the primary source to generate a stable, PPL synchronized output clock. The input clock can be any of the following sources:
•
•
•
The clock commands are listed in the configuration file with the highest priority listed first.
If the current primary clock source is good, specifying another clock source of higher priority does not cause the clock source to switch to the higher priority clock source. The new higher priority clock source is used as a backup clock source. This prevents switching of the clock source as you enter multiple dial-tdm-clock priority configuration commands in random order. Also, it is important not to disturb the existing clock source as long as it is good. To force the new higher priority clock source to take over from a currently good primary clock source, configure the new clock source and use the no dial-tdm-clock priority command to remove the current primary clock source.
To display the current primary and backup clocks along with their priorities, use the show dial-shelf clocks EXEC command.
Examples
In the following example, an external clock source is set at priority 1 and the trunk card in slot 4, port 1 is set at priority 5:
Router(config)# dial-tdm-clock priority 1 external t1Router(config)# dial-tdm-clock priority 5 trunk-slot 4 port 1Router(config)# exitRelated Commands
show dial-shelf
Displays information about the dial shelf, including clocking information.
dot1q tunneling ethertype
To define the Ethertype field type used by peer devices when implementing Q-in-Q VLAN tagging, use the dot1q tunneling ethertype command in interface configuration mode. To remove the VLAN tag Ethertype, use the no form of this command.
dot1q tunneling ethertype ethertype
no dot1q tunneling ethertype ethertype
Syntax Description
ethertype
Type of Ethertype field. Valid values are 0x8100 or 0x9100 or 0x9200. Default is 0x8100.
Note
Defaults
The Ethertype field used by peer devices when implementing Q-in-Q VLAN tagging is 0x8100.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the dot1q tunneling ethertype command if the peer switching devices are using an Ethertype field value of 0x9100 or 0x9200. All Cisco switching devices use the default Ethertype field value of 0x8100. The Cisco 10000 series router additionally supports the 0x9200 Ethertype field value.
Note
This command is used with the IEEE 802.1Q-in-Q VLAN Tag Termination feature in which double VLAN tagging is configured using the encapsulation dot1q command. 802.1Q double tagging allows a service provider to use a single VLAN to support customers who have multiple VLANs.
Examples
The following example shows how to configure an Ethertype field as 0x9100:
Router(config)# interface gigabitethernet 1/0/0Router(config-if)# dot1q tunneling ethertype 0x9100The following example shows how to configure an Ethertype field as 0x9200 on a Cisco 10000 series router:
Router(config)# interface gigabitethernet 1/0/0Router(config-if)# dot1q tunneling ethertype 0x9200Related Commands
down-when-looped
To configure an interface to inform the system that it is down when loopback is detected, use the down-when-looped command in interface configuration mode.
down-when-looped
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is valid for High-Level Data Link Control (HDLC) or PPP encapsulation on serial and High-Speed Serial Interface (HSSI) interfaces.
This command does not have a no form.
Backup Interfaces
When an interface has a backup interface configured, it is often desirable that the backup interface be enabled when the primary interface is either down or in loopback. By default, the backup is enabled only if the primary interface is down. By using the down-when-looped command, the backup interface will also be enabled if the primary interface is in loopback.
Testing an Interface with the Loopback Command
If testing an interface with the loopback command, or by placing the DCE into loopback, the down-when-looped command should not be configured; otherwise, packets will not be transmitted out the interface that is being tested.
Examples
The following example shows how to configure interface serial 0 for HDLC encapsulation. The interface is then configured to let the system know that it is down when in loopback mode.
Router(config)# interface serial0Router(config-if)# encapsulation hdlcRouter(config-if)# down-when-loopedRelated Commands
backup interface
Configures an interface as a secondary or dial backup interface.
loopback (E3 controller)
Diagnoses equipment malfunctions between an interface and a device.
ds0-group (J1 controller)
To configure channelized J1 time slots, use the ds0-group command in controller configuration mode. To remove the DS0 group, use the no form of this command.
ds0-group ds0-group-no timeslots timeslot-list type external-signaling
no ds0-group ds0-group-no timeslots timeslot-list type external-signaling
Syntax Description
Defaults
No DS0 group is defined.
Command Modes
Controller configuration
Command History
Usage Guidelines
The ds0-group command replaces the existing cas-group command. Making the command generic allows flexibility and scalability. It is not restricted to channel associated signaling (CAS) or channel bundling.
The ds0-group command automatically creates a logical voice port that is numbered as follows on Cisco 2600 and Cisco 3600 series routers: slot/port:ds0-group-no. Although only one voice port is created for each group, applicable calls are routed to any channel in the group.
Examples
The following example is sample output from the show controllers j1 command on the Cisco 3660 series after channelized J1 time slots have been configured:
Router(config-controller)# ds0-group 1 timeslots 1-15,17-31 type e&m-wink-startRouter(config-controller)# endRouter# show controllers j1*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(1), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(2), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(3), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(4), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(5), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(6), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(7), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(8), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(9), cp*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(10), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(11), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(12), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(13), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(14), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(15), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(17), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(18), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(19), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(20), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(21), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(22), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(23), p*Mar 1 03:12:26.259: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(24), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(25), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(26), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(27), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(28), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(29), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(30), p*Mar 1 03:12:26.263: %LINK-3-UPDOWN: Interface recEive and transMit3/0:0(31), pRelated Commands
dsl-mode shdsl symmetric annex
To specify the operating mode of the digital subscriber line (DSL) controller, use the dsl-mode shdsl symmetric annex command in controller configuration mode. To return the DSL to the default Annex A, use the no form of this command.
dsl-mode shdsl symmetric annex mode
Syntax Description
Defaults
The annex defaults to A for North America.
Command Modes
Controller configuration
Command History
Usage Guidelines
This command is used to configure the DSL controller interface to operate in a specified DSL mode and to set regional operating parameters. The shdsl keyword is used to set the mode to SHDSL and configures multirate, high-speed DSL per ITU G.991.2. The symmetric keyword configures the controller to symmetric mode. The annex keyword configures the controller to use regional operating parameters. The regional operating parameters default to North America.
Examples
The following example displays the use of the controller dsl 0/0 command to configure the controller in the router configured on the central office (CO) side. Use the dsl-mode shdsl symmetric annex b command to configure the controller for multirate, high-speed DSL with symmetric mode for European operating parameters.
Router# configure terminalRouter(config)# controller dsl 0/0Router(config-controller)# line-term coRouter(config-controller)# dsl-mode shdsl symmetric annex bRouter(config-controller)# mode atmRouter(config-controller)#00:22:07: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to downRouter(config-controller)# line-mode 4-wire00:23:25: %CONTROLLER-5-UPDOWN: Controller DSL 0/0, changed state to up00:23:31: %LINK-3-UPDOWN: Interface ATM0/0, changed state to up00:23:32: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0/0, changed state to upRelated Commands
dsu bandwidth
To specify the maximum allowable bandwidth used by a T3 or E3 controller or the PA-T3 and PA-E3 port adapters, use the dsu bandwidth command in interface configuration mode. To return to the default bandwidth, use the no form of this command.
dsu bandwidth kbps
no dsu bandwidth
Syntax Description
Defaults
E3 or PA-E3 Port Adatpters
34,010 kbps
T3 Controller
44,210 kbps
PA-T3 Port Adapter
44,736 kbps
Cisco 10000 Series Router
34,368 kbps for E3
44,210 kbps for T3
Command Modes
Interface configuration
Command History
Usage Guidelines
Local and Remote Bandwidths
The local interface configuration must match the remote interface configuration. For example, if you reduce the maximum bandwidth to 16,000 on the local port, you must also do the same on the remote port.
The dsu bandwidth command reduces the bandwidth by padding the E3 and T3 frame.
Verifying DSU Bandwidth
To verify the data service unit (DSU) bandwidth configured on the interface, use the show interfaces serial user EXEC command.
G.751 Framing
When G.751 framing is used, DSU bandwidth can be used to select a payload subrate from 34,010 kbps down to 22 kbps. Before framing bypass can be used, a DSU bandwidth of 34,010 kbps must be configured.
Continuous Range of Bandwidth
Even though Cisco_IOS software allows you to configure a continuous range of bandwidths in subrate modes, vendors support bandwidths only in quantums (for example, in an E3 digital link, bandwidth must be in multiples of 358 kbps). Therefore, the software sets the user-configured bandwidth to the closest vendor-supported bandwidth. Use the show interfaces serial slot/port command to display the actual bandwidth that is configured.
Subrates
The user-configured subrate mode, subrate bandwidth, actual subrate bandwidth configured, and scramble configuration are displayed near the end of the show interfaces serial command output.
DSU Modes and Vendor-Supported Bandwidths
The following table shows DSU modes and vendor-supported bandwidths.
Examples
The following example sets the maximum allowable DSU bandwidth to 16,000 kbps on interface 1/0/0:
Router(config)# interface serial 1/0/0Router(config-if)# dsu bandwidth 16000The following example shows the user-configured subrate bandwidth and the actual configured subrate bandwidth as displayed in the output of the show interfaces serial command:
Router# show interfaces serialSerial1/0 is up, line protocol is upHardware is DSXPNM SerialMTU 1500 bytes, BW 44210 Kbit, DLY 20000 usec,reliability 253/255, txload 1/255, rxload 1/255Encapsulation HDLC, crc 16, loopback not setKeepalive not setDTR is pulsed for 0 seconds on reset, Restart-Delay is 1637167 secsLast input 04:59:04, output 04:59:04, output hang neverLast clearing of "show interface" counters 00:00:02Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0Queueing strategy:fifoOutput queue :0/40 (size/max)5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 0 bits/sec, 0 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort0 packets output, 0 bytes, 0 underruns0 output errors, 0 collisions, 0 interface resets0 output buffer failures, 0 output buffers swapped out0 carrier transitionsDSU mode 0, bandwidth 34010, real bandwidth 34010, scramble 0Related Commands
show interfaces serial
Displays information that is specific to the interface hardware.
dsu mode
To specify the interoperability mode used by a T3 or E3 controller or the PA-T3 and PA-E3 port adapters, use the dsu mode command in interface configuration mode. To return to the default mode, use the no form of this command.
dsu mode {0 | 1 | 2 | 3 | 4}
no dsu mode
Cisco 10000 Series Router
dsu mode {adtran | cisco | digital-link | kentrox | larscom | verilink-highbit | verilink-lowbit}
no dsu mode
Syntax Description
Defaults
0
Cisco 10000 Series Router
cisco
Command Modes
Interface configuration
Command History
Usage Guidelines
Scrambling Support in DSU Mode 1
DSU mode 1 refers to Kentrox mode. If DSU mode is used on a T3 serial interface and the bandwidth is greater than or equal to 35,000 bits per second (bps), the scrambling option is not supported. Likewise, if DSU mode 1 is used for an E3 serial interface and the bandwidth is greater than or equal to 24,510 bps, scrambling is not supported.
Match Local and Remote DSU Configurations
The local interface configuration must match the remote interface configuration. For example, if you define the DSU interoperability mode as 1 on the local port, you must also do the same on the remote port.
Know the DSU Type
You must know what type of DSU is connected to the remote port to determine if it interoperates with an E3 or T3 controller or a PA-E3 or PA-T3 port adapter. The dsu mode command enables and improves interoperability with other DSUs.
Verify DSU Mode
To verify the DSU mode configured on the interface, use the show controllers serial or show interfaces serial user EXEC commands.
Cisco 10000 Series Router
Only Cisco, Digital Link, and Kentrox DSUs are supported on E3 interfaces.
Examples
Setting DSU Mode
The following example sets the DSU mode to 1 on interface 1/0/0:
Router(config)# interface serial 1/0/0Router(config-if)# dsu mode 1Serial Interface in DSI Mode 1
The following example shows the configuration for a serial interface configured in DSU mode 1. The bandwidth is set higher than that supported by the Kentrox firmware allows for scrambling. therefore, the scrambling option is not supported in this configuration.
Router(config)# interface serial 1/0/0Router(config-if)# mtu 4474Router(config-if)# ip address 192.168.93.114 255.255.255.252Router(config-if)# ip mtu 4470Router(config-if)# dsu mode 1Router(config-if)# dsu bandwidth 44210Cisco 10000 Series Router
The following example sets the DSU mode to cisco:
Router(config)# interface serial 1/0/0Router(config-if)# dsu mode ciscoRelated Commands
show controllers
Displays information about the controllers.
show interfaces
Displays statistics for all interfaces configured on the router.
dte-invert-txc
To invert the transmit external clock (TXC) signal received from the DCE when the device is operating as a DTE, use the dte-invert-txc command in interface configuration mode. If the DCE accepts serial clock transmit external (SCTE) signal when the device is operating as a DTE, use the no form of this command.
dte-invert-txc
no dte-invert-txc
Syntax Description
This command has no arguments or keywords.
Defaults
The TXC signal is not inverted.
Command Modes
Interface configuration
Command History
Usage Guidelines
Use this command if the DCE cannot receive SCTE from the DTE, the data is running at high speeds, and the transmission line is long. The dte-invert-txc command prevents phase shifting of the data with respect to the clock.
On the Cisco 4000 series, you can specify the serial Network Processor Module timing signal configuration. When the board is operating as a DTE, the dte-invert-txc command inverts the TXC clock signal it gets from the DCE that the DTE uses to transmit data.
If the DCE accepts SCTE from the DTE, use no dte-invert-txc.
Examples
The following example inverts the TXC on serial interface 0:
Router(config)# interface serial 0Router(config-if)# dte-invert-txcduplex
To configure duplex operation on an interface, use the duplex command in interface configuration mode. Use the no form of this command to return to the default value.
duplex {full | half | auto}
no duplex
Syntax Description
Defaults
Half-duplex mode
For the 4-Port 10/100 Fast Ethernet SPA and the 2-Port 10/100/1000 Gigabit Ethernet SPA on the Cisco 7304 router, the default is auto.
Command Modes
Interface configuration
Command History
Usage Guidelines
General Usage Guidelines
To use the autonegotiation capability (that is, detect speed and duplex modes automatically), you must set both the speed command and duplex command to auto.
Duplex Options and Interfaces
Table 9 lists the supported command options by interface.
If the transmission speed on a 16-port RJ-45 Gigabit Ethernet port is set to 1000, the duplex mode is set to full. If the transmission speed is changed to 10 or 100, the duplex mode stays at half duplex. You must configure the correct duplex mode when the transmission speed is changed to 10 or 100 from 1000.
Gigabit Ethernet is full duplex only. You cannot change the duplex mode on Gigabit Ethernet ports or on a 10/100/1000-Mbps port that is configured for Gigabit Ethernet.
When manually configuring the interface speed to either 10 or 100 Mbps, you should also configure the duplex mode on the interface.
Caution
Usage Guidelines for the 4-Port 10/100 Fast Ethernet SPA and the 2-Port 10/100/1000 Gigabit Ethernet SPA on the Cisco 7304 router.
The duplex command applies to Shared Port Adapter (SPA) interfaces that are using RJ-45 media. Gigabit Ethernet interfaces using fiber media support full-duplex mode only, and use the negotiation command to enable and disable autonegotiation.
To enable the autonegotiation capability on an RJ-45 interface, you must set either the speed command or the duplex command to auto. The default configuration is that both commands are set to auto.
Note
Table 10 describes the interface behavior for different combinations of the duplex and speed command settings. The specified duplex command configured with the specified speed command produces the resulting system action.
If you specify both a duplex and speed setting other than auto on an RJ-45 interface, then autonegotiation is disabled for the interface.
Note
Note
If you disable autonegotiation, then you must be sure that the remote device is configured to support flow control because flow control is automatically enabled for all interfaces on the 4-Port 10/100 Fast Ethernet SPA.
Examples
The following example shows how to configure full-duplex operation on a Cisco AS5300:
Router(config)# interface fastethernet 0Router(config-if)# duplex fullThe following example specifies advertisement of half-duplex support only, and either 10-Mbps or 100-Mbps capability during autonegotiation for the second interface (port 1) on the SPA located in the bottom subslot (1) of the MSC that is installed in slot 2 of the Cisco 7304 router:
Router# configure terminal
Router(config)# interface fastethernet 2/1/1
Router(config-if)# duplex half
Router(config-if)# speed auto
With this configuration, the interface advertises the following capabilities during autonegotiation:
•
•
Note
Related Commands
dxi interface-dfa
To specify a map command for a point to point serial interface, use the Data Exchange Interface (dxi) command dxi interface-dfa in interface configuration mode. To deletct the map command, use the no form of this command.
dxi interface-dfa vpi-number vci[snap | mux]
no dxi interface-dfa vpi-number vci
Syntax Description
Defaults
No map command is specified.
Command Modes
Interface configuration
Defaults
No map definition is established.
Command Modes
Interface configuration
Command History
10.3
This command was introduced.
12.4
This command was integrated into Cisco IOS Release 12.4.
Examples
The following example shows how to specify a map command.
Router(config)# interface serial 1Router(config-if)# dxi interface-dfa 10Related Commands
dxi pvc
Configures multiprotocol or single protocol AMT-Data Exchange Interface (dxi) encapsulation.
dxs3mode
To define the controller type as an E3 or T3 controller, use the dxs3mode command in controller configuration mode. To remove the controller, use the no form of this command.
dxs3mode [e3 | t3]
no dxs3mode [e3 | t3]
Syntax Description
Defaults
t3
Command Modes
Controller configuration
Command History
Examples
The following example defines a T3 controller:
Router(config)# controller dsx3 2/0/0Router(config-controller)# dsx3mode t3Related Commands
e2-clockrate
To configure serial interface 0 for E2 (8 MHz full duplex) and to shut down the other three serial interfaces (1 to 3), use the e2-clockrate command in interface configuration mode. To disable the full duplex E2, use the no form of this command.
e2-clockrate
no e2-clockrate
Syntax Description
This command has no arguments or keywords.
Defaults
All interfaces are running.
Command Modes
Interface configuration
Command History
Usage Guidelines
The e2-clockrate command is an interface configuration command and is seen only with interface serial0. When this command is used, serial interface 0 supports speeds up to E2 (8 MHz full duplex) and the other three serial interfaces (1 to 3) are put in the "shutdown" state. Also, running this command displays the following warning message:
Serial interface 0 is configured to support E2 rates and serial ports "1-3" are moved to shutdown state.Examples
The following example shows sample display output for the e2-clockrate EXEC command.
Router(config-if)# e2-clockrateInterface Serial 0 is configured to support clockrates up to E2 (8Mbps)Interfaces serial 1-3 will not be operationalRelated Commands
clock rate
Configures the clock rate for the hardware connections on serial interfaces such as NIMs and interface processors to an acceptable bit rate.
early-token-release
To enable early token release on Token Ring interfaces, use the early-token-release command in interface configuration mode. To disable this function, use the no form of this command.
early-token-release
no early-token-release
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Early token release is a method whereby the Token Ring interfaces can release the token back onto the ring immediately after transmitting, rather than waiting for the frame to return. This feature helps increase the total bandwidth of the Token Ring.
The Token Ring Interface Processor (TRIP) on the Cisco 7500 series routers and the Token Ring adapters on the Cisco 7200 series routers all support early token release.
Examples
The following example enables the use of early token release on Token Ring interface 1:
Router(config)# interface tokenring 1Router(config-if)# early-token-releaseThe following example enables the use of early token release on the Token Ring interface processor in slot 4 on port 1 on the Cisco 7500 series routers:
Router(config)# interface tokenring 4/1Router(config-if)# early-token-releaseeigrp interface
Note
To set a threshold value to minimize hysteresis in a router-to-radio configuration, use the eigrp interface command in interface configuration mode. To reset the hysteresis threshold to the default value, use the no form of this command.
eigrp vmi-interface-number interface [dampening-change value] [dampening-interval value]
no eigrp vmi-interface-number interface [dampening-change value] [dampening-interval value]
Syntax Description
Command Default
Default for change-based dampening is 50 percent of the computed metric.
Default for interval-based dampening is 30 seconds.
Command Modes
Interface configuration (config-if)
Command History
Usage Guidelines
This command advertises routing changes for EIGRP traffic only.
The REPLY sent to any QUERY will always contain the latest metric information. Exceptions which will result in immediate UPDATE being sent:
•
•
•
Change-based Dampening
The default value for the change tolerance will be 50% of the computed metric. It can be configured in the range from 0 to 100 percent. If the metric change of the interface is not greater (or less) than the current metric plus or minus the specified amount, the change will not result in a routing change, and no update will be sent to other adjacencies.
Interval-based Dampening
The default value for the update intervals is 30 seconds. It can be configured in the range from 0 to 64535 seconds. If this option is specified, changes in routes learned though this interface, or in the interface metrics, will not be advertised to adjacencies until the specified interval is met. When the timer expires, any changes detected in any routes learned through the interface, or the metric reported by the interfaces will be sent out.
Examples
Change-based Dampening Example
The following example sets the threshold to 50 percent tolerance routing updates involving VMI interfaces and peers:
interface vmi1ip address 10.2.2.1 255.255.255.0ipv6 address 2001:0DB1:2::1/96ipv6 enableeigrp 1 interface dampening-change 50physical-interface Ethernet0/0Interval-based Dampening Example
The following example sets the interval to 30 seconds at which updates occur for topology changes that affect VMI interfaces and peers:
interface vmi1ip address 10.2.2.1 255.255.255.0ipv6 address 2001:0DB1:2::1/96ipv6 enableeigrp 1 interface dampening-interval 30physical-interface Ethernet0/0Related Commands
emulation-mode
To configure Configuration Circuit Emulation (CEM), use the emulation-mode command in unidirectional mode.
emulation-mode { bidirectional | {unidirectional {rx | tx} }
no emulation-mode
Syntax Description
Command Default
Default mode is unidirectional mode.
Command Modes
Configuration CEM mode (emulation-mode).
Command History
12.4(20)YA
This command was introduced.
12.4(22)T
This command is integrated into Cisco IOS Release 12.4(22)T.
Usage Guidelines
You can use the emulation-mode command to configure the CEM in unidirectional mode. Once configured, traffic will flow only in that direction through the CEM channel. The CEM status gets displayed as "active (rx-only)" or "active (tx-only)" depending on the configuration. To disable the effect of the command, use the no form of this command.
Examples
The following example shows how the command configures the traffic in unidirectional mode:
Router(config-cem)# emulation-mode unidirectional txThe following example shows how the command configures the traffic in bidirectional mode:
Router(config-cem)# emulation-mode bidirectionalencapsulation
To set the encapsulation method used by the interface, use the encapsulation command in interface configuration mode. To remove the encapsulation, use the no form of this command.
encapsulation encapsulation-type
no encapsulation encapsulation-type
Syntax Description
Defaults
The default depends on the type of interface. For example, synchronous serial interfaces default to HDLC and asynchronous interfaces default to SLIP.
Command Modes
Interface configuration
Command History
Usage Guidelines
SLIP and PPP
To use SLIP or PPP, the router or access server must be configured with an IP routing protocol or with the ip host-routing command. This configuration is done automatically if you are using old-style slip address commands. However, you must configure it manually if you configure SLIP or PPP via the interface async command.
On lines configured for interactive use, encapsulation is selected by the user when they establish a connection with the slip or ppp EXEC command.
IP Control Protocol (IPCP) is the part of PPP that brings up and configures IP links. After devices at both ends of a connection communicate and bring up PPP, they bring up the control protocol for each network protocol that they intend to run over the PPP link such as IP or IPX. If you have problems passing IP packets and the show interface command shows that line is up, use the negotiations command to see if and where the negotiations are failing. You might have different versions of software running, or different versions of PPP, in which case you might need to upgrade your software or turn off PPP option negotiations. All IPCP options as listed in RFC 1332, PPP Internet Protocol Control Protocol (IPCP), are supported on asynchronous lines. Only Option 2, TCP/IP header compression, is supported on synchronous interfaces.
PPP echo requests are used as keepalive packets to detect line failure. The no keepalive command can be used to disable echo requests. For more information about the no keepalive command, refer to the chapter "IP Services Commands" in the Cisco IOS IP Command Reference, Volume 1 of 4: Addressing and Services and to the chapter "Configuring IP Services" in the Cisco IOS IP Configuration Guide.
To use SLIP or PPP, the Cisco IOS software must be configured with an IP routing protocol or with the ip host-routing command. This configuration is done automatically if you are using old-style slip address commands. However, you must configure it manually if you configure SLIP or PPP via the interface async command.
Note
SS7
The SS7 encapsulation command is new with the Integrated SLT feature and is available only for interface serial objects created by the channel-group command. For network access server (NAS) platforms, the encapsulation for channel group serial interface objects defaults to HDLC. You must explicitly set the encapsulation type to SS7 to override this default.
When encapsulation is set to SS7, the encapsulation command for that object is no longer available. A serial SS7 link is deleted only when its associated dial feature card (DFC) card is removed. As with existing Cisco 26xx-based SLTs, you do not need to specify whether the SS7 link is to be used as an A-link or an F-link.
By itself this command does not select the correct encapsulation type. Therefore, once created, you must set the encapsulation type to the new SS7 value, as well as assign a session channel ID to the link at the serial interface command level. The configuration on a digital SS7 link can be saved (no shutdown) only when its encapsulation is successfully set to SS7 and it has been assigned a channel identifier.
VLANs
Do not configure encapsulation on the native VLAN of an IEEE 802.1q trunk without the native keyword. (Always use the native keyword when the vlan-id is the ID of the IEEE 802.1q native VLAN.)
For detailed information on use of this command with VLANs, refer to the Cisco IOS Switching Services Configuration Guide and the Cisco IOS Switching Services Command Reference.
Examples
The following example shows how to reset HDLC serial encapsulation on serial interface 1:
Router(config)# interface serial 1Router(config-if)# encapsulation hdlcThe following example shows how to enable PPP encapsulation on serial interface 0:
Router(config)# interface serial 0Router(config-if)# encapsulation pppThe following example shows how to configure async interface 1 for PPP encapsulation:
Router(config)# interface async 1Router(config-if)# encapsulation pppTo learn more about the virtual serial interface and check SS7 encapsulation, enter the show interfaces serial slot/trunk:channel-group command in privileged EXEC mode, as in the following example:
Router# show interfaces serial 7/3:1Serial7/3:1 is up, line protocol is downHardware is PowerQUICC SerialMTU 1500 bytes, BW 1544 Kbit, DLY 20000 usec,reliability 255/255, txload 4/255, rxload 1/255Encapsulation SS7 MTP2, loopback not setKeepalive set (10 sec)Last input never, output 00:00:00, output hang neverLast clearing of "show interface" counters 03:53:40Queueing strategy: fifoOutput queue 0/40, 0 drops; input queue 0/75, 0 drops5 minute input rate 0 bits/sec, 0 packets/sec5 minute output rate 26000 bits/sec, 836 packets/sec0 packets input, 0 bytes, 0 no bufferReceived 0 broadcasts, 0 runts, 0 giants, 0 throttles0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort11580159 packets output, 46320636 bytes, 0 underruns0 output errors, 0 collisions, 1 interface resets0 output buffer failures, 0 output buffers swapped out2 carrier transitionsDCD=up DSR=down DTR=down RTS=down CTS=downRelated Commands
end (satellite initial configuration)
To exit satellite initial configuration mode, save any new or changed parameters, and reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the end command in satellite initial configuration mode.
end
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
The end command is identical to the exit command in satellite initial configuration mode.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Examples
The following example shows what appears when you enter the end or exit command after changing one or more initial configuration parameters:
Router(sat-init-config)# endApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router#The following example shows what appears when you enter the end or exit command when no parameters have been changed:
Router(sat-init-config)# endRouter#Related Commands
equipment loopback
To run loopbacks in conjunction with remote equipment, use the equipment loopback command in controller configuration mode. To terminate the loopback, use the no form of this command.
equipment [customer | network] loopback
no equipment [customer | network] loopback
Syntax Description
customer
(Optional) Enables the line card to respond to remote T3 loopback commands from the remote T3 equipment.
network
(Optional) Causes the line card to ignore remote T3 loopback commands.
Defaults
No default behavior or values.
Command Modes
Controller configuration
Command History
Examples
The following example configures an equipment network loopback:
Router(config)# controller t3 1/0/0Router(config-controller)# equipment network loopbackRelated Commands
errdisable detect cause
To enable the error-disable detection, use the errdisable detect cause command in global configuration mode. To disable the error-disable detection, use the no form of this command.
errdisable detect cause {all | dtp-flap | l2ptguard | link-flap | packet-buffer-error | pagp-flap | udld}
no errdisable detect cause {all | dtp-flap | l2ptguard | link-flap | pagp-flap | udld}
Syntax Description
Defaults
Enabled for all causes
Command Modes
Global configuration
Command History
Usage Guidelines
Note
A cause (bpduguard, dtp-flap, link-flap, pagp-flap, root-guard, udld) is defined as the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in an error-disabled state (an operational state that is similiar to the link-down state).
You must enter the shutdown and then the no shutdown commands to recover an interface manually from the error-disable state.
Examples
This example shows how to enable the error-disable detection for the Layer 2 protocol-tunnel guard error-disable cause:
Router(config)# errdisable detect cause l2ptguardRouter(config)#Related Commands
errdisable recovery
To configure the recovery mechanism variables, use the errdisable recovery command in global configuration mode. To return to the default state, use the no form of this command.
errdisable recovery cause all | arp-inspection | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap | gbic-invalid | l2ptguard | link-flap | pagp-flap | pesecure-violation | security-violation | udld | unicast-flood
errdisable recovery interval interval
no errdisable recovery cause all | {arp-inspection | bpduguard | channel-misconfig | dhcp-rate-limit | dtp-flap | gbic-invalid | l2ptguard | link-flap | pagp-flap | pesecure-violation | security-violation | udld | unicast-flood
no errdisable recovery interval interval
Syntax Description
Defaults
The defaults are as follows:
•
•
Command Modes
Global configuration
Command History
Usage Guidelines
The secure-violation option is not supported.
A cause (bpduguard, dhcp-rate-limit, dtp-flap, l2ptguard, link-flap, pagp-flap, security-violation, channel-misconfig, psecure-violation, udld, or unicast-flood) is defined as the reason why the error-disabled state occurred. When a cause is detected on an interface, the interface is placed in an error-disabled state (an operational state that is similiar to the link-down state). If you do not enable errdisable recovery for the cause, the interface stays in the error-disabled state until a shutdown and no shutdown occurs. If you enable recovery for a cause, the interface is brought out of the error-disabled state and allowed to retry operation once all the causes have timed out.
You must enter the shutdown and then the no shutdown commands to recover an interface manually from the error-disabled state.
Examples
This example shows how to enable the recovery timer for the BPDU-guard error-disable cause:
Router(config)# errdisable recovery cause bpduguardRouter(config)#This example shows how to set the timer to 300 seconds:
Router(config)# errdisable recovery interval 300Router(config)#Related Commands
error throttling
To stop receiving error data packets on multiple channel groups configured on all interfaces on the T1 controller of a channelized T3 port adapter, use the error throttling command in T3 controller configuration mode. To continue receiving error data packets on all channels on the T1 controller, use the no form of this command.
error throttling
no error throttling
Syntax Description
This command has no arguments or keywords.
Defaults
The error throttling command is enabled by default.
Command Modes
T3 controller configuration
Command History
Usage Guidelines
Use the show controllers t3 command to display whether the current router configuration has error throttling enabled or disabled.
The error throttling command disables the T1 level clock in order to stop receiving error data packets on a T1 controller.
When a T1 has multiple channel groups configured over it, error throttling affects all the channels on a T1. If any single interface receives a burst of errors, over a short duration, such as 400 errors in 100 milliseconds, the T1 clock is turned off for a period of 100 milliseconds. The reason is that when there is a high rate of errors, the error rate is very likely to continue for a long duration of time. Using error throttling to stop receiving the error data packets reduces wasteful processing and discarding of error packets.
The no error throttling command allows all the error data packets to be processed, dropped, and accounted for on a T1 controller. When the error rate is high, the CPU can become overloaded.
When the no error throttling command is used to configure a T3 port, the configuration applies to all of the 28 associated T1 channels.
Examples
The following example enables error throttling by disabling the T1 clock in order to stop receiving error data packets on a T1 controller:
Router(config-controller)# error throttlingThe following example uses the show controllers t3 command to display partial output showing that error throttling is enabled on the T1 controller:
Router# show controllers t3 2/1/0T3 2/1/0 is down. Hardware is 2CT3 single wide port adapterCT3 H/W Version: 0.2.2, CT3 ROM Version: 1.0, CT3 F/W Version: 2.5.1FREEDM version: 1, reset 0 resurrect 0Applique type is Channelized T3Transmitter is sending remote alarm.Receiver has loss of signal.FEAC code received: No code is being receivedFraming is M23, Line Code is B3ZS, Clock Source is InternalRx-error throttling on T1's ENABLED...Related Commands
show controllers t3
Displays whether the current router configuration has error throttling enabled or disabled.
exit (satellite initial configuration)
To exit satellite initial configuration mode, save any new or changed parameters, and reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the exit command in satellite initial configuration mode.
exit
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Satellite initial configuration
Command History
Usage Guidelines
The exit command is identical to the end command in satellite initial configuration mode.
When you enter the exit or end command to exit satellite initial configuration mode, the system automatically saves any changed parameters to the NM-1VSAT-GILAT network module nonvolatile memory and resets the NM-1VSAT-GILAT network module.
Examples
The following example shows what appears when you enter the exit or end command after changing one or more initial configuration parameters:
Router(sat-init-config)# exitApplying changed parameters to the satellite module.Parameter update succeeded. Module is now resetting.Router#The following example shows what appears when you enter the exit or end command when no parameters have been changed:
Router(sat-init-config)# exitRouter#Related Commands
