Configure action-allowed and secondary managers


By default, only a node's primary management server can start actions on the node. To enable other management servers to start actions on a node, you must specify action-allowed management servers in a flexible management policy and deploy it to the node. This is important if you forward messages that have automatic and operator-initiated actions to other management servers.

The primary management server is initially set during the agent installation. To enable other management servers to become a node's primary management server, you can specify secondary management servers in the same policy. If a node has the HTTPS agent, the secondary management servers can also deploy policies and packages to the node, without first becoming the primary management server.

A flexible management policy that configures action-allowed and secondary managers must contain the following statements:

 RESPMGRCONFIGS
	RESPMGRCONFIG DESCRIPTION "Policy description"
	SECONDARYMANAGERS
	ACTIONALLOWMANAGERS

You can add to this minimal policy as many secondary managers and action-allowed managers as you need. You can specify either the IP address or host name of each management server. To specify only the host name, use the IP address 0.0.0.0. For example, the following policy specifies manager1.example.com and manager2.example.com as secondary and action-allowed managers. It also specifies that the management server with IP address 192.168.1.3 is an action-allowed manager.

 RESPMGRCONFIGS
	RESPMGRCONFIG DESCRIPTION "Enable manager1, manager2, and 192.168.1.3"
	SECONDARYMANAGERS
			SECONDARYMANAGER NODE IP 0.0.0.0 "manager1.example.com"
			SECONDARYMANAGER NODE IP 0.0.0.0 "manager2.example.com"
	ACTIONALLOWMANAGERS 
			ACTIONALLOWMANAGER NODE IP 0.0.0.0 "manager1.example.com"
			ACTIONALLOWMANAGER NODE IP 0.0.0.0 "manager1.example.com"
			ACTIONALLOWMANAGER NODE IP 192.168.1.3

If you use agent-based flexible management, you can add the secondary and action-allowed managers to an existing flexible management policy.

To configure action-allowed and secondary managers

  1. In the console tree, open Policy managementarrowAgent policies grouped by type. Right-click Flexible Management, and then click Newarrow Policy. The flexible management policy editor appears.
  2. In the General tab, type a flexible management policy that specifies secondary and action-allowed managers.
  3. Optional. Click Check Syntax. A message appears, which gives details of any errors. Correct any syntax errors.
  4. Save the policy, and then deploy it to the nodes that you want to configure.

Alternatively, you can edit or copy one of the sample flexible management policies, which are available in Policy managementarrowPolicy groupsarrowSamplesarrow Agent-based Flexible Management.

Related Topics: