Last Modified: Jan 26, 2023
See more info
Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2
13.0.0, 12.1.2, 11.6.1 HF2, 11.5.4
Opened: Aug 04, 2015
Related Article: K13213552
Modifying a Secure Sockets Layer (SSL) profile associated with a virtual server may result in the Traffic Management Microkernel (TMM) producing a core file. As a result of this issue, you may encounter one or more of the following symptoms: -- BIG-IP system sends an invalid memory access segmentation fault (SIGSEGV) or floating point error (SIGFPE), signal to TMM, resulting in a stack trace that appears in the /var/log/tmm file. -- TMM restarts and produces a core file in the /shared/core directory. -- The BIG-IP system generates an assertion failure panic string in the /var/log/tmm file that appears similar to the following example: panic: ../kern/umem.c:3881: Assertion "valid type" failed
Traffic disrupted while tmm restarts.
1. LTM virtual server is configured with multiple SSL profiles, one of which is the default SNI profile. 2. A configuration change is made that affects the virtual server. Among others: -- Configuration is reloaded either manually or automatically after config sync. -- Change is made to any of the SSL profiles configured on the virtual server. -- SSL profiles are added or removed from the virtual server profile list. -- Change is made to the virtual server. -- Virtual server is deleted.
Making SSL profile configuration changes now completes successfully.