You can perform an iDRAC reset using the sample racadm reset task under Remote tasks in OME. Right Click and clone the task, then right click and edit on the cloned task and provide the task target.
Also, when you launch iDRAC console, you can see the option to reset idrac on the right hand side under Quick Launch tasks.
If you try running this following command, you will be able to see the job lists in queue on the iDRAC. Do you see anything which says state as job pending?
Note : Giving JID_CLEARALL for Job ID will delete all the queued jobs. To delete a particular job, give the job ID of that particular job.
Once the job ids are clear, please do idrac reset, NOTE: do not perform factory reset, just do a reset. Try re-running the system update task. You can do that by right click the already created system update task in OME 1.2.
Can you please confirm the LC version on the server?
One more thing which you can try:
Reboot the server and press F10 to enter the system services. Once entered, save and exit. This helps LC to mount the new packages on the LC. Please try this and then create the system update task. I hope this helps.
I am having the exact same issue. My LC rev is 1.6.0.73 (R710), BIOS 6.3.0, Firmware 1.95 (Build 05). When I run the job stats check I get back the same results even after I do a iDRAC reset and reboot into the LC (F10) and exit.
The winrm command "winrm e cimv2/root/dcim/DCIM_LifecycleJob -u: -p: -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -SkipRevocationCheck -auth:basic -encoding:utf-8" should be run while the update is tried from OME to get to the root of exact issue.
So, when you start the update tasks from OME, immediately run the winrm command on the target iDRAC to see if the required jobs are created in the life cycle controller. You may have to run the command multiple times in a gap of few seconds to ensure you capture all the jobs created. Once you have these details, please post it here so that we can know the reason for failure.
1. What is the OS version on which OME is running ?
2. What's the winrm version on your OME system ? Is it 2.0 ? You can check following link to find out your "winrm" version.
"
3. Also, can you please attach a screenshot of the comparison report generated in OME for the target iDRAC. The comparison report can be checked in "Select Updates to Apply" section under "Non-Compliant Systems" tab in System Update portal.
You can select the specific server/iDRAC to see the report for individual targets.
To be sure, did you run the "winrm" command multiple times after the update task was started in OME ? As I mentioned in earlier post, you may have to run the "winrm" multiple times in a gap of few seconds, after the update is started in OME. This will ensure capturing of all the jobs in Life cycle controller.
DELL-Pupul M
2 Intern
•
1K Posts
0
July 25th, 2013 06:00
Hi Stefan,
You can perform an iDRAC reset using the sample racadm reset task under Remote tasks in OME. Right Click and clone the task, then right click and edit on the cloned task and provide the task target.
Also, when you launch iDRAC console, you can see the option to reset idrac on the right hand side under Quick Launch tasks.
DELL-Pupul M
2 Intern
•
1K Posts
0
July 25th, 2013 06:00
Hi Stefan,
If you try running this following command, you will be able to see the job lists in queue on the iDRAC. Do you see anything which says state as job pending?
winrm e cimv2/root/dcim/DCIM_LifecycleJob -u: -p: -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -SkipRevocationCheck -auth:basic -encoding:utf-8
If there are pending jobs, please clear the queue by running this command:
winrm invoke DeleteJobQueue cimv2/root/dcim/DCIM_JobService?CreationClassName=DCIM_JobService+Name=JobService+SystemName=Idrac+SystemCreationClassName=DCIM_ComputerSystem @{JobID="JID_ "} -u: -p: -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -auth:basic -encoding:utf-8
Note : Giving JID_CLEARALL for Job ID will delete all the queued jobs. To delete a particular job, give the job ID of that particular job.
Once the job ids are clear, please do idrac reset, NOTE: do not perform factory reset, just do a reset. Try re-running the system update task. You can do that by right click the already created system update task in OME 1.2.
Let us know if this helps.
Stefan Feneberg
23 Posts
0
July 25th, 2013 06:00
Hi Pupul,
Sorry for the stupid question: Where can I do the iDRAC reset?
Thanks,
Stefan
DELL-Pupul M
2 Intern
•
1K Posts
0
July 25th, 2013 07:00
So, does the output of the command which i suggested shows that there are no pending jobs in the queue?
Stefan Feneberg
23 Posts
0
July 25th, 2013 07:00
Found it! But still no improvement, the "Software Update Task Failed".
Stefan Feneberg
23 Posts
0
July 25th, 2013 07:00
It still shows the clearing command:
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = CLEARALL
PercentComplete = 0
Stefan Feneberg
23 Posts
0
July 25th, 2013 07:00
Hi Pupul,
The LC Version is 1.5.5.27 (A00). Accessed system Services, rebooted and reconfigured the update task, but still the same error!
Best regards,
Stefan
DELL-Pupul M
2 Intern
•
1K Posts
0
July 25th, 2013 07:00
Hi Stefan,
Can you please confirm the LC version on the server?
One more thing which you can try:
Reboot the server and press F10 to enter the system services. Once entered, save and exit. This helps LC to mount the new packages on the LC. Please try this and then create the system update task. I hope this helps.
Ron Valkenburg
1 Rookie
•
53 Posts
0
July 25th, 2013 09:00
I am having the exact same issue. My LC rev is 1.6.0.73 (R710), BIOS 6.3.0, Firmware 1.95 (Build 05). When I run the job stats check I get back the same results even after I do a iDRAC reset and reboot into the LC (F10) and exit.
DCIM_LifecycleJob
InstanceID = JID_CLEARALL
JobStartTime = TIME_NA
JobStatus = Pending
JobUntilTime = TIME_NA
Message = NA
MessageID = NA
Name = CLEARALL
PercentComplete = 0
Stefan Feneberg
23 Posts
0
July 26th, 2013 00:00
Glad that I'm not the only one with that problem! Potentially a bug?
Have a nice Weekend!
Stefan
cyberg
1 Message
0
July 26th, 2013 01:00
I have the same problem here. M610, LC 1.6.0.73, BIOS 6.3.0, iDRAC6 3.50
Stefan Feneberg
23 Posts
0
August 5th, 2013 01:00
Any statement by somebody at Dell? Seems to be a problem that occurs not only in my environment.
Best regards,
Stefan
DELL-Ashish S
34 Posts
0
August 5th, 2013 01:00
Hi Stefen,
The winrm command "winrm e cimv2/root/dcim/DCIM_LifecycleJob -u: -p: -r:https:// /wsman:443 -SkipCNCheck -SkipCACheck -SkipRevocationCheck -auth:basic -encoding:utf-8" should be run while the update is tried from OME to get to the root of exact issue.
So, when you start the update tasks from OME, immediately run the winrm command on the target iDRAC to see if the required jobs are created in the life cycle controller. You may have to run the command multiple times in a gap of few seconds to ensure you capture all the jobs created. Once you have these details, please post it here so that we can know the reason for failure.
Thanks,
Ashish
DELL-Ashish S
34 Posts
0
August 6th, 2013 01:00
Hi Stefen,
Few more things to check:
1. What is the OS version on which OME is running ?
2. What's the winrm version on your OME system ? Is it 2.0 ? You can check following link to find out your "winrm" version.
"
3. Also, can you please attach a screenshot of the comparison report generated in OME for the target iDRAC. The comparison report can be checked in "Select Updates to Apply" section under "Non-Compliant Systems" tab in System Update portal.
You can select the specific server/iDRAC to see the report for individual targets.
Thanks,
Ashish
DELL-Ashish S
34 Posts
0
August 6th, 2013 01:00
Hi Stefen,
Thanks for trying this out !
To be sure, did you run the "winrm" command multiple times after the update task was started in OME ? As I mentioned in earlier post, you may have to run the "winrm" multiple times in a gap of few seconds, after the update is started in OME. This will ensure capturing of all the jobs in Life cycle controller.
Let me know if you need further help.
Thanks,
Ashish