Configuring the Agent Failover monitor profile


This topic provides information about configuring the monitor profile for PATROL for Agent High Availability to start monitoring.

Prerequisites for configuration

  • 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 BMC Helix Operations Management, while the secondary agent remains disconnected from BMC Helix Operations Management.
  • It is recommended to use a tag-based policy configuration for the agents, ensuring that the required monitoring policy is already applied to the primary agent.

To configure the KM, set the following preferences on the Add Monitoring Configuration dialog.

Monitoring Solution

Monitor Profile

Monitor Type

PATROL for Agent Failover 

PATROL for Agent Failover

Environments

Configuration details

Click Add button to add the FailOver Monitoring Configuration.

Field

Description

FailOver Environment Settings

FailOver Environment Name

Enter a name to identify the failover environment configuration.

Virtual Agent name used by Member Agents

Enter a virtual agent name utilized when setting up the PATROL_VIRTUALNAME_<port#> environment variable on both PATROL Agents responsible for data collection.

Virtual Agent Port# used by Member Agents

Enter a virtual agent port number for configuring the PATROL_VIRTUALNAME_<port#> environment variable on both PATROL Agents involved in data collection.

Debug Logging - located in log directory using PAW-host.kmlog

Select this check box to enable debug logging.

Monitoring 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.

  • You can add any number of Agent Tags to the configuration.
  • These Agent Tags should be placed within the configuration of the collection agents to link the "Active" PATROL Agent with the desired collection configuration policy or policies.
    Example: If a pair of agents are engaged in remote ping, the PING tag should be associated with those agents containing the PING policy.
  • Each Tag can be independently added to the respective Policy, enabling versatile and granular configuration.

Member Agents - Setup Details

Connection Credentials

User Name

Enter a user name.

Password

Enter a password.

Confirm Password

Confirm the password.

Primary Server Details

Primary Agent Hostname

Enter a primary agent host name.

Primary Agent Integration connect string

Enter a primary agent integration connect string

Primary Agent Proxy Server Name

Enter a primary agent proxy server name.

Primary Agent Proxy Server User

Enter a primary agent proxy server user name, if your primary agent needs to be connected to proxy server.

Primary Agent Proxy Server Password

Enter a primary agent proxy server password.

Important: A password is unnecessary when using a credentials-less proxy server.

Secondary Server Details

Secondary Agent Hostname

Enter a secondary agent host name.

Secondary Agent Integration connect string

Enter a secondary agent integration connect string, if blank then primary agent integration connect string will be used.

Secondary Agent Proxy Server Name

Enter a secondary agent proxy server name, if your secondary agent needs to be connected to proxy server, If blank and primary agent proxy server details available then those details will be used.

Secondary Agent Proxy Server User

Enter a secondary agent proxy server user name.

Secondary Agent Proxy Server Password

Enter a secondary agent proxy server password.

Important: A password is not needed when using a credentials-less proxy server.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC PATROL for Agent High Availability 23.4