LACP – Static LACP on HP Switch with Multiple VLANs

Assuming the other side of Gi 0/1 is also a GigabitEthernet, the most likely cause is a bad cable. You need a cable with all four pairs connected. 100M will work with only two pairs. That is probably why you negotiate to 100M.

For more info on how GE uses all four pairs, see: http://goo.gl/DMYkSM

this behaviour is because you begin to tag frames from the vSwitch and the Switch HP procurve Core SW is not tagging VLAN 1, this is usual because VLAN 1 is most frequently the default VLAN or Native VLAN. In most environments this VLAN is not tagging.

To make this work right:

1)you must untagged VLAN 1 in the vSwitch, and tag all the others VLAN that you want to create.

2) other option: you can tag VLAN 1 in your vSwitch and in the HP procurve Core SW.

I would prefer first option, but its matter of taste.

I Hope Helps!