New OMSA install on PE T610 shows no

Hi Jeff,

Based on the issue, most likely Data Manager service is not running successfully on the server. Kindly run the following command to see the Data Manager service status and also observe the /var/log/messages if there are any errors/crashes reported during Server Administrator services start up.


To see the service status:

/etc/init.d/dataeng status

To Start or restart

/etc/init.d/dataeng start/restart



Regards

Chandra

Message: 1
Date: Tue, 10 Nov 2015 10:45:53 -0800
From: Jeff Boyce
Subject: [Linux-PowerEdge] Hard Drive firmware update issue with DSU
To: "[email protected]"
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed

Greetings -

Well it looks like a recent drive replacement has created a domino effect for me with a firmware update and now an OMSA installation issue. I will hold the OMSA issue for another email, as I am still have a little research to try to identify and resolve the issue.

The basics of the firmware update issue that I have is that the DSU inventory identifies that I have drives (same manufacturer and model) showing different firmware, but that running the update does not update the firmware on the drive that is not shown as the current version.
Details of the dsu output are below. My system is a PE T610 and I have
4 drives installed configured in a RAID 5 (3 active drives and 1 hot
spare) on a PERC H700 Controller. The model of the drive replaced (all drives are the same model) is a Seagate SAS 300GB, ST3300657SS. The Seagate support site identifies the current firmware for the drive as 000B, released on 8/13/2012. The Dell support site identifies the current firmware for the drive as ES68, released on 6/10/2015. The new drive I installed shows a firmware version of 000B, while the firmware of the three original drives is shown as ES68. This is shown in the dsu --inventory results below (all other firmware on the box is up-to-date and is not shown). However when the dsu update is run it only identifies the first drive in the backplane (which has current firmware) and does not make any reference to the other three drives, and in particular the drive that has firmware 000B. So my question becomes, how do I updated the firmware in one specific drive? Is this a bug in the implementation of the dsu utility?

Please cc any responses directly to me, as I only receive the daily digest of this mailing list. Thanks.

[root@earth ~]# dsu --inventory
Getting System Inventory...

8. Firmware for - Disk 0 in Backplane 0 of PERC H700 Integrated
Controller 0 ( Version : ES68 )
9. Firmware for - Disk 2 in Backplane 0 of PERC H700 Integrated
Controller 0 ( Version : 000B )

[root@earth ~]# dsu
Getting System Inventory...
Determining Applicable Updates...

|-----------Dell System Updates-----------|
[ ] represents 'not selected'
[*] represents 'selected'
[-] represents 'Component already at repository version (cannot be selected)'
Choose: q - Quit without update, c to Commit, - To Select/Deselect, a - Select All, n - Select None

[-]6 Firmware for - Disk 0 in Backplane 0 of PERC H700 Integrated Controller 0
Current Version : ES68 same as : ES68

Enter your choice : q
[root@earth ~]#


--

Jeff Boyce
Meridian Environmental
www.meridianenv.com



------------------------------

Message: 2
Date: Tue, 10 Nov 2015 14:58:12 -0800
From: Jeff Boyce
Subject: [Linux-PowerEdge] New OMSA install on PE T610 shows no
information
To: "[email protected]"
Message-ID:
Content-Type: text/plain; charset=utf-8; format=flowed

Greetings -

