Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Network Node Manager i Software10.30

Administer > Configure Incidents > Configure Trap Logging > Node Group Logging Configuration Form

Node Group Logging Configuration Form

[This is the context-sensitive help for the Node Group Trap Configuration form.]

NNMi enables you override the Trap Logging Configuration for nodes in a specified Node Group.

To configure Node Group Trap Configuration:

Navigate to the Incidents folder:
1. From the workspace navigation pane, select the Configuration workspace.
2. Expand the Incidents folder.
Expand the Trap Server folder.
Select Trap Logging Configuration.
Navigate to the Node Group Logging Configuration tab.
Do one of the following:
1. To add a configuration, click the New icon, and continue.
2. To edit a configuration, double-click the row representing the configuration you want to edit, and continue.
3. To delete a configuration, select a row, and click the Delete icon.
Make your Basic configuration choices (see table).
Make your Log Configuration choices (see table).
Click Save and Close to save your changes and return to the previous form.

Note See Manage Incoming SNMP Traps for information about the criteria NNMi uses to determine when to receive or discard traps.

Node Group Logging Basic Configuration
Name	Description
Node Group	Specifies the Node Group that contains the nodes for which you want to configure trap logging information. To specify a Node Group, click the Lookup icon, and do one of the following: To display a list of possible Node Groups, select Quick Find. In the Quick Find dialog, select the Incident of interest. To create a Node Group, select New.
Ordering	Ordering specifies the order in which the configuration should be considered for nodes that appear in multiple Node Groups and therefore might have conflicting Node Group Logging Configurations. NNMi uses the Node Group Logging Configuration that has the lowest Ordering value. For example, Ordering is used in the following scenario: A node is in both the Routers Node Group and the Switches Node Group. Node Group Logging Configuration is specified for both Node Groups. The Ordering value for the Routers Node Group is 3. The Ordering value for the Switches Node Group is 5 In this example, for any node that appears in both the Routers Node Group and the Switches Node Groups. NNMi uses the Node Group Logging Configuration specified for the Routers Node Group, which has the lowest Ordering number.
Logging	If the Enabled options is selected, NNMi logs this SNMP Trap to the `trap.log` and `trap.csv` log files for the nodes in the specified Node Group. If the Disabled option is selected, NNMi does not log the specified SNMP Trap configuration to the `trap.log` and `trap.csv` log files for nodes in the specified Node Group. If the Inherited option is selected, NNMi uses the Logging value from the Logging Configuration form. For example, if Logging is Disabled in the Logging Configuration for this trap, then logging is disabled for the nodes in the specified Node Group. This option is available only for Node Group Logging Configuration. See Trap Logging Configuration Formfor more information.

Name Description

Log Message Format

Specify the information you want NNMi to include in the SNMP Trap's Message attribute value. You can use any combination of valid parameter strings and Custom Incident attributes to configure the Message.

For more information, see:

Valid Parameters for Trap Logging Messages

Include varbinds in Your Log Message Format

Severity

The Severity represents the seriousness calculated for the SNMP trap. Use the Severity attribute to specify the Severity that should be assigned to the SNMP trap when it appears in the trap.log and trap.csv log files.

Note If different from the associated SNMP Trap Incident Configuration, the Severity value overrides the SNMP Trap Incident Configuration Severity value.

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.

See "Monitor Incidents for Problems" for more information about these severity values.

Category

The Category attribute helps you organize your SNMP Traps. Select the category that you want to be associated with this SNMP Trap when it appears in the trap.log and trap.csv log files.

Note If different from the associated SNMP Trap Incident Configuration, the Category value overrides the SNMP Trap Incident Configuration Severity value.

Each of the possible Category values is described in the following table.

Incident Categories Provided by NNMi
Category	Description
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 (see Extend a Licensed Capacity) or that a certain NNMi process or service lost connection to the Process Status Manager (see Stop or Start an NNMi Process and Stop or Start NNMi Services).
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.

Family

You can use Family values to further categorize the types of SNMP Traps that might be generated. Select the category that you want to be associated with this SNMP Trap when it appears in the trap.log and trap.csv log files.

Note If different from the associated SNMP Trap Incident Configuration, the Family value overrides the SNMP Trap Incident Configuration Severity value.

Each of the possible Family values are described in the following table.

Incident Family Attribute Values Provided by NNMi
Family	Description
Address	Indicates the incident is related to an address problem.
Aggregated Port	Indicates the incident is related to a Split 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.
RAMS	Indicates the incident is related to a Router Analytics Management System problem.
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).

Author

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.

Send Help Center feedback