I couldn’t find how to do this via the web GUI (hate the new 5400 web console - what happened to the performance graphs??) – anyhow this is the commands to do it via commandline…
5406zl-A# show vlan 200 Status and Counters - VLAN Information - Ports - VLAN 200 VLAN ID : 200 Name : VLAN200 Status : Port-based Voice : No Jumbo : No
5406zl-A# configure 5406zl-A(config)# vlan 200 jumbo 5406zl-A(config)# end 5406zl-A# sho vlan 200
Cisco’s Etherchannel and HP’s LACP are very similar – probably why I assumed both are supported by vmware. But as per below – it is not the case.
From a procurve perspective the differences between a “trunk” and “static lacp” trunk is the total bandwidth per connection. A typical end point on a “trunk” trunk can transmit various connections down both pipes, but only receive down one – sometimes refered to as TLB (transmit load balancing). In vmwares case when you are using a “trunk” trunk you will have ip hash set as a load balancer, effectively meaning a different nic will be used on the vmware side for each connection a virtual machine makes.