Expressway-E – Gatekeeper Timed Out

[Bill]

We have a new MRA Expressway-E cluster running version X14.3.4

The secondary expressway is showing an error message every 15 seconds.

It is reporting the gatekeeper timed out referencing the primary expressway (10.2.2.251)

tvcs: Event="External Server Communications Failure" Reason="gatekeeper timed out" Service="NeighbourGatekeeper" Detail="name:10.2.2.251:1719" Level="1" UTCTime="2024-02-25 14:11:21,529"

Does anyone know why I am seeing this?

Do to firewall restrictions, we have the Exp-E's configured with a Single Interface and reflexive NAT.

Thanks

[Nithin Eluvathingal]

It is recommended to use the dual NIC as it will prevent many problems. Is your tunnel between E and C up? How about your clustering? Is clustering done?

[Bill]

Nithin, thanks for the response.
I agree on the dual nic recommendation, unfortunately this customer is unable (or unwilling) to create the second DMZ.
But your suggestion might be pointing to the issue.
There are no SSH tunnels to the secondary Exp-E.
I will look into why this is.
Clustering is configured and looks good. TLS enforced and showing all Green for both C's and E's.

[Bill]

Strange. 
The Secondary Exp-E is showing no tunnels to the C's.
The UC Status says there are no Domains configured on the Exp-C.
But there are. The Primary Exp-E sees them.