Last Modified: Apr 10, 2019
See more info
Known Affected Versions:
11.3.0, 11.4.0, 11.4.1, 11.5.0
11.5.1, 11.5.0 HF1, 11.4.1 HF4, 11.3.0 HF9
Opened: Feb 07, 2014
Related AskF5 Article: K15599
Occasionally, customers cannot log on their BIG-IP VEs. This happens on VEs hosted by Hyper-V where the host storage used to back VMs is a remote storage. The VE guest seems "frozen". Pinging <mgmt-ip> still works. Long-lived SSH sessions (opened prior freeze) may or may not appear to work. BIGIP VE is not passing traffic and it's not possible to power off VE. Resetting BIG-IP VM is the only option to allow it to "unfreeze".
BIGIP VE is not functional - it cannot pass traffic and users cannot log on it.
BIG-IP VE on Windows Sever 2012/2012R2 (Hyper-V). VEs are deployed using remote storage. OS is booted up using EMC storage via iSCSI. BIG-IP dual-node HAs are configured between VMs running in the same host. Hyper-V cluster and failover storage are configured too.
Use local host storage to back VMs running on Hyper-V (Windows 2012/2012R2).
The emulated IDE storage driver has been replaced with PV (para-virtualized) SCSI storage driver. PV SCSI driver gracefully handles disk I/O timeouts and recovers from them.