|
|
This appendix provides the test procedures necessary to ensure your Cisco 6100 Series system is connected correctly and is communicating with the ViewRunner software.
To run the tests described in this appendix, you need the following equipment:
Before proceeding with the connection test procedures, inspect the chassis from the front and back.
To inspect the Cisco 6100 Series system from the front, verify that the multiplexer chassis (MC), fan tray, and POTS splitter chassis (PSC) (if applicable) are securely mounted to rack. Tighten the mounting screws as necessary.
When you inspect the Cisco 6100 Series system from the rear, you need to complete the
following steps:
Step 1 Verify that the cables from the MC to the line concentration chassis (LCC) and from the LCC to the PSC are in the proper position. The following types should be present:
Step 2 Verify that all cables are as described in the Cisco 6100 Set Up and Installation Manual.
Step 3 Verify that all connectors are securely fastened (screwed in). Ensure that the Champ connectors are tie wrapped to the connector bracket. (See Figure D-1.)
Step 4 Verify that the 10BaseT Ethernet/LAN connection is attached to the DS3 system I/O card.
Step 5 Verify that the MC, LCC, and PSC are grounded. (Refer to the Cisco 6100 Set Up and Installation Manual.)
Step 6 Verify that the following are wired to the MC from the proper sides of the fuse and
alarm panel:
Step 7 Verify that the correct fuse and alarm panel slot is wired to the MC (fuse and alarm panel slot 1).
Step 8 Verify that the proper fuse and alarm panel slot and values for both A and B power. Refer to the Cisco 6100 Series User Guide for fuse calculation tables.
Step 9 Verify that the proper voltage is present on the MC (-42 VDC to -56 VDC, nominal -48 VDC).
Use the following steps to configure the management port IP:
Step 1 From the Windows PC, load a terminal program (such as ProComm Plus or HyperTerminal).
Step 2 Configure the program for 38.4 kbps, 8 data bits, 1 stop bit, and no parity bits
Step 3 Attach the 9-pin serial cable to the PC and the system controller (SC) module front panel 9-pin D-sub connector.
Step 4 To reset the SC module, do one of the following:
Step 5 Wait for all LEDs on the SC module to turn off.
Step 6 Once the LEDs turn off, immediately press Enter on the PC. The SC module IP configuration menu is displayed. If the SC module has already exited the self-test, you can restart by removing and reinstalling the SC module and going back to Step 3.
Step 7 Using the appropriate menu options, configure the IP address, subnet mask, and IP gateway. 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. When prompted to reset the system, enter Y and press Enter.
To attach ViewRunner management software to the Cisco 6100 Series system, use these steps:
Step 1 Verify that the PC that will be used during these connection test procedures has an IP address that is on the same subnet as the Cisco 6100 Series system IP address configured in the previous section.
Step 2 Unplug the 10BaseT Ethernet/LAN connection from the DS3 system I/O card and connect the PC to the DS3 system I/O card using a 10BaseT Ethernet/LAN crossover cable. Verify IP connectivity to the MC by pinging the MC from the PC.
Step 3 Load Load ViewRunner for Windows. Enter admin twice, once for the default username and once for the password.
Step 4 Choose Options >> 6100 Addresses from the pull-down menu.
Step 5 Type in the SC module IP address as configured in the previous section and an optional name for this system.
Step 6 Choose Add and then choose OK.
Step 7 From the drop-down list at the top of the screen, select 6100 IP address from the list of IP addresses and press Discover. This button has an icon with circular arrows and is positioned near the IP address window.
Step 8 Verify that all installed modules are properly discovered through ViewRunner. For additional information, see the "Autodiscovery" section.
To provision the Cisco 6100 Series system for the test, use these steps:
Step 1 To save the current configuration of the MC to the PC, select File >> Save Configuration.
Step 2 To view the current MC software version running on the MC, double-click on the SC module and look at the Module Properties Configuration dialog box in ViewRunner. If necessary, update the software on the MC. See "Updating the Cisco 6100 Series System Software," for software download instructions.
Step 3 If a software update is necessary, build a new configuration of the MC. Make sure the new configuration matches the old configuration of the MC. See "Updating the Cisco 6100 Series System Software," for software update procedures.
Step 4 Right-click the MC top border and select 6100 Properties >> Configuration.
Step 5 Set the proper date and time and select OK.
Step 6 Verify that all installed xTU-C modules have green tabs and that all other xTU-C module slots have blue tabs. A blue tab indicates a provisioned but noninstalled module.
This system connectivity test is a method for testing connectivity between the Cisco 6100 Series system and the MDF for all CAP ATU-C ports in the system. It is also known as a Zing Test.
Step 7 Attach the CPE device to the first wire pair on the subscriber side of the MDF. If 66-type punchdown blocks are used, connection can be made 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 8 Loop back the network interface port. For a DS3 network interface (NI) module, attach a short coax cable between the DS3 transmit and receive connectors to loop back the interface. For an OC-3c NI module, use a short multi-mode or single-mode fiber to loop back the interface.
Step 9 Train the Cisco 675 to the first modem port on the MC.
Step 10 To perform a BER test on the line, use these steps:
(a) Log in to the Cisco 675 using an Ethernet or serial port.
(b) At the prompt, type enable debug commands and press Enter.
(c) At the prompt, type int wan0 stay and press Enter.
(d) At the prompt, type debug bert on and press Enter.
This command initiates the BER test.
(e) At the prompt, type debug bert header 00100011 and press Enter.
This sets the header bits of the outgoing cells and qualifies the incoming cells. Step 3b through Step 3e are the four bytes of header not including the calculated HEC byte. See Table D-1 for a description of the bit fields.
| 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: | |||||||
(f) At the prompt, type debug bert count and press Enter.
This 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, and the second number is the number of cells with bit errors.
(g) Repeat Step 2 through Step 3g 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.
If you choose to test PPP connectivity, you will need to do the following:
Step 1 Attach the Cisco 675 to the first wire pair on the subscriber side of the MDF. If 66-type punchdown blocks are used, connection can be made 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 Cisco 675 and verify that the PPP LCP and NCP states are open after the train.
Step 3 Move the RJ-11 jumper to the next punched line and repeat the procedure until you verify all punched lines.
Posted: Fri Oct 8 16:11:11 PDT 1999
Copyright 1989-1999©Cisco Systems Inc.