Administer > Configure Incidents > Configure Management Events > Management Event form > Configure basic settings for a management event incident

Configure basic settings for a management event incident

The Basics settings for a Management Event Incident specifies general information for an incident configuration, including the name, severity, and message.

In the Basics group of the Management Event Configuration form, verify that Enable is selected for each configuration you want to use.

To configure Basic settings for a Management Event incident:

Navigate to the Management Event Configuration form:

  1. From the workspace navigation panel, select the Configuration workspace.
  2. Expand the Incidents folder.
  3. Select Management Event Configurations.
  4. Do one of the following:

    1. To create an incident configuration, click the New icon, and continue.
    2. To edit an incident configuration, select a row, click the Open icon, and continue.
    3. To delete an incident configuration, select a row, and click the  Delete icon.
  5. Configure the required Basic settings (see the Basic Attributes table).
  6. Click  Save and Close to save your changes and return to the previous form. NNMi uses the SNMP Object ID to enable forwarding of Management Events as SNMP traps. NNMi automatically assigns a unique SNMP Object ID to all Management Events provided by NNMi.
Basic Attributes for Management Event Configuration
Task How
Specify the Incident Configuration Name (Management Events)

Use the Basics pane of the Management Event Configuration form. Specify a name that helps you to identify the configuration for subsequent use.

When providing the Name for an incident configuration, use the following guidelines:

Name


The name is used to identify the incident configuration and must be unique. Use a name that will help you to remember the purpose or kind of Management Event, Syslog Message or SNMP Trap for which you are configuring an incident. Name is also used to identify your Pairwise configurations.

Alpha-numeric and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted. No spaces are permitted.

SNMP Object ID 

The SNMP Object ID assigned by NNMi.

Note the following about the SNMP Object ID that appears in the Basics settings of the Management Event Configuration form:

  • The Management Event SNMP Object ID is used when sending Management Events to another application. For example, you might want to send NNMi Management Event to an event consolidator such as Operations Manager. The SNMP Object ID is used to uniquely identify the management event in the application receiving the event.
  • NNMi assigns a unique SNMP Object ID to each Management Event configuration it provides. If you choose to create a new Management Event configuration, NNMi assigns the following "generic" SNMP Object ID to these user-created configurations:

    .1.3.6.1.4.1.11.2.17.19.2.0.9999

  • For user-defined Management Events, a combination of the SNMP Object ID and the user-defined event name must be used to uniquely identify the Management Event in an application receiving the event.
  • If you choose to create a new Management Event configuration, NNMi automatically assigns the same "generic" SNMP Object ID to all new Management Event configurations.
Specify whether you want to enable this configuration. In the Basics group of the Management Event Configuration form, verify that Enable  is selected for each configuration you want to use.
Specify Category and Family Attribute Values for Organizing Your Incidents (Management Events)

Use the Basics pane of the Management Event Configuration form. You can organize your incidents using Category and Family.

When configuring incidents, NNMi provides the Category and Family attributes to help you organize your incidents.

Preconfigured Categories
The Category attribute helps you organize your incidents. Select the category that you want to be associated with this type of incident when it appears in an incident view. Each of the possible Category values is described in the following list:

  • Accounting: Used to indicate problems related to usage statistics and allocation of costs associated with the billing of time and services provided by devices. This category is not used by NNMi with default configurations, but it is available for incidents you define.
  • Application Status: Indicates there is a problem with the health of the NNMi software. Examples of these kinds of events include license expiration or that a certain NNMi process or service lost connection to the Process Status Manager.
  • Configuration: Indicates there is a problem with the configuration of a managed device. For example, there is a physical address mismatch.
  • Fault: Indicates a problem with the network, for example Node Down.
  • Performance: Indicates a Monitored Attribute value crossed a configured threshold. For example, Disk Space Utilization exceeds the configured threshold criteria for High Value = 90 percent .
  • Security: Indicates there is a problem related to authentication. For example, an SNMP authentication failure.
  • Status: Indicates some kind of status message. Examples of these kinds of incidents include "SNMP Link Up" or an "HSRP Group status Normal" message.

You can add your own Category entries to NNMi.

