# System configuration file creator: oamgen

#### Name

oamgen

#### Purpose

Scans a chassis for boards and creates a system configuration file describing the board setup.

Note: The system configuration file created by oamgen may not be appropriate for your configuration. You may need to make further modifications to the file before running oamsys to configure your boards based on the file.

#### Usage

oamgen

This utility has no command-line options.

#### Description

Use oamgen to create a system configuration file describing the configuration of the boards in a chassis. oamgen creates a file called sample.cfg, located in the directory from which oamgen was invoked.

Note: For oamgen to operate, ctdaemon must be running. To learn how to start ctdaemon, refer to Starting the Natural Access Server.

As oamgen locates each board, it displays the product name and PCI bus:slot location of the board. For example:

NMS OAM configuration file generator
...Inserting board AG_4040C_E1 (2:9)
...Inserting board CG_6000C_Quad (2:10)
...Inserting board CG_6100C (2:11)
...Inserting board AG_4040C_E1 (2:13)
A sample OAM configuration file sample.cfg has been generated.
To boot the NMS boards in the chassis, use the command:
oamsys -f sample.cfg

In the system configuration file, oamgen assigns a board name and number to each board. Boards are numbered in the order in which oamgen discovers them in the system starting with board 0. The board name for each board is N ame x, where x is the board number, for example, Name0.

oamgen also assigns each board a keyword file, based on the board's product type. Each keyword file is one of the sample keyword files installed for the boards in the \nms\oam\cfg directory (opt/nms/oam/cfg under UNIX). To learn what sample board keyword files are installed for your board types, refer to the board documentation.

When oamgen is complete, you can immediately run oamsys to configure and start the boards in the system based on sample.cfg. Alternatively, you can modify sample.cfg to suit your configuration before running oamsys. For more information about system configuration files, refer to Creating a system configuration file. For more information about oamsys, refer to Using oamsys.

If you have a chassis with an unusual PCI bus topology (for example, bus number 171 directly follows bus number 0), oamgen functions more slowly. To speed up operation, create a text file specifying PCI bus numbers to search. Refer to Specifying PCI bus numbers for board search functions for more information.

Note: Wink start protocol keyword files are installed on your system only if one of the countries you chose during software installation is the United States. If the sample.cfg file output by oamgen calls for a wink start protocol keyword file, modify sample.cfg or install the wink start protocol keyword files before running oamsys.

The following example is a typical sample.cfg file generated by oamgen:

#---------------------------------------------------------
# sample.cfg
#
# Sample OAM configuration file generated by oamgen
# based on the NMS boards found in this chassis.
#
# To boot the NMS boards in this chassis, use the command:
# oamsys -f sample.cfg
#
# You may need to modify the keyword configuration files
# on the "File = XXXX.cfg" lines to suit your needs.
#---------------------------------------------------------
[Name0]
Product = AG_4040C_E1
Number = 0
Bus = 2
Slot = 9
File = agpi4000.cfg # AG 4040C E1, Wink-start protocol
[Name1]
Product = CG_6000C_Quad
Number = 1
Bus = 2
Slot = 10
File = c6nocc.cfg # CG 6000C, T1, No call control
[Name2]
Product = CG_6100C
Number = 2
Bus = 2
Slot = 11
File = c61enocc.cfg # CG 6100C, E1, No call control
[Name3]
Product = AG_4040C_E1
Number = 3
Bus = 2
Slot = 12
File = agpi4000.cfg # AG 4040C E1, Wink-start protocol