iDRAC 9 version 6.10.00.00 400 Bad Request error

A typo in previous post, the old iDRAC version is 6.00.02.00 not 6.02.00.00.

Di

Hello this may help: https://dell.to/3jjZ1h0

Hello,

Unfortunately the knowledge base article https://www.dell.com/support/kbdoc/en-ca/000193619/http-https-fqdn-connection-failures-on-idrac9-firmware-version-5-10-00-00?dgc=SM&cid=376139&lid=spr8799951350&refid=sm_LITHIUM_spr8799951350&linkId=199564916  doesn't help. Before when we updated to 5.10.00.00, we met the same issue and this knowledge base article helped. However this time with 6.10.00.00, it seems different as I mentioned in my first post.

Di

Hello Charles,

Yes, I have reset the DRAC for many times in order to debug the issue and check the results of different configurations. The resets were done by racadm command line since we can still access with ssh.

The server mode is PowerEdge C6420, from download pages, the version 6.10.30.00 is still not available for me to download. When it is available, I definitely will try this version.

Thanks,

Di

Hello Di Qing,

Have you reset the DRAC and check results?

How to Reset the Integrated Dell Remote Access Controller (iDRAC)

https://dell.to/3DDJ0Jz

You may also try a flea power drain:

drain flea power (shut down, disconnect power cables and Network cables, hold in power button 20 seconds with cords removed).  After flea power drain, system has to set for 3 minutes for DRAC to reset without any power plugged in, then plug in NIC and power but wait 2 minutes before power on to give DRAC time to initialize.

Would you let us know your server model?  I see an iDRAC9 firmware 6.10.30.00 update but I don't know if it is for your model.

Can you share the FQDN used to access iDRAC and output of "racadm get idrac.webserver" command

The FQDN is "wns0054-drac.devices.t1", and the output of "racadm get idrac.webserver":

racadm>>get idrac.webserver
[Key=idrac.Embedded.1#WebServer.1]
BlockHTTPPort=Disabled
CustomCipherString=
Enable=Enabled
HostHeaderCheck=Enabled
Http2Enable=Disabled
HttpPort=80
HttpsPort=443
HttpsRedirection=Disabled
ManualDNSEntry=wns0054-drac,wns0054-drac.devices.t1
#MaxNumberOfSessions=8
SSLEncryptionBitLength=128-Bit or higher
Timeout=1800
TitleBarOption=Auto
TitleBarOptionCustom=
TLSProtocol=TLS 1.1 and Higher

As you can see, it's some internal domain name used here.

Thanks,

Di

I can confirm that we have the same issue as Di.

In the past, we have used the idrac.webserver.ManualDNSEntry workaround method described above (https://www.dell.com/support/kbdoc/en-ca/000193619/http-https-fqdn-connection-failures-on-idrac9-firmware-version-5-10-00-00?dgc=SM&cid=376139&lid=spr8799951350&refid=sm_LITHIUM_spr8799951350&linkId=199564916) for many of our Poweredge R640 and R650 servers running idrac firmware version 5.100 and above until 6.00.2.00, and it has always worked fine.

Now, after updating a new R650 server to idrac firmware 6.10.00, setting the ManualDNSEntry value does not work and returns the 400 Bad Request Error.

Hello, does this happen to a certain system only or to all? 

Hello,

I got the same issue on 2 servers, both R740XD and both with Windows Server 2016

1. server from 4.10.0 to 6.10.00
2. server from 5.10.1 to 6.10.00

Solved !

With SSH connect to your idrac :

racadm set idrac.webserver.HostHeaderCheck 0

For my 14th gen, go to the iDRAC's webgui > iDRAC Settings > Connectivity > Network > Common Settings and:

Set Register iDRAC on DNS to Enabled

Set the "DNS iDRAC Name" to the actual DNS hostname for the iDRAC

Add your domain to the "Static DNS Domain Name"

racadm way :

racadm set iDRAC.NIC.DNSRacName iDRACNAME

racadm set iDRAC.NIC.DNSDomainName DOMAIN.NAME

When that "DNS iDRAC Name" does not match the name used in the URL, the login will barf.

In our case, if set idrac.webserver.HostHeaderCheck to 0, I could not open the virtual console viewer from the iDRAC web interface though the secure web access did not fail.

Hello, there's no known issue with this version internally so far (refering to your comment "It looks like to me a new bug in version 6.10.00.00." ) What I'd suggest is you can try to use another version and see if the issue persists.