Forum Discussion
amsh_4376
Nimbostratus
NimbostratusTrunk down and interfaces unitialized
I have a BIG-IP VE 11.2 running on VMWARE ESXi Vsphere 5. In BIG-IP, i can see three interfaces (1.1,1.2 and 1.3). 1.3 configured for HA and trunk (1.1+1.2) for traffic (one armed mode).
When these interfaces are configured as members of trunk, these interfaces are unitialized and trunk status is down.
Is this a bug or am i missing any configuration?
Laudec_55181Altostratus
Are you using LACP? If so, LACP is not supported. Other than that, trunking works on the VE.
amsh_4376There is no LACP option, while configuring trunks in BIG-IP
These are the steps i followed to configure trunks:
1. Interface 1.1 shown as unitialized
2. Trunks tab: Name Trunk_DATA , Assigned 1.1 interface in the members and all other values kept default
3. Vlans tab: Available as Trunk_DATA* shown, assigned to the tagged column in Resources tab, Clicked Finished. Error pops up : "01070734:3: Configuration error: vmw-compat: vlan member type must be an interface"
JB_106099this is a very old post, has this been resolved? I am having the same issue.
nitassEmployee
i understand trunk and lacp is still not supported in virtual edition.
stan_peachey_86Cirrus
I have the same issue described above with VE 11.6.0. Is trunk still not supported? Is there a work-around to trunk multiple vlans over f5 VE interface?
Thong_19681611.6 - what abut try to uncheck the LACP option?
cybershoeTrunking multiple VLANs is supported, you just assign multiple VLANs as "tagged" on the same interface. Just make sure your hypervisor isn't stripping VLAN tags and you're good to go.
In F5 parlance, a "trunk" refers to a LAG or port channel, which is where LACP comes in to play (and is not supported in VE). This difference in terminology has confused more than one user coming from the Cisco world :)