Last Modified: Aug 08, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 12.1.4, 126.96.36.199, 12.1.5
Opened: May 09, 2018
During the BIG-IP system boot-up, waagent is unable to get a response from the intended wire server endpoint, which stops it from running custom script extensions. This happens because of the missing route to the Azure virtual public IP address of 188.8.131.52. The var/log/waagent.log contains error messages similar to the following: -- INFO Protocol endpoint not found: WireProtocol, [ProtocolError] [Wireserver Exception] [HttpError] [HTTP Failed] GET http://n.n.n.n,n.n.n.n/?comp=versions -- IOError [Errno -3] Temporary failure in name resolution -- 6 attempts made
waagent custom script extensions do not complete, failing the BIG-IP provisioning that waagent intends to perform during startup.
-- BIG-IP system is deployed in Azure VNet with a custom DNS server. -- The DHCP server has assigned a classless-static-route in its dhclient lease (/var/lib/dhclient/dhclient.leases) which contains a custom route to 184.108.40.206.
Add 220.127.116.11 route on mgmt interface during BIG-IP system initialization to facilitate correct waagent custom script extension execution.