Last Modified: May 14, 2019
See more info
Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 188.8.131.52, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1
Opened: Apr 20, 2016
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.
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.
Alternate-addresses are configured on an SCTP virtual server that aren't in the correct route domain.
Ensure that all addresses for SCTP virtual servers are in the same route domain.
The SCTP profile now screens alternate addresses for route domain membership before advertising them.