IETF Logo Mail Archive

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

Thomas Narten <narten@us.ibm.com> Thu, 02 February 2012 13:47 UTC

Return-Path: <narten@us.ibm.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 D5BE321F876A for <dc@ietfa.amsl.com>; Thu, 2 Feb 2012 05:47:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.417
X-Spam-Level:
X-Spam-Status: No, score=-108.417 tagged_above=-999 required=5 tests=[AWL=0.982, BAYES_00=-2.599, J_CHICKENPOX_42=0.6, J_CHICKENPOX_73=0.6, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 KHFDiUjLziNG for <dc@ietfa.amsl.com>; Thu, 2 Feb 2012 05:47:41 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 34A2621F85D6 for <dc@ietf.org>; Thu, 2 Feb 2012 05:47:41 -0800 (PST)
Received: from /spool/local by e9.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <dc@ietf.org> from <narten@us.ibm.com>; Thu, 2 Feb 2012 08:47:40 -0500
Received: from d01dlp01.pok.ibm.com (9.56.224.56) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Thu, 2 Feb 2012 08:47:39 -0500
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 4A74538C8063 for <dc@ietf.org>; Thu, 2 Feb 2012 08:47:38 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q12DlcBo255444 for <dc@ietf.org>; Thu, 2 Feb 2012 08:47:38 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q12DlbQX021263 for <dc@ietf.org>; Thu, 2 Feb 2012 08:47:37 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-196-49.mts.ibm.com [9.65.196.49]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q12Dla0Q021213 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 2 Feb 2012 08:47:37 -0500
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q12DlZQr008542; Thu, 2 Feb 2012 08:47:36 -0500
Message-Id: <201202021347.q12DlZQr008542@cichlid.raleigh.ibm.com>
To: yu.jinghai@zte.com.cn
In-reply-to: <201202020107.q1217pSU061250@mse01.zte.com.cn>
References: <201202020107.q1217pSU061250@mse01.zte.com.cn>
Comments: In-reply-to yu.jinghai@zte.com.cn message dated "Thu, 02 Feb 2012 09:05:17 +0800."
Date: Thu, 02 Feb 2012 08:47:34 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12020213-7182-0000-0000-000000A534D7
Cc: 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 13:47:41 -0000

yu.jinghai@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

v2.23.0 | Report a Bug | By Email