This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.
You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

"Unreachable on configured port" error: VMAN timeout adjustment?

We have a client located in a mountain region where the only internet connectvity is available is a satellite link. We communicate to their site through a Site to Site VPN tunnel and they have ridiculous latency; as of right now it takes an average of almost 1300 MS for a ping to reach from my network to their firewall LAN and back. I'm trying to add an ESXi host to VMAN and I keep getting an error reading "<ip address> is unreachable on its configured port. Please validate the host information and try again."

I have validated the host information-many times, and in fact once I got lucky enough that the validation worked (the latency must have dropped just enough to connect for an instant) and I know it's not a firewall blockage because the VPN tunnel allows all traffic. We have many clients set up this way using the same equipment and configurations on both ends and this is the only one behaving this way, so after troubleshooting I've come to the conclusion that the latency is what's causing the problem. Is there any way to make an adjustment to VMAN's timeout settings, either by specfic node-which I would prefer-or even globally?

Or is it possible that I'm incorrect and something else is causing the problem? Because I don't know what else it could be.

Anyone else ever run into this issue?

  • Hi,

    do you have VMAN Appliance or VIM in Orion?

    If you have VMAN and it is really connection issue, we suggest to deploy Federated Collector on the site (where host is located), configure collector's connection with VMAN and let poll mentioned host via collector.

    This will hopefully work + this should also save some network resources.

    There is also KB article about this (especially second half of it):
    Use federated collectors in Virtualization Manager

    If this won't help, open case with support and we will try to find another solution.