If there are communication issues between the GX and the Agent Manager, you see a similar warning as the one below: Sep 26 00:59:44 2014 al-gx5208 iss-spa: Info: CSessionConfigServices::GetServerInfo: Returning this info: Destination=2:0 Name=AgentManager_HOSTNAME Host=x.x.x.x Account= Password= Port=3995 Proxy= Proxy Port=0 Use Proxy=false Proxy user= Proxy password=******(hidden) Once the doheartbeat command completes, run the following:Ī successful heartbeat looks similar to this: Then, run the service iss-spa doheartbeat command again and confirm it is now successful. Note: If you see any output other than what is shown in the screen capture above, run service iss-spa restart to restart the iss-spa service. You should receive a message similar to the one below: To do this, run the command that is specified below: You can also try forcing a heartbeat and confirming in the messages file that it was successful. The GX must be able to communicate to the Agent Manager on this port for the device to be Active. Ensure that there are no firewalls or other devices that might be blocking the traffic from the GX to the Agent Manager over port 3995. If this message is seen, it is likely due to some device that is blocking the traffic. If it fails to connect, you see a message similar to the output below: To test the communication, run the command below:Ĭurl -kv (where x.x.x.x is the IP address of the Agent Manager)Ī successful test shows that it connects followed by SSL certification messages. If you are unable to access the LMI of the appliance to do the previous test, you can use these steps below to troubleshoot communication issues via the command line.įirst, SSH to the device and login with the root credentials. If the test fails with different errors, copy the entire output of the log and contact IBM Security Systems Technical Support. If you see similar errors, it is likely due to some device that is blocking this traffic. Look in the log file for lines similar to the ones shown below:ģ 15:15:47.778 T:3078534864 Debug: CSessionConfigServices::InternalPostData: PXSSLCLIENT-LOWLEVEL: Failed to connect to 10.2.2.111: Connection timed outģ 15:15:47.778 T:3078534864 Error: CSessionConfigServices::InternalPostData: PXSSL exception thrown: Could not Perform request to server: ģ 15:15:47.778 T:3078534864 Debug: CSessionConfigServices::FilterCommError: Entered with err: 7ģ 15:15:47.778 T:3078534864 Debug: CSessionConfigServices::FilterCommError: Exiting with RC: c7590009ģ 15:15:47.778 T:3078534864 Debug: CSessionConfigServices::InternalPostData: Exiting with RC: 0xc7590009ģ 15:15:47.778 T:3078534864 Error: main(): Caught issErrorException!Įxception description: The send operation failed due to a communication failure. If this fails, it is typically due to not being able to connect to the Agent Manager over port 3995. If it failed, consult the log file for details of the failure. After the test is complete, a pop-up box will appear with the results. It tests the communication and give you a pop-up box with the results. Then, click the SiteProtector tab and click the Test Connection button. To access this, go to Manage System Settings > Appliance > System Tools. The easiest way to confirm the connectivity between the GX and the Agent Manager is through the LMI's System Tools utility.