F
F
Fiftydotov2021-09-06 13:41:08
Virtualization
Fiftydotov, 2021-09-06 13:41:08

How to tie VCSA to ESXi in different networks?

Good afternoon.

Input data: there is a host on Hetzner, the ESXi host is rolled out on it, it is assigned a white IP (conditionally 99.99.99.99). It also hosts the VM VCSa, is routed through Mikrotik RouterOS (a separate IP 99.99.99.98 is assigned), respectively, all other machines that are connected in the virtual switch have an A / B / C network, VCSA 10.1.19.

So I start connecting the host to VCenter, it finds it at 99.99.99.99, determines if initialization starts, throws out this error 6135ea97ceadb427575022.png

Google says that you need to restart the host, it is necessary that the versions of the host and vcenter match, be on the same network (I put it behind NAT ), check the services, added lines to the hosts file, changed the MTU to 1320, but nothing has changed. Who can help with this?

Answer the question

In order to leave comments, you need to log in

3 answer(s)
M
Maxim Grishin, 2021-09-06
@Fiftydotov

Give the host a management interface on the 10.1.19 network, and connect through it. Exposing ESXi with your bare ass to the Internet is at least unsafe. At the same time, solve the problem of network connectivity, since the VCS is behind NAT.

A
Alexey Dmitriev, 2021-09-06
@SignFinder

ESXI and VCSA need to be denied access to the Internet - as already mentioned above for security reasons.
Create a separate vnet for them with local addressing, and expose Mikrotik outside.

C
CityCat4, 2021-09-06
@CityCat4

Well, the host's version must be equal to or less than the realm's version - hosts of a version higher than the realm's, it just doesn't know.
It is quite possible that it is breaking into the host through some ports, and cannot get through.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question