1) Recommend to check on the instance names from the Database dashboard | click on Settings | Remove from monitoring.
2) Under Dashboards | Databases | Support Dashboard | Databases Technical Support | Clear Agent Model Data.
The federation server simply pulls all Topology from the remote children FMS servers. If DBSS agent topology exists under child, the master would pull it. The DB agent topology needs to be deleted from all children and master Topology sync must be in working condition. Then the topology of deleted agents should disappear from master after the Sync happens. I assumed all the FMS children are the same version.
3) The Master topology sync is having a problem with the Child FMS (Federation Master FMS Support Bundle), these messages are in the Federator FMS log:
WARN [RemoteAlarmAccessor-46-jnp://hostname] com.quest.nitro.service.federation.RemoteServer - An attempt to get data from the remote server "jnp://hostname:1099" failed due to an unexpected error (most likely originating on the remote server).
org.hibernate.exception.GenericJDBCException: Cannot open connection
WARN [RemoteDataAccessor-5-jnp://hostname] com.quest.nitro.service.federation.RemoteServer - An attempt to get data from the remote server "jnp://hostnamet:1099" failed due to an unexpected error (most likely originating on the remote server).
java.lang.RuntimeException: org.jboss.util.NestedSQLException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] ); - nested throwable: (javax.resource.ResourceException: No ManagedConnections available within configured blocking timeout ( 30000 [ms] )) at com.quest.nitro.service.util.JDBCHelper.getConnection(JDBCHelper.java:124)
4) How can you force a topology refresh, to ensure that the Federation Master is up-to-date?
Here is the location of the federation.config file on the Federation Master FMS:
To force a topology refresh:
Set TopologyRefreshPeriod=1 (in the federation.config file).
Wait for one minute.
Reset TopologyRefreshPeriod to its old value.
Wait for the refresh to finish.
IMPORTANT: Refresh time depends on the environment complexity.
To force the topology refresh from the JMX:
http:///jmx-console based on the parent FMS (Federator)
Invoke refreshAll() on the TopologySynchService MBean.
(We need to search for the “TopologySynchService” then click on it and scroll down to “refreshAll()” then click on Invoke.
IMPORTANT: No configuration changes are necessary.
5). Currently the Federator FMS does not support deleting the TopologyObject automatically when the specific child FMS cannot be contacted. A CR for this issue has been logged as FGL-18525.