gmane.linux.hardware.dell.poweredge

OpenManage 7.0 can't see all storage cards

David B. — 2012-05-25T08:51:42

Hi Dell users,

I've got a bunch of PE servers and I'm looking to upgrade them to
OpenManage 7.0.

All servers are on Debian Squeeze.

For now, this openmanage upgrade seems to be ok.

Yesterday, I found an issue with a R710.

# omreport chassis info
Chassis Information
Index                                    : 0
Chassis Name                             : Main System Chassis
iDRAC6 Version                           : 1.80.00 (Build 17)
Lifecycle Controller Version             : 1.3.0.350
Chassis Model                            : PowerEdge R710
Chassis Lock                             : Present
Chassis Asset Tag                        :
Flash chassis identify LED state         : Off
Flash chassis identify LED timeout value : 300


This server have 2 SCSI cards and 2 RAID cards.
OS is working well and kernel can see all theses cards.

# lspci
03:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS 1078
(rev 04)
06:08.0 SCSI storage controller: LSI Logic / Symbios Logic 53c1030 PCI-X
Fusion-MPT Dual Ultra320 SCSI (rev c1)
07:00.0 RAID bus controller: LSI Logic / Symbios Logic LSI MegaSAS 9260
(rev 05)
09:08.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068 PCI-X
Fusion-MPT SAS (rev 01)

But, OM 7.0 can only see 3 of them.
We've tried two kernels (2.6.35-5-adm64 and 3.2.0-0.bpo.2-amd64).

Yesterday, OM can't see my H800 :
# omreport storage controller
0 : LSI Logic 1020/1030 Ultra320 SCSI Adapter
1 : PERC 6/i Integrated
2 : SAS 5/E Adapter

H800 not in this list.
BUT, OM can see that a battery is charging on controller 2, but this
controller 2 is a SAS 5/E adapter without battery.

We've tried several reboots and OM can see all cards but not in the same
time !

This morning, I've got this :
# omreport storage controller
0 : LSI Logic 1020/1030 Ultra320 SCSI Adapter
1 : PERC 6/i Integrated
2 : H800

SAS 5/E is not there, but H800 is here !

So I reboot this server (again) without changing anything.

And now I get :
# omreport storage controller
0 : LSI Logic 1020/1030 Ultra320 SCSI Adapter
1 : PERC 6/i Integrated
2 : SAS 5/E Adapter

I've lost my H800 again.

I'm confuse. Did someone already see this behaviour ?

Best regards
David.

Strange view on OME via OMSA on CentOS

2012-05-25T01:34:05

Hello experts,

Does anyone know URLs and so on which I can see some problems, troubles and bugs about
OME(OpenManage Essentials) & OMSA on CentOS.
If you know some informations, please let me know about that.

Seiji Watabe
渡部 誠士
Sales Engineer
Dell | Enterprise Solutions Organaization
Ext. 8135567,  Office. +81 3 5442 5567
Fax. +81 44 556 3445
Seiji_Watabe< at >dell.com<mailto:Seiji_Watabe< at >dell.com>

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: PE2950: CentOS 6.2 doesn't reboot

Gianluca Cecchi — 2012-05-24T15:55:05

On Thu, May 24, 2012 at 5:24 PM, Gianluca Cecchi
<gianluca.cecchi< at >gmail.com> wrote:


I found this bug that applies to my setup:

http://bugs.centos.org/view.php?id=5488

I'm going to apply the workaround referred and eventually reproduce
with RH EL 6 too, opening bugzilla for it.

Gianluca

No controllers found. OMSA 6.5. CentOS 6.2. PERC H710. PowerEdgeR620. No support yet?

André Luciano Dias — 2012-05-24T15:39:04

I´m trying to make OMSA command "omreport storage *" work. "omreport
chassis *"  and "omreport system *" are ok.

# omreport storage controller
No controllers found

My system: OMSA 6.5. CentOS 6.2. PERC H710. PowerEdge R620. I did the
installation using yum:

# wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash

# yum install srvadmin-all dell_ft_install

I´m starting to think there is no support for H710 on OMSA 6.5. Am i right?

I found the 7.0 version on Ubuntu repository, but the latest version
on the official repository is 6.5. Any date for 7.0 to be avaiable?

Thanks,

Andre

PE2950: CentOS 6.2 doesn't reboot

Gianluca Cecchi — 2012-05-24T15:24:02

Hello,
installed CentOS 6.2 x86_64 + updates on a PE2950 generation II server

Each time I try to reboot the server, it stops like in this image:
https://docs.google.com/open?id=0BwoPbcrMv8mvVGVVc2tXU2JobEk

How can I debug this problem?
Until today this server had rh el 5.7 x86_64 and didn't show this problem.

fw levels are ok
drac5 fw  1.51
BMC 2.37
bios 2.6.1
perc 5/i  5.2.2-0072

This reboot problem btw prevents me to update bios to latest 2.7.0
through PE2950_BIOS_LX_2.7.0.BIN file.
In fact when I have to reboot the server, it stops and so I'm forced
to power cycle and I get back my 2.6.1 version...

This behaviour is the same with and without the 6.5.0 omsa for rhel6
installed (they seems to work ok, after changing redhat-release file)

Thanks in advance.
Gianluca

PE R310/510 Special NIC Bonding

Martin Seener — 2012-05-24T09:21:25

Hello everyone,

we have some R510 with the Dual-NIC Broadcom onboard and an PCIe Intel 
Single-Port GigE Card separately attached.

We now setup a Linux Bonding (Debian Squeeze latest with ifenslave-2.6) 
using settings below and i want to ask if its okay or not to use one 
Broadcom and the Intel Card in a Bond together or if its better to use 
NICs from the same vendor for that (the 3rd NIC is a normal iface)

We saw issues with SLES11 on R310 while bonding them (mode4 LACP) and 
using an IPSec Tunnel over this with the following error. so i want to ask

2012:05:24-09:42:22 seth kernel: [659323.689392] ppp0 received packet on 
queue 2, but number of RX queues is 1

bonding on that 510 is mode 1 active/backup. - here the config (eth0/1 
is internal broadcom, eth2 intel pcie) - i dont think that this causes 
similar errors because only one card is active and not both the same 
time like on the SLES11 we have a mode=4 bonding.

auto lo
iface lo inet loopback
#
auto bond0
iface bond0 inet static
address 10.1.30.10
netmask 255.255.255.0
gateway 10.1.30.1
bond_mode active-backup
bond_miimon 100
bond_downdelay 200
bond_updelay 200
bond_primary eth0
slaves eth0 eth2
#
auto eth1
iface eth1 inet static
address 172.1.30.1
netmask 255.255.255.0

Q: Success/Caveats running Debian Squeeze/Wheezy on 12th GenPowerEdges?

Stephen Dowdy — 2012-05-23T17:03:47

Has anyone successfully got Debian Squeeze running on a 12th gen
PowerEdge (R[67]20 mainly).  Which squeeze backports kernel works
best (at all?)  Any issues, significant performance/stability
problems?  Does Testing/Wheezy work?

Thanks,
--stephen

RE: R620/12G servers w/CentOS 5.7 and low-latency?

2012-05-23T16:28:33

Matt,
Here is a link to documentation on this topic.  http://en.community.dell.com/techcenter/b/techcenter/archive/2012/05/07/configuring-low-latency-environments-on-dell-poweredge-12th-generation-servers.aspx.  The BIOS team is investigating your report of inconsistent performance, but I have not heard anything back from them.  Hopefully your issue is being addressed by the formal channels.

Wayne Weilnau
Systems Management Technologist
Dell | OpenManage Software Development 

Please consider the environment before printing this email.

Confidentiality Notice | This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, immediately contact the sender by reply e-mail and destroy all copies of the original message.

-----Original Message-----
From: linux-poweredge-bounces-Lists On Behalf Of Matt Garman
Sent: Friday, May 18, 2012 12:50 PM
To: linux-poweredge-Lists
Subject: R620/12G servers w/CentOS 5.7 and low-latency?

Hi,

I was just wondering if anyone else on this list happens to be using
the new 12G servers (R620 in our case) with CentOS 5.7 in an ultra-low
latency environment?  We have configured the standard BIOS settings
appropriately (disable c-cstates/c1e, max performance, etc---a
familiar drill from previous-gen servers).

However, what we are seeing in our simulations and testing is
inconsistent performance results.  Even doing the same exact test, one
right after the other, the results vary substantially (up AND down).
A full-on simulation one day to the next can vary by 50%.

With the previous-gen (11G) servers, I had a similar performance issue
that was ultimately fixed by a BIOS update (but six months after the
11G release).  I'm hoping to not see a repeat of this kind of issue.

