Administer > Configure Incidents > Configure SNMP Trap Incidents > SNMP Trap Configuration Form > Configure Actions for an SNMP Trap Incident > Lifecycle Transition Action Form (SNMP Trap Incidents)

Lifecycle Transition Action Form (SNMP Trap Incidents)

For information about each Action tab: Concept Link IconSee Also

Use this form to enter the command you want to run when an incident of the type you are configuring is at a particular Lifecycle State. For example, when an incident is generated (Registered), you might want to automatically open a trouble ticket or email or page your network operator.

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.

To configure an action for an incidents:

  1. ClosedNavigate to the Lifecycle Transition Actions form:
    1. From the workspace navigation pane, select the Configuration workspace.
    2. Expand the Incidents folder.
    3. Select SNMP Trap Configurations.
    4. Select the Actions tab.

    5. From the Lifecycle Transition Action 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.

  2. Make your configuration choices (see table).

    Note NNMi reloads the configuration information anytime the incident configuration is changed.

  3. Click  Save and Close to save your changes and return to the previous form. 
Create Action Attributes
Attribute Description
Lifecycle State Select a Lifecycle State from the drop-down menu.
Command Type

If you provided a Jython command, select JythonJython is a programming language (successor of JPython) uses Java class, instead of Python modules. from the drop-down list.

If you are using an executable or bat file, select ScriptOrExecutable from the drop-down list.

Command

Enter one of the following:

  • A Jython method with the required parameters
  • Executable command for the current operating system with the required parameters.

When entering a Command value, note the following:

  • Left or right bracket ([ ]) and backtick ( ` Unicode character: 0060 hex = 96 dec) characters are not permitted in the Command attribute. If you need these characters in your shell script, place them in a shell script file and reference that file from the Command attribute.
  • Windows only: Shell commands are not permitted in the Command attribute. To use shell commands, place them in a shell script file and reference that file from the Command attribute.
  • Use absolute paths to executables instead of relying on the PATH variable as it might not be set correctly.
  • Verify that you do not have two Jython methods with the same name. Otherwise, NNMi is not able to tell which is the correct method to load.
  • You can use the same Jython method for more than one incident configuration.

  • Jython (.py) files must reside in the following directory (see Manage environment variables):

    Note All the functions defined in the Jython files that reside in this directory are also accessible by NNMi. The files are also executed by NNMi on startup.

    Windows:

    %NnmDataDir%\shared\nnm\actions

    Linux:

    $NnmDataDir/shared/nnm/actions

  • When using executable files, specify the absolute path to the executable command or make sure the directory in which the executable file resides is in your PATH environment variable.
  • NNMi provides a set of parameters that can pass attribute values from an incident configuration. See Valid Parameters for Configuring Incident Actions (Management Events) for more information.

Send Help Center feedback