Aruba & ProVision-based
1753902 Members
9874 Online
108810 Solutions
New Discussion

Re: 3400cl and ESXi 5.0 trunking

 
SOLVED
Go to solution
kurtbuff
Occasional Contributor

3400cl and ESXi 5.0 trunking

All,

 

I have a new VMware ESXi 5.0 server that I'm trying to set up for trunking with my 3400cl. I can ping and connect with the server when the 4 NICs from the server are connected the switch and the ports to which they are connected are tagged to the VLAN, but as soon as I trunk the ports (trunk 1-4 trk1 trunk) and tag the trunk to the VLAN I lose connectivity.

 

The relevant fragment of the non-working configuration are below.

 

Thanks,

 

Kurt

 

interface 1
   no lacp
exit
interface 2
   no lacp
exit
interface 3
   no lacp
exit
interface 4
   no lacp
exit
interface 7
   no lacp
exit
interface 8
   no lacp
exit
trunk 1-4 Trk1 Trunk
trunk 7-8 Trk2 Trunk
ip routing
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   ip address dhcp-bootp
   no untagged 5-6,9-48,Trk1-Trk2
   exit
vlan 110
   name "VLAN110"
   untagged 5-6,9-17,19-48,Trk2
   ip address 192.168.10.1 255.255.255.0
   tagged Trk1
   exit

4 REPLIES 4
paulgear
Esteemed Contributor

Re: 3400cl and ESXi 5.0 trunking

What load-sharing mode are you using on the ESXi vSwitch? You should be using route based on IP hash.
Regards,
Paul
kurtbuff
Occasional Contributor

Re: 3400cl and ESXi 5.0 trunking

Route based on IP Hash is set, and all 4 NICs attached to the vswitch are set as active.

 

If I merely tag ports 1-4 in the VLAN, I get connectivity, but as soon as I trunk them, I can't ping the server, either from the serial console on the switch or a machine attached to the swtich.

 

Kurt

kurtbuff
Occasional Contributor
Solution

Re: 3400cl and ESXi 5.0 trunking

I found it. The route settings on the Management port group didn't match the route settings on the vswitch.

 

Once both of those had been set to route based on IP hash, I got connectivity.

paulgear
Esteemed Contributor

Re: 3400cl and ESXi 5.0 trunking

Good to hear you've got it solved!  Thanks for taking the time to document your solution.

Regards,
Paul