If the Agent Manager is behind a firewall and unable to connect to the Foglight Management Server (FMS).
The Agent Manager logs display the following message:
"com.quest.spi.iiop.session.MasterSessionClientBinder - A network failure has been detected that prevents SPID from connecting to the server while creating MasterSession. Please consult the logs for more information. The error reported is: org.omg.CORBA.TRANSIENT: Retries exceeded, couldn't reconnect to xxx.yyy.zzz.ccc.:port vmcid: 0x0 minor code: 0 completed: No"
where xxx.yyy.zzz.ccc.:port is an IP address of the first physical network interface on FMS.
By default, FMS uses the first physical NIC and its IP address to bind all services when FMS starts.
Problem can occur, if some clients are located behind a firewall and or they are configured to use other (Virtual) IP address of FMS .
The following links provide details on configuring a FMS or a FglAM to communicate on a specific NIC IP address.
To specify the IP address or host name to be used for communication, set the following:
You can set this using the command line interface or by adding the following to the $FGLHOME/config/server.config file:
server.cmdline.option0 = "-Djboss.bind.address=127.0.0.1";
server.cmdline.option0 = “-Dbind.address”;
server.cmdline.option1 = “127.0.0.1”;
where 127.0.0.1 is the desired IP address
In Foglight 5.7.1 Tomcat is used instead of JBoss. In addition to changing the server.config file the following changes may need to be made to the server.xml file under $FMS_HOME
Also, please make sure that the parameter within the server.config.cfg file are set as follows, where xx.xx.xx.xxx is the ip addresss or hostname.
server.vm.option2 = "-Djboss.bind.address=xx.xx.xx.xxx";
FglAM: Binding to a local address
Please follow https://support.quest.com/foglight/kb/215398 if you want change it manually