Bug ID 473163: RAID disk failure and alert.conf log message mismatch results in no trap

Last Modified: Apr 16, 2019

Bug Tracker

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

Known Affected Versions:
11.2.1, 11.3.0, 11.4.0, 11.4.1, 11.5.0, 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, 11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1, 11.6.0 HF6, 11.5.4, 11.4.1 HF10, 11.2.1 HF16

Opened: Jul 25, 2014
Severity: 4-Minor
Related AskF5 Article:
K17299

Symptoms

Due to a mismatch between the definition of an alert for RAID disk failure in alert.conf, and the actual log message syntax, the appropriate SNMP traps are not issued when a disk is failing.

Impact

Actual log message syntax matches the following: 'alert kernel: md/raid1:md12: Disk failure on dm-29, disabling device.' As a result, there is no SNMP trap for a failing disk, so no SNMP trap is issued, and the LCD message is not displayed.

Conditions

This happens when there is a RAID disk failure and the definition RAID disk failure in alert.conf is similar to the following: alert BIGIP_RAID_DISK_FAILURE "raid[0-9]: Disk failure .*?" { snmptrap OID=".1.3.6.1.4.1.3375.2.4.0.96"; lcdwarn description="RAID disk failure." priority="3" }

Workaround

For information about configuring custom traps, see SOL3727: Configuring custom SNMP traps, available here: https://support.f5.com/kb/en-us/solutions/public/3000/700/sol3727.html.

Fix Information

RAID disk failure and alert.conf log message now match, so appropriate SNMP traps are now issued when a disk is failing.

Behavior Change