RESOLUTION 1:
To confirm the port the FglAM uses to connect to the FMS check for messages like the following in the ManagementServer log:
2016-10-28 15:22:29.980 INFO [http-exec-9] com.quest.glue.common.comms.HostStatus - New connection from downstream host [fglamhostname/IP_Address]
RESOLUTION 2:
If more than one IP address is referenced in the messages in the ManagementServer log check the output of the following netstat commands on the FglAM host to confirm that the FglAM is bound to the designated IP address.
netstat -tulpn (Linux)
netstat -boa (Windows)
RESOLUTION 3:
The debug logging can be increased on the FglAM to display "Get connection" and "Creating new connection" messages in the FglAM logs. The messages indicate the port the FglAM uses to connect to the FMS.
2016-10-28 15:47:31.524 DEBUG2 [Startup Thread] com.quest.glue.core.comms.transport.http.ClientConnectionTask - Making required upstream connection
2016-10-28 15:47:31.556 ECHO DEBUG2 [Startup Thread] com.quest.glue.core.util.CommonsLoggingToQuestBridge - Get connection: /192.168.0.1->{s}->https://hostname:8443, timeout = 60000
...
2016-10-28 15:47:31.556 ECHO DEBUG2 [Startup Thread] com.quest.glue.core.util.CommonsLoggingToQuestBridge - Creating new connection [/192.168.0.1->{s}->https://hostname:8443]
