Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
13.1.0, 12.1.3, 11.6.3
Opened: Feb 14, 2017
Related AskF5 Article: K85772089
Removing a pool from a virtual server does not update the virtual server's status.
The virtual will appear to be associated with a monitored pool when it is not. This should have no functional impact on the virtual server, since a virtual server without a pool has no traffic to pass, and associating a pool with the virtual server will reflect the pool status.
1) Create a pool and assign a monitor to it. 2) Ensure the pool goes green. 3) Create a virtual server without assigning the pool to it. 4) Ensure the virtual server stays blue (unknown). 5) Associate the pool to the virtual server. 6) Ensure the virtual server goes green (available). 7) Remove the pool from the virtual server. 8) The virtual server should go back to blue (unknown); however, it doesn't and stays green.
Restart the BIG-IP system. The status should be blue/unchecked once again after the BIG-IP is restarted. Note: Restarting the BIG-IP system might have an impact on existing traffic. Because this issue is cosmetic, this workaround is not recommended for BIG-IP systems in production.
Associating a pool with the virtual server now correctly updates the virtual server status.