I've started getting this error in my 3.4.0 installation. I upgraded to 3.6.1.6, and after clearing my cache finally got all my devices and UI buttons to show up correctly. Tried another update: same exact error. This used to work just fine, and I haven't changed anything in my environment!
idracs being talked to are v9.
OME VM has 16GB ram. I've restarted it post-upgrade, too.
On the drac side, I can see the job appear, say "downloading", and then give a RED016 error. This takes about 3 minutes.
Firmware compliance upgrade job messages:
Messages:
Running
Starting communication with the device.
Checking LC-Service state
Checking Remote Services availability
Remote Service is ready.
Initiated Update Job for DCIM:INSTALLED#741__BIOS.Setup.1-1 with JobId (JID_248191728294)
So if I understood correctly in your message. You had this error on version 3.4.0 and when updating and clearing the cache you got all the devices and UI buttons to show up correctly. Is that correct? In which version is OME now? I have seen this RED016 error related to firewall issues. Can you check this also? Can you please check Network settings?
-Selective firmware update: yep, ran into problem with just idrac update (wound up doing that one manually), and then again with just BIOS update. This was after an 'all' also failed.
-Restart Services in text UI: yep, no difference
-Deleted device, re-discovered, tried again: same error.
I'm currently on 3.6.1 (build 6), still with the same problem, after experiencing it on 3.4.0.
Network settings seem fine: in the GUI, under Application Settings->Network->Current Settings it doesn't show a DNS domain name or FQDN, but it des show the correct (static) IP, netmask, gateway, dns servers. In the text UI, under "Set Appliance Hostname", I have set the FQDN, but it doesn't show up in the GUI anywhere. I do have a reverse PTR set up and everything.
There is no separate firewall between the OME VM and the drac interfaces. They are on different subnets, but those subnets are clearly able to communicate with each other
I am sorry you faced with this issue. May I please ask you, did you try troubleshooting steps, which were provided above? Also could you please share which version ofiDRAC is installed?
Could you please also share the error message you received? I would like to make a research and this information will be useful.
I tried the various troubleshooting steps -- I had the problem on V3.7, upgraded to V3.8 thinking that would resolve it as I have seen it improve for a couple of instances after the upgrade. In the case I'm working with today, the upgrade failed to improve on the situation. The systems involved are FC640 servers in FX2 chassis. I have 2 FX2's and 5 FC640s spread between them -- all 5 are exhibiting this problem.
If those don't help you may need to contact support and open a case. They may have you enable debug logging from the text user interface, produce the error and collect logs.
DELL-Charles R
Social Media and Communities Professional Dell Technologies | Enterprise Support Services #IWork4Dell
Did I answer your query? Please click on ‘Accept as Solution’. ‘Thumbs up’ the posts you like!
DELL-Young E
Moderator
•
5421 Posts
•
37 Points
4408
0
Posted June 27th, 2021 21:00
Hi,
Have tried following troubleshooting:
Restart iDRAC
Restart OMEnt Appliance
Selective of Firmware update rather than just running all
Delete Server and Rediscover/Reinventory.
If the above doesn’t work, you could refer to this old post:
Another alternative to a re-deploy _may_ be the "Restart Services" option from the Text User Interface (TUI, on the console window).
https://dell.to/3jgr9z3
Social Media and Communities Professional
Dell Technologies | Enterprise Support Services
#IWork4Dell
Did I answer your query? Please click on ‘Mark as Accepted Answer’. ‘Thumbs up’ the posts you like!