Bug ID 588794: Misconfigured SCTP alternate addresses may emit incorrect ARP advertisements

Last Modified: Sep 13, 2023

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:
13.1.0, 12.1.3.6

Opened: Apr 20, 2016

Severity: 3-Major

Symptoms

SCTP alternate addresses may be advertised on the server-side that are in a route-domain that is different from that of the virtual server.

Impact

There is no impact to traffic processing. Alternate-addresses will be advertised even though they are not in the correct domain. Some addresses advertised may fail to respond to negotiation, but the SCTP association overall will be stable.

Conditions

Alternate-addresses are configured on an SCTP virtual server that aren't in the correct route domain.

Workaround

Ensure that all addresses for SCTP virtual servers are in the same route domain.

Fix Information

The SCTP profile now screens alternate addresses for route domain membership before advertising them.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips