Our AMD Ryzen Dedicated Servers are managed via Supermicro IPMI, a powerful and proven out-of-band management solution specifically designed for professional server environments. Unlike our Intel-based configurations that rely on HPE iLO, the AMD Ryzen platform uses Supermicro hardware and therefore offers IPMI as the native management interface.
Supermicro IPMI allows you full remote control of your server regardless of the operating system state. You can power the system on or off, reboot, monitor hardware health, read sensors, and work directly on the server via the remote console as if you were on-site. This ensures maximum control, fast response times, and reliable administration—even in critical situations.
Open the Remote Management tab of your Dedicated Server in the ZapX customer panel. There, activate a time-limited remote management session by clicking the "Start Session" button.
Please note it may take a few seconds until the session is fully available. Once the session is active, ZapX will display temporary access credentials. To open IPMI, click the "Open Remote Management" button – this will redirect you through the ZapX gateway directly to the actual IPMI interface.
Curious about how the IPMI management interface is structured and what the individual sections are for? This overview introduces the different pages of the interface and shows how monitoring, hardware insights, and remote management are organized.
It provides a guided introduction to explore the IPMI environment and understand how the views work together to give you full control and transparency over your server.
Offers a consolidated overview of the current server status and key management functions. System information such as hardware model, BIOS version, BMC firmware, and operational status are displayed for quick orientation.
The power section shows the current power state and consumption, allowing you to directly control power on/off and restarts while also gaining insight into energy usage.
Direct access to the remote console is available here, giving you full remote control of keyboard, video, and mouse—ideal for OS installations, troubleshooting, and maintenance regardless of server state.
Displays a detailed overview of installed hardware components and their current status. Information is provided for CPU, RAM modules, power supplies, power delivery, network AOC, sensors, and cooling systems.
Each section presents hardware-specific details such as model information, configuration, and operational status. Status indicators help you quickly identify healthy components as well as warnings or errors.
Lists system-related events logged by the management controller, providing a chronological history of hardware and health activities. Entries include power events, boot processes, sensor threshold violations, temperature warnings, voltage irregularities, and hardware errors.
Provides an overview of connected storage devices and their current operational status. Information includes detected drives, interface type, capacity, and health indicators as reported by the controller and available sensors.
Shows a list of existing user accounts with their assigned roles and permission levels. This page is for information so you can see which accounts have access to the management interface.
Displays the current configuration for system notifications and alert handling. Here you see which event types can trigger notifications, e.g., hardware errors, temperature thresholds, power issues, or sensor warnings.
Shows the network configuration of the management interface. This includes the assigned IP address, subnet mask, gateway, MAC address, and the current connection status of the IPMI network port.
You usually mount your own ISO files directly via the Installation tab in the ZapX panel (see our Custom ISO guide).
Alternatively, this section also allows the use of remote media images via the management interface. Here you see the status of mounted virtual media such as ISO images or remote storage devices connected to the server.
Virtual media can be used to boot the system, install an operating system, or perform recovery and maintenance tasks—without physical access to the hardware.
Shows configuration details of the Baseboard Management Controller. This section provides info on firmware version, system identification data, and general controller behavior.
Provides access to functions for direct remote interaction with the server. Here you find power control options such as power on, power off, reboot, and controlled shutdown.
It also serves as an entry point for remote management features that allow interaction with the system regardless of the operating system state.
Gives insight into the firmware status of the management environment, including the active BMC firmware and related components. Firmware versions and their current status can be checked to ensure consistency of the management stack. Updates or changes are intentionally not available to customers.
Records maintenance-related activities and system actions performed via the management interface. Logged entries include configuration changes, firmware-related operations, resets, and administrative actions.
-
Server does not boot or hangs during POST: If the server does not complete the boot process or hangs during POST, open the remote console to identify the exact phase where the process stops. Hardware initialization messages or error messages may be visible there. Perform a power cycle using the power control options by forcibly turning off the system for a few seconds and then restarting it. If the server still does not boot, contact support.
-
Remote console does not open or stays black: Make sure the remote console is not already in use by another connection. Close existing sessions and try again. Sometimes refreshing the browser or reopening the console helps resolve loading issues. If the problem persists, check if the server is powered on and reachable.
-
Virtual medium ISO is not recognized: Check if the ISO source is reachable and the file is directly accessible, e.g., by opening the link in a browser. Ensure the virtual media is correctly mounted and reboot the server after mounting the ISO. Also verify the boot order prioritizes virtual CD/DVD media.
-
Server takes a long time to start: Long boot times are normal for enterprise hardware. Hardware initialization, controller checks, and memory training can take several minutes, especially after a full power cycle.
-
IPMI interface temporarily unreachable: Make sure there is an active session in the Remote Management tab. After configuration changes or extended inactivity, the management interface may be temporarily unavailable. Wait a few minutes and try again, or start a new session. If access does not return, contact support to check the status of the management interface.