19.6 MESSAGE FORWARDING
There are two types of message-forwarding configurations. They can be used separately or in combination. One type of message forwarding instructs the managed node to send messages to a different management server. The MoM template called allnodes or hex_address is transferred to the managed node and renamed mgrconf during a normal template distribution. The manager-to-manager message forwarding is a configuration that instructs the management servers to forward messages to other managers. The file msgforw resides on the servers that participate in the message-forwarding scenarios.19.6.1 Message-Forwarding Cookbook
After the message-forwarding scenario is determined, select the appropriate sample templates, rename, and distribute to the node or rename msgforw for server-to-server message forwarding.19.6.2.1 Management server configuration tasks
This section lists the general tasks to configure message forwarding between the multiple management servers and the managed nodes.
Add the forward managers to the primary manager's node bank as a message allowed node.Add the primary manager to the forward manager's node bank as a message allowed node.Add the forward managers to a node group on the primary manager.Add the primary manager to a node group on the forward manager.Copy the message-forwarding sample template from the tmpl_respmgrs directory to the work_respmgrs directory.Edit the template; add the names of the responsible target (forward) forward managers.Add the appropriate attributes for message control, notification or acknowledgement. (Refer to Section 19.3.3 for a definition of the attributes)If necessary, edit the server configuration file ovconfchg to modify the default message-forwarding behavior.Use the opcmomchk utility to syntax check the template.Move the message-forwarding template to the respmgrs directory.Create the managed node message-forwarding template by renaming the file (allnodes or hex_address).If this file is for server to server message forwarding, rename the file msgforw.Distribute the configuration to the other management servers. This step is performed to ensure that the servers have the appropriate attributes in the database to receive messages from nodes in other domains.Restart the management server processes to activate the message-forwarding template on the server.Test the configuration. Create test messages (using opcmsg) that match the conditions of the message-forwarding templates.19.6.2.3 Message Forwarding Attributes
The message attributes described in this section are used within the MSGTARGETRULECONDS of the template and define processing instructions for the message after it arrives on the MSGTARGETMANAGER server.Message forwarding attributes include the following:- MSGCONTROLLINGMGR
Within the message-forwarding template, assign this attribute to each manager that should get a switch-control copy of the message from the managed node. - NOTIFYMGR
Assign this attribute to managers that receive notify messages from the managed node. - ACKNONLOCALMGR
This attribute, when assigned to the messages sent to the primary server, causes the message to automatically acknowledge and transfer directly to the history browser.
|
لطفا منتظر باشید ...
