Dell R710 – Keyboard not working in iDRAC Console

TL;DR:– Check the USB drivers in windows, if the iDRAC remote console Keyboard doesn’t work.


A frustrating few weeks of troubleshooting a flaky server without the use of a working iDRAC remote console left me determined to find out why my iDRAC consoles for my R710 servers were not working.

I read everything there is to read about iDRAC eccentricities on google. I pulled apart Vlans, Java, firewalls, BIOS settings, adding exceptions here, there, and everywhere, to no avail. And I gave up on it, an emotional wreck, defeated, vanquished.

Then, I recently added a 3rd R710 to the site, and lo and behold the iDRAC was fully functional. Now I knew it wasn’t a site issue, and was even more determined to find out what was going on …………….

Rising up, back on the street
Did my time, took my chances
Went the distance, now I’m back on my feet
Just a man and his will to survive

 

I then discovered the Keyboard and mouse worked fine for the BIOS screens (how I didn’t spot this before I don’t know). So it must be something with Windows……

……..so right at the bottom of Device manager were 4 USB controllers with Yellow triangles! It seems that a recent Dell SUU installed bad Intel Drivers for these controllers (a bad .inf file I think). Switching the driver for the affected devices back to the Microsoft ones, immediately fixed the Keyboard and mouse in the iDRAC Remote Consoles!

 

Not once did I see this suggested anywhere when searching – so I’m posting it here where nobody will find it.

 

It’s the eye of the tiger
It’s the thrill of the fight
Rising up to the challenge of our rival
And the last known survivor
Stalks his prey in the night
And he’s watching us all with the eye of the tiger

 

Advertisements
Dell R710 – Keyboard not working in iDRAC Console

Note to self – Hyper-V Replication Certificates

After quite a bit of frustration (lots of 0x00002f8f errors) with attempts to get Certificate based Hyper-V replication to work, the below should configure Self-Signed certs to work for Hyper-V. You will need Makecert.exe  – Google it, it is obtainable as part of the Windows software development kit I think.

1-Create CA Cert on Source replication server

2-Create Client Cert on Source replication server

3-Add Cert to Hyper-V Replication settings.

4-Export Client cert as PFX

5-Install PFX on Destination Server

Repeat steps above  if replication is going to go the other way also (it will be most likely)

 

1-Create CA Cert

makecert.exe -pe -n “CN=MyLocalCA” -ss root -sr LocalMachine -sky signature -r “MyLocalCA.cer”

2-Create Client Cert (2 examples)

makecert.exe -pe -n “CN= RepBkr01.lab.local” -ss my -sr LocalMachine -sky exchange -eku 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2 -in “MyLocalCA” -is root -ir LocalMachine -sp “Microsoft RSA SChannel Cryptographic Provider” -sy 12 RepBkr01.lab.local.cer

makecert.exe -pe -n “CN=RepBkr02.lab.local” -ss my -sr LocalMachine -sky exchange -eku 1.3.6.1.5.5.7.3.1,1.3.6.1.5.5.7.3.2 -in “MyLocalCA” -is root -ir LocalMachine -sp “Microsoft RSA SChannel Cryptographic Provider” -sy 12 RepBkr02.lab.local.cer

3-Hyper-V manager-> “Hyper-V Settings” -> “Replication Configuration”-> “Select Certificate” -> Select the cert just created.

4-Go to Certificate manager (mmc.exe -> add snapin Certificate manager) and export the Client Cert from personal store to disk (inc Private key, + extended properties), copy to Destination server.

5-On Destination server, double click on Cert and install for Local machine.

You Should now be able to enable replication using these certificates.

Troubleshooting

Makecert.exe gives “Fail to acquire a security provider from the issuer’s certificate” – why?

Because the first command to create MyLocalCA below has not be run on the host you are trying create a Client cert on..

RUN BOTH CA and Client Cert commands on a Source host.

 

You May also have to disable the Cert Revocation check for the Cert if Hyper-V complains, if so add these to your Registry

reg add “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\FailoverReplication” /v DisableCertRevocationCheck /d 1 /t REG_DWORD /f
reg add “HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Virtualization\Replication” /v DisableCertRevocationCheck /d 1 /t REG_DWORD /f

Note to self – Hyper-V Replication Certificates

Backup and.. uh.. Forwardups

I needed to make a list of these because I’m forever looking them up – I thought I’d share.

https://helpcenter.veeam.com/backup/vsphere/backup_methods.html

Forever Forward (1x I/O on target)

12

 

Forward Incremental w/Synthetic Full

2x I/O on target (read + write for each block)

345

 

Forward Incremental w/Active Full

(Full created from Source) (1x I/O on target)

6

 

Forward Incremental, Transforming to Reverse incremental Chains per backup

4x I/O on target (read + write + read + write for each block

7

 

Reverse Incremental –

3x I/O on target (write + read + write for each changed block)

89

Backup and.. uh.. Forwardups