Federation Topology Viewer showed that FMS Child failed to report to Federation Master.
From FMS master, ping test returns fmschild as xxx.xxx.xxx.123 and telnet fmschild 1099 was successfully
The following exception were found in FMS log (master)
YYYY-MM-DD HH:MM:SS WARN [QuartzScheduler.Utility_Worker-2] com.quest.nitro.service.federation.FederationConnectionManager - Unable to connect to the remote server "jnp://fmschild:1099". The server may not be running or may not support working with federation servers.
Additional Exception were captured in DiagnosticSnapshot log.
---- Last connection exceptions ----
jnp://fmschild:1099 -- javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: xxx.xxx.xxx.456; nested exception is:
java.net.ConnectException: Connection timed out: connect]
javax.naming.CommunicationException [Root exception is java.rmi.ConnectException: Connection refused to host: xxx.xxx.xxx.456; nested exception is:
java.net.ConnectException: Connection timed out: connect]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:780)
...
Caused by: java.rmi.ConnectException: Connection refused to host: xxx.xxx.xxx.456; nested exception is:
java.net.ConnectException: Connection timed out: connect
...
Caused by: java.net.ConnectException: Connection timed out: connect