3.1 Configuring and Verifying the CG System

3.1.1 Customizing the OAM Configuration Files

3.1.2 Modifying Sample System Configuration Files

3.1.3 Modifying Sample CG Board Keywords Files

3.1.4 Configuring T1 or E1 Line Interfaces

3.1.5 CG Board HDLC Instances

3.1.6 Sample HDLC Configurations

GR-303 (T1) Configuration

V5.2 (E1) Configuration

3.1 Configuring and Verifying the CG System

Platform Support for DLCP provides a set of software libraries that enable applications to access on board devices (such as HDLC controllers and framers) necessary to support the upper layers of a GR-303 or V5.2 protocol. Once you have installed Platform Support for DLCP software, you can perform the following steps to configure it:

Step	Description	For details, refer to...
1. Create or edit an NMS OAM system configuration file and board keyword files.	Specify system and board keyword settings that optimize the CG hardware configuration for the DLCP environment.	Section 3.1.1
2. Run the oamsys utility with the edited NMS OAM configuration files.	Use oamsys to update the NMS OAM configuration database and configure the CG hardware on the system.	NMS OAM System User's Manual
3. Run one of the demonstration programs nms303tool or nmsv5tool.	Compile and run one of the demonstration programs provided with Platform support for DLCP. These programs verify that the Platform Support for DLCP software can initialize a Layer 1 for GR-303 or V5.2 protocols, set up provisioning, start interfaces, perform transmit and receive HDLC operations, and report trunk alarms and performance statistics	Section 4.2.3, Section 4.3.3, and Chapter 7

3.1.1 Customizing the OAM Configuration Files

When you install and boot the CG board with the sample board keyword files provided on the Natural Access CD, it is ready for general-purpose use. To configure the board to work with Platform Support for DLCP product, reboot the board with oamsys using one of the following Platform Support for DLCP sample board keyword files:

Board Keyword File	Description
cg6gr303.cfg	Configuration file for T1 interfaces (used on GR-303 systems).
cg6v5.cfg	Configuration file for E1 interfaces (used in V5.2 systems).

The sample board keyword files specify the following CG board settings:

• Line interface type (T1/E1)

• Board clocking configuration

• On-board resource management

• Downloadable software modules

Edit a sample board keyword file to specify appropriate configuration information for your system. For detailed information about customizing CG board keyword files refer to Chapter 4 or the board's hardware documentation.

The NMS OAM system configuration file references all OAM board keyword files for boards on the system as shown in the following diagram:

Figure 5. NMS OAM System Configuration and Board Keyword Files

3.1.2 Modifying Sample System Configuration Files

When necessary, you can modify the CG board bus and slot number to include multiple boards in a system. Each board entry in the system configuration file must contain the following keywords:

Keyword	Description
Product	Board product type
Number	Logical board number
Bus	PCI Bus number of the CG board
Slot	PCI Slot number of the CG board

You can obtain CG board bus and slot numbers by running the pciscan utility. For more information about pciscan, refer to the NMS OAM Service System Users's Manual.

Make sure that the system configuration file references all the board keyword files associated with boards in your system. After you customize the individual board keyword files, you can run the oamsys utility to configure the boards as specified in the configuration files. When you run the oamsys, it creates NMS OAM database records based on the contents of the specified system configuration file and board keyword files. It then directs NMS OAM to start the boards and configure them according to the specified parameters.

3.1.3 Modifying Sample CG Board Keywords Files

When you install CG boards, you use the NMS OAM service to specify configuration information for the system and for individual boards within the system. NMS OAM includes the oamsys utility, which transfers software modules specified in configuration files to the boards in the system. Use oamsys to initialize your boards based on the information in a system configuration file and one or more board keyword files.

After you install CG or boards and the software required by Platform Support for DLCP, you may need to change some of the sample board keyword parameters as appropriate for your system. This section describes how to modify board keywords associated with Platform Support for DLCP, so that they meet your system requirements.

