Unsolved
This post is more than 5 years old
4 Posts
0
445974
Updating via iDRAC failed
Hi,
I have build a testing ground for OME. Currently the devices I have are PowerEdge 2950 and R710. OME is installed on 2950 and I am trying to update the R710 through iDRAC.
Every time I try installing any updates I get an error that the package "failed to download on target device".
Here are the troubleshooting steps I have taken so far:
- Manually updated iDRAC and BIOS
- Troubleshooting tools says that I should be able to use WS-MAN for everything.
- Tested HTTPS connection to iDRAC from OME server.
- Checked that all ports are open between the connection from OME to iDRAC.
- Checked that OME server is able to download packages and they can be found from directory C:\Program Files(x86)\Dell\SysMgt\Essentials\SystemUpdate\Packages
Please help me to figure this out. I am seriously running out of ideas...
DELL-Rob C
2 Intern
2 Intern
•
2.8K Posts
0
June 3rd, 2013 10:00
Hi and thanks for the post.
There is a long thread that may contain some useful info for your.
Can you review this one and see if it provides anything useful?
What is the version of iDrac f/w you currently have on the R710?
Thx
Rob
en.community.dell.com/.../19475405.aspx
nioman
4 Posts
0
June 5th, 2013 08:00
Hi,
I have now tried the following:
- Removed the device from OME
- deleted job queue
- Added device using only ws-man
- Resetted iDRAC.
After this I tried updating, and it still fails (both with and without hash check)
Here are is the queue I can see with the command "winrm e cimv2/root/dcim/DCIM_LifecycleJob -u:username -p:password -SkipCNcheck -SkipCAcheck -r:https://iDRAC IPAddress/wsman:443 -auth:basic -encoding:utf-8"
While running the update task:
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = CLEARALL
PercentComplete = 0
DCIM_LifecycleJob
InstanceID = JID_001370451373
JobStartTime = TIME_NA
JobStatus = Downloading
JobUntilTime = TIME_NA
Message = Downloading package.
MessageID = RED003
Name = update:DCIM:INSTALLED:PCI:1000:0060:1F0C:1028:6.2.0-0013
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451382
JobStartTime = TIME_NA
JobStatus = New
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = update:DCIM:INSTALLED:NONPCI:18981:0
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451389
JobStartTime = TIME_NA
JobStatus = New
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = update:DCIM:INSTALLED:NONPCI:18980:1.5.5.27
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451398
JobStartTime = TIME_NA
JobStatus = New
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = update:DCIM:INSTALLED:NONPCI:196:5118A0
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451404
JobStartTime = TIME_NA
JobStatus = New
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = update:DCIM:INSTALLED:PCI:14E4:1639:0235:1028:5.0.9
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = RID_001370451406
JobStartTime = TIME_NA
JobStatus = Pending Reboot
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = Reboot1
PercentComplete = NA
And after some time:
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = CLEARALL
PercentComplete = 0
DCIM_LifecycleJob
InstanceID = JID_001370451373
JobStartTime = TIME_NA
JobStatus = Failed
JobUntilTime = TIME_NA
Message = Dell Update Package Download failed.
MessageID = RED006
Name = update:DCIM:INSTALLED:PCI:1000:0060:1F0C:1028:6.2.0-0013
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451382
JobStartTime = TIME_NA
JobStatus = Failed
JobUntilTime = TIME_NA
Message = Dell Update Package Download failed.
MessageID = RED006
Name = update:DCIM:INSTALLED:NONPCI:18981:0
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451389
JobStartTime = TIME_NA
JobStatus = Failed
JobUntilTime = TIME_NA
Message = Dell Update Package Download failed.
MessageID = RED006
Name = update:DCIM:INSTALLED:NONPCI:18980:1.5.5.27
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451398
JobStartTime = TIME_NA
JobStatus = Failed
JobUntilTime = TIME_NA
Message = Dell Update Package Download failed.
MessageID = RED006
Name = update:DCIM:INSTALLED:NONPCI:196:5118A0
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = JID_001370451404
JobStartTime = TIME_NA
JobStatus = Downloading
JobUntilTime = TIME_NA
Message = Downloading package.
MessageID = RED003
Name = update:DCIM:INSTALLED:PCI:14E4:1639:0235:1028:5.0.9
PercentComplete = NA
DCIM_LifecycleJob
InstanceID = RID_001370451406
JobStartTime = TIME_NA
JobStatus = Pending Reboot
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = Reboot1
PercentComplete = NA
At the moment the fw version on R710 iDRAC is 1.95
nioman
4 Posts
0
June 7th, 2013 02:00
Hi,
Could you answer a few questions for me about the update requirements via iDRAC?
- Does the OME server also have to be at least iDRAC6?
- What ports are necessary to be open between the OME server and the iDRAC I am attempting to update.
- The R710 I am attempting to update does not have internet access itself.
- I am using a proxy on the OME server for access to ftp.dell.com. Does this effect the update process in any way since the R710 iDRAC I am updating is not reachable through this proxy. It is only accessible via LAN. (OME does not have settings to ignore proxy setting for certain addresses)
DELL-Raj S
327 Posts
1
June 7th, 2013 10:00
OME server does NOT need to have iDRAC 6. All the commands/file transfer happens between OME package server and iDRAC at the end node.
Following ports need to be opened on OME server to perform system updates:
2607 - HTTPS TCP port for accessing Web GUI and sending https commands
1278 - HTTP TCP port for package server to transfer files between OME and iDRAC
1279 - HTTP TCP port for Scheduling tasks
21 - FTP TCP for accessing ftp.dell.com
Following ports need to be opened on the iDRAC end node to perform system updates:
443 - For receiving and responding to WSMAN commands/requests
Troubleshooting tips:
1) Make sure iDRAC6 (target node) can ping the IP address of OME server. Connect to iDRAC6 from OME server using putty (SSH connection) and run the command "racadm ping "
2) Check if you can access the package path on OME server:
http:// :1278/install_packages/Packages/2950_ESM_Firmware_4NNNG_WN32_2.50_A00.EXE
3) If OME server is dual homed, make sure the package path above has the right IP Address of OME server that is accessible by iDRAC (target node)
Verify that the package path is mapped to http and not https. Follow these steps to confirm:
On OME server, navigate to Start->Administrative Tools->Internet Information Services (IIS) Manager
Expand Sites->OpenManage Essentials->install_packages->Packages
Right click on Packages and select "Switch to Content View"
Right click on any of the package on the right side and say "Browse".
It should launch the browser with http (not https) as the URL path and prompt for downloading the package (run, save...options)
From the JOB status you shared earlier, it looks like iDRAC is not able to download any package from OME server (Message ID = RED006).
dilipnet
2 Intern
2 Intern
•
153 Posts
0
August 2nd, 2013 05:00
Hi
I am facing an issue here :
When I run the update task for iDRAC Firmware upgrade ... task Start running and failed after sometime.
I have selected the update method as iDRAC
machine is listed under non-compliant
I tried the last option which is mentioned on the above
"Right click on any of the package on the right side and say "Browse"."
out-put is attached
https://localhost:2607/install_packages/Packages/
HTTP Error 403.14 - Forbidden
Detailed Error Information:
Module
DirectoryListingModule
Notification
ExecuteRequestHandler
Handler
StaticFile
Error Code
0x00000000
What is the solution for the this issue ?
Regards
Dilip
dilipnet
2 Intern
2 Intern
•
153 Posts
0
August 16th, 2013 12:00
It should launch the browser with http (not https) as the URL path and prompt for downloading the package (run, save...options)
regarding the above statement ... when Itred it is opening with https
does it means the problem is that the updates are failing ?
if yes how to correct it
Regards
Dilip
dilipnet
2 Intern
2 Intern
•
153 Posts
0
August 16th, 2013 12:00
/admin1-> xx.xx.xx.xx/.../ESM_Firmware_3VM7N_W
N32_1.85_A00.EXE
cmdstat
status : 2
status_tag : COMMAND PROCESSING FAILED
error : 253
error_tag : COMMAND NOT RECOGNIZED
/admin1->
How do I overcome this issue.
Regards
Dilip
parmand
10 Posts
0
March 26th, 2014 14:00
Hi Raj,
I know this is an incredibly old post, but I found this on the forums and I'm having a similar issue with my Openmanage. I'm running the new v1.3, and when installing packages on some servers I'm getting the "Package Verification Failed". The 1.3 log of my update is as follows:
Results:
Downloading Packages.
Calling InstallFromUri method to Download packages to the iDRAC
Downloading Package: Lifecycle-Controller_Application_GFFFC_WN32_1.6.0.73_A00.EXE onto the iDRAC
Package download has successfully started and the Job ID is JID_001395863239
The URI given to the iDRAC to download from: http://172.16.1.44:1278/install_packages/Packages/Lifecycle-Controller_Application_GFFFC_WN32_1.6.0.73_A00.EXE
Checking the Status on the following Job(s): JID_001395863239
The JOBID JID_001395863239 has failed with the following message:
Package verification failed.
MessageID: RED007
Download Error occured.
Package Lifecycle-Controller_Application_GFFFC_WN32_1.6.0.73_A00.EXE failed to download on target device. Update failed.
Software Update Task Failed.
One thing I saw is that you mentioned that if you right click in IIS and go to browse that it should go to the http page and not https...mine IS going to https. How do I change this to make it force http and not https?
Thanks!
Dell-PPrabhu
58 Posts
0
April 2nd, 2014 14:00
Parmand - this is a known issue with the older version of the iDRAC firmware. We found the following information. Try this and let us know whether it helps you.
PPrabhu
Problem:
OpenManage Essentials (OME) may fail to update certain Dell Servers with out of band updates. This can be due to a certificate chain change made in May of 2012. The Dell Remote Access Controller (DRAC) changed the certificate chain after a firmware revision. For more details of this issue, refer to the Dell iDRAC release notes in the Dell Lifecycle Controller USC-LCE Version 1.5.5 Readme file.
Solution:
1. Update the iDRAC to firmware version 1.85 for monolithic (3.35 for Blades).
2. Update the Lifecycle Controller to firmware version 1.5.2.
Dell-PPrabhu
58 Posts
0
April 10th, 2014 07:00
Parmand - any update on this? We believe updating your iDRAC will solve this problem. Do let us know your experience...
parmand
10 Posts
0
April 17th, 2014 11:00
Hi Everyone,
Sorry for not getting back to you sooner. Yes, with my servers running 1.5 DRAC, the steps that worked the best for me were:
Manually update to DRAC 1.85
Use Openmanage to update Lifecycle and DRAC to current versions (do NOT do anything else)
Use Openmanage to update all other drivers.
As of right now all of my rackmount servers are up to date, and I'm starting on the blades.
JM_DK
3 Posts
0
May 31st, 2015 11:00
Hi everyone
Hope this thread is still live
I'm having a similar issue. I have had to manually update all my firmware as I cannot get the software to download using OME. Same isues as already mentioned running idrac 2.10.10.10 on an M620 Blade.
The blades were discovered using WSMAN, they were all showing as needing updates. I select the updates to install. I can then login to my idrac and see the jobs appear in the job queue as downloading, but every time the download fails with a RED006 error the same as mentioned previously.
I can access the folder location on OME from Idrac to copy the files for a manual firmware update.
When I browse to the file to download in IIS it automatically launches the https page and the file then starts to download after I have cleared the certificate error on the webpage. How do I force it to use http if this is a known issue?
commoncourtesy
40 Posts
1
August 21st, 2015 06:00
we had the same issue..
i just figured out that our FW was not allowing the port to/from..
remember that it needs to be opened for the network that the iDRAC is on to the IP of the OME server..
the OS ip range is not the same unless they are on the same network..
for my setup, the iDRAC is an isolated network.
Brain Mc
1 Message
0
May 16th, 2019 08:00