Last Modified: Sep 14, 2023
Affected Product(s):
BIG-IP All
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6
Opened: Feb 13, 2018 Severity: 2-Critical
TMM continues to restart on vCMP guest. /var/log/tmm shows: <13> Feb 1 00:00:30 slot1/hostname notice ** SIGSEGV ** <13> Feb 1 00:00:30 slot1/hostname notice fault addr: 0x1d8 <13> Feb 1 00:00:30 slot1/hostname notice fault code: 0x1 . . .
vCMP guest can't become active.
-- Using the following platforms: + BIG-IP 800, 1600, 3600, 3900, 6900, 89xx, 11xxx. + VIPRION 42xx/43xx and B21xx blades. -- Configure vCMP host and guest. System has Common Criteria or FIPS mode enabled.
There is no workaround.
None