A systems administrator applies a kernel patch to a Linux file server that is housed in a remote co-location facility. After the scheduled reboot, monitoring shows the host is powered on but not responding to SSH or ping. The IP-based KVM switch on the out-of-band (OOB) network is reachable. When the administrator opens the KVM viewer, the server's display is frozen at the GRUB menu. Which of the following is the BEST action to quickly restore the service without traveling to the site?
Open the IP KVM console and choose the previous kernel entry in GRUB to complete the boot process.
Send a Wake-on-LAN magic packet from the IP KVM interface to force the server to start normally.
Use the IP KVM web portal to cycle the rack PDU outlet and reboot the server.
Install a BIOS firmware update remotely through the IP KVM so the boot loader can proceed.
An IP KVM passes the server's keyboard, video, and mouse signals over the management network, giving an administrator the same low-level console control they would have while standing in front of the rack. By connecting to the remote console and selecting the previously working kernel in GRUB, the administrator can boot the operating system and bring the server back online.
Sending Wake-on-LAN (WoL) traffic is unnecessary because the server is already powered on, and most IP KVM appliances do not originate WoL packets. Pushing a BIOS firmware update would not address a boot-loader error and cannot be performed directly through a KVM switch. Power-cycling the PDU outlet might restart the host, but it does not fix the underlying kernel selection issue and is outside the normal feature set of an IP KVM. Therefore, using the KVM console to interact with GRUB is the most effective maintenance step.
Ask Bash
Bash is our AI bot, trained to help you pass your exam. AI Generated Content may display inaccurate information, always double-check anything important.
What is an IP KVM switch and how does it work?
Open an interactive chat with Bash
What is the purpose of the GRUB menu in Linux?
Open an interactive chat with Bash
What is the role of Wake-on-LAN (WoL), and why is it unnecessary here?