configure multiple networks for ESXi

[jnsvano]

Hello All,

I'm not strong in Vmware networking, just need to return back to life ESXi 6.7 server, once was working ok. It has only one physical NIC once connected to Aruba/HP switch, but which port nobody remembers. Server has virtual machines from networks A and B.

So, network A is also management network, and when I connect server to untagged Network A port, web interface and vm's from that network work OK. I added same Aruba port as tagged for Network B, but no luck.

Network B has it's own Portgroup and vSwitch, I tried set Vlan Id for Portgroup, but doesn't help. vSwitch's security settings are: Promiscuous mode Reject, MAC address changes Accept and Forged transmits Accept.

So, how I must configure Aruba port ?

[josephjoy]

Are both  A and B network port of same VLAN ? was there any VLAN trunking at the swtich level , have you checked it ?

[jnsvano]

I think "tagged ports" on Aruba is the same as "VLAN trunking" on Cisco. I did check, and put either both ports to "tagged", or network A to untagged and network B to tagged, it didn't help.

[EarleE1]

Click Virtual Machines in the VMware Host Client inventory. Right-click a virtual machine in the list and select Edit settings from the pop-up menu. Click the Virtual Hardware tab and click Add network adapter. In the network connection panel, select either a network with a specific label or a legacy network.

 

 

[sguadamu1]

Hello.

You are having access to the management because you are using the VMkernel for management, VMware has vmkernel for differente purposes, and one of it is management. You can check the vmkernel configuration in the ESXi host and once you identify the vmkernel, yu can determine the vmnic (physical adapter) that is it using for this purpose. 

Also, you need to be sure how many vmnic does the host has, and you need to check the configuration in the DVS, checking the DVS you are going to check the vmnic adapter configuration. My advice will be to configure the interfaces as trunk to confirm that the connectivity between the host and the TOR switch is working fine. Once it is confirmed, please change to config to the required vlan tagging.

Best Regards.

SG

 

[Dragan Ilic]

Can you pls share exact model of your Aruba switch, so we can confirm required port config for it?

Thank you,

Dragan

[CostasKon]

Hi,

i used to checked oldies a similar case with a server having same config as yours and i did a portgroup assignment with the special vlan tag 4095 on esxi PGrp.  and set trunk to trunk allowance on the switches as i didnt had access on a locked switch over a takeover till the owners decide as i recall and worked for this occasion.

BR,

Costas

[sarafoster]

To configure the Aruba port for Network B, you need to set it up as a tagged VLAN port. Here are the steps you can follow:

1. Log in to the Aruba/HP switch's web interface or CLI.
2. Find the port that is connected to the ESXi server and set it up as a tagged port for the VLAN that Network B is using.
3. On the ESXi host, go to the Networking section and click on the vSwitch that Network B is connected to.
4. Click on the "Add Networking" button and select "VMkernel Network Adapter".
5. Choose the vSwitch that Network B is connected to and click "Next".
6. Select "Use VLAN ID" and enter the VLAN ID that Network B is using.
7. Configure the IP settings for the VMkernel adapter.
8. Verify that the VMs on Network B can connect to the network.

Make sure that you have configured the VLAN settings correctly on the switch and the ESXi host. If you still have issues, you can check the ESXi host's logs to see if there are any errors related to networking.

 

[vmkfix-SSA]

 

 

https://vmkfix.blogspot.com/2023/03/nics-are-not-detected-traffic-on-esxi.html