Using ipmidirect...
- leo
On 11/5/07, Cress, Andrew R <[EMAIL PROTECTED]> wrote:
>
> Leo,
>
> I think David was probably more interested in which ipmi plugin you were
> using (ipmi or ipmidirect).
>
> Andy
>
> ------------------------------
> *From:* [EMAIL PROTECTED] [mailto:
> [EMAIL PROTECTED] *On Behalf Of *Leon Jacob
> *Sent:* Monday, November 05, 2007 2:23 AM
> *To:* [email protected]
> *Subject:* Re: [Openhpi-devel] Subagent Implementation
>
> Sorry for the delay, We are developing an implementation of the IPMI based
> on IPMI v1.5 rev 1.1 (Proofe of concept). And are also trying to export
> the SDR tables (Full Record, entity associaton record, device locator
> records, MC COnfirmation record, BMC Channel Info.
>
> All these are records maintained by variour other processes in the system,
> and like the SDR Full record table they need to be fetched before responding
> to the snmp user.
>
> - Leo
>
>
> On 10/30/07, David Judkovics <[EMAIL PROTECTED]> wrote:
> >
> >
> > Leon,
> >
> > I developed the MIB along with Konrad a couple years ago and need a
> > little help remembering before I can try to help. What IPMI interface
> > are you referring to?
> >
> > Cheers
> > David Judkovics
> >
> >
> > On Tue, 2007-10-30 at 19:57 +0530, Leon Jacob wrote:
> > > I'm trying to implement the sensor table, from the IPMI document,
> > > What mib2c option should i be using?
> > >
> > > mib2c.array-user.conf, [ i'm confused as hpi-subagent uses this but
> > > this data should be fetched using the ipmi inteface from a
> > > elsewhere.]
> > > mib2c.iterate.conf [ I thought this should be used. ]
> > > or mib2c.mfd.conf [ looks like safe bet.]
> > >
> > > - leo
> > >
> > > sensorTable OBJECT-TYPE
> > > SYNTAX SEQUENCE OF SensorEntry
> > > MAX-ACCESS not-accessible
> > > STATUS current
> > > DESCRIPTION
> > > "A table defining the staic sensor data found in the
> > > Sensor Resource Data Repository."
> > > ::= { SensorManagement 1 }
> > >
> > > sensorEntry OBJECT-TYPE
> > > SYNTAX SensorEntry
> > > MAX-ACCESS not-accessible
> > > STATUS current
> > > DESCRIPTION
> > > ""
> > > INDEX { sensorIndex }
> > > ::= { sensorTable 1 }
> > >
> > > -- should this have fruid to identify which FRU this sensor belongs
> > > to??
> > > SensorEntry ::= SEQUENCE {
> > > -- Sensor Header Begin
> > > sensorIndex INTEGER, -- 01
> > > (2 bytes)
> > > sensorSdrVersion Integer32, -- 02
> > > (1Byte )
> > > sensorRecordType Integer32, -- 03 (1
> > > Byte)
> > > --sensorRecordLen Integet32, -- (1
> > > Byte)
> > > -- Sensor Header End
> > >
> > > -- Record "KEY" Bytes Begin
> > > sensorOwnerId Integer32, -- 04 (1
> > > Byte)
> > > sensorOwnerLun Integer32, -- 05
> > > (1Byte)
> > > sensorNumber Integer32, -- 06 (1
> > > Byte)
> > > -- Record "KEY" Bytes End
> > >
> > > -- Record Body Begin
> > > sensorEntityId Integer32, -- 07 (1
> > > Byte)
> > > sensorEntityInstance Integer32, -- 08 (1
> > > Byte)
> > > sensorInitialization Integer32, -- 09 (1
> > > Byte)
> > > sensorCapabilities Integer32, -- 10 (1
> > > Byte)
> > > sensorType INTEGER, -- 11(1
> > > Byte)
> > > sensorEvent INTEGER, -- 12
> > > (1 Byte) Event/Reading Type Code.
> > > sensorAssertionEventMask Integer32, -- 13 (2
> > > Bytes)
> > > sensorDeassertionEventMask Integer32, -- 14 (2
> > > Bytes)
> > > sensorDiscreteReadMask Integer32,
> > > -- 15 (2 Bytes)
> > > sensorUnits Integer32, -- 16 (1
> > > Byte)
> > > sensorBaseUnit Integer32, -- 17 (1
> > > Byte)
> > > sensorModifierUnit Integer32, -- 18 (1
> > > Byte)
> > > sensorLinearization Integer32, -- 19(1
> > > Byte)
> > > sensorM Integer32, -- 20(1
> > > Byte)
> > > sensorMTolerance Integer32, -- 21(1
> > > Byte)
> > > sensorB Integer32, -- 22(1
> > > Byte)
> > > sensorBAccuracy Integer32, -- 23(1
> > > Byte)
> > > sensorAccuracyExp Integer32, -- 24(1
> > > Byte)
> > > sensorRExp Integer32, -- 25(1
> > > Byte)
> > > sensorBExp Integer32, -- 26(1
> > > Byte)
> > > sensorCharacteristicFlags Integer32, -- 27(1
> > > Byte)
> > > sensorNominalReading Integer32, -- 28(1
> > > Byte)
> > > sensorNormalMaximum Integer32, -- 29(1
> > > Byte)
> > > sensorNormalMinimum Integer32, -- 30(1
> > > Byte)
> > > sensorMaximumReading Integer32, -- 31(1
> > > Byte)
> > > sensorMinimumReading Integer32, -- 32(1
> > > Byte)
> > > sensorUpperNonRecoverableThreshold Integer32, -- 33(1
> > > Byte)
> > > sensorUpperCriticalThreshold Integer32, -- 34(1
> > > Byte)
> > > sensorUpperNonCriticalThreshold Integer32, -- 35(1
> > > Byte)
> > > sensorLowerNonRecoverableThreshold Integer32, -- 36(1
> > > Byte)
> > > sensorLowerCriticalThreshold Integer32, -- 37(1
> > > Byte)
> > > sensorLowerNonCriticalThreshold Integer32, -- 38(1
> > > Byte)
> > > sensorPositiveGoingThresholdHysteresis Integer32, -- 39(1
> > > Byte)
> > > sensorNegativeGoingThresholdHysteresis Integer32, -- 40(1
> > > Byte)
> > > -- ignore the two reserved bytes for now
> > > sensorOem Integer32, -- 41(1
> > > Byte)
> > > sensorIdStringType Integer32, -- 42
> > > Type/Len (1Byte)
> > > sensorIdString DisplayString -- 43
> > > (max 16 Bytes)
> > > }
> > >
> > >
> > -------------------------------------------------------------------------
> > > 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/
> > > _______________________________________________ Openhpi-devel mailing
> > list [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
> >
> >
> >
> > -------------------------------------------------------------------------
> > 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/
> > _______________________________________________
> > Openhpi-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
> >
>
>
> -------------------------------------------------------------------------
> 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/
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>
>
-------------------------------------------------------------------------
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/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
