Default event maps
Network Manager provides a default set of event maps. Use this information to understand which default event maps are available and what each event map does, and to understand how legacy event maps delegate to current event maps.
Default event maps
The following table describes the default event maps.| Event map | Stitcher called by event map | Event map description |
|---|---|---|
| ChassisFailure | LookupMainNode |
Handles events where the Expected input fields:
|
| EMSNonPollingEvent | LookupEMSEntity | Handles polling events from element management systems
(EMSs). Expected input fields:
|
| EMSPollingEvent | LookupEMSEntity | Handles non-polling events from element management systems
(EMSs). Expected input fields:
|
| EntityFailure | LookupIp | Handles events where the LocalNodeAlias is sufficient
to specify the entity, or if no further data is available. Expected input field:
LocalNodeAlias, where this field contains one of the following:
|
| EntityMibTrap | LookupEntPhysEntry | Handles traps from the ENTITY MIB. Expected input fields:
|
| EntityStateChange | LookupEntityId | Handles events raised by the Topology manager, ncp_model. No plug-ins
currently register interest in this event map. Nevertheless the map allows for population of
standard fields. The events raised by ncp_model are the following:
Expected input field: |
| genericip-event | LookupMainNode | Processes events that do not match any other event map. Note: This
event map is intended as a catch-all. Plug-ins should not register interest in this eventMap.
Instead, events of interest should be passed to the EntityFailure event map.
Expected input field: LocalNodeAlias, where this field contains one of the
following:
|
| ItncmResourceEvent | LookupMainNode | Used to handle events raised by Netcool Configuration Manager. This event map
maps the entity identifier (entityId) in Network Manager to its corresponding
Netcool Configuration Manager
credentials.Expected input fields: NmosEntityId. If this field is not available,
then uses as input: LocalNodeAlias, where this field contains one of the
following:
|
| ItnmHealthChk | No related stitcher | Used by the Failover plug-in, to process Network Manager health check
events. Expected input field: |
| ItnmLinkDownIfIndex | LookupIfEntry | Expects an interface event to be identified by the ifIndex if the
interface NmosEntityId is not set.Expected input fields:
|
| ItnmMonitorEventNoRca | LookupEntityId | Used to handle events raised by the Network Manager Polling engine,
ncp_poller, for which root-cause analysis should not be performed. Expected input fields:
|
| ItnmStatus | No related stitcher | Catch-all event map for Network Manager status information events that are not explicitly handled by any other event map, for example, ItnmHealthCheck. No action is taken for these events. |
| LinkDownIfDescr | LookupIfEntry | Expects an interface event to be identified by the
ifDescr value.Expected input fields:
|
| LinkDownIfIndex | LookupIfEntry | Expects an interface event to be identified by the
ifIndex value.Expected input fields:
|
| LinkDownIfName | LookupIfEntry | Expects an interface event to be identified by the
ifName value.Expected input fields:
|
| NbrFail | LookupNbrFailure | Handles OSPF, LDP and BGP adjacency change events. In addition to
performing the requisite lookup, the LookupNbrFailure stitcher also adds a
RemoteNodeEntityId value, used by the RCA plug-in.Expected input fields:
|
| OspfIfState | LookupOspfIfEntry | Handles OSPF interface events. Expected input fields:
|
| PollFailure | LookupIp | Covers events raised for a specific IP address, such as Tivoli Netcool/OMNIbus ping probe
events. Expected input fields: |
| PrecisionMonitorEvent | LookupEntityId | Used to handle events raised by the ITNM poller, for which root-cause
analysis must be performed. Expected input fields: |
| Reconfiguration | LookupMainNode |
Events assigned to this event map are used by the Disco plug-in to rediscover the device associated with them. By default, reboot events (events with event ID of NmosSnmpReboot) are assigned to this event map, based on the assumption that following reconfiguration of a device (for example, addition of a new card), the device will be rebooted, and then needs to be immediately discovered, so that the changes in configuration can be rapidly stored in the topology model. Expected input field:
LocalNodeAlias, where this field contains one of
the following:
|
| rttMonNotifications | LookupProbeSourceEntity |
Expected input fields:
|
Legacy event maps
The following table lists the legacy event maps and, for each legacy event map, specifies which 3.9 event map is delegated to.| Legacy event map | Handled by the following 3.9 event map |
|---|---|
| EntityIfDescr | LinkDownIfDescr |
| NbrFailIfDescr | NbrFail |
| NcpHealthChk | ItnmHealthChk |
| OSPFIfStateChange | OspfIfState |
| OSPFIfStateChangeIP | OspfIfState |
How legacy event maps delegate to 3.9 event maps
This example explains how the NbrFailIfDescr legacy event map delegates to the NbrFail 3.9 event map.- An event is received that has an eventId listed in the config.precedence table, mapping to the NbrFailIfDescr eventMap.
- The NbrFailIfDescr eventMap delegates to the NbrFail eventMap, using the HandledBy field.
- The event is treated exactly as if it had been mapped to the NbrFail eventMap in the first
place, that is it will be handled as follows:
- The LookupNbrFailure stitcher is called. This stitcher is referenced in the
Stitcherfield relevant to the NbrFail event map entry in the config.eventMaps table. - The fields of the NbrFail eventMap (not the NbrFailIfDescr to which the event was originally mapped) are appended to the event before passing it to plug-ins.
- Plugins that have registered interest in the NbrFail eventMap (not the NbrFailIfDescr to which the event was originally mapped) receive the event.
- The LookupNbrFailure stitcher is called. This stitcher is referenced in the
Adds the main node and probe ID to incoming RTTMON traps.