Bug ID 536939: Secondary blade may restart services if configuration elements are deleted using a * wildcard.

Last Modified: Oct 01, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP All(all modules)

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.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2

Fixed In:
11.5.4

Opened: Jul 31, 2015
Severity: 3-Major

Symptoms

In certain situations a chassis based system with more than one working blade may encounter service restart on the secondary blade.

Impact

Services will restart on the secondary blade.

Conditions

- Chassis system with 2 or more working blades. - Configuration to be deleted via tmsh using a wildcard. For instance: tmsh delete ltm virtual test*

Workaround

Do not use * wildcards with tmsh when deleting configuration elements on a chassis system.

Fix Information

Services no longer restart on a secondary blade when deleting configuration elements via tmsh using a * wildcard.

Behavior Change