Server

OS Installation Guide

Issue 09
Date 2025-07-30

XFUSION INTERNATIONAL PTE. LTD.

Copyright © XFUSION INTERNATIONAL PTE. LTD. 2025. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of XFUSION INTERNATIONAL PTE. LTD.

Trademarks and Permissions

and other xFusion trademarks are trademarks of XFUSION INTERNATIONAL PTE. 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 xFusion 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.

XFUSION INTERNATIONAL PTE. LTD.

Website: [Link]

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. i

Server
OS Installation Guide About This Document

About This Document

Purpose
This document describes the process and methods of installing an operating system
(OS) on x86-based servers. It also describes how to configure OS fault locating and
troubleshoot faults that you may experience during installation.

Intended Audience
This document is intended for:
● Technical support engineers
● Enterprise administrators

Symbol Conventions
The following table lists the symbols that may be found in this document.

Symbol Description

Indicates a hazard with a high level of risk which, if not avoided,

could result in death or serious injury.

Indicates a hazard with a medium level of risk which, if not

avoided, could result in death or serious injury.

Indicates a hazard with a low level of risk which, if not avoided,

could result in minor or moderate injury.

Indicates a potentially hazardous situation which, if not avoided,

could result in equipment damage, data loss, performance
degradation, or unpredictable results.
NOTICE is used to address practices not related to personal
injury.

Supplements the important information in the main text.

NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. ii

Server
OS Installation Guide About This Document

Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.

Issue Date Description

09 2025-07-30 Updated 5.3 Installing the OS

(xFusionBMC).

08 2024-07-30 Updated 7.2.1 Creating the VMware

ESXi 6.X/7.X Installation Source.

07 2023-06-30 This issue is the seventh official release.

Updated 5.4 Precautions for OS
Installation on NVMe SSDs.

06 2023-04-27 This issue is the sixth official release.

● Added 6.2 Loading Drivers.
● Added [Link] Configuring Kdump
on RHEL 8/RHEL 9.
● Added [Link] Configuring kdump
on SLES 15.

05 2022-08-02 This issue is the fifth official release.

Updated 8.4 Upgrading Firmware.

04 2022-07-12 This issue is the fourth official release.

● Updated 5.1.3 Setting the BIOS
System Time and Boot Device.
● Updated 5.1.4 (Optional) Setting UEFI
Secure Boot.

03 2022-04-02 This issue is the third official release.

Updated 1 Overview.

02 2022-02-16 This issue is the second official release.

Updated 3 Selecting an Installation
Mode.

01 2021-12-30 This issue is the first official release.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. iii

Server
OS Installation Guide Contents

Contents

About This Document.........................................................................................................ii

1 Overview........................................................................................................................... 1
2 Installation Process......................................................................................................... 2
3 Selecting an Installation Mode....................................................................................... 3
4 Installing an OS Using Smart Provisioning...................................................................6
4.1 Preparing for Installation..............................................................................................................................6
4.1.1 Obtaining the OS Installation Material...................................................................................................... 6
4.1.2 Setting the BIOS System Time and Boot Device......................................................................................7
4.2 Installing the OS...........................................................................................................................................7

5 Installing an OS Using a DVD-ROM or Image File........................................................ 8

5.1 Preparing for Installation..............................................................................................................................8
5.1.1 Obtaining the OS Installation Material...................................................................................................... 8
5.1.2 Configuring RAID......................................................................................................................................8
5.1.3 Setting the BIOS System Time and Boot Device......................................................................................9
5.1.4 (Optional) Setting UEFI Secure Boot........................................................................................................9
5.1.5 (Optional) Configuring SAN Boot for FC HBA...........................................................................................9
[Link] Configuring SAN Boot for Emulex FC HBA........................................................................................... 9
[Link].1 Configuring SAN Boot in Legacy Mode............................................................................................ 10
[Link].2 Configuring SAN Boot in UEFI Mode................................................................................................15
[Link] Configuring SAN Boot for Qlogic FC HBA........................................................................................... 27
[Link].1 Configuring SAN Boot in Legacy Mode............................................................................................ 27
[Link].2 Configuring SAN Boot in UEFI Mode................................................................................................33
5.2 Installing the OS.........................................................................................................................................39
5.3 Installing the OS (xFusionBMC).................................................................................................................49
5.4 Precautions for OS Installation on NVMe SSDs........................................................................................ 63

6 Installing an OS by Loading a RAID Controller Card Driver...................................... 65

6.1 Preparing for Installation............................................................................................................................65
6.1.1 Obtaining the OS Installation Material.................................................................................................... 65
6.1.2 Configuring RAID....................................................................................................................................67
6.1.3 Setting the BIOS System Time and Boot Device....................................................................................67
6.1.4 (Optional) Setting UEFI Secure Boot......................................................................................................67

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. iv

Server
OS Installation Guide Contents

6.1.5 (Optional) Configuring SAN Boot for FC HBA.........................................................................................67

[Link] Configuring SAN Boot for Emulex FC HBA......................................................................................... 68
[Link].1 Configuring SAN Boot in Legacy Mode............................................................................................ 68
[Link].2 Configuring SAN Boot in UEFI Mode................................................................................................73
[Link] Configuring SAN Boot for Qlogic FC HBA........................................................................................... 85
[Link].1 Configuring SAN Boot in Legacy Mode............................................................................................ 85
[Link].2 Configuring SAN Boot in UEFI Mode................................................................................................91
6.2 Loading Drivers..........................................................................................................................................97
6.2.1 Legacy Mode.......................................................................................................................................... 97
[Link] SLES....................................................................................................................................................97
[Link] RHEL................................................................................................................................................. 100
6.2.2 UEFI Mode............................................................................................................................................106
[Link] SLES..................................................................................................................................................106
[Link] RHEL..................................................................................................................................................110
6.2.3 Ubuntu...................................................................................................................................................115
[Link] Loading RAID Controller Card Drivers During OS Installation........................................................... 116
[Link].1 ISO Driver....................................................................................................................................... 116
[Link] Installing the RAID Controller Card Driver Before OS Reboot...........................................................121
6.3 Installing the OS.......................................................................................................................................124

7 Installing an OS by Creating an Installation Source.................................................138

7.1 Preparing for Installation..........................................................................................................................138
7.1.1 Obtaining the OS Installation Material.................................................................................................. 138
7.1.2 Configuring RAID..................................................................................................................................140
7.1.3 Setting the BIOS System Time and Boot Device..................................................................................140
7.1.4 (Optional) Setting UEFI Secure Boot....................................................................................................140
7.1.5 (Optional) Configuring SAN Boot for FC HBA.......................................................................................140
[Link] Configuring SAN Boot for Emulex FC HBA....................................................................................... 141
[Link].1 Configuring SAN Boot in Legacy Mode.......................................................................................... 141
[Link].2 Configuring SAN Boot in UEFI Mode..............................................................................................146
[Link] Configuring SAN Boot for Qlogic FC HBA......................................................................................... 158
[Link].1 Configuring SAN Boot in Legacy Mode.......................................................................................... 158
[Link].2 Configuring SAN Boot in UEFI Mode..............................................................................................164
7.2 Installing an OS by Creating an Installation Source.................................................................................170
7.2.1 Creating the VMware ESXi 6.X/7.X Installation Source........................................................................170

8 Installing and Upgrading Drivers and Firmware....................................................... 178

8.1 Preparing for Installation..........................................................................................................................178
8.2 Checking the Driver and Firmware Versions............................................................................................180
8.2.1 Checking Driver Versions on Windows................................................................................................. 180
8.2.2 Checking Driver and Firmware Versions on Linux................................................................................ 182
8.2.3 Checking Driver and Firmware Versions on VMware........................................................................... 184
8.3 Installing Drivers...................................................................................................................................... 186
8.3.1 Installing Drivers on Windows...............................................................................................................186

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. v

Server
OS Installation Guide Contents

8.3.2 Installing Drivers on Linux.....................................................................................................................189

8.3.3 Installing Drivers on VMware................................................................................................................ 191
8.4 Upgrading Firmware................................................................................................................................ 193

9 Common Operations................................................................................................... 194

9.1 Connecting to the Server......................................................................................................................... 194
9.1.1 Connecting Mouse, Keyboard, and VGA Cables to a Rack Server...................................................... 194
9.1.2 Connecting a High-Density Cable to a Blade or High-Density Server.................................................. 195
9.2 Logging In to the Virtual Console.............................................................................................................197
9.2.1 Logging In to the Remote Console (iBMC Earlier than V561).............................................................. 197
9.2.2 Logging In to the Remote Console (iBMC V561 or Later or [Link] or Later).................................200
9.2.3 Logging In Using the iMana 200 WebUI............................................................................................... 205
9.2.4 Logging In to the E9000 Compute Node KVM Using the MM910 WebUI.............................................208
9.2.5 Logging In to the E6000 Server KVM Using the MM620 WebUI.......................................................... 212
9.2.6 Logging In to the KVM (xFusionBMC).................................................................................................. 217
9.3 Transferring Files Using WinSCP............................................................................................................ 220
9.4 Transferring Files Using the Local Directory............................................................................................221

10 Locating OS Faults.................................................................................................... 223

10.1 Configuring Memory Dump Tools...........................................................................................................223
10.1.1 Configuring kdump on Linux............................................................................................................... 223
[Link] Concepts..........................................................................................................................................223
[Link] Configuring kdump on RHEL 5........................................................................................................ 224
[Link] Configuring kdump on RHEL 6........................................................................................................ 225
[Link] Configuring kdump on RHEL 7........................................................................................................ 227
[Link] Configuring Kdump on RHEL 8/RHEL 9..........................................................................................229
[Link] Configuring kdump on SLES 11.......................................................................................................230
[Link] Configuring kdump on SLES 12.......................................................................................................233
[Link] Configuring kdump on SLES 15.......................................................................................................235
10.1.2 Configuring DiskDump on VMware.....................................................................................................237
10.1.3 Configuring the Memory Dump Service on Windows......................................................................... 239
10.2 Configuring SOL.................................................................................................................................... 240
10.2.1 Configuring SOL on Linux...................................................................................................................240
10.2.2 Configuring SOL on VMware.............................................................................................................. 240
10.3 Configure an NMI...................................................................................................................................242
10.4 Configuring Magic Keys for Linux.......................................................................................................... 244
10.5 Changing Linux System Log Levels.......................................................................................................246
10.6 Disabling the Screen Saver................................................................................................................... 247
10.7 Deploying and Verifying Fault Locating Tools on Linux......................................................................... 248
10.8 Troubleshooting..................................................................................................................................... 250
10.8.1 Failed to Start kdump..........................................................................................................................250
10.8.2 Failed to Detect Drives After the kdump Process Starts.....................................................................250
10.8.3 OOM Reported After the kdump Process Starts.................................................................................251
10.8.4 Failed to Install an OS on a Drive with RAID Information................................................................... 252

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. vi

Server
OS Installation Guide Contents

10.8.5 Red Hat Linux Displayed on the BIOS Boot Option Menu During the CentOS 6.X Installation in UEFI
Mode..............................................................................................................................................................253
10.8.6 Blue Screen Is Displayed When the Server Reboots Upon Installation of Windows Server 2012 R2
.......................................................................................................................................................................253
10.8.7 How to Install a Windows Server 2016 Patch..................................................................................... 254
10.8.8 Installing Drivers on Linux...................................................................................................................258

A How to Obtain Help..................................................................................................... 261

A.1 Collecting Fault Information.....................................................................................................................261
A.2 Preparing for Debugging......................................................................................................................... 261
A.3 Using Product Documentation.................................................................................................................261
A.4 Technical Support....................................................................................................................................262

B Appendix...................................................................................................................... 263
B.1 Glossary.................................................................................................................................................. 263
B.2 Acronyms and Abbreviations...................................................................................................................266

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. vii

Server
OS Installation Guide 1 Overview

1 Overview

Servers support the installation of mainstream operating systems (OSs), such as

Windows, Red Hat Enterprise Linux (RHEL), CentOS, SUSE Linux Enterprise Server
(SLES), Ubuntu, and VMware ESXi in UEFI or Legacy mode.

OS Installation Methods
You can install an operating system (OS) for your servers using the following
methods: Smart Provisioning, direct installation, driver loading, and installation
source. Different hardware configurations support different OSs and installation
methods. You can query the operating systems and installation modes supported by
the server by referring to Compatibility Checker.

Server Login Methods

You can use a remote client (PC) or a local KVM server.
● When logging in to the virtual console of the server through a remote client (PC),
you can mount the system DVD-ROM in the physical DVD-ROM drive of the PC
through the virtual console, or mount the image file through the virtual DVD-
ROM drive. This login mode applies to all the preceding four installation
methods. For details, see 9.2 Logging In to the Virtual Console.
● When logging in to the server through a local KVM, you can use only the
physical DVD-ROM drive of the server. This login mode applies only to two
installation methods: using an installation DVD-ROM or image file, and using
Smart Provisioning. For details, see 9.1 Connecting to the Server.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 1

Server
OS Installation Guide 2 Installation Process

2 Installation Process

Figure 2-1 shows the process for installing an OS on servers.

Figure 2-1 Installation process

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 2

Server
OS Installation Guide 3 Selecting an Installation Mode

3 Selecting an Installation Mode

The OS installation methods and NIC drivers to be installed vary according to the OS
or NIC type.
You can choose one of the four installation methods described in Table 3-1.

Table 3-1 OS installation methods

Install Description
ation
Metho
d

Using Smart Provisioning is an OS installation wizard that simplifies the process

Smart for engineers to install OSs and drivers.
Provis Smart Provisioning has the following features:
ioning
● Helps users install OSs and drivers required by the detected
hardware.
● Provides a wizard to make installation processes more simple and
consistent.
● Simplifies and speeds up OS deployment on servers.

Using It is a common method to install an OS using an OS installation DVD-

a DVD ROM or image file.
or If you choose this method, you can use a physical DVD-ROM drive to
image read content from a physical DVD or use a virtual DVD drive to load an
file image file.

Installi If a server is configured with RAID controller cards, you can load the
ng an RAID controller card drivers to install the OS and the drivers at the same
OS by time.
loadin You can use a virtual DVD drive to load an ISO driver image, or use a
ga virtual floppy drive to load an IMG driver image.
RAID
contro ● Loading an ISO driver image: You can use a virtual DVD-ROM drive to
ller switch between the OS image file and the RAID controller card driver
card image file.
driver ● Loading an IMG driver image: You can directly load the driver.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 3

Server
OS Installation Guide 3 Selecting an Installation Mode

Install Description
ation
Metho
d

Installi This installation method applies only to VMware ESXi OSs. The drivers
ng an for OS installation are encapsulated into an ISO image file.
OS by If you choose this method, you need to use a virtual DVD drive to load
creati the image file.
ng an
install
ation
sourc
e

Procedure
Step 1 Access the compatibility list on the technical support website.

Step 2 Select a corresponding server type in the FusionServer drop-down list.

Step 3 Query the correct OS installation method.

NO TE

As technology evolves, hardware components and platforms of servers will be upgraded.

Generally, CPUs are upgraded once per year and platforms once every two years. To match
new hardware products, OS manufacturers will also upgrade their OS versions. This is why OS
manufacturers claim that they support a certain hardware platform since a specified version
and do not provide technical support for OSs with earlier versions.

1. Select the server model and component to be queried.

2. Click Search.
The supported OSs are displayed, as shown in Figure 3-1.
The notes displayed at the lower part of the page list the applicable OS
installation methods.

Figure 3-1 Supported OSs

Step 4 Install the OS.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 4

Server
OS Installation Guide 3 Selecting an Installation Mode

For details about the installation methods, see the corresponding sections.
● 4 Installing an OS Using Smart Provisioning
● 5 Installing an OS Using a DVD-ROM or Image File
● 6 Installing an OS by Loading a RAID Controller Card Driver
● 7 Installing an OS by Creating an Installation Source

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 5

Server
OS Installation Guide 4 Installing an OS Using Smart Provisioning

4 Installing an OS Using Smart

Provisioning

NO TE

Before installing an OS, access Compatibility Checker to check whether the OS supports this
installation method.

Smart Provisioning is an OS installation wizard that simplifies the process for

engineers to install OSs and drivers.

You can install the OS by integrating Smart Provisioning on the mainboard or by

mounting the Smart Provisioning image.

For details about how to install other OSs, see the corresponding server OS
installation guide cases.
4.1 Preparing for Installation
4.2 Installing the OS

4.1 Preparing for Installation

4.1.1 Obtaining the OS Installation Material

NO TE

For details about the OSs supported by the server, see Compatibility Checker.

Procedure
Step 1 Obtain the OS installation DVD-ROM or image file.

Prepare the OS installation DVD-ROM or image file in advance.

Step 2 Obtain the Smart Provisioning image file.

To obtain the image file, perform the following steps:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 6

Server
OS Installation Guide 4 Installing an OS Using Smart Provisioning

1. Visit the Technical Support Website > Software Download > Smart
Provisioning.
2. Click the path where the required version is stored and download the Smart
Provisioning image file. The file name is in the format of SmartProvisioning-
[Link] (x.x.x.x indicates the SmartProvisioning version).

NO TE

To avoid using software packages that have been tampered with during transmission or
storage, download their digital signature files for integrity check while downloading the
software packages.
After the software package is downloaded from the technical support website, verify its PGP
digital signature. See the OpenPGP Signature Verification Guide. If the software package fails
the verification, do not use the software package, and contact technical support.
Before using a software package in installation or update, verify its digital signature according
to the OpenPGP signature verification guide to ensure that the software package is not
tampered with.

----End

4.1.2 Setting the BIOS System Time and Boot Device

NO TE

Set the boot device through iBMC. For details, see the iBMC user guide of corresponding
server model.

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

4.2 Installing the OS

After the installation is ready, refer to the corresponding version of Smart Provisioning
user guide.

NO TICE

● Before you install an OS on a drive using Smart Provisioning, back up data on the
drive because the drive will be formatted during installation.
● When installing an OS in Legacy mode, ensure that the capacity of the drive
where the OS is installed is less than 2 TB.

You are advised to configure the OS fault locating function after the installation is
complete. For details, see 10 Locating OS Faults. If you need to upgrade the drivers
for related components, see 8 Installing and Upgrading Drivers and Firmware.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 7

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

5 Installing an OS Using a DVD-ROM or

Image File

NO TE

Before installing an OS, access Compatibility Checker to check whether the OS supports this
installation method.

This section describes how to install the OS by using an installation DVD-ROM or

ISO image file. You do not need to install drivers or compile the installation source
during installation.

For details about how to install other OSs, see the corresponding server OS
installation guide cases.
5.1 Preparing for Installation
5.2 Installing the OS
5.3 Installing the OS (xFusionBMC)
5.4 Precautions for OS Installation on NVMe SSDs

5.1 Preparing for Installation

5.1.1 Obtaining the OS Installation Material

Prepare the OS installation DVD-ROM or image file in advance.

NO TE

For details about the OSs supported by the server, see Compatibility Checker.

5.1.2 Configuring RAID

Procedure
Step 1 Configure RAID.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 8

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Different RAID controller cards support different RAID configurations. For details, see
the RAID controller card user guide of corresponding server model.

Step 2 Configure the boot option.

● If you have configured multiple RAID groups or a RAID group with multiple
virtual drives (VDs), you must set the boot device. Otherwise, the OS installation
may become abnormal.
Different RAID controller cards support different RAID configurations. For details,
see the RAID controller card user guide of corresponding server model.
● If multiple RAID controller cards (including SoftRAID) are configured, access the
Boot tab on the BIOS screen and set a RAID controller card as the boot device.
Parameter names vary between different BIOS platforms. For details about the
parameters, see the BIOS parameter reference of corresponding server model.

----End

5.1.3 Setting the BIOS System Time and Boot Device

NO TE

Set the boot device through iBMC/xFusionBMC. For details, see the iBMC/xFusionBMC user
guide of corresponding server model.

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

5.1.4 (Optional) Setting UEFI Secure Boot

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

5.1.5 (Optional) Configuring SAN Boot for FC HBA

To use a FC HBA and boot the OS from storage area network (SAN), configure SAN
Boot for FC HBA before installing an OS.

NO TE

The operation procedure varies depending on the BIOS platform. For Purley, Cedar Island,
Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley, Brickland, and Romley,
the default boot type is Legacy.
● In Legacy mode, during power-on self-test (POST), press Alt+E or Ctrl+E to enter the
Emulex BIOS setup screen, or press Ctrl+Q or Alt+Q to enter the QLogic BIOS setup
screen.
● In UEFI mode, configure SAN Boot for FC HBA using Device Manager on the front screen.
For details, see the user manual of corresponding BIOS platform.

[Link] Configuring SAN Boot for Emulex FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 9

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of the Emulex FC HBA and configure the SAN Boot
of the FC HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 5-1 is displayed,
press Alt+E or Ctrl+E to enter the BIOS Setup screen.

Figure 5-1 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 5-2 Selecting a port for SAN Boot (FC mode)

Step 4 On the screen displayed in Figure 5-3, select Enable/Disable Boot from SAN and
press Enter to access the SAN Boot enabling option screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 10

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-3 SAN Boot configuration screen

Step 5 Select Enable and press Enter to enable SAN Boot. By default, SAN Boot is
disabled.

Figure 5-4 Enabling SAN Boot

Step 6 (Optional) Scan for disk arrays.

1. Press Esc to go back to the screen shown in Figure 5-3.
2. Select Scan for Target Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 5-5.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 11

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-5 Disk array information

Step 7 Configure the SAN Boot device.

1. Press Esc to go back to the screen shown in Figure 5-3.
2. Select Configure Boot Devices, and press Enter.

Step 8 Select a boot option, and press Enter.

