ML30 Gen 10 with Server 2019 loses keyboard on console

[F1Systems]

ML30 Gen 10 with Server 2019 loses keyboard on console.

Several times a week this newly installed Server 2019 Standard will lose keyboard input. The system is on the login screen and the mouse moves but does not click and there is no keyboard input. Rebooting the server restores the keyboard. There are no events in the log related to power, kernel., or USB. Any thoughts?

[BPSingh]

Greetings!

Are you using a KVM or an USB keyboard with the server? 
Is the issue seen with another good known keyboard as well?

Please ensure workload profile is set correctly from BIOS. High Performance Compute (HPC) for non virtualised environment and Virtualization
- Max Performance for virtualised environment.

Please refer: Applying a Workload Profile
https://support.hpe.com/hpesc/public/docDisplay?docId=a00112581en_us&docLocale=en_US&page=t_applying_WLP.html 

Also ensure server is running driver and firmware as per latest HPE Service Pack for Proliant. 

[F1Systems]

Thanks for the input. Have changed to Virtualization - Max Performance and will see how it behaves. When it becomes unresponsive it drops it’s network connection as well which would seem to rule out KVM or USB keyboard related issues, though I removed the KVM. We shall see.

[F1Systems]

Changing the Workload Profile does not seem to have helped. This issue has proved to be more than an unresponsive keyboard. Perhaps i should post this as a new question. Heres what is happening.

-------------

I have two physical servers and one Hyper-V virtual machine.

They are:
Server01 (PDC, AD, DNS, DHCP)
Server02 (PDC, AD, DNS)
RDServer (IIS, RA, RDS) This is a Hyper-V virtual hosted on Server01.

Normally have an RD session running into each server. Came in this morning and I had lost connection to Server01, the PDC, and it was unable to reconnect. The connections to Server02 and RDServer (the virtual hosted on Server01) were still up and responsive. There is no KVM used and Workload Profile is Virtualization - Max Performance.

Symptoms:

1. Cannot RD into Server01 from any machine
2. Hyper-V virtual RDServer hosted on Server01 is available and working.
3. Server01 file shares are available on the network
4. DC replication fails (repadmin /syncall)
5. Console allows username and password then goes to spinning balls.

Have waited 30 minutes for it to login before I did a hard shutdown and reboot.

Reboots normally and logs on, remote sessions reconnect.

DNS Event Log entry shortly after hard shutdown at 11:33:22 AM on ‎10/‎31/‎2022

Error ID 4013 10/31/2022 11:36:55 AM

"The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed."

There are no critical errors or warnings for about 2 days preceding this issue reoccuring.

[BPSingh]

Greetings!

Thank you for the additional information.

From the issue description, I believe we have to get this investigated both from the hardware and OS level.
Please ensure that the servers are running on the latest firmware revision (Gen10 Service Pack for ProLiant (SPP) Version 2022.09.01.00)
https://techlibrary.hpe.com/us/en/enterprise/servers/products/service_pack/spp/index.aspx#!&tab=TAB1

If the issue persists, then the Active Health System (AHS) logs will have to be analyzed to check and identify events if any related to the reported issue. Please log a support case to get this issue investigated from a hardware perspective.

[F1Systems]

Installed the Service Pack on Thursday and sometime before MMonday it became unresponsive again. 

I have opened a care on this. The repsonse from an HP tech was the same day, I was impressed.

Thanks for your help.