hpssacli

[Earl Sullaway]

It appears HP is moving away from hpacucli and going to hpssacli for Gen8 and newer servers, and is changing the location of such files which are listed in the documentation.

I downloaded the hpacucli from http://downloads.linux.hpe.com/SDR/repo/spp/2013.02.0_supspp_rhel6.4_x86_64/ which is slightly different from what the install.vbs script shows.

The latest hpssacli seems to be located http://downloads.linux.hpe.com/SDR/repo/spp/2015.10.0_supspp_rhel7.2_x86_64/hpssacli-2.30-6.0.x86_64.rpm

As I am just starting to use ESOS and am not as familiar with how it all works, should hpssacli be used in place of hpacucli?

Thanks

[Marc Smith]

Hi Earl,

Yes, its likely hpssacli would work fine in place of hpacucli as a CLI
management tool in ESOS, but its unlikely the install scripts would
handle this new package for installing (either with install.vbs or
install.sh). You'd need to extract the archive and then copy (SCP) the
files up to a running ESOS host. If you put the binary utility under
/opt (eg, /opt/sbin/) then it will synchronize to the USB flash drive
and be persistent.

And to clarify the above, ESOS supports those hardware RAID utilities
as CLI tools to be used from the shell in ESOS. Currently, only
MegaRAID (via MegaCLI) adapters are supported using the TUI "dialogs"
for hardware RAID controllers. A plan is on the books for making the
TUI support the other hardware RAID tools as well, but we're not there
yet.

Do you know if hpssacli will support the older HP Smart Array
controllers as well? Is it a direct replacement?


Thanks,

Marc

> --
> You received this message because you are subscribed to the Google Groups
> "esos-users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to esos-users+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Eric Hicks]

I was wondering the same thing.  I know that hpssacli works for cards like the p212, p410, p812 and p822 but I don't know about older cards.  

[Earl Sullaway]

I do not know if hpssacli will support the older HP Smart Array controllers. I have some older servers I was planning on doing some testing and documenting with before I convert my current gen8 boxes. Having a challenge booting the G4s from USB. If I can resolve that, I will test to see if the hpssacli will support them. I don't think I can get much older and still have x86_64 CPUs.

[Marc Smith]

I'd like to integrate this into the master branch... I extracted the
RPM and it appears these two binaries would be useful (paths are
relative):
opt/hp/hpssacli/bld/hpssacli
opt/hp/hpssacli/bld/hpssascripting

Not sure about the "hprmstr". The two wrappers in "usr/sbin/" can
probably be omitted... "/var/run" will already exist on ESOS systems.
I tried using the hpssacli tool on my system and it starts up with
this:
./hpssacli
HP Smart Storage Administrator CLI 2.30.6.0
Detecting Controllers...Done.
Type "help" for a list of supported commands.
Type "exit" to close the console.

Although it appears to hang after that. Maybe because I don't have any
HP controllers in system. Can someone try this tool with ESOS and make
sure it runs properly and if so I'll include this in the installer
scripts.


--Marc

On Wed, Jan 13, 2016 at 12:26 PM, Earl Sullaway <esul...@gmail.com> wrote:
> I do not know if hpssacli will support the older HP Smart Array controllers. I have some older servers I was planning on doing some testing and documenting with before I convert my current gen8 boxes. Having a challenge booting the G4s from USB. If I can resolve that, I will test to see if the hpssacli will support them. I don't think I can get much older and still have x86_64 CPUs.
>

[Earl Sullaway]

I have copied the contents of /usr/sbin to /usr/sbin on the esos test system and the contents of /opt/hp/... to /opt/hp/... on the esos test system.

I was able to query the array after launching the command line utility.  The query function appears to work

It appears to be the same as the hpacucli as far as information is concerned.  I have not yet started to configure the array yet, that may be in a few days.

It does not hang and the system continues to run, but I have not used it to change the array yet.

-Earl

[Earl Sullaway]

I have modified the existing array, and created another array.  All appears to function correctly.  After restart, the items in /usr/sbin are now missing.  I do not believe I know the process to make the items persistent.

Is there anything else needed to test with the tool that you want done?

[Marc Smith]

Hi Earl,

You'll want to copy just this one file: opt/hp/hpssacli/bld/hpssacli

To this directory: /opt/sbin/

Then run a 'conf_sync.sh' and this will "save" the utility so it
persists across reboots.

I've updated the installer scripts in the master branch for this new
tool. I'm leaving the option to install either (or both) for now, but
perhaps some day we will remove hpacucli. I'm going to test these
changes and then will push them up for a new build. I will also check
the issue with install.vbs and hpacucli.


--Marc

[Earl Sullaway]

I tried the master branch as it was supposed to include the hpssacli.  Creating the boot usb seemed to go well.

Starting the server, not so well for the master branch.  Ethernet ports come up as enp3s0f0, enp3s0f1, eno1, eno2, eno3, eno4.  I was expecting eth0,1,2,3,4,5.

Is this the expected result?

Also the first port, enp3s0f0 (eth0 on the 1.8 version) would not show a connection.  The 1.8 version would show a connection.

Is there any more information I can provide you?

[Marc Smith]

Hi Earl,

The "master" branch is different and newer then "0.1.x" (eg, where the
0.1.8 version comes from). In the master branch, we now use udev
(eudev) instead of mdev, so the device naming is a bit different. The
Ethernet interface names you see now are correct. You will likely need
to re-configure your network interfaces, or if you're comfortable at
the command line, edit '/etc/network.conf' and replace 'eth0' with
'enp3s0f0' as you described. Then restart the network in the TUI or
'/etc/rc.d/rc.network stop && /etc/rc.d/rc.network start' from the
shell.

Let us know if you have any more questions, we're happy to help.


--Marc