How is BMC or IPMI access different from SSH access to a dedicated server?
SSH normally reaches a service running inside the operating system. A baseboard management controller can provide hardware monitoring, console and power functions independently of that OS, subject to platform capability and standby power. Treat the management controller as a separate administrative system with its own network access and credentials.
Before you start
- Authorised access to the dedicated server and the named inspection tools.
Instructions
1. Identify which endpoint you are using
Confirm whether the hostname belongs to the operating system, a provider console gateway or the BMC. An OS administrator account is not automatically a BMC account, and the public server IP may not be the management address.
2. Inspect local BMC support when the OS is available
On supported Linux hardware, a local IPMI query can identify the controller without opening a remote management port.
sudo ipmitool -I open mc infoThis requires a working local IPMI driver/interface and permission. It is not a method for bypassing BMC authentication from another computer.
Check the result
- The operating-system and management-plane endpoints, access roles and recovery procedure are documented separately and tested through authorised routes.
Troubleshooting
- SSH is unavailable but the BMC responds
- Use console observations to distinguish boot, network and OS-service faults.
- The BMC is unavailable too
- Check the authorised management network and provider state; complete power or network loss can affect both access paths.
- IPMI is not exposed to the OS
- The provider may intentionally restrict local access. Use its supported authenticated console service.
Official references
Use the documentation for your installed version when a flag, service name or platform feature differs.
