Skip to Content

Verifying the configuration

After configuring the Failover Agent (before activation), ensure that the desired data collection is accurately executed on the Primary Agent. Utilize one or more policies based on Agent Selection Criteria using specified TAG(s). For instance, the Primary Agent should already possess the necessary TAG(s). These TAG(s) are registered as a part of the Failover configuration.

To verify the expected behavior:

Action

Expected behavior

Activate the PATROL Failover Agent Policy.

  • Generates instances under the respective Device, displaying the associated "Environments," and the Primary and Secondary Agent hosts linked to them.
  • Attributes are presented at each level, representing the state of the Objects.

Assuming this Agent maintains solid connections to both the Primary and Secondary agents, halt the PATROL Agent on the Primary Server. 

After a brief delay, monitoring seamlessly transitiona to the Secondary Agent, and data collection proceeds as intended.

To initiate a failback to the Primary Agent, restart the PATROL Agent on the primary host server.

After a short delay, monitoring shifts back to the Primary Agent, and data collection resumes as expected.

 

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

BMC PATROL for Agent High Availability 23.4