Hide Forgot
Several different issues can be caused by improperly configured firewall in the hosts or bad network configuration. If the engine could select a proxy host to run ports checks against other hosts, the engine could help the administrator to avoid failing migrations or timeouts on opening consoles due to bad network/firewall configuration. Sometimes this is only hit when it's really needed, like in the case of automated migrations or when a host needs to be put into maintenance. The 5900-6923 and 49152-49216 ranges and also 16514 would be quite nice to have.
As an additional test, a host could try test connection against all other hosts incoming migration port, resolving their FQDNs and attempting to connect. If it fails then a warning could be displayed in the Administration Portal saying that Migration from X to Y might fail.
*** This bug has been marked as a duplicate of bug 994170 ***
BZ<2>Jira Resync