Professional Documents
Culture Documents
V2R2
Issue 06
Date 2020-04-27
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Contents
1 Overview....................................................................................................................................1
2 Logging In to a Server Using the Independent Remote Console (Windows)...........3
3 Logging In to a Server Using the Independent Remote Console (Ubuntu).............. 6
4 Logging In to a Server Using the Independent Remote Console (macOS)............... 9
5 Logging In to a Server Using the Independent Remote Console (Red Hat)...........12
1 Overview
The independent remote console is a remote control tool developed based on the
Huawei server management software iBMC and iMana 200. It plays the same
functions as Remote Control provided by the WebUI. This tool allows you to
remotely access and manage a server, without worrying about the compatibility
between the client's browser and the JRE.
This document uses the independent remote console for the iBMC as an example.
Basic Principle
Figure 1-1 shows the basic principle of the independent remote console.
Compatibility
The independent remote console can run in an environment that meets the
requirements listed in Table 1-1.
Windows 10 32-bit or
64-bit
Download
You can click Independent Remote Console to download the independent remote
console.
2
Logging In to a Server Using the
Independent Remote Console (Windows)
Scenarios
Use the independent remote console to remotely access a server from a client
running Windows.
Prerequisites
Conditions
The client (for example, a PC) is connected to the iBMC management network
port of the server to be accessed.
Data
● iBMC management network port IP address and port number
● User name and password for logging in to the iBMC
Software
You have downloaded the independent remote console software package to the
client (PC) and decompressed it.
Procedure
Step 1 Configure an IP address for the client (PC) to enable communication between the
client and the iBMC. That is, the IP address configured and the iBMC management
network port IP address must be in the same network segment.
Step 2 Double-click KVM.exe.
The independent remote console interface is displayed, as shown in Figure 2-1.
● The iBMC versions earlier than V228 only support logins of local users. The iBMC V228 and
later versions support logins of local and LDAP domain users.
● For the versions earlier than iBMC V228, Port number indicates the RMCP+ service port
number. For iBMC V228 and later versions, Port number indicates the HTTPS service port
number.
● The IPv6 address must be included in square brackets ([ ]), for example, [fc00::64]:444. Do
not include the IPv4 address, for example, 192.168.100.1:444.
● If the default port number is used, you do not need to enter the port number.
----End
Scenarios
Use the independent remote console IRC to remotely access a server from a client
running Ubuntu.
Prerequisites
Conditions
● The client (for example, a PC) is connected to the iBMC management
network port of the server to be accessed.
● The ipmitool later than 1.8.14 has been installed.
Data
● iBMC management network port IP address and port number
● User name and password for logging in to the iBMC
Software
You have downloaded the independent remote console software package to the
client (PC) and decompressed it.
Procedure
Step 1 Configure an IP address for the client (PC) to enable communication between the
client and the iBMC. That is, the IP address configured and the iBMC management
network port IP address must be in the same network segment.
Step 2 Open the console and specify the folder in which the IRC is stored as the working
folder.
Step 3 Run the chmod 777 KVM.sh command to set the permission for the independent
remote console.
● The iBMC versions earlier than V228 only support logins of local users. The iBMC V228 and
later versions support logins of local and LDAP domain users.
● For the versions earlier than iBMC V228, Port number indicates the RMCP+ service port
number. For iBMC V228 and later versions, Port number indicates the HTTPS service port
number.
● The IPv6 address must be included in square brackets ([ ]), for example, [fc00::64]:444. Do
not include the IPv4 address, for example, 192.168.100.1:444.
● If the default port number is used, you do not need to enter the port number.
----End
Scenarios
Use the independent remote console to remotely access a server from a client
running macOS.
Prerequisites
Conditions
● The client (for example, a PC) is connected to the iBMC management
network port of the server to be accessed.
● The ipmitool later than 1.8.14 has been installed.
Data
● iBMC management network port IP address and port number
● User name and password for logging in to the iBMC
Software
You have downloaded the independent remote console software package to the
client (PC) and decompressed it.
Procedure
Step 1 Configure an IP address for the client (PC) to enable communication between the
client and the iBMC. That is, the IP address configured and the iBMC management
network port IP address must be in the same network segment.
Step 2 Open the console and specify the folder in which the IRC is stored as the working
folder.
Step 3 Run the chmod 777 KVM.sh command to set the permission for the independent
remote console.
● The iBMC versions earlier than V228 only support logins of local users. The iBMC V228 and
later versions support logins of local and LDAP domain users.
● For the versions earlier than iBMC V228, Port number indicates the RMCP+ service port
number. For iBMC V228 and later versions, Port number indicates the HTTPS service port
number.
● The IPv6 address must be included in square brackets ([ ]), for example, [fc00::64]:444. Do
not include the IPv4 address, for example, 192.168.100.1:444.
● If the default port number is used, you do not need to enter the port number.
----End
5
Logging In to a Server Using the
Independent Remote Console (Red Hat)
Scenarios
Use the independent remote console to remotely access a server from a client
running Red Hat.
Prerequisites
Conditions
● The client (for example, a PC) is connected to the iBMC management
network port of the server to be accessed.
● The ipmitool later than 1.8.14 has been installed.
Data
● iBMC management network port IP address and port number
● User name and password for logging in to the iBMC
Software
You have downloaded the independent remote console software package to the
client (PC) and decompressed it.
Procedure
Step 1 Configure an IP address for the client (PC) to enable communication between the
client and the iBMC. That is, the IP address configured and the iBMC management
network port IP address must be in the same network segment.
Step 2 Open the console and specify the folder in which the IRC is stored as the working
folder.
Step 3 Run the chmod 777 KVM.sh command to set the permission for the independent
remote console.
● The iBMC versions earlier than V228 only support logins of local users. The iBMC V228 and
later versions support logins of local and LDAP domain users.
● For the versions earlier than iBMC V228, Port number indicates the RMCP+ service port
number. For iBMC V228 and later versions, Port number indicates the HTTPS service port
number.
● The IPv6 address must be included in square brackets ([ ]), for example, [fc00::64]:444. Do
not include the IPv4 address, for example, 192.168.100.1:444.
● If the default port number is used, you do not need to enter the port number.
----End