Testing Configuration Connections for the Cisco 6100 with NI-2 System

This chapter provides the test procedures to ensure that your Cisco 6100 with NI-2 system is connected correctly and is properly communicating with the management software.

In this chapter, you will test the system connections by completing the following procedures:

Caution Proper ESD protection is required whenever you handle Cisco digital subscriber line access multiplexer (DSLAM) equipment. Installation and maintenance personnel should be properly grounded using ground straps to eliminate the risk of ESD damage to the equipment. Cards are subject to ESD damage whenever they are removed from the chassis.

Required Equipment

To run the tests described in this chapter, you need the following equipment:

Crossover Ethernet cable

Terminal emulator (for example, ProComm Plus or HyperTerminal)

Appropriate customer premises equipment (CPE) device (optional)

Cisco 675 for quad-port flexi ATU-C line cards (4xflexis) configured as CAP

Cisco 677 for 4xflexis configured as DMT

Cisco 678 for 4xflexis configured as CAP or DMT
Cable (optional--see "Cable and Port Mapping Specifications" for cable information)
Punch-down tool (optional)
66 block to RJ-11 jumper (optional)
Necessary equipment for ESD protection--Required whenever you handle Cisco DSLAM equipment, which includes the chassis, modules, and cards

Testing System Connectivity

This system connectivity test is a method for testing connectivity between the Cisco 6100 with NI-2 system and the MDF for all xTU-C ports in the system. This test is also known as a Zing Test.

Note The system connectivity test is optional. The Cisco 675 and Cisco 678 are the only CPE devices that can perform bit error rate (BER) testing.

Complete the following steps to test system connectivity:

Step 1 Attach the CPE device to the first wire pair on the subscriber side of the MDF.

If you use 66-type punchdown blocks, you can make the connection by using a cable with alligator clips on one end and an RJ-11 connector on the other. Depending on the type of MDF that you are using, a different cabling configuration can be required.

Step 2 Loop back the network interface port.

For a DS3/DS3 NI-2 card, attach a short coaxial cable between the DS3 transmit and receive connectors to loop back the interface. For an OC-3c/OC-3c NI-2 card, use a short multimode or single-mode fiber to loop back the interface.

Step 3 Train the CPE device to the first modem port on the Cisco 6100/6130.

Step 4 To perform a BER test on the line, complete these steps:

a. Log in to the CPE device using an Ethernet or serial port.

b. Type enable debug commands and press Enter.

c. Type int wan0 stay and press Enter.

Note This step prevents the CPE device from trying to retrain, even though it does not recognize far-end terminating equipment.

d. Type debug bert on and press Enter.

: This command initiates the BER test.

e. Type debug bert header 00100011 and press Enter.

: This sets the header bits of the outgoing cells and qualifies the incoming cells. Step 4b through Step 4e are the four bytes of header not including the calculated header error control (HEC) byte. See Table 6-1 for a description of the bit fields.

Table 6-1: Bit Field Description

7 6 5 4 3 2 1 0

GFC

VPI

VPI

VCI

VCI

VCI

VCI

PTI

CLP

Example: VPI=1, VCI=1 (GFC=0, PTI=0, CLP=0) across the ADSL loop:
NSOS>debug bert header 00100010 <Enter>

7	6	5	4	3	2	1	0
GFC	VPI
VPI	VCI
VCI	VCI
VCI	PTI	CLP
Example: VPI=1, VCI=1 (GFC=0, PTI=0, CLP=0) across the ADSL loop: NSOS>debug bert header 00100010 <Enter>

f. Type debug bert count and press Enter.

: This step displays a count of the BER test errors and cell loss since the previous query. The first number reported is the number of cells with sequence errors. The second number is the number of cells with bit errors.

Note The meaning for each of the top two LEDS on the CPE device changes during the BER test. The BERT SYNC LED (WAN LNK) is illuminated once the CPE device detects a valid BER test pattern. The BERT ERROR LED (WAN ACT) is toggled whenever the CPE device detects a BER test error. During a successful BER test, the WAN LNK LED is illuminated. The WAN ACT LED is solid (either off or on, but not blinking).

g. Repeat Step 3 through Step 4g for the remaining 15 lines.

h. Repeat the Zing test for the Champ connectors labeled for lines 16 through 32, 33 through 48, and 49 through 64.

Testing PPP Connectivity

This section provides instructions for testing point-to-point protocol (PPP) connectivity.

Note Testing PPP connectivity is optional. The Cisco 633 does not have PPP connectivity capabilities.

Step 1 Attach the CPE device to the first wire pair on the subscriber side of the MDF.

If you use 66-type punchdown blocks, you can make the connection by using a cable with alligator clips on one end and an RJ-11 connector on the other. A different cabling configuration can be required depending on the MDF type.

Step 2 Power on the CPE device.

Step 3 Verify that the PPP LCP and NCP states are open after the train.

Step 4 Move the RJ-11 jumper to the next punched line and repeat the procedure until you verify all punched lines.

Table of Contents