Re: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]

AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com> Wed, 15 February 2012 15:38 UTC

Return-Path: <Peter.AshwoodSmith@huawei.com>
X-Original-To: armd@ietfa.amsl.com
Delivered-To: armd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4287A21F85C5 for <armd@ietfa.amsl.com>; Wed, 15 Feb 2012 07:38:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.566
X-Spam-Level:
X-Spam-Status: No, score=-2.566 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id szh6Fhdm8yVv for <armd@ietfa.amsl.com>; Wed, 15 Feb 2012 07:38:27 -0800 (PST)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 8947C21F85C3 for <armd@ietf.org>; Wed, 15 Feb 2012 07:38:27 -0800 (PST)
Received: from 172.18.9.243 (EHLO dfweml202-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id ADP88062; Wed, 15 Feb 2012 10:38:27 -0500 (EST)
Received: from DFWEML403-HUB.china.huawei.com (10.193.5.151) by dfweml202-edg.china.huawei.com (172.18.9.108) with Microsoft SMTP Server (TLS) id 14.1.323.3; Wed, 15 Feb 2012 07:35:16 -0800
Received: from DFWEML503-MBX.china.huawei.com ([10.124.31.29]) by dfweml403-hub.china.huawei.com ([10.193.5.151]) with mapi id 14.01.0323.003; Wed, 15 Feb 2012 07:35:11 -0800
From: AshwoodsmithPeter <Peter.AshwoodSmith@huawei.com>
To: Aldrin Isaac <aldrin.isaac@gmail.com>, Thomas Narten <narten@us.ibm.com>
Thread-Topic: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]
Thread-Index: AQHM6+tz2aQ3CA7uUUiJzv2UoHOYiJY+jZEA//+DSwA=
Date: Wed, 15 Feb 2012 15:35:10 +0000
Message-ID: <7AE6A4247B044C4ABE0A5B6BF427F8E291E4DB@dfweml503-mbx>
In-Reply-To: <4D9F477D-70C5-44B7-8146-992579B0D543@gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.193.60.101]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "armd@ietf.org" <armd@ietf.org>
Subject: Re: [armd] Multicast in the data center [was Re: address resolution requirement from hosts to overlay edge nodes. Any opinion?]
X-BeenThere: armd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion of issues associated with large amount of virtual machines being introduced in data centers and virtual hosts introduced by Cloud Computing." <armd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/armd>, <mailto:armd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/armd>
List-Post: <mailto:armd@ietf.org>
List-Help: <mailto:armd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/armd>, <mailto:armd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2012 15:38:28 -0000

> My impression is that many data centers do not enable IP multicast on
> their routers. That means you can use link-local multicast (which
> works fine within one IP subnet and doesn't really have scaling
> issues). But if you want multicast that goes beyond one link (and IP
> subnet), which is presumably necessary for an overlay like
> VXLAN/NVGRE, that is where you have problems.

Agreed. If you extrapolate a bit and imagine VXLAN with 1000's of logical groups.. then that maps either to head end replication in the hypervisor, or to IGMP from the hypervisor and PIM between the TOR and CORE 'switches' and the gateway router.

> The question is not even whether L3 multicast scales. It's whether the
> DC operater is willing to enable such multicast.

No choice if you want to run a Layer 2 Emulation over IP and you care about multicast banwdidh effeciency.

This highlights one of the major differences between the L2 over IP and L2 over L2 solutions, i.e. signalling v.s. computation for the multicast state.

This is why I think an understanding of the true uses of that multicast is important because if 90% of the applications are only finding each other and signalling each other using multicast there are better ways but if they are truly multicasting data in large volumes .. well we need extremely good underlay multicast scale.

Peter