Using Static VIPA on Agent Manager

Products

• ESP Workload Automation

Issue/Introduction

After moving the ESP agent manager, the static VIPA from home system was mistakenly created as a dynamic VIPA on target system. This caused the IP address of the home system to become unavailable. This resulted in communication issues, as nothing could connect from the home system to other LPARs due to the home system IP being taken by the ESP agent manager on the target system.

Resolution

There are at least 2 possibilities. 

1. If you can start different started task on H100 LPAR then you can concatenate additional RESTPROP members (RPROH100, RPROH140) where you will define appropriate server.address to correct DNS name or IP address for specific LPAR. This solution will be preferred if it is feasible for you.
2. If it is not possible to start different started task then you can enhance RESTOPS script with simple IF statement which will set variable DNS_NAME and then use this variable in RESTPROP member.

RESTOPTS update:

HOST_NAME=$(hostname -s)
echo "HOST_NAME=$HOST_NAME"
export DNS_NAME="0.0.0.0"
if  [ "$HOST_NAME" = "hostname" ]; then
 echo "H140"
 DNS_NAME="name.xx.xx"
elif  [ "$HOST_NAME" = "hostname" ]; then
 echo "H100"
 DNS_NAME="name.xx.xx"
else
 echo "Unknown hostName $HOST_NAME"
fi
"DNS_NAME=$DNS_NAME"

RESTPROP update: 

server.address=${DNS_NAME}