Upgrading the Field-Programmable Device Before Configuring the T3 Mode

Before you can configure the T3 mode, you must upgrade the field-programmable device (FPD), if an upgrade is required. An FPD upgrade requirement message appears when the hardware is installed and it is recognized. The FPD upgrade is first available in Cisco IOS Release 12.4(15)T and is available in future releases of Cisco IOS Release 12.4T.

You can perform the upgrade automatically or manually. The automatic upgrade method is preferred.

Using the EXEC Command Interpreter

You modify the configuration of your router through the software command interpreter called the EXEC (also called enable mode). You must enter the privileged level of the EXEC command interpreter with the enable command before you can use the configure command to configure a new interface or change the existing configuration of an interface. The system prompts you for a password if one has been set.

The system prompt for the privileged level ends with a pound sign (#) instead of an angle bracket (>). At the console terminal, use the following procedure to enter the privileged level:

Step 1 At the user-level EXEC prompt, enter the enable command. The EXEC prompts you for a privileged-level password as follows:

Router> enable

Password:

Step 2 Enter the password (the password is case sensitive). For security purposes, the password is not displayed.

When you enter the correct password, the system displays the privileged-level system prompt (#):

Router#

Replacing an Existing Port Adapter

Before you remove or replace a port adapter, use the shutdown command to disable the port adapter to prevent anomalies when you remove and reinstall the port adapter. When you shut down an interface, it is designated administratively down in the show command displays.

Configuring the Card Type

Use the card type command to configure or change the card type to T3 or E3 when the card is first inserted into the router. You must use this command before you can proceed with any other configuration tasks.

To enable the card type, issue the command card type {t3 | e3} slot

Note If you change the card type, you must reboot the router for the configuration to take effect.

Configuring an Unchannelized T3 Link

If you installed a new PA-T3/E3-EC or if you want to change the configuration of an existing PA-T3/E3-EC link, you must enter the privileged level of the EXEC command interpreter and then use the configure command. If you replace a PA-T3/E3-EC that was previously configured, the system recognizes the new PA-T3/E3-EC link and brings it up in its existing configuration.

After you verify that the new PA-T3/E3-EC is installed correctly (the ENABLED LED goes on), use the privileged-level configure command to configure the new interface. Be prepared with the information you need, such as the following:

•Protocols you plan to route on each new interface

•IP addresses, if you plan to configure the interfaces for IP routing

The configure command requires privileged-level access to the EXEC command interpreter, which usually requires a password. Contact your system administrator if necessary to obtain EXEC-level access.

Setting the Framing Type for the Serial Interface

Use the no form of this command to return to the default, c-bit framing.

Specifying the Cable Length for the Serial Interface

At the prompt, specify the cable length using the cablelengthfeet interface command, where:

•feet is a numeral from 0 to 450.

•The default value is 10 feet.

An example follows:

Router(config-if)# cablelength 40

Note For the cablelengthfeet command, user-specified T3 cable lengths are structured into ranges: 0-49 and 50-450 to represent short and long cables.

If the numerical value entered by the user falls within the lower range, then the PA-T3/E3-EC T3 port is set for short cable output levels. If the value falls into higher range, the long cable output levels will be used.

In the preceding example, a cable length of 40 is specified, which means that the 0-49 range is used. If you change the cable length to 45, then the 0-49 range still applies. Further, if you specify a cable length of 100 or 200, the 50-450 range applies in both cases. Only moving from one range (0-49) to the other range (50-450) has an effect. The actual cable-length number you enter is stored in the configuration file. It is recommended that the actual cable length be entered to ensure future compatibility.

Setting the Clock Source for the Serial Interface

At the prompt, set the internal or line clock source for the selected T3 controller with the clock source {line | internal} interface command, where:

•line selects a network clock source.

•internal selects an internal clock source.

The default is clock source internal.

Examples follow:

•Instruct the PA-T3/E3-EC to use a line clock source.

The example that follows is for a port adapter in slot 1 of a Cisco 7200 VXR router:

Router(config)# interface serial 1/0

Router(config-if)# clock source line

•Instruct the PA-T3/E3-EC to use an internal clock source.

The example that follows is for a port adapter in slot 1 of a Cisco 7200 VXR router:

Router(config)# interface serial 1/0

Router(config-if)# clock source internal

Configuring MDL Messages for the Serial Interface

You can configure maintenance data link (MDL) messages (which are defined in the ANSI T1.107a-1990 specification) on the PA-T3/E3-EC.

The local DSU mode must match the remote DSU or T3 port configuration. For example, if an ADC Kentrox DSU is at the remote end of the T3 link, then the local T3 port must be configured for mode 1.

You need to know what type of DSU is at the remote T3 end to find out if it interoperates with the PA-T3/E3-EC. Specify mode 0 for connection from a PA-T3/E3-EC to another PA-T3/E3-EC or a Digital Link DSU (DL3100). Specify mode 1 for connection from a PA-T3/E3-EC to a Kentrox DSU. Specify mode 2 for connection from a PA-T3/E3-EC to a Larscom DSU. See Table 4-1 for a list of DSUs and their corresponding bandwidth ranges.

Note If the far-end DSU has more than one DTE (HSSI) port, connect to and configure only DTE#1. See Caution below for Verilink DSUs.

Caution Always connect to and configure HSSI port B on the Verilink HDM 2182. Port A is not supported by the PA-T3/E3-EC.

Caution The PA-T3/E3-EC does not support the Kentrox DSU bandwidth setting of 1.0 mbps. The Kentrox DSU speed must be set to 1.5 mbps or greater.

Caution For all DSU modes, the DSU must be configured for the same transmit and receive speeds. Asymmetrical transmit and receive speeds are not supported.

Setting the Bandwidth for the Serial Interface

In interface configuration mode, set the bandwidth to be used by the serial interface on the T3 link by entering the dsu bandwidthbandwidth configuration command, as in the following example:

Router(config-if)# dsu bandwidth 16000

The allowable bandwidth range is 1 to 44210 kbps. Use the no form of this command to return to the default, 44210.

The local DSU bandwidth value must match the remote DSU or T3 port bandwidth exactly. For example, if you set the DSU bandwidth to 16000 on the local port, you must do the same on the remote DSU or T3 port.

Setting Scrambling for the Serial Interface

In interface configuration mode, enable serial interface scrambling by entering the scramble configuration command, as in the following example:

Router(config-if)# scramble

Use the no form of this command to restore the default value, disabled.

The local port configuration must match the remote DSU or T3 port configuration. For example, if you enable scrambling on the local port, you must do the same on the remote DSU or T3 port.

Configuring Loopback Mode for the Serial Interface

With loopbacks, you can detect and isolate equipment malfunctions by testing the connection between thePA-T3/E3-EC interface and a remote device such as a CSU/DSU. Remote loopback sends a command to loop the T3 line at the far end. It can be used to diagnose problems with cables from the port adapter to the switching office. Network loopback loops the PA-T3/E3-EC T3 port back to the network, allowing the remote end to test the connection to the PA-T3/E3-EC.

Local loopback loops the PA-T3/E3-EC T3 port back to itself, allowing it to be tested in isolation from the T3 cables and remote T3 equipment.

The loopback command places an interface in loopback mode, which enables test packets that are generated from the ping command to loop through a remote device and cables. If the packets complete the loop, the connection is good.

The default is no loopback.

To return the serial interface to its default unlooped condition, use the no form of the command.

2These loopback commands are only available when the DSU mode is set to 1, Kentrox mode.

Shutting Down the Serial interface

You can shut down the serial interface on the PA-T3/E3-EC with the shutdown controller command.

This command sends a DS3 idle signal toward the network. You can bring the serial interface back up with the no shutdown command.

The example that follows is for a port adapter in slot 1 of a Cisco 7200 VXR router:

Router(config)# interface serial 1/0

Router(config-controller)# shutdown

Configuring a BER Test on the Serial Interface

Bit error rate test (BERT) circuitry is built into the PA-T3/E3-EC. With BER tests, you can test cable and signal problems in the field.

There are two categories of test patterns that can be generated by the onboard BER test circuitry: pseudorandom and repetitive. The former test patterns are polynomial-based numbers and conform to the CCITT/ITU O.151 and O.153 specifications; the latter test patterns are zeros or ones, or alternating zeros and ones.

A list of the available test patterns follows:

•Pseudorandom test patterns:

–2^15 (per CCITT/ITU O.151)

–2^20 (per CCITT/ITU O.151 non-QRSS)

–2^23 (per CCITT/ITU O.151)

•Repetitive test patterns:

–All zeros (0s)

–All ones (1s)

–Alternating zeros (0s) and ones (1s)

Both the total number of error bits received and the total number of bits received are available for analysis. You can set the testing period from 1 minute to 14,400 minutes (240 hours), and you can also retrieve the error statistics anytime during the BER test.

When running a BER test, your system expects to receive the same pattern that it is transmitting. To accomplish this, two common options are available:

•Use a loopback somewhere in the link or network.

•Configure remote testing equipment to transmit the same BER test pattern at the same time.

Sending a BER Test Pattern on the T3 Line

You can send a BERT pattern on the T3 line with the bert pattern patternintervaltime command in controller configuration mode, where:

For a BER test that you terminate, this line indicates the time the test would have taken to run and the time remaining for the test to run had you not terminated it; "unable to complete" signifies that you interrupted the test.

Bit Errors(since BERT started): 6 bits,

Bits Received(since BERT started): 8113 Kbits

Bit Errors(since last sync): 6 bits

Bits Received(since last sync): 8113 Kbits

These four lines show the bit errors that have been detected versus the total number of test bits that have been received since the test started and since the last synchronization was detected. Bits and errors are only counted when the test status is "sync".

Terminating a BER Test

You can terminate a BER test with the no bert controller command.

The following example terminates the BER test running on T3 line 0.

The example that follows is for a port adapter in slot 1 of a Cisco 7200 VXR router:

Performing a Basic Serial Interface Configuration

Following are instructions for a basic configuration: enabling an interface and specifying IP routing. You might also need to enter other configuration commands, depending on the requirements for your system configuration and the protocols you plan to route on the interface. For complete descriptions of configuration commands and the configuration options available for serial interfaces, refer to the appropriate software documentation.

In the following procedure, press the Return key after each step unless otherwise noted. At any time you can exit the privileged level and return to the user level by entering disable at the prompt as follows:

Router# disable

Router>

Step 1 Enter configuration mode and specify that the console terminal is the source of the configuration commands, as follows:

Step 7 After including all of the configuration commands to complete your configuration, press Ctrl-Z—hold down the Control key while you press Z—or enter end or exit to exit configuration mode and return to the EXEC command interpreter prompt.

Step 8 Write the new configuration to NVRAM as follows:

Router# copy running-config startup-config

[OK]

Router#

This completes the procedure for creating a basic configuration.

Checking the Configuration

After configuring the new interface, use the show commands to display the status of the new interface or all interfaces, and use the ping and loopback commands to check connectivity. This section includes the following subsections:

Using show Commands to Verify the New Interface Status

Table 4-3 demonstrates how you can use the show commands to verify that new interfaces are configured and operating correctly and that the PA-T3/E3-EC appears in them correctly. Sample displays of the output of selected show commands appear in the sections that follow. For complete command descriptions and examples, refer to the publications listed in the "Related Documentation" section on page iv.

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.

Table 4-3 Using show Commands

Command

Function

Example

show version orshow hardware

Displays system hardware configuration, the number of each interface type installed, Cisco IOS software version, names and sources of configuration files, and boot images

Router# show version

show controllers

Displays all the current interface processors and their interfaces

Router# show controllers

show diagslot

Displays types of port adapters installed in your system and information about a specific port adapter slot, interface processor slot, or chassis slot

Displays protocols configured for the entire system and for specific interfaces

Router# show protocols

show running-config

Displays the running configuration file

Router# show running-config

show startup-config

Displays the configuration stored in NVRAM

Router# show startup-config

If an interface is shut down and you configured it as up, or if the display indicates that the hardware is not functioning properly, ensure that the interface is properly connected and terminated. If you still have problems bringing up the interface, contact a service representative for assistance. This section includes the following subsections:

Using the show version or show hardware Commands

Display the configuration of the system hardware, the number of each interface type installed, the Cisco IOS software version, the names and sources of configuration files, and the boot images, using the show version (or show hardware) command.

Note The outputs that appear in this document may not match the output you receive when running these commands. The outputs in this document are examples only.

Following is an example of the show version command from a Cisco 7200 VXR router with the PA-T3/E3-EC:

c7201alpha1 uptime is 5 days, 18 hours, 32 minutes System returned to ROM by power-on
System image file is "disk0:c7200p-adventerprisek9-mz.2006-10-01.biffdev"

This product contains cryptographic features and is subject to United States and local
country laws governing import, export, transfer and use. Delivery of Cisco cryptographic
products does not imply third-party authority to import, export, distribute or use
encryption.

Importers, exporters, distributors and users are responsible for compliance with U.S. and
local country laws. By using this product you agree to comply with applicable laws and
regulations. If you are unable to comply with U.S. and local laws, return this product
immediately.

A summary of U.S. laws governing Cisco cryptographic products may be found at:

http://www.cisco.com/wwl/export/crypto/tool/stqrg.html

If you require further assistance please contact us by sending email to export@cisco.com.

Using the show controllers Command

You can display information for the T3 controller within a PA-T3/E3-EC in Cisco 7200 VXR routers with the show controllers t3port-adapter/t3-port [brief | tabular] command, where:

•brief displays a list of configurations only.

•tabular displays a list of configurations and MIB data in a tabular format.

Note If you use the show controllers T3port-adapter/t3port command without either of the optional arguments (brief or tabular), all information is displayed for the T3 controller you specified; therefore, the resulting display output can be extensive.

If you use the show controllers T3 command without specifying a port address (port-adapter/t3port), all information is displayed for all T3 port adapters in the router; therefore, the resulting display output can be extensive.

Following is an example of the show controllers T3 command that shows a PA-T3/E3-EC in port adapter slot 4 of a Cisco 7200 VXR router:

Router# show controllers t3 5/0

T3 5/0 is up.

Applique type is Subrate 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 Line

Equipment customer loopback

Configured not to accept remote request to reset subrate

Data in current interval (48 seconds elapsed):

145 Line Code Violations, 5 P-bit Coding Violation

3 C-bit Coding Violation, 1 P-bit Err Secs

0 P-bit Severely Err Secs, 1 Severely Err Framing Secs

0 Unavailable Secs, 1 Line Errored Secs

1 C-bit Errored Secs, 0 C-bit Severely Errored Secs

1 Severely Errored Line Secs

1 Far-End Errored Secs, 1 Far-End Severely Errored Secs

0 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 0 Far-end path failures

0 Far-end code violations, 0 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

Data in Interval 1:

157 Line Code Violations, 17 P-bit Coding Violation

12 C-bit Coding Violation, 4 P-bit Err Secs

0 P-bit Severely Err Secs, 4 Severely Err Framing Secs

2 Unavailable Secs, 2 Line Errored Secs

3 C-bit Errored Secs, 0 C-bit Severely Errored Secs

1 Severely Errored Line Secs

4 Far-End Errored Secs, 1 Far-End Severely Errored Secs

11 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 1 Far-end path failures

12 Far-end code violations, 11 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

Total Data (last 1 15 minute intervals):

157 Line Code Violations, 17 P-bit Coding Violation,

12 C-bit Coding Violation, 4 P-bit Err Secs,

0 P-bit Severely Err Secs, 4 Severely Err Framing Secs,

2 Unavailable Secs, 2 Line Errored Secs,

3 C-bit Errored Secs, 0 C-bit Severely Errored Secs

1 Severely Errored Line Secs

4 Far-End Errored Secs, 1 Far-End Severely Errored Secs

11 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 1 Far-end path failures

12 Far-end code violations, 11 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

Using the ping Command to Verify Network Connectivity

Using the ping command, you can verify that an interface port is functioning properly. This section provides a brief description of this command. Refer to the publications listed in the "Related Documentation" section on page iv for detailed command descriptions and examples.

The ping command sends echo request packets out to a remote device at an IP address that you specify. After sending an echo request, the system waits a specified time for the remote device to reply. Each echo reply is displayed as an exclamation point (!) on the console terminal; each request that is not returned before the specified timeout is displayed as a period (.). A series of exclamation points (!!!!!) indicates a good connection; a series of periods (.....) or the messages [timed out] or [failed] indicate a bad connection.

Following is an example of a successful ping command to a remote server with the address 10.0.0.10:

If the ping command to the remote IP address failed, then use loopbacks to troubleshoot the T3 connection using the following steps:

Step 1 Use the show controller T3 and show interfaces serial commands to confirm that the T3 controller, serial interface, and line protocol are up.

Step 2 Place the serial interface of the PA-T3/E3-EC in local loopback using the loopback local command.

Step 3 Repeat the ping command using the IP address of the local serial interface. Using the previous example where the remote server's IP address was 10.0.0.10, if the local IP address is 10.0.0.5, then use the command:

ping 10.0.0.5

If the ping is successful, proceed to Step 4. A failure indicates a configuration problem or a hardware problem with the PA-T3/E3-EC.

Step 4 Remove the local loop with the no loopback command and place the remote server or DSU in network loopback with the loopback remote command.

Note The loopback remote command is only available when the framing is set to c-bit parity. If the framing is not set to c-bit parity, the remote server will have to be placed into network loopback by someone at the remote site.

Step 5 Repeat Step 3. If the ping is successful, then the PA-T3/E3-EC and the T3 link to the remote site is functioning correctly. The problem is probably in the remote DSU or server configuration or hardware. If the ping fails, then one of the following has a problem: the T3 link to the remote site, the remote server or DSU configuration, or the hardware .