6.1 Concepts for incidents
NNMi collects network status information from the following sources:
-
The NNMi Causal Engine, which analyzes the health of your network and provides an ongoing health status reading for each device. The Causal Engine also extensively evaluates and determines the root cause of network problems whenever possible.
-
SNMP traps from network devices. The NNMi Causal Engine uses this information as symptoms during its analysis.
NNMi converts this network status information into incidents that provide useful information for managing the network. NNMi provides many default incident correlations that reduce the number of incidents for network operators to consider.
You can customize the default incident correlations and create new incident correlations to match the network management needs of your environment.
The incident configurations on the NNMi console define the incident types that NNMi can create. If no incident configuration matches a received SNMP trap, that information is discarded. NNMi always discards an incoming trap when the management mode of the source object is set to Not Managed or Out of Service in the NNMi database or the device is not monitored by fault polling.
nnmtrapconfig.ovpl -dumpBlockList outputs information about the current incident configuration, including SNMP traps that were not passed into the incident pipeline because of nonexistent or disabled incident configurations.
Additionally, NNMi discards SNMP traps from network devices that are not in the NNMi topology. For details about changing this default behavior, see Handle Unresolved Incoming Traps in NNMi Help.
For details, see the following:
-
About the Event Pipeline in NNMi Help
-
The NNMi Causal Engine and Incidents in NNMi Help