Bug ID 534458: SIP monitor marks down member if response has different whitespace in header fields.

Last Modified: Nov 07, 2022

Bug Tracker

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

Known Affected Versions:
10.2.4, 11.0.0, 11.1.0, 11.2.0, 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.10, 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, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 12.0.0

Fixed In:
12.1.0, 12.0.0 HF1, 11.6.1, 11.5.4

Opened: Jul 21, 2015
Severity: 4-Minor
Related Article:
K17196

Symptoms

In certain circumstances the SIP monitor may incorrectly mark a SIP pool member down. This is due to the comparison the monitor makes of the standard header fields in the SIP monitor request to the response.

Impact

Unable to monitor the SIP pool member accurately using the standard SIP monitor because the pool member will be marked down.

Conditions

SIP monitor and response differ in the use of whitespace in the header fields, for example, 'field:value' and 'field: value'.

Workaround

Use other types of monitors, e.g., UDP.

Fix Information

SIP monitor now correctly processes monitor responses when the use of whitespace in header fields differ.

Behavior Change