Symptoms
A BIG-IP tenant running on a VELOS system incorrectly reports all "ha-only" trunk objects as up, regardless of the actual status of the trunk.
BIG-IP tenants can also report incorrect status of trunks after the LAG type is changed from LACP to STATIC or vice-versa.
An interface name is displayed as empty when an interface is deleted from a LAG.
As a result of these, high availability (HA) group failover based on trunk status is unreliable and unusable.
Impact
HA group failover based on trunk status is unreliable and unusable for BIG-IP tenants running on an F5OS system.
Conditions
-- LAGs configured on F5OS system.
-- Attempting to use high availability (HA) group failover based on trunk status inside BIG-IP tenant.
Workaround
After configuring a new LAG in the the F5OS partition or changing a LAG type from LACP to STATIC or from STATIC to LACP, reboot the traffic blades.
For rSeries devices, the entire device must be restarted.
After rebooting, the ha-group trunk entries should show the expected values when one or more members are missing from the aggregate link.
Fix Information
This issue has been corrected.
