Update AutoSys Configuration for Tie-Breaker IP Address Change
search cancel

Update AutoSys Configuration for Tie-Breaker IP Address Change

book

Article ID: 442216

calendar_today

Updated On:

Products

Autosys Workload Automation

Issue/Introduction

An AutoSys Tie-Breaker server is being relocated or assigned a new IP address.
Guidance is required to ensure the AutoSys instance (Primary, Shadow, and Tie-Breaker) correctly recognizes the new network information without service interruption.

Environment

  • Product: AutoSys Workload Automation
  • Component: Scheduler / Application Server / Tie-Breaker

Resolution

When updating the IP address of a Tie-Breaker server while maintaining the same Hostname or Fully Qualified Domain Name (FQDN), follow these steps to ensure the AutoSys configuration remains synchronized:

1. Verify Configuration Files

Check the $AUTOUSER/config.$AUTOSERV file on the PrimaryShadow, and Tie-Breaker servers.

  • Ensure there are no hardcoded IP addresses for the schedulers or application servers.
  • Confirm that all references use the Hostname or FQDN Tie-breaker realted queries.

2. Update DNS

Coordinate with your network team to update the DNS records for the Tie-Breaker server.

  • Ensure the new IP address is mapped to the existing Hostname/FQDN.
  • Verify that DNS changes have propagated across the network before starting the maintenance window Tie-breaker realted queries.

3. Disable IP Caching

To prevent the Scheduler from using stale or cached IP information, it is recommended to disable IP caching:

  • Set EnableIPCaching=0 in the AutoSys instance configuration.
  • Restart the Scheduler to apply this change Tie-breaker realted queries.

4. Restart Services

After the IP change is complete:

  • Restart the Tie-Breaker Scheduler and Application Server.
  • Agent Refresh: If any agents report a "Missing" status, restart those agents to force a refresh of the hostname resolution to the new IP Tie-breaker realted queries.

Note: Broadcom recommends testing these steps in a lower environment first to confirm the specific behavior of your network configuration.

Additional Information

EnableIPCaching