Last Modified: Oct 10, 2025
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
17.5.1
Fixed In:
17.5.1.2
Opened: Jul 14, 2025 Severity: 3-Major
When using REST API to issue commands to a BIG-IP system and specifying the API version to use, BIG-IP v17.5.1 does not recognize v17.5.0 as a supported version and raises an error: "Version 17.5.0 is not supported" This causes BIG-IQ to no longer be able to discover a BIG-IP running on 17.5.1
Any REST API query sent to a BIG-IP v17.5.1 fails if it has 'ver=17.5.0' in the query string. This leads to an unreliable REST API on BIG-IP v17.5.1. One such business impact is that BIG-IPs become unmanageable from BIG-IQs as the REST API queries are still using v17.5.0 API version in them.
1. A REST API query is sent to a BIG-IP v17.5.1 system 2. This REST API query uses v17.5.0 API version by including 'ver=17.5.0' in the query string.
When sending a REST API query to BIG-IP v17.5.1, use a different available API version other than v17.5.0. For ex. Instead of 'ver=17.5.0', use 'ver=17.1.1'. restcurl -u admin "/tm/sys/provision/urldb?ver=17.5.0" restcurl -u admin "/tm/sys/provision/urldb?ver=17.1.1"
BIG-IP v17.5.1 now recognizes v17.5.0 as a supported version in the context of REST API commands