Unsolved
This post is more than 5 years old
1 Message
0
1424
wsman calls to change boot to be pxe as #0 position fail at job time
Hi. Stuck. Need help!
I run this:
wsman invoke -a ChangeBootOrderByInstanceID 'http://schemas.dell.com/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_BootConfigSetting?InstanceID="UEFI"' -h 10.x.19.66 -P 443 -V -v -c dummy.cert -u "RmAdm" -p "Hin" -y basic -k "Source=UEFI:BIOS.Setup.1-1#UefiBootSeq#NIC.PxeDevice.1-1#81e55d13a36bc065ca3bf9bf8d699391"
and it is successful. If I retrieve the DCIM_BootSourceSettings, it shows that PXE is pending to be #0 in the boot sequence and the RAID disk is pending for #1 slot....
I then run this:
Result: wsman invoke -a CreateTargetedConfigJob 'http://schemas.dell.com/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_iDRACCardService?SystemCreationClassName="DCIM_ComputerSystem",SystemName="DCIM:ComputerSystem",CreationClassName="DCIM_iDRACCardService",Name="DCIM:iDRACCardService"' -h 10.x.19.66 -P 443 -V -v -c dummy .cert -u "RmAdm" -p "Hin" -y basic -k "Target=iDRAC.Embedded.1" -k "ScheduledStartTime=TIME_NOW"
And the output says “No pending configurations” yet when I go to the UI, to logs, to Life Cycle Logs and find the job, I find an entry:
“Unable to run the (installation or configuration) job JID_.... because Unable to Commit Configuration.”
And the pending settings are reverted back – nothing changed. And no other info to be found! HELP! So what am I trying to do? Create a call that changes the boot to PXE is first option (#0) to be used in out drp automation.
Jim.
There are no words how happy I'd be for hints on what I am missing, why it can't commit.
DELL-Daniel My
Moderator
Moderator
•
6.2K Posts
0
February 26th, 2018 17:00
Hello
Please send a private message with your service tag to ensure we have all appropriate information on your system.
Thanks