I'm working the formal channels with Dell on this, but just thought
I'd throw a feeler out there to see if anyone else is seeing similar
issues.

Thanks!
Matt

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: Dell R410 and CentOS 6.2

Baptiste AGASSE — 2012-05-23T16:03:59

Hi,


We just tested with another switch, but nothing change...

Have a nice day.

Regards.

Baptiste.

Re: R610 PXE RHEL5 install

Govind B. Songara — 2012-05-23T14:12:24

My R610 box having 4* 1GB Broadcom , 2*10GB Intel PCIe card.

I am using PXE kickstart for install,

Is there any option to disable or ban module/driver from loading for these
10GB card.?

I dont know how to do that.. any suggestion ?

Thanks


On Tue, May 22, 2012 at 7:39 PM, <Spike_White< at >dell.com> wrote:

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

Re: Some Problems with "gpg -keyserver"

Olivier Calzi — 2012-05-23T09:28:38

Thanks Jared,

I'have tried :

gpg --keyserver  109.230.243.87 --recv-key 1285491434D8786F

with each serveur the dig command found.
I'm in a firm, we have a Squid proxy. Do you think it will be the reason of
the failure?

Thanks, Have a nice day

2012/5/22 <Jared_Dominguez< at >dell.com>

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

RE: R510 Linux NIC Order

Bart Lubberdink — 2012-05-23T05:22:29

Hello Martin,

We have seen this problem also (only in our case) with some RedHat installations in combination with more than 2 network interfaces.
And on multiple servers (PE1950, R410... etc.)
I assumed it had something to do with a timing problem so udev wil detect card 1 and card 2 in a random order

The only option to get this fixed is the option Stefan mentioned.
Setting udev rules didn't solve the problem for our situation.

Kind regards,
___________________________________
Bart Lubberdink
Technical Consultant
 
RAM Mobile Data
Planetenbaan 26
3606 AK Maarssen
 
