Changing Autosys Agent servers without reinstall

[Yehonatan Amir]

Hey All,

We have recently installed a fresh installation of Autosys version -

1589 LINUX ORA 11.3.6 SP7 16accc0d ptktl-autosys11web ptktl-autosys11web.bezeqint.co.il

insted of our old -

163 LINUX ORA 11.3 SP1INC4_CUM3 16ac7c0d autosys-ptk.bezeqint.co.il autosys-ptk.bezeqint.co.il

anyone knows if its possible to change the Agents configuration so they would work with the new servers (instead of uninstalling them and reinstalling) - we need this procedure for both Windows and Linux servers

Thanks and regards,

Yoni

[Steven Anderson]

Yoni,
Run autoping to the agent machine(s) from the new Scheduler machine.  This should populate the manager_node info in the agent's agentparm.txt file.
Thanks and regards,

[Yehonatan Amir]

Hey Steven,

Thanks for the tip :)

Some of the Agents just connected automatically to the new scheduler like you suggested they would when using the autoping command,
however, for some machines the autoping still fails.

I tried restarting the problematic Agents , but it doesnt help.

Any ideas ?

Thanks Yoni

[Steven Anderson]

Hi Yoni,
If autoping to the agent fails to popluate the agent's agentparm.txt file with the manager node info, then add the manager node information manually to agentparm.txt and restart the agent.

[Yehonatan Amir]

Hey Steven, 

Thanks again , I looked in the agentparm.txt , and the new scheduler is indeed written there .. but still i'm unable to connect.

Are there other places where the scheduler  should be mentioned in for the Agent to allow him to connect ?

Thanks and regards,

Yoni

[Steve Carrobis]

Are they behind load balancers? It may not be going to the right machines.

You need to have the actual nodes registered in AutoSys.

Make it mandatory..

 

 

 

Steve C.

 

Nothing in this message is intended to constitute an electronic signature unless a specific statement to the contrary is included in this message.

Confidentiality Note: This message is intended only for the person or entity to which it is addressed. It may contain confidential and/or privileged material. Any review, transmission, dissemination or other use, or taking of any action in reliance upon this message by persons or entities other than the intended recipient is prohibited and may be unlawful. If you received this message in error, please contact the sender and delete it from your computer.

[Yehonatan Amir]

Hey Steve , 

Its not behind any kind of LB, just plain Agent.

[autosys@ptktl-autosys11p ~]$ autorep -M ptktw-hexcdr -q

/* ----------------- ptktw-hexcdr ----------------- */

insert_machine: ptktw-hexcdr
type: a
factor: 1.00
port: 7520
node_name: ptktw-hexcdr
agent_name: ptktw-hexcdr
encryption_type: DEFAULT
character_code: ASCII
[autosys@ptktl-autosys11p ~]$

I tried sending jobs to the Agent (even though the autoping fails) and no files been added to the spool directory..

The funny thing is , that on several other agents , i didnt have to do anything , autoping just worked like a charm right off the bat..

I think i will have to try to reinstall the Agent

Thanks for all the help :)

Yoni
bezeq international

[John Hiett]

Hi Yoni,

If the manager ID has been added to the agentparm.txt automatically then it may be possible that the Manager->Agent connection is succeeding, but the return connection (Agent->Manager) is not.

If you haven't done so already it may be worth checking that the Manager address recorded in the reciever.log file can be resolved from the Agent machine.

Kind regards,
John

[Steve Carrobis]

The only thing the agent needs is to be autopinged. unless you mean the CLI portion.

[Yehonatan Amir]

Hey Steve and John,

Thanks for all the help , eventually i found out the problem was related to the routing table on the autosys servers , where 
the response from the server was directed to the wrong vlan.

After we added the right routing the problem was solved :)

Thanks and kind regards,

Yoni
Bezeq international