Bug ID 425008: SCTP profile cannot handle SID value

Last Modified: Mar 12, 2019

Bug Tracker

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

Known Affected Versions:
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.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, 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, 11.6.3.2, 11.6.3.3, 11.6.3.4

Fixed In:
12.0.0

Opened: Jul 11, 2013
Severity: 3-Major
Related AskF5 Article:
K17363

Symptoms

The SCTP stream id (SID) is always set to zero on egress from the BIG-IP system. This causes applications that expect to send or receive data on other streams to fail.

Impact

Applications that require multiple streams will not function correctly. The SCTP protocol profile can be edited to set the maximum input and output streams to 1, which prevents a client from expecting to be able to use more than one stream. This might cause the client to fail to connect, rather than connect and get unexpected behavior.

Conditions

The SCTP proxy always behaves this way when it receives a non-zero SID.

Workaround

None

Fix Information

This release provides multi-streaming support for SCTP profiles when handling stream id values.

Behavior Change