When you install an agent, you assign a primary CA User Activity Reporting Module server for the agent to contact first with collected events. When you configure an agent, you add other CA User Activity Reporting Module servers in an ordered list. When an agent that is ready to send collected logs to the primary server cannot reach it, the agent contacts each secondary server in the list until it finds an available one. Configuration of an ordered list of secondary servers guarantees log delivery from agent to server. An agent can send events to only one CA User Activity Reporting Module at a time; that is, there is no event duplication.
When the servers that you select to manage an agent are assigned new IP addresses, the ability of the agent to forward collected events to a server on its list can be impacted. By taking precautionary steps, you can help ensure that servers remain highly available to the agents that use them, even when these servers undergo manual or dynamic reassignment of their IP addresses.
The IP address of an installed CA User Activity Reporting Module could change in the following cases:
The CA User Activity Reporting Module server in a single-server system is configured to have DHCP assign its IP address. At some point after this server is selected to manage agents, DHCP assigns it a new IP address. This can occur when the CA User Activity Reporting Module is offline long enough for the IP address lease to elapse. No user notification is required when IP addresses are dynamically changed.
The CA User Activity Reporting Module servers are configured with static IP addresses. Due to a site process where IP addresses are reassigned as part of deploying a new subnet, new IP addresses are manually assigned to the CA User Activity Reporting Module servers.
Take appropriate action to ensure high availability of servers to agents, when those servers' IP addresses are subject to change.
|
Copyright © 2013 CA.
All rights reserved.
|
|