Testing Configuration Connections for the Cisco 6100 Series System

Note Testing configuration connection procedures for both a Direct Connect and a Digital Off-Hook (DOH) configuration are covered in this chapter.

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

Step 2 Verify that the Cisco 6110 chassis is securely mounted to the rack (applicable in a DOH configuration only).

Step 3 Verify that the fan tray is securely mounted to the rack.

Step 4 Verify that the POTS splitter (Cisco 6120 or Siecor POTS splitter) chassis is securely mounted to the rack.

Step 5 Tighten any mounting screws as necessary.

• Cisco 6100/6130 chassis to the POTS splitter---Direct Connect with a POTS splitter configuration

• POTS splitter (Cisco 6120 or Siecor POTS splitter) to main distribution frame (MDF)---Direct Connect with a POTS splitter configuration

• Cisco 6130 chassis to MDF---Direct Connect without a POTS splitter configuration

• Cisco 6100 chassis to Cisco 6110 chassis---DOH configuration

• Cisco 6110 chassis to additional Cisco 6110 chassis---DOH configuration

• Cisco 6110 chassis to the Cisco 6120 chassis---DOH configuration

• Cisco 6120 chassis to the MDF---DOH configuration

• -48V_A

• -48RTN (A)

• -48V_B

• -48RTN (B)

Step 2 Configure the program for 38.4 kbps, 8 data bits, 1 stop bit, and no parity bits.

Step 4 Remove and reinsert the system controller module in the Cisco 6100/6130 to reset the module.

Step 5 Wait for all LEDs on the system controller module to turn off.

Step 6 Immediately press Enter on the PC once the LEDs turn off.

The system controller module IP configuration menu is displayed. If the system controller module has exited the self-test, you can restart by removing and reinserting the system controller module and going back to Step 3.

Step 7 Configure the IP address, subnet mask, and IP gateway using the appropriate menu options.

When configuring the server IP address, enter the address of the laptop PC that will be used to run the ViewRunner application.

Step 8 Choose the menu option to save the configuration to EEPROM.

Step 9 Choose Exit.

Step 10 Enter Y and press Enter when prompted to reset the system.

Step 2 Unplug the 10BaseT Ethernet/LAN connection from the system I/O card and connect the PC to the system I/O card using a 10BaseT Ethernet/LAN crossover cable.

Step 3 Verify IP connectivity to the Cisco 6100/6130 chassis by pinging the chassis from the PC.

Step 4 Load ViewRunner for Windows.

Step 5 Enter admin twice, once for the default username and once for the password.

Step 6 Select 6100 Addresses from the Options menu.

Step 7 Type in the system controller module IP address as configured in the previous section and an optional name for this system.

Step 8 Choose Add and then choose OK.

Step 9 Use the down arrow to select the 6100 IP address from the list of IP addresses and press Discover.

The Discover button has an icon with circular arrows and is positioned near the IP address window.

Step 10 Verify that all installed modules are properly discovered through ViewRunner.

Note For additional information, refer to the chapter on discovery in the ViewRunner for Windows User Guide or the ViewRunner for HP OpenView User Guide.

Step 2 Double-click on the system controller module and look at the Module Properties Configuration dialog box in ViewRunner to view the current Cisco 6100/6130 chassis software version running on the chassis.

If necessary, update the software on the chassis. Refer to the ViewRunner for Windows User Guide or the ViewRunner for HP OpenView User Guide for software download instructions.

Step 3 Build a new configuration of the chassis if a software update is necessary.

Make sure the new configuration matches the old configuration of the chassis. Refer to the ViewRunner for Windows User Guide or the ViewRunner for HP OpenView User Guide for software download instructions.

Step 4 Right-click the Cisco 6100/6130 chassis top border and select Configuration from the 6100 Properties menu.

Step 5 Set the proper date and time.

Step 6 Select OK.

Step 7 Verify that all installed xTU-C modules have green tabs.

Step 8 Verify that all other (noninstalled) xTU-C module slots have blue tabs. A blue tab indicates a provisioned but noninstalled module.

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 NI-1 module, attach a short coax cable between the DS3 transmit and receive connectors to loop back the interface. For an OC-3c NI-1 module, use a short multi-mode 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.

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 on the far end.

d. Type debug bert on and press Enter.

This command initiates the BER test.

e. Type debug bert header 00100011 and press 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.

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