Remote actions allow you to run a command on a remote device. Remote actions can only be triggered from the Infrastructure Management Server and not from any other remote source.
Before you can run remote actions, they must be configured on the administrator console, as described in the following topics:
The xCmd protocol enables an application to run a command on a remote host and does not require a port number. The xCmd protocol requires a remote user name and password. xCmd is only supported on Windows servers.
The xCmd protocol requires local administrative privileges to the network shares.
The telnet protocol can pass on the data it has received to many other types of processes including the remote logon server. Communication is established using TCP/IP and is based on a Network Virtual Terminal (NVT). The telnet protocol requires a remote user name, user password, system prompt, and a port.
You must change the protocol if you have used a different protocol after upgrading to the recent version of Infrastructure Management.
Also see, Properties files that control remote actions.
There are two types of remote actions in TrueSight Infrastructure Management. Both types of remote actions appear in the Tools > Remote Actions menu when you click an event in the operator console.
Remote actions that are defined from the administrator console and used in the remote action policy must be used to remotely run scripts (for example) on remote devices. Therefore, you must set up the credentials for any device that such remote actions are going to run on. For more information, see Creating remote actions on the administrator console.
Remote actions that run on the cell can execute a command from the computer in which the cell is running (typically, the TrueSight Infrastructure Management Server). These remote actions are defined in the pw/server/etc/cellName/kb/bin/mc_actions.mrl file. The following example is the definition of the 'ping EVENT mc_host_address' action:
You can trigger these remote actions from the KB rules using the perform primitive. These remote actions cannot be triggered using a policy.