Control-M Windows agent not communicating using an Alias

Everything about Control-M agents installation or setup.
Post Reply
User avatar
RaboClanJ
Nouveau
Nouveau
Posts: 5
Joined: 15 Jun 2007 12:00

Control-M Windows agent not communicating using an Alias

Post by RaboClanJ » 18 Mar 2011 4:08

Recently Upgraded Control-M/Server & EM to Version 6.4 from 6.3 (Windows MSSQL).
While upgrading the Agents to 6.4 from 6.3 encountered a problem with communicating with one agent.
This windows webserver has the agent installed as default.
The Control-M/Server can communicate with the agent using the server name and shows the agent as available.
However, the server the agent is installed on, has three other alias names, each with its own separate IP address.
I am unable to get the Control-M/Server to communicate with the agent using any of the three alias names.
When I run the comm_diag from the CTM_Menu/Troubleshooting:
as Server name - CTMS ping to Agent: Success
as Alias #1 - CTMS ping to Agent: Failed
as Alias #2 - CTMS ping to Agent: Failed
as Alias #3 - CTMS ping to Agent: Failed

The agents instance name is Default

Prior to the upgrade of the Agent to 6.4, all the Alias names were working with the 6.3 Agent.
The Configuration Manager showed the alias' as available.
Now after the agent upgrade, the server shows available but the Alias' show unavailable.

Anyone have any ideas what the problem communicating with the agent via the alias' might be ?

User avatar
rchkevin
Nouveau
Nouveau
Posts: 67
Joined: 29 Oct 2007 12:00
Location: Chennai

Post by rchkevin » 30 Mar 2011 8:55

Hi,

Please verify the agent configuration.

Listen to Network Interface is set to ANY

Post Reply