Thanks for your reply.
You have said that these problems are due to compliance problems of BMCs.
Would you please let me know your suggestions to overcome these issues?

Thank you,
Arun



On 7/24/06, Corey Minyard <[EMAIL PROTECTED]> wrote:
Arun Babu wrote:
> I am trying to write an application which needs to perform certain
> operation on a sensor exceeding thresholds.
> The sample3.c provided with the distribution is very useful and I
> tried it..
>
> 1. The program detects sensors and are reported successfully. (It
> reports reading type as threshold for all of the sensors). On reading
> the values, the program reads for some of them successfully, whereas
> for several of them i have the error below:
> Error 0x1000016 getting discrete states for sensor (0.0).3V3BATTERY
> Error 0x1000016 getting discrete states for sensor (0.0).+2.5VIN
> Error 0x1000016 getting discrete states for sensor ( 0.0).+1.25VIN
> Error 0x1000016 getting discrete states for sensor (0.0).VDD5VIN
> Error 0x1000016 getting discrete states for sensor (0.0).VDD_3VIN
> Error 0x1000016 getting discrete states for sensor ( 0.0).H0VDD_CORE
> Error 0x1000016 getting discrete states for sensor (0.0).H1VDD_CORE
> :
> :
> Why am not able to read the values of these sensors?
I would suspect bad SDRs.  The entity information is wrong, at least, I
suspect other things are wrong.  The errors are also not valid error
values, so this is very strange.  The "1" in the top 8 bits
>
> 2. Also i get "Error 0x26" while trying to set the threshold values
> for all sensors
I suspect that the sensors say in their SDRs that they don't have
working thresholds, so OpenIPMI won't let you set them.

From what I see, the BMC has some compliance problems.
>
> 3. I get "Error 0x10000c1" while setting events for sensors
>
> How do i interpret these error messages?
That's a good FAQ; I'll add the following to the FAQs.

The top 8 bits of an error are the error type (basically where the error
came from).  The rest of the value is the error itself; make sure to use
the proper IPMI_xxx_ERR_VAL() to extract it.  The error types are:

    * 00 - An OS error or an error from OpenIPMI itself.  These are
      standard errno values and can be decoded with strerror() and friends.
    * 01 - An error from the remote management controller (An IPMI
      error).  You can look these up in the IPMI manual.
    * 02 - RMCP+ error.  These are in the IPMI LAN section of the IPMI
      manual.
    * 03 - SoL (Serial Over LAN) errors.  These are in the SoL section
      of the IPMI manual.

You can convert any of these errors to a human-readable (currently
English only) string using ipmi_err_get_string().  See
include/OpenIPMI/ipmi_err.h for more details on these things.


Thanks,

-Corey
>
>
> Thank you,
> Arun
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> ------------------------------------------------------------------------
>
> _______________________________________________
> Openipmi-developer mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openipmi-developer
>


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Openipmi-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openipmi-developer

Reply via email to