Hi,
i have my control-m agent behind a firewall.
ag_diag_comm gives error that the unix ping to server platform failed.
ctm_diag_comm from the control-m server is successful, but doesnt return an IP.
if i run a job as control-m agent user, it runs finr (ran a command line ls, hostname etc) and i can view the output.
but if i run some commands by any other user, it fails, but doesnt show the output.
any ideas what need to be changed.
Control-m Agent Behind a firewall
Re: Control-m Agent Behind a firewall
Diagnostic tests should clearly resolve else it is communication issue and needs to be addressed in first place.
Is agent-server(7006) port opened on firewall?
Is the agent communication set to transient or persistent mode?
Thanks
Is agent-server(7006) port opened on firewall?
Is the agent communication set to transient or persistent mode?
Thanks
Re: Control-m Agent Behind a firewall
there was an issue with how the user was configured.
bin/bash was not enable.
the job ran successfully after the user settings were corrected.
-- FYI - the ag_diag_comm still shows the unix ping to server platfrom failed
but this doesn't cause any issues currently .
Regards ,
Johan
bin/bash was not enable.
the job ran successfully after the user settings were corrected.
-- FYI - the ag_diag_comm still shows the unix ping to server platfrom failed
but this doesn't cause any issues currently .
Regards ,
Johan