Re: libsmbios and smbios-* from EPEL conflicts with dell-community repository
Hi, Did Michael Brown take a look at this issue? If believe the EPEL version does work so a dependency on just the package is good enough, let yum choose the newer package. Brandon On Sat, Jun 19, 2010 at 12:11 AM, Robin Bowes robin-li...@robinbowes.com wrote: I believe this because dell-community is missing the i386 version of libsmbios. See this thread: http://lists.us.dell.com/pipermail/linux-poweredge/2010-May/042332.html Any reason this is not yet fixed? R. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
libsmbios and smbios-* from EPEL conflicts with dell-community repository
Hey guys, It seems like the smbios packages from dell-community are conflicting with the same packages in EPEL. Does anybody know what the recommended way to resolve this? Seems like there are 2 choices, use --disablerepo and go with either EPEL or dell-community. epel - smbios-utils-python.2.2.16-2.1.el5 dell-community - smbios-utils-python.2.2.21-3.2.el5 Might not matter too much but wanted to see if you guys have seen a similar problem. Thanks! yum update Resolving Dependencies -- Running transaction check --- Package dell-community-repository.noarch 0:1-11.1.el5 set to be updated --- Package yum-dellsysid.x86_64 0:2.2.21-3.2.el5 set to be updated -- Processing Dependency: smbios-utils-python = 2.2.21-3.2.el5 for package: yum-dellsysid -- Finished Dependency Resolution yum-dellsysid-2.2.21-3.2.el5.x86_64 from dell-community has depsolving problems -- Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) Error: Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: libsmbios and smbios-* from EPEL conflicts with dell-community repository
On Fri, Jun 18, 2010 at 9:46 PM, Matt Domsch matt_dom...@dell.com wrote: On Fri, Jun 18, 2010 at 08:06:49PM -0700, Brandon Ooi wrote: That's a bogus dependency in yum-dellsysid. There's no reason for it to depend on exactly that version of smbios-utils-python. Something strange is happening, as yum-dellsysid is from the same SRPM as smbios-utils-python, meaning the yum-dellsysid noarch package must have gotten pushed out, while the smbios-utils-python packages that match it didn't. But that isn't what happened - they're both present in the repo together... ./isv:/dell:/community/el5-x86_64/x86_64/smbios-utils-python-2.2.21-3.2.el5.x86_64.rpm ./isv:/dell:/community/el5-x86_64/x86_64/yum-dellsysid-2.2.21-3.2.el5.x86_64.rpm As as shot in the dark, perhaps upgrade only the dell-community-repository RPM first, and then try the full yum upgrade. It may be that the new repository RPM needs to be installed first to provide proper (maybe fixed?) pointers to the community repo, so subsequent upgrades will find the right content. Michael Brown has been working on this code again this last week - hopefully he can look into it - but likely not over the weekend. Thanks, Matt -- Matt Domsch Technology Strategist Dell | Office of the CTO I did a yum upgrade dell-community-repository to see if that solved the problem but it did not. It was good to isolate the problem though. Here's the latest update attempt. Is there an SRPM for yum-dellsysid? I didn't find it in http://linux.dell.com/repo/community/repositories/isv:/dell:/community/el5-x86_64/src/ Setting up Update Process Resolving Dependencies -- Running transaction check --- Package yum-dellsysid.x86_64 0:2.2.21-3.2.el5 set to be updated -- Processing Dependency: smbios-utils-python = 2.2.21-3.2.el5 for package: yum-dellsysid -- Finished Dependency Resolution yum-dellsysid-2.2.21-3.2.el5.x86_64 from dell-community has depsolving problems -- Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) Error: Missing Dependency: smbios-utils-python = 2.2.21-3.2.el5 is needed by package yum-dellsysid-2.2.21-3.2.el5.x86_64 (dell-community) You could try using --skip-broken to work around the problem You could try running: package-cleanup --problems package-cleanup --dupes rpm -Va --nofiles --nodigest The program package-cleanup is found in the yum-utils package. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: linux.dell.com rsync targets
wget has a spider feature you can use. On Thu, Apr 1, 2010 at 4:59 PM, David Pierce david.pie...@reachlocal.comwrote: Probably not the right place to ask, but I really doubt they would. I'd just use curl and a bit of logic in a script: 1. Get a list of files. 2. If I don't have a file in that list, get it. 3. If I have it, does mine have the same size (and maybe timestamp) (poorman's checksum)? If not, get it. DP On 04/01/2010 02:58 PM, Eberhard Moenkeberg wrote: Hi, would it be possible to offer http://linux.dell.com/files/ via rsync? Viele Gruesse Eberhard Moenkeberg (emoe...@gwdg.de, e...@kki.org) ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: R710: clear SEL
omconfig system esmlog action=clear On Wed, Mar 24, 2010 at 3:18 PM, Steve Thompson s...@vgersoft.com wrote: Anyone know of a way to clear the event log of an R710 using OMSA? I know that it can be done with ipmitool, but I'm looking for a solution using omconfig (and not via the web interface). The documentation appears silent on this point. TIA, Steve ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: openmanage 6.2 / missing controller issue fixed ?
there are other software packages that implement IPMI (freeipmi?) On Wed, Mar 24, 2010 at 5:55 PM, Ryan Miller rmil...@smartertravelmedia.com wrote: There's something funny about this--none of my 1950/2950/610/710 hardware has OpenIPMI installed, yet omreport is working everywhere. Ryan -Original Message- From: Ryan Pugatch [mailto:li...@ryanp.com] On Behalf Of Ryan Pugatch Sent: Friday, March 19, 2010 3:39 PM To: Brandon Ooi Cc: Nielsen, Steve; Ryan Miller; linux-poweredge@dell.com Subject: Re: openmanage 6.2 / missing controller issue fixed ? On 03/19/2010 02:57 PM, Brandon Ooi wrote: This series of commands works for all of my RHEL/Centos machines. yum -y install procmail OpenIPMI chkconfig --level 345 ipmi on service ipmi start wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash yum -y install srvadmin-all #relogin to pick up new $PATH srvadmin-services.sh enable srvadmin-services.sh start wget -q -O - http://linux.dell.com/repo/community/bootstrap.cgi | bash #next part is firmware install. optional yum -y install dell_ft_install yum -y install $(bootstrap_firmware) Nice, this worked for me on a 1950. Will be testing on an R710 soon. Ryan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: openmanage 6.2 / missing controller issue fixed ?
This series of commands works for all of my RHEL/Centos machines. yum -y install procmail OpenIPMI chkconfig --level 345 ipmi on service ipmi start wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash yum -y install srvadmin-all #relogin to pick up new $PATH srvadmin-services.sh enable srvadmin-services.sh start wget -q -O - http://linux.dell.com/repo/community/bootstrap.cgi | bash #next part is firmware install. optional yum -y install dell_ft_install yum -y install $(bootstrap_firmware) On Fri, Mar 19, 2010 at 11:03 AM, Nielsen, Steve sniel...@comscore.comwrote: You need to install OpenIPMI and then run srvadmin-sevices.sh restart. That works on my systems. Steve Steve Nielsen VP, Open Source Engineering | comScore, Inc. (NASDAQ:SCOR) o +1 (312) 775-6473 | sniel...@comscore.com comScore Measuring the Digital World Introducing the AdEffx™ Suite for Digital Advertising Effectiveness Measure what Matters Correctly http://www.comscore.com/AdEffx -Original Message- From: linux-poweredge-boun...@dell.com [mailto: linux-poweredge-boun...@dell.com] On Behalf Of Ryan Pugatch Sent: Friday, March 19, 2010 12:42 PM To: Ryan Miller Cc: linux-poweredge@dell.com Subject: Re: openmanage 6.2 / missing controller issue fixed ? Yeah, with srvadmin-all. Fresh install on both R710 and 1950. [r...@testbox ~]# omreport storage controller No controllers found [r...@testbox ~]# omreport chassis info Error! Chassis info setting unavailable on this system. etc.. from our kickstart post-reboot script: yum -y install srvadmin-all /usr/bin/srvadmin-services.sh start after we do that, we install Dell firmware upgrades and do a yum update. I wonder if maybe one of those breaks it? On 03/19/2010 01:20 PM, Ryan Miller wrote: Did you actually install srvadmin-all ? I know it seems like it should work with just the storage packages, but I think some of the underlying services are set up by other packages. 6.2 is now working for me with clean install on CentOS 5 with PERC6i and SAS5i controllers. Haven't tried it on an H700 yet. Ryan -Original Message- From: linux-poweredge-boun...@dell.com [mailto:linux-poweredge- boun...@dell.com] On Behalf Of Ryan Pugatch Sent: Friday, March 19, 2010 12:31 PM To: Keith Beeby Cc: linux-poweredge@dell.com Subject: Re: openmanage 6.2 / missing controller issue fixed ? On 03/19/2010 12:29 PM, Keith Beeby wrote: Hi, So is just the case we are waiting for Dell to resolve this with a new update? Anyone know if Dell has acknowledged the issue and working on a resolve? Thanks Keith I'm not really sure at this point.. some people say it works, others day it doesn't. It doesn't work for me. Ryan ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Adding a second Quad Core L5420 CPU to a 1950 III
Actually I tried this for some of our SC1435's, the cpu doesn't matter but it's the 1U heatsink that needs to be Dell to mount properly. There is almost 0 market for the heatsinks. Did you find a Dell heatsink? If it is, that's probably all you need. I've seen it replaced before and it's part-less and tool-less. Brandon On Thu, Feb 18, 2010 at 11:19 AM, PJF sec-al...@socalweb.com wrote: I currently have a 1950 III with a single Quad Core Intel(R) Xeon(R) CPU L5420 @ 2.50GHz, I'd like to add an additional one. Street price for the L5420 with Heatsink and Fan included is $424.99 Dell wants to charge me $795.00 for the CPU and $49.99 for the Heatsink and install kit, this is even with special pricing discounts applied. $844.99 vs $424.99 I cant justify the markup. Am I missing something? Are they including some other special dell only parts I need to install this? If I buy the CPU on my own is there any special parts I may need to install it? Anyone here who has added second CPU's on their own to their 1950 III's kindly let me know. Thanks in advance. -- pjf ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Vendor ID?
On my T300 with a PERC6 : Controller PERC 6/i Adapter (Slot 3) ID: 0:0:0 Status: Ok Name : Physical Disk 0:0:0 [..] Vendor ID : SEAGATE Product ID: ST31000640SS Stephan Non-Dell disks? You rebel! ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Third-party drives not permitted on Gen 11 servers
I'm sorry - I must have missed something here. I understand that in Enterprise Storage Solutions (such as Hitachi and NetApp) they only allow qualified drives. Are you officially stating that the R710 box is an Enterprise Storage Solution? Because from my understanding, the R710 is listed in the Servers category on www.dell.com, rather than in the storage category. So I fail to understand your rationale, as I believe that many here do. (Though I don't want to speak for others.) If Dell is intending to provide Enterprise Storage Systems in the form of the PowerEdge line, complete with vendor hard disk lock-in, please let us know clearly and equivocally. I understand this in storage boxes, but not in servers. The hardware lock-in path is a dangerous one, tried by IBM, Sun, Compaq (before they were bought by HP), and HP. Doing this in a server line almost always ends badly. I implore Dell to rethink this strategy. Thank you, -I Hi, Just wanted to input my 2 cents if Dell is listening. The main reason we use Dell is because it's cheap, works well with standard equipment (SATA, SAS, PCI, RAM, Link Agg etc..) and is consistent. Cheap to the point where I buy 2 of everything so I have a hot/cold spare. I'm probably spending more than I would at HP or Sun but I've got 2 of 'em. Ram/drive bad? Throw in something. If it's standard, it'll work. We don't buy cheap drives or cheap ram but with a variety of other systems; I don't want to keep multiple brands of the same 300GB 15k drive or the same 2gb stick of ram handy in case there's a failure. I challenge Dell to show me a case where the generic drive (like a Fujitsu MBA3300RC) fails but their magical firmware succeeds. We've probably bought around 250 Dell servers. If there's lock-in on hard drives that drive up cost.. I might just start building our own servers. Sure, it might fail... but i've got 2 of 'em. Brandon ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Third-party drives not permitted on Gen 11 servers
On Sat, Feb 6, 2010 at 1:59 PM, Robin Bowes robin-li...@robinbowes.comwrote: On 06/02/10 21:45, Steve Thompson wrote: On Sat, 6 Feb 2010, Dameon Wagner wrote: I've only been lurking on the list for a week or so, but after recent experience buying some dell servers, and almost a MD1000 (backed out of that because of the drive/hot-swap-tray availability issue) I'm still damn annoyed, and irritated enough to chip in my 2c... I have found that the caddies for 3.5 drives in MD1000/PE2900 etc are in fact widely available, albeit not from Dell. I just bought quite a few, with screws, for $24 each (I'm in upstate NY). I did call Dell and they said that they _could_ sell me one, but only _one_. Now, that's interesting. I'm looking to buy some storage shortly. I have a quote for an MD1200 with 12 of 2TB NLSAS drives. I'm guessing it would be quite a bit cheaper to just get the MD1220 and source the drives and caddies elsewhere. Where did you see the caddies available? R. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq We usually buy caddies from http://discountechnology.com/Products/SCSI-Hard-Drive-Caddies-Trays ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Third-party drives not permitted on Gen 11 servers
This thread on the dell community forum may be related. boo... http://en.community.dell.com/forums/p/19314432/19649799.aspx On Fri, Feb 5, 2010 at 2:53 PM, Chase Bolt cb...@datinggold.com wrote: I hope this isn't true. If so I will have to start looking into a new solution for our server purchases as this is unacceptable. - Original Message - From: Philip Tait phi...@subaru.naoj.org To: Linux-PowerEdge@dell.com Sent: Friday, February 5, 2010 2:31:00 PM GMT -08:00 US/Canada Pacific Subject: Third-party drives not permitted on Gen 11 servers I just received my first Gen11 server, R710, with H700 PERC. I removed the supplied drives, and installed 4 Barracuda ES.2s. After doing a Clear Configuration in the pre-boot RAID setup utility, I can perform no operation with the drives - they are marked as blocked. Is Dell preventing the use of 3rd-party HDDs now? Thanks for any enlightenment. Philip J. Tait http://subarutelescope.org ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Firmware updates not being applied to PE2950
Ah, that worked. Thanks! Here's what I did (exactly what you told me to) yum erase dell-firmware-repository yum erase firmware-tools yum -y install dell_ft_install yum -y install $(bootstrap_firmware) update_firmware --yes -v Let me know if you still want the update_firmware output and log. I assumed no because it fixed my problem. Thanks again! Brandon On Mon, Feb 1, 2010 at 7:29 AM, jeffrey_l_mend...@dell.com wrote: From: linux-poweredge-bounces-Lists On Behalf Of Brandon Ooi Sent: Saturday, January 30, 2010 8:16 PM To: linux-poweredge-Lists Subject: Firmware updates not being applied to PE2950 Here are the steps I've followed to get to this point... yum -y install procmail OpenIPMI chkconfig --level 345 ipmi on service ipmi start wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash yum -y install srvadmin-all #relogin srvadmin-services.sh enable srvadmin-services.sh start wget -q -O - http://linux.dell.com/repo/community/bootstrap.cgi | bash wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi | bash yum -y install firmware-addon-dell yum -y install dell_ft_install yum -y install $(bootstrap_firmware) --- I wouldn't configure both the old firmware repo and the current hardware repo. Try: Removing the firmware repo Removing firmware-tools and everything that depends on it. Redo: yum -y install dell_ft_install yum -y install $(bootstrap_firmware) Run: update_firmware --yes -v Capture: /var/log/firmware-updates.log Send the output of the update command and the log. -Jeff ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: update_firmware not showing updates ?
Do you have the firmware and community repositories added? Did you do a yum update to pick up the new firmware packages? http://linux.dell.com/wiki/index.php/Products/PowerEdge I've also seen problems if the dell_ft_install isn't installed B On Sun, Jan 31, 2010 at 9:22 AM, Stephan van Hienen stephan.van.hie...@thevalley.nl wrote: I tried running update_firmware on an outdated PE1950 system today, but it didn't have any updates ? Output from update_firmware below (system is running RHEL 4.8) Searching storage directory for available BIOS updates... Checking BIOS - 2.3.1 Did not find a newer package to install that meets all installation checks. Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.05 Did not find a newer package to install that meets all installation checks. Checking System BIOS for PowerEdge 1950 - 2.3.1 Did not find a newer package to install that meets all installation checks. Checking PERC 5/i Integrated Controller 0 Firmware - 5.2.1-0067 Did not find a newer package to install that meets all installation checks. Checking BMC - 2.37 Did not find a newer package to install that meets all installation checks. Checking MAY2036RC Firmware - d108 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. While SUU 6.2 gives the following output : === Comparison Results component: BIOS component type: BIOS current version: 2.3.1 repository version: 2.6.1 Package name: PE1950_BIOS_LX_2.6.1.BIN Applicability: Package can be applied - component: BMC component type: Firmware current version: 2.37 = repository version: 2.37 Package name: BMC_FRMW_LX_R202156.BIN Applicability: Package cannot be applied - component: PERC 5/i Integrated Controller 0 Firmware component type: Firmware current version: 5.2.1-0067 repository version: 5.2.2-0072 Package name: RAID_FRMW_LX_R189337.BIN Applicability: Package can be applied - component: SAS/SATA Backplane 0:0 Backplane Firmware component type: Firmware current version: 1.05 = repository version: 1.05 Package name: ESM_FRMW_LX_R149431.BIN Applicability: Package cannot be applied - component: NetXtreme II BCM5708 Gigabit Ethernet rev 11 (eth0) component type: Firmware current version: 4.6.0 repository version: 5.0.12 Package name: NETW_FRMW_LX_R246418.BIN Applicability: Package can be applied - component: NetXtreme II BCM5708 Gigabit Ethernet rev 11 (eth1) component type: Firmware current version: 1.8.0 repository version: 5.0.12 Package name: NETW_FRMW_LX_R246418.BIN Applicability: Package can be applied - component: OpenManage Server Administrator Managed Node component type: Application current version: 6.2.0 = repository version: 6.2.0 Package name: OM_6.2.0_ManNode_A00.tar.gz Applicability: Package cannot be applied Any hints why update_firmware doesn't show these updates ? firmwaretools rpm version installed is 2.1.9.d1-2.1.el4. ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Firmware updates not being applied to PE2950
Hi guys, I'm having some problems applying firmware updates for my PE2950's with the update_firmware tool. Seems like it detects the hardware and installs the firmware, but upon soft reboot all the versions are still the same and update_firmware still says that it found firmware that needs to be updated. I tried putting reboot=bios as a kernel arg but it didn't seem to change anything. Applying these firmware updates manually seems to work (e.g. ./PE2950_BIOS_LX_2.6.1.BIN). All the OMSA tools seem to work correctly. Did I miss a step somewhere? Is there any way I can find out what went wrong? this is on a clean CentOS 5.4 machine. [r...@core17 ~]# update_firmware --yes hello world from update module doCheck() Running system inventory... Searching storage directory for available BIOS updates... Checking SAS/SATA Backplane 0:0 Backplane Firmware - 1.05 Available: dell_dup_componentid_11204 - 1.05 Did not find a newer package to install that meets all installation checks. Checking ST373455SS Firmware - s527 Available: dell_dup_componentid_16113 - s528 Found Update: dell_dup_componentid_16113 - s528 Checking PERC 6/i Integrated Controller 0 Firmware - 6.0.2-0002 Available: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Found Update: pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Checking NetXtreme II BCM5708 Gigabit Ethernet rev 12 (eth1) - 4.0.3 Did not find a newer package to install that meets all installation checks. Checking BIOS - 2.3.1 Available: dell_dup_componentid_00159 - 2.6.1 Found Update: dell_dup_componentid_00159 - 2.6.1 Checking System BIOS for PowerEdge 2950 - 2.3.1 Did not find a newer package to install that meets all installation checks. Checking NetXtreme II BCM5708 Gigabit Ethernet rev 12 (eth0) - 4.0.3 Did not find a newer package to install that meets all installation checks. Checking BMC - 2.10 Available: dell_dup_componentid_05814 - 2.37 Available: dell_dup_componentid_05814 - 1.05 Found Update: dell_dup_componentid_05814 - 2.37 Found firmware which needs to be updated. Running updates... 100% Installing dell_dup_componentid_16113 - s528 Done: Update complete. You must perform a warm reboot for the update to take effect. 100% Installing dell_dup_componentid_00159 - 2.6.1 Done: Update complete. You must perform a warm reboot for the update to take effect. 100% Installing pci_firmware(ven_0x1000_dev_0x0060_subven_0x1028_subdev_0x1f0c) - 6.2.0-0013 Done: Update complete. You must perform a warm reboot for the update to take effect. 100% Installing dell_dup_componentid_05814 - 2.37 Done: Update complete. You must perform a warm reboot for the update to take effect. [r...@core17 ~]# shutdown -r now Broadcast message from root (pts/0) (Sat Jan 30 13:11:59 2010): The system is going down for reboot NOW! [r...@core17 ~]# logout Here are the steps I've followed to get to this point... yum -y install procmail OpenIPMI chkconfig --level 345 ipmi on service ipmi start wget -q -O - http://linux.dell.com/repo/hardware/latest/bootstrap.cgi | bash yum -y install srvadmin-all #relogin srvadmin-services.sh enable srvadmin-services.sh start wget -q -O - http://linux.dell.com/repo/community/bootstrap.cgi | bash wget -q -O - http://linux.dell.com/repo/firmware/bootstrap.cgi | bash yum -y install firmware-addon-dell yum -y install dell_ft_install yum -y install $(bootstrap_firmware) ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
Re: Automatic Detection of PowerEdge Servers
I like to use the 'lshw' program. not sure why rhel doesn't carry it but you can get it in rpmforge. it's got an impressive database of hardware. It should detect the product and vendor of most all components like chassis, cpu, usb connected stuff, add on cards.. Even tells you serial numbers of your ram sticks and firmware versions of your disks. for scripting use XML output snip description: Rack Mount Chassis product: PowerEdge 1950 vendor: Dell Inc. serial: DELL width: 64 bits capabilities: smbios-2.5 dmi-2.5 vsyscall64 vsyscall32 configuration: boot=normal chassis=rackmount uuid=44454C4C--1044-8045-80C04F4C4C20 *-firmware description: BIOS vendor: Dell Inc. physical id: 0 version: 2.6.1 (04/20/2009) *-storage description: RAID bus controller product: MegaRAID SAS 1078 vendor: LSI Logic / Symbios Logic physical id: 0 bus info: p...@:01:00.0 logical name: scsi0 version: 04 width: 64 bits *-disk description: SCSI Disk product: PERC 6/i vendor: DELL physical id: 2.0.0 bus info: s...@0:2.0.0 logical name: /dev/sda version: 1.22 serial: size: 278GiB (299GB) capabilities: partitioned partitioned:dos configuration: ansiversion=5 signature=00063af8 * a lot more stuff etc..etc.. /snip On Wed, Jan 20, 2010 at 2:22 PM, Alexander Dupuy alex.du...@mac.com wrote: Stephen Dowdy suggested: [r...@foo ~]# ipmitool mc info 'lspci' would show up a DRAC4, but thanks for the clue on 'lsusb' for the DRAC5! (following this logic... lspcmcia ?? heh ;) darn :-( 'ipmitool fru list' doesn't show it, and i'm pretty sure dmidecode doesn't show it (unless there's encoding in one of the OEM specific types, and i wouldn't rule that out) You may get some joy from ipmitool sdr elist mcloc: On a 1950 with a BMC (but no DRAC 5, despite the output): # ipmitool sdr elist mcloc BMC | 00h | ok | 7.1 | Dynamic MC @ 20h DRAC 5 | 00h | ok | 11.1 | Dynamic MC @ 26h On a R710 with iDRAC6: # ipmitool sdr elist mcloc iDRAC6 | 00h | ok | 7.1 | Dynamic MC @ 20h If you validate the presence of add-in cards like DRAC4/5 with lspci/lsusb you will probably have a pretty reliable result. @alex -- mailto:alex.du...@mac.com ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq ___ Linux-PowerEdge mailing list Linux-PowerEdge@dell.com https://lists.us.dell.com/mailman/listinfo/linux-poweredge Please read the FAQ at http://lists.us.dell.com/faq
