Hi Pierre,
  Thanks a lot for the clue. Yes, I am using ipmidirect plugin.
   
  How does the ipmi plugin work? Is it like ipmidirect? Or does it take 
something extra?
   
  Regards,
  Pradip

Pierre Sangouard <[EMAIL PROTECTED]> wrote:
        v\:* {behavior:url(#default#VML);}  o\:* {behavior:url(#default#VML);}  
w\:* {behavior:url(#default#VML);}  .shape {behavior:url(#default#VML);}        
st1\:*{behavior:url(#default#ieooui) }                It really depends on 
which plugin you are using: ipmi plugin implements the mapping specification 
but ipmidirect does not.
   
  Pierre
   
        
---------------------------------
  
  From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pradip Biswas
Sent: Thursday, July 31, 2008 10:29
To: openhpi devel
Subject: Re: [Openhpi-devel] System Chassis Resource representation in RPT

   
    Hi Anton,

    Thanks a lot for your input but this is what we have been using from the 
beginning.

     

    So there was no change in OpenHPI behavior, i.e, it still does not give you 
the Shelf Resource entry in RPT.

     

    Any comments on whether OpenHPI implements the mapping spec section 4.1 
correctly?

     

    Regards,

    Pradip

Anton Pak <[EMAIL PROTECTED]> wrote:

    Hellop Pradip.

You can set

entity_root = "{ADVANCEDTCA_CHASSIS,1}"

in handler stanza in openhpi.conf.

Anton Pak

On Tue, 29 Jul 2008 18:18:11 +0400, Pradip Biswas 

wrote:

> Hi,
> We came across the following RPT related issue with the OpenHPI 
> implementation while we were testing it with our HPI Tester for the ATCA 
> mapping conformance:
> OpenHPI does not seem to represent the ATCA Shelf in the RPT. Which 
> means, if you keep doing saHpiRptEntryGet(), you will never get an 
> RPTEntryT with the entity path as {SAHPI_ENT_ADVANCEDTCA_CHASSIS, 
> }, {SAHPI_ENT_ROOT, 0}.
> As I understand, the Shelf Resource is mandatory as per the mapping 
> spec so every HPI Implementation adhering to the mapping spec must have 
> a Shelf Resource (Req 4.1.1.1).
> For example, how would you get the Chassis Manufacturer Id or Chassis 
> Product ID? How does the HPI user access the Chassis Inventory (Section 
> 4.1.2 of the mapping spec)? How does the OpenHPI implementation conform 
> to Section 4.1.1 of the mapping spec for that matter?
>
> Regards,
> Pradip
> ======================
> Pradip Biswas
> Senior Project Manager
> Polaris Networks
> www.polarisnetworks.net
>
>



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
  




-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel



-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel

Reply via email to