Matej,

My understanding is that IPMI Direct plug-in sends Get Device Id only to  
Boards (FRU #0) but not to subsidiary FRUs (even if they are intelligent).

        Anton Pak

On Wed, 17 Aug 2011 15:26:50 +0400, Matej Kenda <[email protected]> wrote:

> 2011/8/16 Anton Pak <[email protected]>:
>> Hello Matej,
>>
>> Seems device_id field is not mapped at all.
>> Other fields from Get Device Id response are mapped to  
>> SaHpiResourceInfoT
>> data structure.
>>
>>        Anton Pak
>
> Anton, thank you for you answer.
>
> I read the IPMI spec again and it is really better for us to use
> manufacturer and product id instead of device id.
>
> However I noticed that the fields in the SaHpiResourceInfoT are filled
> only for the MCH (MicroTCA Carrier Hub) and not for other FRUs (all
> fields are 0). This can be observed below:
>
> 1. Partial output from hpitree:
>
> Entity Path: {ADVANCEDTCA_CHASSIS,1}{SHELF_MANAGER,0}{SWITCH_BLADE,0}
>
>       EntryId: 55
>       ResourceId: 55
>       Resource Information:
>         Resource Revision: 2
>         Device Support: 3e
>         Manufacturer ID: Gesellschaft f<FC>r Netzwerk- und
> Automatisierungs-Technologie GmbH
>         Product ID: 2819
>         Firmware Major Revision: 2
>         Firmware Minor Revision: 10
>       Entity Path:  
> {ADVANCEDTCA_CHASSIS,1}{SHELF_MANAGER,0}{SWITCH_BLADE,0}
> ....
>
> Entity Path: {ADVANCEDTCA_CHASSIS,1}{SUBBOARD_CARRIER_BLADE,1}{AMC,1}
>
>       EntryId: 58
>       ResourceId: 58
>       Resource Information: None
>       Entity Path:  
> {ADVANCEDTCA_CHASSIS,1}{SUBBOARD_CARRIER_BLADE,1}{AMC,1}
>       Capabilities:
>         CONTROL | FRU | INVENTORY_DATA | RDR | RESET | RESOURCE | SENSOR
>       HotSwap Capabilities: None
>       Resource Severity: OK
>       ResourceFailed: FALSE
>       ResourceTag:
>         Data Type: TEXT
>         Language: ENGLISH
>         Data Length: 16
>         Data: A1:AM4020
>
> ...
>
> 2. Output from my test utility.
>
> Entity:  
> {SWITCH_BLADE(65543)/0}{SHELF_MANAGER(65554)/0}{ADVANCEDTCA_CHASSIS(65539)/1}
> ResourceInfo: rev: 2 dev sup: 62 man-id: 0x6c78 prod-id: 0xb03 fw-rev:
> 2.a aux-rev: 0 guid: 00000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00
> Entity:  
> {AMC(65561)/1}{SUBBOARD_CARRIER_BLADE(65556)/1}{ADVANCEDTCA_CHASSIS(65539)/1}
> ResourceInfo: rev: 0 dev sup: 0 man-id: 0x0 prod-id: 0x0 fw-rev: 0.0
> aux-rev: 0 guid: 00000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00
>
> 3. Output from ipmitool
>
> # ipmitool -I lan -H 10.0.3.105 -P "nat" -T 0x82 -t 0x72 -b 7 mc info
> Device ID                 : 16
> Device Revision           : 0
> Firmware Revision         : 5.24
> IPMI Version              : 1.5
> Manufacturer ID           : 15000
> Manufacturer Name         : Kontron
> Product ID                : 45824 (0xb300)
> Product Name              : Unknown (0xB300)
> Device Available          : yes
> Provides Device SDRs      : yes
> Additional Device Support :
>     Sensor Device
>     FRU Inventory Device
>     IPMB Event Receiver
>     IPMB Event Generator
>     Chassis Device
> Aux Firmware Rev Info     :
>     0x16
>     0x01
>     0x00
>     0x00
>
> I run OpenHPI 2.14.0 on Ubuntu Lucid (32-bit).
> Hardware: Schroff MicroTCA crate with NAT MCH.
>
> Am I doing something wrong?
>
> Regards,
>
> Matej
>
>>
>> On Tue, 16 Aug 2011 16:15:57 +0400, Matej Kenda <[email protected]>  
>> wrote:
>>
>>> Dear all,
>>>
>>> I hope that I am addressing my question to the correct mailing list,
>>> because I didn't see any mailing list for user-type questions.
>>>
>>> Our team is working on a software application that uses AMC boards in
>>> MicroTCA crate. Enumeration and inventory of the hardware is done with
>>> OpenHPI (openipmi-direct plugin).
>>>
>>> Hardware's firmware provides type information of the boards through
>>> IPMI command eIpmiCmdGetDeviceId.
>>>
>>> I was searching through the source code of OpenHPI to find out whether
>>> the fields from device ID (especially the first field: device_id) are
>>> accessible through OpenHPI in any way.
>>>
>>> It looks like the ID is queried in cIpmiMcThread::Discover, but not
>>> exported through any API.

------------------------------------------------------------------------------
Get a FREE DOWNLOAD! and learn more about uberSVN rich system, 
user administration capabilities and model configuration. Take 
the hassle out of deploying and managing Subversion and the 
tools developers use with it. http://p.sf.net/sfu/wandisco-d2d-2
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to