|
|
You can now perform the following new tasks on the Channelized T3 Interface Processor (CT3IP) available on Cisco 7500 series routers, and on Cisco 7000 series routers with the 7000 Series Route Switch Processor (RSP7000) and 7000 Series Chassis Interface (RSP7000CI). You can also perform these tasks on the Channelized T3 dual-wide port adapter (PA-CT3/4T1), which can be used in Cisco 7200 series routers:
This feature is supported on these platforms:
The following sections describe the new, optional configuration tasks for the CT3IP.
The CT3IP can be configured to send a Maintenance Data Link (MDL) message as defined in the ANSI T1.107a-1990 specification. To specify the transmission of the MDL messages, complete the following tasks beginning in global configuration mode:
Use the show controllers t3 command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.
The CT3IP supports performance reports via the Facility Data Link (FDL) per ANSI T1.403. By default, performance reports are disabled. To enable FDL performance reports, complete the following tasks beginning in global configuration mode:
To display the remote performance report information, complete the following task in EXEC command mode:
To enable and disable generation of a bit error rate testing (BERT) test pattern for a specified interval for a specific T1 channel, complete the following tasks beginning in global configuration mode:
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 command. The BERT results include the following information:
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 pattern command is not written to NVRAM because it is only used for testing the T1 channel for a short predefined interval and to avoid accidentally saving the command, which could cause the interface not to come up the next time the router reboots.
You can perform the following types of remote Facility Data Link (FDL) loopbacks on a T1 channel:
To enable loopbacks on a T1 channel, complete the first task beginning in global configuration mode followed by Step 2 or Step 3 depending on the type of loopback you want to perform:
| Task | Command |
|---|---|
| Step 1 Select the T1 channel (values are 1 to 28) on the CT3IP and enter interface configuration mode. | interface serial slot/port-adapter/port:t1-channel (Cisco 7500 series and Cisco 7000 series routers with the RSP7000 and RSP7000CI) interface serial slot/port:t1-channel (Cisco 7200 series) |
| Step 2 Enable the remote payload FDL ANSI bit loopback on the T1 channel. | loopback remote payload [fdl] [ansi] |
| Step 3 Enable the remote line FDL ANSI bit loopback or remote SmartJack loopback on the T1 channel. | loopback remote line fdl {ansi | bellcore} |
The following examples show several of the Maintenance Data Link (MDL) messages for the CT3IP in slot 9:
Router(config)#controller t3 9/0/0Router(config-controller)#mdl string eic Router CRouter(config-controller)#mdl string lic Network ARouter(config-controller)#mdl string fic Bldg 102Router(config-controller)#mdl string unit 123ABCRouter(config-controller)#exitRouter(config)#
In the following example, the performance reports are generated for T1 channel 6 on the CT3IP in slot 9:
Router(config)#controller t3 9/0/0Router(config-controller)#t1 6 fdl ansiRouter(config-controller)#exit
The following example shows how to enable a BERT test pattern that consists of a repeating pattern of ones (...111...) and runs for 30 minutes for T1 channel 8 on CT3IP in slot 9:
Router(config)#controller t3 9/0/0Router(config-controller)#t1 8 bert pattern 1s interval 30Router(config-controller)#exit
The following example shows how to enable a remote payload FDL ANSI bit loopback for T1 channel 6 on CT3IP in slot 3:
Router(config)#interface serial 3/0/0:6Router(config-if)#loopback remote payload fdl ansiRouter(config-if)#exit
This section documents new and modified commands. All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references.
To loop individual T1 channels on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers, use the loopback interface configuration command. Use the no form of this command to remove the loopback.
loopback [local | network {line | payload} | remote {line {fdl {ansi | bellcore} | inband} || local | (Optional) Loops the router output data back toward the router at the T1 framer and sends an AIS signal out toward the network. |
| network {line | payload} | (Optional) Loops the data back toward the network before the T1 framer and automatically sets a local loopback at the HDLC controllers (line) or loops the payload data back toward the network at the T1 framer and automatically sets a local loopback at the HDLC controllers (payload). |
| remote line fdl {ansi | bellcore} | (Optional) Sends a repeating, 16-bit ESF data link code word (00001110 11111111) to the remote end requesting that it enter into a network line loopback. Specify the ansi keyword to enable the remote line Facility Data Link (FDL) ANSI bit loopback on the T1 channel, per the ANSI T1.403 Specification. Specify the bellcore keyword to enable the remote SmartJack loopback on the T1 channel, per the TR-TSY-000312 Specification. |
| remote line inband | (Optional) Sends a repeating, 5-bit inband pattern (00001) to the remote end requesting that it enter into a network line loopback. |
| remote payload [fdl] [ansi] | (Optional) Sends a repeating, 16-bit ESF data link code word (00010100 11111111) to the remote end requesting that it enter into a network payload loopback. Enables the remote payload Facility Data Link (FDL) ANSI bit loopback on the T1 channel.
You can optionally specify fdl and ansi, but it is not necessary. |
Disabled
Interface configuration
This command first appeared in Cisco IOS Release 11.1 CA.
Use this command for troubleshooting purposes.
To better diagnose T1 provisioning problems, you can place the the remote CSU or remote SmartJack into loopback. The loopback remote line fdl interface configuration command allows you to place either the CSU or the SmartJack into loopback:
When both are configured, transmission of LOF indication (yellow alarm) takes priority over transmission of some FDL messages.
If the remote loopback appears not to be working, use the show cont t3 command to determine if the given T1 is currently attempting to transmit a LOF indication (yellow alarm):
Router#show controllers t3 0/0/0:2T3 0/0/0 is up.CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9Mx H/W version: 2, Mx ucode ver: 1.34T1 2 is down, speed: 1536 kbs, non-inverted datatimeslots: 1-24FDL per AT&T 54016 spec.Transmitter is sending LOF Indication.Receiver is getting AIS.
If the transmitter is sending a LOF indication, as in the previous example, stop the transmission of the LOF indication (yellow alarm) with the no t1 yellow generation configuration command as shown in the following example:
Router(config)#controllers t3 0/0/0Router(config-controll)#no t1 2 yellow generationRouter(config-controll)#^D
To verify that the transmission of the LOF indication (yellow alarm) has stopped, use the show cont t3 command:
Router# show cont t3 0/0/0:2
T3 0/0/0 is up.
CT3 H/W Version: 5, CT3 ROM Version: 1.2, CT3 F/W Version: 2.5.9
Mx H/W version: 2, Mx ucode ver: 1.34
T1 2 is down, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per AT&T 54016 spec.
Receiver is getting AIS.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
Yellow Alarm Generation is disabled
Now retry the remote loopback command. When diagnosis is complete, remember to re-enable the LOF indication (yellow alarm).
You can also loopback all the T1 channels by using the loopback (CT3IP) interface configuration command.
The following example configures T1 channel 5 for a local loopback:
interface serial 3/0/0:5 loopback local
loopback (T3)
To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification for the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers, use the mdl interface configuration command. Use the no form of this command to remove the message.
mdl {transmit {path | idle-signal | test-signal} | string {eic | lic | fic | unit | pfi | port || transmit path | Enables transmission of the MDL Path message. |
| transmit idle-signal | Enables transmission of the MDL Idle Signal message. |
| transmit test-signal | Enables transmission of the MDL Test Signal message. |
| string eic string | Specifies the Equipment Identification Code; can be up to 10 characters. |
| string lic string | Specifies the Location Identification Code; can be up to 11 characters. |
| string fic string | Specifies the Frame Identification Code; can be up to 10 characters. |
| string unit string | Specifies the Unit Identification Code; can be up to 6 characters. |
| string pfi string | Specifies the Facility Identification Code sent in the MDL Path message; can be up to 38 characters. |
| string port string | Specifies the Port number string sent in the MDL Idle Signal message; can be up to 38 characters. |
| string generator string | Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters. |
No MDL message is configured
Controller configuration
This command first appeared in Cisco IOS Release 11.1 CA.
Use the show controllers t3 command to display MDL information (received strings). MDL information is displayed only when framing is set to C-bit.
The following examples show several of the mdl commands for the CT3IP in slot 9:
controller t3 9/0/0 mdl string eic Router A mdl string lic Test Network mdl string fic Building B mdl string unit ABC
To display information about the Channelized T3 Interface Processor (CT3IP) on Cisco 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers or to display information about the PA-CT3/4T1 in Cisco 7200 series routers, use the show controller t3 privileged EXEC command.
show controller t3 [slot/port-adapter/port [:t1-channel]] [remote performance [brief || slot | (Optional) Backplane slot number. The value varies depending on the platform. |
| port-adapter | (Optional) The port adapter and port numbers for the CT3IP are 0. |
| port | (Optional) The port adapter and port numbers for the CT3IP are 0. |
| :t1-channel | (Optional) For the CT3IP, the T1 channel is a number between 1 and 28. |
| remote performance | (Optional) Displays the far-end ANSI performance monitor information when enabled on the T1 channel with the t1 fdl ansi controller command. |
| brief | (Optional) Displays a subset of information. |
| tabular | (Optional) Displays information in a tabular format. |
Privileged EXEC
This command was modified in Cisco IOS Release 11.1 CA to include the remote performance keyword.
This command displays controller status that is specific to the controller hardware. The information displayed is generally useful for diagnostic tasks performed by technical support personnel only.
The show controllers t3 command also displays Maintenance Data Link (MDL) information (received strings) if MDL is configured and framing is set to C-bit.
The following is partial sample output from the show controller t3 command:
Router# show controller t3 3/0/0
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0
Mx H/W version: 2, Mx ucode ver: 1.24
Applique type is Channelized T3
No alarms detected.
FEAC code received: No code is being received
Framing is M23, Line Code is B3ZS, Clock Source is Internal.
Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OK
Data in current interval (39 seconds elapsed):
0 Line Code Violations, 0 P-bit Coding Violation
0 C-bit Coding Violation
0 P-bit Err Secs, 0 P-bit Severely Err Secs
0 Severely Err Framing Secs, 0 Unavailable Secs
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
Total Data (last 1 15 minute intervals):
0 Line Code Violations, 0 P-bit Coding Violation,
0 C-bit Coding Violation,
0 P-bit Err Secs, 0 P-bit Severely Err Secs,
0 Severely Err Framing Secs, 0 Unavailable Secs,
0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs
T1 1 is down, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per ANSI T1.403 and AT&T 54016 spec.
Configured for FDL Remotely Line Looped
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
BERT test result (running)
Test Pattern: All 0's, Status: Sync, Sync Detected: 1
Interval: 4 minute(s), Tim Remain: 4 minute(s)
Bit Errors (Sync BERT Started): 0 bits
Bit Errors (Sync last Sync): 0 bits, Bits Received: 7 Mbits
...
T1 15 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
Data in current interval (69 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
Total Data (last 1 15 minute intervals):
0 Line Code Violations, 0 Path Code Violations,
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs, 0 Stuffed Secs
The following is partial sample output from the show controller t3 brief command:
router# show controllers t3 3/0/0 brief
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 0.10.0
Mxt H/W version: 2, Mxt ucode ver: 1.24
Applique type is Channelized T3
No alarms detected.
FEAC code received: No code is being received
Framing is M23, Line Code is B3ZS, Clock Source is Internal.
Ext1: LOS, Ext2: LOS, Ext3: LOS, Test: OK
T1 1 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per ANSI T1.403 and AT&T 54016 spec.
Configured for FDL Remotely Line Looped
No alarms detected.
Framing is ESF, LineCode is B8ZS, Clock Source is Internal.
BERT test result (done)
Test Pattern: All 0's, Status: Not Sync, Sync Detected: 1
Interval: 4 minute(s), Tim Remain: 0 minute(s)
Bit Errors(Sync BERT Started): 0 bits
Bit Errors(Sync last Sync): 0 bits, Bits Received: 368 Mbits
...
The following is partial sample output from the show controllers t3 tabular command:
router# show controllers t3 3/0/0 tabular
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 1.2, CT3 F/W Version: 2.1.0
Mx H/W version: 2, Mx ucode ver: 1.25
Applique type is Channelized T3
No alarms detected.
MDL transmission is disabled
FEAC code received: No code is being received
Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Internal.
Ext1: AIS, Ext2: LOS, Ext3: LOS, Test: LOS
INTERVAL LCV PCV CCV PES PSES SEFS UAS LES CES CSES
08:56-09:11 0 0 0 0 0 0 0 0 0 0
08:41-08:56 0 0 0 0 0 0 0 0 0 0
08:26-08:41 0 0 0 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0 0 0 0
T1 2 is up, speed: 1536 kbs, non-inverted data
timeslots: 1-24
FDL per AT&T 54016 spec.
No alarms detected.
Framing is ESF, Line Code is B8ZS, Clock Source is Internal.
INTERVAL LCV PCV CSS SELS LES DM ES BES SES UAS SS
08:56-09:11 0 0 0 0 0 0 0 0 0 0 0
08:41-08:56 0 0 0 0 0 0 0 0 0 0 0
08:26-08:41 0 0 0 0 0 0 0 0 0 0 0
Total 0 0 0 0 0 0 0 0 0 0 0
The following is partial sample output from the show controller t3 remote performance command. This information is available if the t1 fdl ansi controller command is enabled for a T1 channel on a CT3IP.
Router# show controller t3 3/0/0 remote performance
T3 3/0/0 is up.
CT3 H/W Version: 4, CT3 ROM Version: 0.116, CT3 F/W Version: 20.2.0
Mx H/W version: 2, Mx ucode ver: 1.25
T1 1 - Remote Performance Data
Data in current interval (356 seconds elapsed):
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Data in Interval 1:
1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Data in Interval 2:
0 Line Code Violations, 0 Path Code Violations
0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins
0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
Total Data (last 2 15 minute intervals):
1 Path Code Violations
1 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,
2 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs
0 Unavail Secs
...
Table 49 describes the show controller t3 display fields.
| Field | Description |
|---|---|
| T3 3/0/0 is up | T3 controller in slot 3 is operating. The controller's state can be up, down, administratively down. Loopback conditions are shown by (Locally looped) or (Remotely Looped). |
| CT3 H/W Version | Version number of the hardware. |
| CT3 ROM Version | Version number of the ROM. |
| CT3 F/W Version | Version number of the firmware. |
| Mx HW version | Hardware version number of the HDLC controller chip. |
| Mx ucode ver | Microcode version of the HDLC controller chip. |
| Applique type | Controller type. |
| No alarms detected | Any alarms detected by the controller are displayed here. Possible alarms are as follows:
|
|
MDL transmission is disabled | Status of the maintenance data link (either enabled or disabled). |
| FEAC code received | Whether or not a far-end alarm code request is being received. Possible values are as follows:
|
|
Framing is M23 | Framing type on the CT3IP. Values are: M23, C-Bit, and Auto-detect. |
| Line Code is B3ZS | Line coding format on the CT3IP. |
| Clock Source is Internal | Clock source on the CT3IP. Values are: internal or line. |
| BERT test result | BERT test information is available if the t1 bert controller command is enabled for the T1 channel on the CT3IP. The BERT results include the following information:
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. |
| Data in current interval (39 seconds elapsed) | Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. Accumulation period is from 1 to 900 seconds. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer. |
| Line Code Violations | Line Code Violations (LCV) is a count of both Bipolar Violations (BPVs) and Excessive Zeros (EXZs) occurring over the accumulation period. An EXZ increments the LCV by one regardless of the length of the zero string. |
| P-bit Coding Violation | For all DS3 applications, a P-bit coding violation (PVC) error event is a P-bit parity error event. A P-bit parity error event is the occurrence of a received P-bit code on the DS3 M-frame that is not identical to the corresponding locally calculated code. |
| C-bit Coding Violation | For C-bit parity and SYNTRAN DS3 applications, the C-bit coding violation (CCV) is the count of coding violations reported via the C-bits. For C-bit parity, it is the count of CP-bit parity errors occurring in the accumulation interval. For SYNTRAN, it is a count of CRC-9 errors occurring in the accumulation interval. |
| P-bit Err Secs | P-bit errored seconds (PES) is a second with one or more PCVs, one or more out of frame defects, or a detected incoming AIS. This gauge is not incremented when unavailable seconds are counted. |
| P-bit Severely Err Secs | P-bit severely errored seconds (PSES) is a second with 44 or more PCVs, one or more out of frame defects, or a detected incoming AIS. This gauge is not incremented when unavailable seconds are counted. |
| Severely Err Framing Secs | Severely errored framing seconds (SEFS) is a second with one or more out of frame defects or a detected incoming AIS. |
| Unavailable Secs | Unavailable seconds (UAS) are calculated by counting the number of seconds that the interface is unavailable. For more information, refer to RFC 1407. |
| Line Err Secs | Line errored seconds (LES) is a second in which one or more code violations occurred or one or more LOS defects. |
| C-bit Errored Secs | C-bit errored seconds (CES) is a second with one or more C-bit code violations (CCV), one or more Out of Frame defects, or a detected incoming AIS. This gauge is not incremented when UASs are counted. |
| C-bit Severely Errored Secs | C-bit severely errored seconds (CSES) is a second with 44 or more CCVs, one or more Out of Frame defects, or a detected incoming AIS. This gauge is not incremented when UASs are counted. |
| Total Data (last 1 15 minute intervals) | Shows the last 15-minute accumulation period. |
| T1 1 is up | T1 channel is operating. The channel's state can be up, down, administratively down. Loopback conditions are shown by (Locally looped) or (Remotely looped). |
| speed | Speed of the T1 channel in kbps. |
| non-inverted data | Indicates if the T1 channel is configured for inverted data. |
| timeslots | Timeslots assigned to the T1 channel. |
| FDL per AT&T 54016 spec. | Performance monitoring is via Facility Data Link per ANSI T1.403. |
| No alarms detected | Any alarms detected by the T1 controller are displayed here. Possible alarms are as follows:
|
|
Framing is ESF | Type of framing used on the T1 channel. Values are: ESF or SF. |
| LineCode is B8ZS | Type of line coding used on the T1 channel. Values are: B8ZS or AMI. |
| Clock Source is Internal | Clock source on the T1 channel. Values are: internal or line. |
| Path Code Violations | Path coding violation (PCV) error event is a frame synchronization bit error in the D4 and E1-noCRC formats or a CRC error in the ESF and E1-CRC formats. |
| Slip Secs | Controlled slip second (CSS) is a one-second interval containing one or more controlled slips. |
| Fr Loss Secs | Frame loss seconds (SELS) is the number of seconds an Out Of Frame (OOF) error is detected. |
| Line Err Secs | Line errored seconds (LES) is a second in which one or more line code violation errors are detected. |
| Degraded Mins | Degraded minute (DM) is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3. For more information, refer to RFC 1406. |
| Errored Secs | Errored seconds (ES) is a second with one or more path coding violations, one or more Out of Frame defects, or one or more controlled slip events or a detected AIS defect. |
| Bursty Err Secs | Bursty errored seconds (BES) is a second with fewer than 320 and more than one path coding violation error events, no Severely Errored Frame defects, and no detected incoming AIS defects. Controlled slips are not included in this parameter. |
| Severely Err Secs | Severely errored seconds (SES) is a second with 320 or more path code violation errors events, one or more Out of Frame defects, or a detected AIS defect. |
| Stuffed Secs | Stuffed seconds (SS) is a second in which one more bit stuffings take place. This happens when the Pulse Density Enforcer detects a potential violation in the output stream and inserts a 1 to prevent it. Such bit stuffings corrupt user data and indicate the network is misconfigured. This counter can be used to help diagnose this situation. |
To enable or disable a BERT test pattern for a T1 channel on the Channelized T3 Interface Processor (CT3IP) in Cisco 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers, use the t1 bert controller configuration command. To disabled 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| channel | Number between 1 and 28 that indicates the T1 channel. |
| pattern {0s | 1s | 2^15 | 2^20 | 2^23} | Specifies the length of the repeating BERT test pattern. Values are:
· 0s--Repeating pattern of zeros (...000...). · 1s--Repeating pattern of ones (...111...). · 2^15--Pseudo-random repeating pattern that is 32767 bits in length. · 2^20--Pseudo-random repeating pattern that is 1048575 bits in length. · 2^23--Pseudo-random repeating pattern that is 8388607 bits in length. |
| interval minutes | Specifies the duration of the BERT test. The interval can be a value from 1 to 14400 minutes. |
No BERT test is performed.
Controller configuration
This command first appeared in Cisco IOS Release 11.1 CA.
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 command. The BERT results include the following information:
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 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 to avoid accidentally saving the command, which could cause the interface not to come up the next time the router reboots.
In the following example, a BERT test pattern of all zeros is run for 30 minutes on T1 channel 6 on the CT3IP in slot 9:
controller t3 9/0/0 t1 6 bert pattern 0s interval 30
To enable the one-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 7000 series routers with the RSP7000 and RSP7000CI and in Cisco 7500 series routers, use the t1 fdl ansi controller configuration command. Use the no form of this command to disable the performance report.
t1 channel fdl ansi| channel | Number between 1 and 28 that indicates the T1 channel. |
Disabled
Controller configuration
This command first appeared in Cisco IOS Release 11.1 CA.
The t1 fdl ansi command can be used only if the T1 framing type is extended superframe (ESF).
To display the remote performance report information, use the show controllers t3 remote performance command.
In the following example, the performance reports are generated for T1 channel 8 on the CT3IP:
controller t3 9/0/0 t1 8 fdl ansi
The CT3IP supports RFC 1406 and RFC 1407 (CISCO-RFC-1407-CAPABILITY.my). For information on accessing Cisco MIB files, refer to the Cisco MIB User Quick Reference.
For RFC 1406, Cisco supports all tables except the "Frac" table. For RFC 1407, Cisco supports all tables except the "FarEnd" tables.
For more information on the CT3IP, refer to the Channelized T3 Interface Processor (CT3IP) Installation and Configuration publication. For more information on the PA-CT3/4T1, refer to the Channelized T3 Dual-Wide Port Adapter Installation and Configuration publication.
|
|