As I recall the event is generated when reading crosses threshold.
In your case you just have static constant reading, correct?
Anton Pak
On Fri, 11 Feb 2011 01:49:25 +0300, Preeti Sharma
<[email protected]> wrote:
> Hi,
>
> I am trying to generate event for the "RPT Entry Id-4" and "Sensor RDR
> Resource Id-131073". The print of this RPT is given below:
>
> RPTEntry[4] tag: HS DASD 1 2
>
> Entity Path: {SYSTEM_CHASSIS,9}{DISK_DRIVE,2}
>
> RDR[131073]: Sensor[ 1] HS DASD temperature sensor 1 =
> 125.000 Degrees F
>
> Current Sensor State = UPPER_MINOR
>
> Ranges::
>
> Nominal of Range: 100.000 Degrees F
>
> Max of Range: 125.000 Degrees F
>
> Min of Range: 40.000 Degrees F
>
> Normal Max of Range: 110.000 Degrees F
>
> Normal Min of Range: 90.000 Degrees F
>
> Thresholds::
>
> Low Critical Threshold: 40.000 Degrees F
>
> Low Major Threshold: 50.000 Degrees F
>
> Low Minor Threshold: 60.000 Degrees F
>
> Up Critical Threshold: 125.000 Degrees F
>
> Up Major Threshold: 120.000 Degrees F
>
> Up Minor Threshold: 110.000 Degrees F
>
> Pos Threshold Hysteresis: 2.000 Degrees F
>
> Neg Threshold Hysteresis: 2.000 Degrees F
>
>
>
> RDR[131074]: Sensor[ 2] HS DASD temperature sensor 2 = 35.000
> Degrees F
>
> Current Sensor State = UPPER_MINOR
>
> Ranges::
>
> Nominal of Range: 100.000 Degrees F
>
> Max of Range: 125.000 Degrees F
>
> Min of Range: 40.000 Degrees F
>
> Normal Max of Range: 110.000 Degrees F
>
> Normal Min of Range: 90.000 Degrees F
>
> ThresholdsGet ret=INVALID_CMD
>
> RDR[ 65537]: CTRL_RDR Digital Control
>
> RDR[ 65538]: CTRL_RDR Discrete Control
>
> RDR[ 65539]: CTRL_RDR Analog Control
>
> RDR[ 65540]: CTRL_RDR Stream Control
>
> RDR[ 65541]: CTRL_RDR Text Control
>
> RDR[ 65542]: CTRL_RDR Oem Control
>
> RDR[327681]: ANNUNCIATOR_RDR Annunciator 2
>
> RDR[262144]: WATCHDOG_RDR Watchdog 2
>
> RDR[196609]: INVENTORY_RDR Simulator HS DASD Inv 1
>
>
>
> I did below changes in client/hpievent.c
>
> 198,199c198,201
>
> < rdr.RdrType = SAHPI_NO_RECORD;
>
> < rptentry.ResourceId = 0;
>
> ---
>
>> rdr.RdrType = SAHPI_SENSOR_RDR;
>
>> rdr.RecordId = 131073;
>
>> rptentry.ResourceId = 4;
>
>> rptentry.EntryId = 4;
>
>
>
> As well changed simulation.data diff is given below:
>
> 1181c1181
>
> < value.SensorFloat64=35.000000
>
> ---
>
>> value.SensorFloat64=125.000000
>
>
>
> Since temperature 125.000000 is in critical threshold of RDR[131073]
> this should have generated an event. Please let me know what change I am
> missing as I am not getting any event when I run the client.
>
>
>
> Regards,
>
> Preeti
>
>
>
> -----Original Message-----
> From: Preeti Sharma
> Sent: Thursday, February 10, 2011 4:55 PM
> To: [email protected]
> Subject: What changes are required in simulation.data file to see an
> event?
>
>
>
> Hi,
>
> I do not have HPI Chassis yet and want to see an event when I run client
> (client/hpievent). For this, do I need a change
> /etc/openhpi/simulation.data (sample file provided with openHpi). If any
> of you already working with real chassis, could you please provide me a
> simulation.data file which has an event entry.
>
>
>
> Or if I am wrong above what is the way to see an event when we run
> client/hpievent.
>
>
>
> Regards,
>
> Preeti
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
