Perc H320 on OMSA 7.4.1

Hello

I have a Poweredge T320 with Perch H320

I'm assuming that was a typo and you meant H310.

RHEL7.1 and OMSA 7.4.1, but I am unable to manage my storage card.

The storage module is installed by default. It used to be an optional install that was not enabled by default, but that was a long time ago. If you did a default installation then it should be installed. I'm not sure it is possible to not install it anymore. I haven't performed a custom OMSA install in a long time.

Have you restarted since installing OMSA? OMSA will function without restarting, but you will usually encounter odd issues like what you are experiencing if you don't restart.

Stop and start the OMSA services and check to see if any of them are failing to start: srvadmin-services.sh start

Thanks

I'm assuming that was a typo and you meant H310.

Of course! ;)

Have you restarted since installing OMSA? OMSA will function without restarting, but you will usually encounter odd issues like what you are experiencing if you don't restart. Stop and start the OMSA services and check to see if any of them are failing to start: srvadmin-services.sh start

I did restarted my system several times since installation, but Storage section keep telling me "No storage controller.."

Start/stop OMSA services performed well without any error.

I tried to reinstall OMSA packages via ./setup.sh, and i saw that libsmbios = 0:2.2.27-4.3.3.el7 is missing: could it be the reason I can't see my PERC controller?

EDIT:

I performed the command #yum list libsmbios* and this is the result:
libsmbios.x86_64                2.2.27-4.3.3.el7                @dell-omsa-indep
So, libsmbios is actually installed on my system

Alert logs section display error code 2314 every time the server is restarted:

The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible.

Start/stop OMSA services performed well without any error. I tried to reinstall OMSA packages via ./setup.sh, and i saw that libsmbios = 0:2.2.27-4.3.3.el7 is missing: could it be the reason I can't see my PERC controller? EDIT: I performed the command #yum list libsmbios* and this is the result: libsmbios.x86_64                2.2.27-4.3.3.el7                @dell-omsa-indep So, libsmbios is actually installed on my system

I think this may be related to a known issue mentioned in the 7.4.1 release notes.

Conflicting version requirements for libsmbios library Server Administrator is dependent on libsmbios. On Linux OS variants, if there is a mismatch in the version requirement of libsmbios, installing Server Administrator results in warnings. It is recommended to uninstall libsmbios versions (and the dependent software) before installing Server Administrator.

I would try uninstalling and reinstalling again and make sure libsmbios is uninstalled during the OMSA uninstall. Also, I'm not sure how you are installing, but you should try installing OMSA through another method.

Thanks

Thank'you for your support.

I tried to uninstall and then reinstall the whole OMSA package.

I removed libsmbios prior to reinstall, but now I'm getting this error while trying to install the "Remote enablement interface", the only one module missing:

 libcmpiCppImpl.so.0()(64bit) necessario a srvadmin-itunnelprovider-7.4.1-4.7.1.el7.x86_64
        libcmpiCppImpl0 >= 2.0.0 necessario a srvadmin-itunnelprovider-7.4.1-4.7.1.el7.x86_64
OMSA is now running as before, with the 2314 error on system Log:

The initialization sequence of SAS components failed during system startup. SAS management and monitoring is not possible.

Are you using our repository to do the update or are you downloading it? I suggest using our repository. It should install all necessary files:

http://linux.dell.com/repo/hardware/latest/

I'm using the downloaded package OM-SrvAdmin-Dell-Web-LX-7.4.1-1341.RHEL7.x86_64_A00.tar.gz

I tried with yum command "yum install srvadmin-all, but it was unable to find the package.

I tried with yum command "yum install srvadmin-all, but it was unable to find the package.

Did you follow the instructions on the page I linked? You can't simply run a yum install. You must add our repository to yum. The default repository locations would not likely be able to locate the OMSA install.

Thanks

Did you follow the instructions on the page I linked? You can't simply run a yum install. You must add our repository to yum. The default repository locations would not likely be able to locate the OMSA install.

Of course I did!

But I also read the OMSA 7.4.1 release notes, and this warning:

NOTE: If you are using Dell’s 11 th generation or 12 th generation of PowerEdge servers running the Red Hat Enterprise Linux 7 operating system and want to install Dell OpenManage Server Administrator 7.4.1. Go to dell.com/support/home and download the OM-SrvAdmin-Dell-Web-LX-7.4.1-1341.RHEL7.x86_64_A00.tar.gz web pack.

I've also upgraded PERC H310 at the latest release available, but still no controller found...

EDIT:

My problem seems related to RHEL upgrade from 7 to 7.1: I've found another user who experienced the similar problem:

http://lists.us.dell.com/pipermail/linux-poweredge/2015-March/049670.html

My problem seems related to RHEL upgrade from 7 to 7.1: I've found another user who experienced the similar problem: lists.us.dell.com/.../049670.html

I have also heard that OMSA is not fully functional with RHEL 7.1, but I have not seen any internal testing information about it. I talked with someone about it yesterday. If I receive confirmation of what we talked about then I will post it here. At this time it appears we do not have a version of OMSA that will work with 7.1.

Thanks

I have also heard that OMSA is not fully functional with RHEL 7.1, but I have not seen any internal testing information about it. I talked with someone about it yesterday.

It is also reported in CentOS 7.1 release notes under Known Issues section:

"If you are using Dell OpenManage v7.4.1, omreport storage vdisk and some other subcommands may not show the requested information. This appears to be a problem with RHEL 7.1 as well."

Uninstalling OMSA 7.4.1 and then installing OMSA 7.0 did the trick!