For information about each SNMP Traps tab: 
See Also
For information about each Actions tab: See Also
You can configure actions to automatically run at any point in the incident lifecycle. For example, you might want to configure an action to occur when an incident of the type you are configuring is generated (Registered). When an incident is generated, you might want to automatically open a trouble ticket or send email or page your network operator. After the incident is Closed, you might want to automatically close the trouble ticket.
Note Your actions will not be executed until you enable the Actions configuration by either clicking Enable 
on the Actions tab or using the Actions → Enable Configuration option.
If the NNMi management server is running on a Windows operating system, NNMi runs each action that you configure using the Local System account. If the NNMi management server is running on a Linux operating system, NNMi runs each action that you configure using the bin user name.
You can also configure incident actions based on either of the following:
- The Source Node's participation in a Node Group. See Configure Incident Actions for a Node Group (SNMP Trap Incident) for more information.
- The Source Object's participation in an Interface Group. See Configure Incident Actions for an Interface Group (SNMP Trap Incident) for more information.
You can configure actions for incidents generated from SNMP traps, Syslog Messages, and the NNMi management events. Any time an incident configuration changes, the action directory is rescanned and any executable or script files (for example, Jython) are reloaded to the NNMi database. See Lifecycle Transition Action Form (SNMP Trap Incidents) for more information about the actions directory.
Tip Copy any required executable or script files to the NNMi actions directory before you configure an incident action. New or updated actions are loaded into NNMi only when an incident configuration is updated or created. See Lifecycle Transition Action Form (SNMP Trap Incidents) for the location of the NNMi action directory.
When the defined Incident Action runs, output is logged to the incidentActions.*.*.log file. To view the contents of the Actions log, use the Tools → Incident Actions Log menu option.
See Verify that NNMi Services are Running for more information about log files and where they are located.
NNMi sets the default values described in the following table.
See the "Maintaining NNMi" chapter in the Network Node Manager i Software Deployment Reference for information about changing the default values for Action Server Properties.
| Property | Description | Value |
|---|---|---|
| numProcess | Number of actions that can be run at one time. | 10 |
| numJythonThreads | Number of threads the action server uses to run Jython scripts | 10 |
| userName | User name under which the action server runs. | bin |
To configure an automatic action for an incident:
-
Navigate to the Actions tab.
- From the workspace navigation panel, select the Configuration workspace.
- Expand the Incidents folder.
- Select SNMP Trap Configurations.
-
Do one of the following:
- To create an incident configuration, click the
New icon, and continue. - To edit an incident configuration, select a row, click the
Open icon, and continue. - To delete an incident configuration, select a row and click the
Delete icon.
- To create an incident configuration, click the
- Select the Actions tab.
- From the Lifecycle Actions table toolbar, do one of the following:
- To create an Action configuration, click the New icon, and continue.
- To edit an Action configuration, select a row, click the Open icon, and continue.
- To delete an Action configuration, select a row and click the Delete icon.
- In the Lifecycle Transition Action Form (SNMP Trap Incidents), provide the required information.
-
Click
Save and Close to save your changes and return to the previous form. The next time the lifecycle changes, NNMi launches the action associated with the lifecycle for the incident of that type.