4.1 Introduction

4.2 LEDs

4.2.1 Trunk LEDs

4.2.2 Hot Swap LED

4.2.3 Ethernet LEDs

4.3 Verifying That the Board is Installed Correctly

4.4 Verifying That the Board is Working Correctly

4.5 Demonstration Programs

4.1 Introduction

This chapter provides the procedures used to verify that the CG 6100C board is installed and configured correctly. Before you begin, make sure you have created a board keyword file. For more information about CG 6100C board keyword files, refer to Chapter 3.

4.2 LEDs

The CG 6100C board contains three types of LEDs: trunk, Hot Swap, and Ethernet.

4.2.1 Trunk LEDs

The CG 6100C board has one green indicator (LED) for each trunk on the end bracket of the board. The green LED indicates proper frame sync to the trunk: all required framing alignment has been found. This LED will be blinking if one or more of the following conditions exist:

• All ones alarm (AIS)

• Loss of frame

• Loss of signaling multiframe

• CRC errors (when the board is configured for HDB3)

• Red or yellow alarm
  Note: When the board is not configured, the trunk indicators blink in an alternating pattern (odd trunks/even trunks).

Figure 26 illustrates the trunk LEDs on the CG 6100C faceplate.

Figure 26. Trunk LEDs on the CG 6100C Faceplate

4.2.2 Hot Swap LED

The Hot Swap LED (blue) illuminates when it is safe to remove the CG 6100C board from the system. The LED illuminates under one of the following conditions:

• If the board is fully inserted when the backplane is powered-up, the blue LED momentarily flashes. This is a normal part of the initialization process.

• After opening the handles (during the extraction process), the LED illuminates to indicate that it is safe to remove the board. Do not remove the board until the LED illuminates. This occurs only if Hot Swap software is present.

• If the LED remains illuminated after insertion of a board and after you have closed the handles, the board failed to successfully perform its primary hardware initialization. While it is safe to remove the board, this condition indicates a problem.

The Hot Swap operation is defined in the CompactPCI Hot Swap Specification PICMG 2.1 R1.0.

4.2.3 Ethernet LEDs

The Ethernet LEDs (green) will not light. Ethernet is not currently supported.

4.3 Verifying That the Board is Installed Correctly

To verify that you have installed the board correctly:

1. Create a board keyword file to boot the CG 6100C board by copying or editing one of the sample board keyword files to match your specific configuration. Refer to Chapter 3 for more information about the configuration file. You may want to use the c61lc.cfg file which configures the board for line interface.

2. Run oammon to monitor the status of all boards.

3. Use the pciscan utility to determine the bus and slot number. Refer to the NMS OAM System User's Manual for more information about the pciscan utility.

4. Edit the system configuration file, oamsys.cfg, to reflect the board locations in your system.

5. Boot the board using a command such as:
   oamsys
   No trunk LEDs are illuminated if the NetworkInterface.T1E1[x].Type keyword is set NONE.

4.4 Verifying That the Board is Working Correctly

To verify your board is working:

1. Set the following keyword values in the board keyword file:

2. Clocking.HBus.ClockSource = OSC

3. Clocking.HBus.ClockMode = STANDALONE.

4. Boot the board using a command such as:
   oamsys

5. Run the digital trunk monitor utility, trunkmon.
   trunkmon monitors alarms and gathers performance statistics for T1 and E1 trunks. On a T1 trunk, an alarm state is indicated by the red, yellow, or blue alarm. On an E1 trunk, an alarm state is entered upon local or remote loss of frame, or excessive bit errors.
   If no T1/E1 trunk cables are connected to the CG 6100C board, trunkmon shows a loss of frame sync (Frame sync: No Frm) and an alarm state on all trunks. The green LEDs on the front panel should be blinking for all trunks. Refer to the NMS OAM System User's Manual for more information about trunkmon.

6. Connect a cross-over cable between any two trunks of the CG 6100C board. The Frame Sync status should immediately change to OK. The green LEDs for those trunks will light continuously after frame sync has been acquired. Both trunks will then leave the alarm state. trunkmon indicates NONE for the alarm status.

4.5 Demonstration Programs

The following demonstration programs are provided with Natural Access and may be used to verify that the CG 6100C board is operating correctly:

Program	Description
ctatest	Demonstrates Natural Access functions.
incta	Demonstrates handling inbound calls.
outcta	Demonstrates establishing outbound calls.
prt2prt	Demonstrates call transfer from an incoming line to an outgoing line and uses the Switching service to make connections and to send patterns.
vceplay	Demonstrates using the Voice Message service to play messages in voice files.
vcerec	Records one or more messages to a voice file.

Note: Executables for incta, outcta, and prt2prt are in the respective sub-directories under nms\ctaccess\demos.

Running these demonstration programs requires a connection to either a live T1/E1 trunk or a connection to T1/E1 test equipment which supports call generation and voice path testing. It is also possible to use the T1/E1 cross-over cable to loopback one trunk to another trunk. Calls placed on the first trunk can then be received on the other trunk.

To run these demonstration programs on the CG 6100C board, specify the
MVIP-95 stream and slot number of the local DSP resource on which to run the program.

For example, on a CG 6100C board configured as an E1 CAS board, the DSP resources on stream 64, timeslots 0..29 are connected to the first trunk. Timeslots 30..59 are connected to the second trunk, and so on. Assume that the board number is 0.

• To run ctatest on the first channel of the first E1 trunk, enter:

     ctatest -s0 -b 0
  
  

• To run ctatest on the first channel of the second E1 trunk, enter:

     ctatest -s30 -b 0