Symptoms

Activation of Blob failed after config from ucs files (saved config has policy with atleast 1 rule) and running config has a policy (with same name) without any rules

Impact

Activation fails

Conditions

Running config has a policy (say policy name = X) with no rules and associated to a context. Saved config (UCS) has a different policy (but same name X) with at least 1 rule. When loading UCS (saved config), blob activation fails due to TMM not being able to revise counters for the new container.

Workaround

N/A

Fix Information

Correct counter tracking

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips