To view the latest 11.3.x version, see  PATROL Agent 11.3.02 Open link .

PATROL Agent for failovers

This section details troubleshooting information for a PATROL Agent in a cluster environment that supports failovers.

One virtual IP address for each group or package

For PATROL Console applications and utilities to communicate with the agent after a group or package has failed over to another host, you must assign a virtual IP Address to the cluster application. A virtual IP address assigned to your DNS server or other host name/IP address resolution table guarantees that the console application can communicate with the agent regardless of which host it is running on.

PATROL Agent must recognize the virtual IP address

The cluster application's virtual IP address must be included in this list of IP addresses for the agent. This list is set in /AgentSetup/IPAddresses. PATROL Agent does not accept communication packets from IP addresses that it does not recognize.

Local KM customizations

Local customization are stored in the Knowledge Module with a host name designation. The only name that can be used is the actual host name of the PATROL Agent host. For this reason, it is important to use the actual host name when adding a PATROL Agent to the developer console. Using the actual host name ensures that the PATROL Agent loads the customization.

Local customizations made using this method will not behave consistently when a failover occurs.

Note

BMC recommends that you make local customizations with an operator console with modified patrol.conf entry. These customizations are stored in the agent Configuration File. For information about modifying patrol.conf, see PATROL Console for Microsoft Windows User Guide — Customizing PATROL, Volume 3.

Was this page helpful? Yes No Submitting... Thank you

Comments