Last Modified: Jan 30, 2019
See more info
BIG-IP DNS, GTM, Link Controller
Known Affected Versions:
11.2.1, 11.4.0, 11.4.1, 11.5.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 12.0.0, 12.0.0 HF1
12.1.0, 12.0.0 HF2, 11.6.1, 11.6.0 HF8, 11.5.4, 11.5.1 HF11, 11.4.1 HF10, 11.2.1 HF16
Opened: Nov 10, 2015
Related AskF5 Article: K36385016
In BIG-IP Link Controller and GTM 11.5.3, 11.6.0 and prior versions, and BIG-IP DNS 12.0.0, the inbound ISP link load balancing functionality uses pool members for more than one ISP link per data center.
If a pool has multiple members that use different ISP links within a data center, the system uses only pool members associated with the ISP link of the first available pool member. The system marks pool members associated with subsequent ISP links as unavailable (grey).
Using the inbound ISP link load balancing functionality in BIG-IP Link Controller and GTM 11.5.3, 11.6.0 and prior versions, and BIG-IP DNS 12.0.0.
-- If you reside in the United States and used these EoL load balancing features prior to January 26, 2016: You might be eligible to re-enable the functionality by contacting F5 Support to determine eligibility for requesting a software patch. -- If you reside outside of the United States: Go to downloads.f5.com :: Non-US Patches for BIG-IP and download linkcost.im patch.
The inbound ISP link load balancing functionality will use pool members for only one ISP link per data center for each pool.
Beginning in BIG-IP Link Controller and GTM 11.5.4, 11.6.1, and BIG-IP DNS 12.1.0, the ISP link load balancing functionality will use pool members for only one ISP link per data center for each pool. The link that is associated with the first configured and available pool member within each data center will determine the link that will be used for the data center. The system will use only pool members associated with that link.