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

[David Allan I <[e-mail]>]

Hi Lizhong

VM MACs are administered, and only require uniqueness within a customer VLAN. So as long as a single customer VLAN does not have multiple administators, there should be no issue.

IMO a MAC conflict within a single VLAN administration is complete incompetence, not somthing to kill ourselves trying to find a solution over!

my 2 cents
Dave

________________________________
From: [e-mail] [mailto:[e-mail]] On Behalf Of Lizhong Jin
Sent: Thursday, February 02, 2012 6:47 AM
To: [e-mail]
Cc: [e-mail]; [e-mail]
Subject: Re: [dc] Requirement for a method to manage mac address in DC

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<http://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