The OAM Database MIB presents an SNMP front end to the contents of the OAM API database on a system. Within this database, NMS OAM software maintains tables of configuration data for hardware and software components in the system. Each table of configuration data constitutes a managed object: the logical representation of the component to the system. Using the OAM Database MIB, you can query, add, modify, or delete information for managed objects in much the same way as NMS OAM does.
For detailed information about NMS OAM, refer to the NMS OAM System User's Manual and to the NMS OAM Service Developer's Reference Manual.
NMS OAM manages the following components:
|
Component |
Description |
|
A separate set of configuration information is kept for each AG, CG, CX, and QX board in the system. |
|
|
NMS OAM keeps configuration information for its Supervisor process that oversees all other NMS OAM components. |
|
|
NMS OAM communicates with boards using software extensions called board plug-ins. There is one plug-in per board family. NMS OAM maintains a separate set of configuration information for each plug-in. |
|
|
Extended management components (EMCs) are software modules that add functionality to the OAM API. A separate set of configuration data is kept for each EMC. Currently, two EMCs are supplied with NMS OAM:
|
For information about the Hot Swap EMC and the Clock Management EMC, refer to the NMS OAM System User's Manual.
The following illustration shows the relationship between the components in a system, their representation as managed objects within NMS OAM, and the relationship of managed objects to data within the OAM API database: