Communicate with DCE agents installed by HP Operations Manager for UNIX


The instructions below explain how to configure a DCE agent installed by HP Operations Manager for UNIX so that it will send messages to, and accept instruction from, an HP Operations Manager for Windows management server. (HP Operations Manager for Windows will not be able to install policies on the managed node.) Depending on the template that is used, all messages, or a subset of messages can be sent to the HP Operations Manager for Windows management server. In this example, messages are sent to different management servers based on their message group.

Note TIP:
To configure an HTTPS agent installed by HPOM for UNIX so that it sends messages to an HPOM for Windows management server, switch the agent's primary management server. (See Switch the primary management server.)

To communicate with DCE agents installed by HP Operations Manager for UNIX

  1. Add the node to HP Operations Manager for Windows. (See, Create new nodes).
  2. Ensure that the agent is up to date.

  3. As user root, copy the template below to the working directory:

    /etc/opt/OV/share/conf/OpC/mgmt_sv/work_respmgrs/ 

    # This template sets the following configuration:
#
#   - send messages with message group OpC to Unix management server
#   - send messages with message group VPW to Windows management server
#   - allow both servers to run actions on the node
#

TIMETEMPLATES
# none

RESPMGRCONFIGS
		RESPMGRCONFIG
		DESCRIPTION "responsible mgrs for messages and agents"
				SECONDARYMANAGERS
					 SECONDARYMANAGER
						NODE IP 0.0.0.0 "unix.bbn.hp.com"
						DESCRIPTION "HP Operations Manager for UNIX management server"
					 SECONDARYMANAGER
						NODE IP 0.0.0.0 "windows.bbn.hp.com"
						DESCRIPTION "HP Operations Manager for Windows management server"
			ACTIONALLOWMANAGERS
				 ACTIONALLOWMANAGER 
						NODE IP 0.0.0.0 "unix.bbn.hp.com"
						DESCRIPTION "HP Operations Manager for UNIX management server"
					 ACTIONALLOWMANAGER 
						NODE IP 0.0.0.0 "windows.bbn.hp.com"
						DESCRIPTION "HP Operations Manager for Windows management server"
				MSGTARGETRULES
					 MSGTARGETRULE
					 DESCRIPTION "Unix responsibility"
						MSGTARGETRULECONDS 
							 MSGTARGETRULECOND
							 DESCRIPTION "Unix messages"
								MSGGRP "OpC"
							MSGTARGETMANAGERS
							MSGTARGETMANAGER
								TIMETEMPLATE "$OPC_ALWAYS"
								OPCMGR IP 0.0.0.0 "unix.bbn.hp.com"
					 MSGTARGETRULE
					 DESCRIPTION "Windows responsibility"
						MSGTARGETRULECONDS
							 MSGTARGETRULECOND
							 DESCRIPTION "Windows messages"
								MSGGRP "VPW"
						MSGTARGETMANAGERS
							 MSGTARGETMANAGER
								TIMETEMPLATE "$OPC_ALWAYS"
								OPCMGR IP 0.0.0.0 "windows.bbn.hp.com"
					 MSGTARGETRULE
				 DESCRIPTION "Rest of News"
						 MSGTARGETRULECONDS
						 MSGTARGETMANAGERS
							MSGTARGETMANAGER
								 TIMETEMPLATE "$OPC_ALWAYS"
								 OPCMGR IP 0.0.0.0 "$OPC_PRIMARY_MGR"

    Rename the file either allnodes, if the file applies to all nodes, or the IP address of an individual managed node in Hex notation, generated using the command /opt/OV/bin/OpC/install/opc_ip_addr (use opc_ip_addr -h for more information).

  4. Run the HP Operations Manager for UNIX template validation tool opcmomchk(1) on the finished configuration file to ensure that your changes are correct:

    /opt/OV/bin/OpC/opcmomchk <file_name>

    See the man page opcmomchk(1) for more information.

  5. As user root, copy the validated file to the configuration directory: cp <file_name> /etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/

    Note NOTE:
    If several, but not all, managed nodes have the same configuration, you can apply a symbolic link to the Hex file name of the related managed node. In addition, the same configuration directory can contain both an allnodes file and files for specific managed nodes. If configuration files for specific nodes are present, they are used in preference to the allnodes file for those nodes.

    HP Operations Manager for UNIX distributes the management responsibility configuration file from this directory as part of the standard template distribution process.
  6. Install the template(s) on the appropriate managed nodes:
    1. Select the nodes in the Node Bank window or other submap, then select Actions:Agents arrowInstall/Upgrade SW & Config...
    2. Select the Templates check box in the Install/Update Software and Configuration window.
    3. Click OK.