Page tree
Skip to end of metadata
Go to start of metadata

This section provides information about local actions and the Infrastructure Management supported out-of-the-box local actions.

Local actions are actions that you can execute on the computer you are working on. In earlier Infrastructure Management versions, you had to run a command or script to diagnose or solve an issue. Now, these commands are available on the UI in the form of local actions. To access local actions select Local Actions from the Tools menu. Local actions are based on user groups.

Out-of-the-box local actions for non-alarm and non-abnormality events

Infrastructure Management supports the following out-of-the-box local actions for non-alarm and non-abnormality events:

  • Ping Event Origin 
  • Traceroute to Event Origin 
  • Telnet to Event Origin 
  • SSH to Event Origin 
  • VNC to Event Origin 
  • RDC to Event Origin 
  • Show Local Action Environment

Out-of-the-box local actions for alarm and abnormality events

Infrastructure Management supports the same out-of-the-box local actions for non-alarm and non-abnormality events as well as alarm and abnormality events. The only difference is that the slot used to execute local actions for non-alarm and non-abnormality events ismc_origin whereas, for alarm and abnormality events, the slot is mc_host.

For information about adding or modifying local actions, see Adding or modifying local actions in the operator console.

1 Comment

  1. This documentation needs to point out that some of the local actions just contain place holder scripts, and will not actually do anything out of the box.

    On Windows, there is no native ssh nor vnc client, so the 'ssh to event origin' and 'VNC to event origin' local actions just contain place holder scripts that do not do anything when running on Windows.  The mc_vnc script for Linux/Unix is a place holder as well.