AutoSys Workload Automation

We came up with a scenario where our scheduler is not able to ping the F5 loadbalancer but able to autoping the agent residing behind the loadbalancer, previously all the jobs were working fine via loadbalancer now when DC migration happened to our side jobs are not getting triggered via the loadbalancer but individual servers are working fine to run the job. Our customer is asking for resolution why jobs are not running via loadbalaner which was previously not a problem.

Any help would be greatly appreciated.

Was the load balancer configuration updated after the DC migration? There are different configurations for a LTM (local traffic manager) and a GTM (global traffic manager). If you haven’t already, you most likely need to engage the F5 team to investigate.

Thanks for update lisadunaway yes checking with loadbalancer managing person he told ports need to be enabled by network & security team, hoping the issue will be fixed once its done.