Re: [Sigtran] M3UA Recovery after Heart beat loss detection

Suchetha P <suchethap@yahoo.com> Tue, 23 January 2018 15:37 UTC

Return-Path: <suchethap@yahoo.com>
X-Original-To: sigtran@ietfa.amsl.com
Delivered-To: sigtran@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEE79126E01 for <sigtran@ietfa.amsl.com>; Tue, 23 Jan 2018 07:37:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Level:
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1N8mDwuhO4VF for <sigtran@ietfa.amsl.com>; Tue, 23 Jan 2018 07:37:19 -0800 (PST)
Received: from sonic307-9.consmr.mail.gq1.yahoo.com (sonic307-9.consmr.mail.gq1.yahoo.com [98.137.64.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9C78126DED for <sigtran@ietf.org>; Tue, 23 Jan 2018 07:37:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1516721839; bh=csWoeTtlpUNnyVKWs5OlrEbgUZ/bBmTIT7nv6zDn/P0=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=NvscguH7hYnfYXbbtLAS2wKSrinPJnFFNsveJHpLHwWvNoWkGu1yMdeOKWSnrdQTg/WWvzgz/lY2tFAW0s40aHxLs/NfD9rZUkhOeM4x9ah78InGobeJPt94kKdHqVCxPWtXBvk8vz3mwkPO9/Jw9OS3qhQDDja3pjP7GyHpXXOU/r4lOrfNOXGvBywb9nwQbGRZo/1bqkwhSwGUDiqaWPWUzcOs3yRsQhlw9BLRcg8aljJB2mP7WDVZySVdcLuXNtsRVEG4euYOCLOfpHnaCz6XI3bKyclCqb0GrQqNMZy7pOElxHoCmn2jrrAl6knT1D5tcL6xOsAjVWmTnFWvGA==
X-YMail-OSG: w2MRD_IVM1msNkSGQ_4DMbyfRMI5BUNFPyRHlZcaeQ1lvar0BbAwQZfNGHIhGi2 hR4sBtO7dboxFsfjH1VCTCo3XNqHdYlwJ5dLcn_6PkXlcrgBbusvJKQusePMaMp.IaNeRnWiT52V w_NQaXJKLB8.yqsZJI3YMflJ_V_uY5ukZ3w17pkrakpRRkXLFEACcy0TKNExXdQUtEmHIOu.14H3 uDvHlVTEWxy70G.Ku.jGjsnJDyKZ2ctIfJo3wv.levH35FgS3JPd2H0DrbdUWH8727GKeiqXk6bB Fns6SheM9xH_VsjDNW6qTc9TyodHXBDuP7072uz4wcErNBq5SqYnVhevOiUSw2hX4C2tH3Wsnxta j8nRdQBSoucVBm4Xy7My02nMnUfuMyRs2x3wAWk8qAJ81bOr_loEfkf9moRT1N6hY3P42FH4qBbQ Ev_DDydgpT0Zu5I9ZP_8I1UYgXVW.9osxe2JezqokmCe53xu4Ibtj5eHm1ejnuxM082_vfpyKV6p rcr5ZEWYEytO8Kn5e4C8NxKRE5XZUJ79pDHq9Jov50qqs
Received: from sonic.gate.mail.ne1.yahoo.com by sonic307.consmr.mail.gq1.yahoo.com with HTTP; Tue, 23 Jan 2018 15:37:19 +0000
Date: Tue, 23 Jan 2018 15:37:13 +0000
From: Suchetha P <suchethap@yahoo.com>
Reply-To: Suchetha P <suchethap@yahoo.com>
To: "bidulock@openss7.com" <bidulock@openss7.com>
Cc: "sigtran@ietf.org" <sigtran@ietf.org>, "sigtran-request@ietf.org" <sigtran-request@ietf.org>
Message-ID: <872888638.2556753.1516721833038@mail.yahoo.com>
In-Reply-To: <20180123150335.GA25320@openss7.org>
References: <482225217.2287173.1516681473150.ref@mail.yahoo.com> <482225217.2287173.1516681473150@mail.yahoo.com> <1495708682.2347665.1516688420977@mail.yahoo.com> <20180123150335.GA25320@openss7.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_2556752_758334877.1516721833036"
X-Mailer: WebService/1.1.11214 YahooMailNeo Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/sigtran/yOEvXxN1dp1hmkjLFcLM-dwrlBQ>
Subject: Re: [Sigtran] M3UA Recovery after Heart beat loss detection
X-BeenThere: sigtran@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Signaling Transport <sigtran.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sigtran>, <mailto:sigtran-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sigtran/>
List-Post: <mailto:sigtran@ietf.org>
List-Help: <mailto:sigtran-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sigtran>, <mailto:sigtran-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jan 2018 15:37:23 -0000

Hi Brian,
Thanks for your response.I see that the "local" system is not initiating ASP UP message nor aborting the association.Inorder to recover  from the ASP down state the "local system" expects M3UA BEAT,ASP UP messages from the peer which the peer is not initiating.The M3UA Heat beat mechanism needs to be enabled at both the ends isn't it ?I see that the M3UA Heart beat is disabled at the remote end resulting in no response from the peer for the BEAT message sent by the "local system".If M3UA Heart beat was enabled at the remote end then on receiving BEAT from the remote node "loca system" would have responded with BEAT ACK resulting in ASP UP.

Best Regards,Suchetha 

    On Tuesday, January 23, 2018 8:33 PM, Brian F. G. Bidulock <bidulock@openss7.com> wrote:
 

 Suchetha,

Suchetha P wrote:                      (Tue, 23 Jan 2018 06:20:20)
>    Hi,
>    Could some one please reply as soon as possible.
>    Appreciate your help.
>    Best Regards,
>    Suchetha
>    On Tuesday, January 23, 2018 9:54 AM, Suchetha P <suchethap@yahoo.com>
>    wrote:
>    Hi,
>    When M3UA Heart beat loss is detected at local node due BEAT ack  not
>    received for the BEAT message sent and Heart beat timer times out it
>    makes the ASP  down locally.
>    Currently there seems to be no action take when the M3UA layer makes
>    the ASP  down. The local node does not  send any message towards the
>    core network for bringing up the ASP.
>    So I would like to know once ASP is down due to HB lost at M3UA layer
>    then how does the local node recover the M3UA layer ?
> 

Nobody uses M3UA BEAT much, because it is optional and ETSI
prescribes against it.

However, don't you think that the "local" system should either
send an ASP UP or drop the SCTP association and start again?

>    Best Regards,
>    Suchetha

> _______________________________________________
> Sigtran mailing list
> Sigtran@ietf.org
> https://www.ietf.org/mailman/listinfo/sigtran


-- 
Brian F. G. Bidulock
bidulock@openss7.com
http://www.openss7.com/