<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Nan,<br>
<br>
The Set Channel access command was decided to be used to mark the
end of a setting LAN configuration transaction.<br>
The patchset logically matches with using 'Set Channel Access' to
mark the end of set LAN configuration and<br>
apply the data from the cache.<br>
<br>
Regards,<br>
Tom<br>
<br>
<br>
<div class="moz-cite-prefix">On Thursday 03 November 2016 09:52 PM,
Li Nan wrote:<br>
</div>
<blockquote
cite="mid:TY1PR06MB08635DA92530A90D5D2C039DF6A30@TY1PR06MB0863.apcprd06.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi, Tom,</p>
<p>I show my #444 ( story: Confirm LAN device command meet IPMI
2.0 requirements ) implementation below. Want to clarify that
how it works.<br>
</p>
<br>
We did some experiments, so we got that ipmitool would issue
"set lan parameter" command like below:<br>
<div>For instance, change ip address.<br>
After we sent "ipmitool -I dbus lan set 1 ipaddr 1.2.3.4",
ipmitool would do:<br>
(1)sent Get Channel Info command.<br>
(2)echo "Setting LAN IP Address to 1.2.3.4" to the shell.<br>
(3)sent Get LAN <span>command to </span>fetch the value of
"set in progress"(which is 0x0) .<br>
(4)sent Set LAN command to change "set in progress" parameter
to "Set in Progress"(0x1).<br>
(5)sent Get LAN <span>command to </span>fetch the value of
"set in progress"( which is 0x1) .<br>
(6)sent Set LAN command to set "ip address" with value of
"A.B.C.D".<br>
(7)sent Get LAN command to fetch value of ip address.<br>
(8)sent Set LAN command to "commit write" by setting "set in
progress" to 0x2.<br>
(9)sent Set LAN command to set "set in progress " to "set
complete"(0x0).</div>
<br>
<br>
Because ipmitool would work like that, so we decided to use 2
steps to issue the changing of lan parameter:<br>
Step 1: <br>
Using Set LAN parameter command to cache the user setting. User
can input one item at a time to cache. So user can put items
into cache one be one in sequence.<br>
<br>
Step 2: <br>
Using Set Channel Access to apply those cached items.<br>
<br>
So the mechanism of my implementation is following above steps?
right?<br>
<a moz-do-not-send="true" previewremoved="true" id="LPlnk717207"
href="https://gerrit.openbmc-project.xyz/#/c/822/"
class="OWAAutoLink">https://gerrit.openbmc-project.xyz/#/c/822/</a><br>
<br>
<br>
B.R.<br>
Nan<br>
<br>
<br>
<div style="color: rgb(0, 0, 0);">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
face="Calibri, sans-serif" color="#000000"><b>From:</b>
openbmc
<a class="moz-txt-link-rfc2396E" href="mailto:openbmc-bounces+william.bjlinan=hotmail.com@lists.ozlabs.org"><openbmc-bounces+william.bjlinan=hotmail.com@lists.ozlabs.org></a>
on behalf of Li Nan <a class="moz-txt-link-rfc2396E" href="mailto:william.bjlinan@hotmail.com"><william.bjlinan@hotmail.com></a><br>
<b>Sent:</b> Monday, October 17, 2016 2:55 PM<br>
<b>To:</b> Patrick Williams; tomjose; Adriana Kobylak<br>
<b>Cc:</b> OpenBMC Maillist<br>
<b>Subject:</b> RE: IPMI LAN command story design - try
3rd send</font>
<div> </div>
</div>
<div>
<div id="divtagdefaultwrapper" style="font-size:12pt;
color:#000000;
font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Hi all,</p>
<p>I summarize IPMI LAN command flow here after our
discussion.</p>
<p><br>
</p>
When we want to change single ip address/Subnet
mask/Gateway address, ipmitool (the openbmc/ipmitool) will
automatically use a set of command to accomplish it, it
works like below:<br>
ex. we want to change ip address.<br>
After we send "ipmitool -I dbus lan set 1 ipaddr A.B.C.D",
ipmitool will do:<br>
(1)send Get Channel Info command.<br>
(2)echo "Setting LAN IP Address to A.B.C.D" to shell.<br>
(3)send Get LAN <span>command to </span>fetch the value
of "set in progress"(which is 0x0) .<br>
(4)send Set LAN command to change "set in progress"
parameter to "Set in Progress"(0x1).<br>
(5)send Get LAN <span>command to </span>fetch the value
of "set in progress"( which is 0x1) .<br>
(6)send Set LAN command to set "ip address" with value of
"A.B.C.D".<br>
(7)send Get LAN command to fetch value of ip address.<br>
(8)send Set LAN command to "commit write" by setting "set
in progress" to 0x2.<br>
(9)send Set LAN command to set "set in progress " to "set
complete"(0x0).<br>
<br>
It seems like ipmitool (some version) will automatically
send SET LAN command to change the value of "set in
progress" parameter. So "set in progress" can be used to
identify a transaction. The value of "set in progress"
can tell us the state of the procedure.<br>
<br>
I do my work by using "set in progress" to apply the user
settings.<br>
(1) If user want to change only single setting of "ip
address/subnet mask/gateway address ",<br>
The ipmid will cache the user setting, and wait for
"set complete"(<span>"set in progress" parameter value is
0x0).</span> When ipmid receives "set
complete", it will apply this user setting and the other
two reserved settings fetched from dbus(netman.py).<br>
a. If ipmitool don't send "set complete"
automatically, user can send raw command to send it.<br>
b. We also can send "set complete" in the
implementation of "set channel access" command mentioned
by Tom.<br>
So it will looks like that single setting will be applied
right away.<br>
<br>
(2)If user want to change two or three settings at the
same time:<br>
a. If the "set complete" don't be sent automatically
by ipmitool( some version ).<br>
The user can send settings one by one, and then
use a raw command(set complete) to apply them.<br>
It will works when running from local shell
(accessing it from serial port) or remote interface.<br>
b. If the "set complete" is sent automatically by
ipmitool.<br>
So the single change will be applied immediately,
the user can operate from a local interface.<br>
<br>
Please correct me!<br>
Thanks!<br>
<br>
<br>
<div style="color:rgb(0,0,0)">
<div>
<hr tabindex="-1" style="display:inline-block;
width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font
style="font-size:11pt" face="Calibri, sans-serif"
color="#000000"><b>寄件者:</b> Patrick Williams
<a class="moz-txt-link-rfc2396E" href="mailto:patrick@stwcx.xyz"><patrick@stwcx.xyz></a><br>
<b>寄件日期:</b> 2016年10月4日 上午 09:51<br>
<b>收件者:</b> tomjose<br>
<b>副本:</b> Li Nan; OpenBMC Maillist<br>
<b>主旨:</b> Re: IPMI LAN command story design - try
3rd send</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt">
<div class="PlainText">Forwarding to list.<br>
<br>
On Tue, Oct 04, 2016 at 03:02:54PM +0530, tomjose
wrote:<br>
> Hello Nan,<br>
> <br>
> The current implementation mandates the user
to enter <IP <br>
> Address>,<NetMask> and
<Gateway><br>
> for the network settings to be changed. Even
though the user wants to <br>
> change only the IP<br>
> address , because of the way we have
implemented we are forcing the user <br>
> to enter all the three details.<br>
> <br>
> The LAN settings is a property of the
channel(Channel 1 typically <br>
> corresponds to ETH0) and we can leverage<br>
> the "Set Channel Access" command to apply the
settings.We can apply the <br>
> network settings whenever the<br>
> Access Mode is turned on.(ipmitool lan set 1
access on)<br>
> <br>
> With the solution i am thinking , the Set LAN
configuration command <br>
> would not be used to apply the network<br>
> settings but it would be used to cache the
network settings and it would <br>
> be applied when the Set Channel Access<br>
> command is called.<br>
> <br>
> The following link explains the order of
commands.<br>
> <br>
> <a moz-do-not-send="true"
previewremoved="true" id="LPlnk534825"
href="https://www.thomas-krenn.com/en/wiki/Configuring_IPMI_under_Linux_using_ipmitool%28LAN">https://www.thomas-krenn.com/en/wiki/Configuring_IPMI_under_Linux_using_ipmitool(LAN</a>
<br>
> Configuration section)<br>
> <br>
> Regarding #2 - Authentication Type Support,
it seems that this section <br>
> is not updated properly.<br>
> Get Channel Authentication capabilities is
the first command issued for <br>
> a session setup.<br>
> This command also has the same Authentication
type support field and the <br>
> 7th bit which<br>
> was reserved in #2 is used in this command to
specify IPMI2.0 and <br>
> IPMI1.5 authentication<br>
> capabilities.<br>
> <br>
> So since #2 is outdated to represent the
necessary authentication <br>
> capabilities, i think we do<br>
> not need to support parameter #2.<br>
> <br>
> Regarding #3 - Authentication Type Enables -
this is needed if we <br>
> support different authentication<br>
> types for different requested privilege
levels. Since the authentication <br>
> types are outdated and we<br>
> do not support different authentication types
per privilege levels, we <br>
> can avoid this parameter.<br>
> <br>
> Thanks,<br>
> Tom<br>
> <br>
> <br>
> <br>
> <br>
> On Monday 03 October 2016 07:29 PM, Li Nan
wrote:<br>
> ><br>
> > Hi team,<br>
> ><br>
> > I'm working on the story of Confirm LAN
Command meet IPMI 2.0<br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk92767"
href="https://github.com/openbmc/openbmc/issues/444">
https://github.com/openbmc/openbmc/issues/444</a><br>
> ><br>
> ><br>
> > <<a moz-do-not-send="true"
previewremoved="true" id="LPlnk951354"
href="https://github.com/openbmc/openbmc/issues/444">https://github.com/openbmc/openbmc/issues/444</a>><br>
> ><br>
> > I summarize some fields of settings
below, and need some help to <br>
> > confirm the direction of my work.<br>
> ><br>
> > ```<br>
> ><br>
> ><br>
> > 1.IPMI LAN command status and work
plan<br>
> ><br>
> ><br>
> > 1.1.Current status<br>
> ><br>
> > IPMI LAN command consists of 4 command (
refer to IPMI 2.0 Spec, <br>
> > Chapter 23 ):Set LAN Configuration
Parameters, Get LAN Configuration <br>
> > Parameters, Suspend BMC ARPs and Get
IP/UDP/RMCP Statistics.<br>
> ><br>
> > Existing code includes implementation of
Set/Get LAN configuration <br>
> > Parameters. ( Refer to <br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk167726"
href="https://github.com/openbmc/phosphor-host-ipmid/blob/master/transporthandler.cpp">https://github.com/openbmc/phosphor-host-ipmid/blob/master/transporthandler.cpp</a>
<div
id="LPBorder_GT_14766818700840.05824222564837944"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766818700750.04617596189747686"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="1"
id="ImageCell_14766818700770.22403254259142635"
style="width:250px; display:table-cell;
padding-right:20px">
<div
id="LPImageContainer_14766818700770.18778244300042013"
style="background-color:rgb(255,255,255);
height:250px; margin:auto;
display:table; width:250px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-host-ipmid/blob/master/transporthandler.cpp"
id="LPImageAnchor_14766818700780.03597320227273715"
style="display:table-cell;
text-align:center"><img
moz-do-not-send="true"
id="LPThumbnailImageID_14766818700790.5823514274096728"
style="display:inline-block;
max-width:250px; max-height:250px;
height:250px; width:250px;
border-width:0px;
vertical-align:bottom"
src="imap://tomjose@imap.linux.ibm.com:993/fetch%3EUID%3E.Drafts%3E21?v=3&s=400"
height="250" width="250"></a></div>
</td>
<td colspan="2"
id="TextCell_14766818700810.2512003816386229"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766818700810.02701722095618142"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-host-ipmid/blob/master/transporthandler.cpp"
id="LPUrlAnchor_14766818700820.3482927685581906"
style="text-decoration:none">openbmc/phosphor-host-ipmid</a></div>
<div
id="LPMetadata_14766818700830.7014328133428414"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
github.com</div>
<div
id="LPDescription_14766818700830.8547523260280545"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
phosphor-host-ipmid - dbus-based ipmid
for host-endpoint IPMI commands</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> > )<br>
> ><br>
> ><br>
> > 1.2.IPMI LAN Command Handling<br>
> ><br>
> > Example for Set LAN Configuration
Parameters.<br>
> ><br>
> > Parameter<br>
> ><br>
> > <br>
> ><br>
> > #<br>
> ><br>
> > Number<br>
> ><br>
> > <br>
> ><br>
> > IPMI handling<br>
> ><br>
> > <br>
> ><br>
> > dbus method<br>
> ><br>
> > Set In Progress(Volatile)<br>
> ><br>
> > <br>
> ><br>
> > 0<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
209.<br>
> ><br>
> > variable lan_set_in_progress act as a
statemachine.<br>
> ><br>
> > <br>
> ><br>
> > No need.<br>
> ><br>
> > Authentication Type Support(Read Only)<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
305.<br>
> ><br>
> > Setto 0x4 (MD5)<br>
> ><br>
> > <br>
> ><br>
> > No need.<br>
> ><br>
> > Authentication Type<br>
> ><br>
> > Enables<br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
311.<br>
> ><br>
> > Set to 0x4, 0x4, 0x4, 0x4, 0x4.<br>
> ><br>
> > <br>
> ><br>
> > No need.<br>
> ><br>
> > IP Address<br>
> ><br>
> > <br>
> ><br>
> > 3<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
169.<br>
> ><br>
> > <br>
> ><br>
> > phosphor-neworkd/netman.py: Line 266:
SetAddress4<br>
> ><br>
> > MAC Address<br>
> ><br>
> > (can be Read Only)<br>
> ><br>
> > <br>
> ><br>
> > 5<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
174.<br>
> ><br>
> > <br>
> ><br>
> > phosphor-neworkd/netman.py: Line 334:
SetHwAddress.<br>
> ><br>
> > Subnet Mask<br>
> ><br>
> > <br>
> ><br>
> > 6<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
199.<br>
> ><br>
> > <br>
> ><br>
> > phosphor-neworkd/netman.py: Line 266:
SetAddress4<br>
> ><br>
> > Default Gateway Address<br>
> ><br>
> > <br>
> ><br>
> > 12<br>
> ><br>
> > <br>
> ><br>
> >
phosphor-host-ipmid/transporthandler.cpp, Line
204.<br>
> ><br>
> > <br>
> ><br>
> > phosphor-neworkd/netman.py: Line 266:
SetAddress4<br>
> ><br>
> > Handling of Get LAN Configuration
Parameters command is similar to Set <br>
> > LAN Configuration Parameters. Refer to <br>
> > phosphor-host-ipmid/transporthandler.cpp
and phosphor-networkd/netman.py.<br>
> ><br>
> ><br>
> > 1.3.Gap between current code and
IPMI Spec 2.0<br>
> ><br>
> > LAN Configuration Parameter List<br>
> ><br>
> > Parameter<br>
> ><br>
> > <br>
> ><br>
> > #<br>
> ><br>
> > Number<br>
> ><br>
> > <br>
> ><br>
> > Parameter Data( non-volatile unless
otherwise noted )<br>
> ><br>
> > <br>
> ><br>
> > Bit field<br>
> ><br>
> > <br>
> ><br>
> > Description<br>
> ><br>
> > <br>
> ><br>
> > Current status/Note<br>
> ><br>
> > ( Yes = current support.<br>
> ><br>
> > No = not support. )<br>
> ><br>
> > Set In Progress(Volatile)<br>
> ><br>
> > <br>
> ><br>
> > 0<br>
> ><br>
> > <br>
> ><br>
> > byte 1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 00b -= set complete<br>
> ><br>
> > 0ab = set in progress<br>
> ><br>
> > 10b = commit write<br>
> ><br>
> > 11b = reserved<br>
> ><br>
> > <br>
> ><br>
> > Yes<br>
> ><br>
> > Authentication Type Support(Read Only)<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > byte 1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Authentication type(s) enabled for this
channel(bi0tfield):<br>
> ><br>
> > All bits: 1b =supported<br>
> ><br>
> > 0b= authentication type not available
for use.<br>
> ><br>
> > [5] – OEM proprietary<br>
> ><br>
> > [4] – straight password / key<br>
> ><br>
> > [3] – reserved<br>
> ><br>
> > [2] – MD5<br>
> ><br>
> > [1] – MD2<br>
> ><br>
> > [0] - none<br>
> ><br>
> > <br>
> ><br>
> > Yes.<br>
> ><br>
> > MD5<br>
> ><br>
> > Authenticaton Type<br>
> ><br>
> > Enables<br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > This field is used to configure which
Authentication Types are <br>
> > available for use when a remote console
activates an IPMI messaging <br>
> > connection to the BMC for a given
requested maximum privilege level.<br>
> ><br>
> > <br>
> ><br>
> > Yes.<br>
> ><br>
> > MD5<br>
> ><br>
> > IP Address<br>
> ><br>
> > <br>
> ><br>
> > 3<br>
> ><br>
> > <br>
> ><br>
> > data 1:4<br>
> ><br>
> > MS-byte first<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > IP Address<br>
> ><br>
> > <br>
> ><br>
> > Yes<br>
> ><br>
> > IP Address Source<br>
> ><br>
> > <br>
> ><br>
> > 4<br>
> ><br>
> > <br>
> ><br>
> > data1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > address source<br>
> ><br>
> > 0h – unspecified<br>
> ><br>
> > 1h = static address (manually
configured)<br>
> ><br>
> > 2h = address obtained by BMC running
DHCP<br>
> ><br>
> > 3h = address loaded by BIOS or system
software<br>
> ><br>
> > 4h = address obtained by BMC running
other address assignment protocol<br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > MAC Address<br>
> ><br>
> > (can be Read Only)<br>
> ><br>
> > <br>
> ><br>
> > 5<br>
> ><br>
> > <br>
> ><br>
> > data 1:6<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > MAC Address for messages transmitted
from BMC.<br>
> ><br>
> > MS-byte first.<br>
> ><br>
> > <br>
> ><br>
> > Yes.<br>
> ><br>
> > Subnet Mask<br>
> ><br>
> > <br>
> ><br>
> > 6<br>
> ><br>
> > <br>
> ><br>
> > data1:4<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Yes<br>
> ><br>
> > IPv4 Header Parameter<br>
> ><br>
> > <br>
> ><br>
> > 7<br>
> ><br>
> > <br>
> ><br>
> > data1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No<br>
> ><br>
> > Primary RMCP Port Number(optional)<br>
> ><br>
> > <br>
> ><br>
> > 8<br>
> ><br>
> > <br>
> ><br>
> > data1:2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Secondary RMCP Port Number(optional)<br>
> ><br>
> > <br>
> ><br>
> > 9<br>
> ><br>
> > <br>
> ><br>
> > data1:2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > BMC-generated ARP control (optional)<br>
> ><br>
> > <br>
> ><br>
> > 10<br>
> ><br>
> > <br>
> ><br>
> > data1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Gratuitous ARP interval (optional)<br>
> ><br>
> > <br>
> ><br>
> > 11<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Default GatewayAddress<br>
> ><br>
> > <br>
> ><br>
> > 12<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Yes<br>
> ><br>
> > Default Gateway MAC Address<br>
> ><br>
> > <br>
> ><br>
> > 13<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Backup Gateway Address<br>
> ><br>
> > <br>
> ><br>
> > 14<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Backup Gateway MAC Address<br>
> ><br>
> > <br>
> ><br>
> > 15<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Community String<br>
> ><br>
> > <br>
> ><br>
> > 16<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Number of Destinations( Read Only )<br>
> ><br>
> > <br>
> ><br>
> > 17<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Destination Type (volatile /
non-volatile – see description )<br>
> ><br>
> > <br>
> ><br>
> > 18<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Destination Address<br>
> ><br>
> > <br>
> ><br>
> > 19<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Following parameters are introduced with
IPMI v2.0/RMCP+<br>
> ><br>
> > 802.1q VLAN ID (12-bit)<br>
> ><br>
> > <br>
> ><br>
> > 20<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > 802.1q VLAN Priority<br>
> ><br>
> > <br>
> ><br>
> > 21<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > RMCP+ Messaging Cipher Suite Entry
Support( Read Only )<br>
> ><br>
> > <br>
> ><br>
> > 22<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > RMCP+ Messaging Cipher Suite Entries(
Read Only )<br>
> ><br>
> > <br>
> ><br>
> > 23<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > RMCP+ Messaging Cipher Suite Privilege
Levels<br>
> ><br>
> > <br>
> ><br>
> > 24<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Destination Address VLAN TAGs<br>
> ><br>
> > <br>
> ><br>
> > 25<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Bad Password Threshold<br>
> ><br>
> > <br>
> ><br>
> > 26<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6/IPv4 Support<br>
> ><br>
> > <br>
> ><br>
> > 50<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6/IPv4 Addressing Enables<br>
> ><br>
> > <br>
> ><br>
> > 51<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6/IPv4 Header Static Traffic Class<br>
> ><br>
> > <br>
> ><br>
> > 52<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Header Static Hop Limit<br>
> ><br>
> > <br>
> ><br>
> > 53<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Header Flow Label<br>
> ><br>
> > <br>
> ><br>
> > 54<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Status<br>
> ><br>
> > <br>
> ><br>
> > 55<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Addresses<br>
> ><br>
> > <br>
> ><br>
> > 56<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Static DUID storage length<br>
> ><br>
> > <br>
> ><br>
> > 57<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Static DUIDs<br>
> ><br>
> > <br>
> ><br>
> > 58<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic ( SLAAC/DHCPv6) Address<br>
> ><br>
> > <br>
> ><br>
> > 59<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Dynamic DUID storage length<br>
> ><br>
> > <br>
> ><br>
> > 60<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Dynamic DUIDs<br>
> ><br>
> > <br>
> ><br>
> > 61<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Timing Configuration Support<br>
> ><br>
> > <br>
> ><br>
> > 62<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 DHCPv6 Timing & Configuration<br>
> ><br>
> > <br>
> ><br>
> > 63<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Router Address Configuration
Control<br>
> ><br>
> > <br>
> ><br>
> > 64<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 1 IP Address<br>
> ><br>
> > <br>
> ><br>
> > 65<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 1 MAC Address<br>
> ><br>
> > <br>
> ><br>
> > 66<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 1 Prefix Length<br>
> ><br>
> > <br>
> ><br>
> > 67<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 1 Prefix Value<br>
> ><br>
> > <br>
> ><br>
> > 68<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 2 Address<br>
> ><br>
> > <br>
> ><br>
> > 69<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 2 MAC Address<br>
> ><br>
> > <br>
> ><br>
> > 70<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 2 Prefix Length<br>
> ><br>
> > <br>
> ><br>
> > 71<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Static Router 2 Prefix Value<br>
> ><br>
> > <br>
> ><br>
> > 72<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > Number of Dynamic Router Info Sets<br>
> ><br>
> > <br>
> ><br>
> > 73<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic Router Info IP Address<br>
> ><br>
> > <br>
> ><br>
> > 74<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic Router Info MAC Address<br>
> ><br>
> > <br>
> ><br>
> > 75<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic Router Info Prefix Length<br>
> ><br>
> > <br>
> ><br>
> > 76<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic Router Info Prefix Value<br>
> ><br>
> > <br>
> ><br>
> > 77<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Dynamic Router Received Hop Limit<br>
> ><br>
> > <br>
> ><br>
> > 78<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Neighbor Discovery / SLAAC Timing
Configuration Support<br>
> ><br>
> > <br>
> ><br>
> > 79<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > IPv6 Neighbor Discovery / SLAAC Timing
Configuration<br>
> ><br>
> > <br>
> ><br>
> > 80<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> > OEM Parameters<br>
> ><br>
> > <br>
> ><br>
> > 192:255<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > No.<br>
> ><br>
> ><br>
> > 1.4.Work Plan<br>
> ><br>
> ><br>
> > 1.4.1.Set LAN Configuration
Parameters<br>
> ><br>
> ><br>
> > 1.4.2.Get LAN Configuration
Parameters<br>
> ><br>
> > I figure out what we support in
phosphor-netwokd repo ( Refer to:<br>
> ><br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk841780"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py">https://github.com/openbmc/phosphor-networkd/blob/master/netman.py</a>
) :
<div
id="LPBorder_GT_14766819138340.9971102762841955"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766819138300.49168501737801407"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="1"
id="ImageCell_14766819138310.9478808330593138"
style="width:250px; display:table-cell;
padding-right:20px">
<div
id="LPImageContainer_14766819138310.8455049406206201"
style="background-color:rgb(255,255,255);
height:250px; margin:auto;
display:table; width:250px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPImageAnchor_14766819138320.35430488158962925"
style="display:table-cell;
text-align:center"><img
moz-do-not-send="true"
id="LPThumbnailImageID_14766819138320.00471319408841131"
style="display:inline-block;
max-width:250px; max-height:250px;
height:250px; width:250px;
border-width:0px;
vertical-align:bottom"
src="imap://tomjose@imap.linux.ibm.com:993/fetch%3EUID%3E.Drafts%3E21?v=3&s=400"
height="250" width="250"></a></div>
</td>
<td colspan="2"
id="TextCell_14766819138320.898093031037314"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766819138320.1933719939370082"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPUrlAnchor_14766819138330.19332660816654357"
style="text-decoration:none">openbmc/phosphor-networkd</a></div>
<div
id="LPMetadata_14766819138330.34968770727396603"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
github.com</div>
<div
id="LPDescription_14766819138330.48350723642352855"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
Contribute to phosphor-networkd
development by creating an account on
GitHub.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> ><br>
> > * Set In Progress,<br>
> > * Authentication Type Support,<br>
> > * Authentication Type Enables,<br>
> > * IP Address,<br>
> > * MAC Address,<br>
> > * Subnet Mask,<br>
> > * Default Gateway Address<br>
> ><br>
> > So I think we only support existing
configuration.<br>
> ><br>
> > How can I implement the rest of the
configurations/parameters? (open <br>
> > issues?)<br>
> ><br>
> ><br>
> > 1.4.3.ARP<br>
> ><br>
> > Not implemented in Tom’s IPMI network
story.<br>
> ><br>
> > Should I refer to <br>
> >
openbmc/import-layers/meta-openembedded/meta-networking/recipes-support/arptables<br>
> > ?<br>
> ><br>
> > Optional command. Not to implement?<br>
> ><br>
> ><br>
> > 1.4.4.IP/UDP/RMCP statistics<br>
> ><br>
> > Seems like it was not implemented in
obmc stories too.<br>
> ><br>
> > This is an optional command. Not to
implement?<br>
> ><br>
> ><br>
> > 2.IPMI LAN Commands in IPMI Spec 2.0
-- Format<br>
> ><br>
> ><br>
> > 1.1.Set LAN Configuration Parameters
command<br>
> ><br>
> > Set LAN Configuration Parameters command<br>
> ><br>
> > <br>
> ><br>
> > Byte<br>
> ><br>
> > <br>
> ><br>
> > Bit field<br>
> ><br>
> > <br>
> ><br>
> > Description<br>
> ><br>
> > <br>
> ><br>
> > Support<br>
> ><br>
> > Request Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > [7:4]<br>
> ><br>
> > <br>
> ><br>
> > reserved<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [3:0]<br>
> ><br>
> > <br>
> ><br>
> > Channel number<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Parameter selector<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 3:N<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Configuration parameter data<br>
> ><br>
> > <br>
> ><br>
> > Response Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > Completion code<br>
> ><br>
> > <br>
> ><br>
> > 80h = parameter not supported.<br>
> ><br>
> > 81h = attempt to set the ‘set in
progress’ value (in parameter #0) <br>
> > when not in the ‘set complete’ state.
(This completion code provides a <br>
> > way to recognize that another party has
already ‘claimed’ the parameters)<br>
> ><br>
> > 82h = attempt to write read-only
parameter<br>
> ><br>
> > 83h = attempt to read write-only
parameter<br>
> ><br>
> > <br>
> ><br>
> > Existing code supports 7 LAN command:<br>
> ><br>
> > Set In Progress,<br>
> ><br>
> > Authentication Type Support,<br>
> ><br>
> > Authentication Type Enables,<br>
> ><br>
> > IP Address,<br>
> ><br>
> > MAC Address,<br>
> ><br>
> > Subnet Mask,<br>
> ><br>
> > Default Gateway Address.<br>
> ><br>
> > Refer to:<br>
> ><br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk744383"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py">https://github.com/openbmc/phosphor-networkd/blob/master/netman.py</a>
<div
id="LPBorder_GT_14766819135190.6239112483099216"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766819135120.08389837769896258"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="1"
id="ImageCell_14766819135140.6500910262786991"
style="width:250px; display:table-cell;
padding-right:20px">
<div
id="LPImageContainer_14766819135140.9650201116072317"
style="background-color:rgb(255,255,255);
height:250px; margin:auto;
display:table; width:250px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPImageAnchor_14766819135160.6062355250061481"
style="display:table-cell;
text-align:center"><img
moz-do-not-send="true"
id="LPThumbnailImageID_14766819135160.20224388578162777"
style="display:inline-block;
max-width:250px; max-height:250px;
height:250px; width:250px;
border-width:0px;
vertical-align:bottom"
src="imap://tomjose@imap.linux.ibm.com:993/fetch%3EUID%3E.Drafts%3E21?v=3&s=400"
height="250" width="250"></a></div>
</td>
<td colspan="2"
id="TextCell_14766819135170.7569986700643088"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766819135170.7474263517441381"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPUrlAnchor_14766819135180.6969831556499485"
style="text-decoration:none">openbmc/phosphor-networkd</a></div>
<div
id="LPMetadata_14766819135180.8794501172291314"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
github.com</div>
<div
id="LPDescription_14766819135190.7176377054560807"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
Contribute to phosphor-networkd
development by creating an account on
GitHub.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> ><br>
> > 1.2.Get LAN Configuration Parameters
Command<br>
> ><br>
> > Get LAN Configuration Parameters Command<br>
> ><br>
> > <br>
> ><br>
> > Byte<br>
> ><br>
> > <br>
> ><br>
> > Bit field<br>
> ><br>
> > <br>
> ><br>
> > Description<br>
> ><br>
> > <br>
> ><br>
> > Support<br>
> ><br>
> > Request Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > [7]<br>
> ><br>
> > <br>
> ><br>
> > 0b = get parameter<br>
> ><br>
> > 1b = get parameter revision only<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [6:4]<br>
> ><br>
> > <br>
> ><br>
> > reserved<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [3:0]<br>
> ><br>
> > <br>
> ><br>
> > Channel number<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Parameter selector<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 3<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Set Selector. Selects a given set of
parameters under a given <br>
> > Parameter selector value.<br>
> ><br>
> > 00h if parameter don’t use a Set
Selector.<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 4<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Block Selector (00h if parameter does
not require a block number)<br>
> ><br>
> > <br>
> ><br>
> > Response Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > [7:0]<br>
> ><br>
> > <br>
> ><br>
> > Completion Code.<br>
> ><br>
> > Generic codes, plus following
command-specific completion code(s):<br>
> ><br>
> > 80h = parameter not supported.<br>
> ><br>
> > <br>
> ><br>
> > Existing code supports 7 LAN command:<br>
> ><br>
> > Set In Progress,<br>
> ><br>
> > Authentication Type Support,<br>
> ><br>
> > Authentication Type Enables,<br>
> ><br>
> > IP Address,<br>
> ><br>
> > MAC Address,<br>
> ><br>
> > Subnet Mask,<br>
> ><br>
> > Default Gateway Address.<br>
> ><br>
> > Refer to <br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk958940"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py">https://github.com/openbmc/phosphor-networkd/blob/master/netman.py</a>
<div
id="LPBorder_GT_14766819147140.6668788369201359"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766819147100.8097039239314443"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="1"
id="ImageCell_14766819147110.0495730902037691"
style="width:250px; display:table-cell;
padding-right:20px">
<div
id="LPImageContainer_14766819147110.5637199434999036"
style="background-color:rgb(255,255,255);
height:250px; margin:auto;
display:table; width:250px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPImageAnchor_14766819147120.30565978863141496"
style="display:table-cell;
text-align:center"><img
moz-do-not-send="true"
id="LPThumbnailImageID_14766819147120.6082135988960494"
style="display:inline-block;
max-width:250px; max-height:250px;
height:250px; width:250px;
border-width:0px;
vertical-align:bottom"
src="imap://tomjose@imap.linux.ibm.com:993/fetch%3EUID%3E.Drafts%3E21?v=3&s=400"
height="250" width="250"></a></div>
</td>
<td colspan="2"
id="TextCell_14766819147120.19826267871748815"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766819147120.9875276876214526"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/phosphor-networkd/blob/master/netman.py"
id="LPUrlAnchor_14766819147130.28471537318808626"
style="text-decoration:none">openbmc/phosphor-networkd</a></div>
<div
id="LPMetadata_14766819147130.9575567594901078"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
github.com</div>
<div
id="LPDescription_14766819147140.9548671389913977"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
Contribute to phosphor-networkd
development by creating an account on
GitHub.</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > [7:0]<br>
> ><br>
> > <br>
> ><br>
> > Parameter revision.<br>
> ><br>
> > Format: MSN = present revision. LSN =
oldest revision parameter is <br>
> > backward compatible with. 11h for
parameters in this specification.<br>
> ><br>
> > <br>
> ><br>
> > The following data bytes are not
returned when the ‘get parameter <br>
> > revision only’ bit is 1b.<br>
> ><br>
> > <br>
> ><br>
> > 3:N<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Configuration parameter data.<br>
> ><br>
> > If the rollback feature is implemented,
the BMC makes a copy of the <br>
> > existing parameters when the ‘set in
progress’ state becomes asserted <br>
> > (See the Set in Progress parameter #0).
While the ‘set in progress’ <br>
> > state is active, the BMC will return
data from this copy of the <br>
> > parameters, plus any uncommitted changes
that were made to data. <br>
> > Otherwise, the BMC returns parameter
data from non-volatile storage.<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> ><br>
> > 1.2.1.DHCPv6 Timing Parameters<br>
> ><br>
> > Not support.<br>
> ><br>
> ><br>
> > 1.2.2.Neighbor discovery / SLAAC
Timing Parameters<br>
> ><br>
> > Not support.<br>
> ><br>
> ><br>
> > 1.3.Suspend BMC ARPs command<br>
> ><br>
> > Suspend BMC ARPs Command<br>
> ><br>
> > <br>
> ><br>
> > Byte<br>
> ><br>
> > <br>
> ><br>
> > Bit field<br>
> ><br>
> > <br>
> ><br>
> > Description<br>
> ><br>
> > <br>
> ><br>
> > Support<br>
> ><br>
> > Request<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > [7:4]<br>
> ><br>
> > <br>
> ><br>
> > Reserved<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [3:0]<br>
> ><br>
> > <br>
> ><br>
> > Channel number<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > [7:2]<br>
> ><br>
> > <br>
> ><br>
> > Reserved<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [1]<br>
> ><br>
> > <br>
> ><br>
> > ARP response suspend.<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [0]<br>
> ><br>
> > <br>
> ><br>
> > Gratuitous ARP suspend<br>
> ><br>
> > <br>
> ><br>
> > Respond<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Completion code<br>
> ><br>
> > <br>
> ><br>
> > Do not support.<br>
> ><br>
> > ( Should refer to<br>
> ><br>
> >
openbmc/import-layers/meta-openembedded/meta-networking/recipes-support/arptables?<br>
> > )<br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > present state o f ARP suspension<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [7:2]<br>
> ><br>
> > <br>
> ><br>
> > reserve<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [1]<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [0]<br>
> ><br>
> > <br>
> ><br>
> > Address Resolution Protocol.<br>
> ><br>
> ><br>
> > 1.4.Get IP/UDP/RMCP Statistics
Command<br>
> ><br>
> > Get IP/UDP/RMCP Statistics Command<br>
> ><br>
> > <br>
> ><br>
> > Byte<br>
> ><br>
> > <br>
> ><br>
> > Bit field<br>
> ><br>
> > <br>
> ><br>
> > Description<br>
> ><br>
> > <br>
> ><br>
> > Support<br>
> ><br>
> > Request Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > [7:4]<br>
> ><br>
> > <br>
> ><br>
> > reserved<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [3:0]<br>
> ><br>
> > <br>
> ><br>
> > Channel number<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > 2<br>
> ><br>
> > <br>
> ><br>
> > [7:1]<br>
> ><br>
> > <br>
> ><br>
> > clear statistics<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > [0]<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Respond Data<br>
> ><br>
> > <br>
> ><br>
> > 1<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Completion Code<br>
> ><br>
> > <br>
> ><br>
> > RMCP is implemented in openbmc.<br>
> ><br>
> > Refer to<br>
> ><br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk583796"
href="https://github.com/openbmc/openbmc/issues/432">
https://github.com/openbmc/openbmc/issues/432</a>
and so on.
<div
id="LPBorder_GT_14766819296010.08766393403426853"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766819295980.7597078110033914"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="1"
id="ImageCell_14766819295980.41917779631970675"
style="width:250px; display:table-cell;
padding-right:20px">
<div
id="LPImageContainer_14766819295980.7600807129623182"
style="background-color:rgb(255,255,255);
height:250px; margin:auto;
display:table; width:250px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/openbmc/issues/432"
id="LPImageAnchor_14766819295990.6128558181951922"
style="display:table-cell;
text-align:center"><img
moz-do-not-send="true"
id="LPThumbnailImageID_14766819295990.4969585489793553"
style="display:inline-block;
max-width:250px; max-height:250px;
height:250px; width:250px;
border-width:0px;
vertical-align:bottom"
src="imap://tomjose@imap.linux.ibm.com:993/fetch%3EUID%3E.Drafts%3E21?v=3&s=400"
height="250" width="250"></a></div>
</td>
<td colspan="2"
id="TextCell_14766819295990.6756862189963907"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766819295990.8550862643091643"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://github.com/openbmc/openbmc/issues/432"
id="LPUrlAnchor_14766819296000.716335010636254"
style="text-decoration:none">Attaching
RMCP session to SOL. · Issue #432 ·
openbmc/openbmc</a></div>
<div
id="LPMetadata_14766819296000.4360842965316961"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
github.com</div>
<div
id="LPDescription_14766819296000.23569221320232991"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
openbmc - OpenBMC Distribution</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> ><br>
> > Discussed with Tom, these statistics is
not implemented in <br>
> > phosphor-networkd.<br>
> ><br>
> > <br>
> ><br>
> > 2:3<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > IP Packets Received.<br>
> ><br>
> > <br>
> ><br>
> > 4:5<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Received IP Header Errors<br>
> ><br>
> > <br>
> ><br>
> > 6:7<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Received IP Address Errors<br>
> ><br>
> > <br>
> ><br>
> > 8:9<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Fragmented IP Packets Received<br>
> ><br>
> > <br>
> ><br>
> > 10:11<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > IP Packets Transmitted<br>
> ><br>
> > <br>
> ><br>
> > 12:13<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > UDP Packets Received<br>
> ><br>
> > <br>
> ><br>
> > 14:15<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > Valid RMCP Received<br>
> ><br>
> > <br>
> ><br>
> > 16:17<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > UDP Proxy Packets Received<br>
> ><br>
> > <br>
> ><br>
> > 18:19<br>
> ><br>
> > <br>
> ><br>
> > <br>
> ><br>
> > UDP Proxy Packets dropped<br>
> ><br>
> ><br>
> > 3.End<br>
> ><br>
> > ```<br>
> ><br>
> ><br>
> ><br>
> ><br>
> >
_______________________________________________<br>
> > openbmc mailing list<br>
> > <a class="moz-txt-link-abbreviated" href="mailto:openbmc@lists.ozlabs.org">openbmc@lists.ozlabs.org</a><br>
> > <a moz-do-not-send="true"
previewremoved="true" id="LPlnk28027"
href="https://lists.ozlabs.org/listinfo/openbmc">
https://lists.ozlabs.org/listinfo/openbmc</a>
<div
id="LPBorder_GT_14766819287120.6266425907266072"
style="margin-bottom:20px; overflow:auto;
width:100%; text-indent:0px">
<table
id="LPContainer_14766819287090.6607366742832055"
style="width:90%;
background-color:rgb(255,255,255);
overflow:auto; padding-top:20px;
padding-bottom:20px; margin-top:20px;
border-top:1px dotted rgb(200,200,200);
border-bottom:1px dotted rgb(200,200,200)"
cellspacing="0">
<tbody>
<tr style="border-spacing:0px" valign="top">
<td colspan="2"
id="TextCell_14766819287100.7675997449482372"
style="vertical-align: top; padding:
0px; display: table-cell; position:
relative;">
<div
id="LPTitle_14766819287100.7339780245568891"
style="top:0px; color:rgb(0,120,215);
font-weight:400; font-size:21px;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
line-height:21px">
<a moz-do-not-send="true"
target="_blank"
href="https://lists.ozlabs.org/listinfo/openbmc"
id="LPUrlAnchor_14766819287110.19315001819689293"
style="text-decoration:none">openbmc
Info Page - OzLabs</a></div>
<div
id="LPMetadata_14766819287110.39149908406025946"
style="margin:10px 0px 16px;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:14px">
lists.ozlabs.org</div>
<div
id="LPDescription_14766819287110.12085490578539615"
style="display:block;
color:rgb(102,102,102);
font-weight:400;
font-family:"Microsoft JHengHei
UI","Microsoft
JHengHei","微軟正黑體",MingLiU,"細明體",sans-serif;
font-size:14px; line-height:20px;
max-height:100px; overflow:hidden">
To see the collection of prior
postings to the list, visit the
openbmc Archives. Using openbmc: To
post a message to all the list
members, send email ...</div>
</td>
</tr>
</tbody>
</table>
</div>
<br>
> <br>
<br>
-- <br>
Patrick Williams<br>
</div>
</span></font><br>
</div>
</div>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>