Table of Contents

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

This chapter provides the test procedures to ensure that your Cisco 6130 with NI-2 system is connected correctly and is properly communicating with the system 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 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 tools and equipment:

Testing System Connectivity

This system connectivity test is a method for testing connectivity between the Cisco 6130 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:

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/2DS3 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 6130 chassis.

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

---

Note    This command prevents the CPE device from trying to retrain, although the command does not recognize far-end terminating equipment.

---

This command initiates the Bit Error Rate (BER) test.

This command sets the header bits of the outgoing cells and qualifies the incoming cells. See Table 7-1 for a description of the bit fields.

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).

---

---

Note    In Step 4g and Step 4h, "lines" refers to the incoming wire pairs used for CPE connections.

---

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.

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 may 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. For all Cisco 6xx Series CPE equipment, the command for verification is show ppp. The exception is the Cisco 633, which has no PPP connectivity capabilities. For third-party CPE equipment, consult the documentation that came with the equipment.

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