RE: Query on SCTP:INIT re-transmission interval behavior

[Ravi Puttachannaiah <ravi.puttachannaiah@aricent.com>]

Hi Marcelo,

Thanks for the response. Following is the kernel version we are using and there are only one transport.

Linux 3.10.10-svn1674 #73 SMP Fri Jan 22 12:42:34 IST 2016 armv7l GNU/Linuxs

I have also uploaded the SCTP logs at the following URL. Basically we want to understand why the SCTP:INIT retransmission is starting from "6" (instead of "3") and is it an expected behavior. Could you please help.

https://www.dropbox.com/sh/75cu9n5jytchgkv/AACYXhPSJL_VhlPsj9h5hON-a?dl=0


Regards,

Ravi


-----Original Message-----
From: linux-sctp-owner@vger.kernel.org [mailto:linux-sctp-owner@vger.kernel.org] On Behalf Of Marcelo Ricardo Leitner
Sent: Wednesday, January 27, 2016 9:32 PM
To: Ravi Puttachannaiah <ravi.puttachannaiah@aricent.com>
Cc: linux-sctp@vger.kernel.org
Subject: Re: Query on SCTP:INIT re-transmission interval behavior

Hi,

On Wed, Jan 27, 2016 at 03:36:11PM +0000, Ravi Puttachannaiah wrote:
> Hi,
>
> We are using LKSCTP version 1.0.16 and have configured the SCTP configuration parameters as follows:

Okay but in the end who will do the actual handling of the retransmission is the kernel. Which kernel are you using?

> SctpInitMaxAttempts : 10
> SctpInitRTO : 3000
> SctpMinRTO : 1000
> SctpMaxRTO : 60000
>
> We observed that SCTP:INIT re-transmission is occurring at interval  6,12,24.., 6,12,24.., 6,12,24....... As per our understanding re-transmission should occur at interval  3,6,12,24..., 3,6,12,24...3,6,12,24... since SctpInitRTO000.
>
> Could you please let us know if it is an expected behavior or not. Also why re-transmission interval is not started with 3,6,12,24...

That's my understanding too, 3, 6, 12..

How many transports do you have?

  Marcelo
--
To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@vger.kernel.org More majordomo info at  http://vger.kernel.org/majordomo-info.html
"DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."