IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase > Agent deployments
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Background information about agent autonomy
By default, agents are configured for autonomous operation (IRA_AUTONOMOUS_MODE is Y). When the connection to the Tivoli Enterprise Monitoring Server is lost or the monitoring server otherwise becomes unavailable, the agent continues to run all situations that can be evaluated exclusively at the agent.
Situations that become true while disconnected from the monitoring server are stored persistently and are uploaded to the monitoring server when reconnected. If the agent was starting up when the communications break occurred, startup processing continues.
To disable autonomous agent operation set IRA_AUTONOMOUS_MODE to N in the agent configuration. In this case you must also ensure variable CT_CMSLIST is both specified and not blank; otherwise the agent will not start.
To configure an agent for fully autonomous operation (in other words, it runs without a connection to a monitoring server), the following agent configuration is required:
- The CT_CMSLIST variable must not be set (that is, it should have no value).
- At least one protocol must be defined in the KDC_FAMILIES variable.
- The IRA_AUTONOMOUS_MODE variable does not need to be set, as its default value is Y. If IRA_AUTONOMOUS_MODE is currently set to N, it must be either changed to Y or removed completely.
- If you respond NO to question Will this agent connect to a TEMS? when running the UNIX installer, these parameters get set correctly for you.
- In all cases, including fully autonomous mode, at least one active protocol must be defined using the KDC_FAMILIES environment variable. If no protocols are defined, the agent will not start.
Parent topic:
Agent deployments