Download NMS OAM System User`s Manual

NMS OAM System User's Manual
Overview of NMS OAM
The following illustration shows the relationships between NMS OAM components:
oammon
oaminfo
oamsys
oamcfg
Management host
Resource host
NMS OAM
service
Custom
application
NMS OAM
Configuration
database
To use any NMS OAM utility on any host, the Natural Access Server (ctdaemon) must
be running on the target host and have the NMS OAM Supervisor started within it.
Refer to Starting the Natural Access Server on page 34 for more information.
oamsys
To configure and start managed components on a host, use the oamsys utility. This
utility creates records for components in the NMS OAM database on a resource host
based on system configuration files you supply. It then attempts to start all boards in
the database.
Configuration parameter values for each managed component are listed in the
system configuration file. If the component is a board, this information includes the
board's ID information.
oamsys completely renews the database each time it runs and restarts all boards.
Any parameters not listed in the configuration file are reset to their default settings.
Thus oamsys makes it easy to track the configuration of an entire host.
Note: If you are migrating to NMS OAM, utilities are available to assist in the
transition from agmon to NMS OAM. Refer to Summary of changes on page 121 for
more information.
To perform its tasks, the oamsys utility makes multiple calls to the oamcfg utility.
Use oamsys to set up both local and remote configurations. Refer to Using oamsys
on page 55 for more information.
NMS Communications
11