ProLiant Servers (ML,DL,SL)
1819878 Members
2672 Online
109607 Solutions
New Discussion юеВ

DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

 
SOLVED
Go to solution
cjcrosb
Visitor

DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

We are not able to get the keyboard input to work with the HTML5 remote console in iLO5. Running System ROM A42 v2.80, and iLO Firmware Version 2.96 Aug 17 2023. Other systems are working fine. Doesn't matter if we use the integrated remote console, or pop out window. No errors. Using latest Chrome browser from Linux OS (CentOS 7 in this case). Host OS is RHEL 9.3. iLO Avanced license is installed. This works perfectly fine with the following installed OS's: RHEL 7.9, RHEL 8.9, Rocky 9.3. Any thoughts?

5 REPLIES 5
Vinky_99
Esteemed Contributor

Re: DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

@cjcrosb 

Good day! 

When dealing with issues related to iLO (Integrated Lights-Out) and HTML5 remote console keyboard input not working, there are several steps you can take to troubleshoot and resolve the problem.

Here are some suggestions:

>> Ensure that you are using a supported browser. iLO5 typically supports modern browsers like Google Chrome, Mozilla Firefox, Microsoft Edge, and Safari. Make sure your Chrome browser is up to date.

>>Disable any browser extensions or add-ons, as they may interfere with the functionality of the HTML5 remote console. Try accessing iLO5 in incognito mode or with all extensions disabled.

>> Verify that Java is not interfering with the HTML5 console. Some systems may have Java installed, and it might be conflicting with the HTML5 functionality.

>> Clear your browser cache and cookies. Sometimes, cached data may cause unexpected behavior. After clearing the cache, restart the browser and try again.

>> In iLO settings, check if there is an option to enable or disable Java Console Compatibility Mode. Toggle this setting and see if it resolves the issue.

>> While your firmware versions seem relatively recent, check for any new firmware updates released by the server manufacturer. Sometimes, firmware updates address compatibility issues.

>> Ensure that the keyboard layout and language settings on your local machine match the settings of the server. Mismatched settings can lead to keyboard input issues.

>> Check if there are any network or firewall settings that might be blocking the keyboard input. Ensure that the necessary ports for iLO communication are open.

>> Confirm that your CentOS 7 and RHEL 9.3 systems are fully updated. OS updates may include fixes or improvements related to remote console functionality.
Contact Support:

By systematically going through these steps, you should be able to identify and address the root cause of the keyboard input issue with the iLO5 HTML5 remote console.

If the issue persists, consider reaching out to the HPE support for further assistance.

Good luck!

Let me know how it goes...

These are my opinions so use it at your own risk.
TVVJ
HPE Pro

Re: DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

Hello,

You may try iLO reboot (reset) and see if it helps.

If the above is unsuccessful, then try iLO factory default reset.

Regards,



I work at HPE
HPE Support Center offers support for your HPE services and products when and how you need it. Get started with HPE Support Center today.
[All opinions expressed here are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
cjcrosb
Visitor

Re: DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

>> Ensure that you are using a supported browser. iLO5 typically supports modern browsers like Google Chrome, Mozilla Firefox, Microsoft Edge, and Safari. Make sure your Chrome browser is up to date.

   Latest version of Chrome.

>>Disable any browser extensions or add-ons, as they may interfere with the functionality of the HTML5 remote console. Try accessing iLO5 in incognito mode or with all extensions disabled.

   No browser extensions.

>> Verify that Java is not interfering with the HTML5 console. Some systems may have Java installed, and it might be conflicting with the HTML5 functionality.

   No java on this system.

>> Clear your browser cache and cookies. Sometimes, cached data may cause unexpected behavior. After clearing the cache, restart the browser and try again.

   No dice.

>> In iLO settings, check if there is an option to enable or disable Java Console Compatibility Mode. Toggle this setting and see if it resolves the issue.

   Could not find this setting.

>> While your firmware versions seem relatively recent, check for any new firmware updates released by the server manufacturer. Sometimes, firmware updates address compatibility issues.

   Latest firmware.

>> Ensure that the keyboard layout and language settings on your local machine match the settings of the server. Mismatched settings can lead to keyboard input issues.

   Set correctly.

>> Check if there are any network or firewall settings that might be blocking the keyboard input. Ensure that the necessary ports for iLO communication are open.

   No issues.

>> Confirm that your CentOS 7 and RHEL 9.3 systems are fully updated. OS updates may include fixes or improvements related to remote console functionality.

   Fully up-to-date.

cjcrosb
Visitor

Re: DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

You may try iLO reboot (reset) and see if it helps.

If the above is unsuccessful, then try iLO factory default reset.

   No luck with this. Issue persists.

cjcrosb
Visitor
Solution

Re: DL385 Gen10 Plus iLO5 HTML5 Remote Console Keyboard Input Not Working

** UPDATE **

The issue appears to be with the host OS being RHEL 9.3. We have the exact same issue with another system running RHEL 9.3, same hardware, same iLO firmware. The iLO firmware (Version 2.96 Aug 17 2023) supports up through 9.2. On systems at or below 9.2, the interaction with the console works. The odd thing is that Rocky 9.3 works perfectly fine. So it appears to be a compatibility issue with RHEL. Closing this discussion. Will have to wait until next firmware release comes out, supporting RHEL 9.3, and see if that fixes the issue.