Hi forum,

Following up on the thread started by other folks, we've managed to get hpasm somewhat running on x86_64 systems.
Apparently (and not very suprisingly), the x86_64 rpms are basically still 32-bit versions, accept for hpasmlited (the IPMI based hpasm), which is 64bit. We will therefore be using IPMI to read out the sensors, instead of the regular hpasm (not that we have much of a choice...).
The following has been tested on a shiny new DL380 G5, running Debian 4.0 Etch RC1.

Part 1: getting to run IPMI-enabled hpasm

Anyway, I started out by downloading the HPasm-rpm2deb script, and changing the arch from i386 to x86_64. Again, make sure the necessary dependencies (alien, wget and fakeroot) are installed before firing up the script:
Now, before running hpasm configure, head towards your /etc/init.d directory, and create a symlink:
The problem is that the startup scripts of hpasm look for /etc/init.d/ipmi, which obviously doesn't exist. You may also want to remove/comment the annoying . /etc/init.d/functions line in the hpasm startup script, as it is quite unnecessary.

Next up (and still before running the configure script), load in all the ipmi modules:
When that's done, run hpasm configure and configure like you normally would.
After configuring, the hpasmlited should be running:
If it's not running, check the syslog to see the problem. If there are messages saying /dev/ipmi0 can't be found, you haven't modprobed the necessary modules (or your controller is not detected by the kernel drivers).

To read out the stats, you can use ipmitool. It's one command away:
You can now issue commands like:
to read out various sensors.

Part 2: getting to run storage agents

As said before, the storage agents are still 32bit binaries, which means we can't use them as-is on our 64bit Debian. Luckily, Debian has foreseen this very problem with a set of 32bit emulation libraries for 64bit systems. Installing these will enable you to run 32bit applications on 64bit environments (provided they don't have funny dependencies).
To get the cmastor bit running, we installed these:
Actually, you only need to punch in the first two, the others are automagically selected as deps.
Once that's done, do a restart of hpasm, and you'll notice a whole lot more processes are running:

EDIT: Part 3: automatic startup

For automatic startup, I added the load of the ipmi modules to /etc/modules, as they are not loaded automatically. Secondly, I issues the command below to get hpasm in the startup:
I ran this particular command to ensure that hpasm gets started after snmp (though I'm not sure if snmp is really used with hpasmlited), and stopped before snmp stops. Not sure if this is necessary, but it's a cleaner way.

Part 4: unresolved issues (edit: was part 3)

Okay, there are still a few 'bugs': first of is the fact that we're not using the fully fledged hpasm. This means we're missing logging to the HP Event Log (which is a pain, I admit). Instead, hpasmlited seems to be logging things to the syslog.
Secondly, although hpasmcli seems to work, it's still a bit unstable on emulation and regularly segfaults. Note that ipmitool can be used as an alternative to this though.

As a conclusion, this small howto is far from finished, and was only tested on one machine. It will most likely need to be generalized for the broader audience. Also, I haven't tried to run hpsmh or the ilo agents just yet (this will probably be done in the next few days). Anyway, any type of comment or problems are welcome in this thread.