Re: Service Redundancy using BFD

Ashesh Mishra <mishra.ashesh@outlook.com> Tue, 28 November 2017 23:21 UTC

Return-Path: <mishra.ashesh@outlook.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E0D0128BA2 for <rtg-bfd@ietfa.amsl.com>; Tue, 28 Nov 2017 15:21:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.009
X-Spam-Level:
X-Spam-Status: No, score=-0.009 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, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.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 opWUYfnJhKHx for <rtg-bfd@ietfa.amsl.com>; Tue, 28 Nov 2017 15:21:36 -0800 (PST)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010017.outbound.protection.outlook.com [40.92.10.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A3C5128D64 for <rtg-bfd@ietf.org>; Tue, 28 Nov 2017 15:21:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=aGAdXa2m+0SYdTXeuj2wemVwE/UmKT3aJ82hA78jnlw=; b=qE3yHj7Ejr5A+t0gTRchYpyqW+kdJeqbtODr4aBahHP4y8AVGQZ9LoauhBaUKVXlQ4UENuh/gbSTUqYzxHeio2MKRUxlsDJTdBUUHdAXLtqijfBHKdlcVc+EeF4DtPuFdHalmd+Y4kN+2N6xL9Kyue2Gu1lSEpxXun8LxB3WKno2+c55Jy2ltDT4ARrLvq5HselWE7O6bU3Nt9tUu55T5RBw5hyoNz0tSI6E0FWkqELOg/up8DyU6qQbd/nqtAHWRIcquSjNvCARxm6O9LCdHQY6oMIVuIM/8KSeIcpAc1TmHaSMTs7YRLLj5/5SfkdRLPxgBL/dFE58hx664qS79Q==
Received: from CO1NAM04FT010.eop-NAM04.prod.protection.outlook.com (10.152.90.52) by CO1NAM04HT127.eop-NAM04.prod.protection.outlook.com (10.152.90.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4; Tue, 28 Nov 2017 23:21:33 +0000
Received: from MWHPR0101MB2880.prod.exchangelabs.com (10.152.90.56) by CO1NAM04FT010.mail.protection.outlook.com (10.152.90.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.20.239.4 via Frontend Transport; Tue, 28 Nov 2017 23:21:33 +0000
Received: from MWHPR0101MB2880.prod.exchangelabs.com ([10.174.170.11]) by MWHPR0101MB2880.prod.exchangelabs.com ([10.174.170.11]) with mapi id 15.20.0260.006; Tue, 28 Nov 2017 23:21:33 +0000
From: Ashesh Mishra <mishra.ashesh@outlook.com>
To: Sami Boutros <sboutros@vmware.com>, Ankur Dubey <adubey@vmware.com>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
CC: Reshad Rahman <rrahman@cisco.com>
Subject: Re: Service Redundancy using BFD
Thread-Topic: Service Redundancy using BFD
Thread-Index: AQHTZ/M82vlye4FAgk+FmQYa86ul9aMpXmmAgAA3kICAAGH9AP//z8oAgAA42wD//9WuAIAART2A
Date: Tue, 28 Nov 2017 23:21:33 +0000
Message-ID: <FCCDE12A-C55F-4044-9A06-486BFD66B41B@outlook.com>
References: <3A4A67EC-042C-4F8A-80AB-E7A5F638DE15@vmware.com> <76804F35-63BB-46A0-A74C-9E41B2C213B4@outlook.com> <6FB7BA5C-8ECC-4330-89D0-8FD7306217F5@vmware.com> <00F17C92-E43D-4BFB-81B1-534DD221E66F@outlook.com> <42407007-C6BA-4CAF-8BE8-F6C552B92A38@vmware.com> <874DFFD3-1DE2-43A1-B726-B128E5746DBE@outlook.com> <828E73CC-E8C2-48C8-93CD-3CB580174536@vmware.com>
In-Reply-To: <828E73CC-E8C2-48C8-93CD-3CB580174536@vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:451FB04FA6B8CE60738AAB2984287C0F6F3C0A23144F188D0A98E39485F8BC74; UpperCasedChecksum:4D6FE4C54F551C423FB663363D6236D5CF60290F6ADABDB57269DAC691255899; SizeAsReceived:7337; Count:47
x-ms-exchange-messagesentrepresentingtype: 1
x-tmn: [WcUH+GSEalMlOlvgHLvXOT6A2Pt4QzDI]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO1NAM04HT127; 6:eDRahJgIiLZZHqO+eJHQhes6I0oC6ICNtI3mH3GA3j90yiFLrwdymtdN5S+uhGBRu9iaytF3hBbgmwfQ1pOwjskskySu6ZPFtlvFvAU+KxwFF0fFJnSIl4shcGB1WXeVGOTjnYE6AyodOenCPRmLBHTq44ZVg6NB6JtLCUqcPiMWNl/OkfgL2YBTd+aMoNIXmt7hlgwqVWRhF0q1SnqW3DCP2m6aInkipU9Ptd52rCpl4OmhDMM8LPMhPrbUwfNc/jTdI9W6P4ELblGzZskZFhgWOT6etye8tRouS3zvWXkDFQ0rllcdJ6+gx6XylaKV4vaoO+DnbBxvEDa3lApfK63YGGt4uJwGDq/9VQB51pc=; 5:q69lWSxhXsqH6IJRZytDR/AKTTy98BNSBI/IJuNcKcFtGRwMqIKgCW6OP7sSo5TZQMTGbSO6g1u+OjKm9fLevdQTgeFlZiDyKfr3+zS3f5FVO35GX9/9j8JUSQSRGjl3dFwE0llSBSjw1FyNCTCD16KYbNEE1boRo3LjL+kdlMw=; 24:tub7d2IytmmYe50u4Cx3ku5CVbYDKLyj1iGsnWZaBkGuf1qiUI1zEPmc5lv5B95uQtNjkKWQbc4EaYaZc98DA3rZWCdQxkRYJMUtPP/YEYw=; 7:PywcXaV8nwy6Blh3uKC+YQT1NWyMPP6mzyfdWkAHRfEm5n0DSI077EchGFTT+CDL4FCNYNQzxlkpMXVoeHjIvnFJkETlAbQyggsyzbhq569MnxtGDw84PZWasPWPwVXQmITRHthIZaXnzU3ki8a7tN7+zwBYfxFbvQNkKRA0SsnrQRKZfc9QZyNU/JWzq3hVDyWrBK9YiFlGe9aPhBq8hlYV/SEUMX7LdsyRcCKwL35zgpqO3QC6ffRaPzdt5Gfj
x-incomingheadercount: 47
x-eopattributedmessage: 0
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322404)(1603101448)(1601125374)(1701031045); SRVR:CO1NAM04HT127;
x-ms-traffictypediagnostic: CO1NAM04HT127:
x-ms-office365-filtering-correlation-id: 86741edf-c523-43ab-a4fb-08d536b6c3b2
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(444000031); SRVR:CO1NAM04HT127; BCL:0; PCL:0; RULEID:(100000803101)(100110400095); SRVR:CO1NAM04HT127;
x-forefront-prvs: 0505147DDB
x-forefront-antispam-report: SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:CO1NAM04HT127; H:MWHPR0101MB2880.prod.exchangelabs.com; FPR:; SPF:None; LANG:;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_FCCDE12AC55F40449A06486BFD66B41Boutlookcom_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 86741edf-c523-43ab-a4fb-08d536b6c3b2
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Nov 2017 23:21:33.7224 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO1NAM04HT127
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/FZNnAa4dtdAe5cBqfiBJTLhKr7c>
X-Mailman-Approved-At: Wed, 29 Nov 2017 04:29:15 -0800
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 28 Nov 2017 23:21:40 -0000

Sami,

Thanks for the clarification. In a typical scenario, this will look like:

A <-------------\
            \           \
             C            D
            /           /
B <-------------/

were there are two sets of services. The BFD session between A and B in this case will be overloaded with the states for the two sets of sessions. It’s not clear from the proposal if this scenario is addressed (and how).

Ashesh
From: Sami Boutros <sboutros@vmware.com>;
Date: Tuesday, November 28, 2017 at 5:13 PM
To: Ashesh Mishra <mishra.ashesh@outlook.com>;, Ankur Dubey <adubey@vmware.com>;, "rtg-bfd@ietf.org"; <rtg-bfd@ietf.org>;
Cc: Reshad Rahman <rrahman@cisco.com>;
Subject: Re: Service Redundancy using BFD

Hi Ashesh,

The topology is more like the following:

A <—\
|         \
BFD      C
|         /
B<—/

A and B are nodes providing L2 and L3 services for C, with A/S redundancy.

A can be active and B standby, if A goes down then B start providing the services.

Thanks,

Sami
From: Ashesh Mishra <mishra.ashesh@outlook.com<mailto:mishra.ashesh@outlook.com>>
Date: Tuesday, November 28, 2017 at 1:45 PM
To: Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>, Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Subject: Re: Service Redundancy using BFD

Okay. That makes sense now.

So in a scenario where you have a primary overlay service between A and B, and a backup overlay service between C and D, the BFD sessions in question will be between A and C, and B and D (so that the backup can send diag code to primary)?

A <------- primary service --------->B
|                                                           |
BFD                                                    BFD
|                                                           |
C<-------- backup service ---------->D

--
Ashesh


From: Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>
Date: Tuesday, November 28, 2017 at 4:21 PM
To: Ashesh Mishra <mishra.ashesh@outlook.com<mailto:mishra.ashesh@outlook.com>>, Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Subject: Re: Service Redundancy using BFD

Hi Ashesh,

A service is an overlay service running on a routing node, this could be a L2 or L3 VPN service running on set of links connected to 2 or more nodes, where one node is active for a service at a given point in time, and one node is standby.

Now, BFD is running on underlay links between the 2 nodes active and standby, once BFD goes down, the standby assumes that the active went down and activates the services that it shares with the active. On the BFD session the standby would signal to the old active when it came back up that it activated the non-preemptive services via this diag code saying that it didn’t fail, so the old active node doesn’t activate those non-preemptive services.

Thanks,

Sami
From: Ashesh Mishra <mishra.ashesh@outlook.com<mailto:mishra.ashesh@outlook.com>>
Date: Tuesday, November 28, 2017 at 1:14 PM
To: Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>, Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Subject: Re: Service Redundancy using BFD

Thanks for the response, Sami. I think our disconnect lies in the definition of a service. From a BFD perspective, I expect the service to be established across two nodes, at the very least, so that BFD can monitor its liveness. Can you elaborate on


-          What, in the context of this draft, a service is?

-          How does BFD signal for a service that it is not monitoring the liveness for?

Thanks,
Ashesh

From: Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>
Date: Tuesday, November 28, 2017 at 1:23 PM
To: Ashesh Mishra <mishra.ashesh@outlook.com<mailto:mishra.ashesh@outlook.com>>, Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>
Subject: Re: Service Redundancy using BFD

Hi Ashesh,

Thanks for your comments.

For your first comment the draft applies to both single hop or what you call interface BFD and multi hop BFD too. And yes the per service could be per interface too if this is a single hop BFD, we can clarify that in the draft.

For your second comment, I am not sure I understand. The service will be active only on one node, if the service is associated with the whole node, then the BFD session is monitoring the node liveness. And when the service is associated with an interface the BFD session will monitor the interface connectivity as well. So, a primary service can’t be active at the 2 node endpoints hosting the BFD session.

Thanks,

Sami
From: Ashesh Mishra <mishra.ashesh@outlook.com<mailto:mishra.ashesh@outlook.com>>
Date: Tuesday, November 28, 2017 at 4:04 AM
To: Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>, "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>, Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>
Subject: Re: Service Redundancy using BFD

Hi Ankur,

This is a good proposal to pursue within the BFD-wg.

Couple of comments:

-          BFD can only signal this diag code for the interface that it is monitoring (the IP next hop, MPLS LSP, etc.). You mention per-service (which I assume means per-service-per-interface) failover in the draft but it may be worthwhile defining behavior on per-service-type-per-interface as well.

-          There still needs to be a method for the primary and backup pairs (two BFD end-points on primary service and two on backup service) to communicate with each other (primary-to-primary and backup-to-backup) if the service is active or standby. This is useful in the scenario when the primary cannot communicate with backup nodes (it is a failure condition after all).

Again, at 10k ft, I like the idea of signaling active/standby using BFD.

Cheers,
Ashesh

From: Rtg-bfd <rtg-bfd-bounces@ietf.org<mailto:rtg-bfd-bounces@ietf.org>> on behalf of Ankur Dubey <adubey@vmware.com<mailto:adubey@vmware.com>>
Date: Monday, November 27, 2017 at 9:47 PM
To: "rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>" <rtg-bfd@ietf.org<mailto:rtg-bfd@ietf.org>>
Cc: Reshad Rahman <rrahman@cisco.com<mailto:rrahman@cisco.com>>, Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>
Subject: Service Redundancy using BFD

Hi all,

Please review and provide comments for the following draft:

https://datatracker.ietf.org/doc/draft-adubey-bfd-service-redundancy/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dadubey-2Dbfd-2Dservice-2Dredundancy_&d=DwMGaQ&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3D1zKBUXYinynnVWgCSqOkn4ccSIcx6rzDitjPm2dfs&s=d4DdCstEXxJ0sOJ09fOaHRCfpS3chnYNcuVWImRCcFQ&e=>






Summary of draft:

This draft proposes a new BFD diag code via which a node running a BFD session with another node, can inform the other node after a BFD session times out, that it didn’t go down and did live through the failure.

Such notification is useful for a set of nodes providing Active/Standby redundancy. When these nodes are running multiple L2/L3/L4-L7 services  in non-revertive mode of redundancy, the standby node taking over as active for non-revertive services after BFD times out needs to indicate in the BFD packet that it outlived the other failed old active node. The new diag code will be used for this purpose. When this diag code is set in the BFD packets, it will provide an indication to the failed old active node that it MUST NOT activate the non-revertive services when it comes up.

For providing a per service level failover, a node activating certain non-revertive services needs to indicate that it is Active ONLY for those non-revertive services. This can be done by using a unique bitmap where each bit position is uniquely identifying a service. This unique bitmap is configured on all nodes by a network controller. When there is at least one non-revertive service for which a node is not active AND it is active for at least 1 non-revertive service, this node will set bits identifying the active services in the bitmap and send it in the payload of the BFD packet.


Thanks,
--Ankur