Trunk to Hyper-V hosts won't come up

[Colin Higgins]

I have two 6513s running VSS with Supervisor 2T modules (quad sup VSS SSO)

I want to create a 802.1q trunk (multi-chassis) between the switches and a Microsoft Hyper-V 2012 machine (host).  On the Hyper-V machine, I establish a 4 network adapter team using "switch independent" (not static or LACP config) encapsulation, and within virtual switch manager, assign the new team as a switch. The server creates a special logical (virtual) nic and I give it an Ip address.

On the switch, the trunk is configured like this

interface po34

switchport

switchport mode trunk

switchport trunk native vlan 313

switchport trunk allowed vlan 313,320-322

interface g1/1/1

switchport

channel-group 34 mode desirable

The individual network cards on the server come up, but the port-channel and trunk never come up.

It seems like I have tried everything to get this to work.

Has anyone done this? Can you do a dot1q trunk to a Hyper-V host? (MS says you can). I don't even see anything in the switch logs.

P.S. I can doa LACP etherchannel connection no problem.     

[acampbell]

Colin,

"channel-group 34 mode desirable"

This set the port channel to use PAGP - this is Cisco proprierty

Try setting "channel-group 34 mode active" and that will try LACP

You final option is

"channel-group 34 mode on"  that is no negotiation -just forced ON

Regards,
Alex.
Please rate useful posts.

[Colin Higgins]

If I use LACP, will it function as a 802.1q trunk and carry vlan info to the hyper-v host? I thought that was only for link aggregation with a single layer 3 interface?

If I use the "mode on" option, the links go into a suspended state and the port-channel interface stays down.

[acampbell · Accepted solution]

Colin,

PAGP is used normally JUST between 2 Cisco devices like SWITCH to SWITCH

LACP (mode active or passive - at least one end must be active) This will use 802.1Q trunking if you have configured the "interface port"  it to do that.

LACP can used for either LAYER2 or LAYER 3

This link may help:-

http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/channel.html

Regards,
Alex.
Please rate useful posts.

[Colin Higgins]

OK, I figured it out

On the Hyper-V side, it HAS to be hard-coded to LACP (switch independent or dependent will not work)

On the switch side, you need to use "switchport nonegotiate" and hard-code to LACP as well.