CTM 6.3 agent discovery issues

gratedsandy · Post by **gratedsandy** » 30 Nov 2009 10:41

Group,
We're running CTM 6.3 server on HP UX.

We are facing issues with agent discovery on one of our boxes.
This Box 'A' has an agent installed and jobs are running fine against it.
We are also running jobs against aliases of 'A' and all these jobs run fine as well (For E.g. Node id - 'B', 'C', etc which are aliases of 'A').

However, we're now trying to run against a new alias 'D' of 'A' and this alias shows to be in 'Discovering' status consistently.
'ctmping' is failing to this alias 'D' as well. However, 'A' is alive and is able to run jobs.

Appreciate any inputs on how i can successfully discover agent 'D' and run jobs against it.

Walty · Post by **Walty** » 30 Nov 2009 4:07

Hi,

in this situation try:

1 - Held job(s) scheduled on nodeid alias D
2 - From <controlm> user execute delete entry for agent D : ctm_menu --> opt 9 --> opt 4
you must receive message like : Agent entry D was deleted successfully.
3 - From <controlm> user execute ctmping -nodeid D -discover y
You must receive message like : Agent : D is alive
4 - Free held job(s) on nodeid alias D
5 - Normaly on CCM your agent D is available now (try ping option to check it)

gratedsandy · Post by **gratedsandy** » 01 Dec 2009 9:34

Walty,
Thanks for your reply.
I only have 1 concern while doing this.

Since 'D' is just an alias of 'A', 'B' and 'C', If I go ahead and do a delete of entry 'D', will this affect status of jobs that may be executing on 'A', 'B' and 'C'?

Thanks.

Walty · Post by **Walty** » 01 Dec 2009 10:15

Hi,

That impact only the jobs scheduled on nodeid D.
In your case, for Control-M each alias is seen like as a unique nodeid (alias A=nodeid A, alias B=nodeid B ,....)

philmalmaison · Post by **philmalmaison** » 02 Dec 2009 11:59

as your agent is in discover status you can not delete the entry.
you must find why this new adress isn't valid, and it should be many thinks.

try to traceroute it to know where are contention
be sure the adress is reconize as well on both controlm agent host and controlm agent host ...

could you ping this adress ???

regards
philmalmaison

gratedsandy · Post by **gratedsandy** » 04 Dec 2009 12:44

Thanks Walty.
Your Procedure worked.

Phil,
To answer your questions, the alias 'D' was very much 'ping'able and also I could ssh to the server using the name 'D'.
Just a weird case where the agent 'D' stayed in 'discovering'state for 2 days.

I deleted the agent entry 'D' and did a ctmping and voila...it became available instantly.

Thanks everyone

RaboClanJ · Post by **RaboClanJ** » 24 Dec 2009 9:37

As per BMC, Control-M Agent 6.3 Fix Pack 4 should correct issues involving the discovering of alias names.