简体   繁体   English

ESXi 6.5 的第二个管理接口/NIC/IP

[英]Second management interface/NIC/IP for ESXi 6.5

We have 3 ESXi servers that each have their public IP for manageability, however for the backups we need the servers to have an internal on a different NIC.我们有 3 台 ESXi 服务器,每台服务器都有自己的公共 IP 以便于管理,但是对于备份,我们需要服务器在不同的 NIC 上有一个内部。

However, when we've added a new VMKernel network, the original (public IP) network won't connect anymore, resulting in the server being only reachable via the newly added LAN network.但是,当我们添加新的 VMKernel 网络时,原始(公共 IP)网络将不再连接,导致只能通过新添加的 LAN 网络访问服务器。

Is there a solution we can use so the servers are reachable on both NICs/IPs ?是否有我们可以使用的解决方案,以便在两个 NIC/IP 上都可以访问服务器?

The 3 servers have these configuration for network: 3台服务器的网络配置如下:

Interface 1: Dell iDRAC
Interface 2: VMWare public management network (public)
Interface 3: VMWare private management network (10.0.0.1/24)
Interface 4-5: Double redundant uplink
Interface 6-7: LAN network trunked

You may use the same switch (with 2 uplinks and explicit LBFO settings for different port groups) or two different switches each using its own uplink - one for external and another for internal management network.您可以使用相同的交换机(具有 2 个上行链路和针对不同端口组的显式 LBFO 设置)或两个不同的交换机,每个交换机都使用自己的上行链路 - 一个用于外部管理网络,另一个用于内部管理网络。

I think you can keep external management network setup as it is now (same vSwitch, same management port group, the same vmk0 adapter in default TCP/IP stack).我认为您可以保持现在的外部管理网络设置(默认 TCP/IP 堆栈中的相同 vSwitch、相同管理端口组、相同 vmk0 适配器)。 This vmk0 adapter may have IP configuration like this:此 vmk0 适配器可能具有如下 IP 配置:

  • IP: 192.168.5.5/24 IP:192.168.5.5/24
  • GW: 192.168.5.1 - it may be defined for default TCP/IP stack or on vmk0 itself GW:192.168.5.1 - 它可以为默认 TCP/IP 堆栈或 vmk0 本身定义

For internal management network, just create another vSwitch, new management port group and new vmk1 adapter.对于内部管理网络,只需创建另一个 vSwitch、新的管理端口组和新的 vmk1 适配器。 Imagine you want to use internal management network like this:想象一下,你想像这样使用内部管理网络:

  • IP: 10.5.5.5/24 IP:10.5.5.5/24
  • GW: 10.5.5.1 GW:10.5.5.1

Because we cannot have 2 gateways in default TCP/IP stack, you can define gateway directly on vmk1 (this is supported in ESXi 6.5):由于默认 TCP/IP 堆栈中不能有 2 个网关,因此您可以直接在 vmk1 上定义网关(ESXi 6.5 支持此功能):

esxcli network ip interface ipv4 set -g 10.5.5.1 -i vmk1 -t static -I 10.5.5.5 -N 255.255.255.0

Once you do this, I think both internal and external management networks should work for you.一旦你这样做了,我认为内部和外部管理网络都应该适合你。 There may be some edge cases with routing where this scheme may not work, but I think for your use-case it should be fine.路由可能存在一些边缘情况,该方案可能不起作用,但我认为对于您的用例来说应该没问题。

In general there is not a problem with having two or more management interfaces.一般来说,拥有两个或更多管理接口没有问题。 You should to give us some more information about network configuration.您应该向我们提供有关网络配置的更多信息。 Did you change default gateway in host configuration?您是否在主机配置中更改了默认网关? Remember that you may have only one default gateway and if you have changed it to correct for LAN then packets get by public interface not know how to return.请记住,您可能只有一个默认网关,如果您已将其更改为更正 LAN,则通过公共接口获取的数据包不知道如何返回。

If this is the problem you should set default gateway properly for public interface.如果这是问题,您应该为公共接口正确设置默认网关。 But you also need to connect from LAN.但是您还需要从 LAN 连接。 If machines in LAN are in the same network segment - it should just work.如果局域网中的机器在同一个网段 - 它应该可以正常工作。 If machines are in other LAN - add entry to routing table, like described here: https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2001426如果机器在其他 LAN 中 - 将条目添加到路由表,如下所述: https : //kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2001426

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM