- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- iLO5 Remote Konsole - Tastatur ESC, F9, F10 ... fu...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 04:10 AM - last edited on 12-03-2020 03:23 AM by Parvez_Admin
12-01-2020 04:10 AM - last edited on 12-03-2020 03:23 AM by Parvez_Admin
iLO5 Remote Konsole - Tastatur ESC, F9, F10 ... funktioniert nicht bei neuem Gen10-Server/Blade
Hallo,
seit ein paar Monaten haben wir mit den Gen10-Servern gelegentlich das Problem, dass bei der Vorbereitung (im Lager), oder nachdem der Server im Rechenzentrum im Rack installiert wurde, das System nicht über die Remote Konsole bedienbar ist. Die Konsole nimmt keine Eingaben mit der Tastatur (ESC, F9, F10, F11, ...) an, um z. B. das BIOS zu konfigurieren, den Smart Storage Administrator aufzurufen, und ein Betriebssystem darauf zu installieren.
Es geht dabei (vor allem) um Rackserver der Typen DL360, DL380 oder DL560 Gen10. Bei BL460c Gen10 ist es glaube ich noch nicht aufgetreten. BIOS, iLO5 und Intelligent Provisioning sind dabei schon einigermaßen aktuell (z. B. BIOS 2.30, iLO 2.14, IP 3.30 ... 3.50), oder sollen eben jeweils mit dem SPP aktualisiert werden. Unsere Server booten gundsätzlich, spätestens nachdem BIOS u. iLO für den Produktiveinsatz konfiguriert wurden, im LEGACY-Mode (nicht mit UEFI).
Bisher half dabei wohl immer das Intelligent Provisioning Update oder Recovery (wenn die Version schon aktuell war), und evtl danach ein "Power OFF" (nicht nur der anschließende Reboot). Geht's danach immer noch nicht sofort, vielleicht noch ein Update des iLO5 auf 2.19 (die 2.3x wird bei uns wegen Problemen mit dem Script noch nicht eingesestzt), und/oder etwas warten.
Beispiel: Beim letzten Fall, mit einem DL380 Gen10, iLO 2.18, BIOS 2.32 u. IP 3.50. Das Intelligent Provisioning Recovery/Update war bereits vom Kunden bzw. einem Kollegen durchgeführt worden, Tastatur funktionierte immer noch nicht, vermutlich wurde der Server nach dem Reboot noch nicht kurz abgeschaltet. Nach einem POWER OFF durch mich wurden bei der Hardware-Initialisierung, während unten die Optionen F9 ... F12 werden, noch keine Eingaben von der Tastatur akzeptiert. Als dies durch war, und oben noch die Optionen für F9, F11 u. F12 angezeigt wurden, wechselte das System im Legacy Mode und startete in's BIOS/RBSU. Ab dann furnkioniert also die Tastatur wieder.
Weiß jemand, woran das liegt, wie man es vorab verhindern kann, oder wie man's schneller und einfacher zum laufen bekommt?
Gruß, Michael (eYc)
Google Translated
Hello,
For a few months now we have occasionally had the problem with the Gen10 servers that the system cannot be operated via the remote console during preparation (in the warehouse) or after the server has been installed in the data center in the rack. The console does not accept any entries with the keyboard (ESC, F9, F10, F11, ...) to e.g. B. to configure the BIOS, call up the Smart Storage Administrator, and install an operating system on it.
These are (mainly) rack servers of the types DL360, DL380 or DL560 Gen10. With the BL460c Gen10 I don't think it has happened yet. BIOS, iLO5 and Intelligent Provisioning are already fairly up-to-date (e.g. BIOS 2.30, iLO 2.14, IP 3.30 ... 3.50), or should be updated with the SPP. Our servers basically boot, at the latest after BIOS and iLO have been configured for productive use in LEGACY mode (not with UEFI).
So far, the Intelligent Provisioning Update or Recovery (if the version was already up to date) has always helped, and possibly a "Power OFF" afterwards (not just the subsequent reboot). If it still doesn't work immediately after that, maybe an update of the iLO5 to 2.19 (the 2.3x is not yet used because of problems with the script), and / or wait a little.
Example: In the last case, with a DL380 Gen10, iLO 2.18, BIOS 2.32 etc. IP 3.50. The Intelligent Provisioning Recovery / Update had already been carried out by the customer or a colleague, the keyboard still did not work, and the server was probably not switched off briefly after the reboot. After a POWER OFF by me, during the hardware initialization, while the options F9 ... F12 are below, no inputs from the keyboard were accepted. When this was done, and above the options for F9, F11, etc. F12 were displayed, the system switched to legacy mode and started in BIOS / RBSU. From then on the keyboard will veneer again.
Does anyone know why this is, how to prevent it in advance, or how to get it to run faster and easier?
Greetings, Michael (eYc)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2021 06:20 PM
01-05-2021 06:20 PM
Re: iLO5 Remote Konsole - Tastatur ESC, F9, F10 ... funktioniert nicht bei neuem Gen10-Server/Blade
Hi @eYc ,
Thank you for the Post.
Please refer the below links :
Let us know if these were helpful.
Thank you
Ram
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2021 08:53 PM
01-09-2021 08:53 PM
Re: iLO5 Remote Konsole - Tastatur ESC, F9, F10 ... funktioniert nicht bei neuem Gen10-Server/Blade
Hi @eYc ,
Good day!
May we please know if the links were helpful and the current status of the posted issue.
Thank you
Ram
I work for HPE.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-15-2021 03:35 AM
01-15-2021 03:35 AM
Re: iLO5 Remote Konsole - Tastatur ESC, F9, F10 ... funktioniert nicht bei neuem Gen10-Server/Blade
Hi @ksram
Thank you for your Reply, and thanks for google translation (I thought there was a german community cause of the possibility to switch language).
I read this document, but i am not sure, whether this "local software" is installed on the Server OS (screen capture software, skype, meeting, ...), or on the client where I start the remote console session. On Server there ist nothing, because it is powered off when i try to access bios or boot menu. This problem occurs on any client, with any user connected to iLO, in a big business environment, so i dont think that skype or similar causes the problem, if 'local software' on the client is meant in this doc.
F11 is'nt a solution, because i can't press ANY key, no matter if F9, F10, F11 or F12. No reaction.
And: An Intelligent Provisioning Recovery and/or iLO5-Update always resolved the problem, without changing anything on the client, where the remote session is started from. This IP update or recovery runs in automatic mode, ISO is mounted to iLO remote console, server boots from virtual odd automatically when boot order is default. Sometimes you have to wait a little, start server a second time with short power off inbetween, and then everything is fine, and i have access to RBSU/BIOS, Boot Menu, Intelligent Prov. via F9, F11, F10 ...