If no boot device is configured, no disk array information is displayed, as shown in

Figure 5-6.

Figure 5-6 Selecting a boot option

Step 9 Select a boot entry, and press Enter, as shown in Figure 5-7.

NO TE

A boot entry specifies the device for SAN Boot. If you select Clear selected boot entry and
press Enter, the SAN Boot configuration of the selected boot entry is cleared.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 12

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-7 Selecting a boot entry

Step 10 Set the starting logical unit number (LUN) by pressing the up and down arrow keys,
and press Enter.

Figure 5-8 Setting the starting LUN

Step 11 Select an LUN for SAN Boot, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 13

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-9 Selecting an LUN for SAN Boot

Step 12 Set the device boot mode and press Enter.

● WWPN is the WWN of the port on the disk array.
● DID is the N_Port_ID assigned to the port by the FC name server.

Figure 5-10 Setting the boot mode

Step 13 View the boot device information. If the status of a boot device is Used, as shown in
Figure 5-11, the boot device has been configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 14

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-11 Boot device sequence (one boot device)

You can use the same method to set more boot devices. Figure 5-12 shows the boot
device sequence when two boot devices are added.

Figure 5-12 Boot device sequence (two boot devices)

NO TE

You can select Reset Adapter Defaults in the screen shown in Figure 5-3 to restore the
default SAN Boot configurations.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 15

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 5-13 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 16

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-14 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 5-15.
NO TE

The default BIOS password is Admin@9000.

Figure 5-15 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 17

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The Front Page screen is displayed, as shown in Figure 5-16 or Figure 5-17.

Figure 5-16 Front Page screen (BIOS V3XX and earlier)

Figure 5-17 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 18

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The Device Manager screen is displayed.

Step 5 Select an FC HBA port, and press Enter.

Figure 5-18 Selecting an SAN Boot port

Step 6 In the screen shown in Figure 5-19, select Set Boot from SAN and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 19

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-19 SAN Boot configuration screen

Step 7 Select Enable and press Enter to enable SAN Boot.

Figure 5-20 Enabling SAN Boot

Step 8 Scan disk array information.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 20

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

1. Press Esc to go back to the screen shown in Figure 5-19.

2. Select Scan for Fibre Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 5-21.

Figure 5-21 Disk array information

Step 9 Add the SAN Boot device.

1. Press Esc to go back to the screen shown in Figure 5-19.
2. Select Add Boot Device, and press Enter.
Select a scanned disk array and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 21

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-22 Selecting a disk array

3. Select a logical unit number (LUN) for the boot device to be set and press Enter.

Figure 5-23 Selecting an LUN for SAN Boot

4. Select Commit Changes, and press Enter.

The boot device is added.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 22

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-24 Committing changes

Step 10 (Optional) Delete a SAN boot device.

1. Press Esc to go back to the screen shown in Figure 5-19.
2. Select Delete Boot Device, and press Enter.
3. Select the boot device to be deleted, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 23

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-25 Selecting the boot device to be deleted

4. Select DELETE, and press Enter.

Figure 5-26 Deleting a boot device

5. Select Commit Changes, and press Enter.

The boot device is deleted.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 24

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-27 Committing changes

Step 11 (Optional) Change the boot device order.

1. Press Esc to go back to the screen shown in Figure 5-19.
2. Select Change Boot Device Order, and press Enter.
3. Select Boot Device Order, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 25

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-28 Selecting the boot device order

4. Select a boot device and press F5 (moving downwards) or F6 (moving upwards)

to change the boot device order.
5. Then, press Tab to select OK and press Enter.

Figure 5-29 Changing the boot device order

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 26

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

6. Select Commit Changes, and press Enter. The boot device order is changed
successfully.

Figure 5-30 Committing changes

----End

[Link] Configuring SAN Boot for Qlogic FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of Qlogic and configure the SAN Boot of the FC
HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 5-31 is displayed,
press Ctrl+Q or Alt+Q to enter the BIOS Setup screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 27

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-31 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 5-32 Selecting a port for SAN Boot

Step 4 Select Configuration Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 28

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-33 Port configuration screen

Step 5 Select Adapter Settings, and press Enter.

Figure 5-34 Configuration Settings screen

Step 6 Set Host Adapter BIOS to Enabled. By default, SAN Boot is disabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 29

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-35 Adapter Settings screen

Step 7 Press Esc to go back to the Configuration Settings screen.

Step 8 Select Selectable Boot Settings, and press Enter.

Figure 5-36 Configuration Settings screen

Step 9 Set Selectable Boot to Enabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 30

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-37 Selectable Boot Settings screen

Step 10 Select a boot option, and press Enter.

Figure 5-38 Selecting a boot option

Step 11 Select a boot entry, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 31

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-39 Selecting a boot entry

Step 12 Set the starting LUN by pressing the up and down arrow keys, and press Enter.

Figure 5-40 Setting the starting LUN

Step 13 View the boot device information. If the boot device is displayed in the Selectable
Boot Settings screen, as shown in Figure 5-41, the boot device has been configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 32

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-41 Boot device sequence

Step 14 Press Esc to go back to the screen shown in Figure 5-36.

Step 15 Press Esc. A confirmation dialog is displayed.

Figure 5-42 Confirmation dialog

Step 16 Select Save changes, and press Enter.

Step 17 Press Esc to exit. The SAN Boot configuration is complete.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 33

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 5-43 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 34

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-44 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 5-45.
NO TE

The default BIOS password is Admin@9000.

Figure 5-45 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 35

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The Front Page screen is displayed, as shown in Figure 5-46 or Figure 5-47.

Figure 5-46 Front Page screen (BIOS V3XX and earlier)

Figure 5-47 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.
The Device Manager screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 36

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 5 Select Network Device List, and press Enter.

Step 6 Select an FC HBA port, and press Enter.

Figure 5-48 Device Manager screen

Step 7 Select Boot Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 37

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-49 Selecting Boot Settings

Step 8 Select Adapter Driver, and press Enter.

Figure 5-50 Boot Settings screen

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 38

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 9 Select Enabled and press Enter to enable SAN Boot.

Figure 5-51 Enabling SAN Boot

Step 10 Press Esc twice to return to the Device Manager screen, exit the FC HBA setup
screen, and save the SAN Boot settings.

----End

5.2 Installing the OS

This section describes how to install the OS by using an installation DVD-ROM or
ISO image file.
The installation methods vary according to the OS version and OS type. You can
access OS official websites for more details. The following describes how to install
SLES 15 in Legacy mode.
For details about how to install other OSs, see the corresponding server OS
installation guide cases.

Procedure
Step 1 Log in to the virtual console of the server.
For details, see the iBMC user guide of corresponding server model.
Step 2 Mount the OS ISO image to the virtual DVD-ROM drive.

1. On the toolbar of the remote control, click .

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 39

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure 5-52.

Figure 5-52 Virtual DVD-ROM drive dialog box

2. Select Image File and click Browse.

The Open dialog box is displayed.
3. Select the OS ISO image file and click Open.
4. In the virtual DVD-ROM drive dialog box, click Connect.
When Connect changes to Disconnect, the virtual DVD-ROM drive is
connected to the server.

Step 3 Access the Boot Manager screen.

1. Reboot the OS.
2. When the startup screen shown in Figure 5-53 is displayed, press Del.

Figure 5-53 BIOS boot screen

3. Enter the password as prompted and press Enter.

NO TE

The default BIOS password is Admin@9000.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 40

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The Front Page screen is displayed, as shown in Figure 5-54.

Figure 5-54 Front Page screen

4. Select Boot Manager and press Enter.

The Boot Manager screen is displayed.

Step 4 On the Boot Manager screen, use F5 (moving down) or F6 (moving up) to set the
drive where the OS is to be installed as the first boot device. Then select Virtual
DVD-ROM VM 1.1.0 and press Enter.

Figure 5-55 Boot Manager screen

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 41

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 5 On the initial installation screen, choose Installation.

The license agreement screen is displayed.

Step 6 Select I Agree to the License Terms and click Next.

The network configuration page is displayed. You can configure the network and click
Next, or directly click Next to skip the network configuration.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 42

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 7 Click Next. The registration screen is displayed.

Step 8 Select Skip Registration.

A confirmation dialog box is displayed.

Click OK and click Next.

Step 9 Select the modules to be installed as required and click Next.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 43

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 10 Select SLES with GNOME and click next.

Step 11 Manually or automatically partition the drives.

● For automatic partitioning, click Next. Go to Step 15.
● For manual partitioning, choose Expert Partitioner > Start with Current
Proposal to go to Step 12.

The Expert Partitioner screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 44

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 12 Manually partition the drives.

1. Delete existing partitions.
Select the drive where the OS is to be installed and click Delete to delete
existing partitions.
2. Create a BIOS Boot Partition.
a. Select the hard disk where the BIOS Boot Partition is to be installed, and
click Add.
b. On the New Partition Size screen, select Custom Size, set Size to 10M
(recommended), and click Next.
c. On the Role screen, select Data and ISV Applications and click Next.
d. On the Format Options screen, select Do Not format device and Do not
mount device, set Partition ID to BIOS Boot Partition, and click Next.
3. Create a root partition.
a. Select the drive where the root partition is to be installed, click Add, and
select Primary Partition.
b. On the New Partition Size screen, select Custom Size, set Size to 100G,
and click Next.
c. On the Role screen, select OperatingSystem and click Next.
d. On the Format Options screen, retain the default value XFS for
Filesystem. You can select another file system as required. Set Mount
Point to / and click Next.
4. Create a swap partition.
a. Select the drive where the swap partition is to be installed, click Add, and
select Primary Partition.
b. On the New Partition Size screen, select Custom Size, set Size to 20G,
and click Next.
c. On the Role screen, select OperatingSystem and click Next.
d. On the Format Options screen, set Filesystem to Swap and Mount Point
to Swap, and click Next.
Step 13 After confirming that the partitions are correctly created, click Accept.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 45

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The Suggested Partitioning screen is displayed.

Step 14 Click Next.

Step 15 Set the required time zone and click Next.

Step 16 On the Local Users screen, select Skip User Creation and click Next.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 46

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The screen for setting the password of the system administrator is displayed.
Step 17 Set a password for the root user and click Next.

Step 18 Click Install.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 47

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

The OS installation starts.

After the OS is installed, the OS login screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 48

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

----End

NO TE

After the OS is installed, check whether the existing driver versions match the OS. If the driver
versions do not match, install the drivers of the required versions. For details, see 8 Installing
and Upgrading Drivers and Firmware. You are advised to configure the OS fault locating
function. For details, see 10 Locating OS Faults.

5.3 Installing the OS (xFusionBMC)

This section describes how to install the OS by using an installation DVD-ROM or
ISO image file.

The installation methods vary according to the OS version and OS type. You can
access OS official websites for more details. The following describes how to install
RHEL 9.4.

For details about how to install other OSs, see the corresponding server OS
installation guide cases.

Procedure
Step 1 Mount OS ISO image in the virtual DVD-ROM drive.
1. Log in to the xFusionBMC WebUI.
2. Choose Remote Control > Remote Virtual Media or Local Virtual Media.
3. Mount the system ISO image through the virtual CD-ROM drive as shown in
Figure 5-56 and Figure 5-57.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 49

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

– Remote Virtual Media: Set the media type and transmission protocol, enter
the URL of the ISO image file, and click Connect. If Connect changes to
Disconnect, the virtual DVD-ROM drive is connected to the server.

Figure 5-56 Remote Virtual Media

– Local Virtual Media: Click Select File, select a local ISO image file, click
Connect, and click . If the value of Connection Status changes from
Connect to Disconnect and the loading action is green, the virtual
DVD-ROM drive is connected to the server.

Figure 5-57 Local Virtual Media

Step 2 Select the virtual CD-ROM drive boot mode.

● Setting on xFusionBMC WebUI
a. Log in to the xFusionBMC WebUI.
b. Choose Power Control > Boot Option Settings.
c. Set Boot Option to Boot from CD/DVD.

Figure 5-58 Boot Options Setting

d. Click Submit.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 50

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

e. Restart the server.

● Setting on the BIOS
a. Restart the server. When the screen as shown in Figure 5-59 is displayed,
press Del.

Figure 5-59 BIOS Boot Screen

b. If prompted for a password, enter the password in the dialog box, press
Enter. The front page is displayed as shown in Figure 5-60.
NO TE

The default BIOS password is Admin@9000.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 51

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-60 Front Page

c. Select EFI USB Device (Byosoft Virtual CD-ROM) under Boot Manager >
DVD-ROM Drive to boot from the virtual DVD-ROM drive.

Figure 5-61 Boot virtual CD-ROM drive

Step 3 Select Remote Control > KVM in the navigation bar on the xFusionBMC WebUI.
The remote virtual desktop page is displayed.
Step 4 On the installation start screen, select Install Red Hat Enterprise Linux 9.4.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 52

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-62 Select OS

Step 5 Select a language (default is English) and click Continue.

Figure 5-63 Select a Language

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 53

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 6 In the LOCALIZATION area, perform the following operations:

● Click Keyboard to configure the keyboard type and language as required and
click Done.
● Click Time & Date to set the time and date. You are advised to set the current
local time. Then click Done.

Figure 5-64 LOCALIZATION Configuration

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 54

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-65 Configuring Time and Date

Step 7 In the SOFTWARE area, click Software Selection.

Figure 5-66 SOFTWARE Configuration

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 55

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 8 Select Server with GUI. Select and install other components as required. Then click
Done.

Figure 5-67 Installing Components

Step 9 In the SYSTEM configuration area, click Installation Destination.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 56

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-68 System Configuration

Step 10 Select the drive where the OS is to be installed, select a partitioning mode, and click
Done.
NO TE

Automatic partitioning and custom partitioning are supported. For example, select Custom.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 57

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-69 Selecting System Drive

Step 11 Select Standard Partition and click Click here to create them automatically. to
create a partition. After the new partition is created, click Done.
NO TE

You can also click the + to create partition manually. After the partition is created, click Done.
Create at least five partitions including /home, /boot/efi, /boot, swap, and /. Create other
partitions as planned.

Figure 5-70 Creating partition

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 58

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 12 Click Root Password to set the root password and click Done.

Figure 5-71 USER SETTINGS Configuration

Figure 5-72 Setting Root Password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 59

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 13 Click User Creation to create a user. After the user is created, click Done.

Figure 5-73 USER SETTINGS Configuration

Figure 5-74 Creating User

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 60

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Step 14 Click Begin Installation to enter the installation screen.

Figure 5-75 Configuration Completed

The OS installation starts.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 61

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Figure 5-76 Installing the OS

Step 15 After the installation is complete, click Reboot System to restart the OS.

Figure 5-77 Completing the Installation

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 62

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Access the OS login screen after the reboot is complete.

Figure 5-78 OS Login Page

----End

5.4 Precautions for OS Installation on NVMe SSDs

For details about the OSs supported by NVMe drives, access the compatibility list on
the technical support website. Table 5-1 describes the support for OS installation
from NVMe SSDs of servers.

Table 5-1 OS installation on NVMe SSDs

Server UEFI Mode Legacy Mode

V3 Supported Not supported.

V5 Supported Supported by BIOS V829

and later versions.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 63

Server
OS Installation Guide 5 Installing an OS Using a DVD-ROM or Image File

Server UEFI Mode Legacy Mode

V6 Supported Supported by BIOS V097

and later versions for
1288H V6, 2288H
V6-32DIMM, 5288 V6,
2288E V6, G5500 V6,
XH321 V6, XH321C V6,
DH120C V6, DH121C V6,
and DH122E V6;
supported by all BIOS
versions for other server
models.

V7 Supported Supported.

V8 Supported Only the 2158H V8

Genoa platform
supported.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 64

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

6 Installing an OS by Loading a RAID

Controller Card Driver

NO TE

Before installing an OS, access Compatibility Checker to check whether the OS supports this
installation method.

This section describes how to install the OS and RAID controller card driver at a time
by loading the driver.
For details about how to install other OSs, see the corresponding server OS
installation guide cases.
6.1 Preparing for Installation
6.2 Loading Drivers
6.3 Installing the OS

6.1 Preparing for Installation

6.1.1 Obtaining the OS Installation Material

Procedure
Step 1 Obtain the OS installation DVD-ROM or image file.
Prepare the OS installation DVD-ROM or image file in advance.
Step 2 Query compatible OSs.
1. Access the compatibility list on the technical support website.
2. Select the server type.
The compatibility query page is displayed.
3. Click the Search OSs tab.
4. Based on the actual hardware configuration of the server, select the
corresponding parts and query the OS compatibility of the specified server.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 65

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 3 Download the driver version mapping table.

1. Visit the Technical Support Website > Software Download > FusionServer
iDriver.
2. On the Software Download tab page, click the required version to go to the
corresponding page.
The table describes the mapping between OSs and drivers or firmware.
NO TE

The driver version mapping table records all the parts whose drivers can be upgraded in
the OS and the corresponding driver and firmware information. If the driver and firmware
information of a part cannot be found, the OS is not compatible with the part.

Step 4 Download the driver installation package.

1. Access the compatibility list on the technical support website.
2. Select the server type.
The compatibility query page is displayed.
3. Click the Search Parts tab.
4. Select the product model and part type to query the part compatibility of the
specified server.
5. Click Search.
The part compatibility list is displayed, as shown in Figure 6-1.

Figure 6-1 Part compatibility list

6. Click Link in the Drivers column.

Go to the download path.
7. Download the required driver installation package by referring to the driver
mapping table.

NO TE

To avoid using software packages that have been tampered with during transmission or
storage, download their digital signature files for integrity check while downloading the
software packages.
After the software package is downloaded from the technical support website, verify its PGP
digital signature. See the OpenPGP Signature Verification Guide. If the software package fails
the verification, do not use the software package, and contact technical support.
Before using a software package in installation or update, verify its digital signature according
to the OpenPGP signature verification guide to ensure that the software package is not
tampered with.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 66

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

6.1.2 Configuring RAID

Procedure
Step 1 Configure RAID.

Different RAID controller cards support different RAID configurations. For details, see
the RAID controller card user guide of corresponding server model.

Step 2 Configure the boot option.

● If you have configured multiple RAID groups or a RAID group with multiple
virtual drives (VDs), you must set the boot device. Otherwise, the OS installation
may become abnormal.
Different RAID controller cards support different RAID configurations. For details,
see the RAID controller card user guide of corresponding server model.
● If multiple RAID controller cards (including SoftRAID) are configured, access the
Boot tab on the BIOS screen and set a RAID controller card as the boot device.
Parameter names vary between different BIOS platforms. For details about the
parameters, see the BIOS parameter reference of corresponding server model.

----End

6.1.3 Setting the BIOS System Time and Boot Device

NO TE

Set the boot device through iBMC/xFusionBMC. For details, see the iBMC/xFusionBMC user
guide of corresponding server model.

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

6.1.4 (Optional) Setting UEFI Secure Boot

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

6.1.5 (Optional) Configuring SAN Boot for FC HBA

To use a FC HBA and boot the OS from storage area network (SAN), configure SAN
Boot for FC HBA before installing an OS.

NO TE

The operation procedure varies depending on the BIOS platform. For Purley, Cedar Island,
Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley, Brickland, and Romley,
the default boot type is Legacy.
● In Legacy mode, during power-on self-test (POST), press Alt+E or Ctrl+E to enter the
Emulex BIOS setup screen, or press Ctrl+Q or Alt+Q to enter the QLogic BIOS setup
screen.
● In UEFI mode, configure SAN Boot for FC HBA using Device Manager on the front screen.
For details, see the user manual of corresponding BIOS platform.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 67

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

[Link] Configuring SAN Boot for Emulex FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of the Emulex FC HBA and configure the SAN Boot
of the FC HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 6-2 is displayed,
press Alt+E or Ctrl+E to enter the BIOS Setup screen.

Figure 6-2 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 6-3 Selecting a port for SAN Boot (FC mode)

Step 4 On the screen displayed in Figure 6-4, select Enable/Disable Boot from SAN and
press Enter to access the SAN Boot enabling option screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 68

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-4 SAN Boot configuration screen

Step 5 Select Enable and press Enter to enable SAN Boot. By default, SAN Boot is
disabled.

Figure 6-5 Enabling SAN Boot

Step 6 (Optional) Scan for disk arrays.

1. Press Esc to go back to the screen shown in Figure 6-4.
2. Select Scan for Target Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 6-6.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 69

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-6 Disk array information

Step 7 Configure the SAN Boot device.

1. Press Esc to go back to the screen shown in Figure 6-4.
2. Select Configure Boot Devices, and press Enter.

Step 8 Select a boot option, and press Enter.

If no boot device is configured, no disk array information is displayed, as shown in

Figure 6-7.

Figure 6-7 Selecting a boot option

Step 9 Select a boot entry, and press Enter, as shown in Figure 6-8.

NO TE

A boot entry specifies the device for SAN Boot. If you select Clear selected boot entry and
press Enter, the SAN Boot configuration of the selected boot entry is cleared.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 70

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-8 Selecting a boot entry

Step 10 Set the starting logical unit number (LUN) by pressing the up and down arrow keys,
and press Enter.

Figure 6-9 Setting the starting LUN

Step 11 Select an LUN for SAN Boot, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 71

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-10 Selecting an LUN for SAN Boot

Step 12 Set the device boot mode and press Enter.

● WWPN is the WWN of the port on the disk array.
● DID is the N_Port_ID assigned to the port by the FC name server.

Figure 6-11 Setting the boot mode

Step 13 View the boot device information. If the status of a boot device is Used, as shown in
Figure 6-12, the boot device has been configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 72

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-12 Boot device sequence (one boot device)

You can use the same method to set more boot devices. Figure 6-13 shows the boot
device sequence when two boot devices are added.

