Comments on: VMware ESX, NIC Teaming, and VLAN Trunking with HP ProCurve http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/ The weblog of an IT pro specializing in virtualization, storage, and servers Wed, 08 Feb 2012 17:13:47 +0000 hourly 1 http://wordpress.org/?v= By: Shaun Clarke http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-51651 Shaun Clarke Tue, 20 Sep 2011 23:50:58 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-51651 Just wanted to say thanks for the post - very informative. I work with ProCurve switches mainly and remember being totally stumped as to what a 'Native VLAN' was - wish I found this article back then! Just wanted to say thanks for the post – very informative.

I work with ProCurve switches mainly and remember being totally stumped as to what a ‘Native VLAN’ was – wish I found this article back then!

]]> By: slowe http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-51645 slowe Tue, 20 Sep 2011 16:26:39 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-51645 Pep, this post is about how to make VLAN trunking work between VMware ESX/ESXi and HP ProCurve switches. I don't have any clue how to perform IP filtering on an HP switch. Good luck to you! Pep, this post is about how to make VLAN trunking work between VMware ESX/ESXi and HP ProCurve switches. I don’t have any clue how to perform IP filtering on an HP switch. Good luck to you!

]]> By: pep http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-51644 pep Tue, 20 Sep 2011 16:17:34 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-51644 I dont know if anyone can help me with this. Here it goes: I have a port Nº 12 on 2524 HP and I only want 3 specific IP pass this port. or in an Enterasys ge.1.33 3 specific IP. Could you please send me the code for both. Thank you. Best regards. I dont know if anyone can help me with this. Here it goes:

I have a port Nº 12 on 2524 HP and I only want 3 specific IP pass this port.

or in an Enterasys ge.1.33 3 specific IP.

Could you please send me the code for both. Thank you.

Best regards.

]]> By: donkarnash http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-50231 donkarnash Tue, 08 Feb 2011 04:44:24 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-50231 When I login to the switch and go to switch configuration and set the ports to trnk1 trunk, I can't ping thru the backup network When I login to the switch and go to switch configuration and set the ports to trnk1 trunk, I can’t ping thru the backup network

]]> By: donkarnash http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-50230 donkarnash Tue, 08 Feb 2011 02:22:43 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-50230 Hi, I have a procurve switch 2510G-24 connected to DL380G6 servers which host ESXi on them. The server has 4 NIC's and two of them are connected directly to the procurve switch for backup and vmotion. The idea is to have the nic's in team so backup (I need to backup about 10T on monthly and about 100G incremental bckp on daily bases) and vmotion can use the same team. I have created two VLAN's on the procurve switch. 5 for bkp and 8 for vmotion. Then from the backup server, I have created a HP team and connected the nics to the switch and configured VLAN 5 on the server for backup traffic. On VLAN configuration, I added the dvport group of backup nic as TAGGED. so for me, port 3,5,7 are for backup with vlan id 5 and 13,15,17 are for vmotion. When I migrate the vm's I see traffic thru the 13,15,17 ports. Its the backup that is causing massive problems. EMC have spent months trying to find out what could be the problem and they say its the backup network. The throughtput of the backup ports are v v low and traffic is sent as multicast (i don't know what that means) Under the network configuration of the host, I see observed traffic as "none" I also see excessive broadcase on these ports. The corporate network people tell me the switch is causing major traffic issues and is bradcasing in muticast, which I don't understand. Can someone please guide me on what can I do to resolve this. Many thanks Hi,

I have a procurve switch 2510G-24 connected to DL380G6 servers which host ESXi on them.

The server has 4 NIC’s and two of them are connected directly to the procurve switch for backup and vmotion. The idea is to have the nic’s in team so backup (I need to backup about 10T on monthly and about 100G incremental bckp on daily bases) and vmotion can use the same team.

I have created two VLAN’s on the procurve switch. 5 for bkp and 8 for vmotion. Then from the backup server, I have created a HP team and connected the nics to the switch and configured VLAN 5 on the server for backup traffic. On VLAN configuration, I added the dvport group of backup nic as TAGGED. so for me, port 3,5,7 are for backup with vlan id 5 and 13,15,17 are for vmotion. When I migrate the vm’s I see traffic thru the 13,15,17 ports.

Its the backup that is causing massive problems. EMC have spent months trying to find out what could be the problem and they say its the backup network. The throughtput of the backup ports are v v low and traffic is sent as multicast (i don’t know what that means)

Under the network configuration of the host, I see observed traffic as “none”

I also see excessive broadcase on these ports.

The corporate network people tell me the switch is causing major traffic issues and is bradcasing in muticast, which I don’t understand.

Can someone please guide me on what can I do to resolve this. Many thanks

]]> By: Craig http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-50155 Craig Mon, 31 Jan 2011 09:19:11 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-50155 Thank you Tom Ranson, I had the exact same issue with losing network connectivity to the host management network. Thank you Tom Ranson, I had the exact same issue with losing network connectivity to the host management network.

]]> By: slowe http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-49979 slowe Fri, 07 Jan 2011 13:55:53 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-49979 Mimmus, thanks for the update! Mimmus, thanks for the update!

]]> By: Mimmus http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-49974 Mimmus Fri, 07 Jan 2011 09:07:31 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-49974 UPDATE to above post: the author says that "dt-lacp" *should* work with VMware but he cannot recommend the configuration in the original post. UPDATE to above post: the author says that “dt-lacp” *should* work with VMware but he cannot recommend the configuration in the original post.

]]> By: Mimmus http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-49543 Mimmus Tue, 23 Nov 2010 11:25:57 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-49543 Just a note to say that HP seems to have a Distributed Trunking (cross-switch etherchannel in Cisco words) feature now and it works with ESX: http://www.vnephos.com/index.php/2009/09/hp-procurve-cross-stack-etherchannel/ Author says that it works although HP chose to use “dt-lacp” as the configuration parameter name and LACP is notoriously unsupported on ESX. Just a note to say that HP seems to have a Distributed Trunking (cross-switch etherchannel in Cisco words) feature now and it works with ESX:
http://www.vnephos.com/index.php/2009/09/hp-procurve-cross-stack-etherchannel/
Author says that it works although HP chose to use “dt-lacp” as the configuration parameter name and LACP is notoriously unsupported on ESX.

]]> By: Alex http://blog.scottlowe.org/2008/09/05/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/comment-page-1/#comment-49293 Alex Tue, 05 Oct 2010 07:34:46 +0000 http://blog.scottlowe.org/2008/08/26/vmware-esx-nic-teaming-and-vlan-trunking-with-hp-procurve/#comment-49293 @Paul. You don't say if your ESX hosts are plugged into the same switch or 2 different switches. Thanks @Paul. You don’t say if your ESX hosts are plugged into the same switch or 2 different switches. Thanks

]]>