Bug ID 1168245: Browser is intermittently unable to contact the BIG-IP device

Last Modified: Mar 24, 2026

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

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, 15.1.10.7, 15.1.10.8, 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, 16.1.6, 16.1.6.1, 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.1.2.2, 17.1.3, 17.1.3.1, 17.5.0, 17.5.1, 17.5.1.2, 17.5.1.3, 17.5.1.4, 17.5.1.5, 21.0.0, 21.0.0.1

Opened: Oct 10, 2022

Severity: 3-Major

Symptoms

When the coloradvisory probes running in the GUI do not receive a response from the BIG-IP device within 30 seconds, the GUI generates a pop-up message "Unable to contact BIG-IP device".

Impact

Browser frequently sees the BIG-IP as unavailable, causing interruptions to management of the device via the GUI.

Conditions

- MCPD is busy serving requests. - Multiple browser connections to the BIG-IP. - HTTP GET request from browser JS for /xui/update/configuration/alert/statusmenu/coloradvisory does not get a response within 30 seconds (default timeout).

Workaround

1. Increase memory allocated to tomcat and restjavad. tmsh modify sys db provision.tomcat.extramb value 512 tmsh modify sys db provision.restjavad.extramb value 2227 Note: these are very large values, not suitable for most systems. Increase tomcat heap size by 50MB a time, and restjavad by 200MB a time (value 600, 800, etc). To have provision.restjavad.extramb values will be capped in effect to 384 + value of provision.extramb. Both tomcat and restjavad need to be restarted to have changes take effect. restjavad will log startup info in ltm log. 2. Adjust the browser-based Javascript status update interval and timeout. 2.1. Remount /usr partition as read-write using the command: mount -o remount,rw /usr 2.2. Edit the file /usr/local/www/xui/framework/scripts/variables.js, and modify the variables: time_updateXui to 8, and timeout_status to 60. Default values are: var time_updateXui = 5; // Seconds var timeout_status = 30; //Timeout value for XUI status update Change these values to: var time_updateXui = 8; // Seconds var timeout_status = 60; //Timeout value for XUI status update 2.3. Remount /usr partition back to read-only. mount -o remount,ro /usr 3. Restart associated daemons: bigstart restart httpd bigstart restart tomcat bigstart restart restjavad

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips