# IPMI Configuration
This article explains how to configure IPMI access for a server in EasyDCIM. It describes the IPMI Settings tab, the fields required to connect to the management controller, the optional Redfish support and the power control methods.
# IPMI Settings
The IPMI protocol enables remote administration, monitoring and management of server parameters through the management controller.
To configure the connection to IPMI, select 'Edit' from the 'Actions' menu located in the server summary view. The setup form has several tabs, in this case, you have to choose 'IPMI Settings'.
The form contains fields where you specify the IPMI controller’s IP address, username, password, board type and whether the device supports the Redfish protocol. There is no separate option to enable IPMI. IPMI is used for a server when the 'IPMI IP Address', 'IPMI Username' and 'IPMI Password' fields are filled in. To stop using IPMI for a server, clear these fields.
The 'IPMI Board Type' field shall specify the manufacturer of the server. Based on this field, EasyDCIM downloads the corresponding applet from the JAVA console for remote connection to the server and selects the Redfish driver when 'Redfish Support' is enabled. EasyDCIM always connects to IPMI on UDP port 623. This port cannot be changed in the form. The IPMI Remote Console Port field indicates an additional port on which the remote console operates.
To test the typed in data, press the 'Test IPMI Connection' button and the system will check the validity of the IPMI connection. The test uses the values currently entered in the form and saves the connection settings for the device. If 'Redfish Support' is enabled, the connection is tested with the Redfish protocol. If the test fails, check the device logs.
Use the 'noVNC KVM Console' button to open the KVM console of the server in a noVNC session. See the noVNC console section below.
- IPMI IP Address - static IPv4 address of the IPMI or Redfish interface
- IPMI Username - provide your IPMI username
- IPMI Password - enter your IPMI password. Use the 'Show' button to see the password.
- IPMI Board Type - specify the manufacturer of the server. Based on this field, EasyDCIM downloads the corresponding applet from the JAVA console for remote connection to the server.
- Redfish Support - enable this option if your device supports the Redfish protocol. IPMI actions, such as power control, will then be performed with the Redfish protocol. Actions that the Redfish driver does not support are still performed with IPMI. When this option is enabled, the 'Sensors' and 'Power Usage' tabs are also available in the server summary view. Default: 'No'.
In most cases, this configuration is sufficient for the IPMI connection. Click 'Show/Hide Advanced Settings' to see the fields for advanced users:
- IPMI Privilege Level - privilege levels determine which IPMI commands a user can execute over a channel. Available options: ADMINISTRATOR (default), CALLBACK, USER and OPERATOR.
- IPMI Proxy Server - a proxy server used for IPMI connections. By default, it is the proxy server used by the location of this device.
- noVNC Proxy Type - the action performed after the noVNC session starts: 'Automatically download and run the JAVA console', 'Start a web browser with access to the management panel' or 'Start a web browser in debug mode. For local use'. By default, the value is taken from the IPMI proxy server settings. A value selected here takes precedence over the proxy server configuration.
- noVNC Java version - the Java version used in the noVNC session: jdk1.8.0_121, jdk1.7.0_80, jre1.8.0_251 or OpenWebStart. By default, the value is taken from the IPMI proxy server settings.
- noVNC Environment Variables - additional environment variables for the noVNC session. Use the format KEY=VALUE;KEY2=VALUE2; to set multiple variables, separated by semicolons.
- IPMI Timeout - specify timeout for lanplus interface, 1 second as default
- IPMI Remote Console Port - used along with applet download for Java Console. Default ports: 443 or 80, depending on the hardware manufacturer.
- IPMI Remote Console Login URL - by default, it is the IPMI IP Address. Fill in only if the factory management panel is different from the IP address of the device.
- IPMI KVM Remote Port - KVM Console Redirection Port, default: 5900
- IPMI Channel - IPMI channel number used for user management commands, default: 1. Allowed values: 0 to 15.
# noVNC console
A noVNC session is created dynamically using the appropriate IPMI Proxy server for the given location. IPMI Proxy servers can be created within the 'IPMI Integration' extension. The IPMI Proxy server can be compared to the gateway between the private IPMI subnet and the end client that will use the KVM console. Once the JAVA console applet is downloaded to the remote agent server, EasyDCIM will create a VNC session that sends the image from the proxy server's virtual screen to the end user. If no IPMI Proxy server is set for the device or its location, the console cannot be started. You can read more about the IPMI Proxy server in the IPMI Proxy section.
To start the console, select 'noVNC KVM Console' from the 'Actions' menu in the server summary view or press the 'noVNC KVM Console' button in the 'IPMI Settings' tab. When the session is ready, click 'Open noVNC Console'. The console opens in a new browser window.
# Power control configuration
Remote power control is one of the most important and time-saving features for dedicated servers. The administrator is not always present at the data center in order to manually switch off a given machine, but thanks to the remote start function, it can be done in our system.
In order to configure the option of the remote power control, select the 'Edit' option from the 'Actions' menu located in the server summary view. There are several tabs in the setup form, in this case, you have to go to the 'Basic Information' tab and find the 'Power Control' section.
In this section, you can specify the 'First Method' and 'Second Method' of power control. Available options: IPMI and PDU. The default first method is IPMI and the default second method is PDU. With the IPMI method, the system executes the relevant command remotely using a specially constructed ipmitool command. If 'Redfish Support' is enabled in the 'IPMI Settings' tab, the IPMI method performs the action with the Redfish protocol instead, when the Redfish driver for the selected board type supports it. Another method of remote control is the management through the PDU outlet. If your device is connected to a selected PDU outlet, the outlet will perform the remote actions using the SNMP protocol.
After you have configured the remote power control option, you can go to the server summary view. In the upper section, you can find the 'Power Control' button containing such actions as Power On, Shutdown and Reboot. After you select and confirm one of these actions, the system performs it with the first method. If the first method fails, the system will automatically run the second method that you have selected. The IPMI Integration extension also adds the 'BMC Reset Cold' and 'Force Boot' actions to this menu.
# Troubleshooting IPMI Connection
TROUBLESHOOTING CENTER
If you are experiencing issues with the IPMI connection, you can find our diagnostic guide here:
IPMI Connection Troubleshooting →