From: Adi Gangidi <adi.gangidi@rackspace.com>
To: Rob Lippert <rlippert@google.com>, Adriana Kobylak <anoo@us.ibm.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>,
Adrian Barrera <abarrera@us.ibm.com>,
Brad DeBauche <brad.debauche@RACKSPACE.COM>,
"Chad Somerlot" <chad.somerlot@RACKSPACE.COM>,
Kenneth Wilke <kenneth.wilke@RACKSPACE.COM>,
"ryan.dc.yu@foxconn.com" <ryan.dc.yu@foxconn.com>
Subject: Re: Switch up eth0 and eth1 to BMC shared and dedicated resp. ( Zaius )
Date: Fri, 16 Jun 2017 02:55:11 +0000 [thread overview]
Message-ID: <1497581711523.17322@rackspace.com> (raw)
In-Reply-To: <CAFRv3wzS2TtJBom-tfSnfOTdc=6rHsvQ5ZJqFbgZUT609i-g2g@mail.gmail.com>
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.
-Adi
________________________________________
From: Rob Lippert <rlippert@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@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@us.ibm.com> wrote:
> Looping in the community for feedback.
>
>
>
> ----- Original message -----
> From: Adi Gangidi <adi.gangidi@rackspace.com>
> To: "anoo@us.ibm.com" <anoo@us.ibm.com>, Kenneth Wilke
> <kenneth.wilke@RACKSPACE.COM>, Brad DeBauche <brad.debauche@RACKSPACE.COM>,
> Chad Somerlot <chad.somerlot@RACKSPACE.COM>, "abarrera@us.ibm.com"
> <abarrera@us.ibm.com>, "ryan.dc.yu@foxconn.com" <ryan.dc.yu@foxconn.com>,
> "Rob Lippert" <rlippert@google.com>
> Cc:
> 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.
>
> -Adi
> ________________________________________
> From: Adi Gangidi
> Sent: Friday, June 9, 2017 10:06 AM
> To: anoo@us.ibm.com; Kenneth Wilke; Brad DeBauche; Chad Somerlot;
> abarrera@us.ibm.com; ryan.dc.yu@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
was removed.
-Rob
>
> 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 ?
>
> -Adi
>
>
>
>
>
>
next prev parent reply other threads:[~2017-06-16 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDE9FA85-CF2B-4B72-9974-1E92EE9EC676@rackspace.com>
[not found] ` <1497022202970.71679@rackspace.com>
2017-06-09 17:03 ` Switch up eth0 and eth1 to BMC shared and dedicated resp. ( Zaius ) Adriana Kobylak
2017-06-09 17:13 ` Rob Lippert
2017-06-16 2:55 ` Adi Gangidi [this message]
2017-06-15 5:30 ` Joel Stanley
2017-06-26 23:05 ` Patrick Williams
2017-09-03 0:12 ` Milton Miller II
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1497581711523.17322@rackspace.com \
--to=adi.gangidi@rackspace.com \
--cc=abarrera@us.ibm.com \
--cc=anoo@us.ibm.com \
--cc=brad.debauche@RACKSPACE.COM \
--cc=chad.somerlot@RACKSPACE.COM \
--cc=kenneth.wilke@RACKSPACE.COM \
--cc=openbmc@lists.ozlabs.org \
--cc=rlippert@google.com \
--cc=ryan.dc.yu@foxconn.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.