[EMAIL PROTECTED] wrote: > My mistake was that I hadn't created a new domain yet. I initiated the > same way I did in my OpenIPMI program (smi 0). Here is the output: > > >> sensor info 'domain1(7.1).SMI Timeout0' >> > Sensor > Name: domain1(7.1).SMI Timeout0 > LUN: 0 > Number: 133 > Event Reading Type: 3 > Event Reading Type Name: discrete_state > Type: 243 > Type Name: invalid > Event Support: entire sensor > Init Scanning: true > Init Events: true > Init Thresholds: false > Init Hysteresis: false > Init Type: true > Init Power Up Events: true > Init Power Up Scanning: true > Ignore If No Entity: false > Auto Rearm: true > OEM1: 0 > Id: SMI Timeout0 > Event > Offset: 1 > Name: state asserted > Supports: assertion > Supports: deassertion > From ipmitool:
> SMI Timeout | 85h | ok | 7.1 | State Deasserted ipmitool appears to be doing some interpretation here. From the information above, this only supports the "asserted" bit, but ipmitool is reporting a "deasserted". So it appears that it's saying: "If I only have an asserted bit, if it's not set, it must be deasserted". -corey ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Openipmi-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/openipmi-developer
