Unsolved
This post is more than 5 years old
6 Posts
0
35733
June 23rd, 2014 11:00
iDRAC 1.57.57 problem with SetAttribute(s) method
Hello, we just upgraded from 1.06.06 to 1.57.57. On version 1.06.06, we have no problems with SetAttribute.
The problem is 1.57.57 always returns with error BIOS006, Configuration job already created, cannot set attribute on specified target until existing job is completed or is cancelled.
Even after clearing the job queue and rebooting the drac, we are still getting this error. It doesn't matter if it is the first job we try to put in the queue, it still replies this way.
Any advice is appreciated, thank you.
0 events found
No Events found!
Alex_sf
6 Posts
0
June 23rd, 2014 12:00
One clarification, we CAN use SetAttribute when targeting the LifeCycle controller.
The BIOS006 error only comes when we are targeting the bios module.
mondeep
30 Posts
0
June 24th, 2014 07:00
Hi Alex_SF,
Can you please try these 2 commands -
1. winrm invoke DeleteJobQueue cimv2/root/dcim/DCIM_JobService?CreationClassName=DCIM_JobService+Name=JobService+SystemName=Idrac+SystemCreationClassName=DCIM_ComputerSystem @{JobID="JID_CLEARALL_FORCE" } -u:UN -p:PWD -r:https://idracip/wsman:443 -SkipCNCheck -SkipCACheck -auth:basic -encoding:utf-8 -skipRevocationCheck
2. winrm i GetRemoteServicesAPIStatus http://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService?SystemCreationClassName=DCIM_ComputerSystem+CreationClassName=DCIM_LCService+SystemName=DCIM:ComputerSystem+Name=DCIM:LCService -u:UN -p:PWD -r:https://idracip/wsman -SkipCNCheck -SkipCACheck -SkipRevocationCheck -encoding:utf-8 -a:basic
Keep executing cmd no 2 till GetRemoteServicesAPIStatus goes to Ready state. Now you can try the SetAttribute method. Do let us know if this fixes the issue.
Regards,
Dell-Mondeep
Alex_sf
6 Posts
0
June 25th, 2014 12:00
Thank you, but yes the job queue is clear and the drac webui reports no jobs to run.
The real problem is that this behavior persists even flashing back to the old firmware versions.
So we have a codebase that works fine with older firmware, but once we flash to new, we can no longer use setAttribute reliably, and it stays this way even after flashing back.
Someone from our company is now following up with a Dell representative to see if they can replicate this issue, thank you.