Problem with external communication on ESXi
Moderator: mike
-
- Posts: 2
- Joined: Wed Nov 02, 2022 11:19 pm
Problem with external communication on ESXi
I've installed the community edition on a VMWare cluster in its own port group. Promiscuous mode is enabled on the port group. The gateway is an SVI on an external switch which also provides dhcp. I can connect to the GUI and the management sessions for the nodes. When I configure the first router in a topology and connect it to cloud 0 it receives an ip address but I can't ping the gateway or connect to anything on the other side of it. A vpc also connected to cloud 0 is not able to get an ip address from the dhcp server. I was able to get this working in a VMWare Workstation install but ESXi is giving me fits. Wireshark packet captures are also not working. Any suggestions?
-
- Posts: 5179
- Joined: Wed Mar 15, 2017 4:44 pm
- Location: London
- Contact:
Re: Problem with external communication on ESXi
1. your EVE must not use ESXi NIC Team
2. Promiscue all 3 security settings must be allowed
3. if vSwitch has not enabled Promiscue 3 security settings then it can be issue as well.
4. this all is described in the Cookbook chapter about Clods and networking
5, Wireshark also has no issues here, just need on the pc from where you doing Wireshark make Putty SSH session to the EVE, it will offer you to save a kefinger key, after wireshark will work from this PC to the EVE
2. Promiscue all 3 security settings must be allowed
3. if vSwitch has not enabled Promiscue 3 security settings then it can be issue as well.
4. this all is described in the Cookbook chapter about Clods and networking
5, Wireshark also has no issues here, just need on the pc from where you doing Wireshark make Putty SSH session to the EVE, it will offer you to save a kefinger key, after wireshark will work from this PC to the EVE
-
- Posts: 2
- Joined: Wed Nov 02, 2022 11:19 pm
Re: Problem with external communication on ESXi
Nic teaming was set up on the vSwitch. I broke this port group out on to a separate vSwitch with a single nic and that fixed the issue. Thanks for the help.