Bug ID 678462: after chassis failover: asmlogd CPU 100% on secondary

Last Modified: Oct 01, 2018

Bug Tracker

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

Known Affected Versions:
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, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 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, 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

Fixed In:
13.1.0, 12.1.3.2, 11.6.3.2

Opened: Aug 15, 2017
Severity: 2-Critical

Symptoms

After a failover in a chassis: - asmlogd CPU 0% on primary slot (which was secondary before the failover). - asmlogd CPU 100% on secondary (which was primary before the failover). Without traffic running through the chassis.

Impact

asmlogd CPU shows 100% on secondary (which was primary before the failover), and vice versa.

Conditions

-- ASM provisioned. -- Chassis with at least two active slots. -- Chassis failover after some traffic was passed through the chassis.

Workaround

There is no workaround at this time.

Fix Information

The asmlogd process now better handles chassis failovers during which the chassis slots change roles (primary/secondary), so this issue no longer occurs.

Behavior Change