Administer > NNMi Incidents > Configure Incidents > Configuring Lifecycle Transition Actions

Configuring Lifecycle Transition Actions

While configuring lifecycle transition actions, note the following:

  • By default, NNMi runs actions in the following location:

    • Windows: %NnmDataDir%\shared\nnm\actions
    • Linux: $NnmDataDir/shared/nnm/actions

    If an action is not in this location, specify the absolute path to the action in the Command field of the Lifecycle Transition Action form.

    Note Jython files must be placed in the actions directory.

  • Each time you make a change to the action configuration, NNMi rereads the actions directory for Jython files and loads them into NNMi.
  • Actions are enabled as a group for an incident type.
  • For information about the NNMi information that you can pass to an action, see Valid Parameters for Configuring Incident Actions in the NNMi help.Provide examples

Load MIBs (non-trivial)

<<Grizzly: use nnmloadmib.ovpl to load incident configuration; use nnmincidentcfg.ovpl to make the incident configuration available>>

Configure traps (reference help for details); select RCA status, provide guidance in this process

Format message, dedup, rate& action configuration

No migration for trapd.conf

Check for migration tool in Panda timeframe

Explain migration tools for traps

Explain incident correlation (or why we don't have it)

Pairwise trap configuration

Hints for trap filters