Bug ID 691477: ASM standby unit showing future date and high version count for ASM Device Group

Last Modified: Oct 10, 2018

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3

Fixed In:
14.0.0, 13.1.0.4, 12.1.3.2

Opened: Oct 30, 2017
Severity: 3-Major

Symptoms

Policy builder is changing configuration of standby unit.

Impact

Unexpected changes are made to the policy on standby device (CID increment).

Conditions

The system state changes from active to standby (also when blade is changed from master to non-master).

Workaround

Restart pabnagd when switching device from active to standby (also when blade is changed from master no non-master): killall -s SIGHUP pabnagd

Fix Information

Policy builder now updates its state correctly and doesn't make changes to a policy on a standby device.

Behavior Change