For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Son_of_Tom_1379's avatar
Son_of_Tom_1379
Icon for Nimbostratus rankNimbostratus
Nov 19, 2014

F5 Virtual Edition sensitive to SAN controller failover

We have a virtual edition running on a problematic SAN in one of our data centers. From time to time the primary SAN controller crashes and restarts, causing a failover to the secondary controller. W...
availability
storage
TMOS
TMSH
virtualization
Chase_Abbott's avatar
Chase_Abbott
Icon for Admin rankAdmin
Nov 24, 2014

Odd. With Linux (in this case CentOS), the guest will mark the failed disk as read-only when it's scsi drivers times out usually 2ish times. In older versions of Linux, this was a moderately short time (2 minutes) but a lot of vendors upped this timer because VM I/O doesn't easily match up against traditional disk drivers. The last time we ran into this failure, the NFS was unavailable for the VMDK files for literally 5 minutes. Our debian installs obviously timed out and marked their volumes as read only and we had to reset servers once NFS was back up.

 

20 seconds should be way to short a time for a VMWare guest to mark a volume as read-only. " target="_blank">The issue here if you didn't see this already.

 

What version of BigIP are you on as CentOS is of course a RHEL derived?