3.1.4 Configuring T1 or E1 Line Interfaces

To configure the T1 (for GR-303) or E1 (for V5) interfaces, ensure that the following keywords appear in the board keyword configuration file:

OAM Keyword	GR-303 (T1) Values	V5.2 (E1) Values	Description
NetworkInterface.T1E1[x]. Type	T1	E1	Specifies the trunk type for each trunk on the board.
NetworkInterface.T1E1[x]. Impedance	DSX1	G703_120_OHM | G703_75_OHM	Specifies the type of cable connecting a CG board to the telephone network.
NetworkInterface.T1E1[x]. LineCode	AMI | B8ZS | AMI_ZCS | AMI_BELL |AMI_DDS| AMI_GTE	HDB3 | AMI	Specifies the ones density maintenance method used on the trunk line to maintain a clear channel transmission.
NetworkInterface.T1E1[x]. FrameType	ESF	CEPT	Specifies the T1 or E1 trunk framing format for the current board(s) or current trunk(s).
NetworkInterface.T1E1[x]. SignalingType	CAS	RAW	Specifies how voice and signaling information is routed to and from the E1 or T1 trunk and DSP resources.

For all keywords in the table, x is a 0-based trunk number or range of trunk numbers. For CG 6000 or CG 6000C boards, x must be less than or equal to three.

Note: When setting the NetworkInterface.T1E1[x].Type keyword, you must specify all trunks as either T1 trunks or E1 trunks. Do not specify more than one trunk type.

For more information about configuring T1 and E1 trunks, refer to Appendix C.

3.1.5 CG Board HDLC Instances

Each CG board T1 or E1 trunk is associated with a single framer instance. On
CG 6000 and CG 6000C boards each framer instance is hard-wired to three HDLC instances.

Applications can use functions from the NMS GR303 or NMS V5 libraries to dynamically configure and operate these HDLC instances once the board environment is booted. The HDLC instances on CG 6000 and CG 6000C boards are organized as shown in the following diagram:

Figure 6. HDLC Controllers and Framer Locations on CG 6000 Boards

3.1.6 Sample HDLC Configurations

The examples that follow show sample trunk configurations for CG 6000 and
CG 6000C boards.

GR-303 (T1) Configuration

The following example shows a GR-303 configuration with four T1 links:

T1
----
NetworkInterface.T1E1[0..3].Type      = T1
NetworkInterface.T1E1[0..3].Impedance = DSX1         
NetworkInterface.T1E1[0..3].LineCode  = B8ZS   [other values possible
NetworkInterface.T1E1[0..3].FrameType = ESF    [other values possible]
NetworkInterface.T1E1[0..3].FrameType = CAS
DSP[0..31].cfg.XLaw                   = MU_LAW
DSPStream.VoiceIdleCode[0..3]         = 0x7F
DSPStream.SignalIdleCode[0..3]        = 0x00   
DLMFiles[x]                           = cg6kdlcp

V5.2 (E1) Configuration

The following example shows a V5 configuration with four E1 links:

E1
----
NetworkInterface.T1E1[0..3].Type          = E1
NetworkInterface.T1E1[0..3].Impedance     = G703_120_OHM [other values 
                                            possible]
NetworkInterface.T1E1[0..3].LineCode      = HDB3[other values possible]
NetworkInterface.T1E1[0..3].FrameType     = CEPT       
NetworkInterface.T1E1[0..3].SignalingType = RAW [other values possible]
DSP[0..31].cfg.XLaw                       = A_LAW
DSPStream.VoiceIdleCode[0..3]             = 0xDS
DSPStream.SignalIdleCode[0..3]            = 0x0D
DLMFiles[x]                               = cg6kdlcp

For more information about customizing Platform Support for DLCP software, refer to Chapter 4. For more information about NMS OAM, refer to the NMS OAM System User's Manual. Refer to the your hardware installation and developer's manual for more information about CG board keyword files.