Hi
I'm not sure, if you are using the bbs installation or an openhpi daemon. If
you are using an openhpi installation, please see the mail from Michael.
For the bbshpib clients on a blade:
- Please make sure to install the correct rpm packets for your blade
(bbs..hpib..rpm)
- For the bbshpib clients you have to change
/opt/bbs/hpib/etc/bbsmultishelf.conf . (or similiar path - I don't remind it
exactly)
In the file you will find some entries like [xyzshelf]. Please configure in
this part the correct IP-address (in common: something like
192.168.<ShelfNumber>.8 for the left shmgr)
And I don't know how far the redundancy concept is implemented . The
IP-address from above is the one of the first shmmgr. You can also configure
the second shmmgr in the configuration file by generating a new entry after
the entry from above like:
[stbShelf]
... = 192.168.<ShelfNumber>.9
(Btw. check the IP-addresses by calling ping on your blade)
Afterwards you can check the configuration by calling the client "hpilist -d
1" (the first shelf Manager is active, "hpilist -d 2" the second one is
active) - one of the commands should show you the whole resources list.
Please don't blame me, if the things from above doesn't fit exactly, but I
don't have any notes or a machine to verify it and it is some time ago since
I work with a C2000.
If you don't replaced the hpi-b daemon on the M105 by an openhpid, you will
need the bbsmultishelf library to communicate with him.
Hope it works
Regards
Lars
On Monday, 7. December 2009 22:44, Thompson, Michael wrote:
> I just did this.
>
> On my Linux system I set my local environment to:
>
> export OPENHPI_UID_MAP=/tmp/uid_map
> export OPENHPI_CONF=/etc/openhpi/openhpi.conf
> export OPENHPI_DAEMON_MODE=NO
> export OPENHPI_DAEMON_HOST=10.179.0.141
> export OPENHPI_DEBUG=NO
>
> And the OpenHPI clients work.
>
> -----Original Message-----
> From: Amir Parniani [mailto:[email protected]]
> Sent: Monday, December 07, 2009 4:36 PM
> To: Lars Wetzel; Anton Pak; [email protected]
> Subject: Re: [Openhpi-devel] Accessing HPI Daemon on ShMC remotely.
>
>
> Hi lars, Anton, thanks for your responses. For my project I will be
> using HPI-Daemon running on the M105 communicating over RMCP. I'll port
> relevant hpi client libraries but I am not yet sure how to configuration
> the IP to communicate with the HPI daemon on the ShMM.
>
> Thanks,
> Amir
>
> -----Original Message-----
> From: Lars Wetzel [mailto:[email protected]]
> Sent: Thursday, December 03, 2009 2:57 AM
> To: [email protected]
> Cc: Anton Pak; Parniani, Amir (CAR:SI30)
> Subject: Re: [Openhpi-devel] Accessing HPI Daemon on ShMC remotely.
>
> Hi Amir,
>
> only some additional information to the mail from Anton.
> Do you use the openhpi daemon or the M105 HPI-Daemon?
>
> In the Centellis 2000 you have a HPI-Daemon running on the M105
> (including the ShelfManager). Now it depends on how you will use it.
> What I mean, do you want to communicate over RMCP/another HPI-B daemon
> or over the bbs-multishelf library?
>
> In the case you are using the bbs-multishelf library you have to
> configure the bbs-multishelf.conf properly (you need the bbs-hpib and
> bbs-hpib-client packets on your blade). Please ask for this purpose also
> the Emerson support.
>
> In any case, you will find some example code looking inside the client
> directories of your bbs/openhpib installation or the hpitest suite on
> www.saforum.org. The client code should work independent of the
> architecture which is chosen (it's only a question of compiling and
> linking).
>
> Regards
> Lars
>
> On Wednesday, 2. December 2009 17:52, Anton Pak wrote:
> > Hello!
> >
> > You can use any HPI API calls.
> > libopenhpi.so implements this interface.
> > See www.saforum.org for the specification of the API.
> >
> > Remote access is a configuration topic.
> > One can define HPI domain with IP address:port in openhpiclient.conf
> > file and then the library will work with remote HPI daemon.
> >
> > Anton Pak
> >
> > On Wed, 02 Dec 2009 19:44:37 +0300, Amir Parniani
> > <[email protected]>
> >
> > wrote:
> > > Hi,
> > >
> > > We are using Centellis 2000 chassis (2-Slot system) where the shelf
> > > manager (ShMC) of the board provides an interface (Hardware Platform
> > >
> > > Interface, HPI) and has HPI daemon running on it to monitor and
> > > control the FRUs on the shelf. I would like to write my own client
> > > code in our system manager, a very thin layer to call HPI
> > > interfaces, to communication between the system manager and the
> > > shelf manager remotely let say from a different blade. I Would like
> > > to know how to communicate to the shelf? And what kind of API's I
> > > can call in my client code, Please le me know if there is any
> > > documentation or examples that I can use.
> > >
> > > Thanks,
> > > AP>
> > >
> > >
> > >---------------------------------------------------------------------
> > >----
> > >----- Join us December 9, 2009 for the Red Hat Virtual Experience, a
> > >
> > >free event focused on virtualization and cloud computing.
> > > Attend in-depth sessions from your desk. Your couch. Anywhere.
> > > http://p.sf.net/sfu/redhat-sfdev2dev
> > > _______________________________________________
> > > Openhpi-devel mailing list
> > > [email protected]
> > > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
> >
> >-----------------------------------------------------------------------
> >----
> >--- Join us December 9, 2009 for the Red Hat Virtual Experience, a
> >free event focused on virtualization and cloud computing.
> > Attend in-depth sessions from your desk. Your couch. Anywhere.
> > http://p.sf.net/sfu/redhat-sfdev2dev
> > _______________________________________________
> > Openhpi-devel mailing list
> > [email protected]
> > https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>
> --
> -------------------------------
> Dipl. Wi.ing.
> Lars Wetzel
> Uttinger Str. 13
> 86938 Schondorf a. Ammersee
>
> Tel.: 0179-2096845
> Mail: [email protected]
>
> USt-IdNr.: DE181396006
>
> ---------------------------------------------------------------------------
>--- Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
>
> ---------------------------------------------------------------------------
>--- Return on Information:
> Google Enterprise Search pays you back
> Get the facts.
> http://p.sf.net/sfu/google-dev2dev
> _______________________________________________
> Openhpi-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/openhpi-devel
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
Openhpi-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/openhpi-devel
