4.1 Introduction

4.1.1 Trunk LEDs

4.1.2 Hot Swap LED

4.1.3 Ethernet LEDs

4.2 Verifying the Installation

4.3 Verifying Trunk Connections

4.4 Demonstration Programs

4.1 Introduction

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

The CG 6000C board face plate provides two sets of indicator lights (LEDs) that display the status of the board's network interfaces. One set shows trunk interface status information and the other shows Ethernet interface status information.

Figure 23. CG 6000C Trunk LEDs and Ethernet LEDs

4.1.1 Trunk LEDs

The CG 6000C board provides three (red, yellow, green) LEDs on its face plate to display the status information about each T1 or E1 trunk (as shown in Figure 23). CG 6000C trunk LEDs provide the following indications:

LED	Description
Red	Indicates loss of frame, loss of signal, or bit error rate.
Yellow	Indicates remote loss of frame, or remote loss of signaling multiframe.
Green	Indicates proper frame sync to the trunk: all required framing alignment has been found. This LED will be off 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 ESF)

Note: When the board is not configured, all trunk indicators are ON.

4.1.2 Hot Swap LED

The CG 6000C board provides a Hot Swap LED to indicate whether or not you can remove the board from the system:

LED

Description

Blue

Illuminated when it is safe to remove the CG 6000C 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 condition occurs only if Hot Swap software is implemented on the system. · 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.1.3 Ethernet LEDs

The CG 6000C board provides three LEDs to provide status information about each of the CG 6000C board's Ethernet interfaces (as shown in Figure 23).
CG 6000C trunk LEDs provide the following indications:

LED	Description
LINK	Indicates the status of the Ethernet link. This LED will be On if the respective Ethernet link is reliable.
100Mb	Indicates the data rate of the Ethernet link. When the LED is On, the data rate is 100 Mb. When the LED is Off, the data rate is 10 MB. This LED is used only when a reliable Ethernet connection has been established (that is, the LINK LED is On).
ACTIVITY	Indicates the transmitting/receiving activity on the respective Ethernet link. When activity is present on the Ethernet link, the LED will flicker.

4.2 Verifying the Installation

To verify that you have installed the board correctly:

1. Create a board keyword file to boot the CG 6000C 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 c6wnk.cfg file that configures the board for the Wink Start protocol.

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

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

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

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

4.3 Verifying Trunk Connections

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 LEDs. On an E1 trunk, the board indicates an alarm state when it detects a local or remote loss of frame or excessive bit errors.
   If no T1/E1 trunk cables are connected to the CG 6000C board, trunkmon shows a loss of frame sync (Frame sync: No Frm) and an alarm state on all trunks. The red alarm LED on the front panel lights up 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 6000C board. The Frame Sync status immediately changes to OK and the green LEDs for those trunks light up. The remote alarm (yellow) LEDs light up to show that the trunk is indicating an alarm state to the other side. About 15 seconds (for T1 trunks, immediately for E1 trunks) after frame sync has been acquired, both trunks leave the alarm state. trunkmon indicates NONE for the alarm status and the red and yellow alarm LEDs go out. The frame sync (green) LEDs remain lit.

4.4 Demonstration Programs

You can use the following demonstration programs, which provided with Natural Access software, to verify that the CG 6000C 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 that 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 6000C 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 6000C board configured as a T1 board, the DSP resources on stream 16, timeslots 0..23 are connected to the first trunk. Timeslots 24..47 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 T1 trunk, enter:

     ctatest -s0 -b 0
  
  

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

     ctatest -s24 -b 0