Unsolved
This post is more than 5 years old
2 Intern
•
615 Posts
0
35098
March 4th, 2013 16:00
OME does not see latest BIOS update available
I have an R710 that has an old BIOS at 2.0.13.
Dell site lists 6.3.0 as latest available for this chssis.
My OME catalog is listed as latest available at PDFW2 from 2/21/2013
When selecting this server under non-compliant systems the BIOS update is not listed. Only a Broadcom firmware update is listed for this chassis.
Why is the new BIOS update not listed? How do I know if other updates are missing as well?
How do I get OME to recognize the missing update so I can use OME to apply this BIOS update?
0 events found
No Events found!


DELL-Raj S
327 Posts
0
March 11th, 2013 10:00
cameron,
With 11G servers (iDRAC6), some of the updates may not show up depending on the installed iDRAC6 and LifeCycle Controller firmware version.
Please review this document:
en.community.dell.com/.../how-to-resolve-errors-when-updating-firmware-via-wsman-in-idrac-with-lifecycle-controller.aspx
Bit more info on this:
******
You need to upgrade to the following firmware versions *first* before updating any other components. This is due to some changes in the certificates on the update package.
• iDRAC6/LC Firmware Release Information
o Rack/Tower (monolithic) – v 1.85
o Blades (modular) – v3.35
• LC 1.5.2
Thanks,
Raj Shresta
cameronredux
2 Intern
•
615 Posts
0
March 11th, 2013 11:00
Thanks Raj,
Your link documentation seems out of date. The latest iDRAC6 monolithic firmware is 1.95
All my iDRAC6 are at the 1.95 iDRAC6 firmware version but some have out of date LC firmware so it looks like I have some work to do :)
I have a question about how OME handles multiple firmware updates simultaneously.
When a server is listed in non-compliant in OME and I select all available updates and then click to apply the updates will OME update them in the correct order so BIOS and LC get done before the rest?
DELL-Raj S
327 Posts
0
March 11th, 2013 16:00
Regarding the documentation, I was not sure what level iDRAC 6 was at ? If it is at 1.95, then please ignore that document. It is applicable to older iDRAC6 firmware version.
DELL-Raj S
327 Posts
0
March 11th, 2013 16:00
cameron,
For this R710 server, what does the software inventory show up in the Details section ("Manage -> Devices -> All Devices" tree) ? Does it list BIOS ?
Can you also check if CSIOR (Collect System Inventory On Restart) feature is enabled on R710 iDRAC6 ? You can run this winrm command from OME server command prompt:
winrm g schemas.dmtf.org/.../DCIM_LCEnumeration -u:Username -p:Password -r:https:// /wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic
Sample output:
DCIM_LCEnumeration
AttributeName = Collect System Inventory on Restart
Caption = null
CurrentValue = Enabled
DefaultValue = Disabled
Description = null
ElementName = LC.emb.1
InstanceID = DCIM_LCEnumeration:CCR5
IsOrderedList = null
IsReadOnly = false
PendingValue = null
PossibleValues = Enabled, Disabled
PossibleValuesDescription = null
Thanks,
Raj Shresta
cameronredux
2 Intern
•
615 Posts
0
March 12th, 2013 12:00
So it looks like CSIOR is a Lifecycle Controller setting not a DRAC setting. It also looks like this setting can be set to enabled or disabled using WS-Man but the LC PDF does not give instructions on how to do that :(
Can you please instruct on how to find out what the setting is set to and then instruct on how to mofify the setting? I know how to do this by rebooting the server and modfying the entry at that time. I am looking to do this without rebooting via CLI command (remote or local) so the production server is ready for next reboot if a change is needed. Is there a racadm command to do this?
cameronredux
2 Intern
•
615 Posts
0
March 12th, 2013 12:00
The device shows the following software info in OME
The only available updates for this device when selected under non-compliant systems are:
SO you can see that the BIOS is out of date but the new BIOS firmware update is not showing!
Where is the CSIOR (Collect System Inventory On Restart) feature on the DRAC? I have never seen this option.
The output of the code you requested I run is as follows:
C:\Users\ome>winrm g schemas.dmtf.org/.../DCIM_LCEnumeration -u:REMOVED -p:REMOVED -r:https://REMOVED/wsman -SkipCNcheck -SkipCAcheck -encoding:u tf-8 -a:basic Fault Code Value = s:Sender Subcode Value = wsa:DestinationUnreachable Reason Text = No route can be determined to reach the destination role defined by the WS-Addressing To. Detail FaultDetail = http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/Inv alidResourceURI Error number: -2144108485 0x8033803B The WS-Management service cannot process the request. The resource URI is missin g or it has an incorrect format. Check the documentation or use the following co mmand for information on how to construct a resource URI: "winrm help uris".
When using the troubleshooting tool from ome server for ws-man to that same IP it retuns successfully the folllowing:
WSMAN Connected. WSMAN profiles found on the remote device are: 1. OS Deployment 2. Software Inventory 3. Software Update 4. Job Control 5. LC Management 6. Persistent Storage 7. Simple NIC 8. Simple FC 9. BIOS and Boot Management 10. Simple RAID 11. Fan 12. Power Supply 13. iDRAC Card 14. Memory 15. CPU 16. System Info 17. PCI Device 18. Video 19. Base Server 20. Service Processor 21. SM CLP Admin Domain 22. Power State Management 23. Active Directory Client 24. Simple Identity Management 25. Role Based Authorization 26. Record Log 27. DHCP Client 28. DNS Client 29. Ethernet Port 30. Ethernet Port 31. IP Interface 32. Power Supply 33. Command Line Protocol Service 34. Physical Asset 35. Base Metrics 36. Virtual Media 37. USB Redirection 38. Power Utilization 39. SMASH Collections
cameronredux
2 Intern
•
615 Posts
0
March 12th, 2013 12:00
DELL-Raj S
327 Posts
0
March 13th, 2013 13:00
For some reason any content w/ http is being masked by this web-site. You need to replace "schemas.dmtf.org/.../DCIM_LCService" with "://schemas.dmtf.org/wbem/wscim/1/cim-schema/2/root/dcim/DCIM_LCService". Add http prior to "://schemas...".
After enabling CSIOR, the server will need to be rebooted for it to take effect.
DELL-Raj S
327 Posts
0
March 13th, 2013 13:00
Couple of things to try:
In OME console, under Manage -> System Updates -> Advanced Settings, select "Enable Downgrades". Wait for 10 minutes and then select "Disable Downgrades". This will update the compliance report. Check if any newer updates show up.
Running WSMAN command is a long and tedious process. I will try to explain it here:
At first, run this command from OME Server (OS command prompt) to verify if the "CurrentValue" for the "AttributeName = Collect System Inventory on Restart" is set to Disabled.
winrm e cimv2/root/dcim/DCIM_LCEnumeration -u:USERNAME -p:PASSWORD -r:https://IPAddress/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic
Create a windows batch (.bat) file and include this command:
winrm i SetAttribute schemas.dmtf.org/.../DCIM_LCService -u:%2 -p:%3 -r:https://%1/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic -file:set_CSIOR_enable.xml
Create a set_CSIOR_enable.xml file and add this text:
schemas.dmtf.org/.../DCIM_LCService">
Collect System Inventory on Restart
// test comments
Enabled
// test comments
#Enabled,Disabled
Make sure the batch script and XML file are in the same directory. Invoke the above batch file and pass in IPAddress, Username and Password:
Ex: BatchFile.bat 10.1.1.1 root calvin
Create another windows batch (.bat) file and include this command:
winrm i CreateConfigJob schemas.dmtf.org/.../DCIM_LCService -u:%2 -p:%3 -r:https://%1/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic -file:job.xml
Create a job.xml file and add this text:
schemas.dmtf.org/.../DCIM_LCService">
Part Configuration Update
Invoke the batch file and pass in IPAddress, Username and Password:
Ex: BatchFile2.bat 10.1.1.1 root calvin
Run this command to verify if the "CurrentValue" for the "AttributeName = Collect System Inventory on Restart" is set to Enabled now.
winrm e cimv2/root/dcim/DCIM_LCEnumeration -u:USERNAME -p:PASSWORD -r:https://IPAddress/wsman -SkipCNcheck -SkipCAcheck -encoding:utf-8 -a:basic
Delete the device from OME and re-run discovery+inventory on the discovery range. Check if the software inventory info is updated.
shakman9999
1 Message
0
February 11th, 2014 08:00
Sorry for the necro-post.
I'm trying to use this process to enable CSIOR on all my M610 blades. They've moved around quite a bit, and OME is not putting the correct blades with the correct chassis.
The schemas.dtmf.org URL you specify above is no longer valid. Can you please update this thread with the correct URL or another location where I can pull this schema?
Thanks.