Bug ID 421317: red pool status not propagated to virtual server when connection or rate limit hit

Last Modified: Oct 06, 2020

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

Known Affected Versions:
10.0.0, 10.1.0, 10.2.0, 10.2.1, 10.2.2, 10.2.3, 10.2.4, 11.0.0, 11.1.0, 11.2.0, 11.2.1, 11.3.0, 11.4.0, 11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4

Fixed In:
11.6.0, 11.5.1 HF5, 11.4.0 HF3, 11.3.0 HF6

Opened: May 16, 2013
Severity: 3-Major
Related AskF5 Article:


A virtual server's default pool status is red, but the virtual server's status is yellow.


The virtual server will display an incorrect status (yellow, when the virtual is unable to load-balance to an available pool member). If route advertisement is enabled for the virtual address corresponding to the virtual server, a route could be advertised for virtual servers that are unable to process traffic.


The virtual server has exceeded either a connection limit or rate limit, and the pool's status is red.



Fix Information

Virtual servers now correctly display a red status when its default pool's status is red, regardless of whether or not a connection or rate limit for the virtual server have been reached.

Behavior Change