I have had some firmware update issues on my PE T610 that I have discussed in another thread; however during the process of updating the firmware I have also run into an issue with OMSA. I previously had a working version (ver. 7.4) on the server, and I had previously used the Dell firmware tools repository to update the firmware. Since the new Dell System Update (DSU) tool is now the preferred method for updating firmware and OMSA, I did a complete un-installation of the ServerAdmin packages using the steps described below. Before uninstalling I confirmed that the latest OMSA version (ver. 8.2) is compatible with my system from the documentation (https://www.dell.com/support/home/us/en/19/product-support/product/dell-opnmang-sw-v8.2/manuals),
specifically the OpenManage Software Support Matrix document, which lists the PE T610 and RHEL 6.7 as a supported hardware / software combination for OMSA 8.2.

Removed the existing OMSA packages.
# yum remove $(rpm -qa | grep srvadmin)

Since I know from past experience, and as advised by those more knowledgeable than me on this mailing list previously, this alone does not cleanly uninstall everything and the additional three commands were invoked for a completely clean un-installation.

*** Warning to others, be careful using this big hammer. *** # rm -fr /opt/dell/srvadmin/ # rm -fr /usr/libexec/dell_dup/ # rm -fr /usr/share/firmware/dell/

Then I installed the DSU utility to setup the repository files.
# wget -q -O - http://linux.dell.com/repo/hardware/dsu/bootstrap.cgi | bash

Made sure that the DSU repository was the only one enable on my system (after seeing some of the recent discussion on this mailing list). The installed the Dell system update software, and OMSA.
# yum install dell-system-update
# yum install srvadmin-all

I checked to make sure that the services I expected to see were installed and running. They were not running, so I started them via my Webmin interface. When I navigated to OMSA web interface and logged in, I was greeted with no information listed, except for a list of the OMSA software installed. Both the Main Chassis and Storage categories in the listing tree are blank. I know there have been issues in the past with the Storage category being blank, but I don't recall seeing an issue with both the Main Chassis and Storage not having any information. So I am looking to others, or the Dell representatives, for ideas how to address this issue. I would like to have a working OMSA back again.

Note: I am running CentOS 6.7 and I have modified /etc/redhat-release so that it shows Red Hat Enterprise Linux Server release 6.7 (Santiago). This change is all that has been necessary in the past to run OMSA on CentOS.

Please cc me directly with any responses, as I only receive the daily digest of this mailing list. Thanks.

Jeff

--

Jeff Boyce
Meridian Environmental
www.meridianenv.com



------------------------------

Message: 3
Date: Wed, 11 Nov 2015 10:23:41 +0530
From:
Subject: Re: [Linux-PowerEdge] DSU and how it uses yum
To: , ,

Message-ID:


Content-Type: text/plain; charset="us-ascii"

Dell Customer Communication
DSU handles the OMSA update, what Soorej means here is we use the RPMs delivered by the OMSA team as is.
We will work with OMSA team to how best to handle this and get back.

Thanks,
Kalyan.


-----Original Message-----
From: linux-poweredge-bounces-Lists On Behalf Of [email protected]
Sent: Tuesday, November 10, 2015 6:19 PM
To: Ponnandi, Soorej; linux-poweredge-Lists
Subject: Re: [Linux-PowerEdge] DSU and how it uses yum

> ----- Original Message -----
> From: [email protected] [mailto:[email protected]]
> Subject: DSU and how it uses yum


> The OMSA install/upgrade is not currently handled by dsu tool. The
> OMSA rpms are hosted in DSU repository for install/update directly
> using yum command. We have forwarded this issue to the corresponding team and will work with them to improve this.

The dsu utility DOES handle OMSA upgrades:

--------------------------------------------------------------------------------
[root@host ~]# dsu
Getting System Inventory...
Determining Applicable Updates...

|-----------Dell System Updates-----------|
[ ] represents 'not selected'
[*] represents 'selected'
[-] represents 'Component already at repository version (cannot be selected)'
Choose: q - Quit without update, c to Commit, - To Select/Deselect, a - Select All, n - Select None



[-]12 OpenManage Server Administrator
Current Version : 8.2.0 same as : 8.2

Enter your choice: q
[root@host ~]#
--------------------------------------------------------------------------------

>From other posts on this list it seems that when an admin tells dsu to upgrade OMSA it will upgrade the entire system. That needs to be fixed ASAP. I handle OMSA upgrades via yum usually long before I get a chance to run dsu on any particular system so it hasn't caused me a problem. But others have had a much worse experience.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20151111/a0a9f1d5/attachment-0001.html

------------------------------

_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

End of Linux-PowerEdge Digest, Vol 138, Issue 13
************************************************

_______________________________________________
Linux-PowerEdge mailing list
[email protected]
https://lists.us.dell.com/mailman/listinfo/linux-poweredge