Configuring the Agent Failover monitor profile
Monitor the availability of PATROL Agents by configuring the Agent Failover solution. For more information about the attributes collected during monitoring agent failover, see Monitor types and attributes.
Before you begin
- Both the primary and secondary agents must be configured to use a common virtual agent name.
- During failover configuration, the primary agent must be connected to the BMC Helix Operations Management, while the secondary agent remains disconnected from the BMC Helix Operations Management.
It is recommended to use a tag-based policy configuration for the agents so that the required monitoring policy is already applied to the primary agent.
To configure Agent Failover
- In BMC Helix Operations Management, select Configuration > Monitor Policies > Create Policy.
- On the Create Monitoring Policy page, select the Monitoring tab and click Add Monitoring Configuration.
- From the Monitoring Solution list, select PATROL for Agent Failover.
- From the Monitor Profile, select PATROL for Agent Failover.
- From the Monitor Type lists, select Environments.
- In the FailOver Monitoring Configuration section, click Add.
- Add the monitoring configuration as described in the following table:
Field | Description |
|---|---|
FailOver Environment Name | Enter a name to identify the failover environment configuration. |
Virtual Agent name used by Member Agents | Enter a virtual agent name to configure the PATROL_VIRTUALNAME_<port#> environment variable on both PATROL Agents that collect data. |
Virtual Agent Port# used by Member Agents | Enter a virtual agent port number to configure the PATROL_VIRTUALNAME_<port#> environment variable on both PATROL Agents that collect data. |
Debug Logging - located in log directory using PAW-host.kmlog | Select this checkbox to enable debug logging. |
| Monitoring Control Tags | Click Add to configure the control tags. Agent Side TAG required for Actively Monitoring Solution—Enter the name of the Agent Tag to associate "Active" PATROL Agents with specific collection configuration policies. For instance, when utilizing a pair of agents for remote ping, the PING tag should be associated with the respective agents.
|
| Member Agents - Setup Details | Expand Member Agents - Setup Details to configure the connection credentials of the member agents.
|
| Advance configuration | Expand the Advance configuration field to configure failover retry attempts. Failover Retry Attempts—Enter the number of retry attempts to reconnect to the primary PATROL Agent before switching to the secondary Agent. If the primary Agent becomes available during these attempts, a failover does not occur. The default value is 3. |
| Primary Server Details | Expand the Primary Server Details to configure the primary server details for the primary agent:
|
| Secondary Server Details | Expand the Secondary Server Details to configure the secondary server details for the secondary agent:
|
- Click Save.