Last Modified: Feb 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2, 17.1.2.1, 17.5.0
Opened: Dec 03, 2024 Severity: 2-Critical
- Dossier creation fails with the following errors in the BIG-IP VE LTM log file: err chmand[4610]: 012a0003:3: DossierReq exception: VirtDossier Service: Instance identity retrieval from the metadata failed. Check network connectivity to the instance metadata before retrying warning get_dossier[10914]: 012a0004:4: hal_request_dossier: request failed err get_dossier[10914]: 01170003:3: halGetDossier returned error (1): Dossier generation failed. - Installing a license from a BIG-IQ returns with an error similar to the following: Licensing failed Assignment of regkey pool license {license_pool_name} (License for XXXXX-XXXXX-XXXXX-XXXXX-XXXXXXX) to N.N.N.N ended with INSTALLATION_FAILED status and message: Failed to install license to device N.N.N.N (Not a valid F5 License)
- BIG-IP fails to generate a dossier and load a license - BIG-IQ is unable to re-license the VE
Any of these license removal scenarios trigger the issue on a Single NIC (1nic) AWS BIG-IP VE : - Previous license has expired - License was revoked using iControl REST command "DELETE /tm/shared/licensing/registration" - License was revoked using BIG-IQ
Fix by deleting and resetting IP routing. 1) tmsh delete net route default 2) bigstart restart dhclient Alternatively manually modify and fix ip route 1) ip route change default via <gateway> dev internal Where <gateway> is IP address seen in 'ip route' output for 'default'. Ex: for following, <gateway> is 172.31.0.1 # ip route default via 172.31.0.1 dev mgmt default via 172.31.0.1 dev mgmt proto none metric 4096 ...
None