Table of Contents
BERT Testing and System Set Up Verification
This appendix refers you to documentation from other sources of information related to the Cisco 6100 and ViewRunner systems but not specifically part of these products.
For the most part, the information in this appendix has to do with testing methods.
This section describes BERT tests using a Cisco 6100, Cisco 675, and an optional HP Broadband test set.
All tests are based on the single cell version of S-PRBS9. This is the only PRBS pattern that is supported by the HP for generating multiple channels of cell load. All cells will have the same data, therefore it is necessary to have a cell sequence number to verify cell loss. This is done using AAL-1.
Cells are generated by the HP and terminated by the 675s in the downstream direction, and vice versa for the upstream direction. The HP can only check BERT data on one channel at a time. It is therefore necessary to manually walk through every channel to verify data integrity. The BERT test can be performed without the HP test set if the 6100 network interface (NI) is physically looped back at the OC3 port.
The following are the procedures for transmitting BERT data. Note that all pertinent tests will be initiated from the optical line interface card, and not a cell processor.
- Configure the load generator (truck icon) to send S-PRBS9 data to each 675 on VPI X / VCI X. Starting with channel 2 on the load generator, set up a connection using VPI 1 / VCI 32. Continue with channel 3 as VPI 1 / VCI 33 and so on until the number of channels that need to be tested are accounted for.
- Set the contents of each cell to S-PRBS9 with AAL-1 enabled. All channels can be done at once by highlighting all of the channels and then setting the contents. AAL-1 provides sequence numbers to determine if cells are being dropped.
- Set the bandwidth to the desired downstream rate. Again, all channels can be highlighted and changed simultaneously. This rate should be slightly lower than the trained rate (1.4M).
- Configure the 6100, using ViewRunner, to set up connections from the network interfaces (NIs) OC3 to the 675s. Use the same connection parameters (VPI/VCI) that were used to configure the load generator.
- Verify that no other cell generation sources are active on the HP and that the laser is turned on.
- Compile the load generator and data will start flowing to the NI, through the 6100 and out to the 675s. Every time a parameter is changed in the load generator it is necessary to compile for the change to take effect.
The 675 should now be receiving BERT data.
Once the 675s have been BERT enabled, they will send S-PRBS9 BERT data towards the 6100. The HP can verify the BERT data once channel at a time. The following are the procedures for receiving BERT data. Note that the ViewRunner must be used to set up all of the connections to the HP (see above).
- Select the receive filter from the optical line interface card and not the cell processor card. This is the net/strainer icon.
- Specify the VPI and VCI that needs to be checked. The receive filter mode should be virtual channel.
- Select S-PRBS9 and AAL-1. Now, only the specified cells will make it to the statistics counters.
- Select the statistics icon (ones and zeros). From there select View and then ATM Statistics.
- Select Selected Cell Count, Bandwidth, Cell Loss, etc.
- Apply
- Select measurements and start the counters.
This will give you the statistics for the cell that is currently selected in the receive filter. Repeat the above procedure to check other channels. The cell protocol processors can be used to view incoming cells if desired.
The following procedures for configuring the 675 requires that you have software version 1.2.2 or greater.
- Login to the 675 via ethernet or serial port
Login: root
Password: <Enter>
- Give access to the BERT commands:
cbos> enable debug commands <Enter>
- Keep the 675s from trying to re-train even though they do not see a Cisco FireRunner on the far end:
cbos> ifc wan0 stay <Enter>
cbos> debug bert on <Enter>
- Set the header bits of the outgoing cells and qualify the incoming cells.
cbos> debug bert header 00100010 <Enter>
Note These are the four bytes of header not including the calculated HEC byte. See the table below for a description of the bit fields.
Table A-1: 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 (see command line above).
- Display a count of the BERT errors and cell loss since the previous query:
cbos> debug bert count <Enter>
Note that the top two LEDs on the 675 take on a new meaning during the BERT tests.
- BERT SYNC LED - This is the top LED and is illuminated once the 675 detects a valid BERT pattern.
- BERT ERROR LED - This is the second LED from the top and is toggled whenever the 675 detects a BERT error.
During a successful BERT test, the top LED will be illuminated, and the second LED will be solid (either off or on, but not blinking).
This procedure can be used to make sure that you have connectivity during installation of the 6100 system. This verification can be done even before the system is provisioned via ViewRunner.
Validate the continuity of the wiring/cabling between the Public Switch Telephone Network (PSTN) and the Main Distribution Frame (MDF) to the POTS splitter chassis (PSC). The following table describes the procedures to determine whether or not the following connections exist:
- End-to-end electrical connectivity between an MDF connection and its associated line interface module (LIM) card and port.
- Digital Off-Hook (DOH) operation for the LIM port being tested.
- Electrical connectivity from the MDF to an ATU-C.
- Electrical connectivity to the PSTN via the POTS splitter for an associated subscriber.
Table A-2: Testing Physical End-to-End Cabling
Required Equipment
| - 1 Cisco 675
- 1 CPE POTS splitter (15K or 8K depending on install configuration)
- 1 telephone (CENTREX type or standard POTS set depending on install configuration)
- 1 RJ-11 cable (one side RJ-11, the other side exposed wire for punch down) for connecting CPE POTS splitter to MDF
- 2 RJ-11 cables (one RJ-11 to RJ-11 for CPE POTS splitter to phoneset, and one RJ-11 to RJ-11 to the 675)
- 1 system controller (SC)
- 1 NI module
- 1 ATU-C
- 1 LIM controller (LC)
- 1 LIM
- 1 POTS splitter module
|
Set Up the 6100
| - Configure the 6100 with 1 SC, 1 ATU-C, 1 LC, 1 LIM, and 1 POTS splitter module. The LIM and POTS modules will go into the slots that contains the port being tested.
- At the MDF, punch down the RJ-11 cable to the subscriber port that is to be tested. This acts as the subscriber line to the 675.
- Punch down a connection to a voice switch or tester providing dial tone for POTS testing.
- Using the RJ-11 cables, hook the telephone, subscriber line, and ADSL line into the POTS splitter as outlined in the CPE documentation.
|
Operation
| - Power the 675 on. Verify that the associated LIM port detects off-hook (the LIM port displays its LED as solid green). Once this has occurred, verify that the ATU-C trains up to the 675 by checking the LEDs on the ATU-C and the 675. If the 675 and the ATU-C are trained, the 675 WAN LNK will be solid green (the LED blinks during training activity), and the ATU-C LED will be solid green. This verifies subscriber connectivity from the MDF for that port.
- Verify the telephone receives dialtone and outgoing calls can be established. Verify incoming calls ring the phone.
|
The following series of steps enable you to determine the presence of a non-interrupted data path between your 6100 system and far-end equipment. More specifically, this test determines whether or not your system has IP connectivity through the ATM network to a far-end server via the FireRunner.
Table A-3: Testing End-to-End Connectivity
Required Equipment
| - 1 Cisco 675 configured with valid IP address
- 1 CPE POTS splitter (15K or 8K depending on install configuration)
- 1 telephone (CENTREX type or standard POTS set depending on install configuration)
- 1 RJ-11 cable (one side RJ-11, the other side exposed wire for punch down) for connecting CPE POTS splitter to MDF
- 2 RJ-11 cables (one RJ-11 to RJ-11 for CPE POTS splitter to phoneset, and one RJ-11 to RJ-11 to the 675)
- 1 SC
- 1 NI module
- 1 ATU-C
- 1 LC
- 1 LIM
- 1 POTS splitter module
- ViewRunner with connectivity to the 6100
|
Set Up the 6100
| - Configure the 6100 with 1 SC, 1 NI, 1 ATU-C, 1 LC, 1 LIM, and 1 POTS splitter module. The LIM and POTS modules need to be inserted into the slot that supports the local loop you want to test. See Cisco 6100 Set Up and Installation Manual for detailed information on the special subscriber tip/ring mapping to a particular LCC/PSC slot or port number.
- Using ViewRunner for Windows, configure the module, port, and subscriber to be tested per the provisioning steps described in "System Alarm/Event Troubleshooting,", in the ViewRunner for Windows Provisioning and Operation Manual.
Note In order to accomplish end-to-end IP testing, an appropriate VPI/VCI path must be established from the 6100 network side connection through the ATM switching infrastructure to the Cisco FireRunner.
- At the MDF, punch down the RJ-11 cable to the subscriber port that is to be tested. This acts as the subscriber line to the 675.
- Connect the subscriber line to the CPE POTS splitter.
- Using the RJ-11 cables, hook the telephone, subscriber line, and ADSL line into the POTS splitter as outlined in the CPE documentation.
|
Operation
| - Power the 675 LIM ports on. Verify that the associated LIM port detects DOH (the LIM port displays its LED as solid green). Once this has occurred, watch the multiplexer chassis (MC) for a blinking ATU-C. Verify that the ATU-C trains up to the 675 by checking the LEDs on the ATU-C and the 675. If the 675 and the ATU-C are trained, the 675 WAN LNK will be solid green (the LED blinks during training activity), and the ATU-C LED will be solid green. This verifies subscriber connectivity through the MDF, the PSC, and through the LIM and to the ATU-C for that port.
- Verify the telephone receives dialtone and outgoing calls can be established. Verify incoming calls ring the phone.
- For IP connectivity, try pinging the server from the laptop once the 675 has successfully trained. Follow the pinging procedure documented in the 675 manual. If the system responds to your ping request with an acknowledgment, end-to-end connectivity has been successfully established between the 675 and the FireRunner. This also validates a current 6100 configuration and subscriber line connection.
|
Posted: Tue Nov 16 11:52:16 PST 1999
Copyright 1989-1999©Cisco Systems Inc.