( 030-2390 390
Ê 030-2390 320
* b.lubberdink< at >ram.nl
 
RAM Mobile Data (Netherlands) B.V.
Statutair gevestigd te Utrecht
Handelsregisternr. 30115741
 
P please don't print this e-mail unless you really need to
 

-----Original Message-----
From: linux-poweredge-bounces< at >dell.com [mailto:linux-poweredge-bounces< at >dell.com] On Behalf Of Heijmans S (spir-it)
Sent: dinsdag 22 mei 2012 15:51
To: Martin Seener; linux-poweredge< at >lists.us.dell.com
Subject: RE: R510 Linux NIC Order

Hi,

Just saw that debian uses /etc/network/interfaces for the NIC configuration. 
Do you use something like this in the config file;
'hwaddress ether 00:01:04:1b:2C:1F'


Stefan

-----Oorspronkelijk bericht-----
Van: Martin Seener [mailto:martin< at >seener.de] 
Verzonden: dinsdag 22 mei 2012 15:40
Aan: Heijmans S (spir-it)
Onderwerp: Re: R510 Linux NIC Order

You mean "ifconfig eth0" - yes theres by default the mac-addr = hwaddr.
its just debian squeeze default, if you want...

martin

Am 5/22/12 3:18 PM, schrieb Heijmans S (spir-it):

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

RE: Two questions from a newbie

2012-05-23T03:39:50

Hi Mesterhazy,

Using omarolemap feature, administrators can only elevate the privileges of the users. Demotions are not a use case and technically it is not advised to do so. If there is an entry pointing to demotion, then the users will get their default OS based privilege level.

OMSA has the ability to limit the user access based on group (Administrators, Power users, Users). Please refer the below commands:

1. omconfig preferences useraccess enable=user  : Grants Server Administrator access to Users, Power Users, and Administrators.
2. omconfig preferences useraccess enable=poweruser : Grants Server Administrator access to Power Users and Administrators.
3. omconfig preferences useraccess enable=admin : Grants Server Administrator access to Administrators only

Thanks,
Chandrasekhar R
Dell | OpenManage
office +91 80 41178649

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

Message: 1
Date: Tue, 22 May 2012 10:33:58 -0500
From: <Jared_Dominguez< at >DELL.com>
Subject: RE: Some Problems with "gpg -keyserver"
To: <oliviercalzi< at >gmail.com>, <linux-poweredge< at >lists.us.dell.com>
Message-ID:
<93720FE55DA3044C9F74B2962338F7DE8A0CED4D57< at >AUSX7MCPC109.AMER.DELL.COM>

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

pool.sks-keyservers.net is a pool using DNS round robin. If you have trouble getting the key from there, you can try from one of the constituent hosts. "dig pool.sks-keyservers.net" and choose one to use for the --keyserver option in the instructions below, but I recommend not hardcoding a specific server in any configuration files. (The point of the pool is to avoid hammering one keyserver.)

--Jared

From: linux-poweredge-bounces-Lists On Behalf Of Olivier Calzi
Sent: Tuesday, May 22, 2012 4:18 AM
To: linux-poweredge-Lists
Subject: Some Problems with "gpg -keyserver"

Hye Everyone,

I'm Oliver from France.

I have been try to instal Dell OM 7.0 on my Ubuntu 11.04.
I have some probleme of dependancy.
I have tried to folow : https://linux.dell.com/repo/community/deb/latest/

This instructions didn't work for me:

gpg --keyserver pool.sks-keyservers.net<http://pool.sks-keyservers.net> --recv-key 1285491434D8786F

gpg -a --export 1285491434D8786F | sudo apt-key add -

What do you think about it?

Thanks

Olivier Calzi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.us.dell.com/pipermail/linux-poweredge/attachments/20120522/a1fdde17/attachment-0001.html 

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

Message: 2
Date: Tue, 22 May 2012 18:32:20 +0200
From: Mester <mester< at >freemail.hu>
Subject: Re: Two questions from a newbie
To: David RIBEIRO <david.ribeiro76< at >gmail.com>
Cc: linux-poweredge< at >dell.com
Message-ID: <4FBBBF94.6040405< at >freemail.hu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed


I tried but with no luck.
If I only have user1 * Administrator in this file the root user can still logon.
I also tried to disable User logons to OMSA and have root * User in the omarolemap but root can still logon as administrator.
So is there a way to somehow disable root logons?


Attila Mesterhazy



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

_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

End of Linux-PowerEdge Digest, Vol 96, Issue 39
***********************************************

Re: R610 PXE RHEL5 install

Bryan Seitz — 2012-05-22T19:16:56

All,

     I know this post is about RHEL5, but just a tidbit of information
here that might be useful to some.  You will find that EL6 will name the
interfaces 'em1/em2' for embedded 1 and embedded 2 respectively.  I use
the following kernel option during install and after install to use the
old behavior:

biosdevname=0 

Cheers

On 5/22/12 2:39 PM, "Spike_White< at >Dell.com" <Spike_White< at >Dell.com> wrote:

Re: newbie hep - R610 with RHEL6.2 and multipath issues

Ricardo Stella — 2012-05-22T19:01:10

Hi Austin,

I did boot rescue and was able to restore the multipath.conf file.  I
also edited it and blacklisted the local device.

However, the device is still being managed by multipath no matter what. 
Any other ideas?  TIA.

Ricardo.

°((( = (( ===°°° ((( ================================================

On 5/21/2012 10:09 AM, Austin Murphy wrote:
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

RE: R610 PXE RHEL5 install

2012-05-22T18:39:00

Yes, the RHEL5 boot image enumerates NICs screwy.   Often it even enumerates daughter card NICs before on-board NICs.  

PARENTHETICAL NOTE:   This is not a real problem, except in imaging. As I anticipate your post-install scripts will re-enumerate your NICs in your desired way.  So this is a nuisance only during imaging. 

I image a lot of Dell PowerEdge servers w/ RHEL5, here's several tips:

1. For all of a particular server model, it *always* enumerates the same screwy way.  So if your daughter NICs are enumerated before your onboards on one R610, they will be enumerated this way on *all* R610s.

That means....

2. If you can go physical to image a R710 w/ this NIC config, you can click on "identify" on the NIC selection screen.   Flash the NIC for 30 - 60 secs, go around back to identify which NIC this is. Once you identify how the RHEL5 boot image enumerates this R610, you know it will enumerate all R710s the same way.  So you can then remote image R610s w/ confidence.  (NOTE:  flashing NICs works less well w/ blade server models.  :-) )

More tips:
3. you can look up the on-board NIC vendor for a particular server model and eliminate NIC candidates that way.  For example, I believe on a R610 all on-board NICs are Broadcom.  So if you see Intel NICs in your NIC selection menu, you know they're daughter cards.

4. *Usually* the daughter cards are more recent chipset than the onboard NICs.  So look for the older chipset NICs, those are usually your onboard NICs.  For instance, B'com 5708's or 5709's.

Message: 2
Date: Tue, 22 May 2012 10:57:47 +0530
From: <Charles_Rose< at >Dell.com>
Subject: RE: R610 PXE RHEL5 install
To: <govind.rhul< at >gmail.com>, <linux-poweredge< at >lists.us.dell.com>
Message-ID:
<D29774500E5B5D4B9F499BD4D416440124703F5EE3< at >BLRX7MCDC201.AMER.DELL.COM>

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

Govind,
When you arrive at the network device selection screen in the installer, try choosing eth1 (if you had chosen eth0 earlier and it did not work for you).

It is possible that our assumption of NIC1->eth0, NIC2->eth1 might be NIC1->eth1, NIC2->eth0. So the installer is probably sending out DHCP requests on NIC2. You could also add NIC2's MAC to DHCP server and see if that helps.

-Charles

From: linux-poweredge-bounces-Lists On Behalf Of Govind B. Songara
Sent: Monday, May 21, 2012 9:47 PM
To: linux-poweredge-Lists
Subject: R610 PXE RHEL5 install

Hi,

I am newbie with PE  R610 server, stuck with  RHEL5 installation via PXE.

It has 4 1gb NIC, NIC1/NIC2 enabled for "Enabled with PXE " and completely disabled NIC2/3

DHCP server configured to listen for mac of NIC1, it received the request from this mac only once and offered it, then download the kernel and try to install and stuck with configuring TCP/IP and there is no subsequent DHCP request from it.

Is my bios setting  wrong or Am  I missing anything?

Thanks
Govind

*************

Re: Two questions from a newbie

Sabuj Pattanayek — 2012-05-22T18:11:52

anywhere in the world client vpn -> nxclient (administrative box),
browser -> OMSA on server

Re: Two questions from a newbie

Sabuj Pattanayek — 2012-05-22T16:41:30

If you can't figure out how to get this to work, what I ended up doing
was locking down web access to 1311 from my administrative system or
particular IPs to which only I and other admins have access.

On Tue, May 22, 2012 at 11:32 AM, Mester <mester< at >freemail.hu> wrote:

Re: Two questions from a newbie

Mester — 2012-05-22T16:32:20

I tried but with no luck.
If I only have user1 * Administrator in this file the root user can 
still logon.
I also tried to disable User logons to OMSA and have root * User in the 
omarolemap but root can still logon as administrator.
So is there a way to somehow disable root logons?


Attila Mesterhazy

RE: Some Problems with "gpg -keyserver"

2012-05-22T15:33:58

pool.sks-keyservers.net is a pool using DNS round robin. If you have trouble getting the key from there, you can try from one of the constituent hosts. "dig pool.sks-keyservers.net" and choose one to use for the --keyserver option in the instructions below, but I recommend not hardcoding a specific server in any configuration files. (The point of the pool is to avoid hammering one keyserver.)

--Jared

From: linux-poweredge-bounces-Lists On Behalf Of Olivier Calzi
Sent: Tuesday, May 22, 2012 4:18 AM
To: linux-poweredge-Lists
Subject: Some Problems with "gpg -keyserver"

Hye Everyone,

I'm Oliver from France.

I have been try to instal Dell OM 7.0 on my Ubuntu 11.04.
I have some probleme of dependancy.
I have tried to folow : https://linux.dell.com/repo/community/deb/latest/

This instructions didn't work for me:

gpg --keyserver pool.sks-keyservers.net<http://pool.sks-keyservers.net> --recv-key 1285491434D8786F

gpg -a --export 1285491434D8786F | sudo apt-key add -

What do you think about it?

Thanks

Olivier Calzi
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge

M610 Bios update from repo

jean-marc vizier — 2012-05-22T14:51:45

Hello,

I made a mirror from linux.dell.com/repo on centos (daily update). It seems
ok but when i upgrade firmware for an M610, the last bios found is 6.0.7 or
on dell web site, the last one is 6.1.0.*

Is the Dell repo up2date ? maybe mine ..

All commands are run from centos 6 via PXE

--> The yum logs : (i remove the No package list)

Loaded plugins: dellsysid, fastestmirror, security
Loading mirror speeds from cached hostfile
Setting up Install Process
Package
4:Server_BIOS_11G_componentid_00159_for_system_ven_0x1028_dev_0x0287-6.0.7-1.noarch
already installed and latest version
Package 4:AL11SX_2_5_15K_SAS_146GB_DU_componentid_20515-a02-1.noarch
already installed and latest version
Package
4:SAS_Backplane_Firmware_componentid_11204_for_system_ven_0x1028_dev_0x0287-a00-1.noarch
already installed and latest version
Package 4:M710HD_Quad_Port_1Gig_5709_NDC_ven_0x14e4_dev_0x163a-a07-1.noarch
already installed and latest version
Package 4:M710HD_Quad_Port_1Gig_5709_NDC_ven_0x14e4_dev_0x163a-a07-1.noarch
already installed and latest version
Package 4:M710HD_Quad_Port_1Gig_5709_NDC_ven_0x14e4_dev_0x163a-a07-1.noarch
already installed and latest version
Package 4:M710HD_Quad_Port_1Gig_5709_NDC_ven_0x14e4_dev_0x163a-a07-1.noarch
already installed and latest version
Package
4:PERC_6_i_Integrated_Blade_ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0d-a14-1.noarch
already installed and latest version
Resolving Dependencies
--> Running transaction check
---> Package
32_Bit_Diagnostics_componentid_00196_for_system_ven_0x1028_dev_0x0287.noarch
4:5154.1-1 will be installed
--> Processing Dependency: dell_ie_module(MASER_DIAGS) for package:
4:32_Bit_Diagnostics_componentid_00196_for_system_ven_0x1028_dev_0x0287-5154.1-1.noarch
---> Package
Lifecycle_Controller_componentid_18980_for_system_ven_0x1028_dev_0x0287.noarch
4:a00-1 will be installed
--> Processing Dependency: dell_ie_module(MASER_USC) for package:
4:Lifecycle_Controller_componentid_18980_for_system_ven_0x1028_dev_0x0287-a00-1.noarch
---> Package
OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_dev_0x0287.noarch
4:a00-1 will be installed
--> Processing Dependency: dell_ie_module(MASER_DP) for package:
4:OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_dev_0x0287-a00-1.noarch
---> Package
iDRAC_componentid_15051_for_system_ven_0x1028_dev_0x0287.noarch 4:a00-1
will be installed
--> Processing Dependency: dell_ie_module(ESM_Oxygen) for package:
4:iDRAC_componentid_15051_for_system_ven_0x1028_dev_0x0287-a00-1.noarch
--> Running transaction check
---> Package dell_ie_maser_diags.x86_64 0:3.1.0-1.3.2.el6 will be installed
---> Package dell_ie_maser_dp.x86_64 0:3.1.0-1.3.2.el6 will be installed
---> Package dell_ie_maser_usc.x86_64 0:3.1.0-1.3.2.el6 will be installed
---> Package dell_ie_oxygen.x86_64 0:6.5.0-1.239.1.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package                         Arch   Version           Repository
Size
================================================================================
Installing:
 32_Bit_Diagnostics_componentid_00196_for_system_ven_0x1028_dev_0x0287
                                 noarch 4:5154.1-1        dell-omsa-indep
4.0 M
 Lifecycle_Controller_componentid_18980_for_system_ven_0x1028_dev_0x0287
                                 noarch 4:a00-1           dell-omsa-indep
6.1 M
 OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_dev_0x0287
                                 noarch 4:a00-1           dell-omsa-indep
107 M
 iDRAC_componentid_15051_for_system_ven_0x1028_dev_0x0287
                                 noarch 4:a00-1           dell-omsa-indep
20 M
Installing for dependencies:
 dell_ie_maser_diags             x86_64 3.1.0-1.3.2.el6   dell-omsa-indep
4.3 k
 dell_ie_maser_dp                x86_64 3.1.0-1.3.2.el6   dell-omsa-indep
4.3 k
 dell_ie_maser_usc               x86_64 3.1.0-1.3.2.el6   dell-omsa-indep
4.4 k
 dell_ie_oxygen                  x86_64 6.5.0-1.239.1.el6 dell-omsa-indep
4.2 k

Transaction Summary
================================================================================
Install       8 Package(s)

Total download size: 138 M
Installed size: 161 M
Downloading Packages:
--------------------------------------------------------------------------------
Total                                            32 MB/s | 138 MB
00:04
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : dell_ie_oxygen-6.5.0-1.239.1.el6.x86_64
1/8
  Installing : dell_ie_maser_dp-3.1.0-1.3.2.el6.x86_64
2/8
  Installing : dell_ie_maser_usc-3.1.0-1.3.2.el6.x86_64
3/8
  Installing : dell_ie_maser_diags-3.1.0-1.3.2.el6.x86_64
4/8
  Installing : 4:32_Bit_Diagnostics_componentid_00196_for_system_ven_0x10
5/8
  Installing : 4:Lifecycle_Controller_componentid_18980_for_system_ven_0x
6/8
  Installing : 4:OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_
7/8
  Installing : 4:iDRAC_componentid_15051_for_system_ven_0x1028_dev_0x0287
8/8

Installed:

32_Bit_Diagnostics_componentid_00196_for_system_ven_0x1028_dev_0x0287.noarch
4:5154.1-1

Lifecycle_Controller_componentid_18980_for_system_ven_0x1028_dev_0x0287.noarch
4:a00-1
  OS_Drivers_Pack_componentid_18981_for_system_ven_0x1028_dev_0x0287.noarch
4:a00-1
  iDRAC_componentid_15051_for_system_ven_0x1028_dev_0x0287.noarch
4:a00-1

Dependency Installed:
  dell_ie_maser_diags.x86_64
0:3.1.0-1.3.2.el6
  dell_ie_maser_dp.x86_64
0:3.1.0-1.3.2.el6
  dell_ie_maser_usc.x86_64
0:3.1.0-1.3.2.el6
  dell_ie_oxygen.x86_64
0:6.5.0-1.239.1.el6

Complete!

--> update_firmware logs :

Running system inventory...

Searching storage directory for available BIOS updates...
Checking BIOS - 6.0.7
    Available: dell_dup_componentid_00159 - 6.0.7
    Available: dell_dup_componentid_00159 - 6.0.7
    Did not find a newer package to install that meets all installation
checks.
Checking MBE2147RC Firmware - d906
    Available: dell_dup_componentid_20515 - d906
    Did not find a newer package to install that meets all installation
checks.
Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.07
    Available: dell_dup_componentid_11204 - 1.07
    Available: dell_dup_componentid_11204 - 1.07
    Did not find a newer package to install that meets all installation
checks.
Checking System BIOS for PowerEdge M610 - 6.0.7
    Did not find a newer package to install that meets all installation
checks.
Checking Dell Lifecycle Controller - 1.5.1.57
    Available: dell_dup_componentid_18980 - 1.5.1.57
    Did not find a newer package to install that meets all installation
checks.
Checking NetXtreme II BCM5709S Gigabit Ethernet rev 20 (eth1) - 6.2.16
    Available: pci_firmware(ven_0x14e4_dev_0x163a) - 6.2.16
    Did not find a newer package to install that meets all installation
checks.
Checking NetXtreme II BCM5709S Gigabit Ethernet rev 20 (eth0) - 6.2.16
    Available: pci_firmware(ven_0x14e4_dev_0x163a) - 6.2.16
    Did not find a newer package to install that meets all installation
checks.
Checking Dell OS Drivers Pack - 6.5.3
    Available: dell_dup_componentid_18981 - 6.5.3
    Did not find a newer package to install that meets all installation
checks.
Checking iDRAC6 - 3.30
    Available: dell_dup_componentid_15051 - 3.30
    Did not find a newer package to install that meets all installation
checks.
Checking NetXtreme II BCM5709S Gigabit Ethernet rev 20 (eth3) - 6.2.16
    Available: pci_firmware(ven_0x14e4_dev_0x163a) - 6.2.16
    Did not find a newer package to install that meets all installation
checks.
Checking NetXtreme II BCM5709S Gigabit Ethernet rev 20 (eth2) - 6.2.16
    Available: pci_firmware(ven_0x14e4_dev_0x163a) - 6.2.16
    Did not find a newer package to install that meets all installation
checks.
Checking PERC 6/i Integrated Controller 0 Firmware - 6.3.1-0003
    Available:
pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0d) - 6.3.1-0003
    Did not find a newer package to install that meets all installation
checks.
Checking Dell 32 Bit Diagnostics, v.5154A0, 5154.1 - 5154a0
    Available: dell_dup_componentid_00196 - 5154a0
    Did not find a newer package to install that meets all installation
checks.

This system does not appear to have any updates available.
No action necessary.


Thanks

----

Vizier Jean-Marc
_______________________________________________
Linux-PowerEdge mailing list
Linux-PowerEdge< at >dell.com
https://lists.us.dell.com/mailman/listinfo/linux-poweredge