Control-M Agent 6.3.0.2 - Logical Agent Name

airhawk · Post by **airhawk** » 05 Mar 2008 5:13

Hi,

Would need the expertise of the guru in this forum.

Had installed the latest agent version of 6.3.0.2 for our servers. Encountered a serious problem on hand.

The new agent had an additional component being input into the register, that is the "Logical Agent Name". That fixed the machine name as the registered for the agent.

Due to this setup, encountered problem when we're doing our DR testing. Upon switched the Alias of our PRD over to DR side, Alias is now pointing to our DR server. Ordered in a test job using the same alias, and job is either unable to run or immediately turned to unknown status.

Had any one encountered the same problem and had a work around to this hertic problem ?

Would greatly appreciate your knowledge.

Thanks in advance.

Zakeer · Post by **Zakeer** » 05 Mar 2008 10:29

Hi,

When you switched to DR server did Control-M Server and agent connected to that server were in running status?

Are both the PROD and DR server pointing to the same database?

philmalmaison · Post by **philmalmaison** » 05 Mar 2008 4:37

speaking about 6.3.01.200 version , you're enable to not parameter the S to A port number, enableling you to have more than one agent on the same server, using the logical adress of your server intstead of StA port number.
So in DR mode could you ping the logical adress ?

regards
Philmalmaison

gglau · Post by **gglau** » 05 Mar 2008 11:17

Is it simpler to define a node group using the alias name? Normally this node group has PRD agent. Upon DR, add the DR agent into the group. Removing PRD agent is optional if PRD agent is not available.