On Tue, Aug 21, 2012 at 5:03 PM, Joseph L. Casale <[email protected]> wrote: >> went back to the article linked above, and set up NIC teaming with IP >>HASH and made sure that all four NICs were active, then tried setting >>up the trunk again, and again had no success. >> >>Does anyone have thoughts regarding what I might be missing? > > I'm looking at two esxi servers done this very way with an HP as well. > > The Route based on IP hash with "trunk" not LACP mode is well doc'ed for > procurves. I then have all the exposed vlans tagged on the HP. Finally, the > port groups are each tagged into their respective vlan. > > Each server has the vmk port in its own vswitch tagged into the esxi mgmt > vlan as well. So mgmt, storage, various production traffic is all segmented. > > One thing I had to do was set the duplex on all the interfaces to G/full. No > matter the vendor, Intel and Broadcoms all needed this... > > hth, > jlc
I'm not sure it does, but I'll try setting the duplex/speed statically on the switch and server and see if that gets me anywhere. Definitely trk1 is in trunk (non-LACP) mode. This is the initial config of this server, and the switch it's being configured against is my shelf spare - just three VLANs, currently - VLANs 1, 110 and 111. VLAN 110 is the same number as my server VLAN in production VLAN 111 is to test connectivity from a different subnet, so it won't be tagged to trk1 VLAN 1 is the default VLAN, and I'm keeping everything out of it, and it's the native VLAN. Below are two configs of the switch - one that has trunking but doesn't work, and the other that doesn't have trunking but does work - the configuration of the server is the same for each - a single vswitch with the management network and VM network on it. This machine has no local storage, it's booting from flash, so there are no VMs yet. Just the four active NICs set up with teaming based on IP HASH. Kurt ----------Begin non-working trunked config---------- hostname "ProCurve Switch 3400cl-48G" interface 1 no lacp exit interface 2 no lacp exit interface 3 no lacp exit interface 4 no lacp exit trunk 1-4 Trk1 Trunk ip routing snmp-server community "public" Unrestricted vlan 1 name "DEFAULT_VLAN" ip address dhcp-bootp no untagged 5-48,Trk1 exit vlan 110 name "VLAN110" untagged 5-17,19-48 ip address 192.168.10.1 255.255.255.0 tagged Trk1 exit vlan 111 name "VLAN111" untagged 18 ip address 67.50.118.1 255.255.255.0 exit spanning-tree Trk1 priority 4 ----------End non-working trunked config---------- ----------Begin working non-trunked config---------- hostname "ProCurve Switch 3400cl-48G" ip routing snmp-server community "public" Unrestricted vlan 1 name "DEFAULT_VLAN" untagged 1-4 ip address dhcp-bootp no untagged 5-48 exit vlan 110 name "VLAN110" untagged 5-17,19-48 ip address 192.168.10.1 255.255.255.0 tagged 1-4 exit vlan 111 name "VLAN111" untagged 18 ip address 192.168.11.1 255.255.255.0 exit ----------End working non-trunked config---------- ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
