Agent Unreachable - Only one connection server

[leemill]

We have an agent unreachable issue but it is only affecting one connection server of the pair that we run. Some of our View desktops go agent unreachable following a restart but only on one of the connection servers. On the other server they are fully available and work OK. I've checked for connectivity between the desktop and the 'bad' connection server and that seems fine even when the unreachable status is shown.

Restarting the View Agent Service on the desktop seems to restore the agent connectivity but obviously this is causing some issues.

Has anyone encountered / solved a similar issue?

[mpryor]

Only on one connection server? The agents will connect to a single server, but messages are meant to be routed between them - so if you're seeing "unreachable" on one server but not the other you're likely looking at messaging issues between the connection servers themselves. Have you looked at the connection server logs to see if there are other related errors/timeouts? Can you confirm that traffic on port 4100 (JMS inter-router communication) is healthy?

[leemill]

Hi

The two connections servers are on the same network with not firewall etc between them so I assume the 4100 traffic is allowed. I will confess to being unsure about what to look for in the connection server logs but no obvious time out errors. Any clues?

[pari2k3]

It could be ADAM replication issue between the Connection Servers.  Can you please check the status of the connection servers on the dashboard.

Forcing replication between ADAM databases (1021805) | VMware KB

[kevinpower]

Hello,

did you tried to restart the connection servers to clear the ADLDS Synchronization between servers?

Restart order of the View environment to clear ADLDS (ADAM) synchronization in Horizon View (2068381...