Last Modified: Nov 22, 2021
See more info
Known Affected Versions:
15.0.0, 15.0.1, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 15.1.0, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 15.1.1, 15.1.2, 126.96.36.199, 15.1.3, 188.8.131.52
Opened: Nov 12, 2019
The outgoing SCTP connection does not expire after attempting to INIT the maximum number of times. It then becomes stuck and does not expire when it reaches its idle-timeout, and cannot be manually deleted.
Stale SCTP connections are left in the system and start to use up memory. Traffic may be interrupted in certain configurations, as the system thinks it is still attempting to bring up the lost SCTP connection and does not ever try to create a new one.
An outgoing SCTP connection is permitted to attempt the INIT retransmit the maximum number of times configured with no responses (accepting or aborting) from the target endpoint.
To clear the stale connections, restart tmm: bigstart restart tmm Note: Restarting tmm causes an interruption to traffic.
SCTP connections now expire properly after the maximum number of INITs have been attempted and can no longer get stuck in this case.