Agent and Scalability Servers Move Operations
An Agent is configured to connect to only one Domain Manager at any given time. However, the Agent can be reconfigured. The following command triggers the move operation of an Agent:
cla140
An Agent is configured to connect to only one Domain Manager at any given time. However, the Agent can be reconfigured. The following command triggers the move operation of an Agent:
caf setserveraddress new_scalability_server
The following command triggers the move operation of a Scalability Server:
cserver config -h new_domain_manager cserver register
Whenever a Software Delivery Scalability server is moved, the following things happen:
- The OSIM targets where agent is installed and having OSIM job status as “Current” will be moved to the new Domain Manager.
- The OSIM targets with any of the following conditions may remain in the old Domain Manager:
- Targets where agent is installed but the status is not “Current.”
- Targets with “Current” as the status but agent is not installed (that is, the OS is deployed with the boot parameter Install Agent = No).
Before moving the Server, ensure that the OS and Boot images that are used by the OSIM targets in the Old Domain Manager are registered in the new Domain Manager.
Whenever a calendar is updated on a CA Common Services (CCS) server on a DSM Manager), update the CCS agents on Scalability Servers. Therefore, run the Scalability Server procedure “Synchronize CCS Calendar” on every downstream Scalability Server that has a CCS agent installed.
If you move a Scalability Server from one manager to another using the cserver config -h new_manager command, CCS agent on the Scalability Server is automatically reconfigured to connect to the new manager.
To ensure that CCS values are not changed when re-registering the server, use the cserver command with the "-i" option instead of "-h".
If the server is moved using policy, the agent continues to connect to the old CCS server. So move the server manually. To change to the CCS server on the new_manager, use the following commands on the Scalability Server computer:
cautenv setlocal CA_CALENDAR_NODE new_manager_address cautenv setlocal CA_OPR_PROXY new_manager_address unicntrl stop all unicntrl start all