Bug ID 532035: Long trap messages can overwrite bigipNotifyObjNode field

Last Modified: Mar 21, 2019

Bug Tracker

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

Known Affected Versions:
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.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9

Fixed In:
11.6.0, 11.4.1 HF9

Opened: Jul 07, 2015
Severity: 3-Major

Symptoms

Corrupted bigipNotifyObjNode in trap messages.

Impact

Your monitoring system may depend on bigipNotifyObjNode to be correct

Conditions

Occurs when there are numerous pool member monitors configured, the pool monitor names are long and monitor status up/down message is triggered.

Workaround

Use shorter monitor names and/or fewer monitors.

Fix Information

No solution yet.

Behavior Change