Adding Access Gateway Service to an existing cluster causing service unavailability error

Fresh install of Access Manager 3.1 SP3 on SLES11 and configured the Admin console and 
Identity (IDP) Server. Installed SLES11x64 based Access Gateway Service (AGS) on another host and did basic
testing to make sure functionality existed ie. users were able to access protected resources on
Web server after authenticating to IDP server.

After initial AGS install, an Access Gateway cluster was then created and service access continued to
work fine.

For performance reasons, a second AGS server was Installed and added to the existing Access Gateway
cluster. After doing so, modified some user workstation HOSTS file to confirm operation through the
new AGS worked fine. However, no user user could access any resources through this AGS.

Using iManager, go to the proxy service page and select the AGS server that failed. Change the 
listening IP to any other IP address, apply changes and select the original IP once again.
Update and Apply.

Applying the new AGS server to the cluster creates the socket 127.0.0.2:80 but does not listen 
on the real IP of the AGS.

Engineering is aware of the issue and it will be addresses in 3.1 SP3 IR1.