IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > High Availability Guide for Distributed Systems > Autonomous mode and autonomous agents > Autonomous mode agent switch from a secondary monitoring server back to the primary hub monitoring server
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Agent configuration parameters
The following agent configuration parameters can control agent to Tivoli Enterprise Monitoring Server connectivity and behavior:
See the IBM Tivoli Monitoring: Installation and Setup Guide for a complete list of common agent environment variables and the IBM Tivoli Monitoring: Administrator's Guide for more information about autonomous agent behavior.
- CT_CMSLIST
- Required variable that specifies the primary or secondary Tivoli Enterprise Monitoring Server the agent must connect with. Takes a semicolon-delimited list of monitoring servers of the form network protocol:hostname or protocol:address.
- CTIRA_RECONNECT_WAIT
- This parameter specifies, in seconds, the frequency with which the agent will attempt to connect with the monitoring server. The default is 600 (10 minutes).
- CTIRA_MAX_RECONNECT_TRIES
- This parameter is being deprecated. Use it to specify the number of consecutive times without success the agent attempts to connect to a monitoring server before giving up and exiting. The default value of 0 means that the agent will remain started regardless of its connection status with the monitoring server.
Before the release of Tivoli Monitoring V6.2.2, the default value was 720. Along with the CTIRA_RECONNECT_WAIT default setting of 600, the agent tries to connect to the monitoring server for 432000 seconds (5 days) before giving up and exiting. If you prefer to have the agent shut down when the reconnect limit is reached, specify the number of retries. You must also disable the agent watchdog function (disarmWatchdog), which is described in the Agent User's guide.
- CTIRA_PRIMARY_FALLBACK_INTERVAL
- Forces the agent to switch from the primary Tivoli Enterprise Monitoring Server to one of the defined secondary monitoring servers, because the primary monitoring server is offline or due to network-connectivity issues. It is desirable for the agent to switch back to the primary monitoring server as soon as possible when it becomes available. This parameter controls the frequency with which the agent performs lookup of the primary monitoring server. If the primary monitoring server is found, the agent disconnects from the secondary monitoring server and reconnects to the primary monitoring server. The minimum value must be 2.5 times CTIRA_RECONNECT_WAIT value. Default value is 4500 seconds, or 75 minutes.
A value of zero disables this feature. Always set CTIRA_PRIMARY_FALLBACK_INTERVAL=0 for agents that are directly connected to the hub monitoring server. If Hot Standby is configured, the agent will switch based on the Hot Standby failover operation and not based on the primary fallback feature.
In an hot standby configuration, an agent switches to the acting hub monitoring server after receiving a SWITCH command from the standby hub monitoring server, even if CTIRA_PRIMARY_FALLBACK_INTERVAL=0, because the standby hub monitoring server reroutes agents to the acting hub monitoring server. If the agent requires redundant access to a monitoring server, the minimum configuration is two hub monitoring servers in a Hot Standby configuration and two remote monitoring servers. The agent must be configured to only the remote monitoring servers. That configuration provides the agent two monitoring servers to connect to at any time. If redundancy is not required, then do not configure Hot Standby.
Parent topic:
Autonomous mode agent switch from a secondary monitoring server back to the primary hub monitoring server