VMware Cloud Community
fusebox
Enthusiast
Enthusiast

Quick Question - ESX Networking - VLANs,Trunking,NIC Teaming

I have teamed the 2 uplinks , assigned it to to a vswitch and then created two port groups ( vlan 85 & 86) as shown in the screenshots.On the physical switch side,we have the trunk port(s) and 802.1q setup.

The issue I am facing is,when I remove one of the physical links,I am not able to access the VLAN 86. So,in short what should the settings be on the esx end to ensure the VLAN traffic for 85 & 86 are accessible if one of the nic goes down. Am I missing something? Any help would be appreciated..It is very critical to fx this...

Thanks.

Reply
0 Kudos
6 Replies
Texiwill
Leadership
Leadership

Hello,

You want to employ VMware NIC Teaming and not 802.3ad. THere is no need for etherchannel. Not sure if that is the culprit but I would disable that for starters.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill
Reply
0 Kudos
fusebox
Enthusiast
Enthusiast

Thanks for the reply Texiwill...A small correction.My mistake......There is no etherchannel setup..Its actually VLAN Trunking (802.1 Q) and the trunk ports are setup as required...So,what do I check now from esx and pswitch end?

Reply
0 Kudos
dominic7
Virtuoso
Virtuoso

You see in that first screenshot where is has a field called "observed network ranges" grab the seperator on thr right side of that field and extend it as far as you can then you should see all the VLANs that are availble to that physical nic. Make sure that both vlan85 and vlan86 are in there and you should be good to go.

fusebox
Enthusiast
Enthusiast

That is exactly what bothering Me. I do see both the VLANs for both the teamed nics.That means,its fine from the esx side.And,the network team says they have the trunk setup fine on their switch..Now,I have doubts about that...Maybe some setting is missing or done incorrectly....I have one more question,just a clarification .....Does the load balancing setting need to be in,"according to port group id" or "source based ip hash" ?

Is there anything specific I can ask,the network folks to recheck from their end?

Reply
0 Kudos
fusebox
Enthusiast
Enthusiast

ok.This issue is resolved now. Made sure the trunk was fine,both the VLANs were visible to both the nics and most importantly ENABLED PORTFAST on the pswitch and made sure the spanning tree is disbaled. After,these changes were confirmed on the pswitch,when I pull out the cable from one of the nics,I am able to access both the VLANs from the uplink which is up and running.

Thanks to everyone.

Reply
0 Kudos
Texiwill
Leadership
Leadership

Hello,

It is either Enable Portfast with STP enabled or disable STP altogether. No need to enable PortFast if STP is disabled. But enabling PortFast will cover your bases if STP is suddenly enabled as well.


Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

CIO Virtualization Blog: http://www.cio.com/blog/index/topic/168354

As well as the Virtualization Wiki at http://www.astroarch.com/wiki/index.php/Virtualization

--
Edward L. Haletky
vExpert XIV: 2009-2023,
VMTN Community Moderator
vSphere Upgrade Saga: https://www.astroarch.com/blogs
GitHub Repo: https://github.com/Texiwill