You can specify the action that the BMC ProactiveNet Child Servers must perform when the policy is applied. The actions apply to all the devices associated with the BMC PATROL Agent and all the monitor instances that the agent monitors.
Ensure that monitor configuration is complete before the server configuration is applied. Server configuration cannot be applied to the monitors that are not configured through Central Monitoring Administration. If you have not done so already, perform the steps provided under the following sections:
On the Server Configuration page, provide the following details:
|Add monitors to group||Name of a group on the BMC ProactiveNet Child Server under which you want to add the monitors that are created as a result of this policy|
You can provide multiple group names, separated by commas. If a group does not exist, a new group is created. Use a forward slash (/) to specify a group in a hierarchy. For example, server/device1/myGroup.
If more than one group exists with the same name and a distinct hierarchy is not specified, monitor instances are not added to the group. The group names are case sensitive.
|Copy baseline from device|
Display name of the device from which you want to copy the baseline
Associate user groups with Computer System CI (Devices) for access control
Name of the user group on the child servers to associate with the devices that are created as a result of the policy
You can provide multiple group names, separated by commas. The user group names are case sensitive.
After you complete the server configuration, click Next or Finish.
On the Server Configuration page, update the values.
After you save or update a policy, the server configuration details are pushed to the selected BMC PATROL Agents.
When user groups in a policy are edited or deleted, the devices remain in the user groups to which they have been added. The changes to user groups affect the devices that are discovered after the policy is saved.
The following table lists various use cases on adding and updating groups while creating a policy in Central Monitoring Administration and how these groups are displayed in the BMC ProactiveNet Operations Console.
|Use case||Behavior of groups and monitors in the Operations Console|
|Initially no groups are present, and then you add a group while creating a policy in Central Monitoring Administration||No groups are created in the Operations Console because the groups are not present when the monitor instances are discovered.|
|Add a group and then change the group name by updating the policy||A new group is created and this group will contain monitor instances from the old group. The old group is deleted.|
|Initially two groups are present and you add another group while updating the policy||A new group is created and monitor instances from the already defined groups are copied to the new group.|
|Add a group while creating a policy and later remove the group while updating the policy||The group is deleted.|
|Delete or disable a policy that contains a group||The group is deleted.|
Groups are dynamically updated as and when a policy is updated.