Bug ID 438877: If the SASP monitor receives an unexpected message from the GWM server containing an expected message id then the monitor stops processing any further messages.

Last Modified: Feb 13, 2019

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

Fixed In:
11.5.2, 11.4.1 HF9, 10.2.4 HF12

Opened: Nov 25, 2013
Severity: 3-Major
Related AskF5 Article:
K16283

Symptoms

The send weight messages message id field does not serve any purpose as per the SASP rfc 4678. Consider a scenario where the SASP monitor sents a registration request message containing message id x. It expects a registration reply with message id x. However, if it receives a send seight message with message id x then it throws the monitor out of sync. It stops processing any further messages.

Impact

The SASP monitor stops processing of any messages after it receives the unexpected send weights message.

Conditions

The SASP monitor sends a request message with a message id in it to the GWM server. It expects a reply from the GWM server to the request message containing the same message id. But instead it receives a send weights reply containing the expected message id.

Workaround

None.

Fix Information

The SASP monitor ignores up to 5 consecutive unexpected send weight messages and keep looking for registration reply response from GWM. If it does not get the reply in 5 attempts then the monitor shall restart.

Behavior Change