Problem with CA ESP Workload Automation System Agent having Natted MANAGER IP Address when MGRADDR command is issued.

Products

• ESP Workload Automation

Issue/Introduction

One CA ESP WA System Agent specifies a natted MANAGER IP address in its agentparm file. That IP address firstly gets translated to the real IP address used in the AGENTDEF table for MANAGER. It works fine as long as the MGRADDR command is not used. Once it IS used, the agent starts using the IP address defined in AGENTDEF table for MANAGER instead of the 'isolated' IP address required for this Agent. As a result, the Agent can't communicate to CA Workload Automation EE (ESP) system until it's recycled.

Environment

Release: CA Workload Automation ESP Edition
 

Resolution

Use DNS name on MANAGER statement in AGENTDEF table, combined with the IF logic. For example:

IF SYSNAME='SYSA' THEN DO 

  MANAGER NAME(ESP_MANAGER) TCPIP(SYSA.xxxx.COM) 

ENDDO       

ELSE IF SYSNAME='SYSB' THEN DO       

        MANAGER NAME(ESP_MANAGER) TCPIP(SYSB.xxxx.COM) 

     ENDDO       

ELSE IF SYSNAME='SYSC' THEN DO       

        MANAGER NAME(ESP_MANAGER) TCPIP(SYSC.xxxx.COM) 

     ENDDO

Then MGRADDR command will send the DNS name, merely a string like SYS?.xxxx.COM, and it will be up to the agent side to resolve it to a numeric address. It implies the availability of a DNS server or/and an appropriate HOST file on the agent side.