Re: [dc] Requirement for a method to manage mac address in DC

Lizhong Jin <lizho.jin@gmail.com> Thu, 02 February 2012 14:47 UTC

Return-Path: <lizho.jin@gmail.com>
X-Original-To: dc@ietfa.amsl.com
Delivered-To: dc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7269121F8575 for <dc@ietfa.amsl.com>; Thu, 2 Feb 2012 06:47:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.481
X-Spam-Level:
X-Spam-Status: No, score=-2.481 tagged_above=-999 required=5 tests=[AWL=-0.683, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_27=0.6, J_CHICKENPOX_42=0.6, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_LOW=-1]
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 VC39Af-X6F9S for <dc@ietfa.amsl.com>; Thu, 2 Feb 2012 06:47:06 -0800 (PST)
Received: from mail-qy0-f172.google.com (mail-qy0-f172.google.com [209.85.216.172]) by ietfa.amsl.com (Postfix) with ESMTP id 9E88421F856C for <dc@ietf.org>; Thu, 2 Feb 2012 06:47:06 -0800 (PST)
Received: by qcsg13 with SMTP id g13so1656460qcs.31 for <dc@ietf.org>; Thu, 02 Feb 2012 06:47:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=FEPlBBjKfIIq/EiCBjaIvTI9HzsdJtEet84DSmXO/r0=; b=LcqlFlJ4WJ+2whKGV1raJNX/ZeiL1z0eIFGHBl2MOvrd14pVUUpWAha65TM5nsLwLb 6sA0kA8/EGOrkKj9tsoMX2A4lQR0LpLMfVOHWDqll7agcZf+DaRNijIGdqdH/vtMlPkA S6U9FRvYPgiaUhmM4k5QAQXR/K01eacmm9StQ=
MIME-Version: 1.0
Received: by 10.229.78.86 with SMTP id j22mr1112266qck.95.1328194026163; Thu, 02 Feb 2012 06:47:06 -0800 (PST)
Received: by 10.224.189.6 with HTTP; Thu, 2 Feb 2012 06:47:06 -0800 (PST)
Date: Thu, 02 Feb 2012 22:47:06 +0800
Message-ID: <CAH==cJynjN2HxMYh8w+0P0jKVMKWBoX-az=J=EqKX_w4E6GjCw@mail.gmail.com>
From: Lizhong Jin <lizho.jin@gmail.com>
To: narten@us.ibm.com
Content-Type: multipart/alternative; boundary="00235429c8181f4d8704b7fc457d"
X-Mailman-Approved-At: Sat, 11 Feb 2012 14:04:35 -0800
Cc: yu.jinghai@zte.com.cn, dc@ietf.org
Subject: Re: [dc] Requirement for a method to manage mac address in DC
X-BeenThere: dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Data Center Mailing List <dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dc>, <mailto:dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dc>
List-Post: <mailto:dc@ietf.org>
List-Help: <mailto:dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dc>, <mailto:dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Feb 2012 14:47:07 -0000

Hi Thomas,
The VMs connected by SPB-M or NVO3/VXLAN/NVGRE will still reside in one L2
network, and the VMs MAC will still conflict if have same MAC address. VM
MAC confliction could not be mitigated or solved by these mechanism if I
understand correctly.

Lizhong

-------------------------------------
yu.jinghai at zte.com.cn writes:


>
>    I wonder whether it is necessary to manage mac address in DC.
> As you know,VM's mac is randomly generated.
> The risk of mac conflict is increasing with  the amount of VMs in DC.
> If there is a method to auto manage and allocate mac address,the
>    risk maybe avoid.
> That method may facilitate the operator to control network easily
>    and other available benefits.

One straightforward way to mitigate C-MAC conflicts is via
encapsulations, whether through something like SPB-M or
NVO3/VXLAN/NVGRE.

Do such approaches not address the problem sufficiently?

Thomas