What IPMI provides
IPMI is the server's out-of-band management system. It remains separate from the installed operating system and its network configuration. The Remote console page shows only the methods reported by the selected hardware: browser KVM (HTML5), a Java KVM launcher (JNLP), Serial over LAN in a browser, or Serial over LAN through an SSH gateway.
Choose the right access method
Use browser KVM when you need video, keyboard and mouse interaction or must observe firmware and early boot. The Java KVM launcher can provide virtual-media features on compatible hardware but needs a working Java Web Start environment. Use browser SoL for a copy-and-paste capable text console, or SSH SoL from a terminal after supplying a complete raw SSH public key. SoL does not provide video or virtual ISO mounting.
Open a restricted temporary session
Request the shortest practical lifetime and restrict the session to the administrator's public IPv4 address when that option is available. Creating access starts an asynchronous infrastructure task; keep the page open while Silurian checks it. Browser KVM and browser SoL then open through a one-time Silurian address whose secret is removed before the console loads. Java and SSH launchers remain direct because they use their own applications. Never paste any console link, SSH address or launcher into a ticket, chat, bookmark or maintenance record.
Test and reset IPMI
If access does not work, run all three diagnostics: IPMI web access, IPMI authentication and IPMI network reachability. Review their latest results before resetting anything. Reset console sessions to clear stuck temporary sessions. Reset the IPMI interface only when the management controller is unresponsive; this can take several minutes but does not reboot or interrupt the dedicated server's operating system.
Diagnose before changing boot mode
Capture the current boot screen and error, confirm the selected server and check whether planned maintenance explains it. Inspect boot order, filesystem errors and network configuration before switching to rescue mode. Disable infrastructure monitoring before deliberately installing an operating system through IPMI so the expected outage is not mistaken for a fault.
Recover through rescue mode
Select the appropriate rescue environment, reboot deliberately and mount the installed system's filesystems without modifying them first. Back up critical configuration, repair the identified fault, restore normal local-disk boot and reboot again. Verify SSH, routing, storage and the application from an external network.
Close the recovery path
Close the temporary console, remove any emergency access rule and rotate a credential if it may have been exposed. Record the cause, commands or configuration changed, recovery time and the checks that proved normal service returned.
