# Starting, stopping, and testing boards

This topic provides information about performing the following tasks with oamcfg:

- Starting boards

- Stopping boards

- Testing boards

## Starting boards

Once a board is properly configured and is physically installed in the system, use the -s option to start the board:

oamcfg -s -n myboard

If no board is specified, oamcfg attempts to start all boards in the NMS OAM database.

By default, oamcfg waits after attempting to start the specified boards until all board start attempts succeed or fail, reporting the results to stdout. To avoid this, use the -i option:

oamcfg -s -i

If the -i option is used, results are still available. The results come asynchronously encapsulated in NMS OAM events, which oammon can receive and display.

## Stopping boards

To stop a board, use the -p option:

oamcfg -p -n myboard

If no board is specified, oamcfg attempts to stop all boards in the NMS OAM database.

Note: The specified board stops immediately, interrupting any ongoing process. To avoid problems, make sure a board is not performing any operations before stopping it.

By default, oamcfg waits after attempting to stop the board until all board stop attempts succeed or fail, reporting the results to stdout. To avoid this, use the -i option:

oamcfg -p -i

If the -i option is used, results are still available. The results come asynchronously encapsulated in NMS OAM events, which oammon can receive and display.

## Testing boards

To test a board, use the -t testopts option:

oamcfg -t 0x80000301 -n myboard

testopts is a bit mask indicating how the test is performed. If no board is specified, oamcfg attempts to start testing on all boards in the NMS OAM database. Testing is started on the boards in numerical order (of board numbers).

Note: Currently, only CG boards support testing. Testing can interrupt current board activities. For this reason, do not use a board for any other operations during testing.

After attempting to start the board tests, oamcfg waits by default until all board test start attempts succeed or fail, reporting results to stdout and oammon. To avoid this wait, use the -i option:

oamcfg -n myboard -t 0x80000301 -i

If the -i option is used, results are still available. The results come asynchronously encapsulated in NMS OAM events, which oammon can receive and display.