Unsolved
8 Posts
0
9965
December 14th, 2021 14:00
"Internal Server Error" after upgrading to iDRAC9 to 5.10.00.00
some servers take it, some don't. I see about 50% success rate.
thankfully, racadm shell works. so, the solution is to rollback.
ssh root@ -p22
racadm rollback iDRAC.Embedded.1-1
probably good to stick to 5.00.10.20 for now.
No Events found!
ben.rosenqvist
1 Rookie
•
10 Posts
0
December 15th, 2021 02:00
I just updated a single server. Now throws the below error while accessing using FQDN, IP works. Rolling back
Bad Request
Your browser sent a request that this server could not understand.
Additionally, a 400 Bad Request error was encountered while trying to use an ErrorDocument to handle the request.
jabuzz
1 Rookie
•
31 Posts
0
December 16th, 2021 01:00
Note if you go into the iDRAC and set it's hostname to match the DNS and then user the FQDN to access the iDRAC it works. By default the hostname is "idrac- " and for some reason Dell decided to break https access unless that matched the name registered in the DNS.
TheOldSoul
4 Posts
3
January 14th, 2022 03:00
Okay, that there is a mismatch between the configured DNS name and the actual used hostname is not well handled by the iDRAC. To work around that, fix the hostname in the UI or perform one of the two commands with the racadm tool. They both work on their own, it's just what you prefer.
Or
FBBen
13 Posts
0
January 21st, 2022 09:00
We ran in to this as well and engaged support. Dell has a KB article with the options to resolve this. If the FQDN for your iDRAC is internal you will likely have to use "iDRAC.WebServer.ManualDNSEntry". This is what we had to do to stay on 5.10.00.00.
HTTP/HTTPS FQDN Connection Failures On iDRAC9 firmware version 5.10.00.00 | Dell US
We are still working with Dell to see if we can use iDRAC.NIC.DNSRacName and iDRAC.NIC.DNSDomainName instead (It rejects our internal FQDN). I'll update when I hear back.
_Joren_
5 Posts
1
February 9th, 2022 05:00
This can be fixed by browsing to the ip address of the iDrac.
Then go to the ''iDrac settings'' tab then click 'Configure Network Settings'' at the right top corner. Open the "Common settings" dropdown and for "Static DNS Domain Name" set your full domain.
Example you want to reach idrac from following address: https://myidrac.sub.domain.com then "Static DNS Domain Name" needs to be: sub.domain.com
Then the webinterface works again after changing this for the DNS name and not only on ip address.
In my case I had issues sending alert mails changing the domain name setting as from this moment iDrac was trying to send from idrac@sub.domain.com which our mail relay server could not handle. I fixed that by going to the ''iDrac settings'' tab and clicking "SMTP(email) settings" and for "Sender Email Address" I set a custom mail adres like idrac@domain.com