VMware Cloud Community
Kumatech
Contributor
Contributor

VmWare i3 Nic Teaming Details Question

Hello,

I see that enabling nic teaming in vmware esx3.5 (i3 with 3 hosts), is a joke. Each of my hosts has a second nic ready to be used in a team. As far as I can see it seems like there are no issues related to configuring this.

My question is... When I enable nic teaming do I have to make sure my switches enable generic trunking? Is there some kind of walk through for this aspect of the configuration? In other words, do I need to makes sure I have manageable switches so the ports can be configured with the virtual mac address of the team and apply the same uplinking configuration to other switches in the LAN so I am truly using this aggregation in a large switches environment? Am I making this far more complicated that it is in reality? Let me know!

0 Kudos
4 Replies
Texiwill
Leadership
Leadership

Hello,

I see that enabling nic teaming in vmware esx3.5 (i3 with 3 hosts), is a joke. Each of my hosts has a second nic ready to be used in a team. As far as I can see it seems like there are no issues related to configuring this.

Yes it is easy.

My question is... When I enable nic teaming do I have to make sure my switches enable generic trunking? Is there some kind of walk through for this aspect of the configuration? In other words, do I need to makes sure I have manageable switches so the ports can be configured with the virtual mac address of the team and apply the same uplinking configuration to other switches in the LAN so I am truly using this aggregation in a large switches environment? Am I making this far more complicated that it is in reality? Let me know!

Depends on how you have to set things up. If you use VST, then both links to your pSwitches must trunk the same VLANS. So yes you need to fix this. However you are mistaken, you only get load balancing across a NIC Team (if you choose to do this) not aggregation.

However, with only 2 pNICs you may have security issues at hand and may want more pNICs to make your installation more secure.

Check out the VMware Whitepaper on 802.1q (VLANS) for information on trunking, etc.


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.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

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

So let me see if I understand this correctly. Say for example I have 3 Virtual Swtiches each with 2 physical NICS using VST I would have to trunk 1 or three ports per ESX Host?

1. vSwtich 0

1.Service Console VLAN 10

2. VM Network (Backup) VLAN 40

vSwtich 1

1. VMkernal VLAN20

vSwtich2

1. VM network VLAN 30

i know i should have redundant Service Console port but have not got around to implementing.

Mike

0 Kudos
TomHowarth
Leadership
Leadership

So let me see if I understand this correctly. Say for example I have 3 Virtual Swtiches each with 2 physical NICS using VST I would have to trunk 1 or three ports per ESX Host?

1. vSwtich 0

1.Service Console VLAN 10

2. VM Network (Backup) VLAN 40

you would create two port groups on this vSwitch and tag the traffice with 10 and 40 respectively. you would then create a switch trunk on your physical switch that passed 40 and 10. you would configure the vNICs as ServiceConsole VMNIC0 live failover to VMNIC1 and VM Network VMNIC1 live VMNIC0 failover.

vSwtich 1

1. VMkernal VLAN20

You would configue your phyiscal switch ports as a trunk configured to pass VLAN20 and mark your vSwitch with tag 20

vSwtich2

1. VM network VLAN 30

You would configue your phyiscal switch ports as a trunk configured to pass VLAN30 and mark your vSwitch with tag 30

i know i should have redundant Service Console port but have not got around to implementing.

That is correct you will have rudundancy and resilliance on all vSwitches

If you found this or any other answer useful please consider the use of the Helpful or correct buttons to award points

Tom Howarth

VMware Communities User Moderator

Blog: www.planetvm.net

Tom Howarth VCP / VCAP / vExpert
VMware Communities User Moderator
Blog: http://www.planetvm.net
Contributing author on VMware vSphere and Virtual Infrastructure Security: Securing ESX and the Virtual Environment
Contributing author on VCP VMware Certified Professional on VSphere 4 Study Guide: Exam VCP-410
0 Kudos
Kumatech
Contributor
Contributor

Hey Guys,

I just wanted to let you know FYI, I have not abandoned the post, I have been sidetracked with some work and waiting for the client to send their HpProcurve switch credentials. I want to apply what I've read and use the thread to address any further issues once I apptempt to impliment it in the real world. Please be patient I will close up this post at some point in the near future!

Thanks for the info.... Ed... I like the credentials, very impressive!

0 Kudos