Administering Critical Events › Understanding Configuration Manager › Automatic Responses to Event Messages › Message Routing to Remote Hosts

Message Routing to Remote Hosts

The best way to route messages to a remote machine through message/action policies is to create a message record that traps those events and a message action that uses the FORWARD action keyword and specifies the remote node to which you want the messages sent. Since one message can have many message actions, it is easy to send messages to multiple machines.

You can specify the name of any machine that is currently defined for CAICCI remote communication. The configuration is set up during installation.

On UNIX/Linux platforms, one source of event messages is the Berkeley syslog daemon, which can route messages to a CA NSM server for processing, even those originating from servers not running CA NSM.

Event Management takes advantage of the powerful messaging facilities provided by the syslog daemon to:

• Select from several priorities, levels, and facilities of messages.
• Route messages by level or priority to different devices.
• Route messages by level or priority to different hosts.
• Receive messages from other hosts for local display.

To instruct the syslog daemon to route all messages to a remote machine, edit the syslog daemon’s configuration file and insert the remote host name in the action part of the line, prefixing the host name with a single at sign (@).

Note: If you use both the Berkeley syslog daemon and specific message action policies to reroute the same messages to the same remote machines, those messages will display twice on those remote machines as they were sent there twice, once by the Berkeley syslog daemon and again by Event Management.