VMware Cloud Community
acruizu
Enthusiast
Enthusiast
Jump to solution

Fail to implement port channel in cisco 3750 and ESXi 4u1

I configure one vswitch with one uplink and trunking for several vlans. Everything works fine, when the network admin replicate the configuration in a second network port and set up a port channel with both interfaces all my communication with my network management interface is lost, but the management network test from the esxi is sucessfull.

The vswitch is using ip hash and the pswitch use src-dst-ip policy.

Thanks in advance for any help you can provide.

P.D: Here's the Switch configuration:

interface
GigabitEthernet1/0/17
switchport trunk encapsulation dot1q
switchport
mode trunk
switchport nonegotiate
channel-group 3 mode on
spanning-tree
portfast trunk
spanning-tree bpduguard enable

interface
GigabitEthernet1/0/7
switchport trunk encapsulation dot1q
switchport
mode trunk
switchport nonegotiate
channel-group 3 mode on
spanning-tree
portfast trunk
spanning-tree bpduguard enable

interface
Port-channel3
switchport trunk encapsulation dot1q
switchport
mode trunk
switchport nonegotiate
spanning-tree portfast trunk
spanning-tree
bpduguard enable

port-channel load-balance src-dst-ip

0 Kudos
1 Solution

Accepted Solutions
Rumple
Virtuoso
Virtuoso
Jump to solution

Take off allowed vlan 4094....the native should not be part of traffic that will flow over the link...

View solution in original post

0 Kudos
9 Replies
Rumple
Virtuoso
Virtuoso
Jump to solution

One thing you should set is the native vlan to something that will never pass over the trunk (so esx will force tagging)

Next, you need to make sure your vswitch is set to Route Based on IP Hash.

I don't see anything that that actually says what vlans are allowed over that trunk..you should have allowed vlan's or allow all or something I would suspect

0 Kudos
depping
Leadership
Leadership
Jump to solution

I would start with allowing specific VLANs. (should allow all by default I believe though, but seen this go wrong in the past)

Duncan

VMware Communities User Moderator | VCP | VCDX

-


Now available: Paper - vSphere 4.0 Quick Start Guide (via amazon.com) | PDF (via lulu.com)

Blogging: | Twitter:

0 Kudos
acruizu
Enthusiast
Enthusiast
Jump to solution

Thank you! I'll ask my network admin to change the native vland id

trunk native vlan 4094

Also I hear about that Management Port on ESXi U1 does not propage from vswitch0 ( http://communities.vmware.com/message/1449363#1449363 ) ?

Best Regards,

0 Kudos
acruizu
Enthusiast
Enthusiast
Jump to solution

I decided to try to reconfigure one of the server, just one interface in a new vswitch, this is the interface configuration:

interface

GigabitEthernet1/0/13

switchport trunk encapsulation dot1q

switchport

trunk native vlan 4094

switchport trunk allowed vlan 111,4094

switchport

mode trunk

switchport nonegotiate

This is my vswitch1 configuration:

8288_8288.png

Corp is mean to be the native vlan, even If I try to use none as vlanid, neither vm_net(vlan111) or corp (native id4094) doesnt work, the network admin says that the vswitch is not tagging.

Any idea?

I appreciate all the help you can provide,

Best regards,

0 Kudos
Rumple
Virtuoso
Virtuoso
Jump to solution

Take off allowed vlan 4094....the native should not be part of traffic that will flow over the link...

0 Kudos
acruizu
Enthusiast
Enthusiast
Jump to solution

Rumble, a question? you cant use the native vlan in the same trunk? Should I use a separate vswitch for native vlan?

0 Kudos
Rumple
Virtuoso
Virtuoso
Jump to solution

Just make up a vlan...create vlan 666 and then make that the native vlan...but allow 4094 across that link if needed.

0 Kudos
acruizu
Enthusiast
Enthusiast
Jump to solution

Thank you!!!! I just need it to pass my native lan with other vlan id and everything works great!

0 Kudos
Rumple
Virtuoso
Virtuoso
Jump to solution

That native vlan piece gets a lot of people (along with making sure switch is ip src dest and that the port group is route based on ip hash.)

0 Kudos