Figure 6-13 Boot device sequence (two boot devices)

NO TE

You can select Reset Adapter Defaults in the screen shown in Figure 6-4 to restore the
default SAN Boot configurations.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 73

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 6-14 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 74

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-15 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 6-16.
NO TE

The default BIOS password is Admin@9000.

Figure 6-16 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 75

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The Front Page screen is displayed, as shown in Figure 6-17 or Figure 6-18.

Figure 6-17 Front Page screen (BIOS V3XX and earlier)

Figure 6-18 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 76

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The Device Manager screen is displayed.

Step 5 Select an FC HBA port, and press Enter.

Figure 6-19 Selecting an SAN Boot port

Step 6 In the screen shown in Figure 6-20, select Set Boot from SAN and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 77

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-20 SAN Boot configuration screen

Step 7 Select Enable and press Enter to enable SAN Boot.

Figure 6-21 Enabling SAN Boot

Step 8 Scan disk array information.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 78

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

1. Press Esc to go back to the screen shown in Figure 6-20.

2. Select Scan for Fibre Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 6-22.

Figure 6-22 Disk array information

Step 9 Add the SAN Boot device.

1. Press Esc to go back to the screen shown in Figure 6-20.
2. Select Add Boot Device, and press Enter.
Select a scanned disk array and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 79

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-23 Selecting a disk array

3. Select a logical unit number (LUN) for the boot device to be set and press Enter.

Figure 6-24 Selecting an LUN for SAN Boot

4. Select Commit Changes, and press Enter.

The boot device is added.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 80

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-25 Committing changes

Step 10 (Optional) Delete a SAN boot device.

1. Press Esc to go back to the screen shown in Figure 6-20.
2. Select Delete Boot Device, and press Enter.
3. Select the boot device to be deleted, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 81

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-26 Selecting the boot device to be deleted

4. Select DELETE, and press Enter.

Figure 6-27 Deleting a boot device

5. Select Commit Changes, and press Enter.

The boot device is deleted.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 82

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-28 Committing changes

Step 11 (Optional) Change the boot device order.

1. Press Esc to go back to the screen shown in Figure 6-20.
2. Select Change Boot Device Order, and press Enter.
3. Select Boot Device Order, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 83

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-29 Selecting the boot device order

4. Select a boot device and press F5 (moving downwards) or F6 (moving upwards)

to change the boot device order.
5. Then, press Tab to select OK and press Enter.

Figure 6-30 Changing the boot device order

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 84

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

6. Select Commit Changes, and press Enter. The boot device order is changed
successfully.

Figure 6-31 Committing changes

----End

[Link] Configuring SAN Boot for Qlogic FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of Qlogic and configure the SAN Boot of the FC
HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 6-32 is displayed,
press Ctrl+Q or Alt+Q to enter the BIOS Setup screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 85

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-32 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 6-33 Selecting a port for SAN Boot

Step 4 Select Configuration Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 86

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-34 Port configuration screen

Step 5 Select Adapter Settings, and press Enter.

Figure 6-35 Configuration Settings screen

Step 6 Set Host Adapter BIOS to Enabled. By default, SAN Boot is disabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 87

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-36 Adapter Settings screen

Step 7 Press Esc to go back to the Configuration Settings screen.

Step 8 Select Selectable Boot Settings, and press Enter.

Figure 6-37 Configuration Settings screen

Step 9 Set Selectable Boot to Enabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 88

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-38 Selectable Boot Settings screen

Step 10 Select a boot option, and press Enter.

Figure 6-39 Selecting a boot option

Step 11 Select a boot entry, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 89

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-40 Selecting a boot entry

Step 12 Set the starting LUN by pressing the up and down arrow keys, and press Enter.

Figure 6-41 Setting the starting LUN

Step 13 View the boot device information. If the boot device is displayed in the Selectable
Boot Settings screen, as shown in Figure 6-42, the boot device has been
configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 90

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-42 Boot device sequence

Step 14 Press Esc to go back to the screen shown in Figure 6-37.

Step 15 Press Esc. A confirmation dialog is displayed.

Figure 6-43 Confirmation dialog

Step 16 Select Save changes, and press Enter.

Step 17 Press Esc to exit. The SAN Boot configuration is complete.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 91

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 6-44 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 92

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-45 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 6-46.
NO TE

The default BIOS password is Admin@9000.

Figure 6-46 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 93

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The Front Page screen is displayed, as shown in Figure 6-47 or Figure 6-48.

Figure 6-47 Front Page screen (BIOS V3XX and earlier)

Figure 6-48 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.
The Device Manager screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 94

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 5 Select Network Device List, and press Enter.

Step 6 Select an FC HBA port, and press Enter.

Figure 6-49 Device Manager screen

Step 7 Select Boot Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 95

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-50 Selecting Boot Settings

Step 8 Select Adapter Driver, and press Enter.

Figure 6-51 Boot Settings screen

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 96

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 9 Select Enabled and press Enter to enable SAN Boot.

Figure 6-52 Enabling SAN Boot

Step 10 Press Esc twice to return to the Device Manager screen, exit the FC HBA setup
screen, and save the SAN Boot settings.

----End

6.2 Loading Drivers

6.2.1 Legacy Mode

NO TE

For details about how to load drivers when installing CentOS and Oracle Linux, see [Link]
RHEL.

[Link] SLES
The installation GUI varies with OSs. This section describes how to load the driver
when installing the SLES 12 series.

Step 1 On the OS installation wizard page, select Installation, press F6, and select Yes.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 97

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 2 Enter startup parameters in the Boot Options text box and press Enter to install the
system.

Step 3 Load the driver.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 98

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

NO TE

● The following describes how to mount a driver image in the ISO format to a virtual DVD-
ROM drive. If the driver image is in the IMG format, use the virtual floppy drive to mount the
image. When loading the driver, select the corresponding floppy drive device instead of the
DVD-ROM drive sr0.
● To mount multiple drivers, replace the image and repeat this step.

1. Eject the OS image from the virtual DVD-ROM drive and insert the driver image.
2. Select OK and press Enter.

The driver starts to be loaded.

After the driver is loaded, the following interface is displayed again.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 99

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 4 After the driver is loaded, eject the driver image from the virtual DVD-ROM drive,
insert the system image again, and click Back to continue the system installation.

----End

[Link] RHEL
The installation GUI varies with OSs. This section describes how to load the driver
when installing the RHEL 7 series.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 100

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 1 On the OS installation wizard page, select Install Red H Enterprise Linux and press
Tab.

Step 2 Enter Linux dd and press Enter.

You can see the DVD-ROM drive and floppy drive devices as follows.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 101

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 3 Load the driver.

NO TE

● The following describes how to mount driver images in the ISO and IMG formats. Use a
virtual DVD-ROM drive to mount the ISO driver image, and use a virtual floppy drive to
mount the IMG driver image.
● To mount multiple drivers, replace the image and repeat this step.
● ISO driver image:
1. Eject the system image from the virtual DVD-ROM drive and insert the driver
image.
2. Press r to refresh the page.

3. Enter 1 and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 102

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

4. Enter 1 and press Enter.

5. Enter C and press Enter.

The driver starts to be loaded.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 103

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

6. To continue loading the driver, replace the driver image, enter r, and press
Enter. Otherwise, eject the driver image from the virtual DVD-ROM drive, insert
the system image again, enter r, and press Enter.

● IMG driver image:

1. Insert the driver image into the virtual floppy drive.
2. Enter 2 and press Enter.
NO TE

Select sd* device for the virtual floppy drive according to the actual environment. sda is
used as an example here.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 104

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

3. Enter 1 and press Enter.

4. Enter C and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 105

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

5. To continue loading the driver, replace the driver image, enter r, and press
Enter.
Step 4 Enter C and press Enter to continue the system installation.

----End

6.2.2 UEFI Mode

NO TE

For details about how to load drivers when installing CentOS and Oracle Linux, see [Link]
RHEL.

[Link] SLES
NO TE

The following describes how to mount a driver image in the ISO format to a virtual DVD-ROM
drive. If the driver image is in the IMG format, use a virtual floppy drive to mount it.

The installation GUI varies with OSs. This section describes how to load the driver
when installing the SLES 12 series.

Step 1 On the OS installation wizard page, select Installation, and press E.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 106

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 2 Add linux dud=1 to the end of the linuxefi line and press Ctrl+x or F10 to restart the
server.

Step 3 Eject the system image from the virtual DVD-ROM drive, insert the ISO driver image,
select the CD-ROM drive, select OK and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 107

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The driver starts to be loaded.

After the driver is loaded, the following interface is displayed again.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 108

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

NO TE

To mount multiple drivers, replace the image and repeat this step.

Step 4 After the driver is loaded, eject the driver image from the virtual DVD-ROM drive,
insert the system image again, and click Back to continue the system installation.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 109

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

[Link] RHEL
The installation GUI varies with OSs. This section describes how to load the driver
when installing the RHEL 7 series.

Step 1 On the OS installation wizard page, select Install Red Hat Enterprise Linux 7.0,
and press E.

Step 2 Add linux dd at the end of the linuxefi line and press Ctrl+x.
NO TE

RHEL 9.4 requires adding [Link] at the end of the linuxefi line.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 110

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

You can see the DVD-ROM drive and floppy drive devices as follows.

Step 3 Load the driver.

NO TE

● The following describes how to mount driver images in the ISO and IMG formats. Use a
virtual DVD-ROM drive to mount the ISO driver image, and use a virtual floppy drive to
mount the IMG driver image.
● To mount multiple drivers, replace the image and repeat this step.
● If the server management software is xFusionBMC, log in to the xFusionBMC WebUI and
mount the ISO file on the Remote Control > Local Virtual Media page.
● ISO driver image:
1. Eject the system image from the virtual DVD-ROM drive and insert the driver
image.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 111

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

2. Press r to refresh the page.

3. Enter 1 and press Enter.

4. Enter 1 and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 112

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

5. Enter C and press Enter.

The driver starts to be loaded.

6. To continue loading the driver, replace the driver image, enter r, and press
Enter. Otherwise, eject the driver image from the virtual DVD-ROM drive, insert
the system image again, enter r, and press Enter.

● IMG driver image:

1. Insert the driver image into the virtual floppy drive.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 113

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

2. Enter 2 and press Enter.

NO TE

Select sd* device for the virtual floppy drive according to the actual environment. sda is
used as an example here.

3. Enter 1 and press Enter.

4. Enter C and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 114

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

5. To continue loading the driver, replace the driver image, enter r, and press
Enter.
Step 4 Enter C and press Enter to continue the system installation.

----End

6.2.3 Ubuntu
NO TE

● The driver is loaded in the same way during the installation of Debian and Ubuntu.
● The driver is loaded in the same way during the Ubuntu installation in the Legacy and UEFI
modes.

The Ubuntu driver needs to be loaded twice, that is, during the OS installation and
before the system reboot.
Perform the following steps to load the driver:

Step 1 Complete operations in section [Link] Loading RAID Controller Card Drivers
During OS Installation.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 115

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 2 Complete operations in section [Link] Installing the RAID Controller Card Driver
Before OS Reboot.

----End

[Link] Loading RAID Controller Card Drivers During OS Installation

If the OS does not contain a built-in RAID controller card driver configured in the
environment, a message is displayed during installation indicating that drives cannot
be detected. You are required to load the driver to identify drives and continue the
installation.

[Link].1 ISO Driver

Step 1 Press Ctrl+Alt+F2 on the KVM.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 116

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 2 Go to the following interface and press Enter.

Go to the following interface.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 117

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 3 Run the umount /dev/sr0 command to unmount sr0.

Step 4 On the KVM console, eject the system ISO image from the virtual DVD-ROM drive
and insert the RAID controller card ISO image.

Step 5 Create a folder, for example, raid_driver, and mount the driver image (if the
message "Device or resource busy" is displayed, run the mount command again).
Copy the driver file to the created raid_driver folder and switch to the created
directory.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 118

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 6 Query the driver module information and check whether the driver has dependent
modules as follows:
● megaraid_sas.ko driver: Go to the raid_driver driver directory and run the
modinfo megaraid_sas.ko | grep -i depends command. The value of depends
is empty as follows.

● [Link] driver: Go to the raid_driver driver directory and run the modinfo
[Link] | grep -i depends command. The modules scsi_transport_sas
and raid_class dependency modules are displayed in the value of depends as
follows.

Step 7 Load the depends driver module list (if the depends module list is empty, you do not
need to load dependency modules). Insert the RAID controller card driver module as
follows:
● megaraid_sas.ko driver: If the depends module list is empty, directly insert the
megaraid_sas.ko driver.
insmod megaraid_sas.ko

● [Link] driver: If modules scsi_transport_sas and raid_class are

displayed in the depends list, load the dependency modules first.
modprobe scsi_transport_sas
modprobe raid_class
insmod [Link]

Step 8 Run the ls command to query drives.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 119

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 9 Run the umount /dev/sr0 command to unmount sr0.

Step 10 On the KVM console, eject the driver ISO image from the virtual DVD-ROM drive and
insert the system ISO image.

Step 11 Run the mount /dev/sr0 /cdrom command. If the message "Device or resource
busy" is displayed, run the mount command again.

Step 12 Press Ctrl+Alt+F1 on the KVM.

Go back to the installation GUI.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 120

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Step 13 Press Enter to go to the drive partitioning page. Continue the installation from drive
partitioning.

----End

[Link] Installing the RAID Controller Card Driver Before OS Reboot

After the installation is completed, the following page is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 121

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

If the RAID controller card driver is loaded during the OS installation, when you click
Continue to boot the OS, the system fails to be booted as follows.

You are required to install the RAID controller card driver as follows:

Step 1 Press Ctrl+Alt+F2 on the KVM.