You can use Family attribute values to further categorize the types of incidents that might be generated. Each of the possible values are described in the following list:

  • Address: Indicates the incident is related to an address problem.
  • Aggregated Port: Indicates the incident is related to a Link Aggregation or Split Link Aggregation problem.
  • BGP: Indicates the incident is related to a problem with BGP (Border Gateway Protocol). This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • Board: Indicates the incident is related to a board problem. This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • Card: Indicates the incident is related to a card problem. This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • Chassis: Indicates the incident is related to a chassis problem.
  • Component Health: Indicates the incident is related to Node Sensor or Physical Sensor data collected by NNMi.
  • Connection: Indicates the incident is related to a problem with one or more connections.
  • Correlation: Indicates the incident has additional incidents correlated beneath it. These incidents are associated with a duplicate count so that you can determine the number of correlated incidents associated with it.
  • Custom Poller: Indicates the incident is related to the NNMi Custom Poller feature.
  • HSRP: (NNMi Advanced) Indicates the incident is related to a problem with Hot Standby Router Protocol (HSRP).
  • Interface: Indicates the incident is related to a problem with one or more interfaces.
  • IP Subnet: Indicates the incident is related to a problem with the IP Subnet.
  • License: Indicates the incident is related to a licensing problem.
  • NNMi Health: Indicates the incident is related to NNMi health.
  • Node: Indicates the incident is related to a node problem.
  • OSPF: Indicates the incident is related to an OSPF problem. This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • RMON: Indicates the incident is related to a Remote Monitor (IETF standard, RFC 1757) problem. This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • RRP: (NNMi Advanced) Indicates the incident is related to a problem with a Router Redundancy Protocol configuration.
  • STP: Indicates the incident is related to Spanning-Tree Protocol problem. This family is not used by NNMi with default configurations, but it is available for incidents you define.
  • Syslog: NNMi does not use this Family with default configurations. It is available for incidents you define.
  • System and Applications: Indicates the incident is related to a problem with a system or application in your environment that is configured to send traps to the NNMi server, for example your corporate database application.
  • Trap Analysis: Requires Network Node Manager iSPI Network Engineering Toolset Software (NNM iSPI NET).

    Indicates the incident is related to an SNMP trap storm.

  • VLAN:  Indicates the incident is related to a problem with a virtual local area network.
  • VRRP: (NNMi Advanced) Indicates the incident is related to a problem with Virtual Router Redundancy Protocol (VRRP).

You can add your own Family entries to NNMi.

Specify the Incident Severity (Management Events)

Use the Basics pane of the Management Event Configuration form. Possible Severity values include: Normal, Warning, Minor, Major, and Critical.

The incident severity represents the seriousness calculated for the incident. Use the severity attribute to specify the severity that should be assigned to the incident you are configuring. Possible values are described in the following table.

Incident Severity Values
Attribute Description
Normal Indicates there are no known problems related to the associated object. This severity is meant to be informational. Generally, no action is needed for these incidents.
Warning Indicates there might be a problem related to the associated object.
Minor Indicates NNMi has detected problems related to the associated object that require further investigation.
Major Indicates NNMi has detected problems related to the associated object to be resolved before they become critical.
Critical Indicates NNMi has detected problems related to the associated object that require immediate attention.
Specify Your Incident Message Format (Management Events)

Use the Basics pane of the Management Event Configuration form. The message format determines the message to be displayed for the incident.

When configuring an incident, specify the information you want NNMi to include in the incident's Message attribute value. You can use any combination of valid parameter strings and Custom Incident attributes to configure the Message.

Note The incident Message limit is 1024 characters. If the returned values exceed this limit, NNMi truncates the value starting from the end of the returned text string.

Specify a Description for Your Incident Configuration (Management Events)

Use the Basics pane of the Management Event Configuration form. Provide a meaningful description.

NNMi provides the Description attribute to help you further identify the current incident configuration.

Description

Use the description field to provide additional information that you would like to store about the current incident configuration. This description applies only to the configuration entry.

Type a maximum of 1024 characters. Alpha-numeric, spaces, and special characters (~ ! @ # $ % ^ & * ( ) _+ -) are permitted.

Specify an Author for Your Incident Configuration (Management Events)

Use the Basics pane of the Management Event Configuration form to indicate who created or last modified the event.

If the Author attribute value is Network Node Manager, any changes are at risk of being overwritten in the future.

  • Click  Lookup and select  Show Analysis to display details about the currently selected Author.
  • Click  Quick Find to access the list of existing Author values.
  • Click  New to create an Author value.

Related topics