Page is loading ...
H3C Servers
Operating System Installation Guide
New H3C Technologies Co., Ltd.
http://www.h3c.com
Document version: 6W103-20181114
Copyright © 2018, New H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior written
consent of New H3C Technologies Co., Ltd.
Trademarks
Except for the trademarks of New H3C Technologies Co., Ltd., any trademarks that may be mentioned in this
document are the property of their respective owners.
Notice
The information in this document is subject to change without notice. All contents in this document, including
statements, information, and recommendations, are believed to be accurate, but they are presented without
warranty of any kind, express or implied. H3C shall not be liable for technical or editorial errors or omissions
contained herein.
Preface
This preface includes the following topics about the documentation:
• Audience.
• Conventions.
• Documentation feedback.
Audience
This documentation is intended for:
• Network planners.
• Field technical support and servicing engineers.
• Server administrators working with the Server.
Conventions
The following information describes the conventions used in the documentation.
Command conventions
Convention Description
Boldface Bold
text represents commands and keywords that you enter literally as shown.
Italic
Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars,
from which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select a minimum of one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n>
The argument or keyword and argument combination before the ampersand (&) sign
can be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.
GUI conventions
Convention Description
Boldface
Window names, button names, field names, and menu items are in Boldface. For
example, the
New User
window opens; click
OK
.
>
Multi-level menus are separated by angle brackets. For example,
File
>
Create
>
Folder
.
Symbols
Convention Description
WARNING!
An alert that calls attention to important information that if not understood or followed
can result in personal injury.
CAUTION:
An alert that calls attention to important information that if not understood or followed
can result in data loss, data corruption, or damage to hardware or software.
IMPORTANT:
An alert that calls attention to essential information.
NOTE:
An alert that contains additional or supplementary information.
TIP:
An alert that provides helpful information.
Network topology icons
Convention Description
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that
supports Layer 2 forwarding and other Layer 2 features.
Represents an access controller, a unified wired-WLAN module, or the access
controller engine on a unified wired-WLAN switch.
Represents an access point.
Represents a wireless terminator unit.
Represents a wireless terminator.
Represents a mesh access point.
Represents omnidirectional signals.
Represents directional signals.
Represents a security product, such as a firewall, UTM, multiservice security
gateway, or load balancing device.
Represents a security module, such as a firewall, load balancing, NetStream, SSL
VPN, IPS, or ACG module.
Examples provided in this document
Examples in this document might use devices that differ from your device in hardware model,
configuration, or software version. It is normal that the port numbers, sample output, screenshots,
and other information in the examples differ from what you have on your device.
T
T
T
T
Documentation feedback
You can e-mail your comments about product documentation to info@h3c.com.
We appreciate your comments.
i
Contents
Overview ························································································ 1
Installation workflow ·········································································· 2
Selecting an installation mode ····························································· 3
Installing an OS ··············································································· 4
Preparing for installation ·············································································································· 4
Logging in to the server ········································································································ 4
Preparing an OS image ········································································································ 4
Obtaining a storage controller driver file ················································································· 10
Setting the BIOS boot mode ································································································ 11
Configuring RAID ·············································································································· 13
Procedure ······························································································································ 13
Installing a Windows OS ····································································································· 13
Installing a Red Hat/CentOS 6.x OS ······················································································ 21
Installing a Red Hat/CentOS 7.x OS ······················································································ 33
Installing an SUSE OS ······································································································· 43
Installing a VMware ESXi OS ······························································································· 54
Installing a Citrix OS ·········································································································· 61
Installing a Ubuntu OS ········································································································ 72
Installing a CAS OS ··········································································································· 81
Installing a network adapter ······························································ 82
Overview ································································································································ 82
Installing a Windows network adapter ··························································································· 82
Checking network adapter version ························································································ 82
Installing the network adapter ······························································································ 84
Installing a Linux network adapter ································································································ 85
Checking network adapter version ························································································ 85
Installing the network adapter ······························································································ 86
Troubleshooting ············································································· 87
SUSE11SP4 installation failure in Legacy or UEFI mode ·································································· 87
No boot options can be found ····································································································· 88
Failure to enter SUSE OS in Legacy mode ···················································································· 88
An error occurred during SLES12 OS installation ············································································ 88
Failure to install an OS by using PXE ··························································································· 89
Failure to install a VMware OS when only mLOM adapters are installed ·············································· 89
HBA-H460-M1 storage controller drive can be installed successfully only after two installation operations ··· 89
SUSE12SP2 OS installation in Legacy and UEFI modes takes a long time and the webpage is stuck after
installation ······························································································································ 90
Storage controller HBA-H460-M1 FW1.04 can be installed successfully on an RHEL OS but the system
prompts installation failure ········································································································· 91
Bluescreen or kernel error occurred when BIOS NUMA is enabled and IMC0 and IMC1 for CPU 1 or CPU 2 are
disabled ································································································································· 91
An error occurred on an NVMe drive and the drive went offline after a managed hot plug ························ 92
A blue screen occurred when the network adapter-10GE-2P-520F-B2-1 driver was being installed ··········· 93
Some NVMe drives might fail to be identified when multiple NVme drives are installed after OS installation 94
Failed to install CASE0306 on an NVMe SSD drive ········································································· 94
The system cannot be restored after the server is powered down unexpectedly ···································· 94
Bluescreen occurred if chipset drivers are installed before GPU-M60-1 and GPU-M60-1-X display card drivers
are installed on the Windows system ···························································································· 95
Bluescreen occurred during the installation of the IB-MCX354A-FCBT-56/40Gb-2P network adapter driver on
Windows Server 2012 R2 ·········································································································· 95
OS installation takes a long time when the OS image is mounted through an HDM shared network interface97
CAS E0306 OS installation failure ······························································································· 97
1
Overview
This document provides information about operating system installation methods available for the
server at the time of this writing. The operating system installation methods available for the server
are subject to change over time. For the most up-to-date operating system installation methods,
consult your sales representative.
The model name of a hardware option in this document might differ slightly from its model name
label.
A model name label might add a prefix or suffix to the hardware-coded model name for purposes
such as identifying the matching server brand or applicable region. For example, the
DDR4-2666-8G-1Rx8-R memory model represents memory module labels including
DDR4-2666-8G-1Rx8-R, DDR4-2666-8G-1Rx8-R-F, and DDR4-2666-8G-1Rx8-R-S, which have
different suffixes.
This document describes how to install an operating system (OS) in the BIOS Setup Utility through a
drive, optical disk drive, bootable USB disk, and virtual media.
This guide is applicable to the following products:
• H3C UniServer R6900 G3
• H3C UniServer R4900 G3
• H3C UniServer R4700 G3
• H3C UniServer R2900 G3
• H3C UniServer R2700 G3
2
Installation workflow
Figure 1 Installation workflow
Start
Drive detected?
Install storage
controller driver
OS installation completed
Install device driver
End
No
Yes
Prepare OS image
Configure RAID
3
Selecting an installation mode
Obtaining the OS compatibility matrixes
Visit www.h3c.com.hk, and then select Technical Support > Technical Documents.
Checking the installation method for the target OS
As a best practice, download a driver from the H3C website.
For storage controller and operating system compatibility, see H3C UniServer R4900 G3 Server
Hardware Option and Operating System Compatibility Matrices, H3C UniServer R4700 G3 Server
Hardware Option and Operating System Compatibility Matrices, H3C UniServer R2900 G3 Server
Hardware Option and Operating System Compatibility Matrices, H3C UniServer R2700 G3 Server
Hardware Option and Operating System Compatibility Matrices, and H3C UniServer R6900 G3
Server Hardware Option and Operating System Compatibility Matrices.
4
Installing an OS
Information on the BIOS setup utility might be subject to change over time.
Preparing for installation
Logging in to the server
You can log in to the server through KVM or the HDM remote console.
Preparing an OS image
Before installing an OS, obtain an OS image from the official website of the OS, and then connect the
boot media that contain the OS image to the server.
• For KVM login, you can use an optical disk drive, bootable USB disk, or PXE server as the boot
media. Using a PXE server as the boot media is applicable to batch OS installation.
• For HDM login, you can use an optical disk drive, bootable USB disk, PXE server, or virtual
media (virtual disk, CD/DVD, or drive/USB) as the boot media.
Prepare an OS image as shown in the following table.
Table 1 Preparing an OS image
Boot media Preparing for installation
Optical disk drive Insert the optical disk drive that contains the OS image into the optical drive.
Bootable USB drive
Insert the bootable USB disk that contains the OS image into the USB port.
The server might be unable to install an OS if you use a Windows tool to
create a Red Hat Enterprise Linux 7.x bootable USB drive. To resolve this
issue, make sure the label name of the USB drive is the same as the label
name in
inst.stage2=hd:LABEL=
labelname
of the
linuxefi
line in the
/EFI/BOOT/grub.cfg
file and the
append
line in the
/isolinux/isolinux.cfg
file.
Change the
labelname
in LABEL=
labelname
to the label name of the
USB drive, rhel7.2 for example, and then save the modification.
PXE server
1. Prepare a PXE server, and then connect the PXE server to an Ethernet
port on the server where the OS is to be installed.
2. Upload the OS image to the PXE server.
3. Enable PXE (enabled by default) on the server where the OS is to be
installed. For more information, see "Enabling PXE (for H3C UniServer
R49
00/4700/2900/2700 G3)."
Virtual media
Mount the OS image through HDM. For more information, see "Mounting an
OS image through HDM."
Enabling PXE (for H3C UniServer R4900/4700/2900/2700 G3)
PXE is enabled by default and cannot be disabled if the BIOS boot mode is Legacy. This section
describes how to enable PXE in UEFI boot mode. For more information about BIOS boot modes, see
"Setting the BIOS boot mode."
T
o enable PXE:
1. Enter the BIOS Setup Utility.
5
2. Click the Advanced tab, select Network Stack Configuration, and then press Enter.
3. Set Network Stack, IPv4 PXE Support, and IPv6 PXE Support to Enabled.
Figure 2 Enabling PXE
4. Press F4 to save the configuration and reboot the server.
5. Click the Save & Exit tab, and then select the boot option for PXE in the Boot Override area.
The boot options for UEFI and Legacy boot modes are different.
For UEFI boot mode, select the option corresponding to the port connecting to the PXE server.
As shown in Figure 3, port
1 connects to the PXE server, so you must select the option
corresponding to port 1.
Figure 3 PXE boot options in UEFI boot mode
In Legacy boot mode, all ports on the network adapter share the same PXE boot option.
6
Figure 4 PXE boot options in Legacy boot mode
Enabling PXE (for H3C UniServer R6900 G3)
1. Enter the Front Page.
2. Select Setup Utility.
3. Click the Boot tab, and then set Network Stack to Enabled.
4. Select UEFI:IPV4/IPV6 for PXE Boot Capability.
Figure 5 Enabling PXE
5. Press F4 to save the configuration and reboot the server.
6. Enter the Front Page, and then select Windows Boot Manager.
7
7. Select PXE boot options in the EFI Boot Devices area.
The boot options for UEFI and Legacy boot modes are different.
For UEFI boot mode, select the option corresponding to the port connecting to the PXE server.
As shown in Figure 3, port
1 connects to the PXE server, so you must select the option
corresponding to port 1.
Figure 6 PXE boot options in UEFI boot mode
In Legacy boot mode, all ports on the network adapter share the same PXE boot option.
Figure 7 PXE boot options in Legacy boot mode
8
Mounting an OS image through HDM
This section mounts a virtual CD/DVD.
To mount an OS image through HDM:
1. Log in to the server from the HDM console.
2. Select Media > Virtual Media Wizard from the navigation bar.
Figure 8 Virtual Media
3. Click the CD/DVD tab, and then click Browse in the CD/DVD Media: I area. In the dialog box
that opens, select a CD/DVD file, and then click Open.
9
Figure 9 Selecting a CD/DVD file
4. Click Connect to complete mounting the CD/DVD image file.
Figure 10 Mounting a CD/DVD image file
5. Display the mounted image.
10
{
For H3C UniServer R4900/4700/2900/2700 G3, enter the BIOS Setup Utility, and then click
the Save & Exit tab. If you can find the mounted image file in the Boot Override area, the
file has been mounted successfully.
Figure 11 Displaying the mounted image
{
For H3C UniServer R6900 G3, enter the Front Page, and then select Windows Boot
Manager. If you can find the mounted image file in the EFI Boot Devices area, the file has
been mounted successfully.
Figure 12 Displaying the mounted image
Obtaining a storage controller driver file
During the OS installation process, a storage controller driver file might be needed. As a best
practice, obtain a storage controller driver file from the H3C website before installing an OS.
11
Setting the BIOS boot mode
Setting the BIOS boot mode for H3C UniServer R4900/4700/2900/2700 G3
The Legacy and UEFI boot modes are available. The default mode is UEFI. For the BIOS boot
modes supported by different operating systems, see the operating system compatibility matrices for
the server.
To set the BIOS boot mode:
1. In the BIOS Setup Utility, click the Boot tab, select Boot mode select, and then press Enter.
Figure 13 Setting the BIOS boot mode
2. Select the Legacy or UEFI mode, and then press Enter.
Figure 14 Selecting a BIOS boot mode
3. Press F4 to save the configuration and reboot the server.
Setting the BIOS boot mode for H3C UniServer R6900 G3
The Legacy and UEFI boot modes are available. The default mode is UEFI. For the BIOS boot
modes supported by different operating systems, see the operating system compatibility matrixes for
the server.
12
To set the BIOS boot mode:
1. On the Front Page, select Setup Utility, click the Boot tab, select a boot type, and then press
Enter.
Figure 15 Setting the BIOS boot mode
2. Select the Legacy or UEFI mode, and then press Enter.
Figure 16 Selecting a BIOS boot mode
13
3. Press F4 to save the configuration and reboot the server.
Configuring RAID
For more information, see H3C Server Storage Controller User Guide.
Procedure
Installing a Windows OS
The installation procedure is the same for different Windows OS versions. This section uses
Windows Server 2012 R2 as an example.
A Windows OS cannot be installed on a dual SD card.
To install a Windows OS:
1. Enter BIOS and select boot options:
{
For H3C UniServer R4900/4700/2900/2700 G3, enter the BIOS Setup Utility, select a boot
option in the Save & Exit tab, and then press Enter. This example selects UEFI:AMI
Virtual CDROM0 1.00.
Figure 17 Selecting a boot option
{
For H3C UniServer R6900 G3, enter the Front Page, in the Boot Manager, select a boot
option, and then press Enter. This example selects EFI USB Device(AMI Virtual
CDROM0.
/
