UNSOLVED
PE2650 ESM version updating?
I have a number of PE2650s and I am trying to keep them updated and on the same versions. I have updated all of them to the A10 BIOS, the Primary Backplane Firmware version is 1.01 but the Embedded Server Management / Baseboard Management Controller Firmware Version is not getting updated no matter what I do. Some have v1.07, v1.22, v1.23 and v2.00.
This does not happen when I update my PE6650s. When I updated the PE6650s it made everything current.
Please Advise,
DELL-Mark A
2 Intern
•
2521 Posts
217
0
Posted June 10th, 2003 18:00
Hi,
There are 3 files involved to update the PowerEdge 2650 (Note, the BIOS is now at version A13):
System BIOS, PowerEdge 2650, A13
FileName: PE2650-BIOSA13.exe [633 KB]
Release Date: 6/9/2003
http://support.dell.com/FileLib/Format.aspx?ReleaseID=R61040ESM Firmware, PowerEdge 2650, A02
Filename: fwsBPa02.exe [112 KB]
http://support.dell.com/us/en/filelib/download/index.asp?fileid=R53488ERA and DRACIII/XT, Firmware, 2650, PV 775N, v.2.21, A00
FileName: d_0424v221bm.exe [2 MB]
Release Date: 5/8/2003
http://support.dell.com/FileLib/Format.aspx?ReleaseID=R60406- I have had to do my upgrades for the ERA from tftp. Log into server administrator and change the remote file access under Remote Firmware Configuration to the IP address of your tftp server. Then log into the RAC and choose udate. The files need to be unzipped into the root directory on your tftp server. I had to do this on 4 out of 6 boxes in order to urgrade the RAC. Also a reboot was required before I was able to see my changes in server administrator. Very weird.
The DRAC/ERA/ESM firmware of the 2650's are erratic when it comes to updating via OMSA. We just updated over 100 boxes, and had about 6 that would not update via Server Administrator no matter what. We ended up just sending out an onsite tech and having them do it via floppy. Worked every time.
One thing I have also noticed, is that if you want to reboot the server after performing the update, it is best to wait about 8-9 minutes after you perform the update. The last step of the update is an ESM reset, and sometimes if you reboot the server during an ESM reset, it does not come back up, or comes back up with the ESM not responding.
- A force doesnt do much except remove any dependencies.... like ignoring the current version number, and tells SMFLASH to run no matter what. The issue we have is, that even tho it runs, it does not successfully complete the update. Therefore, I dont think force will help much.... I havent tried any of the new package based executable updates yet, on boxes that could not be updated via OMSA, since we have already updated most of those...
- I noted here that you folks were able to acutally get the RAC on a PE2650 to update it's firmware via TFTP. I have configured my host system and have verified that the RAC is indeed retrieving the firmware, but it just sort of hangs in the middle of the update(70% checksumming or something).
My host is RH 7.2 and the RAC is running 2.10 (Build 02.21). The PE2650 is running BIOS A10 and ESM 2.10. Any ideas? - WHAT IS THE EXACT ORDER of the update process for ESM, BIOS, ESA and PERC?I know for certain that the order is specific and extremely important as I have made a PE4300 unusable by following the wrong advice. Please tell me the order and is it consistent forPE2650 and PE2850 servers?Thank you,Barry.
tnetjpm
37 Posts
217
0
Posted June 5th, 2003 13:00
The ERA firmware (which I believe is at Version 2.21 now) also updates the ESM.
In fact, all 4 versions you've mentioned are ERA firmware versions.
Hope this helps.