-
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
test platform police ipv6 disable
test satellite satellite mfg link
test satellite satellite reset
transmit-buffers backing-store
tug-2 e1 channel-group timeslots
t1
To create a logical T1 controller from each of the specified time slots of the T3 line, use the t1 command in controller configuration mode. To delete the defined logical controller, use the no form of this command.
t1 ds1 controller
no t1 ds1 controller
Syntax Description
Defaults
No default behavior or values.
Command Modes
Controller configuration
Command History
Usage Guidelines
The purpose of this command is to convert the collection of the 28 T1 controllers comprising the T3 controller into individual T1 controllers that the system can use. In other words, the Cisco AS5800 access server cannot pass data until a T1 controller is configured (using the controller command), and you cannot configure a T1 controller until it has been created using the t1 command.
Examples
The following example shows how to configure a logical T1 controller at T1 time slot 1 for the T3 controller located in shelf 1, slot 4, port 0. Note that you have to enter the command from controller configuration mode.
Router(config)# controller t3 1/4/0Router(config-controller)# t1 1 controllerRouter(config-controller)# endRelated Commands
controller
Configures a T1 and other types of controller and enters controller configuration mode.
controller t3
Configures a T3 controller.
t1 bert
To enable or disable a bit error rate tester (BERT) test pattern for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 bert command in controller configuration mode. To disable a BERT test pattern, use the no form of this command.
t1 channel bert pattern {0s | 1s | 2^15 | 2^20 | 2^23} interval minutes [unframed]
no t1 channel bert pattern {0s | 1s | 2^15 | 2^20 | 2^23} interval minutes [unframed]
Syntax Description
Defaults
No BERT test is performed.
Command Modes
Controller configuration
Command History
Usage Guidelines
The BERT test patterns from the CT3IP are framed test patterns (that is, the test patterns are inserted into the payload of the framed T1 signal).
To view the BERT results, use the show controller t3 or show controller t3 brief EXEC commands. The BERT results include the following information:
•
Type of test pattern selected
•
•
•
•
•
When the T1 channel has a BERT test running, the line state is DOWN. Also, when the BERT test is running and the Status field is Not Sync, the information in the total bit errors field is not valid. When the BERT test is done, the Status field is not relevant.
The t1 bert command is not written to NVRAM because it is only used for testing the T1 channel for a short predefined interval and for avoiding accidentally saving the command, which could cause the interface not to come up the next time the router reboots.
Note
numbering schemes for T1 channels within channelized T3 equipment.Examples
The following example shows how to run a BERT test pattern of all zeros for 30 minutes on T1 channel 6 on the CT3IP in slot 9:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 6 bert pattern 0s interval 30Related Commands
show controllers t3
Displays the hardware and software driver information for a T3 controller.
t1 clock source
To specify where the clock source is obtained for use by each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 clock source command in controller configuration mode.
t1 channel clock source {internal | line}
Syntax Description
channel
Number between 1 and 28 that indicates the T1 channel.
internal
Specifies that the internal clock source is used. This is the default.
line
Specifies that the network clock source is used.
Defaults
Internal
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 clock source command, the default clock source of internal is used by all the T1s on the CT3IP.
You can also set the clock source for the CT3IP by using the clock source (CT3IP) controller configuration command.
Note
(0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco
numbering schemes for T1 channels within channelized T3 equipment.This command does not have a no form.
Examples
The following example shows how to set the clock source to line T1 6 and T1 8 on the CT3IP:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 6 clock source lineRouter(config-controller)# t1 8 clock source lineRelated Commands
clock source (CT3IP)
Specifies where the clock source is obtained for use by the CT3IP in Cisco 7500 series routers.
t1 external
To specify that a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers is used as an external port so that the T1 channel can be further multiplexed on the Multichannel Interface Processor (MIP) or other multiplexing equipment, use the t1 external command in controller configuration mode. To remove a T1 as an external port, use the no form of this command.
t1 external channel [cablelength feet] [linecode [ami | b8zs]]
no t1 external channel
Syntax Description
Defaults
No external T1 is specified.
The default cable length is 133 feet.
The default line coding is B8ZS.Command Modes
Controller configuration
Command History
Usage Guidelines
The first three T1 channels (1, 2, and 3) of the CT3IP can be broken out to the DSUP-15 connectors on the CPT3IP so that the T1 channel can be further demultiplexed by the MIP on the same router or on another router.
After you configure the external T1 channel, you can continue configuring it as a channelized T1 (also referred to as a fractional T1) from the MIP. All channelized T1 commands might not be applicable to the T1 interface. After you configure the channelized T1 on the MIP, you can continue configuring it as you would a normal serial interface. All serial interface commands might not be applicable to the T1 interface.
The line coding on the T1 channel and the MIP must be the same. Because the default line coding format on the T1 channel is B8ZS and the default line coding on the MIP is AMI, you must change the line coding on the MIP or on the T1 so that they match.
To determine if the external device connected to the external T1 port is configured and cabled correctly before configuring an external port, use the show controllers t3 command and locate the line
)in the display output. The line status can be one of the following:•
•
•
Note
numbering schemes for T1 channels within channelized T3 equipment.
Note
following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example,
entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there
is no change because 200 is within the 134 to 266 range. However, if you change the cable length to
399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.Examples
The following example shows how to configure T1 1 on the CT3IP as an external port using AMI line coding and a cable length of 300 feet:
Router(config)# controllers t3 9/0/0Router(config-controller)# t1 external 1 cablelength 300 linecode amiRelated Commands
show controllers t3
Displays the hardware and software driver information for a T3 controller.
t1 fdl ansi
To enable the 1-second transmission of the remote performance reports via the Facility Data Link (FDL) per ANSI T1.403 for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 fdl ansi command in controller configuration mode. To disable the performance report, use the no form of this command.
t1 channel fdl ansi
no t1 channel fdl ansi
Syntax Description
Defaults
Disabled
Command Modes
Controller configuration
Command History
Usage Guidelines
The t1 fdl ansi command can be used only if the T1 framing type is Extended Super Frame (ESF).
To display the remote performance report information, use the show controllers t3 remote performance command.
Note
numbering schemes for T1 channels within channelized T3 equipment.Examples
The following example shows how to generate the performance reports for T1 channel 8 on the CT3IP:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 8 fdl ansiRelated Commands
show controllers t3
Displays the hardware and software driver information for a T3 controller.
t1 framing
To specify the type of framing used by T1 channels, use the t1 framing command in controller configuration mode.
Cisco 7500 Series Routers with Channelized T3 Interface Processor
t1 channel framing {esf | sf}
Channelized T3 Shared Port Adapters
t1 channel framing {esf | sf [hdlc-idle {0x7e | 0xff}] [mode {j1}]}
no t1 channel framing {esf | sf [hdlc-idle {0x7e | 0xff}] [mode {j1}]}
Syntax Description
Defaults
esf (for C3TIP)
sf (for 2-Port and 4-Port Channelized T3 SPA)
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 framing command, the default ESF is used.
Note
numbering schemes for T1 channels within channelized T3 equipment.To return to the default mode, use the no form of this command. This command does not have a no form on the Cisco 7500 series router with the CT3IP.
The mode keyword is not supported on Cisco 7304 routers with the2-Port and 4-Port Channelized T3 SPA.
Examples
The following example shows how to set the framing for the T1 6 and T1 8 on the CT3IP to Super Frame:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 6 framing sfRouter(config-controller)# t1 8 framing sfRelated Commands
controller
Configures a T1, E1, or T3 controller and enters controller configuration mode.
show controller
Displays controller configuration.
t1 linecode
To specify the type of line coding used by the T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 linecode command in controller configuration mode.
t1 channel linecode [ami | b8zs]
Syntax Description
Defaults
B8ZS
Command Modes
Controller configuration
Command History
Usage Guidelines
If you do not specify the t1 linecode command, the default B8ZS is used.
AMI Line Coding
If you select ami line coding for the T1 channel, you must also invert the data on the T1 channel by using the invert data interface command. This is required because the T1 channel is bundled into the T3 signal, so there are no local T1 line drivers and receivers associated with it. Therefore, the t1 channel linecode ami command does not modify local line driver settings. Rather, it advises the CT3IP what line code the remote T1 is using. The CT3IP uses this information solely for the purpose of determining whether or not to enable the pulse density enforcer for that T1 channel.
B8ZS Line Coding
When you select b8zs line coding, the pulse density enforcer is disabled. When you select ami line coding, the pulse density enforcer is enabled. To avoid having the pulse density enforcer corrupt data, the T1 channel should be configured for inverted data.
Note
(0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco
numbering schemes for T1 channels within channelized T3 equipment.Examples
The following example shows how to set the line coding for T1 channel 16 on the CT3IP to AMI:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 16 linecode amiRouter(config-controller)# exitRouter(config)# interface serial 9/0/0:16Router(config-if)# invert dataRelated Commands
invert data
Inverts the data stream.
loopback remote (interface)
Loops packets through a CSU/DSU, over a DS3 link or a channelized T1 link, to the remote CSU/DSU and back.
t1 logging-events
To print typical T1 controller Up and Down messages on a channelized T3 port adapter in T3 controller, use the t1 logging-events command configuration mode. To disable printing of the T1 controller Up and Down messages, use the no form of this command.
t1 {t1} logging-events [detail]
[no] t1 {t1} logging-events
Syntax Description
Defaults
The t1 logging-events command is the default.
Command Modes
T3 controller configuration mode.
Command History
Usage Guidelines
This command refers to the T1 controller as part of a T3 controller.
The no t1 logging-events command disables printing of the controller Up and Down messages. These messages will appear neither on the console nor in the logs.
Examples
The following example uses the t1 logging-events command to print normal controller Up and Down messages, without indicating the reason code for a changed state. The T1 1 controller is part of the T3 controller with a bay/port of 4/1.
Router(config-controller)# t1 1 logging-events*Jun 20 00:29:39: %CONTROLLER-5-UPDOWN: Controller T3 4/1 T1 1, changed state to UP*Jun 20 00:30:09: %CONTROLLER-5-UPDOWN: Controller T3 4/1 T1 1, changed state to DOWNThe following example uses the t1 logging-events detail command to show the Out-of-Frame (OOF) reason code when the T1 1 controller of a T3 controller with a bay/port of 4/1 changes from an Up state to a Down state:
Router(config-controller)# t1 1 logging-events detail*Jun 19 17:47:50: %CONTROLLER-5-DOWNDETAIL: Controller T3 4/1 T1 1, changed state to down due to OOFRelated Commands
logging-events
Prints typical T3 controller Up and Down messages on a channelized T3 port adapter.
t1 span
To enable link noise monitoring on a clear channel T1 link on Cisco 10000 series routers, use the t1 span command in controller configuration mode. To disable link noise monitoring, use the no form of this command.
t1 channel span {minor-warn | remove | major-warn}[duration seconds | lcv threshold [pcv threshold] [set | clear]]
no t1 channel span {minor-warn | remove | major-warn}[duration seconds | lcv threshold [pcv threshold] [set | clear]]
Syntax Description
Command Default
Link Noise Monitoring on any T1 or E1 link is disabled by default. If enabled without specifying any thresholds, the default values are used as mentioned in the Syntax Description.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
Note the following when configuring link noise monitoring on T1 and E1 links:
•
•
•
•
•
•
•
•
•
•
Examples
The following example shows how to generate an exceed event for a minor warning, if the number of LCVs on the T1 line remain above or equal to 20, or the number of PCVs remains above or equal to 10 for 10 continuous seconds.
Router(config-controller)# t1 1 span minor-warn lcv 20 pcv 10 duration 10 setThe following example shows how to generate an improve event for a minor warning, if the number of LCVs on the T1 line remain below 15 or the number of PCVs remain below 8 for 20 continuous seconds.
Router(config-controller)# t1 1 span minor-warn lcv 15 pcv 8 duration 20 clearThe following example shows the same threshold value being used by the set and clear conditions, when both keywords are not specified. In this example, the threshold value is 80 for both conditions.
Router(config-controller)# t1 1 span major-warn lcv 150 pcv 100 duration 80Router(config-controller)# endRouter# show running-config | section controller sonet 7/0/0controller SONET 7/0/0framing SONETpath 1 controller t3clock source internalcontroller T3 7/0/0.1t1 1 channel-group 0 timeslots 1-24t1 1 span minor-warn lcv 150 pcv 100 duration 80 sett1 1 span minor-warn lcv 150 pcv 100 duration 80 clearThe following example shows how the threshold value specified for the clear condition is used by the set condition when set condition is not specified. In this example, the threshold value of 100 specified for the clear condition is used for the set condition.
Router(config-controller)# t1 1 span major-warn lcv 100 pcv 70 duration 100 clearRouter(config-controller)# endRouter# show running-config | section controller sonet 7/0/0controller SONET 7/0/0framing SONETpath 1 controller t3clock source internalcontroller T3 7/0/0.1t1 1 channel-group 0 timeslots 1-24t1 1 span minor-warn lcv 100 pcv 70 duration 100 sett1 1 span minor-warn lcv 100 pcv 70 duration 100 clearThe following is a sample output showing the details of the calculated PCV threshold value. The calculated PCV value is 141:
Router# debug c10k lnmRouter(config-controller)# t1 1 span major-warn lcv 150Router(config-controller)# end*Sep 10 20:34:43.923: T1 extrapolation: pcv_delta=130 lcv_delta=139 factor=140 pcv_const=14computed pcv_threshold = 141*Sep 10 20:34:43.923: CMD for minor-warn set*Sep 10 20:34:43.923: clear taking set thresholds*Sep 10 20:34:43.923: T3 7/0/0.1#1 setting values to be sent to LC for WARN ENABLE 3*Sep 10 20:34:43.923:3, 150, 150, 141, 141, 10, 10, 0, 0, 0, 0, 0, 0Router# show running-config | section controller sonet 7/0/0controller SONET 7/0/0framing SONETpath 1 controller t3clock source internalcontroller T3 7/0/0.1t1 1 channel-group 0 timeslots 1-24t1 1 span minor-warn lcv 150 pcv 141 duration 10 sett1 1 span minor-warn lcv 150 pcv 141 duration 10 clearRelated Commands
t1 span syslog
To generate syslog messages for all the spans on which the link noise monitoring feature is enabled, use the t1 span syslog command in controller configuration mode. To disable the generation of syslog messages, use the no form of this command.
t1 channel span syslog
no t1 channel span syslog
Syntax Description
channel
Number that indicates the T1 channel. The range is from 1 to 28.
syslog
Generates syslog messages for T1 links that are enabled with the Link Noise Monitoring feature.
Command Default
Syslog messages are disabled by default.
Command Modes
Controller configuration (config-controller)
Command History
Usage Guidelines
The Cisco 10000 series router is a scalable platform and supports up to 4000 T1 links on one chassis. When enabled, syslog messages are generated for all T1 links on which link noise monitoring is configured. A syslog event is reported as a message. The syslog report stores the last five events.
When an `exceed' event is reported, a syslog message is generated. Such syslog messages from all links clog up the logging buffer. When enabling syslog messages, a message prompts you to confirm whether to generate syslog messages or not.
To view the events for a line card, use the show controller type number lnm event command in the privileged EXEC mode. To view the events for a SPA, use the show platform spa slot/subslot lnm event command.
Examples
The following example shows the message displayed when the minor warning threshold has exceeded:
LNM-3- MINWARNEXCEED: Interface Serial7/0/0.1/1:0, noise exceeded above minor warning thresholdThe following example shows the sample output of the show controller command, when executed for a specified T1 channel:
Router# show controllers t3 7/0/0.1 /5 lnmChannel Monitoring type Thresholds (lcv/pcv/duration)--------------------------------------------------------------------------------5 minor-warn (syslog disabled) Set(154 /145 /10 ) Clear(154 /145 /10 )Router#The following example shows the sample output of the last five stored messages:
Router# show controller t3 7/0/0.1 lnm eventsChannel Last five events--------------------------------------------------------------------------------1 MINWARNEXCEED : Noise exceeded minor-warn thresholds at Jun 11 1995 13:42:01MAJWARNEXCEED : Noise exceeded major-warn thresholds at Jun 11 1995 13:42:01MINWARNIMPROVE: Noise improved minor-warn thresholds at Jun 11 1995 13:42:01MAJWARNIMPROVE: Noise improved major-warn thresholds at Jun 11 1995 13:42:012 Channel not configured for E1/T13 Channel not configured for E1/T14 No events5 Channel not configured for E1/T1Related Commands
t1 test
To break out a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers to the test port for testing, use the t1 test command in controller configuration mode. To remove the T1 channel from the test port, use the no form of this command.
t1 test channel [cablelength feet] [linecode [ami | b8zs]]
no t1 test channel
Syntax Description
Defaults
No test port is configured.
The default cable length is 133 feet.
The default line coding is B8ZS.Command Modes
Controller configuration
Command History
Usage Guidelines
You can use the T1 test port available on the CT3IP to break out any of the 28 T1 channels for testing (for example, 24-hour bit error-rate tester (BERT) testing as is commonly done by telephone companies before a line is brought into service).
The T1 test port is also available as an external port. For more information on configuring an external port, see the t1 external controller configuration command.
To determine if the external device connected to the T1 test port is configured and cabled correctly before configuring a test port, use the show controllers t3 command and locate the line
-controller)in the display output. The line status can be one of the following:•
•
•
Note
(0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco
numbering schemes for T1 channels within channelized T3 equipment.
Note
following ranges: 0 to 133, 134 to 266, 267 to 399, 400 to 533, and 534 to 655. For example,
entering 150 feet uses the 134 to 266 range. If you later change the cable length to 200 feet, there is
no change because 200 is within the 134 to 266 range. However, if you change the cable length to
399, the 267 to 399 range is used. The actual number you enter is stored in the configuration file.Examples
The following example shows how to configure T1 6 on the CT3IP as a test port using the default cable length and line coding:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 test 6Related Commands
t1 timeslot
To specify the time slots and data rate used on each T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 timeslot command in controller configuration mode. To remove the configured T1 channel, use the no form of this command.
t1 channel timeslot range [speed {56 | 64}]
no t1 channel timeslot
Syntax Description
Defaults
No time slots are specified for the T1 channel.
The default data rate is 64 kbps.Command Modes
Controller configuration
Command History
Usage Guidelines
You must specify the time slots used by each T1 channel.
Note
(0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco
numbering schemes for T1 channels within channelized T3 equipment.Examples
The following example shows how to assign time slots 1 through 24 to T1 1 for full T1 bandwidth usage:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 1 timeslot 1-24The following example shows how to assign time slots 21 to 23 and 26 to 28 and a data rate of 56 kbps to T1 6 for fractional T1 bandwidth usage:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 6 timeslot 21-23,26-28 speed 56t1 yellow
To enable detection and generation of yellow alarms for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7500 series routers, use the t1 yellow command in controller configuration mode. To disable the detection and generation of yellow alarms, use the no form of this command.
t1 channel yellow {detection | generation}
no t1 channel yellow {detection | generation}
Syntax Description
Defaults
Yellow alarms are detected and generated on the T1 channel.
Command Modes
Controller configuration
Command History
Usage Guidelines
If the T1 framing type is super frame (SF), you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with SF framing.
NoteExamples
The following example shows how to disable the yellow alarm detection on T1 channel 6 on the CT3IP:
Router(config)# controller t3 9/0/0Router(config-controller)# t1 6 framing sfRouter(config-controller)# no t1 6 yellow detectiontcam priority
To prioritize the interfaces for forwarding to software in the event of Ternary Content Addressable Memory (TCAM) entry or label exhaustion, use the tcam priority command interface configuration mode. To revert to the default setting, use the no form of this command.
tcam priority [high | low]
no tcam priority
Syntax Description
Defaults
normal
Command Modes
Interface configuration
Command History
Usage Guidelines
The interfaces are chosen in this order:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
Examples
This example shows how to set the priority:
Router(config-if)# tcam priority lowRelated Commands
termination
To configure the termination mode of the controller, use the termination command in the controller configuration mode.
termination [co | cpe]
Syntax Description
Command Default
The command default termination mode is CPE.
Command Modes
Controller configuration mode (config-controller)
Command History
Examples
The following example shows the line termination set to "co":
Router(config-controller)# termination coRelated Commands
controller shdsl
Configures a controller for single-pair high-bit-rate digital subscriber line (SHDSL) mode.
test aim eeprom
To test the data compression Advanced Interface Module (AIM) after it is installed in the Cisco 2600 series router, use the test aim eeprom command in privileged EXEC mode.
test aim eeprom
Syntax Description
This command has no arguments or keywords.
Defaults
No tests are performed on the data compression AIM card.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
This command does not have a no form.
CautionThis command is the AIM counterpart of the test pas eeprom command, which performs similar tasks for port modules.
Table 1 shows the questions asked of the user when the test aim eeprom command is entered, and the recommended user responses.
There is a danger that you can erase all bytes in the entire EEPROM. Though it is good to have a diagnostic tool that allows you to read and write data, there is a danger that lost data will make the Advanced Interface Module (AIM) card fail.
During your session with the test dialog, you have access to the following commands:
Examples
The following example displays the test aim eeprom command user dialog:
Router# test aim eepromAIM Slot [0]: 0Use NMC93C46 ID EEPROM [y]: yAIM Slot 0 eeprom (? for help)[?]: ?d - dump eeprom contentse - erase all locations (to 1)p - primitive accessq - exit eeprom testz - zero eeprom'c' rules of radix type-in and display apply.AIM Slot 0 eeprom (? for help)[?]:test cable-diagnostics
To test the condition of 10-Gigabit Ethernet links or copper cables on 48-port 10/100/1000 BASE-T modules, use the test cable-diagnostics command in privileged EXEC mode.
test cable-diagnostics tdr interface type number
Syntax Description
Defaults
This command has no default settings.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Cable diagnostics can help you detect whether your cable has connectivity problems.
The TDR test guidelines are as follows:
•
•
•
•
•
•
Router# test cable-diagnostics tdr interface gigabitethernet2/12% Interface Gi2/12 is administratively down% Use 'no shutdown' to enable interface before TDR test start.•
•
•
•
•
Examples
This example shows how to run the TDR-cable diagnostics:
Router # test cable-diagnostics tdr interface gigabitethernet2/1TDR test started on interface Gi2/1A TDR test can take a few seconds to run on an interfaceUse 'show cable-diagnostics tdr' to read the TDR results.Related Commands
Clears a specific interface or clears all interfaces that support TDR.
Displays the test results for the TDR cable diagnostics.
test interface fastethernet
To test the Fast Ethernet interface by causing the interface to ping itself, use the test interface fastethernet command in user EXEC or privileged EXEC mode.
test interface fastethernet number
Syntax Description
Command Modes
User EXEC
Privileged EXECCommand History
Usage Guidelines
This command sends pings from the specified interface to itself. Unlike the ping command, the test interface fastethernet command does not require the use of an IP address.
Examples
The following example shows how to test a Fast Ethernet interface on a Cisco 4500 router:
Router# test interface fastethernet 0Related Commands
test platform police get
To get the IPv6 internal police rate, use the test platform police get command in privileged EXEC mode.
test platform police get
Syntax Description
This command has no arguments or keywords.
Command Default
0 (No rate has been applied.)
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRD1
The command was introduced on the Cisco 7600 series routers for the ES+ line cards, the SIP-400, and the 7600-ES+ITU-2TG and 7600-ES+ITU-4TG.
Usage Guidelines
Use this command under the exec command of the line card console. It is not visible from the route processor (RP) console.
Examples
The following example shows how to get the IPv6 internal police rate:
Router> enableRouter# test platform police getIPv6 with HBH header is policed at 100000 kbpsRelated Commands
test platform police set
To set the IPv6 internal police rate, use the test platform police set command in privileged EXEC mode. This command does not have a no form.
test platform police set rate
NoteSyntax Description
Command Default
For ES40 line cards, the default police rate is 12.8 Mbps.
For the SIP-400, the default police rate is 21.36 kpps.
Command Modes
Privileged EXEC (#)
Command History
12.2(33)SRD1
The command was introduced on the Cisco 7600 series routers for the ES+ line cards, the SIP-400, and the 7600-ES+ITU-2TG and 7600-ES+ITU-4TG.
Usage Guidelines
Use this command under the EXEC command of the line card console. It is not visible from the route processor (RP) console.
For both the ES+ line cards and the SIP-400, setting the police rate to 0 turns off the policing.
For both the ES+ line cards and the SIP-400, when the policer is set from the the line card console, the setting remains effective even if the line card is moved to another chassis running the Cisco IOS Release 12.2(33)SRD1 (or later) image.
For the SIP-400, IPv6 HBH packets will continue to go through the QoS policing configured on the line card. For ES+ line cards, IPv6 HBH packets will bypass any QoS configured on the line card.
Examples
The following examples shows how to set the IPv6 with HBH header to be policed at 100000 kbps:
Router> enableRouter# test platform police set 100000Related Commands
test platform police ipv6 disable
To disable the IPv6 internal policer, use the test platform police ipv6 disable command in privileged EXEC mode.
test platform police ipv6 disable
Syntax Description
This command has no arguments or keywords.
Command Default
0 (No rate has been applied)
Command Modes
Privileged EXEC (#)
Command History
15.1(3)S1
The command was introduced on the Cisco 7600 series routers for the ES+ line cards, the SIP-400, and the 7600-ES+ITU-2TG and 7600-ES+ITU-4TG.
Usage Guidelines
Use this command under the exec command of the line card console. It is not visible from the route processor (RP) console.
Examples
This example shows how to disable the IPv6 internal police rate:
Router (config)# test platform police ipv6 disableRelated Commands
test platform police ipv6 set
Sets the IPv6 internal police rate.
test platform police ipv6 get
Gets the IPv6 internal police rate.
test satellite satellite mfg link
To force the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT) to show that the backbone link to the hub is up, even when the link is actually down, use the test satellite satellite mfg link command in privileged EXEC mode.
test satellite satellite slot/unit mfg link {force | normal}
Syntax Description
Defaults
The actual status (UP or DOWN) of the satellite link is displayed.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test satellite satellite mfg link command only when instructed by your satellite service provider or a technical support representative.
Examples
The following example shows how to force the NM-1VSAT-GILAT network module to show that the backbone link to the hub is up, even if the link is actually down:
Router# test satellite satellite 1/0 mfg link forceThe following example shows how to allow the NM-1VSAT-GILAT network module to show the actual status (UP or DOWN) of the satellite link:
Router# test satellite satellite 1/0 mfg link normaltest satellite satellite reset
To reset the Cisco IP VSAT satellite WAN network module (NM-1VSAT-GILAT), use the test satellite satellite reset command in privileged EXEC mode.
test satellite satellite slot/unit reset [hard]
Syntax Description
slot
Router chassis slot in which the network module is installed.
unit
Interface number. For NM-1VSAT-GILAT network modules, always use 0.
hard
Hardware reset. Not available on all routers.
Defaults
Without the hard keyword, the command initiates a software reset.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
Use the test satellite satellite reset command only when instructed by your satellite service provider or a technical support representative. You will lose satellite network connectivity while the NM-1VSAT-GILAT network module resets.
We recommend that you first try a software reset. The hardware reset option is not available on all routers.
Examples
The following example shows how to initiate a software reset of the NM-1VSAT-GILAT network module:
Router# test satellite satellite 1/0 resetThe following example shows how to initiate a hardware reset of the NM-1VSAT-GILAT network module:
Router# test satellite satellite 1/0 reset hardtest service-module
To perform self-tests on an integrated CSU/DSU serial interface module, such as a 4-wire, 56/64 kbps CSU/DSU, use the test service-module command in privileged EXEC mode.
test service-module interface-type interface-number
Syntax Description
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The following tests are performed on the CSU/DSU:
•
•
•
•
•
These self-tests are also performed at power on.
This command cannot be used if a DTE loopback, line loopback, or remote loopback is in progress.
Data transmission is interrupted for 5 seconds when you issue this command. To view the output of the most recent self-tests, use the show service-module command.
This command does not have a no form.
Examples
The following example shows how to perform a self-test on serial interface 0:
Router# test service-module serial 0SERVICE_MODULE(0): Performing service-module self testSERVICE_MODULE(0): self test finished: PassedRelated Commands
test trunk
To configure the test port on a trunk card, use the test trunk command in privileged EXEC mode.
test trunk stm1 {drop | monitor} {tx | rx} {on | off} e1 controller
Syntax Description
Defaults
The test port is disabled.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If a controller does not go up, or there are a large number of errors associated with a specific E1 controller, you might be able to determine whether the problem is in the server card or in an external line by using the test port. The test port is located on the front panel of the SDH/STM-1 trunk card.
This command does not have a no form because the command itself switches the test port on or off.
To use this command, one E1 controller is selected and the transmit and receive lines can be put into drop or monitor mode. Both drop and monitor modes can be used at the same time on either the transmit or receive lines, but both transmit and receive lines cannot be used in drop or monitor mode at the same time.
Examples
The following example shows how to configure a test port to use drop mode on the receive line of an E1 controller in the second path of an STM-1 trunk card in slot 2 of a Cisco AS5850 chassis:
Router# test trunk stm-1 drop rx on E1 2/0.2/1/2timeslot
To enable framed mode on a serial interface on a G.703 E1 port adapter, an FSIP, or an E1-G.703/G.704 serial port adapter, use the timeslot command in interface configuration mode. To restore the interface to unframed mode, use the no form of this command or set the start slot to 0.
timeslot start-slot stop-slot
no timeslot
Syntax Description
Defaults
The default G.703 E1 interface is not configured for framed mode.
Command Modes
Interface configuration
Command History
Usage Guidelines
Framed mode allows you to specify a bandwidth for the interface by designating some of the 32 time slots for data and reserving the others for framing (timing). Unframed mode, also known as clear channel, does not reserve any time slots for framing.
This command applies to Cisco 4000, 7000, 7200, and 7500 series routers. G.703 E1 interfaces have two modes of operation, framed and unframed. When in framed mode, the range from start-slot to stop-slot gives the number of 64-kbps slots in use. There are thirty-two 64-kbps slots available.
In framed mode, timeslot 16 is not used for data. To use timeslot 16 for data, use the ts16 interface configuration command.
Examples
The following example shows how to enable framed mode on a serial interface on a G.703 E1 port adapter or an E1-G.703/G.704 port adapter:
Router(config)# interface serial 3/0Router(config-if)# timeslot 1-3Related Commands
Controls the use of timeslot 16 for data on a G.703 E1 interface or on an E1-G703/G.704 serial port adapter.
tod
To configure the time of day message format used by the 1PPS interface use the tod command in global configuration mode. To remove a time of day configuration, use the no form of this command.
tod slot/bay {iso8601 | ubx | nmea | cisco | ntp} [delay delay-amount]
no tod slot/bay {iso8601 | ubx | nmea | cisco | ntp} [delay delay-amount]
Syntax Description
Command Default
No default behavior or values.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
This command applies only to platforms that have 1PPS ports.
Examples
The following example shows how to configure a PTP announcement interval:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config)# tod 3/0 ntpRouter(config)# exitRelated Commands
transceiver type all
To enter in to transceiver type configuration mode (which in turn facilitates you to enable the monitoring of all transceivers), use the transceiver type all command in global configuration mode. This command does not have the no form.
transceiver type all
Syntax Description
This command has no arguments or keywords.
Command Default
Transceiver type configuration is disabled.
Command Modes
Global configuration (config)
Command History
Usage Guidelines
You can enter the transceiver type configuration mode using the transceiver type all command. You can then monitor the transceiver types and also set the monitoring interval using the monitoring command.
Examples
This example shows how to enter in to transceiver type configuration mode and then enable the monitoring for all transceiver types:
Router(config)# transceiver type allRouter(config-xcvr-type)# monitoring interval 500Related Commands
transmit-buffers backing-store
To buffer short-term traffic bursts that exceed the bandwidth of the output interface, use the transmit-buffers backing-store command in interface configuration mode. To disable this function, use the no form of this command.
transmit-buffers backing-store
no transmit-buffers backing-store
Syntax Description
This command has no arguments or keywords.
Defaults
The default is off, unless weighted fair queueing is enabled on the interface. If weighted fair queueing is enabled on the interface, the transmit-buffers backing-store command is enabled by default.
Command Modes
Interface configuration
Command History
Usage Guidelines
If the transmit-buffers backing-store command is enabled and a full hardware transmit queue is encountered, packets are swapped out of the original memory device (MEMD) into a system buffer in DRAM. If the transmit-buffers backing-store command is not enabled and the output hold queue is full, packets are dropped instead of being copied if a full hardware transmit queue is encountered. In both cases, the original MEMD buffer is freed so that it can be reused for other input packets.
To preserve packet order, the router checks the output hold queue and outputs previously queued packets first.
Examples
The following example shows how to enable the transmit-buffers backing-store command on a FDDI interface:
Router(config)# interface fddi 3/0Router(config-if)# transmit-buffers backing-storeRelated Commands
transmit-clock-internal
To enable the internally generated clock on a serial interface on a Cisco 7200 series or Cisco 7500 series router when a DTE does not return a transmit clock, use the transmit-clock-internal command in interface configuration mode. To disable the internally generated clock, use the no form of this command.
transmit-clock-internal
no transmit-clock-internal
Syntax Description
This command has no arguments or keywords.
Defaults
The internally generated clock is disabled.
Command Modes
Interface configuration
Command History
Examples
The following example shows how to enable the internally generated clock on serial interface 3/0 on a Cisco 7200 series or Cisco 7500 series router:
Router(config)# interface serial 3/0Router(config-if)# transmit-clock-internaltransmit-interface
To assign a transmit interface to a receive-only interface, use the transmit-interface command in interface configuration mode. To return to normal duplex Ethernet interfaces, use the no form of this command.
transmit-interface type number
no transmit-interface
Syntax Description
type
Transmit interface type to be linked with the (current) receive-only interface.
number
Transmit interface number to be linked with the (current) receive-only interface.
Defaults
Disabled
Command Modes
Interface configuration
Command History
Usage Guidelines
Receive-only interfaces are used commonly with microwave Ethernet links.
Examples
The following example specifies Ethernet interface 0 as a simplex Ethernet interface:
interface ethernet 1ip address 128.9.1.2transmit-interface ethernet 0transmitter-delay
To specify a minimum dead-time after transmitting a packet, use the transmitter-delay command in interface configuration mode. To restore the default, use the no form of this command.
transmitter-delay delay
no transmitter-delay
Syntax Description
Defaults
0 flags or microseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
This command is especially useful for serial interfaces that can send back-to-back data packets over serial interfaces faster than some hosts can receive them.
The transmitter delay feature is implemented for the following Token Ring cards: CSC-R16, CSC-R16M, CSC-1R, CSC-2R, and CSC-CTR. For the first four cards, the command syntax is the same as the existing command and specifies the number of microseconds to delay between sending frames that are generated by the router. Transmitter delay for the CSC-CTR uses the same syntax, but specifies a relative time interval to delay between transmission of all frames.
Examples
The following example shows how to specify a delay of 300 microseconds on serial interface 0:
Router(config)# interface serial 0Router(config-if)# transmitter-delay 300transport-mode
To configure a transport mode, use the transport-mode command in interface configuration mode. To return to the default state, use the no form of this command.
transport-mode {lan | wan | otn bit-transparent {opu1e | opu2e}}
no transport-mode {lan | wan | otn bit-transparent {opu1e | opu2e}}
Syntax Description
Command Default
LAN
Command Modes
Interface configuration (config-if)
Command History
Examples
The following example shows how to configure a LAN transport mode:
Router(config-if)# transport-mode lanRelated Commands
transport ipv4
To specify IPv4 transport source mode and the transport source interface, use the transport ipv4 command in L3 VPN encapsulation configuration mode. To remove the transport source, use the no form of this command.
transport ipv4 [source interface-type interface-number]
no transport [ipv4]
Syntax Description
source
Specifies the IPv4 transport source.
interface-type
(Optional) The source interface type.
interface-number
(Optional) The source interface number.
Command Default
The IPV4 transport source mode and interface are not defined.
Command Modes
L3VPN Encapsulation Configuration (config-l3vpn-encap-ip)
Command History
Usage Guidelines
The transport ipv4 command specifies IPv4 transport source mode and defines the transport source interface while configuring the L3VPN encapsulation profile. When you use this command, make sure that the specified source address is used as the nexthop in BGP updates advertised by the PE.
Examples
The following example shows how to specify IPv4 transport source mode and the transport source interface:
Router(config-l3vpn-encap-ip)# transport ipv4 source loopback 0Related Commands
transport ipv4 (PTP)
To specify the IP version, transmission mode, and interface that a Precision Time Protocol clock port uses to exchange timing packets, use the transport ipv4 command in PTP clock port configuration mode. To remove a transport configuration, use the no form of this command.
transport ipv4 {unicast | multicast | multicast-mix} interface interface-type interface-number [negotiation]
no transport ipv4 {unicast | multicast | multicast-mix} interface interface-type interface-number [negotiation]
Syntax Description
Command Default
The IP version, transmission mode, and interface are not specified for exchanging timing packets.
Command Modes
PTP clock port configuration (config-ptp-port)
Command History
Usage Guidelines
You can configure different transport values for each PTP clock port.
Examples
The following example shows how to use the transport ipv4 command:
Router# configure terminalRouter(config)# ptp clock ordinary domain 0Router(config-ptp-clk)# clock-port masterport masterRouter(config-ptp-port)# transport ipv4 unicast interface top5/2/2Router(config-ptp-port)# endRelated Commands
ts16
To control the use of time slot 16 for data on a G.703 E1 interface or on an E1-G.703/G.704 serial port adapter, use the ts16 command in interface configuration mode. To restore the default, use the no form of this command.
ts16
no ts16
Syntax Description
This command has no arguments or keywords.
Defaults
Time slot 16 is used for signaling.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command applies to Cisco 4000, 7000, 7200, and 7500 series routers. By default, time slot 16 is used for signaling. Use this command to configure time slot 16 to be used for data. When in framed mode, in order to get all possible subframes or time slots, you must use the ts16 command.
Examples
The following example shows how to configure time slot 16 to be used for data on a G.703 E1 interface or an E1-G.703/G.704 serial port adapter:
Router(config-if)# ts16Related Commands
Enables framed mode serial interface on a G.703 E1 port adapter, an FSIP, or an E1-G.703/G.704 serial port adapter.
ttb
To send a trace trail buffer in E3 g832 framing mode, use the ttb command in interface configuration mode. To disable the trace, use the no form of this command.
ttb {country | rnode | serial | snode | soperator | x} line
no ttb {country | rnode | serial | snode | soperator | x} line
Syntax Description
country line
Two-character country code.
rnode line
Receive node code.
serial line
M.1400 Serial
snode line
Sending Town/Node ID code.
soperator line
Sending Operator code.
x line
XO
Defaults
No default behavior or values
Command Modes
Interface configuration
Command History
Usage Guidelines
Use the ttb command to attach a header that contains fields to send to a remote device.
Examples
The following example starts a TTB message on the first port on slot 5.
Router# configure terminalRouter(config)# int serial 5/0/0Router(config-if)# ttb country usRouter(config-if)# ttb snode 123Router(config-if)# ttb rnode rnRouter(config-if)# ttb x 9Router(config-if)# ttb serial 432Related Commands
tug-2 e1
To create E1 controllers for a specified path under the Tributary Unit group type 2 (TUG-2), use the tug-2 e1 command in controller configuration mode.
tug-2 tug-2-number e1 e1-number
Syntax Description
Defaults
Default tug-2-number value for STM-1 card is 1.
Command Modes
Controller configuration
Command History
12.0(14)S
This command was introduced.
12.2(15)T
This command was integrated into Cisco IOS Release 12.2(15)T.
Usage Guidelines
Use the tug-2 e1 command to create an E1 controller with the following name format:
slot/port.path/tug-2-number/e1-number
Up to 21 controllers can be created for one path. Only one path can be selected at a time.
Examples
The following example shows how to configure 15 E1 controllers on the second path of an STM-1 in physical slot number 2 of a Cisco AS5850 chassis:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-4Router(config-ctrlr-tug3)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 5 e1 3Related Commands
tug-2 e1 bert pattern
To send a BER test pattern on an E1 line that has been mapped to a TUG-3, use the tug-2 e1 bert pattern command in configuration controller tug3 mode.
To send a BER test pattern on an E1 line that has been mapped to an AU-3, use the tug-2 e1 bert pattern command in configuration controller au3 mode.
To stop the BER test, use the no form of this command.
tug-2 tug-2 number e1 e1-number [bert pattern pattern interval time]
[no] tug-2 tug-2 number e1 e1-number [bert pattern pattern interval time]
Syntax Description
Defaults
No BER test is configured.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
Use the tug-2 e1 bert pattern command in configuration controller tug3 command mode to send a BERT test on an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 bert pattern command in configuration controller au3 command mode to send a BERT test on an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
To view the test results of a BER test pattern, use the show controller sonet command.
Examples
The following example sends a BER 2^11 pseudorandom pattern through E1 line 1, that has been mapped to a TUG-3 on a Cisco 7500 series router, for five minutes:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 bert pattern 2^11 interval 5The following example sends a BER 2^15 pseudorandom pattern through E1 line 1, that has been mapped to an AU-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch, for ten minutes:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 bert pattern 2^15 interval 10Related Commands
tug-2 e1 channel-group timeslots
To create a logical channel group on an E1 line that has been mapped to a TUG-3 or AU-3, use the tug-2 e1 channel-group timeslots command in the appropriate configuration mode. To remove a logical channel group, use no the form of this command.
tug-2 tug-2-number e1 e1-number [[channel-group channel-group-number] [timeslots list-of-timeslots]]
no tug-2 tug-2-number e1 e1-number [[channel-group channel-group-number] [timeslots list-of-timeslots]]
Syntax Description
Defaults
No channel groups are configured on an E1 line.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
This command is supported on the C 10000 router. It is used with the Cisco channelized STM-1 card. Use the tug-2 e1 channel-group timeslots command in configuration controller tug3 command mode to configure a logical channel group on an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 channel-group timeslots command in configuration controller au3 command mode to configure a logical channel group on an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example configures logical channel group 15 on E1 1, that is mapped to a TUG-3, and assigns channelized time slots 1 to 5 and 20 to 23 on a Cisco 7500 series router:
Router(config)# controller sonet 2/0/0Router(config-controller)# framing sdhRouter(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 channel group 15 timeslots 1-5, 20-23The following example configures logical channel group 10 on E1 1, that is mapped to an AU-3, and assigns channelized time slots 1 to 5 and 20 to 23 on a Cisco 7200 VXR router or a Catalyst 6000 family switch:
Router(config)# controller sonet 2/0Router(config-controller)# framing sdhRouter(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 channel group 10 timeslots 1-5, 20-23Related Commands
tug-2 e1 clock source
To set the clock source on an E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 clock source command in the appropriate configuration mode.
tug-2 tug-2-number e1 e1-number clock source {internal | line}
Syntax Description
tug-2-number
A number in the range of 1 to 7.
e1-number
A number in the range of 1 to 3.
internal
Specifies the PA-MC-STM-1 as the clock source.
line
Specifies the E1 line as the clock source.
Defaults
Clock source is configured from the E1 line.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
Use the tug-2 e1 clock source command in configuration controller tug3 command mode to configure the clock source of an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 clock source command in configuration controller au3 command mode to configure the clock source of an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example configures E1 line 1, that has been mapped to an AU-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch, to be the clock source:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 clock source lineThe following example configures E1 line 1, that has been mapped to a TUG-3 on a Cisco 7500 series router to use the PA-MC-STM-1, as the clock source:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 clock source internalRelated Commands
tug-2 e1 framing
To set the type of framing used by an E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 framing command in appropriate configuration mode. To disable the framing mode, user the no form of this command.
tug-2 tug-2-number e1 e1-number framing {crc4 | no-crc4}
no tug-2 tug-2-number e1 e1-number framing {crc4 | no-crc4}
Syntax Description
tug-2-number
A number in the range of 1 to 7.
e1-number
A number in the range of 1 to 3.
crc4
Specifies 4-bit cyclic redundancy check framing.
no-crc4
Specifies basic framing.
Defaults
Framing format is crc4.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
Use the tug-2 e1 framing command in configuration controller tug3 command mode to configure the type of framing used by an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 framing command in configuration controller au3 command mode to configure the type of framing used by an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example configures E1 line 1, that has been mapped to a TUG-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch, to use crc4 framing:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 framing crc4The following example configures E1 line 1, that has been mapped to an AU-3 on a Cisco 7500 series router, to use basic framing:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 framing no-crc4Related Commands
tug-2 e1 loopback
To specify a loopback on an E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 loopback command in appropriate configuration mode. To disable the loopback, use the no form of this command.
tug-2 tug-2-number e1 e1-number loopback {local | network {line | payload}}
[no] tug-2 tug-2-number e1 e1-number loopback {local | network {line | payload}}
Syntax Description
Defaults
No loopbacks are set on an E1 line.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3Command History
Usage Guidelines
Use the tug-2 e1 loopback command in configuration controller tug3 command mode to specify a loopback for an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 loopback command in configuration controller au3 command mode to specify a loopback for an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example sets E1 line 1, that has been mapped to an AU-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch, into network line loopback:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 loopback network lineThe following example sets E1 line 1, that has been mapped to a TUG-3 on a Cisco 7500 series router, into local loopback:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 loopback localRelated Commands
tug-2 e1 national bits
To set the national reserved bits on an E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 national bits command in appropriate configuration mode.
tug-2 tug-2-number e1 e1-number national bits pattern
Syntax Description
Defaults
0x1F
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
Use the tug-2 e1 national bits command in configuration controller tug3 command mode to configure the national reserved bits for an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 national bits command in configuration controller au3 command mode to configure the national reserved bits for an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example configures the national reserved bits for E1 line 1, that has been mapped to a TUG-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch, into a 0x0 hexadecimal pattern:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 national bits 0x0The following example configures the national reserved bits for E1 line 1, that has been mapped to an AU-3 on a Cisco 7500 series router, into decimal pattern 0:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 national bits 0Related Commands
tug-2 e1 shutdown
To shut down an individual E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 shutdown command in appropriate configuration mode. To enable an individual E1 line, use the no form of this command.
tug-2 tug-2-number e1 e1-number shutdown
[no] tug-2 tug-2 number e1 e1-number shutdown
Syntax Description
Defaults
E1 lines are not shut down.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3Command History
Usage Guidelines
Use the tug-2 e1 shutdown command in configuration controller tug3 command mode to shut down an individual E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 shutdown command in configuration controller au3 command mode to shut down an individual E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
Examples
The following example shuts down E1 line 1 that has been mapped to an AU-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 shutdownThe following example shuts down E1 line 1, that has been mapped to a TUG-3 on a Cisco 7500 series router:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 shutdownRelated Commands
tug-2 e1 unframed
To create an E1 unframed (clear channel) logical channel group on an E1 line that has been mapped to a TUG-3 or an AU-3, use the tug-2 e1 unframed command in appropriate configuration mode. To remove a logical channel group, use the no form of this command.
tug-2 tug-2-number e1 e1-number unframed
[no] tug-2 tug-2-number e1 e1-number unframed
Syntax Description
Defaults
No default behavior or values.
Command Modes
Configuration controller tug3 (for an E1 line mapped to a TUG-3)
Configuration controller au3 (for an E1 line mapped to an AU-3)Command History
Usage Guidelines
Use the tug-2 e1 unframed command in configuration controller tug3 command mode to create an unframed (clear channel) logical channel group on an E1 line that has been mapped to a TUG-3 via the aug mapping au-4 command.
Use the tug-2 e1 unframed command in configuration controller au3 command mode to create an unframed (clear channel) logical channel group on an E1 line that has been mapped to an AU-3 via the aug mapping au-3 command.
The channel group number for unframed E1 lines is always 0.
Examples
The following example configures an unframed logical channel group on E1 line 1 that has been mapped to a TUG-3 on a Cisco 7200 VXR router or a Catalyst 6000 family switch:
Router(config)# controller sonet 2/0Router(config-controller)# aug mapping au-4Router(config-controller)# au-4 1 tug-3 2Router(config-ctrlr-tug3)# tug-2 4 e1 1 unframedThe following example configures an unframed logical channel group on E1 line 1 that has been mapped to an AU-3 on a Cisco 7500 series router:
Router(config)# controller sonet 2/0/0Router(config-controller)# aug mapping au-3Router(config-controller)# au-3 1Router(config-ctrlr-au3)# tug-2 4 e1 1 unframedRelated Commands
