AutoSys Scheduler retains old IP for PROD agents after DNS change to redirect to Disaster Recovery (DR)
search cancel

AutoSys Scheduler retains old IP for PROD agents after DNS change to redirect to Disaster Recovery (DR)

book

Article ID: 443935

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

When performing a Disaster Recovery (DR) test or DNS failover, the AutoSys Scheduler may continue to route jobs to the primary network agents even after DNS has been updated to point to the DR network. This occurs because the Scheduler caches the IP addresses of the agent machines.

Environment

Product: AutoSys Workload Automation AE (All Versions)
Operating System: All supported UNIX/Linux and Windows platforms

Cause

The parameter EnableIPCaching=1 is set in the $AUTOUSER/config.$AUTOSERV file. When enabled, the Scheduler caches the resolved IP address for a machine's node_name. It only performs a new lookup if:

  1. The connection to the cached IP fails.
  2. The Scheduler service is restarted.

If the primary agents remain active during the DNS switch, the Scheduler maintains successful connections to the old IPs and never triggers a new DNS lookup.

Cycling an agent machine OFFLINE and ONLINE does not clear this cache.

Resolution

To force the Scheduler to recognize the new IP addresses after a DNS change, perform one of the following:

  • Option 1: Restart Services (Recommended) Restart the AutoSys Scheduler services. This clears the internal IP cache and forces a fresh DNS resolution for all defined machines upon startup.

  • Option 2: Disable Primary Agents Shut down the AutoSys Agent services on the primary (Prod) servers. Once the Scheduler fails to connect to the cached IPs, it will perform a new DNS lookup and find the DR IP addresses.

  • Option 3: Workaround (Dynamic Update) If a restart is not immediately possible:
    1. Modify $AUTOUSER/config.$AUTOSERV to set EnableIPCaching=0.
    2. Send a SIGHUP to the Scheduler (kill -HUP <pid>).
    3. Perform the DR activities.
    4. Re-enable caching by setting EnableIPCaching=1 and sending another SIGHUP once the failover is complete.

Additional Information

For more details, see EnableIPCaching.
To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on your respective region.