[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config
From: |
Al Chu |
Subject: |
Re: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config |
Date: |
Wed, 17 Nov 2010 12:34:56 -0800 |
Hey Holger,
By SVN Version, I assume you mean the head trunk, not the 0-8-0 stable
branch?
The primary differences between 0.8.10 and trunk is my call to "BMC boot
flag valid bit clearing" (param 3 as you describe below). My
recollection about this section is a little hazy, but I believe you want
to call this command so that boot parameters are permanently stored
(rather than being cleared after a reboot). Is this the side affect
you're witnessing?
Since this was a semi-big change, I decided not to backport it.
However, if you guys need it, I can go ahead and backport it into the
stable branch and release with the next version.
Al
On Wed, 2010-11-17 at 04:26 -0800, Liebig, Holger wrote:
> Hi Al,
> do you have any background info or remember what has caused the
> current change in the SVN version of ipmi-chassis-config versus the
> 0.8.10 in sending the Set Boot Device Parameter? It is working fine
> with the SVN version on our system, but the older version seems to
> have some side effects.
>
> Background is: A customer is trying to temporary set the Boot Option
> for booting into PXE for installation on a System under Solaris with
>
> ./ipmi-chassis-config --commit -e "Chassis_Boot_Flags:Boot_Device=PXE"
>
> As far as I can see from the trace, the SVN version sends
> Param 5 / Param 3 / Param 4
>
> While the slightly older version is sending
> Param 5 / Param 4
>
> In our Web Interface of the BMC we are sending (only disabling the 60 seconds
> timer with param 3):
> Param 3 / Param 5
>
> The customer wants to perform some unattended/scripted installation,
> so we recommended freeipmi to him but he currently only has the
> official release.
>
> Thanks,
> Holger Liebig
>
>
> _______________________________________________
> Freeipmi-devel mailing list
> address@hidden
> http://BLOCKEDlists.gnu.org/mailman/listinfo/freeipmi-devel
>
--
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory
- [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Peter Selby, 2010/11/15
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/15
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/15
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/16
- [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config, Liebig, Holger, 2010/11/17
- Re: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config,
Al Chu <=
- RE: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config, Liebig, Holger, 2010/11/18
- RE: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config, Al Chu, 2010/11/18
- RE: [Freeipmi-devel] Set Boot Device Parameter in ipmi-chassis-config, Liebig, Holger, 2010/11/22
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/16
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/17
- Message not available
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/17
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/17
- Message not available
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Al Chu, 2010/11/18
- Re: [Freeipmi-devel] fiid_obj_get: maximum_privilege_for_cipher_suite_3: no data set, Christopher Maestas, 2010/11/18