NMS OAM events are generated by:
The NMS OAM Supervisor, in response to an NMS OAM asynchronous function (such as oamStartBoard, oamStopBoard, or oamTestBoard), or when lower-level events or errors occur.
The Hot Swap EMC, when Hot Swap state changes or other events or errors occur.
The Clock Management EMC, when events or errors occur.
Board plug-ins, when events or errors occur.
Other registered applications, using oamAlertNotify.
To receive events from the NMS OAM service and from installed EMCs such as Hot Swap and Clock Management, a client application must register with the NMS OAM service using oamAlertRegister. See Receiving NMS OAM alert notifications.
NMS OAM events are encapsulated within the standard CTA event structure. In NMS OAM events, the CTA event buffer field points to an OAM_MSG structure that contains more information about the event. After processing NMS OAM events, applications must free the Natural Access event buffers as described in Event buffer management.