Last Modified: Sep 13, 2023
Affected Product(s):
BIG-IP MA-VE, TMOS
Known Affected Versions:
11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1
Fixed In:
5.3.0, 14.0.0, 13.1.0.2, 12.1.3.2
Opened: Jul 10, 2014 Severity: 3-Major Related Article:
K12155235
BIG-IP VE instances cannot use encrypted disks in AWS as encryption-decryption introduces some data corruption in the disk that causes failure in some of the TMOS daemons at run-time.
TMM cores at startup, and does not start.
Deploy a BIG-IP VE guests in AWS with an encrypted disk.
Do not use encrypted disks in AWS for BIG-IP VE instances.
BIG-IP VE instances can now work with an encrypted disk in AWS.