Bug ID 702933: Loading UCS with different provisioning can cause a single TMM crash

Last Modified: May 14, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP ASM, AVR(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1

Opened: Jan 21, 2018
Severity: 3-Major

Symptoms

Saving a UCS file on one system and loading it on another that has different provisioning, can lead to TMM crash. Note: The crash will take place only once and the next process of TMM that will be automatically restarted will work without problems.

Impact

When the system restarts after loading the UCS, TMM can crash but second process of TMM will work fine. There is no actual impact, since the system is not operational anyway during UCS load, it only takes more time to bring the system to active state after loading the UCS.

Conditions

-- Save a UCS on a system that has AVR or ASM with DoS configured. -- Load the UCS on a system that does not have AVR nor ASM provisioned.

Workaround

When loading a UCS that was saved on a system that had AVR or ASM, make sure the same modules are provisioned first, and then load the UCS.

Fix Information

None

Behavior Change