<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" >Hi Patrick,</div>
<div dir="ltr" > </div>
<div dir="ltr" >Certain test cases which we tried through IPMI,Here are few.</div>
<div dir="ltr" > </div>
<div dir="ltr" >Valid conf</div>
<div dir="ltr" >=========</div>
<div dir="ltr" >ipmitool -I dbus lan set 1 ipsrc static<br>ipmitool -I dbus lan set 1 ipaddr x.x.x.x<br>ipmitool -I dbus lan set 1 netmask x.x.x.x<br>ipmitool -I dbus lan set 1 defgw ipaddr x.x.x.x<br>ipmitool -I dbus raw 0x06 0x40</div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<div dir="ltr" >InvalidIP</div>
<div dir="ltr" >========</div>
<div dir="ltr" >ipmitool -I dbus lan set 1 ipsrc static<br>ipmitool -I dbus lan set 1 ipaddr <invalid ip address><br>ipmitool -I dbus lan set 1 netmask x.x.x.x<br>ipmitool -I dbus lan set 1 defgw ipaddr x.x.x.x<br>ipmitool -I dbus raw 0x06 0x40</div>
<div dir="ltr" > </div>
<div dir="ltr" >Invalid Gateway</div>
<div dir="ltr" >=============</div>
<div dir="ltr" >ipmitool -I dbus lan set 1 ipsrc static<br>ipmitool -I dbus lan set 1 ipaddr 9.3.185.83<br>ipmitool -I dbus lan set 1 netmask 255.255.255.0<br>ipmitool -I dbus lan set 1 defgw ipaddr <invalid gateway><br>ipmitool -I dbus raw 0x06 0x40</div>
<div dir="ltr" > </div>
<div dir="ltr" >Regards</div>
<div dir="ltr" >Ratan Gupta</div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<blockquote data-history-content-modified="1" dir="ltr" style="border-left:solid #aaaaaa 2px; margin-left:5px; padding-left:5px; direction:ltr; margin-right:0px" >----- Original message -----<br>From: Patrick Venture <venture@google.com><br>To: Ratan K Gupta <ratagupt@in.ibm.com><br>Cc: Dave Cobbley <david.j.cobbley@linux.intel.com>, OpenBMC Maillist <openbmc@lists.ozlabs.org><br>Subject: Re: phoshor-network manager daemon + IPMI<br>Date: Tue, Oct 24, 2017 8:06 PM<br>
<div><font size="2" face="Default Monospace,Courier New,Courier,monospace" >On Tue, Oct 24, 2017 at 3:16 AM, Ratan K Gupta <ratagupt@in.ibm.com> wrote:<br>> Hi Dave,<br>><br>> We have enabled the link local address auto configuration,thats why you are<br>> noticing the link local address,<br>> But as a side effect of this,you should not notice this problem that the<br>> DHCP IP has not get assigned to the<br>> BMC.<br>><br>> Please try the "ip addr show dev eth0" instead of ifconfig.<br>><br>> Now days kernel supports ip aliasing where a single interface can have<br>> multiple ip adress,so on a intterface you may see link local address<br>> as well as DHCP assigned/Static Assigned IP address.<br>><br>> I have tried on our setup and it is working fine.<br><br>However, have you tried updating the IP address over IPMI? As part of<br>that code, it calls delete on those interfaces and IPs (all of them).<br>Which fails. Should there be logic in the ipmi daemon to only delete<br>non-local-link addresses? And then, if you try to delete a DHCP<br>assigned address, it also fails -- so how does one transition from<br>DHCP to static? I'd just like to hear how these cases were tested so<br>I can verify the problem is on my end with my configuration, or<br>possibly that more work is required before this is working fine.<br><br>><br>> Regards<br>> Ratan<br>><br>><br>> ----- Original message -----<br>> From: Patrick Venture <venture@google.com><br>> Sent by: "openbmc" <openbmc-bounces+ratagupt=in.ibm.com@lists.ozlabs.org><br>> To: Dave Cobbley <david.j.cobbley@linux.intel.com><br>> Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org><br>> Subject: Re: phoshor-network manager daemon + IPMI<br>> Date: Mon, Oct 23, 2017 11:59 PM<br>><br>> On Mon, Oct 23, 2017 at 10:18 AM, Dave Cobbley<br>> <david.j.cobbley@linux.intel.com> wrote:<br>>> I have been digging into the network manager as well.<br>>> The link local problem has been popping up on our systems as well.<br>>><br>>> I'm not sure why linklocaladdress causes our systems to get the 169.XX IP<br>>> Address.<br>>> I suspect is has something to do with the way our DHCP servers are setup<br>>> on<br>>> the network, systemd-networkd is not recognizing that we do in fact get an<br>>> IP from DHCP.<br>>><br>>> I'm assuming engineers at IBM are not seeing this behavior since the patch<br>>> was accepted (please correct me if I'm wrong).<br>>> Therefore this is more likely not a bug in systemd, but something strange<br>>> with the configuration of network infrastructure.<br>>> Either way, root cause needs to be identified.<br>>><br>>> To work around it, simply delete the line linklocaladdress=xxxx from<br>>> /etc/systemd/networkd/00-bmc-ethx.network<br>><br>> I ended up updating the default configuration file writer to not set<br>> that, then found that once it had DHCP=yes in it, it also would crash<br>> on attempt to delete (from the exception it raises when you try)<br>><br>>><br>>> Let me know if you make any more observations about the strange behavior<br>>> (it<br>>> would be nice to get past this issue).<br>>><br>>> Thanks,<br>>> -Dave Cobbley<br>>><br>>><br>>> On 10/23/2017 07:48 AM, Patrick Venture wrote:<br>>><br>>>> I'm curious if anyone has experience using the phosphor-network<br>>>> manager daemon. I've run into some oddities using it for instance, if<br>>>> you don't configure anything it sets up both links as LinkLocal and<br>>>> enables DHCP, etc -- and then even if DHCP fails, it doesn't update it<br>>>> (although it's aware of the failure) -- and when I then go to set the<br>>>> IP address over IPMI to a static IP, I run the two lan channel set<br>>>> commands which work (because they just set the object contents) --<br>>>> when i call "access on" over IPMI, it tries to delete all the dbus<br>>>> objects for the network, which fail because of checks in the network<br>>>> daemon that prevent this, which causes the network daemon to crash.<br>>>><br>>>> Ultimately I'm going to enable the host ipmi daemon to support<br>>>> multiple channels -- the trick is then to map the channel to an<br>>>> ethernet device... Some patches will be send up today to reviewing<br>>>> this type of change.<br>>>><br>>>> I'm going through the uses cases now trying to get it working, and<br>>>> just curious what I should be doing to get it to work.<br>>>><br>>>> Also of note, when I set the MAC address -- which works :), it doesn't<br>>>> update the configuration for the systemd network file with that<br>>>> information -- I'll be sending a patch for that today -- but I was<br>>>> curious if that was deliberate, etc.<br>>>><br>>>> Thanks,<br>>>> Patrick<br>>><br>>><br>><br>><br>><br>><br>></font><br> </div></blockquote>
<div dir="ltr" > </div></div><BR>