Last Modified: Jul 12, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
15.0.1, 15.0.0, 14.1.3, 14.1.2.8, 14.1.2.7, 14.1.2.6, 14.1.2.5, 14.1.2.4, 14.1.2.3, 14.1.2.2, 14.1.2.1, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.4, 13.1.3, 13.1.1, 13.1.0, 12.1.6, 12.1.5, 12.1.4
Fixed In:
15.1.0, 14.1.3.1
Opened: May 07, 2018 Severity: 3-Major
A Virtual server will respond to client SYN packets with RST and note an internal F5 reset cause of "VIP disabled (administrative)" despite having resources available or fallback functionality configured.
Client traffic is rejected by virtual server despite it's ability to successfully handle the traffic.
There are a number of different scenarios where this can occur: 1. All pool members marked administratively down, HTTP profile and Fallback Host configured 2. All pool members marked administratively down, iRule configured to select a different, available pool. 3. Pool members available, pool member status modified by ConfigSync operation.
There are different workarounds based on the scenario: 1. If all pool members are marked administratively down, ensure at least one pool member is in a different state (Available, Offline etc). 2. If one or more pool members are available and a ConfigSync operation caused the behavior, fail over to the Standby BIG-IP and reboot the affected BIG-IP.
N/A