IETF Logo Mail Archive

Re: BFD stability follow-up from IETF-91

Manav Bhatia <manavbhatia@gmail.com> Fri, 05 December 2014 03:02 UTC

Return-Path: <manavbhatia@gmail.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AF981A90A0 for <rtg-bfd@ietfa.amsl.com>; Thu, 4 Dec 2014 19:02:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, SPF_PASS=-0.001] autolearn=ham
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 cbfC5X9NQc3i for <rtg-bfd@ietfa.amsl.com>; Thu, 4 Dec 2014 19:02:47 -0800 (PST)
Received: from mail-ob0-x229.google.com (mail-ob0-x229.google.com [IPv6:2607:f8b0:4003:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71F5B1A909B for <rtg-bfd@ietf.org>; Thu, 4 Dec 2014 19:02:42 -0800 (PST)
Received: by mail-ob0-f169.google.com with SMTP id vb8so3927175obc.0 for <rtg-bfd@ietf.org>; Thu, 04 Dec 2014 19:02:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S1YcGtujvqThbmgxgfyEDcImx7rjvTCpMDcAt/xAjQU=; b=IEujmCj8/m0nkcbyftotLkpzp2docmBR+6vYqnKhPfqt2rybZvTLLo+7R3cH6rxmlj pUESlnRt+Yu4CtJdKFFcWQqhRCdXnDNoVuBv1CC99LRqihNRc6FZpL3P/+MTz0Efxler 6nw+1V1xkx7wxJGPQ31j4LbFrdf3NzUHtlUzuiuWxnttcpZayZ1nfQwTgjenPNeKGhUs 5AQhI3M4UkpSIlhcQHdMwkh8jXHM7A4suOZzGh5u3RjBbIyaDbaItxFGuG0Qzs6+5mA4 44p/fjD9OAFR8eOTD9ERKLOahSdLtI5t/jd6odK1y0sGTiP+NTRFJTx8QqjaIdfolmhv SIyw==
MIME-Version: 1.0
X-Received: by 10.202.204.208 with SMTP id c199mr8724399oig.42.1417748561780; Thu, 04 Dec 2014 19:02:41 -0800 (PST)
Received: by 10.76.178.199 with HTTP; Thu, 4 Dec 2014 19:02:41 -0800 (PST)
In-Reply-To: <7347100B5761DC41A166AC17F22DF1121B8AACDB@eusaamb103.ericsson.se>
References: <007701d00af9$28719050$7954b0f0$@chinamobile.com> <D09E5FAC.27C51%mmudigon@cisco.com> <007e01d00b07$9c02cc10$d4086430$@chinamobile.com> <7347100B5761DC41A166AC17F22DF1121B8998E7@eusaamb103.ericsson.se> <00a001d00d64$7735ce50$65a16af0$@chinamobile.com> <7347100B5761DC41A166AC17F22DF1121B8A87E6@eusaamb103.ericsson.se> <730769BB-D021-4E22-878A-2C289822A156@gmail.com> <7347100B5761DC41A166AC17F22DF1121B8AA754@eusaamb103.ericsson.se> <09CD6B2F-4DCC-429F-848B-223C72A0F171@gmail.com> <7347100B5761DC41A166AC17F22DF1121B8AAA24@eusaamb103.ericsson.se> <CO2PR0501MB8231A4913DEB31323847CA8B3780@CO2PR0501MB823.namprd05.prod.outlook.com> <7347100B5761DC41A166AC17F22DF1121B8AAC0D@eusaamb103.ericsson.se> <CAG1kdoiquWYaAz5ti14VrmiqXmph-SpjgYs=m8AuQGdKGo2xXQ@mail.gmail.com> <7347100B5761DC41A166AC17F22DF1121B8AACDB@eusaamb103.ericsson.se>
Date: Fri, 05 Dec 2014 08:32:41 +0530
Message-ID: <CAG1kdojHAY46xwhhqoi9uQu6cBYwQvcH=hm5GN9sZGDWoAH-tA@mail.gmail.com>
Subject: Re: BFD stability follow-up from IETF-91
From: Manav Bhatia <manavbhatia@gmail.com>
To: Gregory Mirsky <gregory.mirsky@ericsson.com>
Content-Type: multipart/alternative; boundary="001a1135329c67e64705096f4f82"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtg-bfd/ZW9JYpU9gCClJXVK9vY2r_jJRto
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Dec 2014 03:02:52 -0000

Hi Greg,

I am sure the WG would appreciate such a lecture since that would obviate
the need for such an ID. Are you suggesting that i turn on logging and
packet tracing for *each* incoming BFD packet for all the sessions that i
have? Trying doing that for 25 BFD sessions where few are running at 50ms
and 100ms TX intervals. Now trying combing through the logs when 1 BFD
session flaps to understand where the issue was.

Cheers, Manav

On Thu, Dec 4, 2014 at 10:03 PM, Gregory Mirsky <gregory.mirsky@ericsson.com
> wrote:

>  Hi Manav,
>
> I hope you don’t expect me to give a lecture on how to design and
> implement debugable implementation using logging and packet tracing.
>
>
>
>                 Regards,
>
>                                 Greg
>
>
>
> *From:* Manav Bhatia [mailto:manavbhatia@gmail.com]
> *Sent:* Thursday, December 04, 2014 8:16 AM
> *To:* Gregory Mirsky
> *Cc:* Santosh P K; Mahesh Jethanandani; rtg-bfd@ietf.org
>
> *Subject:* Re: BFD stability follow-up from IETF-91
>
>
>
> I am not sure what the confusion is Greg.
>
>
>
> Assume i have a BFD session thats up. At some point in time it flaps. Now
> i need to know whether the issue was at the TX or the RX.
>
>
>
> Please tell me how TWAMP can help me here. Also tell me how what tool i
> can use if its a uBFD session that flapped.
>
>
>
> Cheers, Manav
>
>
>
>
>

v2.23.0 | Report a Bug | By Email