Bug ID 853585: REST Wide IP object presents an inconsistent lastResortPool value

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5,,,, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,,,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 15.1.0,,,,,, 15.1.1, 15.1.2, 16.0.0,, 16.0.1

Fixed In:
16.1.0,,, 14.1.4,, 12.1.6

Opened: Nov 27, 2019

Severity: 3-Major


The output of a REST call to tm/gtm/wideip/<wideip_kind> returns objects that contain inconsistent values for the property 'lastResortPool'. For instance, for the kind 'aaaa', the output might be: ... "lastResortPool": "aaaa \"\"" ...


The lastResortValue in the REST response might be confusing for an external orchestrator that consumes the BIG-IP configuration via iControl REST. BIG-IQ, for instance. BIG-IQ might not work as expected with these values.


The BIG-IP admin has modified a Wide IP object via tmsh and used the following command structure: tmsh modify gtm wideip <wideip_kind> www.example.com last-resort-pool <pool_kind>


Change the Wide IP object via the GUI and set the Last Resort Pool to None, then save the changes.

Fix Information

The tmsh interpreter now enforces the structure 'tmsh modify gtm wideip <wideip_kind> www.example.com last-resort-pool <pool_kind> <pool_name>'.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips