Well,
After I swapped the modules from the two boxes, I was able to update the
system that had the bad firmware. I think the iDRAC express module is
corrupted since I can ping the IP but not ssh nor connect via web. This is
on the box that has no video now.
The one with no video shows
You can get
https://downloads.dell.com/FOLDER03547784M/1/iDRAC6_2.85_A00_FW_IMG.exe
and then just unzip it to get firmimg.d6
[boutilpj@bartdl dell]$ unzip -l iDRAC6_2.85_A00_FW_IMG.exe
Archive: iDRAC6_2.85_A00_FW_IMG.exe
Length DateTimeName
- -- -
Thanks - I pulled the iDRAC modules from the box that had no video and was
able to reset them on the current system. Firmware I have now is:
iDRAC 1.80.17
Lifecycle 1.5.1.57
I have the Lifecycle repair package, but cannot find the latest idrac
firmware.
Thanks
On Fri, May 12, 2017 at 12:51 PM,
Hi,
while I still try to recover these R610 from a failed firmware upgrade, I
got a hold of an R710 which has RHEL 6.9 installed (just updated) but
firmware is very much old.
Is there a preferred update method and or steps? I would do it via DSU, but
should I update something first before
iDRAC is not responding. The network switch connects but at 10 half and no
mac address is presented.
The second R610 that has a working iDRAC (but no password) is not giving
any video past "Configuring System Memory" so something else is wrong with
this one. This was not upgraded AFAIK. So I
Usually this is the default behavior if the systems wasn’t able to enter
lifecycle controller multiple times or someone manually disabled system
services.
You can go to BIOS an enable system services & try again. If the system is
working fine then, no further action required. If you still
Are you able to access the DRAC GUI? If so you can update there with the
.usc file in the firmware update section.
Cameron Smith
Technical Operations Manager
Network Redux, LLC
Cell: 503-926-4928
On Fri, May 12, 2017 at 7:26 AM, Ricardo Stella wrote:
>
> So we had this
So we had this older R610 which was put off production and was trying to
give it a new life. Used Dell repository manager to create a firmware
bundle and after this got the errors on the title.
Obviously, the system didn't like the firmware updates, so has anyone else
experienced this before and
Hi Mark,
I use spacewalk (upstream version of satellite) with DSU. Note however that my
setup (the default AFAIK) has changed the yum configuration in such a way that
every request goes to spacewalk. So nothing to change on the DSU side, since
every yum request goes to spacewalk. This works