Step 2 Run the following command to install the RAID controller card driver.
1. Run the cp /raid_driver/* /target/root/ command to copy the RAID controller
card driver to the/target/root directory.
2. Run the chroot /target command to change the /target directory as the root
directory.

3. Run the dpkg –i /root/ [Link] command to install the RAID controller card deb
driver (replace [Link] with the complete name of the actual deb driver). The
following uses megaraid_sas and mpt3sas drivers as examples. You can install
other drivers by referring to the examples.
– megaraid_sas

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 122

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

– mpt3sas

Step 3 Press Ctrl+Alt+F1 on the KVM.

Go back to the GUI, click Continue, and press Enter to reboot the system.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 123

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

6.3 Installing the OS

This section describes how to install RHEL 6.5 by loading the SoftRAID driver. The
operation procedure is similar for other types of RAID controller card drivers.

For details about how to install other OSs, see the corresponding server OS
installation guide cases.

The installation methods vary according to the OS type. For details, visit the OS
official websites.

Procedure
Step 1 Prepare a new or a formatted drive.

Step 2 Obtain the SoftRAID driver installation package.

For details, see 6.1.1 Obtaining the OS Installation Material.

Step 3 Set the DVD-ROM drive as the boot device.

On the WebUI of the management software, set the DVD-ROM drive as the boot
device by performing the following operations.

● On the iBMC WebUI, choose Configuration > Boot Device and set Boot
Medium as DVD-ROM, or choose System > BIOS Settings > Boot Device and
set Preferred Boot Medium as DVD-ROM drive.
NO TE

The WebUI varies depending on the iBMC version. For details, see the iBMC user guide
of corresponding server model.
● On the iMana 200 WebUI, choose Configuration > System Configuration >
System Boot Option, and set System Boot Option to CD/DVD.

Step 4 Load the OS installation DVD-ROM or image file.

NO TE

If the server management software is xFusionBMC, log in to the xFusionBMC WebUI and
mount the ISO file on the Remote Control > Local Virtual Media page.

1. Perform one of the following operations based on the installation media:

– If you use an OS installation DVD-ROM, insert the DVD-ROM into the
physical DVD-ROM drive and skip Step 4.2.
If you use an ISO file, skip Step 4.3.
If you use an IMG file, perform Step 4.3.
– If you use an OS image file, perform Step 4.2.
If you use an ISO file, skip Step 4.3.
If you use an IMG file, perform Step 4.3.
2. Mount the virtual DVD-ROM drive.

a. On the toolbar of the remote virtual console, click .

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 124

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure

6-53.

Figure 6-53 Virtual DVD-ROM drive dialog box

b. Select Image File and click Browse.

The Open dialog box is displayed.
c. Select the OS ISO image file and click Open.
d. In the virtual DVD-ROM drive dialog box, click Connect.
When Connect changes to Disconnect (as shown in Figure 6-54), the
virtual DVD-ROM drive is successfully connected to the server.

Figure 6-54 Connection created

3. Mount the virtual floppy drive.

a. On the toolbar of the remote virtual console, click .

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure
6-55.

Figure 6-55 Virtual floppy drive dialog box

b. Deselect Write Protect.

c. Select Image File and click Browse.
The Open dialog box is displayed.
d. Select the driver installation package for the RAID controller card, and click
Open.
e. In the virtual floppy drive dialog box, click Connect.
When Connect changes to Disconnect, the virtual floppy drive is
connected to the server.
Step 5 Restart the server.

1. On the toolbar, click to restart the server.

A confirmation dialog box is displayed.
2. Click Yes.
The server reboots. The Welcome to Red Hat Enterprise Linux 6.5 screen is
displayed, as shown in Figure 6-56.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 125

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-56 RHEL 6.5 boot screen

Step 6 Install the OS.

1. Select Install or upgrade an existing system by pressing arrow keys.
2. Press Tab to edit options.
Enter a space in the end, enter linux dd blacklist=ahci nodmraid, and press
Enter.
The Welcome to Red Hat Enterprise Linux screen is displayed, as shown in
Figure 6-57.

Figure 6-57 Welcome screen

3. If the driver package is an IMG file, select Yes on the Driver disk window and
press Enter. The Driver Disk Source window is displayed, as shown in Figure
6-58. Select sda and press Enter. Then, select OK and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 126

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

If the driver package is an ISO file, click Disconnect, click Browse, select the
driver file, and click Connect. On the Driver disk window, select Yes and press
Enter.
The Driver Disk Source window is displayed, as shown in Figure 6-58.

Figure 6-58 Driver Disk Source window

4. On the displayed Insert Driver Disk window, select OK and press Enter.
The driver is automatically loaded. The loading is complete if the More Driver
Disks window is displayed, as shown in Figure 6-59.

Figure 6-59 More Driver Disks window

5. If the driver package is an IMG file, select No on the More Driver Disks window
and press Enter. The Disc Found window is displayed.
If the driver package is an ISO file, click Disconnect, click Browse, select the
OS file, and click Connect. On the More Driver Disks window, select NO and
press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 127

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

The Disc Found screen is displayed, as shown in Figure 6-60.

Figure 6-60 Disc Found window

6. Select Skipand press Enter.

The welcome screen is displayed.
7. Click Next.
The language selection screen is displayed.
8. Select language and click Next. English (English) is selected as an example.
The keyboard layout selection screen is displayed.
9. Select keyboard layout and click Next. U.S. English is selected as an example.
The installation device selection screen is displayed, as shown in Figure 6-61.

Figure 6-61 Selecting a device for installation

10. Select the installation device according to the actual situation and click Next.
Select Basic Storage Devices in this example.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 128

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

After the device is initialized, the host name setting screen is displayed, as
shown in Figure 6-62.

Figure 6-62 Setting the host name

11. Enter the host name and click Next.

The time zone setting screen is displayed, as shown in Figure 6-63.

Figure 6-63 Setting the time zone

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 129

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

12. Select a city and click Next.

– If System clock uses UTC is selected, the UTC is used as the system time.
– If System clock uses UTC is deselected, the local time is used as the
system time.
The screen shown in Figure 6-64 is displayed, prompting you to set the
password for the root user.

Figure 6-64 Setting the root user password

13. Enter the root user password twice and click Next.
The installation method selection screen is displayed, as shown in Figure 6-65.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 130

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-65 Selecting an installation mode

14. Select an installation method as required and click Next. Create Custom
Layout is selected as an example in this section.
NO TE

You can select the installation method as required.

– Manual partitioning: Select Create Custom Layout.
– Automatic partitioning: Select Use All Space, Replace Existing Linux System(s),
Shrink Current System, or Use Free Space according to the actual situation.
15. Create drive partitions.
If the OS is to be installed on the first drive, create partitions on the sda drive.
Table 6-1 describes how to create and delete drive partitions.

Table 6-1 Creating and deleting drive partitions

Operation Procedure

(Optional) Select a drive and click Delete to delete the existing partitions.
Delete
existing
partitions.

Create a root 1. Select the drive where the root partition is to be created,
partition. and click Create.
2. In the Create Storage dialog box, select Standard
Partition and click Create.
3. Set Mount Point to /, and File system Type to Ext4. Set
the capacity to 20 GB.
4. Click OK.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 131

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Operation Procedure

Create a 1. Select the drive where the root partition is to be created,

swap and click Create.
partition. 2. In the Create Storage dialog box, select Standard
Partition and click Create.
3. Set File system to Swap. Set the capacity to 4 GB.
4. Set Mount Point to swap.
5. Click OK.

16. Click Next.

The Format Warnings dialog box is displayed.
17. Click Format.
The Writing storage configuration to disk dialog box is displayed, as shown in
Figure 6-66.

Figure 6-66 Confirming the configuration

18. Click Write changes to disk.

The partition list is displayed.
19. Click Next.
The Boot loader screen is displayed, as shown in Figure 6-67.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 132

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-67 Boot loader screen

20. Select Install boot loader on /dev/sda and click Next.

The software selection screen is displayed, as shown in Figure 6-68.

Figure 6-68 Software selection screen

21. Select Software Development Workstation and the required software.

22. Select Customize later at the lower left corner, and click Next.
The file copying progress is displayed, as shown in Figure 6-69.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 133

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-69 Copying file

23. After the copying is complete, click Reboot in the reboot confirmation screen.
After the reboot is complete, the Welcome screen is displayed, as shown in
Figure 6-70.

Figure 6-70 Welcome screen

24. Click Forward.

The License Information screen is displayed.
25. Select Yes, I agree to the License Agreement to agree to the license
agreement.
26. Click Forward.
The Set Up Software Updates screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 134

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

27. Select No, I prefer to register at a later time. to register subscription

information later and click Forward.
A confirmation dialog box is displayed.
28. Click Register Later to confirm.
The Finish Updates Setup screen is displayed.
29. Click Forward.
The Create User screen is displayed, as shown in Figure 6-71.

Figure 6-71 Creating a user

30. Set user information and click Forward.

The Date and Time screen is displayed, as shown in Figure 6-72.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 135

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

Figure 6-72 Setting the date and time

31. Set the date and time and click Forward.

The Kdump screen is displayed, as shown in Figure 6-73.

Figure 6-73 Configuring kdump

32. Deselect Enable Kdump and set the parameter as required.

33. Click Finish.
A confirmation dialog box is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 136

Server 6 Installing an OS by Loading a RAID Controller Card
OS Installation Guide Driver

34. Click Yes.

The OS reboots. After the reboot is complete, the RHEL 6.5 OS is displayed.

----End

NO TE

After the OS is installed, check whether the existing driver versions match the OS. If the driver
versions do not match, install the drivers of the required versions. For details, see 8 Installing
and Upgrading Drivers and Firmware. You are advised to configure the OS fault locating
function. For details, see 10 Locating OS Faults.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 137

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

7 Installing an OS by Creating an
Installation Source

This installation method applies only to VMware ESXi OSs. The drivers for OS
installation are encapsulated into an ISO image file for OS installation.
For details about how to install other OSs, see the corresponding server OS
installation guide cases.
7.1 Preparing for Installation
7.2 Installing an OS by Creating an Installation Source

7.1 Preparing for Installation

7.1.1 Obtaining the OS Installation Material

Procedure
Step 1 Obtain the OS installation DVD-ROM or image file.
Prepare the OS installation DVD-ROM or image file in advance.
Step 2 Query compatible OSs.
1. Access the compatibility list on the technical support website.
2. Select the server type.
The compatibility query page is displayed.
3. Click the Search OSs tab.
4. Based on the actual hardware configuration of the server, select the
corresponding parts and query the OS compatibility of the specified server.
Step 3 Download the driver version mapping table.
1. Visit the Technical Support Website > Software Download > FusionServer
iDriver.
2. On the Software Download tab page, click the required version to go to the
corresponding page.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 138

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

3. In the Documentation area, download the required driver version mapping

table.
The table describes the mapping between OSs and drivers or firmware.
NO TE

The driver version mapping table records all the parts whose drivers can be upgraded in
the OS and the corresponding driver and firmware information. If the driver and firmware
information of a part cannot be found, the OS is not compatible with the part.

Step 4 Download the driver installation package.

1. Access the compatibility list on the technical support website.
2. Select the server type.
The compatibility query page is displayed.
3. Click the Search Parts tab.
4. Select the product model and part type to query the part compatibility of the
specified server.
5. Click Search.
The part compatibility list is displayed, as shown in Figure 7-1.

Figure 7-1 Part compatibility list

6. Click Link in the Drivers column.

Go to the download path.
7. Download the required driver installation package by referring to the driver
mapping table.

NO TE

To avoid using software packages that have been tampered with during transmission or
storage, download their digital signature files for integrity check while downloading the
software packages.
After the software package is downloaded from the technical support website, verify its PGP
digital signature. See the OpenPGP Signature Verification Guide. If the software package fails
the verification, do not use the software package, and contact technical support.
Before using a software package in installation or update, verify its digital signature according
to the OpenPGP signature verification guide to ensure that the software package is not
tampered with.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 139

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

7.1.2 Configuring RAID

Procedure
Step 1 Configure RAID.

Different RAID controller cards support different RAID configurations. For details, see
the RAID controller card user guide of corresponding server model.

Step 2 Configure the boot option.

● If you have configured multiple RAID groups or a RAID group with multiple
virtual drives (VDs), you must set the boot device. Otherwise, the OS installation
may become abnormal.
Different RAID controller cards support different RAID configurations. For details,
see the RAID controller card user guide of corresponding server model.
● If multiple RAID controller cards (including SoftRAID) are configured, access the
Boot tab on the BIOS screen and set a RAID controller card as the boot device.
Parameter names vary between different BIOS platforms. For details about the
parameters, see the BIOS parameter reference of corresponding server model.

----End

7.1.3 Setting the BIOS System Time and Boot Device

NO TE

Set the boot device through iBMC. For details, see the iBMC user guide of corresponding
server model.

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

7.1.4 (Optional) Setting UEFI Secure Boot

The BIOS screen varies depending on the platform. For details, see the BIOS
parameter reference of corresponding server model.

7.1.5 (Optional) Configuring SAN Boot for FC HBA

To use a FC HBA and boot the OS from storage area network (SAN), configure SAN
Boot for FC HBA before installing an OS.

NO TE

The operation procedure varies depending on the BIOS platform. For Purley, Cedar Island,
Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley, Brickland, and Romley,
the default boot type is Legacy.
● In Legacy mode, during power-on self-test (POST), press Alt+E or Ctrl+E to enter the
Emulex BIOS setup screen, or press Ctrl+Q or Alt+Q to enter the QLogic BIOS setup
screen.
● In UEFI mode, configure SAN Boot for FC HBA using Device Manager on the front screen.
For details, see the user manual of corresponding BIOS platform.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 140

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

[Link] Configuring SAN Boot for Emulex FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of the Emulex FC HBA and configure the SAN Boot
of the FC HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 7-2 is displayed,
press Alt+E or Ctrl+E to enter the BIOS Setup screen.

Figure 7-2 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 7-3 Selecting a port for SAN Boot (FC mode)

Step 4 On the screen displayed in Figure 7-4, select Enable/Disable Boot from SAN and
press Enter to access the SAN Boot enabling option screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 141

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-4 SAN Boot configuration screen

Step 5 Select Enable and press Enter to enable SAN Boot. By default, SAN Boot is
disabled.

Figure 7-5 Enabling SAN Boot

Step 6 (Optional) Scan for disk arrays.

1. Press Esc to go back to the screen shown in Figure 7-4.
2. Select Scan for Target Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 7-6.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 142

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-6 Disk array information

Step 7 Configure the SAN Boot device.

1. Press Esc to go back to the screen shown in Figure 7-4.
2. Select Configure Boot Devices, and press Enter.

Step 8 Select a boot option, and press Enter.

If no boot device is configured, no disk array information is displayed, as shown in

Figure 7-7.

Figure 7-7 Selecting a boot option

Step 9 Select a boot entry, and press Enter, as shown in Figure 7-8.

NO TE

A boot entry specifies the device for SAN Boot. If you select Clear selected boot entry and
press Enter, the SAN Boot configuration of the selected boot entry is cleared.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 143

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-8 Selecting a boot entry

Step 10 Set the starting logical unit number (LUN) by pressing the up and down arrow keys,
and press Enter.

Figure 7-9 Setting the starting LUN

Step 11 Select an LUN for SAN Boot, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 144

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-10 Selecting an LUN for SAN Boot

Step 12 Set the device boot mode and press Enter.

● WWPN is the WWN of the port on the disk array.
● DID is the N_Port_ID assigned to the port by the FC name server.

Figure 7-11 Setting the boot mode

Step 13 View the boot device information. If the status of a boot device is Used, as shown in
Figure 7-12, the boot device has been configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 145

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-12 Boot device sequence (one boot device)

You can use the same method to set more boot devices. Figure 7-13 shows the boot
device sequence when two boot devices are added.

Figure 7-13 Boot device sequence (two boot devices)

NO TE

You can select Reset Adapter Defaults in the screen shown in Figure 7-4 to restore the
default SAN Boot configurations.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 146

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 7-14 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 147

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-15 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 7-16.
NO TE

The default BIOS password is Admin@9000.

Figure 7-16 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 148

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

The Front Page screen is displayed, as shown in Figure 7-17 or Figure 7-18.

Figure 7-17 Front Page screen (BIOS V3XX and earlier)

Figure 7-18 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 149

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

The Device Manager screen is displayed.

Step 5 Select an FC HBA port, and press Enter.

Figure 7-19 Selecting an SAN Boot port

Step 6 In the screen shown in Figure 7-20, select Set Boot from SAN and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 150

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-20 SAN Boot configuration screen

Step 7 Select Enable and press Enter to enable SAN Boot.

Figure 7-21 Enabling SAN Boot

Step 8 Scan disk array information.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 151

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

1. Press Esc to go back to the screen shown in Figure 7-20.

2. Select Scan for Fibre Devices, and press Enter.
If the FC HBA is successfully connected to disk arrays, information about the
disk arrays is displayed, as shown in Figure 7-22.

Figure 7-22 Disk array information

Step 9 Add the SAN Boot device.

1. Press Esc to go back to Figure 7-20.
2. Select Add Boot Device, and press Enter.
Select a scanned disk array and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 152

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-23 Selecting a disk array

3. Select a logical unit number (LUN) for the boot device to be set and press Enter.

Figure 7-24 Selecting an LUN for SAN Boot

4. Select Commit Changes, and press Enter.

The boot device is added.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 153

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-25 Committing changes

Step 10 (Optional) Delete a SAN boot device.

1. Press Esc to go back to the screen shown in Figure 7-20.
2. Select Delete Boot Device, and press Enter.
3. Select the boot device to be deleted, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 154

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-26 Selecting the boot device to be deleted

4. Select DELETE, and press Enter.

Figure 7-27 Deleting a boot device

5. Select Commit Changes, and press Enter.

The boot device is deleted.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 155

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-28 Committing changes

Step 11 (Optional) Change the boot device order.

1. Press Esc to go back to the screen shown in Figure 7-20.
2. Select Change Boot Device Order, and press Enter.
3. Select Boot Device Order, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 156

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-29 Selecting the boot device order

4. Select a boot device and press F5 (moving downwards) or F6 (moving upwards)

to change the boot device order.
5. Then, press Tab to select OK and press Enter.

Figure 7-30 Changing the boot device order

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 157

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

6. Select Commit Changes, and press Enter. The boot device order is changed
successfully.

Figure 7-31 Committing changes

----End

[Link] Configuring SAN Boot for Qlogic FC HBA

The operation procedure varies depending on the BIOS platform. For Purley, Cedar
Island, Whitley, and Eagle Stream, the default boot type is UEFI. For Grantley,
Brickland, and Romley, the default boot type is Legacy.

[Link].1 Configuring SAN Boot in Legacy Mode

Access the BIOS setting screen of Qlogic and configure the SAN Boot of the FC
HBA. The procedure is as follows:

Step 1 Log in to the BIOS, and set the Legacy boot type. For details, see 5.1.3 Setting the
BIOS System Time and Boot Device.
Step 2 Power on or reboot the server. When the screen shown in Figure 7-32 is displayed,
press Ctrl+Q or Alt+Q to enter the BIOS Setup screen.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 158

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-32 BIOS startup screen

Step 3 Select a port, and press Enter.

Figure 7-33 Selecting a port for SAN Boot

Step 4 Select Configuration Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 159

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-34 Port configuration screen

Step 5 Select Adapter Settings, and press Enter.

Figure 7-35 Configuration Settings screen

Step 6 Set Host Adapter BIOS to Enabled. By default, SAN Boot is disabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 160

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-36 Adapter Settings screen

Step 7 Press Esc to go back to the Configuration Settings screen.

Step 8 Select Selectable Boot Settings, and press Enter.

Figure 7-37 Configuration Settings screen

Step 9 Set Selectable Boot to Enabled.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 161

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-38 Selectable Boot Settings screen

Step 10 Select a boot option, and press Enter.

Figure 7-39 Selecting a boot option

Step 11 Select a boot entry, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 162

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-40 Selecting a boot entry

Step 12 Set the starting LUN by pressing the up and down arrow keys, and press Enter.

Figure 7-41 Setting the starting LUN

Step 13 View the boot device information. If the boot device is displayed in the Selectable
Boot Settings screen, as shown in Figure 7-42, the boot device has been
configured.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 163

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-42 Boot device sequence

Step 14 Press Esc to go back to the screen shown in Figure 7-37.

Step 15 Press Esc. A confirmation dialog is displayed.

Figure 7-43 Confirmation dialog

Step 16 Select Save changes, and press Enter.

Step 17 Press Esc to exit. The SAN Boot configuration is complete.

----End

[Link].2 Configuring SAN Boot in UEFI Mode

Go to the Device Manager screen and configure SAN Boot for an FC HBA. The
following uses the Purley BIOS as an example. The BIOS screens on different
platforms vary depending on the actual situation. The procedure is as follows:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 164

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Step 1 Log in to the BIOS, and set the boot type to UEFI Boot. For details, see 5.1.3
Setting the BIOS System Time and Boot Device.
Step 2 When the BIOS boot screen shown in the following figure is displayed, press the
corresponding shortcut key to go to the Front Page screen.
● BIOS V3XX and earlier: Press F11 or F3.
● BIOS V6XX and later: Press Delete or F4.

Figure 7-44 BIOS boot screen (V3XX and earlier)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 165

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-45 BIOS boot screen (V6XX and later)

Step 3 Enter the password as prompted and press Enter, as shown in Figure 7-46.
NO TE

The default BIOS password is Admin@9000.

Figure 7-46 Entering the password

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 166

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

The Front Page screen is displayed, as shown in Figure 7-47 or Figure 7-48.

Figure 7-47 Front Page screen (BIOS V3XX and earlier)

Figure 7-48 Front Page screen (BIOS V6XX and later)

Step 4 Select Device Manager using arrow keys, and press Enter.
The Device Manager screen is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 167

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Step 5 Select Network Device List, and press Enter.

Step 6 Select an FC HBA port, and press Enter.

Figure 7-49 Device Manager screen

Step 7 Select Boot Settings, and press Enter.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 168

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Figure 7-50 Selecting Boot Settings

Step 8 Select Adapter Driver, and press Enter.

Figure 7-51 Boot Settings screen

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 169

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

Step 9 Select Enabled and press Enter to enable SAN Boot.

Figure 7-52 Enabling SAN Boot

Step 10 Press Esc twice to return to the Device Manager screen, exit the FC HBA setup
screen, and save the SAN Boot settings.

----End

7.2 Installing an OS by Creating an Installation Source

This section describes uses Vmware ESXi as an example to describe how to create
an installation source.

For details about how to install other OSs, see the corresponding server OS
installation guide cases.

7.2.1 Creating the VMware ESXi 6.X/7.X Installation Source

Overview
The ESXi-Customizer-PS script is a PowerShell script that greatly simplifies and
automates the use of the VMware PowerCLI Image Builder module, facilitating the
quick customization of VMware ESXi 6.X/7.X OS images.

Environment requirements
● Windows 10 OS (with built-in PowerShell)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 170

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

● VMware PowerCLI 5.1 or later.

Procedure
Step 1 Install VMware PowerCLI.
1. Download the VMware PowerCLI package. The download address is as follows:
[Link]

NO TE

To download the package, you need to log in and need to subscribe to VMware services.

2. Decompress the [Link] package downloaded

in Step 1.1 and copy the decompressed files to the C:\Program Files
\WindowsPowerShell\Modules directory.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 171

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

3. Open Windows PowerShell as an administrator, run the Set-ExecutionPolicy

RemoteSigned command to allow remote execution, and run the Import-
Module [Link] command to install VMware PowerCLI.

4. Run the following command to ignore certificate verification.

Set-PowerCLIConfiguration -Scope AllUsers -ParticipateInCeip $false -
InvalidCertificateAction Ignore

Step 2 Obtain the ESXi-Customizer-PS script.

1. Download the ESXi-Customizer-PS script.
Visit [Link] and click Download
ZIP.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 172

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

2. Decompress the [Link] package downloaded in Step

2.1.
3. Obtain the ESXi-Customizer-PS.ps1 script.

Step 3 Customize the VMware ESXi ISO image.

NO TE

Customizing the VMware ESXi ISO image requires ESXi offline bundle and driver offline
bundle.

Download the ESXi Offline Bundle.

1. Visit the BROADCOM technical support website (https://
[Link]).
NO TE

To download the package, you need a VMware account and need to subscribe to
VMware services.
2. Click Software, and click next to VMware Cloud Foundation, then click My
Downloads.
NO TE

To download the package, you need to log in and need to subscribe to VMware services.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 173

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

3. Click VMware vSphere.

4. Click VMware vSphere Enterprise Plus, select the target version.

5. On the Primary Downloads tab page, click View Group next to VMware
vSphere Hypervisor (ESXi).

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 174

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

6. Download the VMware vSphere Hypervisor (ESXi) Offline Bundle.

Step 4 Create an ISO image.

NO TE

The following describes how to add the Intel i40e NIC driver and LSI SAS3108 RAID controller
card driver to the ESXi 6.5 offline bundle. The method for adding other drivers to other ESXi
6.X/7.X versions is similar.

1. Create the ESXi_6.5_ISO folder.

2. Go to the ESXi_6.5_ISO folder and save the ESXi-Customizer-PS.ps1 script

and ESXi 6.5.0 U1 offline bundle update-from-esxi6.5-6.5_update01.zip to this
folder.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 175

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

3. Create the Drivers folder in the ESXi_6.5_ISO folder.

4. Place the NIC-X710_X722_XL710-ESXi6.5-i40en-1.7.11-x86_64.zip and

RAID-3004iMR_3108_3408iMR_3416iMR_3508_3516-ESXi6.5-
lsi_mr3-[Link]-x86_64.zip offline bundles in the Drivers folder.

5. Switch the Windows PowerShell working directory to C:\ESXi_6.5_ISO.

6. Run the following command to generate the ESXi ISO image.

.\ESXi-Customizer-PS.ps1 -izip .\update-from-esxi6.5-6.5_update01.zip -
pkgDir .\Drivers\

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 176

Server
OS Installation Guide 7 Installing an OS by Creating an Installation Source

The created ESXi ISO image is stored in the ESXi_6.5_ISO folder and can be
used to install the VMware ESXi system on a host.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 177

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

8 Installing and Upgrading Drivers and

Firmware

On different OSs, you can use Firmware and Driver Mapping Guide to check
whether the driver and firmware versions of the server components meet the
requirements in the version mapping table. If the versions do not meet the
requirements, install or upgrade the driver and firmware to ensure the normal running
of the server.

If the drivers or firmware to be installed are not described in the document, contact
technical support.
8.1 Preparing for Installation
8.2 Checking the Driver and Firmware Versions
8.3 Installing Drivers
8.4 Upgrading Firmware

8.1 Preparing for Installation

Before installing drivers and firmware, download the driver version mapping table,
driver software, and firmware.

NO TICE

● If the PCIe cards you use are not in the compatibility list, obtain the drivers,
firmware, and matching documentation from their official websites.
● Obtain the corresponding driver package and version mapping table according to
the server hardware configuration.
● You do not need to install drivers for the hardware devices that have not been
configured on the server.
● If the correct driver and firmware cannot be obtained by the following methods, or
the server still cannot identify the device after the drivers and firmware are
installed, contact the customer service center.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 178

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Procedure
Step 1 Download the driver version mapping table.
1. Visit the Technical Support Website > Software Download > FusionServer
iDriver.
2. On the Software Download tab page, click the required version to go to the
corresponding page.
3. In the Documentation area, download the required driver version mapping
table.
The table describes the mapping between OSs and drivers or firmware.
NO TE

The driver version mapping table records all the parts whose drivers can be upgraded in
the OS and the corresponding driver and firmware information. If the driver and firmware
information of a part cannot be found, the OS is not compatible with the part.

Step 2 Download the driver installation package.

1. Access the compatibility list on the technical support website.
2. Select the server type.
The compatibility query page is displayed.
3. Click the Search Parts tab.
4. Select the product model and part type to query the part compatibility of the
specified server.
5. Click Search.
The part compatibility list is displayed, as shown in Figure 8-1.

Figure 8-1 Part compatibility list

6. Click Link in the Drivers column.

Go to the download path.
7. Download the required driver installation package by referring to the driver
mapping table.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 179

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

NO TE

To avoid using software packages that have been tampered with during transmission or
storage, download their digital signature files for integrity check while downloading the
software packages.
After the software package is downloaded from the technical support website, verify its
PGP digital signature. See the OpenPGP Signature Verification Guide. If the software
package fails the verification, do not use the software package, and contact technical
support.
Before using a software package in installation or update, verify its digital signature
according to the OpenPGP signature verification guide to ensure that the software
package is not tampered with.

Step 3 Download the firmware.

1. Visit the Technical Support Website > Software Download > FusionServer
iDriver.
2. Click the required version to go to the corresponding page.
3. Select FW in the Software Type area.
4. View and download the firmware patch.

NO TE

The current Windows OS supports batch firmware upgrade using FusionServer Tools. For
details, see the corresponding version of FusionServer Tools user guide.
To avoid using software packages that have been tampered with during transmission or
storage, download their digital signature files for integrity check while downloading the
software packages.
After the software package is downloaded from the technical support website, verify its PGP
digital signature. See the OpenPGP Signature Verification Guide. If the software package fails
the verification, do not use the software package, and contact technical support.
Before using a software package in installation or update, verify its digital signature according
to the OpenPGP signature verification guide to ensure that the software package is not
tampered with.

----End

8.2 Checking the Driver and Firmware Versions

8.2.1 Checking Driver Versions on Windows

Check the current driver version of the Windows and determine whether to install the
driver.
The OS installation interfaces vary depending on the OS. This section describes how
to check driver versions in Windows Server 2019.

Procedure
Step 1 Log in to the virtual console of the server.
For details, see 9.2 Logging In to the Virtual Console.
Step 2 Log in to the server OS.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 180

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Step 3 Enter Windows PowerShell in the search box on the Start menu and press Enter.
The Windows PowerShell window is displayed, as shown in Figure 8-2.

Figure 8-2 Windows PowerShell window

Step 4 Enter devmgmt in the Windows PowerShell window.

The Device Manager window is displayed, as shown in Figure 8-3.

Figure 8-3 Device Manager window

Step 5 Expand Network adapters.

Step 6 Double-click the NIC to be viewed, and click the Driver tab.
The driver information is displayed, as shown in Figure 8-4.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 181

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Figure 8-4 Driver information

Step 7 Check whether the driver version is the one specified in the Driver Version Mapping.
● If yes, no further action is required.
● If no, uninstall the driver, and then install the driver of the correct version.

----End

8.2.2 Checking Driver and Firmware Versions on Linux

Check the current driver and firmware versions of Linux to determine whether to
install the driver and upgrade the firmware.

This section describes how to check the board driver and firmware versions in RHEL
7.7.

Procedure
Step 1 Log in to the virtual console of the server.

For details, see 9.2 Logging In to the Virtual Console.

Step 2 Mount the driver ISO file, for example, onboard_driver_RHEL7.[Link].

NO TE

If the server management software is xFusionBMC, log in to the xFusionBMC WebUI and
mount the ISO file on the Remote Control > Local Virtual Media page.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 182

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

1. On the toolbar of the remote virtual console, click .

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure 8-5.

Figure 8-5 Virtual DVD-ROM drive dialog box

2. Select Image File and click Browse.

The Open dialog box is displayed.
3. Select the OS ISO image file and click Open.
4. In the virtual DVD-ROM drive dialog box, click Connect.
When Connect changes to Disconnect (as shown in Figure 8-6), the virtual
DVD-ROM drive is successfully connected to the server.

Figure 8-6 Connection created

Step 3 Log in to the server OS as user root.

Step 4 Run the mount command to manually mount the ISO file to the /mnt directory.
mount /dev/sr0 /mnt

Step 5 Run the following command to create a new file path to save the drivers, for
example, /root/driver.
mkdir /root/driver

Step 6 Run the cp command to copy all the ISO files to /root/driver.
cp -vr /mnt/* /root/driver

Step 7 Go to the /root/driver directory.

cd /root/driver

Step 8 Run the following commands.

chmod +x [Link]
./[Link]

The following information is displayed:

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 183

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Step 9 Enter 2.
The script automatically checks whether the current hardware driver versions are
compatible with each other and displays the check result.

NO TE

● The script also checks the firmware and driver versions. If the version information in the
Driver Version and Firmware Version columns is green, the firmware version is compatible
with the driver version. If the version information is red, upgrade the firmware or driver to
the version displayed after Target.
● For details about how to upgrade the firmware, see the upgrade guide of corresponding
server model.
● If yes, enter q to exit. No further action is required.
● If no, press any key, and enter 1 to upgrade the driver.
Step 10 Reboot the server. Then, repeat Step 1 to Step 9 to check the firmware and driver
versions.

----End

8.2.3 Checking Driver and Firmware Versions on VMware

Check the current driver and firmware versions of VMware to determine whether to
install the driver and upgrade the firmware.
This section describes how to check driver and firmware versions in VMware ESXi
7.0.

Procedure
Step 1 Decompress the NIC driver installation package, for example, FusionServer iDriver-
[Link].
Figure 8-7 shows the files generated after the decompression.

Figure 8-7 Decompressing the driver software package

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 184

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Figure 8-8 shows the files in the decompressed [Link] directory.

Figure 8-8 Driver files

Step 2 Log in to the server OS as the administrator.

NO TICE

If you log in to the OS over the service network port of a network adapter involved in
driver installation, the network connection will be disconnected and the driver
installation will fail.

Step 3 Press Alt+F1 to switch to CLI.

Step 4 Copy all files obtained in Step 1 to the /tmp directory on the server using a file
transfer tool (for example, SFTP).
Step 5 Go to the /tmp directory.
cd /tmp

Step 6 Run the following commands.

chmod +x [Link]
./[Link]

Step 7 Enter 2.
The script automatically checks whether the current hardware driver versions are
compatible with each other and displays the check result.

Step 8 Select an appropriate installation method based on the check result displayed in the
Mark column.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 185

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

● If the check result is as follows, the driver version is correct. Press any key and
enter q to exit.
OK

● If the check result is as follows, the driver version is incompatible. Press any key
and enter 1 for automatic driver upgrade.
please update this device's driver!

● If the check result is as follows, the driver does not exist. Press any key and
enter 1 for automatic driver installation.
please install this device's driver!

● If the check result is as follows, the driver does not support automatic
installation. Install the driver manually by following the instructions of the
readme_zh file in the FusionServer iDriver software package.
Current script does not support xxx! xxx Network Card must manual install driver.
Current script does not support ConnectX-4 pro!

● If the check result is as follows, the driver installation script is not compatible with
the system kernel. Download the driver installation package by following the
instructions in 8.1 Preparing for Installation.
The Install Script only support VMware ESXi xxx. Do not support ESXi xx.

NO TE

– The installation script also checks the firmware version. An error message will be
displayed if the firmware version is incorrect.
– For details about how to upgrade the firmware, see the upgrade guide of
corresponding server model.

Step 9 Reboot the server. Then, repeat Step 1 to Step 8 to check the firmware and driver
versions.

----End

8.3 Installing Drivers

NO TICE

During upgrade of the NIC driver, in-band and sideband services will be interrupted
for a short time. Back up network port services before the upgrade.

8.3.1 Installing Drivers on Windows

If the existing driver versions on a server are not those specified in the Driver Version
Mapping, install drivers of the required versions. If driver versions are incorrect, the
server may fail to function correctly.

This section describes how to install LSI SAS3008 RAID controller card drivers on
Windows server 2016. For details about how to install drivers of other components,
see the readme file in the FusionServer iDriver software package.

NO TE

If you are installing Windows Server 2016, install required system patches before installing
drivers. For details, see 10.8.7 How to Install a Windows Server 2016 Patch.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 186

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Procedure
Step 1 Decompress the driver software package.
1. Download and decompress the driver software package, for example,
FusionServer [Link].
2. Go to the win2k16 folder, and check for the onboard_driver_win2k16.iso and
[Link] files.
Figure 8-9 shows the files in the win2k16 folder.

Figure 8-9 Checking the files in the win2k16 folder

Step 2 Log in to the virtual console of the server.

For details, see 9.2 Logging In to the Virtual Console.

Step 3 Mount the ISO file.

1. On the toolbar of the remote virtual console, click .

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure 8-10.

Figure 8-10 Virtual DVD-ROM drive dialog box

2. Select Image File and click Browse.

The Open dialog box is displayed.
3. Select the OS ISO file, namely, onboard_driver_win2k16.iso, and click Open.
4. In the virtual DVD-ROM drive dialog box, click Connect.
When Connect changes to Disconnect (as shown in Figure 8-11), the virtual
DVD-ROM drive is successfully connected to the server.

Figure 8-11 Connection created

Step 4 Install the driver.

1. Create a folder in the system drive, for example, C:/iDriver.
2. Go to the CD Drive folder in the virtual DVD-ROM drive, as shown in Figure
8-12.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 187

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Figure 8-12 Files in the CD Driver folder

3. Copy all the files from the CD Driver folder to C:/iDriver.

4. Type cmd in the Run dialog box and press Enter to open the CLI.
5. Run the following command to go to the iDriver folder:
cd C:/iDriver
6. Stop the Server Manager program.
7. Run the following command (as an administrator or an account having
administrator rights) to install all drivers:
[Link] install "all"

NO TE

If only some drivers need to be installed, change the parameter all to their file names,
with each two file names separated by ,, for example, [Link] install
be3_iscsi_11.1.185.0-23_silence.exe, 3108_win2k16_x86_64_6.712.13.00_silence.exe.
8. Check the installation result.

– If Result is success, the driver is installed successfully.

"Result":"success","ErrorInfo":"NA"
– If Result is fail and ErrorInfo is as follows, the driver device does not exist.
Install the driver device by following the instructions in the user guide of your
server.
"Result":"fail","ErrorInfo":"can not find device 2208 raid card"

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 188

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

– If Result is fail and ErrorInfo is as follows, the driver installation package

does not exist. Download the driver installation package by following the
instructions in 8.1 Preparing for Installation.
"Result":"fail","ErrorInfo":"can not find the installation of driver XXX"

NO TE

For details, see the readme file in the FusionServer iDriver software package.

Step 5 Reboot the OS.

----End

8.3.2 Installing Drivers on Linux

If the existing driver versions on a server are not those specified in the Driver Version
Mapping, install drivers of the required versions. If driver versions are incorrect, the
server may fail to function correctly.
This section describes how to install the XP330 NIC driver on SLES 15 SP2. For
details about how to install driver of other components, see the readme file in the
FusionServer iDriver software package.

NO TE

The installation method described in this section is not applicable to the GPU driver of the
Linux OS. For details about how to install a GPU driver, see 10.8.8 Installing Drivers on
Linux.

Procedure
Step 1 Log in to the virtual console of the server.
For details, see 9.2 Logging In to the Virtual Console.
Step 2 Mount the ISO file, for example, onboard_driver_sles11sp1.iso.
NO TE

If the server management software is xFusionBMC, log in to the xFusionBMC WebUI and
mount the ISO file on the Remote Control > Local Virtual Media page.

1. On the toolbar of the remote virtual console, click .

The virtual DVD-ROM drive dialog box is displayed, as shown in Figure 8-13.

Figure 8-13 Virtual DVD-ROM drive dialog box

2. Select Image File and click Browse.

The Open dialog box is displayed.
3. Select the OS ISO image file and click Open.
4. In the virtual DVD-ROM drive dialog box, click Connect.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 189

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

When Connect changes to Disconnect (as shown in Figure 8-14), the virtual
DVD-ROM drive is successfully connected to the server.

Figure 8-14 Connection created

Step 3 Log in to the server OS as user root.

NO TICE

If you log in to the OS over the service network port of a network adapter involved in
driver installation, the network connection will be disconnected and the driver
installation will fail.

Step 4 Run the mount command to manually mount the ISO file to the /mnt directory.
mount /dev/sr0 /mnt

Step 5 Run the following command to create a new file path to save the drivers, for
example, /root/driver.
mkdir /root/driver

Step 6 Run the cp command to copy all the ISO files to /root/driver.
cp -vr /mnt/* /root/driver

Step 7 Go to the /root/driver directory.

cd /root/driver

Step 8 Run the following commands.

chmod +x [Link]
./[Link]

The following information is displayed:

Step 9 Enter 1.

The script automatically installs the required hardware drivers.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 190

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

● If the installation result is as follows, the driver is installed successfully.

"Result":"success","ErrorInfo":"NA"

● If the installation result is as follows, the driver installation has failed. Check the
log file for the detailed error information and take proper measures.
$ddri_name_install install failed,pls check ${mypwd}/log_install_failed.log

● If the installation result is as follows, the driver device does not exist. Install the
driver device by following the instructions in the server user guide.
Currently OS without install the gcc/make and kernel packages,pls install them and reference the [Link] under $
{mypwd} directory

● If the installation result is as follows, the driver does not support automatic
installation. Install the driver manually by following the instructions of the
readme_zh file in the FusionServer iDriver software package.
$ddri_devname must manual install $ddri_name driver
pls reference [Link] which in the driver package or OS installation guide to manually install drivers.

Step 10 Reboot the OS.

----End

8.3.3 Installing Drivers on VMware

If the existing driver versions on a server are not those specified in the Driver Version
Mapping, install drivers of the required versions. If driver versions are incorrect, the
server may fail to function correctly.

This section describes how to install the FC NIC drivers on VMware ESXi 7.0. For
details about how to install driver of other components, see the readme file in the
FusionServer iDriver software package.

Procedure
Step 1 Decompress the NIC driver installation package, for example, FusionServer iDriver-
[Link].

Figure 8-15 shows the files generated after the decompression.

Figure 8-15 Decompressing the driver software package

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 191

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

Figure 8-16 shows the files in the decompressed [Link] directory.

Figure 8-16 Driver files

Step 2 Log in to the server OS as the administrator.

NO TICE

If you log in to the OS over the service network port of a network adapter involved in
driver installation, the network connection will be disconnected and the driver
installation will fail.

Step 3 Press Alt+F1 to switch to CLI.

Step 4 Copy all files obtained in Step 1 to the /tmp directory on the server using a file
transfer tool (for example, SSH or SFTP).

Step 5 Go to the /tmp directory.

cd /tmp

Step 6 Run the following commands.

chmod +x [Link]
./[Link]

Step 7 Enter 1.

The script automatically installs the required hardware drivers.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 192

Server
OS Installation Guide 8 Installing and Upgrading Drivers and Firmware

● If the installation result is as follows, the driver is installed or upgraded

successfully.
The driver install/update completed successfully.
● If the installation result is as follows, the driver installation has failed. Check the
log file for the detailed error information and take proper measures.
The driver install/update encountered a error. Please check it.

Step 8 Reboot the OS.

----End

8.4 Upgrading Firmware

NO TICE

During upgrade of the NIC firmware, in-band and sideband services will be
interrupted for a short time. Back up network port services before the upgrade.

● To upgrade the RAID controller card, NIC, and chassis component firmware,
follow the operations described in the upgrade guide of corresponding server
model. This method applies only to the upgrade of firmware one by one.
● To upgrade the iBMC, BIOS, and CPLD firmware, see "Upgrading Server
Firmware" in the FusionServer Tools user guide of corresponding version. This
upgrade mode supports batch upgrade.
● To upgrade the mezzanine card, compute node, pass-through/switch module,
and chassis component firmware of the E9000, follow the instructions in the
upgrade guide of the corresponding server model.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 193

Server
OS Installation Guide 9 Common Operations

9 Common Operations

9.1 Connecting to the Server

9.2 Logging In to the Virtual Console
9.3 Transferring Files Using WinSCP
9.4 Transferring Files Using the Local Directory

9.1 Connecting to the Server

9.1.1 Connecting Mouse, Keyboard, and VGA Cables to a Rack

Server
The connection method varies depending on the server you use. For more details,
see the user guide for your server.

Both the front and rear panels of the server provide DB15 VGA ports but no standard
PS/2 port for a keyboard or mouse. Connect the keyboard and mouse to the USB
ports on the front or rear panel using either of the following methods:

● Connect the USB keyboard and mouse to the USB ports on the server directly.
● Connect the keyboard and mouse using a USB-to-PS/2 cable.

Procedure
Step 1 Plug the USB connector of the USB-to-PS/2 cable into the USB port on the front or
rear panel of the server.

Step 2 Connect the connectors on the other end of the USB-to-PS/2 cable to the keyboard
and mouse.

Step 3 Connect the DB15 connector of the VGA cable to the VGA port on the front or rear
panel of the server and tighten the two screws.

Step 4 Connect the other end of the VGA cable to the VGA port on the monitor and tighten
the two screws.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 194

Server
OS Installation Guide 9 Common Operations

Figure 9-1 Connecting USB-to-PS/2 and VGA cables

----End

9.1.2 Connecting a High-Density Cable to a Blade or High-

Density Server
Overview
The method of connecting a high-density cable varies depending on the server you
use. This section uses a high-density server as an example. For details about how to
connect a high-density cable for other servers, see the corresponding user guide.
The server node provides a high-density port for connecting a high-density cable.
The high-density cable has the following connectors on one end: one DB-15 VGA
connector, one RJ45 serial port, and three USB 2.0 (USB 1.1 compatible) ports. The
port functions are as follows:
● One DB-15 VGA connector: connects the VGA port on the local client.
● One RJ45 connector: connects the network port on the local client.
● Two USB connectors: connect the USB keyboard and mouse on the local client
to provide KVM functions.
● One USB connector: connects a USB storage device, for example, a USB DVD-
ROM drive or hard drive.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 195

Server
OS Installation Guide 9 Common Operations

Figure 9-2 High-density cable

1 VGA connector (DB-15) 2 USB 2.0 connector (one)

3 Serial port (RJ45) 4 USB 2.0 connector (two)

5 High-density connector - -
(connecting to the UCP
on a server node)

Procedure
Step 1 Hold down the tabs on the connector of the high-density cable. See (1) in Figure 9-3.

Figure 9-3 Connecting a high-density cable

Step 2 Align the connector with the UCP on the server panel, and gently insert the connector
into the port. Ensure that the high-density cable is secured. See (2) in Figure 9-3.
Step 3 Release your fingers.
Step 4 Use the high-density cable to connect to the KVM.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 196

Server
OS Installation Guide 9 Common Operations

9.2 Logging In to the Virtual Console

9.2.1 Logging In to the Remote Console (iBMC Earlier than

V561)
NO TE

For the 2298 V5 (iBMC V378 or later), 1288X V5 (iBMC V507 or later), and 2288X V5 (iBMC
V506 or later), see 9.2.2 Logging In to the Remote Console (iBMC V561 or Later or
[Link] or Later).

Prerequisites
The local PC that uses the remote control function must have the Java runtime
environment (JRE) and the browser of the required version. For details, see the iBMC
user guide of corresponding server model.

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the iBMC management network port.
● User name and password for logging in to the iBMC.

Step 2 Configure the login environment.

1. Connect the network port on a PC to the iBMC management network port of the
server using a network cable.
2. Ensure that the client can access the IP address of the iBMC management
network port.

Step 3 Log in to the server management page.

1. Open Internet Explorer, enter the IP address of the iBMC management network
port in the address box, and press Enter.
URL format: [Link] address of the iBMC management network port.

NO TE

Enter an IPv6 address in brackets or an IPv4 address directly. Examples:

– IPv4 address: [Link]
– [IPv6 address]: [fc00::64]
The iBMC login page is displayed, as shown in Figure 9-4.

NO TE

– If Internet Explorer displays a certificate error, click Continue to this website (not
recommended).
– If the Security Alert dialog box is displayed, click OK.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 197

Server
OS Installation Guide 9 Common Operations

Figure 9-4 iBMC login page

2. On the login page, set the parameters as follows:

a. Select a language.
b. Enter user name and password.
NO TE

▪ The default user name of the V3 server is root. Contact the customer service
center to obtain the default password.

▪ For V5 servers, the default user name is Administrator and the default
password is Admin@9000.
c. Select This iBMC from the Domain drop-down list box.
d. Click Log In. The iBMC WebUI is displayed.
Step 4 Open the virtual console.
1. Choose Remote Console on the menu bar.
The Remote Console page is displayed, as shown in Figure 9-5.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 198

Server
OS Installation Guide 9 Common Operations

Figure 9-5 Remote control page

2. On the Remote Console page, select HTML5 Integrated Remote Console or

Java Integrated Remote Console in exclusive or shared mode.
The Remote Virtual Console page is displayed, as shown in Figure 9-6 or
Figure 9-7.

Figure 9-6 Remote Virtual Console page (Java)

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 199

Server
OS Installation Guide 9 Common Operations

Figure 9-7 Remote Virtual Console page (HTML5)

----End

9.2.2 Logging In to the Remote Console (iBMC V561 or Later or

[Link] or Later)
NO TE

This section also applies to the 2298 V5 (iBMC V378 or later), 1288X V5 (iBMC V507 or later),
and 2288X V5 (iBMC V506 or later).

Prerequisites
The client that uses the remote control function must have the Java runtime
environment (JRE) and the browser of the required version. For details, see the iBMC
user guide of corresponding server model.

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the iBMC management network port.
● User name and password for logging in to the iBMC.

Step 2 Configure the login environment.

1. Connect the network port on a PC to the iBMC management network port of the
server using a network cable.
2. Ensure that the client can access the IP address of the iBMC management
network port.

Step 3 Log in to the server management page.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 200

Server
OS Installation Guide 9 Common Operations

1. Open Internet Explorer, enter the IP address of the iBMC management network
port in the address box, and press Enter.
URL format: [Link] address of the iBMC management network port.
NO TE

Enter an IPv6 address in brackets or an IPv4 address directly. Examples:

– IPv4 address: [Link]
– [IPv6 address]: [fc00::64]
The iBMC login page is displayed as shown in Figure 9-8.
NO TE

– If Internet Explorer displays a certificate error, click Continue to this website (not
recommended).
– If the Security Alert dialog box is displayed, click Yes.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 201

Server
OS Installation Guide 9 Common Operations

Figure 9-8 iBMC login page

2. On the login page, set the parameters as follows:

a. Enter user name and password.
NO TE

The default user name for logging in to the iBMC system is Administrator, and the
default password is Admin@9000.
b. Select This iBMC from the Domain drop-down list box.
c. Click Log In.
After you log in to the system again, the Home page is displayed, as shown
in Figure 9-9.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 202

Server
OS Installation Guide 9 Common Operations

Figure 9-9 Home page

Step 4 Open the remote console.

1. Click Start in the Virtual Console area on the Home page.
2. In the displayed list, select HTML5 Integrated Remote Console or Java
Integrated Remote Console in exclusive or shared mode.
The Remote Virtual Console page is displayed, as shown in Figure 9-10 or
Figure 9-11.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 203

Server
OS Installation Guide 9 Common Operations

Figure 9-10 Remote Virtual Console page (HTML5)

Figure 9-11 Remote Virtual Console page (Java)

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 204

Server
OS Installation Guide 9 Common Operations

9.2.3 Logging In Using the iMana 200 WebUI

Prerequisites
The OS, web browser, and JRE of the required versions have been installed on the
client to enable the remote control function.

Table 9-1 lists the required software versions.

Table 9-1 Required software versions

OS Software Version

● Windows 7 32- Web Internet Explorer 8.0 to 10.0

bit browser
Mozilla Firefox 9.0 to 23.0
● Windows 8 32-
bit Google Chrome 13.0 to 31.0
● Windows
Server 2008 JRE 1.6.0 U25/1.7.0 U40 (32-bit)
32-bit

● Windows 7 64- Web Internet Explorer 8.0 to 10.0

bit browser
Mozilla Firefox 9.0 to 23.0
● Windows 8 64-
bit Google Chrome 13.0 to 31.0
● Windows
Server 2008 JRE 1.6.0 U25/1.7.0 U40 (64-bit)
R2 64-bit
● Windows
Server 2012
64-bit

● RHEL 4.3 64- Web Mozilla Firefox 9.0 to 23.0

bit browser
● RHEL 6.0 64- JRE 1.6.0 U25/1.7.0 U40
bit

MAC X v10.7 Web Safari 5.1

browser
Mozilla Firefox 9.0 to 23.0

JRE 1.6.0 U25/1.7.0 U40

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the iMana management network port.
● User name and password for login to the iMana.

Step 2 Configure the login environment.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 205

Server
OS Installation Guide 9 Common Operations

1. Connect the network port on a PC to the iMana management network port of the
server using a network cable.
2. Configure the PC IP address and connect the PC to the server iMana
management network port.
Step 3 Configure network settings for the web browser.
1. On the menu bar of Internet Explorer, choose Tools > Internet Options.
The Internet Options dialog box is displayed.
NO TE

This section uses Windows 7 with Internet Explorer 8 as an example.

2. Click the Connections tab, and then click LAN Settings.
The Local Area Network (LAN) Settings dialog box is displayed.
3. In the Proxy server area, deselect Use a proxy server for your LAN.
NO TE

You can also retain the proxy server configuration and add the iMana IP address segment
in the Exceptions area in the Advanced dialog box of the proxy server.
4. Click OK
The Local Area Network (LAN) Settings dialog box is closed.
5. Click OK
The Internet Options dialog box is closed.
Step 4 Log in to the server management page.
1. Open Internet Explorer, enter the IP address of the iMana management network
port in the address box, and press Enter.
URL format: [Link] address of the iMana management network port
The Certificate Error: Navigation Blocked page is displayed.
2. Click Continue to this website (not recommended).
The login page is displayed, as shown in Figure 9-12.

Figure 9-12 iMana login page

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 206

Server
OS Installation Guide 9 Common Operations

3. On the login page, set the parameters as follows:

a. Select a language.
b. Enter user name and password.
NO TE

The default user name is root. Contact the customer service center to obtain the
default password.
c. Select This iMana from the Log on to drop-down list box.
d. Click Log In. The iMana WebUI is displayed. You can click Reset to reset
the information.
Step 5 Open the virtual console.
1. In the navigation tree, click Remote Control.
The Remote Console page is displayed, as shown in Figure 9-13.

Figure 9-13 Remote control page

2. On the Remote Control page, click Remote Virtual Console.

The Remote Virtual Console page is displayed, as shown in Figure 9-14.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 207

Server
OS Installation Guide 9 Common Operations

Figure 9-14 Remote virtual console page

----End

9.2.4 Logging In to the E9000 Compute Node KVM Using the

MM910 WebUI

Prerequisites
The OS, web browser, and JRE of the required versions have been installed on the
client to enable the remote control function.

Table 9-2 lists the required software versions.

Table 9-2 Required software versions

Software Version

OS Windows 7 32-bit

Web Internet Internet Explorer 8.0

brows Explorer
er
Mozilla Mozilla Firefox3.0
Firefox

JRE 1.6 or later

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the MM910 management network port.
● User name and password for login to the MM910.

Step 2 Log in to the MM910 WebUI.

1. Connect the Ethernet port on the PC to the Mgmt port on the active MM910 over
a LAN.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 208

Server
OS Installation Guide 9 Common Operations

NO TICE

If you want to connect your local PC directly to the MM910 using a network cable
but the MGMT port on the active MM910 is already connected with a network
cable, do not remove the network cable from the MGMT port on the active
MM910. Otherwise, an active/standby switchover of the MM910s will be
triggered, which may cause network interruption. You can connect the network
cable from the local PC to the STACK port of the active MM910 in the chassis. If
the STACK port on the active MM910 is also used, connect the network cable to
an idle STACK port on an active MM910 in a chassis cascaded with the E9000
chassis.

NO TE

The MM910 management port is provided by two modes.

– An Ethernet port on the switch module in slot 2X or 3X can be used as the MM910
management port. However, if a CX910/CX911/CX912/CX913/CX915 is in slot 2X
or 3X, only a GE port can be used; if a CX920 is in slot 2X or 3X, only a 10GE port
can be used; if a CX916/CX916L/CX930 is in slot 2X or 3X, only a 25GE port can
be used. If a CX110/CX111/CX310/CX311/CX312/CX320/CX710 is in slot 2X or 3X,
any port can be used. The CX910/CX911/CX912/CX913 are not recommended for
providing the management network port of the management module.
– The MGMT port on the MM910 panel can be used as the MM910 management port.
– For MM910 (U54) 2.25 or earlier, the port on the switch module in slot 2X or 3X is
used as the management network port by default. In this case, do not connect the
MGMT port on the MM910 and the port on the switch module to the same network
at the same time, otherwise, a network storm occurs and the network is interrupted.
For MM910 (U54) 2.26 or later, the MGMT port is used as the management network
port by default. For details about how to query the version, see the MM910
Management Module User Guide.
– You can run the outportmode command to change the mode in which the MM910
management port is provided. For details, see section "Querying and Setting the
Network Port Out Mode (outportmode)" in the MM910 Management Module
Command Reference.
2. Set the IP address and subnet mask or route information for the PC to
communicate with the MM910.
3. On the menu bar of Internet Explorer, choose Tools > Internet Options.
The Internet Options dialog box is displayed.
NO TE

This section uses Windows 7 with Internet Explorer 8 as an example.

4. Click the Connections tab, and then click LAN Settings.
The Local Area Network (LAN) Settings dialog box is displayed.
5. In the Proxy server area, deselect Use a proxy server for your LAN.
NO TE

You can also retain the proxy server configuration and add the iMana IP address segment
in the Exceptions area in the Advanced dialog box.
6. Click OK.
The Local Area Network (LAN) Settings dialog box is closed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 209

Server
OS Installation Guide 9 Common Operations

7. Click OK.
The Internet Options dialog box is closed.
8. Reopen Internet Explorer, enter [Link] IP address in the address box,
and press Enter.
NO TE

To log in to the WebUI of the active MM910, enter the static IP address of the active
MM910 or the floating IP address. To log in to the WebUI of the standby MM910, enter
the static IP address of the standby MM910.
For example, enter [Link] in the address box.
The message "There is a problem with this website's security certificate" is
displayed.
9. Click Continue to this website (not recommended).
The HMM Web login page is displayed.
10. Set login parameters. See Figure 9-15.
– Language: Select English.
– User Name: Enter your user name.
– Password: Enter your password.

Figure 9-15 HMM Web login page

11. Click Log In.

The HMM Web page is displayed, as shown in Figure 9-16.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 210

Server
OS Installation Guide 9 Common Operations

Figure 9-16 HMM Web page

Step 3 Log in to the real-time desktop of the compute node.

1. Click KVM via SMM in Figure 9-16.
The Security Alert dialog box is displayed.
NO TE

The information displayed on Figure 9-16 may vary depending on versions.

2. Click Yes.
The Warning-Security dialog box is displayed.
3. Click Yes.
The remote KVM screen is displayed, as shown in Figure 9-17.

Figure 9-17 KVM screen

4. Click the serial number of a compute node.

The real-time desktop of the compute node is displayed.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 211

Server
OS Installation Guide 9 Common Operations

9.2.5 Logging In to the E6000 Server KVM Using the MM620

WebUI
Prerequisites
The OS, web browser, and JRE of the required versions have been installed on the
client to enable the remote control function.
Table 9-3 lists the required software versions.

Table 9-3 Required software versions

OS Software Version

● Windows 7 32- Web Internet Explorer 8.0 to 10.0

bit browser
Mozilla Firefox 9.0 to 23.0
● Windows 8 32-
bit Google Chrome 13.0 to 31.0
● Windows
Server 2008 JRE 1.6.0 U25/1.7.0 U40 (32-bit)
32-bit

● Windows 7 64- Web Internet Explorer 8.0 to 10.0

bit browser
Mozilla Firefox 9.0 to 23.0
● Windows 8 64-
bit Google Chrome 13.0 to 31.0
● Windows
Server 2008 JRE 1.6.0 U25/1.7.0 U40 (64-bit)
R2 64-bit
● Windows
Server 2012
64-bit

● RHEL 4.3 64- Web Mozilla Firefox 9.0 to 23.0

bit browser
● RHEL 6.0 64- JRE 1.6.0 U25/1.7.0 U40
bit

MAC X v10.7 Web Safari 5.1

browser
Mozilla Firefox 9.0 to 23.0

JRE 1.6.0 U25/1.7.0 U40

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the MM620 management network port on the
server.
● User name and password for login to the MM620.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 212

Server
OS Installation Guide 9 Common Operations

Step 2 Log in to the MM620 WebUI.

1. Connect the client to the MM620 management network port using a network
cable.
2. Set an IP address for the client to communicate with the MM620.
3. On the client, open a web browser, enter [Link] address for the MM620
management network port in the address box, and press Enter.
The security warning dialog box is displayed.
4. Click Continue to this website (not recommended).
The MM620 login page is displayed, as shown in Figure 9-18.

Figure 9-18 Logging in to the MM620

5. Set the login parameters, and click Log In.

– Language: Select English.
– User Name: Enter your user name.
– Password: Enter your password.
– Log on to: Select This computer.
The HMM Web 1.0 page is displayed, as shown in Figure 9-19.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 213

Server
OS Installation Guide 9 Common Operations

Figure 9-19 HMM Web 1.0 page

Step 3 Set an IP address for the iMana management network port on the server blade.
1. In the navigation pane, choose System Management > Network Management.
Then click the Blade tab on the right.
The IP address setting page is displayed, as shown in Figure 9-20.

Figure 9-20 Setting an IP address for the iMana management network port

2. Set an IP address for the iMana management network port by following on-
screen instructions.

Step 4 Log in to the real-time desktop of the server blade.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 214

Server
OS Installation Guide 9 Common Operations

1. In the navigation pane, choose System Management > iMana Web.

The iMana Web page is displayed, as shown in Figure 9-21.

Figure 9-21 iMana Web page

2. Click the IP address or domain name of the server blade.

The iMana WebUI login page is displayed, as shown in Figure 9-22.

Figure 9-22 Logging in to the iMana WebUI

Step 5 Log in to the server management page.

On the login page, set the parameters as follows:

1. Select a language.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 215

Server
OS Installation Guide 9 Common Operations

2. Enter user name and password.

NO TE

The default user name is root. Contact the customer service center to obtain the default
password.
3. Select This iMana from the Log on to drop-down list box.
4. Click Log In. The iMana WebUI is displayed. You can click Reset to reset the
information.

Step 6 Open the virtual console.

1. In the navigation tree, click Remote Control.
The Remote Console page is displayed, as shown in Figure 9-23.

Figure 9-23 Remote control page

2. On the Remote Control page, click Remote Virtual Console.

The Remote Virtual Console page is displayed, as shown in Figure 9-24.

Figure 9-24 Remote virtual console page

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 216

Server
OS Installation Guide 9 Common Operations

9.2.6 Logging In to the KVM (xFusionBMC)

Prerequisites
Conditions
Ensure that the local PC meets the following networking conditions:
● The local PC is connected to the xFusionBMC management network port.
● The IP address of the local PC can communicate with the xFusionBMC
management network port.
Data
Obtain the data as shown in Table 9-4.

Table 9-4 Required data

Category Paramete Description
r

User login Username Username for logging in to the xFusionBMC WebUI.

information The default username for logging into the xFusionBMC
is Administrator.

Password User password for logging in to the xFusionBMC

WebUI.
The default xFusionBMC password is Admin@9000.

Procedure
This section uses a PC running Windows 11 and Edge as an example.

Step 1 Open Edge and enter the IP address [Link] in the address bar. Press
Enter.
NO TE

Enter an IPv6 address in brackets or an IPv4 address directly. For example:

● IPv4 Address: "[Link]".
● [IPv6 Address]: "[fc00:]: 64".

Step 2 The security alarm window shown in Figure 8-4 is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 217

Server
OS Installation Guide 9 Common Operations

Figure 9-25 Security alarm

NO TE

If a security alert is displayed, you can ignore this message or perform any of the following to
shield this alert:
● Import a trust certificate and a root certificate to the xFusionBMC.
● If no trust certificate is available and the network is secured, add the xFusionBMC to the
Exception Site List on Java Control Panel or reduce the Java security level. This operation
may reduce user security. Exercise caution when performing this operation.

Step 3 Click Advanced and proceed to access the login page.

The login page is displayed, as shown in Figure 9-26.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 218

Server
OS Installation Guide 9 Common Operations

Figure 9-26 xFusionBMC Sign In page

Step 4 On the xFusionBMC login page, enter the username and password.
Step 5 Click Sign In.
After the login is successful, the Dashboard is displayed.
Step 6 Select Remote Control > KVM in the navigation bar.
The remote virtual desktop page is displayed, as shown in Figure 9-27.

Figure 9-27 Remote virtual desktop page

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 219

Server
OS Installation Guide 9 Common Operations

9.3 Transferring Files Using WinSCP

Scenarios
Use WinSCP to transfer files between a PC and a serve.

Prerequisites
Conditions

The SFTP service has been enabled on the destination device.

Data

The following data is required:

● IP address of the server

● Username and password for logging in to the server

Procedure
Step 1 Open the WinSCP folder and double-click [Link].

The WinSCP Login dialog box is displayed, as shown in Figure 9-28.

NO TE

You can click Languages to select a required system language.

Figure 9-28 WinSCP login

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 220

Server
OS Installation Guide 9 Common Operations

Step 2 Set login parameters.

The parameters are described as follows:

● Host name: Enter the IP address of the device to be connected. For example:
[Link].
● Port number: Use the default value 22.
● User name: Enter the username. For example, admin123.
● Password: Enter the password. For example, admin123.
● Private Key file: Retain the default setting, which is empty.
● Protocol: Retain the default setting S SFTP, and select Allow SCP fallback.

Step 3 Click Log In.

The WinSCP file transfer page is displayed.

NO TE

● If no private key file is selected during your first login, "Continue connecting and add host
key to cache" is displayed. Click Yes. The WinSCP file transfer page is displayed.
● If Windows 7 is used, C:\Users\Administrator\Documents on the local PC is displayed in
the left pane and the /root directory of the destination device is displayed in the right pane
by default.

Step 4 In the left and right panes, create, delete, or copy folders in specific directories as
required.

----End

9.4 Transferring Files Using the Local Directory

Use the local Directory of the server Remote Virtual Console to transfer files
between the client and server. The example in this section describes how to send
files from a local directory to the server.

Procedure
Step 1 Obtain the following data:
● IP address and subnet mask of the iBMC management network port.
● Username and password for logging in to the iBMC.

Step 2 Log in to the virtual console of the server.

Step 3 Open the local directory.

1. Click Remote Virtual Console (Shared Mode) or Remote Virtual Console (Private
Mode) on the Remote Control or Remote Console page.
Open the remote virtual console.

2. Click .
The window shown in Figure 9-29 is displayed.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 221

Server
OS Installation Guide 9 Common Operations

Figure 9-29 Accessing the local directory

3. Click Directory.
4. Click Browse to select a folder on the client, such as D:\ test.
NO TE

This folder cannot be empty.

5. Click Connect.
The selected directory is identified as a local directory of the server.
Step 4 Place the file to be sent in the target directory.
Copy the files (such as driver packages and scripts) to the target directory specified
in 4 of Step 3.
Step 5 Copy the file to the server.
1. Log in to the server as user root.
2. Find the local directory specified in 4 of Step 3.
This operation varies depending on the OS type. For details, see the official OS
documentation.
3. Copy the file in the directory found in Step 5.2 of Step 5 to a directory on the
server (for example, /tmp).

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 222

Server
OS Installation Guide 10 Locating OS Faults

10 Locating OS Faults

10.1 Configuring Memory Dump Tools

10.2 Configuring SOL
10.3 Configure an NMI
10.4 Configuring Magic Keys for Linux
10.5 Changing Linux System Log Levels
10.6 Disabling the Screen Saver
10.7 Deploying and Verifying Fault Locating Tools on Linux
10.8 Troubleshooting

10.1 Configuring Memory Dump Tools

If your OS breaks down, you need to collect information to analyze the causes of the
fault. If the memory dump service is configured, memory image at the time of the
crash is saved to allow fault analysis.

Linux, Windows, and VMware OSs all support memory dump.

10.1.1 Configuring kdump on Linux

kdump provides the memory dump service on Linux. This section describes how to
configure and use kdump to dump core memory information to a hard drive and
check crash information. kdump is based on the kexec mechanism.

[Link] Concepts

kexec
kexec is a fast boot mechanism that allows a Linux kernel to boot from the context of
an already running kernel. This mechanism is faster than booting using BIOS,
especially for mainframes or servers with many peripherals.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 223

Server
OS Installation Guide 10 Locating OS Faults

kdump
Linux kernel is a rather robust entity. It is stable and fault-tolerable and usually does
not suffer irrecoverable faults that crash the entire system. However, these types of
problems are known as kernel crashes and cannot be completely avoided.
Kdump is a new kernel crash dumping mechanism and is reliable. Kdump is a tool
provided by Linux to detect, collect, and analyze crashes. It can be used to locate the
root cause of problems and find solutions to critical errors.
The kdump mechanism involves two types of kernel:
● Standard (production) kernel - kernel used for running services.
● Crash (capture) kernel - kernel specially used for collecting crash dumps
Kdump is a new kernel crash dumping mechanism and is reliable. The crash dump is
captured from the context of a freshly booted kernel and not from the context of the
crashed kernel. Kdump uses kexec to boot into a second kernel whenever the
system crashes. This second kernel, often called a crash or a capture kernel, boots
with little memory and captures the dump image.
Despite the overall reliability of kdump, dumping can occasionally fail. For example, if
transition table suspension is interrupted, a major kernel fault occurs, or a storage
fault occurs during system breakdown, you need to obtain location information using
other methods.

[Link] Configuring kdump on RHEL 5

NO TE

This section applies to the kdump configuration on RHEL 5. For details about the OSs
supported by the server, visit the technical support website and access the compatibility list.

This section describes how to configure kdump on RHEL 5.

For details about kdump settings for each OS version, see sections about testing
kdump in the OS installation guide cases of corresponding server models.

Step 1 Run the following command to open the /boot/grub/[Link] file and add the
crashkernel=<size>M@16M parameter.
# vi /boot/grub/[Link]

Set the kdump size based on the actual physical memory size. For details, see Table
10-1.

Table 10-1 Values of crashkernel (reserved memory size)

RAM Size Value of crashkernel

>0GB 128MB

>2GB 256MB

>6GB 512MB

>8GB 768MB

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 224

Server
OS Installation Guide 10 Locating OS Faults

The following describes how to reserve a memory capacity of 128 MB.

# [Link] generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda3
# initrd /[Link]
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/[Link]
hiddenmenu
title Red Hat Enterprise Linux Server (2.6.18-274.3.1.el5)
root (hd0,0)
kernel /vmlinuz-2.6.18-274.3.1.el5 ro root=/dev/sda3 crashkernel=128M@16M
initrd /[Link]

Step 2 Run the :wq command to save the configuration and exit the edit mode.

Step 3 Run the following command to enable automatic startup for kdump.
~]# chkconfig kdump on

Step 4 If a 4-socket server is used, set the value of nr_cpus to 4 in the

KDUMP_COMMANDLINE_APPEND line of the /etc/sysconfig/kdump configuration
file.
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=4 disable_cpu_apicid=0 reset_devices cgroup_disable=memory
mce=off"

Step 5 Reboot OS.

~]# reboot

Step 6 Run the following command to check the kdump status. If the following information is
displayed, the kdump service is normal.
~]# service kdump status

Kdump is operational

Step 7 Test the kdump configuration.

1. Run the following commands to force the Linux kernel to break down.
~]# echo 1 > /proc/sys/kernel/sysrq
~]# echo c > /proc/sysrq-trigger

2. After the OS automatically reboots, check whether the address-YYYY-MM-DD-

HH:MM:SS/vmcore file exists in the /var/crash/ directory.
– If yes, the kdump function is running properly.
– If no, adjust the reserved memory size.

----End

[Link] Configuring kdump on RHEL 6

NO TE

This section is dedicated for the kdump configuration of RHEL 6 series. For details about the
OSs supported by the server, visit the technical support website and access the compatibility
list.

This section describes how to configure kdump on RHEL 6.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 225

Server
OS Installation Guide 10 Locating OS Faults

For details about kdump settings for each OS version, see sections about testing
kdump in the OS installation guide cases of corresponding server models.

On RHEL 6, kdump is enabled by default and the memory reservation setting is

crashkernel=auto, that is, the kernel automatically reserves an appropriate amount of
memory for kdump. For details about how to change the reserved memory size, see
Manually Adjusting the Reserved Memory Size.

You are advised to perform a test after all applications are installed to verify that
kdump applies to all systems. The crashkernel=auto setting applies only to the
typical configuration.

To test the kdump configuration, perform the following steps:

Step 1 Run the following command to verify that the kdump service is running.
~]# service kdump status
Kdump is operational

Step 2 Run the following commands to force the Linux kernel to break down.
~]# echo 1 > /proc/sys/kernel/sysrq
~]# echo c > /proc/sysrq-trigger

Step 3 If a 4-socket server is used, set the value of nr_cpus to 4 in the

KDUMP_COMMANDLINE_APPEND line of the /etc/sysconfig/kdump configuration
file.
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=4 disable_cpu_apicid=0 reset_devices cgroup_disable=memory
mce=off"

Step 4 After the OS automatically reboots, check whether the address-YYYY-MM-DD-

HH:MM:SS/vmcore file exists in the /var/crash/ directory.
● If yes, the kdump function is running properly.
● If no, manually adjust the reserved memory size. For details, see Manually
Adjusting the Reserved Memory Size.

----End

Manually Adjusting the Reserved Memory Size

When automatic memory reservation is used and the system has many boards and a
large memory capacity, kdump may not work properly. You are advised to adjust the
reserved memory capacity to 512 MB or more.

Third-party modules require more reserved memory.

The formula for calculating the minimum reserved memory is as follows:128 MB

+ (64 MB every 1 TB physical RAM).

For example, if the system memory size is 1 TB, the minimum reserved memory size
is 128 MB + 64 MB = 192 MB.

For example, perform the following steps to set crashkernel=512 MB:

Step 1 Run the vi command to open the GRUB configuration file and set crashkernel=512
MB.
● In Legacy mode, open the /boot/grub/[Link] file.
● In UEFI mode, open the /boot/efi/EFI/redhat/[Link] file.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 226

Server
OS Installation Guide 10 Locating OS Faults

Step 2 Run the :wq command to save the configuration and exit the edit mode.
Step 3 Run the reboot command to reboot the OS.
Step 4 Run the systemctl status kdump command to check the kdump status. If the
following information is displayed, the kdump service is normal.

Step 5 Perform Step 1 and Step 4 to test and verify that the kdump function is running
properly.

----End

[Link] Configuring kdump on RHEL 7

NO TE

This section applies to the kdump configuration on RHEL 7. For details about the OSs
supported by the server, visit the technical support website and access the compatibility list.

This section describes how to configure kdump on RHEL 7.

For details about kdump settings for each OS version, see sections about testing
kdump in the OS installation guide cases of corresponding server models.
On RHEL 7, kdump is enabled by default and the memory reservation setting is
crashkernel=auto, that is, the kernel automatically reserves an appropriate amount of
memory for kdump. For details about how to change the reserved memory size, see
Manually Adjusting the Reserved Memory Size.
You are advised to perform a test after all applications are installed to verify that
kdump applies to all systems. The crashkernel=auto setting applies only to the
typical configuration.
To test the kdump configuration, perform the following steps:

Step 1 Run the following command to verify that the kdump service is running.
~]# systemctl is-active kdump
active

Step 2 Run the following commands to force the Linux kernel to break down.
~]# echo 1 > /proc/sys/kernel/sysrq
~]# echo c > /proc/sysrq-trigger

Step 3 If a 4-socket server is used, set the value of nr_cpus to 4 in the

KDUMP_COMMANDLINE_APPEND line of the /etc/sysconfig/kdump configuration
file.
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=4 disable_cpu_apicid=0 reset_devices cgroup_disable=memory
mce=off"

Step 4 After the OS automatically reboots, check whether the address-YYYY-MM-DD-

HH:MM:SS/vmcore exists in the /var/crash/ directory.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 227

Server
OS Installation Guide 10 Locating OS Faults

● If yes, the kdump function is running properly.

● If no, manually adjust the reserved memory size. For details, see Manually
Adjusting the Reserved Memory Size.

----End

Manually Adjusting the Reserved Memory Size

Minimum reserved memory = 160 MB + (2 bits every 4 KB system memory)

● 8 bits = 1 byte
● 1024 bytes = 1 KB
● 1024 KB=1 MB
● 1024 MB=1 GB
● 1024 GB=1 TB

For example, if the memory capacity is 1 TB, the minimum reserved memory is 160
MB + 64 MB = 224 MB.

For example, perform the following steps to set crashkernel=512 MB:

Step 1 Run the vi /etc/default/grub command to edit the grub file and set
crashkernel=512M.

Step 2 Run the :wq command to save the configuration and exit the edit mode.

Step 3 Save the configuration to the [Link] file.

● In UEFI mode, run the grub2-mkconfig -o /boot/efi/EFI/redhat/[Link]
command.
● In Legacy mode, run the grub2-mkconfig -o /boot/grub2/[Link] command.

Step 4 Run the reboot command to reboot the OS.

Step 5 Run the systemctl status kdump command to check the kdump status. If the
following information is displayed, the kdump service is normal.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 228

Server
OS Installation Guide 10 Locating OS Faults

Step 6 Perform Step 1 and Step 4 to test and verify that the kdump function is running
properly.

----End

[Link] Configuring Kdump on RHEL 8/RHEL 9

On RHEL 8 and RHEL 9, kdump is enabled by default and the memory reservation
setting is crashkernel=auto.

To test the kdump configuration, perform the following steps:

Step 1 Run the following command to verify that the kdump service is running.
~]# systemctl is-active [Link] active

Step 2 Run the following commands to force the Linux kernel to break down.
~]# echo 1 > /proc/sys/kernel/sysrq
~]# echo c > /proc/sysrq-trigger

Step 3 After the OS automatically reboots, check whether the address-YYYY-MM-DD-

HH:MM:SS/vmcore exists in the /var/crash/ directory.
● If yes, the kdump function is running properly.
● If no, manually adjust the reserved memory size. For details, see Manually
Adjusting the Reserved Memory Size.

----End

Manually Adjusting the Reserved Memory Size

To manually adjust the reserved memory size, perform the following operations:

Minimum reserved memory = 160 MB + (2 bits every 4 KB system memory)

● 8 bits = 1 byte
● 1024 bytes = 1 KB
● 1024 KB=1 MB
● 1024 MB=1 GB
● 1024 GB=1 TB

For example, if the memory capacity is 1 TB, the minimum reserved memory is 160
MB + 64 MB = 224 MB.

For example, perform the following steps to set crashkernel=512 MB:

Step 1 Run the vi /etc/default/grub command to edit the grub file and set
crashkernel=512M.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 229

Server
OS Installation Guide 10 Locating OS Faults

Step 2 Save the configuration to the [Link] file.

● In UEFI mode, run the grub2-mkconfig -o /boot/efi/EFI/redhat/[Link]
command.
● In Legacy mode, run the grub2-mkconfig -o /boot/grub2/[Link] command.

Step 3 Run the reboot command to reboot the OS.

Step 4 Run the systemctl status kdump command to check the kdump status. If the
following information is displayed, the kdump service is normal.

Step 5 Perform Step 1 and Step 3 to test and verify that the kdump function is running
properly.

----End

[Link] Configuring kdump on SLES 11

NO TE

This section applies to the kdump configuration on SLES 11. For details about the OSs
supported by the server, visit the technical support website and access the compatibility list.

This section describes how to configure kdump on SLES 11.

For details about kdump settings for each OS version, see sections about testing
kdump in the OS installation guide cases of corresponding server models.

On SLES 11, kdump is enabled by default and the reserved memory size is 128 MB.

To manually adjust the reserved memory size, perform the following steps:

Step 1 Open the CLI on SLES 11.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 230

Server
OS Installation Guide 10 Locating OS Faults

Step 2 Run the yast2 command.

Open the YaST Control Center, as shown in Figure 10-1.

Figure 10-1 YaST Control Center

Step 3 Choose System > Kernel Kdump.

The kdump configuration page is displayed, as shown in Figure 10-2.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 231

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-2 Kdump configuration page

Step 4 Select Enable Kdump and set Kdump Memory to the reserved memory size, for
example, 512.
Step 5 Click OK.
Step 6 If a 4-socket server is used, set the value of nr_cpus to 4 in the
KDUMP_COMMANDLINE_APPEND line of the /etc/sysconfig/kdump configuration
file.
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=4 disable_cpu_apicid=0 reset_devices cgroup_disable=memory
mce=off"

Step 7 Run the reboot command to reboot the OS.

Step 8 After the system is rebooted, run the service [Link] status command to check
whether the kdump is started properly.

● If running is displayed in the command output, perform Step 12.

● If dead is displayed in the command output, perform Step 9 to Step 11.
Step 9 Run the chkconfig [Link] on command to enable automatic startup for the
kdump service.
Step 10 Run the service [Link] start command to enable the kdump service.
Step 11 Perform Step 7 to Step 8 to check whether kdump is started properly.
If kdump cannot be started, repeat Step 4 to Step 8 to change the kdump memory
size.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 232

Server
OS Installation Guide 10 Locating OS Faults

Step 12 Run the echo c > /proc/sysrq-trigger command to force the Linux kernel to break
down.
Step 13 After the OS automatically reboots, check whether the address-YYYY-MM-DD-
HH:MM:SS/vmcore file exists in the /var/crash/ directory.
● If yes, the kdump function is running properly.
● If no, repeat Step 4 to Step 13 to modify the kdump memory size.

----End

[Link] Configuring kdump on SLES 12

NO TE

This section applies to the kdump configuration on SLES 12. For details about the OSs
supported by the server, visit the technical support website and access the compatibility list.

This section describes how to configure kdump on SLES 12.

For details about kdump settings for each OS version, see sections about testing
kdump in the OS installation guide cases of corresponding server models.
On SLES 12, kdump is enabled by default and the memory reservation setting is
crashkernel=auto.

Step 1 Open the CLI on SLES 12.

Step 2 Run the yast2 command.
Open the YaST Control Center, as shown in Figure 10-3.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 233

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-3 YaST Control Center

Step 3 Choose System > Kernel Kdump.

The kdump configuration page is displayed, as shown in Figure 10-4.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 234

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-4 Kdump configuration page

Step 4 Select Enable Kdump, set Kdump Low Memory to 256, and set Kdump High
Memory to 512.
Step 5 Click OK.
Step 6 If a 4-socket server is used, set the value of nr_cpus to 4 in the
KDUMP_COMMANDLINE_APPEND line of the /etc/sysconfig/kdump configuration
file.
KDUMP_COMMANDLINE_APPEND="irqpoll nr_cpus=4 disable_cpu_apicid=0 reset_devices cgroup_disable=memory
mce=off"

Step 7 Run the reboot command to reboot the OS.

Step 8 Run the echo c > /proc/sysrq-trigger command to force the Linux kernel to break
down.
Step 9 After the OS automatically reboots, check whether the address-YYYY-MM-DD-
HH:MM:SS/vmcore file exists in the /var/crash/ directory.
● If yes, the kdump function is running properly.
● If no, repeat Step 4 to Step 9 to modify the kdump memory size.
----End

[Link] Configuring kdump on SLES 15

On SLES 15, kdump is enabled by default and the memory reservation setting is
crashkernel=auto.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 235

Server
OS Installation Guide 10 Locating OS Faults

To test the kdump configuration, perform the following steps:

Step 1 Open the CLI on SLES 15.

Step 2 Run the yast2 command.
Open the YaST Control Center, as shown in Figure 10-5.

Figure 10-5 YaST Control Center

Step 3 Choose System > Kernel Kdump.

The kdump configuration page is displayed, as shown in Figure 10-6.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 236

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-6 Kdump configuration page

Step 4 Select Enable Kdump, change the kdump memory size to 256 and 512, and click
OK.

Step 5 Run the reboot command to reboot the OS.

Step 6 Run the echo c > /proc/sysrq-trigger command to force the Linux kernel to break
down.

Step 7 After the OS automatically reboots, check whether the address-YYYY-MM-DD-

HH:MM:SS/vmcore file exists in the /var/crash/ directory. If yes, the kdump function
is running properly.

----End

10.1.2 Configuring DiskDump on VMware

DiskDump provides memory dump services on VMware ESXi. It works similarly to
kdump.

DiskDump is installed and started by default on VMware (there is no option to change

DiskDump configuration during installation).

After VMware ESXi is installed, the default slot size for the core dump partition
(diskDumpSlotSize) is 100 MB. If the server load is heavy, 100 MB of memory will be
insufficient, which will cause the core dump file to be truncated. In this case, you are
advised to change diskDumpSlotSize to the required value (2 GB is recommended).

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 237

Server
OS Installation Guide 10 Locating OS Faults

ESXi 5.0 Update 2 or later allows users to modify this parameter. There are three
methods for modifying it.

Using CLI
Step 1 Log in to ESXi Shell or another CLI environment.
Step 2 Run the following command to set diskDumpSlotSize. size_in_megabytes
indicates the value of diskDumpSlotSize, and the recommended value is 2000. The
unit is MB.
esxcli system settings kernel set --setting=diskDumpSlotSize --value=size_in_megabytes

Example:
esxcli system settings kernel set --setting=diskDumpSlotSize --value=2000

Step 3 Run the following commands to check the configuration result:

esxcli system settings kernel list -o=diskDumpSlotSize

configured indicates the value of diskDumpSlotSize.

Step 4 Reboot OS.
Step 5 Verify the configuration result.

Runtime indicates the value of configured.

----End

Using the vSphere Web Client

NO TE

vSphere 7.0 and later versions do not support the vSphere Client and use vSphere Web Client
to connect and manage the vCenter Server instance.

Step 1 Install vSphere Web Client on a client.

Step 2 Open vSphere Web Client.
Step 3 Open a connection to the server, as shown in Figure 10-7.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 238

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-7 vSphere Web Client

Step 4 Click the Manage tab on the right.

Step 5 In the navigation pane, choose System > Advanced System Settings.

Step 6 Enter dumpdisk in (4) in Figure 10-7 for searching. The

[Link] project is displayed on the list.

Step 7 Select [Link], and click above the list to open the
editing window.

Step 8 Change the dump space size to 2000, and click OK.

Step 9 Reboot the server for the configuration to take effect.

----End

10.1.3 Configuring the Memory Dump Service on Windows

When Windows crashes and encounters a blue screen of death (BSOD), the system
generates a .dmp memory dump error report file, which is stored in C:\Windows by
default. This file can be used to analyze BSOD causes.

There are three types of dump files on Windows:

● Complete memory dump file: C:\Windows\[Link]

● Kernel memory dump file: C:\Windows\[Link]
● Small memory dump file: C:\Windows\Minidump\

After the OS is installed, you are advised to use the default settings and ensure that
drive C has more than 5 GB idle space for saving dump files.

You can choose System Properties > Advanced > Startup and Recovery to view
the dump configuration. The default configuration shown in Figure 10-8 is for your
reference.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 239

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-8 Dump configuration

10.2 Configuring SOL

Critical errors, such as system breakdown, sometimes occur during server tests and
daily use. When a critical error occurs, the OS will export some important information
to a serial port. It is inconvenient to connect to the physical serial port to obtain the
information. Therefore, you are advised to configure Serial over LAN (SOL) so that
you can obtain the information using SOL or Intelligent Baseboard Management
Controller (iBMC).
This section describes how to configure SOL on Linux and VMware.

10.2.1 Configuring SOL on Linux

To configure SOL on Linux, modify the boot tool configuration file so that the
parameters are transferred to the kernel during the boot process. For the
configuration method, see the corresponding server OS installation guide cases.

10.2.2 Configuring SOL on VMware

You can configure SOL on VMware using CLI, vSphere Client, or vSphere Web
Client.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 240

Server
OS Installation Guide 10 Locating OS Faults

Using CLI
Step 1 Log in to ESXi Shell or another CLI environment.

Step 2 Run the following commands to configure SOL:

esxcli system settings advanced set -o "/Misc/LogToSerial" --int-value "1"
esxcli system settings advanced set -o "/Misc/DebugLogToSerial" --int-value "1"
esxcli system settings advanced set -o "/Misc/LogPort" --string-value "COM1"
esxcli system settings kernel set --setting=com1_baud --value=115200

Step 3 Run the following commands to check the configuration result:

esxcli system settings advanced list -o "/Misc/LogToSerial"
esxcli system settings advanced list -o "/Misc/DebugLogToSerial"
esxcli system settings advanced list -o "/Misc/LogPort"
esxcli system settings kernel list -o=com1_baud

The command output is as follows:

Step 4 Reboot the server for the configuration to take effect.

----End

Using the vSphere Web Client

Step 1 Install vSphere Web Client on a client.

Step 2 Open vSphere Web Client.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 241

Server
OS Installation Guide 10 Locating OS Faults

Step 3 Open a connection to the server, as shown in Figure 10-9.

Figure 10-9 vSphere Web Client

Step 4 Click the Manage tab on the right.

Step 5 In the navigation pane, choose System > Advanced System Settings.

Step 6 In the filter marked with (4) in Figure 10-9, click and configure related parameters
as follows:
● [Link]: 1
● [Link]: 1
● [Link]: COM1
● [Link].com1_baud: 115200

Step 7 Reboot the server for the configuration to take effect.

----End

10.3 Configure an NMI

If the system fails to respond to your operations, you can click the NMI button on the
server to forcibly trigger a non-maskable interrupt (NMI). Then a memory dump
starts, and services are automatically restarted and restored, while logs are
generated for debugging. The NMI function must be used together with the dump
function.

The NMI button is provided on the iBMC WebUI.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 242

Server
OS Installation Guide 10 Locating OS Faults

Deploying the NMI

On Windows and VMware, you can directly trigger an NMI. On Linux, the following
configuration is required:

Step 1 Add the following to the etc/[Link] file:

kernel.unknown_nmi_panic = 1
kernel.panic_on_unrecovered_nmi = 1

Step 2 Run the sysctl -p command for the configuration to take effect.

----End

Verifying the NMI

NO TICE

Verifying the NMI may cause system breakdown. Do not perform this operation when
running other services.

Step 1 Log in to the iBMC WebUI.

For details, see the iBMC user guide of corresponding server model.
Step 2 On the Power Control page, click NMI. The information shown in Figure 10-10 is
displayed. SLES 11.1 is used as an example.
NO TE

The WebUI varies depending on the iBMC version. For details, see the iBMC user guide of
corresponding server model.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 243

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-10 Print information after the NMI is triggered

----End

10.4 Configuring Magic Keys for Linux

Magic keys allow you to obtain specific information when a black screen occurs.

Configuring Magic Keys

Step 1 Add the [Link] = 1 line to the [Link] file.

Step 2 Run sysctl -p for the configuration to take effect.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 244

Server
OS Installation Guide 10 Locating OS Faults

----End

Verifying Magic Keys

Press Alt+PrtSc+M. Wait for 2 minutes, and then run the dmesg command or
access the serial port to check whether memory information is printed. The following
is an example:

Common Magic Keys

The following magic keys may be useful if a black screen occurs:

● Alt+PrtSc+T: shows the current task information.

● Alt+PrtSc+W: shows processes in the congestion state.
● Alt+PrtSc+C: triggers kdump, which causes the server to automatically reboot.
(Exercise caution when using this key combination.)

NO TE

After using a key combination, wait until the output finishes printing before using another key
combination. This can take at least 3 minutes.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 245

Server
OS Installation Guide 10 Locating OS Faults

10.5 Changing Linux System Log Levels

A huge amount of system logs are recorded when the OS recovers after a crash, and
this makes it difficult to find the key information within the logs. To facilitate fault
location, you can change the system log level to narrow the system logs recorded.

Querying the Serial Port Log Level

Run the command cat /proc/sys/kernel/printk in the OS. The first number in the
command output indicates the serial port log level. For example, the following output
indicates that the serial port log level is 3:
linux-70u8:~ # cat /proc/sys/kernel/printk
3 4 1 7

Changing the Serial Port Log Level

NO TE

Changing the serial port log level takes effect only for the current runtime. After the OS is
rebooted, the serial port log level is restored to the level specified in the configuration file.

In the CLI, run the echo N > /proc/sys/kernel/printk command, where N indicates
the serial port log level to be configured. For details about serial port log levels, see
Table 10-2.
linux-70u8:~ # echo 7 > /proc/sys/kernel/printk
linux-70u8:~ # cat /proc/sys/kernel/printk
7 4 1 7

Table 10-2 Serial port log levels

Severity Kernel Log Level Description

0 KERN_EMERG Emergency messages, which indicate

system unavailability and are reported
before a system breakdown.

1 KERN_ALERT Report messages (alerts), which indicate

that immediate measures must be taken.

2 KERN_CRIT Critical messages, which usually indicate

critical hardware or software failures.

3 KERN_ERR Error messages, which are used by driver

programs to report hardware errors. This is
the default log level of the serial port.

4 KERN_WARNING Warning messages, which indicate that

problems may occur.

5 KERN_NOTICE Normal but important information, for

example, security-related information.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 246

Server
OS Installation Guide 10 Locating OS Faults

Severity Kernel Log Level Description

6 KERN_INFO Prompt information, for example, hardware

information recorded during driver startup.

7 KERN_DEBUG Debugging messages. If this log level is

enabled, the system records all logs.

10.6 Disabling the Screen Saver

If it is not convenient to reboot the server and configure the serial port, use the
Remote Virtual Console of iBMC to switch the OS to CLI and disable the screen
saver. This allows breakdown screenshots to be captured for fault location.
This section uses SLES 11.3 as an example. The key combinations for switching
between CLI and GUI vary slightly according to the OS version. The key combination
is usually Ctrl+Alt+Fx, where x ranges from 1 to 7.
● To switch from GUI to CLI, press Ctrl+Alt+F1 in the Remote Virtual Console, as
shown in Figure 10-11.

Figure 10-11 Switching from GUI to CLI

Run setterm -blank 0 -powersave off -powerdown 0 to disable the screen

saver and retain CLI on the Remote Virtual Console. If the system breaks down
when CLI is running, the last information printed on CLI will be captured.
● To switch back from CLI to GUI, press Ctrl+Alt+F7 in the Remote Virtual
Console, as shown in Figure 10-12.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 247

Server
OS Installation Guide 10 Locating OS Faults

After you switch back to GUI, the screen saver is re-enabled.

Figure 10-12 Switching from CLI to GUI

10.7 Deploying and Verifying Fault Locating Tools on

Linux
Deployment
After the OS is installed, configure fault locating tools in the following order:
1. 10.1 Configuring Memory Dump Tools.
The setting takes effect after a server reboot and remains valid permanently.
2. 10.2 Configuring SOL.
The setting takes effect after a server reboot and remains valid permanently.
3. 10.3 Configure an NMI.
The setting takes effect after a server reboot and remains valid permanently. It
works with Kdump.
4. 10.4 Configuring Magic Keys for Linux.
The setting takes effect immediately and remains valid permanently.
5. 10.5 Changing Linux System Log Levels.
The setting takes effect immediately and reverts after a reboot. Change log
levels only after all other configurations are complete and become effective.
Restore the log levels after fault location.
6. 10.6 Disabling the Screen Saver.
The setting takes effect immediately and reverts after a reboot. Disable the
screen saver only after finishing other configurations.
The preceding fault-location methods do not affect system performance, stability, or
security, except that changing log levels affects the drive space used for storing logs.

Verification
● Verifying kdump
Upon system rebooting, verify that kdump is configured successfully by following
the instructions in 10.1.1 Configuring kdump on Linux, and capture a

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 248

Server
OS Installation Guide 10 Locating OS Faults

screenshot of the generated vmcore information system. Then, save the

screenshot of the VMcore information generated.
● Verifying SOL
Upon system rebooting, use FusionServer Tools to collect management software
logs. Visit the Technical Support Website > Software Download >
FusionServer Tools to download the corresponding version of FusionServer
Tools and operation guide.
– iBMC: Decompress the log file dump_info.[Link] and then decompress the
[Link] file in dump_info\OSDump to obtain the serial port output
log file [Link].
– iMana: Decompress the log file BMC__DATA.[Link] and then decompress
the DATA1_DATA2.[Link] file in .\tmp\collect to obtain the serial port output
log file [Link] in .\tmp\maintenance\maintenance\solinfo.
In the serial port output logs, search e820 to view kernel boot information.
Example output:

● Verify NMI and magic keys.

Run sysctl -p on CLI verify that the command output contains the following
parameters and reports no errors, and capture a screenshot of the command
output.
kernel.unknown_nmi_panic = 1
kernel.panic_on_unrecovered_nmi = 1
[Link] = 1

● Verify log levels.

Run cat /proc/sys/kernel/printk on CLI to verify that the command output is
consistent with the configuration, and capture a screenshot of the command
output.

● Verify that the screen saver is disabled.

After switching from GUI to CLI, run setterm -blank 0 -powersave off -
powerdown 0, observe for 5 minutes, and verify that no black screen occurs.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 249

Server
OS Installation Guide 10 Locating OS Faults

10.8 Troubleshooting

10.8.1 Failed to Start kdump

Symptoms
On Oracle Linux 6.2, the echo c > /proc/srq-trigger command is run to force the
system to crash. After the kdump process starts, the system does not respond. See
Figure 10-13.

Figure 10-13 System not responding

Cause Analysis
This issue may occur due to performance settings on Oracle Linux 6.2.

Solution
Change the value of KDUMP_COMMANDLINE_APPEND to noapic for Oracle Linux
6.2 on an x86 server (64-bit), and change the value of Inter@VT for Directed I/
O(VT-D) in the BIOS to disabled.

10.8.2 Failed to Detect Drives After the kdump Process Starts

Symptoms
The echo c > /proc/srq-trigger command is run to force the system to crash. After
the kdump process starts, the system does not respond, and no drive can be
detected. See Figure 10-14.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 250

Server
OS Installation Guide 10 Locating OS Faults

Figure 10-14 Failed to detect drives

Cause Analysis
● If this problem occurs after a kernel upgrade, the driver version of the RAID
controller card may be earlier than the required version.
● If this problem occurs due to a system internal error, the interruption control
mode of the IOAPIC used by kdump may be incorrect.

Solution
● The problem occurs after a kernel upgrade.
Upgrade the RAID controller card driver to the latest version.
If the problem persists, contact the customer service center.
● The problem occurs due to an internal system error.
Open /etc/sysconfig/kdump, add the noapic parameter to
KDUMP_COMMANDLINE_APPEND, and regenerate the kdump file initrd.
Check whether the problem is rectified.
If the problem persists, contact the customer service center.

10.8.3 OOM Reported After the kdump Process Starts

Symptoms
The system reports an out of memory (OOM) error after the kdump process starts.

Cause Analysis
Memory space is insufficient and needs to be reallocated by changing the value of
crashkernel.

Solution
Step 1 The crashkernel parameter is in the format crashkernel=X@Y.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 251

Server
OS Installation Guide 10 Locating OS Faults

Step 2 Open /boot/grub/[Link] and increase the value of X for crashkernel, for
example:
crashkernel=512M@256M

For i386/x86_64, set X to 128M. For PowerPC, set X to 256M. For RHEL 6 and
SLES 11, set X to 512M (recommended).

----End

10.8.4 Failed to Install an OS on a Drive with RAID Information

Symptoms
An error is reported during the installation of RHEL, as shown in Figure 10-15.

Figure 10-15 Error message

Cause Analysis
The drive on which the OS is to be installed has RAID information.

Solution
● (Recommended) Format the drive and install the OS again. For details, see
"Formatting the hard disk" in section "Disk Utilities" of the RAID controller card
user guide of the corresponding server model.
● (Recommended) Delete RAID information from the drive and install the OS
again. For details, see "Formatting the hard disk" in section "Disk Utilities" of the
RAID controller card user guide of the corresponding server model.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 252

Server
OS Installation Guide 10 Locating OS Faults

10.8.5 Red Hat Linux Displayed on the BIOS Boot Option Menu
During the CentOS 6.X Installation in UEFI Mode
Symptoms
During the CentOS 6.X installation in UEFI mode, Red Hat Linux is displayed on the
BIOS Boot Option menu, as shown in Figure 10-16.

Figure 10-16 BIOS boot option

Cause Analysis
The CentOS 6.X boot path is EFI/redhat/[Link], which is a standard Red Hat boot
directory. The CentOS 7.X boot path is EFI/centos/[Link]. Therefore, Red Hat is
displayed instead of CentOS 6.X, but not CentOS 7.X.

Solution
No action is required because this problem does not affect normal installation.

10.8.6 Blue Screen Is Displayed When the Server Reboots

Upon Installation of Windows Server 2012 R2
Symptoms
After Windows Server 2012 R2 is installed, there is a high probability that blue screen
is displayed when the server reboots.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 253

Server
OS Installation Guide 10 Locating OS Faults

Cause Analysis
Due to system limitations of Windows Server 2012 R2, a server equipped with an LSI
SAS2308 RAID controller card may fail to reboot after Windows Server 2012 R2 is
installed. For details, see Microsoft official website:
[Link]
you-install-update-rollup-2919355-in-window

Solution
Reboot the server for multiple times until the reboot is successful, as shown in Figure
10-17.

Figure 10-17 Windows Server 2012 R2 started successfully

Upon system startup, download the [Link] patch from

Microsoft official website ([Link]
[Link]?id=43257), install the driver of the LSI SAS2308 RAID controller card,
and customize Windows Server 2012 R2 for next installation.
For details about how to customize Windows Server 2012 R2, see the corresponding
server OS Installation Guide Cases.

10.8.7 How to Install a Windows Server 2016 Patch

NO TE

Before installing patches, view the current Windows OS version so that you can check whether
the Windows OS version is updated successfully after patch installation.

Step 1 Download the Microsoft update patch KB4038782.

Link for downloading the update patch: [Link]
4038782/windows-10-update-kb4038782
Step 2 Click Microsoft Update Catalog to go to the download page.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 254

Server
OS Installation Guide 10 Locating OS Faults

Step 3 Select the first patch, and click Download.

Step 4 Click the patch, and download it to a local folder.

Step 5 Mount the downloaded AMD64-all-windows10.0-kb4038782-

x64_5cc8dccc86516830eb0b1aa030d67f482dd05af0.msu file to the virtual folder.

Step 6 Go to the CD Drive folder.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 255

Server
OS Installation Guide 10 Locating OS Faults

Step 7 Double-click the patch and click Yes to install the patch.

Step 8 After the patch is installed, click Restart Now to reboot the server.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 256

Server
OS Installation Guide 10 Locating OS Faults

Step 9 Press Windows key+ R to open the Run dialog box.

Step 10 Type winver in the search box, and press Enter.
Check whether the OS version is updated.

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 257

Server
OS Installation Guide 10 Locating OS Faults

10.8.8 Installing Drivers on Linux

RHEL 7.X and CentOS 7.X

Step 1 Install the driver.
1. Log in to the virtual console of the server.
For details, see 9.2 Logging In to the Virtual Console.
2. Mount the driver file.

3. Run the lspci | grep –i nvidia command on CLI to check whether the GPU has
been identified.
The GPU has been identified if the command output shown in the following
figure is displayed.

4. Disable the Nouveau kernel driver.

a. Run the vim /etc/modprobe.d/[Link] command to edit the
[Link] file.
b. Enter blacklist nouveau in the file and add the Nouveau driver to the
[Link] file.
c. Run the mv /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -
r).[Link] command to back up the initramfs file.
d. Run the dracut -v /boot/initramfs-$(uname -r).img $(uname -r) command
to create a new initramfs file.
e. Reboot the OS.
f. Run the lsmod | grep nouveau command to check whether the Nouveau
driver has been loaded.
5. Run the init 3 command to switch to the text mode.
6. Install the driver.
a. Run the cd command to go to the directory where the driver is located.
b. Run the sh ./NVIDIA-Linux-x86_64-[Link] --no-opengl-files
command to start the installation, and install the driver following the
instructions that appear.
7. Run the nvidia-smi command to verify whether the driver has been installed.

Step 2 Configure the [Link] file.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 258

Server
OS Installation Guide 10 Locating OS Faults

NO TE

If the GUI mode is not required, skip the configuration of the [Link] file.

1. Run the Xorg -configure command to generate a [Link] file in the root
directory.
2. Run the cd /root command to go to the root directory.
3. Run the cp [Link] /etc/X11/[Link] command to copy the
configuration file to the /etc/X11/ directory, and change its name to [Link].
[root@localhost ~]# cp [Link] /etc/X11/[Link]
4. Run the lspci | grep -i vga command to check the value of BusID of the
integrated video card.
[root@localhost ~]# lspci |grep -i vga
37:00.0 VGA compatible controller: Device 19e5:1711 (rev 01)
5. Run the vim /etc/X11/[Link] command to open the configuration file, and
edit Identifier, Driver, and BusID as shown in the following figure.
NO TE

The BusID queried in Step 2.4 is a hexadecimal number and the BusID configured in the
[Link] file is a decimal number. Therefore, number conversion is required in this step.
Section "Device"
### Available Driver options are:-
### Values: <i>: integer, <f>: float, <bool>: "True"/"False",
### <string><freq><f>Hz/kHz/MHz",
### <percent><f>%"
### [arg]: arg optional
#Option "ShadowFB" # [<bool>]
#Option "Rotate" # [<str>]
#Option "fbdev" # [<str>]
#Option "debug" # [<bool>]
Identifier "Card0"
Driver "fbdev"
BusID "PCI:X:X:X"
EndSection
6. Run the :wq! command to save the file and exit.
Step 3 Modify the [Link] file.
NO TE

If the GUI mode is not required, skip the configuration of the [Link] file.

1. Run the vim /boot/grub2/[Link] command to open the configuration file, and
add vga=0x314 to the kernel line.

2. Run the :wq! command to save the file and exit.

3. Run the reboot command to reboot the server.

----End

SLES 11 SP4
Step 1 Run the init 3 command to switch to the text mode.
Step 2 Install the driver.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 259

Server
OS Installation Guide 10 Locating OS Faults

1. Run the cd command to go to the directory where the driver is located.

2. Run the sh ./NVIDIA-Linux-x86_64-[Link] --no-opengl-files
command to start the installation, and install the driver following the instructions
that appear.
Step 3 Run the nvidia-smi command to verify whether the driver has been installed.

----End

Ubuntu14.04 LTS & Ubuntu16.04 LTS

Step 1 Install the driver.
1. Disable the Nouveau kernel driver.
a. Run the vim /etc/modprobe.d/[Link] command to edit the
[Link] file.
b. Enter blacklist nouveau in the file and add the Nouveau driver to the
[Link] file.
c. Run the mv /boot/[Link]-$(uname -r) /boot/[Link]-$(uname -
r).bak command to back up the initramfs file.
d. Run the sudo update-initramfs -c -k $(uname -r) command to create a
new initramfs file.
e. Reboot the OS.
f. Run the lsmod | grep nouveau command to check whether the Nouveau
driver has been loaded.
2. Run the init 3 command to switch to the text mode.
NO TE

If the GUI mode is used by default, press Ctrl+Alt+F1 after you run the init 3 command
to switch to the tty1 window. Then, enter your user name and password.
3. Install the driver.
a. Run the cd command to go to the directory where the driver is located.
b. Run the sh ./NVIDIA-Linux-x86_64-[Link] --no-opengl-files
command to start the installation, and install the driver following the
instructions that appear.
4. Run the nvidia-smi command to verify whether the driver has been installed.

Step 2 Configure the [Link] file. For details, see Step 2 in section "RHEL 7.X and
CentOS 7.X".

----End

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 260

Server
OS Installation Guide A How to Obtain Help

A How to Obtain Help

If you encounter a difficult or critical problem during routine maintenance or

troubleshooting, contact technical support.

A.1 Collecting Fault Information

Collect fault information before troubleshooting.

The information includes:

● Customer full name and detailed address

● Contact person and telephone number
● Time when the fault occurred
● Detailed fault symptoms
● Device type and software version
● Measures taken after the fault occurred and results
● Fault severity and required rectification deadline

A.2 Preparing for Debugging

When you contact technical support, the technical support engineers may assist you
in performing some operations to further collect fault information or rectify the fault.

Before you contact technical support, prepare the spare parts for boards and port
modules, screwdrivers, screws, serial cables, and network cables.

A.3 Using Product Documentation

xFusion provides documents delivered with the equipment. The documents provide
solutions to common problems that occur during routine maintenance or
troubleshooting.

Read the documents carefully before you contact technical support.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 261

Server
OS Installation Guide A How to Obtain Help

A.4 Technical Support

xFusion Digital Technologies Co., Ltd. provides timely and effective support for users
through local branch offices, secondary technical support system, telephone
technical support, remote and on-site technical services.

Technical Support Website

Technical documents are available at xFusion website.

Case Library
To obtain case study about servers, visit Knowledge Base.

Technical Support
xFusion provides comprehensive technical support and services. To obtain
assistance, contact xFusion technical support as follows:
● Contact Hyper-Fusion Digital Technologies Co., Ltd. Technical Support Center.
– Customers in China can contact us on:

▪ Telephone: 400-009-8999

▪ Email: support@[Link]
– Global customers can contact us on Global Service Hotline.
● Contact technical support personnel at the local xFusion office.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 262

Server
OS Installation Guide B Appendix

B Appendix

B.1 Glossary
C

Redirection Users can specify a new port for forwarding packets based on
their own QoS policies.

Serial port An input/output port (channel) that can receive data from or
send data to the CPU or communication device of a computer
by one bit at a time. Serial ports are used as the ports of serial
data communication devices and many peripheral devices such
as mouses and printers.

Blade server A blade server is a standard-height rack server that can be

installed with multiple server blades. It is a low-cost server
platform that features high availability and density.

Port Physical socket on the panel.

sensor A special computer that provides services for clients over a

network.

Floating IP Also called a dynamic IP address. An address that is assigned

address to a computer every time it connects to the Internet. Unlike a
static IP address that will be the same every time the user logs
on, a dynamic IP address is different every time.

Internet A cooperative virtual network, which integrates packet switching

network connecting routers and TCP/IP.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 263

Server
OS Installation Guide B Appendix

IP Address A 32-bit (4-byte) binary number that uniquely identifies a host

(computer) connected to the Internet for communication with
other hosts in the Internet by transferring packets. An IP
address is expressed in dotted decimal notation, consisting of
the decimal values of its 4 bytes, separated with periods; for
example, [Link]. The first three bytes of the IP address
identify the network to which the host is connected, and the last
byte identify the host itself.

Rack server A server with a rack structure. The rack structure is a standard
device structure in a traditional telecom equipment room. The
width of the rack structure is 19 inches and its height is
measured by Us.

Chassis A physical entity that consists of the subrack, slot, backplane,

cooling device, and power supply device. Components are
placed and interconnected in the chassis. The chassis protects
the components against pollution and damage.

Port A port through which the server system exchanges data with
other devices on the network and interacts with each other,
such as the port to VLAN. The function of a port is to complete
the data exchange between the server and other network
devices.

Static IP An IP address that is assigned to a user by the local network

address management center and does not change unless it is changed
manually. This is in contrast to a dynamic IP address which may
change at any time. With a static IP address, a computer's
identity can be easily known by others, and other users can
easily connect to it.

Local area A network composed of personal computers and workstations

network (LAN) connected in the same building or within a few square
kilometers. It features high speed and low error rate. Ethernet,
FDDI, and token ring are three main technologies of LAN.
Existing LANs are typically built based on switched Ethernet or
Wi-Fi technology, running at 1000 Mbit/s (1 Gbit/s).

KVM A switcher that provides public video, keyboard and mouse for
all server blades.

Console A configuration port in a server blade, which is a synchronous

serial port.

Screw-in RAID A card connected to the mainboard through the connector, level
controller card to the mainboard. It is used on a device which has high
requirement on space.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 264

Server
OS Installation Guide B Appendix

Panel An external component (including but not limited to ejector

levers, indicators, and ports) on the front or rear of the server. It
seals the front and rear of the chassis to ensure optimal
ventilation and electromagnetic compatibility (EMC).

PCIe A short form of Peripheral Component Interconnect Express

(PCIe). It is a new bus standard, which can replace PCI and
AGP interface specifications. Through the point-to-point and bi-
directional interconnection technology, PCI or AGP parallel data
transmission is changed into serial data transmission. Using this
standard, the data transmission speed between devices can be
improved greatly.

Configuration The configuration file saves the user's server blade

file configuration in command lines and records the entire
configuration process. It allows users to check and view the
configurations conveniently.

network port Numbers which are recognized by Internet and other network
protocols, enabling the computer to interact with others.

network cable The Ethernet cables used by the current products include
standard network cables and straight-through cables. In the
aspect of network connection, the network cables are divided
into two types: straight-through cables and crossover cables.

Write protect Prevents writing information. This is a protection mechanism

that protects important data from being changed or deleted.

Verification Verification is the process of verifying whether a user can gain

access and determining which users can access the network.

Ethernet A technology complemented in LAN. It adopts Carrier Sense

Multiple Access/Collision Detection. The speed of an Ethernet
interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s or 10000
Mbit/s. The Ethernet network features high reliability and easy
maintaining.

User interface The user interface is a configuration interface parallel to the

interface view provided by a server blade. The UI is used to
configure and manage the configuration data of all physical and
logical interfaces in asynchronous and interactive mode. In this
way, user configurations are managed in a unified manner.

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 265

Server
OS Installation Guide B Appendix

Terminal Only the keyboard and monitor do not have disk drives and can
be connected to other devices through the serial ports.

Host A computer that allows multiple users in the network to access

at the same time.

B.2 Acronyms and Abbreviations

B

BIOS Basic Input/Output System Basic Input/Output

System

CPLD Complex Programmable Logical Complex Programmable

Device Logical Device

CPU Central Processing Unit Central Processing Unit

DHCP Dynamic Host Configuration Protocol Dynamic Host

Configuration Protocol

FC Fiber Channel Fiber Channel

GRUB Grand Unified Bootloader Grand Unified Bootloader

iBMC Intelligent Baseboard Management Integrated Baseboard

Controller Management Controller

IE Internet Explorer Internet Explorer

IP Internet Protocol Internet Protocol

JRE Java Runtime Environment Java Runtime

Environment

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 266

Server
OS Installation Guide B Appendix

KVM Keyboard, Video, and Mouse Keyboard, Video, and

Mouse

LAN Local Area Network Local Area Network

NMI Non-maskable Interrupt Non-maskable Interrupt

OS Operating System Operating System

PC Personal Computer Personal Computer

PXE Preboot Execute Environment Preboot Execution

Environment

RAID Redundant Array of Independent Redundant Array of

Disks Independent Disks

RJ45 Registered Jack 45 Registered Jack 45

SAN Storage Area Network Storage Area Network

SAS Serial Attached SCSI Serial Attached SCSI

SATA Serial Advanced Technology Serial Advanced

Attachment Technology Attachment

SD Secure Digital Card Secure Digital Card

SFTP Secure File Transfer Protocol Secure File Transfer

Protocol

SKU Stock Keeping Unit Stock Keeping Unit

SOL Serial Over LAN Serial Over LAN

UEFI Unified Extensible Firmware Interface Unified Extensible

Firmware Interface

USB Universal Serial Bus Universal Serial Bus

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 267

Server
OS Installation Guide B Appendix

UTC Universal Time Coordinated Universal Time

Coordinated

VD Virtual Drive Virtual Drive

VGA Video Graphics Array Video Graphics Array

WebUI Web User Interface Web User Interface

Issue 09 (2025-07-30) Copyright © XFUSION INTERNATIONAL PTE. LTD. 268