Switch up eth0 and eth1 to BMC shared and dedicated resp. ( Zaius )
adi.gangidi at rackspace.com
Fri Jun 16 12:55:11 AEST 2017
Thanks Rob, this helps.
We're working with Broadcom on Link flap caused by the NC-SI interface on both the interfaces. We tested bringing down the NC-SI interface in BMC (with ip command) and link flap won't occur at that point on dedicated connection.
And if it turns out that Broadcom can't resolve this, we will consider disabling that NC-SI interface via device tree.
From: Rob Lippert <rlippert at google.com>
Sent: Friday, June 9, 2017 12:13 PM
To: Adriana Kobylak
Cc: Adi Gangidi; OpenBMC Maillist; Adrian Barrera; Brad DeBauche; Chad Somerlot; Kenneth Wilke; ryan.dc.yu at foxconn.com
Subject: Re: Switch up eth0 and eth1 to BMC shared and dedicated resp. ( Zaius )
On Fri, Jun 9, 2017 at 10:03 AM, Adriana Kobylak <anoo at us.ibm.com> wrote:
> Looping in the community for feedback.
> ----- Original message -----
> From: Adi Gangidi <adi.gangidi at rackspace.com>
> To: "anoo at us.ibm.com" <anoo at us.ibm.com>, Kenneth Wilke
> <kenneth.wilke at RACKSPACE.COM>, Brad DeBauche <brad.debauche at RACKSPACE.COM>,
> Chad Somerlot <chad.somerlot at RACKSPACE.COM>, "abarrera at us.ibm.com"
> <abarrera at us.ibm.com>, "ryan.dc.yu at foxconn.com" <ryan.dc.yu at foxconn.com>,
> "Rob Lippert" <rlippert at google.com>
> Subject: Re: Switch up eth0 and eth1 to BMC shared and dedicated resp. (
> Zaius )
> Date: Fri, Jun 9, 2017 10:30 AM
> Sorry for couple of typo below, corrected them now.
> Please read again if it didn't make sense before.
> From: Adi Gangidi
> Sent: Friday, June 9, 2017 10:06 AM
> To: anoo at us.ibm.com; Kenneth Wilke; Brad DeBauche; Chad Somerlot;
> abarrera at us.ibm.com; ryan.dc.yu at foxconn.com; Rob Lippert
> Subject: Switch up eth0 and eth1 to BMC shared and dedicated resp. ( Zaius )
> Hi Adriana /. Ryan ( Foxconn )
> Right now on openBMC
> BMC Shared = eth0
> BMC Dedicated = eth1
> Instead, Is there a way we can make sure the BMC dedicated comes up as eth0
> and BMC shared link comes up as eth1, in Zaius / Barreleye G2 ?
> In how it works currently . you could have BMC dedicated be eth0 or eth1
> depending upon the hardware config ( Whether or not Broadcom 5719A is popped
> OR de-popped ) . That could confusing to support operators who don't
> understand the nuances .
The eth0 and eth1 on the BMC map to the BMC hardware MAC unit #. On
Zaius MAC1 is connected to various NC-SI stuff and MAC2 is connected
to the dedicated BMC MAC.
So the eth numbers should not move around even if there is nothing
connected on the other end of eth0. The only way the dedicated BMC
MAC MAC2 would become eth0 should be if the devtree entry for BMC MAC1
> If you guys are busy with other things to make the change , can I have your
> thoughts on if this can be changed ? I'm guessing this is a u-boot change .
> Any thoughts on how we could make this change ourselves ?
More information about the openbmc