FusionServer 2288H V5 Server User Guide 21
FusionServer 2288H V5 Server User Guide 21
User Guide
Issue 21
Date 2024-05-11
Notice
In this document, "xFusion" is used to refer to "xFusion Digital Technologies Co., Ltd." for concise description
and easy understanding, which does not mean that "xFusion" may have any other meaning. Any "xFusion"
mentioned or described hereof may not be understood as any meaning other than "xFusion Digital
Technologies Co., Ltd.", and xFusion Digital Technologies Co., Ltd. shall not bear any liability resulting from
the use of "xFusion".
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.
Website: https://www.xfusion.com
Purpose
This document describes the FusionServer 2288H V5 in terms of its appearance,
functions, structure, hardware installation, basic configuration, OS installation
methods, and troubleshooting.
Intended Audience
This document is intended for:
● Enterprise administrators
● Enterprise end users
Symbol Conventions
The symbols that may be found in this document are defined as follows:
Symbol Description
Change History
Issue Date Description
Contents
2 Hardware Description......................................................................................................5
2.1 Front Panel.................................................................................................................................................. 5
2.1.1 Appearance...............................................................................................................................................5
2.1.2 Indicators and Buttons.............................................................................................................................. 7
2.1.3 Ports........................................................................................................................................................13
2.2 Rear Panel.................................................................................................................................................15
2.2.1 Appearance.............................................................................................................................................16
2.2.2 Indicators ............................................................................................................................................... 16
2.2.3 Ports .......................................................................................................................................................18
2.3 Processor...................................................................................................................................................20
2.4 Memory......................................................................................................................................................21
2.4.1 DDR4 Memory........................................................................................................................................ 21
2.4.1.1 Memory Identifier................................................................................................................................. 21
2.4.1.2 Memory Subsystem Architecture......................................................................................................... 22
2.4.1.3 Memory Compatibility.......................................................................................................................... 23
2.4.1.4 DIMM Installation Rules.......................................................................................................................25
2.4.1.5 Memory Installation Positions.............................................................................................................. 26
2.4.1.6 Memory Protection Technologies.........................................................................................................27
2.4.2 DCPMM.................................................................................................................................................. 28
2.4.2.1 Memory Identifier................................................................................................................................. 28
2.4.2.2 Memory Subsystem Architecture......................................................................................................... 29
2.4.2.3 Memory Compatibility.......................................................................................................................... 30
2.4.2.4 DIMM Installation Rules.......................................................................................................................31
2.4.2.5 Memory Installation Positions.............................................................................................................. 32
2.4.2.6 Memory Protection Technologies.........................................................................................................33
2.5 Storage...................................................................................................................................................... 34
2.5.1 Drive Configuration................................................................................................................................. 34
3 Product Specifications.................................................................................................. 85
3.1 Technical Specifications.............................................................................................................................85
3.2 Environmental Specifications.....................................................................................................................91
3.3 Physical Specifications ............................................................................................................................. 93
6 ESD................................................................................................................................100
6.1 ESD Prevention....................................................................................................................................... 100
6.2 Grounding Methods for ESD Prevention..................................................................................................101
8 Troubleshooting Guide................................................................................................155
9 Common Operations................................................................................................... 156
9.1 Querying the iBMC IP Address ............................................................................................................... 156
9.2 Querying the Mainboard iBMC Management Chip Type......................................................................... 157
9.3 Logging In to the iBMC WebUI................................................................................................................ 159
9.3.1 Logging In to the iBMC WebUI (V561 or earlier).................................................................................. 159
9.3.2 Logging In to the iBMC WebUI (V561 or Later).................................................................................... 163
9.3.3 Logging In to the iBMC WebUI (iBMC V3.02.00.00 or Later)............................................................... 170
9.4 Logging In to the Desktop of a Server..................................................................................................... 176
9.4.1 Using the Remote Virtual Console........................................................................................................176
10 More Information........................................................................................................233
10.1 Obtaining Technical Support..................................................................................................................233
10.2 Maintenance Tools.................................................................................................................................233
A Appendix...................................................................................................................... 237
A.1 Chassis Label..........................................................................................................................................237
A.1.1 On the Front Top...................................................................................................................................237
B Glossary....................................................................................................................... 259
B.1 A-E...........................................................................................................................................................259
B.2 F-J........................................................................................................................................................... 259
B.3 K-O.......................................................................................................................................................... 260
B.4 P-T...........................................................................................................................................................260
B.5 U-Z...........................................................................................................................................................261
1 Overview
NO TE
For details about the 2288H V5 nameplate information, see A.4 Nameplate .
13 FlexIO 14 Mainboard
17 Memory 18 Processor
19 Heat sink - -
● The RAID controller card on the mainboard connects to CPU 1 through PCIe
buses, and connects to the drive backplane through SAS high-speed cables. A
variety of drive backplanes are provided to support different local storage
configurations.
● The LBG-2 Platform Controller Hub (PCH) supports:
– Two 10GE optical LOM ports or two 10GE electrical LOM ports
– Two GE electrical LOM ports
● Uses the BMC management chip, and supports a VGA, a management network
port, a debugging serial port, and other management ports.
● The BMC management chip can be an enhanced management chip (VB) or an
ordinary management chip.
2 Hardware Description
2.1.1 Appearance
● 8 x 2.5" drive configuration
9 Power button/indicator - -
9 NMI button - -
2.1.3 Ports
Port Positions
● 8 x 2.5" drive configuration
3 VGA port - -
3 VGA port - -
Port Description
Note: The number of ports varies depending on server configuration. This table
lists the maximum number of ports in different configurations.
2.2.1 Appearance
Figure 2-19 Rear view
NO TE
● I/O modules 1, 2 and 3 can be configured with drive modules or PCIe riser modules.
● The preceding figure is for reference only.
2.2.2 Indicators
Indicator Positions
Indicator Description
UID Indicator The UID indicator helps identify and locate a device.
● Off: The device is not being located.
● Blinking or steady blue: The device is being located.
NOTE
You can turn on or off the UID indicator by pressing the UID
button or remotely running a command on the iBMC CLI.
Indicator Description
2.2.3 Ports
Port Positions
7 PSU socket 8 -
Port Description
2.3 Processor
● The server supports one or two processors.
● If only one processor is required, install it in socket CPU1.
● The same model of processors must be used in a server.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
2.4 Memory
Install the memory modules in the primary memory channels first. If the primary
memory channel is not populated, the memory modules in secondary memory
channels cannot be used.
A DIMM001(G)
B (primary) DIMM010(B)
B DIMM011(H)
C (primary) DIMM020(C)
C DIMM021(I)
D (primary) DIMM030(D)
D DIMM031(J)
E (primary) DIMM040(E)
E DIMM041(K)
F (primary) DIMM050(F)
F DIMM051(L)
A DIMM101(G)
B (primary) DIMM110(B)
B DIMM111(H)
C (primary) DIMM120(C)
C DIMM121(I)
D (primary) DIMM130(D)
D DIMM131(J)
E (primary) DIMM140(E)
E DIMM141(K)
F (primary) DIMM150(F)
F DIMM151(L)
NO TICE
● A server must use the same model of DDR4 DIMMs, and all the DIMMs operate at
the same speed, which is the smallest value of:
● Memory speed supported by a processor
● Maximum operating speed of a DIMM
● The DDR4 DIMMs of different types (RDIMM and LRDIMM) and specifications
(capacity, bit width, rank, and height) cannot be used together.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
● The memory can be used with Intel® Xeon® Scalable Skylake and Cascade
Lake processors. The maximum memory capacity supported varies depending
on the processor model.
– Skylake processors
▪ M processors: 2 TB/socket
NO TICE
● The total memory capacity cannot exceed the maximum memory capacity
supported by the CPUs.
● The total memory capacity refers to the capacity when DDR4 DIMMs are fully
configured. For details about the memory capacity when DCPMMs are used
together with DDR4 DIMMs, see 2.4.2.3 Memory Compatibility.
● Use the Compatibility List to determine the capacity type of a single memory
module.
● The maximum number of DIMMs supported by a server varies depending on the
CPU type, memory type, rank quantity, and operating voltage.
NO TE
Each memory channel supports a maximum of 8 ranks. The number of DIMMs supported
by each channel varies depending on the number of ranks supported by each channel:
Number of DIMMs supported by each channel ≤ Number of ranks supported by each
memory channel/Number of ranks supported by each DIMM
● A memory channel supports more than eight ranks for LRDIMMs.
NO TE
Parameter Specifications
This section applies to a server fully configured with DDR4 DIMMs. If DCPMMs are used
together, see 2.4.2.4 DIMM Installation Rules.
● Observe the following when configuring DDR4 memory modules:
– Install memory modules only when corresponding processors are installed.
– Do not install LRDIMMs and RDIMMs in the same server.
– Install filler memory modules in vacant slots.
● Observe the following when configuring DDR4 memory modules in specific
operating mode:
– Memory sparing mode
NO TICE
At least one DDR4 DIMM must be installed in the memory slots corresponding to
CPU 1.
2.4.2 DCPMM
3 Model NMA1XBD612GQS
4 Capacity ● 128 GB
● 256 GB
● 512 GB
5 SN QR code 8089-A2-1839-00001931
A DIMM001(G)
B (primary) DIMM010(B)
B DIMM011(H)
C (primary) DIMM020(C)
C DIMM021(I)
D (primary) DIMM030(D)
D DIMM031(J)
E (primary) DIMM040(E)
E DIMM041(K)
F (primary) DIMM050(F)
F DIMM051(L)
A DIMM101(G)
B (primary) DIMM110(B)
B DIMM111(H)
C (primary) DIMM120(C)
C DIMM121(I)
D (primary) DIMM130(D)
D DIMM131(J)
E (primary) DIMM140(E)
E DIMM141(K)
F (primary) DIMM150(F)
F DIMM151(L)
NO TICE
● The DCPMMs must be used with the DDR4 memory modules. For details, see the
FusionServer PMem 200-Barlow Pass User Guide.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
● The memory must be used with Intel® Xeon® Scalable Cascade Lake
processors. The maximum memory capacity supported varies depending on the
processor model.
– L processors: 4.5 TB/socket
– M processors: 2 TB/socket
– Other processors: 1 TB/socket
● The DCPMM can work only in App Direct Mode (AD) and Memory Mode (MM).
The total supported memory capacity is calculated as follows:
– DCPMM in AD mode
Total memory capacity = Total capacity of all DCPMMs + Total capacity of all
DDR4 memory modules
– DCPMM in MM mode
Total memory capacity = Total capacity of all DCPMMs (The DDR4 memory
modules are used as the cache and therefore are not calculated as memory
capacity.)
NO TICE
● The total memory capacity cannot exceed the maximum memory capacity
supported by the CPUs.
● For details about the AD and MM modes, see "Operating Modes" in
FusionServer PMem 200-Barlow Pass User Guide.
● Use the Compatibility List to determine the capacity type of a single memory
module.
Item Specifications
Item Specifications
Full-series 1 TB
M series 2 TB
L series 4.5 TB
2.5 Storage
● a: For now, this configuration only supports Avago MegaRAID SAS 9440-8i
(P/N: 02312QWY) and Avago MegaRAID SAS 9460-8i (P/N: 02312QWV) PCIe
plug-in RAID controller card.
● b: For now, this configuration only supports LSI SAS3108 screw-in RAID
controller card.
● c: The rear I/O module 1 (2 x 2.5") uses the module "Rear HDD + PCIe Riser
Module", for details, see 2.7.2 PCIe Slots.
● d: Only when Avago SAS3416iMR, Avago SAS3416IT screw-in RAID controller
cards are configured, I/O module 3 supports SAS/SATA drives.
● e: All slots support mixed installation of SAS/SATA/NVMe drives.
● f: Only when Avago SAS3416iMR, Avago SAS3416IT screw-in RAID controller
cards are configured, built-in drive is supported.
● g: Normal drive management mode only supports Avago SAS3516 PCIe plug-in
RAID controller card.
● h: Normal drive management mode only supports Avago SAS3416iMR, Avago
SAS3416IT screw-in RAID controller card.
● i: Only when Avago SAS3416iMR, Avago SAS3416IT screw-in RAID controller
cards are configured, I/O module 3 supports NVMe drives.
● j: Normal drive management rmode equires one RAID controller card for every
eight front drives. A maximum of three RAID controller cards are supported.
● k: Only when Avago SAS3516 PCIe plug-in RAID controller card is configured,
I/O module 3 supports SAS/SATA drives.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
When the common hard drive management mode is PCH, each SATA drive has a fixed ATA
number. ATA numbers provided in this section are based on the assumption that the hard drive
management mode is PCH. The following table lists the mapping between ATA numbers and
physical hard drive numbers.
● 8 x 2.5" drive pass-through configuration 1 and 8 x 2.5" drive pass-through
configuration 2
Figure 2-35 Drive numbering (I/O module 1 with 2 x 3.5" SAS/SATA drives)
0 ATA3
1 ATA4
2 ATA5
3 ATA6
4 ATA7
5 ATA8
6 ATA9
7 ATA10
8 ATA11
9 ATA12
10 ATA13
11 ATA14
0 ATA3
1 ATA4
2 ATA5
3 ATA6
4 ATA7
5 ATA8
6 ATA9
7 ATA10
0 ATA3
1 ATA4
2 ATA5
3 ATA6
● If the VMD function is enabled and the latest VMD driver is installed, the NVMe
drives support surprise hot swap.
● If the VMD function is disabled, NVMe drives support only orderly hot swap.
M.2 FRU fault indicator ● Off: The M.2 FRU is running properly.
● Blinking yellow: The M.2 FRU is being located, or
RAID is being rebuilt.
● Steady yellow: The M.2 FRU is faulty or not detected.
M.2 FRU activity ● Off: The M.2 FRU is not in position or is faulty.
indicator ● Blinking green: Data is being read, written, or
synchronized.
● Steady green: The M.2 FRU is inactive.
2.6 Network
2.6.1 LOMs
LOMs provide network expansion capabilities.
● Use Compatibility List to obtain information about the cables and optical
modules supported by the LOM ports.
● The LOM ports support NC-SI, WOL, and PXE.
● The LOM ports do not support forced rates.
● The electrical LOM ports cannot be connected to power over Ethernet (PoE)
devices (such as a switch with PoE enabled). Connecting a LOM port to a PoE
device may cause link communication failure or even damage the NIC.
● The electrical LOM ports (GE electrical ports) do not support SR-IOV.
● Forcibly powering off a server will cause intermittent NC-SI disconnection and
disable the WOL function of the LOM ports. To restore the NC-SI connection,
refresh the iBMC WebUI.
Indicator Positions
Indicator Description
● The FlexIO card (with electrical ports) cannot be connected to power over
Ethernet (PoE) devices (such as a switch with PoE enabled). Otherwise, link
communication failure or even damage to the FlexIO card may be caused.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
● When IB cards are used to build an IB network, ensure that the IPoIB modes of
the IB cards at both ends of the network are the same. For details, contact
technical support.
Indicator Positions
● SM210/SM212 with four GE electrical ports
● SM330 with two 10GE optical ports/SM380 with two 25GE optical ports
Indicator Description
10GE optical port Transmission rate ● Off: The network port is not
indicator connected or the data transmission
rate is 100 Mbit/s.
● Steady green: The data transmission
rate is 10 Gbit/s.
● Steady yellow: The data
transmission rate is 1 Gbit/s.
25GE optical port Transmission rate ● Off: The network port is not
indicator connected.
● Steady green: The data transmission
rate is 25 Gbit/s.
● Steady yellow: The data
transmission rate is 10 Gbit/s.
56G IB optical port Connection status ● Off: No physical link is set up.
indicators ● Blinking green: The physical link is
abnormal.
● Steady green: The physical link is
normal.
NO TE
● The B/D/F (Bus/Device/Function Number) values are the default values when
the server is fully configured with PCIe devices. The values may vary if the
server is not fully configured with PCIe devices or if a PCIe card with a PCI
bridge is configured.
● Root Port (B/D/F) indicates the B/D/F of an internal PCIe root port of the
processor.
● Device (B/D/F) indicates the B/D/F (displayed on the OS) of an onboard or
extended PCIe device.
● The PCIe x16 slots are backward compatible with PCIe x8, PCIe x4, and PCIe
x1 cards. The PCIe cards are not forward compatible. That is, the PCIe slot
width cannot be smaller than the PCIe card link width.
● Full-height full-length PCIe slots are backward compatible with full-height half-
length and half-height half-length PCIe cards. Full-height half-length PCIe slots
are backward compatible with half-height half-length PCIe cards.
● All slots support PCIe cards of up to 75 W. The power of a PCIe card varies
depending on its model.
● The SP520, SP521, and SP522 do not support driveless server configuration.
PXE boot is recommended for driveless servers.
2.8 PSUs
● The server supports one or two PSUs.
● The server supports AC or DC PSUs.
● The PSUs are hot-swappable.
● The server supports two PSUs in 1+1 redundancy.
● The same model of PSUs must be used in a server.
● The PSUs are protected against short circuit. Double-pole fuse is provided for
the PSUs with dual input live wires.
● If the DC power supply is used, purchase the DC power supply that meets the
requirements of the safety standards or the DC power supply that has passed
the CCC certification.
● Contact your local sales representative or use the Compatibility List to
determine the components to be used.
NO TE
● When one or two 900 W AC Titanium PSUs are configured and the input voltage ranges
from 100 V AC to 127 V AC, the output power decreases to 550 W.
● When one or two 1500 W AC Platinum PSUs are configured, When the input voltage
ranges from 100 V AC to 127 V AC, the output power decreases to 1000 W.
2.9 Fans
● The server supports four fan modules.
● The fan modules are hot-swappable.
● The server tolerates failure of a single fan.
● The fan speed can be adjusted.
● The same model of fan modules must be used in a server.
2.10 Boards
2.10.1 Mainboard
NO TE
● BOM code for mainboards of enhanced management chip (VB): 0302021706, 0302Y076.
● BOM code for mainboards of normal management chip: 03024AFQ, 03026NEA, 06410432,
03024CXS, 03029JRP, 06410436, 06410592.
Front-Drive Backplanes
● 8 x 2.5" drive pass-through backplane
● Backplane for the 8 x 3.5" drive pass-through configuration and 12 x 3.5" drive
pass-through configuration
Figure 2-72 Backplane for the 8 x 3.5" drive pass-through configuration and 12 x
3.5" drive pass-through configuration (BOM: 03024JMV and 03029TDH)
Built-in-Drive Backplane
● 4 x 3.5" built-in-drive pass-through backplane
3 Power connector -
(INNER HDD PWR/J2)
Rear-Drive Backplanes
● 2 x 2.5" drive pass-through backplane
3 Product Specifications
Component Specifications
Component Specifications
Component Specifications
Component Specifications
Component Specifications
Component Specifications
Category Specifications
NO TE
SSDs and HDDs (including NL-SAS, SAS, and SATA) cannot be preserved for a long time in
the power-off state. Data may be lost or faults may occur if the preservation duration exceeds
the specified maximum duration. When drives are preserved under the storage temperature
and humidity specified in the preceding table, the following preservation time is recommended:
● Maximum preservation duration of SSDs:
● 12 months in power-off state without data stored
● 3 months in power-off state with data stored
● Maximum preservation duration of HDDs:
● 6 months in unpacked/packed and powered-off state
● The maximum preservation duration is determined according to the preservation
specifications provided by drive vendors. For details, see the manuals provided by drive
vendors.
Item Description
NOTE
● See Figure 3-1 for methods in measuring physical
dimensions of the chassis.
● Methods measuring 3.5" and 2.5" drive chassis are the
same. The 3.5" drive chassis is used as an example.
Item Description
Use the Compatibility List to obtain information about the operating systems and
hardware supported.
NO TICE
● If incompatible components are used, the device may be abnormal. This fault is
beyond the scope of technical support and warranty.
● The performance of servers is closely related to application software, basic
middleware software, and hardware. The slight differences of the application
software, middleware basic software, and hardware may cause performance
inconsistency between the application layer and test software layer.
● If the customer has requirements on the performance of specific application
software, contact sales personnel to apply for POC tests in the pre-sales
phase to determine detailed software and hardware configurations.
● If the customer has requirements on hardware performance consistency,
specify the specific configuration requirements (for example, specific drive
models, RAID controller cards, or firmware versions) in the pre-sales phase.
5 Safety Instructions
5.1 Security
5.2 Maintenance and Warranty
5.1 Security
General Statement
● Comply with local laws and regulations when installing devices. These Safety
Instructions are only a supplement.
● The "DANGER", "WARNING", and "CAUTION" information in this document
does not represent all the safety instructions, but supplements to the safety
instructions.
● Observe all safety instructions provided on the device labels when installing
hardware. Follow them in conjunction with these Safety Instructions.
● Only qualified personnel are allowed to perform special tasks, such as
performing high-voltage operations and driving a forklift.
WARNING
Human Safety
● This equipment is not suitable for use in places where children may be present.
● Only certified or authorized personnel are allowed to install the device.
● Discontinue any dangerous operations and take protective measures. Report
anything that could cause personal injury or device damage to a project
supervisor.
● Do not move devices or install racks and power cables in hazardous weather
conditions.
● Do not carry the weight that is over the maximum load per person allowed by
local laws or regulations. Before moving or installing equipment, check the
maximum equipment weight and arrange required personnel.
● Wear clean protective gloves, ESD clothing, a protective hat, and protective
shoes, as shown in Figure 5-1.
● Before touching a device, wear ESD clothing and gloves (or wrist strap), and
remove any conductive objects (such as watches and jewelry). Figure 5-2
shows conductive objects that must be removed before you touch a device.
Equipment Safety
● Use the recommended power cables at all times.
● Use power cables only for dedicated servers. Do not use them for other devices.
● Before operating equipment, wear ESD clothes and gloves to prevent
electrostatic-sensitive devices from being damaged by ESD.
● When moving a device, hold the bottom of the device. Do not hold the handles of
the installed modules, such as the PSUs, fan modules, drives, and the
mainboard. Handle the equipment with care.
● Exercise caution when using tools that could cause personal injury.
● If the device is configured with active and standby PSUs, connect power cables
of active and standby PSUs to different power distribution units (PDUs) to
ensure reliable system operating.
● Ground the equipment before powering it on.
Transportation Precautions
Improper transportation may damage equipment. Contact the manufacturer for
precautions before attempting transportation.
● The logistics company engaged to transport the device must be reliable and
comply with international standards for transporting electronics. Ensure that the
Use Compatibility List to obtain information abut the components supported by a node
or server.
● Power off all devices before transportation.
CAUTION
To reduce the risk of personal injury, comply with local regulations with regard to the
maximum weight one person is permitted to carry.
Table 5-1 lists the maximum weight one person is permitted to carry as stipulated by
a number of organizations.
For more information about safety instructions, see Server Safety Information.
6 ESD
Item Description
Installation process
Precautions
● Properly ground the server before installation to avoid damage to electronic
components from electrostatic discharge. Improper grounding may cause
electrostatic discharge.
For details about how to prevent electrostatic discharge, see 6 ESD.
● Before installing multiple components, read the installation instructions for all the
components and identify similar actions to simplify the installation process.
Use the Compatibility List to obtain information about the components
supported.
CAUTION
Wait until overheating devices have cooled down before touching them to avoid
injury.
Procedure
Step 1 Check whether the packing case and seals are in good conditions.
NO TE
If the packing case is soaked or deformed, or the seals or pressure-sensitive adhesive tapes
are not intact, contact technical support to obtain the Cargo Problem Feedback Form.
CAUTION
Exercise caution with the box cutter to avoid injury to your hands or damage to
devices.
No. Description
----End
Procedure
Step 1 Check whether the packing case and seals are in good conditions.
NO TE
If the packing case is soaked or deformed, or the seals or pressure-sensitive adhesive tapes
are not intact, contact technical support to obtain the Cargo Problem Feedback Form.
CAUTION
Exercise caution with the box cutter to avoid injury to your hands or damage to
devices.
Step 3 Unpack the server and take out the devices layer by layer from top to bottom.
CAUTION
Pay attention to lifting. If the product does not have handles, use each layer of
cushion foam to lift together.
Step 4 Ensure that the components are complete and in good condition without defects such
as oxidation, chemical corrosion, missing components, or other damage incurred
during transport.
----End
Procedure
Step 1 Install the optional parts for the 2288H V5.
For details, see FusionServer 2288H V5 Server Maintenance and Service Guide.
----End
Procedure
Step 1 Install floating nuts.
1. Determine the installation positions of the floating nuts according to the cabinet
device installation plan.
NO TE
1. Position a guide rail horizontally in contact with the mounting bars in the cabinet.
2. Tighten the screws to secure the guide rail.
----End
Procedure
Step 1 Place the rail horizontally in the planned position. Stretch the rail on both sides of the
cabinet based on the cabinet length, keeping it in contact with the mounting bar in the
cabinet, and hook the rail. See (1) in Figure 7-7.
NO TE
The distance between the three holes in each mounting bar for the guide rail must be within 1
U.
Step 2 Plug the second square holes at the front and rear of the rail. See (2) in Figure 7-7.
Step 3 On the first lower square hole at the rear of the rail, insert an M6 screw. See (3) in
Figure 7-7.
NO TE
Although the adjustable L-shaped guide rail does not need screws for installation, you can
perform this operation to improve the shockproof level and fastening degree of the server.
----End
The ball bearing rail kit applies to cabinets with a distance of 610 mm to 914 mm
(24.02 in. to 35.98 in.) between the front and rear mounting bars.
Procedure
Step 1 Press the release latch at the front of the rail and stretch the hook horizontally as far
as it will go. See (1) and (2) in Figure 7-8.
Step 2 Insert the positioning pin at the rear of the rail into the hole on the rear column of the
cabinet. See (3) in Figure 7-8.
Step 3 Align the front end of the rail with the hole on the front column of the cabinet, push
the rail horizontally, and insert the rail into the hole on the column from the side. See
(4) in Figure 7-8.
Step 4 Push the hook horizontally until the release latch clicks into place. See (5) in Figure
7-8.
Step 5 On the third square hole at the rear of the rail, insert an M6 screw. See (6) in Figure
7-8.
NO TE
Although the ball bearing rail kit does not need screws for installation, we recommend you use
M6 screws at the rear end to make the server more shockproof and secure.
----End
The ball bearing rail kit applies to cabinets with a distance of 610 mm to 914 mm
(24.02 in. to 35.98 in.) between the front and rear mounting bars.
Procedure
Step 1 Push the release latch on the front of the rail and pull out the hook. See (1) and (2) in
Figure 7-9.
Step 2 Insert the positioning pin at the rear of the rail into the hole on the rear post of the
cabinet. See (3) in Figure 7-9.
Step 3 Keep the rail horizontal, and push the front end of the rail until it is inserted into the
hole on the front post of the cabinet. See (4) in Figure 7-9.
----End
Procedure
Step 1 Install the server.
NO TICE
At least two people are required to move the device. Otherwise, personal injury or
device damage may occur.
1. At least two people are required to lift the server horizontally from both sides and
place it on the guide rails, see Figure 7-10, then push it into the cabinet, See (1)
in Figure 7-11.
NO TE
If you touch the drive unlock button by mistake, do not remove the drive and immediately
close the drive ejector lever to install the drive in place.
2. Align the mounting ears on both sides of the server with the mounting bars and
tighten the captive screws on the mounting ears. See (2) in Figure 7-11.
Step 2 Connect external cables as required, such as network cables, VGA cables, and USB
devices.
----End
Before installing the server, ensure that the ball bearing rail kit is properly installed.
For details, see 7.2.4.3 Installing the Ball Bearing Rail Kit.
The 2288H V5 servers are stackable onto the ball bearing rail kit.
Procedure
Step 1 Install the server.
NO TICE
At least two people are required to move the device. Otherwise, personal injury or
device damage may occur.
2. Lift the server (at least two people are required), see Figure 7-13, align the
positioning pins on the server with the holes on the inner guide rails, and push
the server in the arrow direction until the locking pins engage, See (1) and (2) in
Figure 7-14.
3. Press the release buttons on both sides and push the server into the rails. See
(1) and (2) in Figure 7-15.
NO TE
If you touch the drive unlock button by mistake, do not remove the drive and immediately
close the drive ejector lever to install the drive in place.
4. Tighten the captive screws on the mounting ears to secure the server.
2. Insert the nail heads on the outer left rail into the holes on the outer support lever
of the CMA, and pull the CMA in the arrow direction. See (2) in Figure 7-17.
3. Insert the nail heads on the inner left rail into the holes on the inner support lever
of the CMA, and pull the CMA in the arrow direction. See (3) in Figure 7-17.
Step 3 Connect external cables as required, such as network cables, VGA cables, and USB
devices.
----End
Before installing the server, ensure that the ball bearing rail kit is properly installed.
For details, see 7.2.4.3 Installing the Ball Bearing Rail Kit.
The 2288H V5 servers are stackable onto the ball bearing rail kit.
Procedure
Step 1 Install the server.
NO TICE
At least two people are required to move the device. Otherwise, personal injury or
device damage may occur.
2. Lift the server (at least two people are required), align the two mounting screws
on the rear part of the server with the holes on the inner rails, and push the
server horizontally until the server cannot move. See Figure 7-19 and Figure
7-20.
3. After securing the two mounting screws on the rear part of the server, slowly
lower the front part of the server and secure the six mounting screws on the front
part of the server to ensure that the server is completely secured on the inner
rails. See Figure 7-21.
4. Unlock the release latches on both sides of the inner rails and push the server
until the server cannot move. See (1) and (2) in Figure 7-22.
NO TE
If you touch the drive unlock button by mistake, do not remove the drive and immediately
close the drive ejector lever to install the drive in place.
Figure 7-22 Pushing a server into the ball bearing rail kit
2. Insert the internal bracket on the left of the CMA into the left guide rail. See (2) in
Figure 7-24.
3. Insert the external bracket on the left of the CMA into the left guide rail. See (3)
in Figure 7-24.
Step 3 Connect external cables as required, such as network cables, VGA cables, and USB
devices.
Step 4 Connect the power cables to the PSUs.
For details, see 7.2.6.8 Connecting PSU Cables.
----End
Basic Guidelines
NO TICE
Do not block the air exhaust vents on the rear panel of the server when you lay out
cables. Otherwise, heat dissipation of the server may be affected.
● Lay out and bind cables of different types (such as power and signal cables)
separately. Cables of the same type must be in the same direction.
– Cables at a small distance can be laid out in crossover mode.
– When laying out cables in parallel, the distance between power cables and
signal cables must be longer than or equal to 30 mm (1.18 in.).
● If you cannot identify cables according to the cable labels, attach an engineering
label to each cable.
● Cables must be protected from burrs, heat sinks, and active accessories, which
may damage the insulation layers of the cables.
● Ensure that the length of cable ties for binding cables is appropriate. Do not
connect two or more cable ties together for binding cables. After binding cables
properly, trim the excess lengths of the cable ties and ensure that the cuts are
neat and smooth.
● Ensure that cables are properly laid out, supported, or fixed within the cable
troughs inside the cabinet to prevent loose connections and cable damage.
● Surplus cable lengths must be coiled and bound to a proper position inside the
cabinet.
● Cables must be laid out straightly and bound neatly. The bending radius of a
cable varies depending on the position where the cable is bent.
– If you need to bend a cable in its middle, the bending radius must be at least
twice the diameter of the cable.
– If you need to bend a cable at the output terminal of a connector, the
bending radius must be at least five times the diameter of the cable, and the
cable must be bound before it is bent.
● Do not use cable ties at a place where the cables are bent. Otherwise, the
cables may break.
Common Methods
The methods of laying out cables inside a cabinet are described as follows:
● Choose overhead or underfloor cabling for power cables based on equipment
room conditions (such as the AC power distribution frame, surge protector, and
terminal blocks).
● Choose overhead or underfloor cabling for service data cables (for example,
signal cables) based on equipment room conditions.
● Place the connectors of all service data cables at the bottom of the cabinet so
that the connectors are difficult to reach.
Procedure
Step 1 Connect the USB connector of the USB-to-PS/2 cable to a USB port on the front or
rear panel of the server.
Step 2 Connect the PS/2 connectors 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 connector of the VGA cable to the VGA port on the monitor and
tighten the two screws.
----End
Procedure
Step 1 Determine the model of the new network cable.
● Shielded cables are recommended.
NO TE
According to the result of the EMC test, if a non-shielded cable is used, the system
cannot respond to the ESD. As a result, the system is suspended and restarts.
● The new and old cables must be of the same model or be compatible.
Remove the network cable from the network interface card (NIC) or board in the
cabinet.
Step 6 Connect the new network cable to the peer network port.
● Connect the other cable connector to the peer device based on the network
plan.
● Connect the new network cable to the same port as the removed one.
● Connect the network cable to the network port securely.
Step 7 Check whether the new network cable is functioning properly.
Power on the device. Check whether the communication with the peer device is
normal by running the ping command.
● If yes, bind the new network cable with other cables.
Bind the new network cable in the same way as the existing network cables. You
can also remove all existing cable ties and bind all network cables again if
necessary.
● If no, check whether the network cable is damaged or whether the connector of
the network cable is not securely inserted.
----End
Procedure
Step 1 Determine the model of the new cable.
You can use an optical cable or an SFP+ cable to connect to the optical port.
Step 2 Number the new cable.
● The number of the new cable must be the same as that of the old one.
● Use the same type of labels for the optical cable.
– Record the name and number of the local device to be connected on one
side of the label, and those of the peer device on the other side.
– Attach the label 2 cm (0.79 in.) away from the end of the optical cable.
Step 3 Lay out the new cable.
● Lay out the new cable in the same way as the old one.
For example, if the old cable is laid out in underfloor cabling mode, so is the new
cable.
● Lay out optical cables or SFP+ cables in the cabinet based on installation
requirements.
You are advised to arrange cables in the same way as existing cables. Ensure
that cables are routed neatly and undamaged.
● Separate optical cables or SFP+ cables from power cables and signal cables
when laying out the cables.
● The minimum bend radius of an optical cable or SFP+ cables is 4 cm (1.57 in.).
● Ensure that optical cables or SFP+ cables are laid out for easy maintenance and
capacity expansion.
● Optical cables must be bound using cable ties. Ensure that:
– Optical cables are bound closely, neatly, and straight.
– Cable ties are in even distance and fastened properly.
Step 4 Connect the cable to an optical port.
● When you use an optical cable:
a. Remove the optical cable to be replaced.
b. Connect the new optical cable.
NO TE
▪ Connect the new optical cable to the same port as the removed one.
i. Insert the optical module into the optical port. See (1) in Figure 7-27.
ii. Close the latch on the optical module to secure it. See (2) in Figure
7-27.
iii. Insert the optical cable into the optical module. See (3) in Figure 7-27.
NO TICE
Power on the device. Check whether the communication with the peer device is
normal by running the ping command.
● If yes, go to Step 7.
● If no, go to Step 6.
Step 6 If the peer device cannot be pinged, check whether the cable is intact or the
connector is securely connected.
● If yes, contact technical support.
● If no, replace the cable or insert the connector securely, and go to Step 5.
Bind the new optical cable in the same way as the existing optical cables. You can
also remove all existing cable ties and bind all optical cables again if necessary.
----End
Procedure
Step 1 Determine the model of the new cable.
Figure 7-30 Removing a cable (for an IB NIC with two 56 Gbit/s ports as an
example)
Figure 7-31 Connecting a cable (for an IB NIC with two 56 Gbit/s ports as an
example)
----End
Procedure
Step 1 Connect the USB device to a USB port of the server.
----End
Procedure
Step 1 Connect the serial cable.
----End
NO TICE
Procedure
Step 1 Take the component out of its ESD bag.
Step 2 Connect one end of the power cable to the power socket on the PSU of the server.
After the power module cables are connected to the server, adjust the velcro on the power
module to the right corner of the handle, and then wrap the velcro tape around the lower part
of the power cable plug, as shown in Figure 7-35.
Step 4 Connect the other end of the power cable to the AC PDU in the cabinet.
The AC PDU is fastened horizontally in the rear of the cabinet. Connect the power
cable to the socket on the PDU according to the plan.
Step 5 Bundle the power cable to the cable guide using cable ties.
----End
NO TICE
Procedure
Step 1 Take the component out of its ESD bag.
Step 2 Connect the cables to the PSU.
● 1200 W (power cable P/N code: 02232SVN)
a. Insert the power cable to the wiring terminals on the PSU until the cable
click into position, as shown in Figure 7-36.
i. Connect the cord end terminal of the negative power cable (blue) to the
NEG(–) wiring terminal on the PSU.
ii. Connect the cord end terminal of the positive power cable (black) to the
RTN(+) wiring terminal on the PSU.
b. Insert the other end of the power cable to the wiring terminals on the PDU,
and tighten the screws. See (1) and (2) in Figure 7-37.
i. Connect the cord end terminal of the negative power cable (blue) to the
PDU(–) wiring terminal.
ii. Connect the cord end terminal of the positive power cable (black) to the
PDU(+) wiring terminal.
● 1500 W (power cable P/N codes: 04151188/04151188-002 for the HVDC cable
and 04152747 for the AC cable)
NO TE
The 1500 W HVDC PSU supports AC and DC input. Cables 04152747 and
04151188/04151188-002 can be used for AC input. Cable 04151188/04151188-002 can
only be used for DC input.
– 04151188/04151188-002
i. Connect one end of the power cable to the power socket on the PSU of
the server.
iii. Insert the other end of the power cable to the wiring terminals on the
PDU, and tighten the screws. See (1) and (2) in Figure 7-40.
1) Connect the cord end terminal of the live wire (brown) to the
PDU(+) wiring terminal.
2) Connect the cord end terminal of the neutral wire (blue) to the
PDU(–) wiring terminal.
3) Connect the cord end terminal of the ground cable (yellow and
green) to the ground terminal of the PDU.
– 04152747
i. Connect one end of the power cable to the power socket on the PSU of
the server.
iii. Connect the other end of the power cable to the PDU in the cabinet.
Step 3 Bundle the power cables to the cable guide using cable ties.
----End
CAUTION
Before checking cable connections, ensure that the power is cut off. Otherwise, any
incorrect connection or loose connection may cause human injury or device damage.
Item Description
Power cable Power cables are correctly connected to the rear of the
chassis.
Ground cable The server does not provide a separate ground port.
● In AC or HVDC environment, the power cables of AC
PSUs are grounded. Ensure that the power cables are
in good contact.
● In DC environment, the ground terminals of DC PSUs
are grounded. Ensure that the ground cables are in
good contact.
NO TICE
● Before powering on a server, ensure that the server is powered off, all cables are
connected correctly, and the power supply voltage meets service requirements.
● During the power-on process, do not remove and insert drives or disconnect and
connect network cables or Console port cables.
● If the power supply to a server is disconnected, wait for at least one minute before
powering it on again.
● If PSUs are properly installed but are not connected to an external power supply,
the server is powered off.
Connect the external power supply to the PSUs. Then the server will be powered
on with the PSUs.
NO TE
The default value of System State Upon Power Supply is Power On, which indicates
that the server automatically powers on after power is supplied to PSUs. To change the
value of System Power, log in to the iBMC WebUI and choose Power > Power Control.
● If the PSUs are powered on and the server is in standby state (the power
indicator is steady yellow), you can use any of the following methods to power
on the server:
– Press the power button on the front panel.
For details, see 2.1.2 Indicators and Buttons.
– Use the iBMC WebUI.
i. Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
ii. Choose Power > Power Control.
The Power Control page is displayed.
iii. Click Power On.
A confirmation message is displayed.
iv. Click OK.
The server starts to be powered on.
– Use the iBMC CLI.
i. Log in to the iBMC CLI.
For details, see 9.5 Logging In to the CLI.
ii. Run the following command:
ipmcset -d powerstate -v 1
iii. Enter y or Y and press Enter.
Power on the server.
– Use the Remote Virtual Console.
i. Log in to the Remote Virtual Console.
For details, see 9.4 Logging In to the Desktop of a Server.
NO TICE
● Before powering on a server, ensure that the server is powered off, all cables are
connected correctly, and the power supply voltage meets service requirements.
● During the power-on process, do not remove and insert drives or disconnect and
connect network cables or Console port cables.
● If the power supply to a server is disconnected, wait for at least one minute before
powering it on again.
● If PSUs are properly installed but are not connected to an external power supply,
the server is powered off.
Connect the external power supply to the PSUs. Then the server will be powered
on with the PSUs.
NO TE
The default value of System State Upon Power Supply is Power On, which indicates
that the server automatically powers on after power is supplied to PSUs. To change the
value of System Power, log in to the iBMC WebUI and choose System > Power >
Power Control.
● If the PSUs are powered on and the server is in standby state (the power
indicator is steady yellow), you can use any of the following methods to power
on the server:
– Press the power button on the front panel.
For details, see 2.1.2 Indicators and Buttons.
– Use the iBMC WebUI.
i. Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
ii. Choose System > Power > Power Control.
The Power Control page is displayed.
iii. Click Power On.
A confirmation message is displayed.
iv. Click Yes.
The server starts to be powered on.
– Use the iBMC CLI.
i. Log in to the iBMC CLI.
For details, see 9.5 Logging In to the CLI.
ii. Run the following command:
ipmcset -d powerstate -v 1
iii. Enter y or Y and press Enter.
Power on the server.
– Use the Remote Virtual Console.
i. Log in to the Remote Virtual Console.
For details, see 9.4 Logging In to the Desktop of a Server.
NO TICE
● Before powering on a server, ensure that the server is powered off, all cables are
connected correctly, and the power supply voltage meets service requirements.
● During the power-on process, do not remove and insert drives or disconnect and
connect network cables or Console port cables.
● If the power supply to a server is disconnected, wait for at least one minute before
powering it on again.
● If PSUs are properly installed but are not connected to an external power supply,
the server is powered off.
Connect the external power supply to the PSUs. Then the server will be powered
on with the PSUs.
NO TE
The default value of System State Upon Power Supply is Power On, which indicates
that the server automatically powers on after power is supplied to PSUs. To change the
value of System Power, log in to the iBMC WebUI and choose System > Power >
Power Control.
● If the PSUs are powered on and the server is in standby state (the power
indicator is steady yellow), you can use any of the following methods to power
on the server:
– Press the power button on the front panel.
For details, see 2.1.2 Indicators and Buttons.
– Use the iBMC WebUI.
i. Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
ii. Choose System > Power > Power Control.
The Power Control page is displayed.
iii. Click Power On.
A confirmation message is displayed.
iv. Click Yes.
The server starts to be powered on.
– Use the iBMC CLI.
i. Log in to the iBMC CLI.
For details, see 9.5 Logging In to the CLI.
ii. Run the following command:
ipmcset -d powerstate -v 1
iii. Enter y or Y and press Enter.
Power on the server.
● Powering off a server will interrupt all services and programs running on it. Therefore,
before powering off a server, ensure that all services and programs have been stopped or
migrated to other servers.
● The "power-off" mentioned here is an operation performed to change the server to the
standby state (the power indicator is steady yellow).
● After a server is powered off forcibly, wait for more than 10 seconds for the server to power
off completely. Do not power on the server again before it is completely powered off.
● Forced power-off may damage user programs or unsaved data. Exercise caution when
performing this operation.
If the server OS is running, shut down the OS according to the onscreen instructions.
For details, see 2.1.2 Indicators and Buttons.
● When the server is in power-on state, holding down the power button on the
server front panel for six seconds can power off the server forcibly.
For details, see 2.1.2 Indicators and Buttons.
● Use the iBMC WebUI.
a. Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
b. Choose Power > Power Control.
The Power Control page is displayed.
c. Click Power Off or Forced Power Off.
A confirmation message is displayed.
d. Click OK.
The server starts to be powered off.
● Powering off a server will interrupt all services and programs running on it. Therefore,
before powering off a server, ensure that all services and programs have been stopped or
migrated to other servers.
● The "power-off" mentioned here is an operation performed to change the server to the
standby state (the power indicator is steady yellow).
● After a server is powered off forcibly, wait for more than 10 seconds for the server to power
off completely. Do not power on the server again before it is completely powered off.
● Forced power-off may damage user programs or unsaved data. Exercise caution when
performing this operation.
● Connect a keyboard, video, and mouse (KVM) to the server and shut down the
operating system of the server using the KVM.
● When the server is in power-on state, pressing the power button on the server
front panel can power off the server gracefully.
NO TE
If the server OS is running, shut down the OS according to the onscreen instructions.
For details, see 2.1.2 Indicators and Buttons.
● When the server is in power-on state, holding down the power button on the
server front panel for six seconds can power off the server forcibly.
For details, see 2.1.2 Indicators and Buttons.
● Use the iBMC WebUI.
● Powering off a server will interrupt all services and programs running on it. Therefore,
before powering off a server, ensure that all services and programs have been stopped or
migrated to other servers.
● The "power-off" mentioned here is an operation performed to change the server to the
standby state (the power indicator is steady yellow).
● After a server is powered off forcibly, wait for more than 10 seconds for the server to power
off completely. Do not power on the server again before it is completely powered off.
● Forced power-off may damage user programs or unsaved data. Exercise caution when
performing this operation.
NO TE
If the server OS is running, shut down the OS according to the onscreen instructions.
For details, see 2.1.2 Indicators and Buttons.
● When the server is in power-on state, holding down the power button on the
server front panel for six seconds can power off the server forcibly.
For details, see 2.1.2 Indicators and Buttons.
● Use the iBMC WebUI.
a. Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
b. Choose System > Power > Power Control.
The Power Control page is displayed.
c. Click Power Off or Forced Power Off.
A confirmation message is displayed.
d. Click Yes.
The server starts to be powered off.
● Use the iBMC CLI.
a. Log in to the iBMC CLI.
For details, see 9.5 Logging In to the CLI.
b. Run the following command:
Change the 1. Change the initial password ● Change the password on the
initial of the iBMC default user. iBMC WebUI or iBMC CLI.
password. ● Use the iBMC WebUI. The method for changing the
password varies depending
● Use the iBMC CLI. on iBMC versions. For
● Use the BIOS. details, see the
2. Change the initial password FusionServer Rack Server
of the iBMC U-Boot. iBMC User Guide of the
For details, see the 9.9 corresponding version.
Changing the Initial ● Use the BIOS. For details,
Password of the iBMC U- see the Server Purley
Boot. Platform BIOS Parameter
NOTE Reference.
If the model does not support
the iBMC U-Boot, you do not
need to change the initial
password of the iBMC U-Boot.
Check the 1. Check the indicators on the ● Check the status of indicators
server. panel to ensure that the on the panel. For details, see
server is running properly. section "Indicators and
2. Check the iBMC or BIOS Buttons".
versions of the server to ● The methods for querying the
ensure that the version is the server version, health status,
same as the target version. and alarm information vary
The query methods are as depending on the iBMC
follows: version. For details, see the
● Use the iBMC WebUI. FusionServer Rack Server
iBMC User Guide of the
● Use the iBMC CLI. corresponding version.
3. Query the health status and ● Upgrade the firmware to the
alarm information of the target version. For details,
server to ensure that the see the FusionServer Rack
server is running properly. Server (V6 or earlier)
The query methods are as Upgrade Guide.
follows:
● Handle the alarms. For
● Use the iBMC WebUI. details, see the
● Use the iBMC CLI. FusionServer Rack Server
iBMC Alarm Handling.
Configure To configure the iBMC network ● The iBMC WebUI and iBMC
the iBMC information, perform the CLI are configured. The
network following steps: configuration mode varies
information. ● Use the iBMC WebUI. depending on the iBMC
version. For details, see the
● Use the iBMC CLI. FusionServer Rack Server
● Use the BIOS. iBMC User Guide of the
corresponding version.
● Use the BIOS. For details,
see the Server Purley
Platform BIOS Parameter
Reference.
Configure Configure the RAID group based Different RAID controller cards
the RAID. on service requirements. have different configuration
NOTE methods. For details, see the V5
When the management mode of Server RAID Controller Card
common drives is PCH, RAID User Guide.
groups cannot be configured.
NOTE
For details about the compatible
RAID controller cards, see the
Compatibility List.
Configure Configure the BIOS based on For details, see the Server
the BIOS. the actual service scenario. Purley Platform BIOS
Parameter Reference.
NOTE
The common settings for
configuring the BIOS are as follows:
● Set the system boot sequence.
● Set PXE of the NIC.
● Set the BIOS password.
● Switch the system language.
Install the Install the OS for the server. For details about how to install
OS. different OSs, see the Server
OS Installation Guide.
NOTE
For details about the compatible
OSs, see the Compatibility List.
8 Troubleshooting Guide
For details about how to troubleshoot servers, see the Server Troubleshooting. It
covers the following content:
● Troubleshooting process
Use appropriate methods to find the cause of a fault and rectify the fault.
Analyze possible causes for a fault and narrow down the scope to reduce
troubleshooting complexity, identify the root cause, and rectify the fault.
● Fault information collection
Collect logs for fault diagnosis when a fault occurs on a server.
● Fault diagnosis
Fault diagnosis rules and tools help technical support engineers and
maintenance engineers to analyze and rectify faults according to alarms and
hardware fault symptoms.
● Software and firmware upgrade
Obtain and install the software and firmware upgrade packages based on the
server model.
● Preventive maintenance
Preventive maintenance promptly detects, diagnoses, and rectifies server faults.
9 Common Operations
You can query the IP address of the iBMC management network port on:
● BIOS
● iBMC WebUI
For details, see the FusionServer Rack Server iBMC User Guide.
● iBMC CLI
Run the ipmcget -d ipinfo command.
For details, see the FusionServer Rack Server iBMC User Guide.
Procedure
Step 1 Access the BIOS.
Step 2 Choose Advanced > IPMI iBMC Configuration, and press Enter.
The IPMI iBMC Configuration screen is displayed.
Step 3 Select iBMC Configuration and press Enter.
The iBMC Configuration screen is displayed.
Step 4 Check the IP address of the iBMC management network port.
----End
NO TE
● BOM codes for mainboard of enhanced management chip (VB): 0302021706, 0302Y076.
● BOM codes for mainboard of normal management chip: 03024AFQ, 03026NEA, 06410432,
03024CXS, 03029JRP, 06410436, 06410592.
----End
Querying the Mainboard iBMC Management Chip Type on the iBMC WebUI
Step 1 Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
Step 2 Query the mainboard iBMC management chip type.
● Check the iBMC firmware version on the home page. See (1) in Figure 9-1.
– If using an enhanced (VB) management chip, the iBMC firmware version
format is X.XX.XX.XX, e.g. "3.03.10.17".
– If using a normal management chip, the iBMC firmware version format is
X.XX, e.g. "2.50".
● View the model name on the home page. See (2) in Figure 9-1.
– If using an enhanced (VB) management chip, the iBMC firmware version
format is X.XX.XX.XX, e.g. "3.03.10.17".
– If using a normal management chip, the iBMC firmware version format is
X.XX, e.g. "2.50".
----End
Checking the Mainboard iBMC Management Chip Type via the BIOS Boot
Page
Step 1 Log in to the server real-time desktop
For details, see 9.4 Logging In to the Desktop of a Server.
NO TICE
● A forced restart or power cycle may cause data loss or program damage.
● Before performing a forced restart or power cycle, ensure that no service
interruption risk exists.
----End
Operation Scenario
This section describes how to log in to the iBMC WebUI. The following uses Internet
Explorer 11.0 as an example.
● A maximum of four users can log in to the WebUI at the same time.
● By default, the system timeout period is 5 minutes. If no operation is performed
on the WebUI within 5 minutes, the user will be automatically logged out of the
WebUI.
● The system locks your account if you enter incorrect passwords for consecutive
five times. You are automatically unlocked 5 minutes later, or an administrator
can unlock your account on the CLI.
● For security purposes, change the initial password upon the first login and
change the password periodically.
● If resources fail to be obtained due to unstable network connection, the iBMC
WebUI may be displayed abnormally. If this occurs, refresh the browser and log
in to the iBMC WebUI again.
Procedure
Step 1 Ensure that the client used to access the iBMC meets the operating environment
requirements.
If you want to use the Java Integrated Remote Virtual Console, ensure that the Java
Runtime Environment (JRE) meets requirements.
Red Hat 6.0 (64-bit) Mozilla Firefox 39.0 to JRE 1.7 U45
54.0 JRE 1.8 U45
JRE 1.8 U144
Step 2 Use a network cable to connect the Ethernet port on the local PC to the iBMC
management network port.
Step 3 Set an IP address and subnet mask or route information for the local PC to enable
the PC to communicate with the iBMC.
Step 4 Open the browser on the local PC, enter https://iBMC management network port IP
address in the address box, and press Enter.
The iBMC login page is displayed.
NO TE
● If the language of the browser you use to log in to the iBMC WebUI is not Chinese, English,
or Japanese, upgrade the iBMC to V260 or later. Otherwise, the login page may fail to
display.
● If the message "There is a problem with this website's security certificate" is displayed, click
Continue to this website (not recommended).
● If a security alert is displayed, you can ignore this message or perform any of the following
to shield this alert:
– Import a trusted certificate and a root certificate to the iBMC.
For details, see "Importing the Trust Certificate and Root Certificate" in the iBMC user
guide of the server you use.
– If no trust certificate is available and network security can be ensured, add the iBMC
to the Exception Site List on Java Control Panel or reduce the Java security level.
This operation poses security risks. Exercise caution when performing this operation.
NO TE
▪ The system provides a default user of the administrator group. The default user
is Administrator, and the default password is Admin@9000.
▪ When Domain is Local iBMC, the maximum length of the user name is 20
characters.
▪ When Domain is not Local iBMC, the maximum length of the user name is 255
characters.
c. Select Local iBMC or Automatic matching from the Domain drop-down
list.
d. Click Log In.
After the login is successful, the Overview page is displayed, showing the
user name in the upper right corner.
NO TE
▪ If you fail to log in to the iBMC WebUI through an Internet Explorer, choose
Tools > Internet Options > Advanced in the menu bar and click Reset to
restore default settings of Internet Explorer. Then attempt to log in again.
● Log in to the iBMC as an LDAP user.
NO TICE
Before login, ensure that the following settings meet the requirements:
– A domain controller exists on the network, and a user domain and LDAP
users have been created on the domain controller.
For details about how to create a domain controller, a user domain, and
LDAP users who belong to the user domain, see related documents about the
domain controller. The iBMC provides only the access function for LDAP
users.
– On the Configuration > LDAP page of the iBMC WebUI, the LDAP function
is enabled, and the user domain and the LDAP user who belong to the user
domain are set.
a. Select a language.
b. Enter the LDAP user name and password.
NO TE
▪ LDAP user name (In this case, Domain can be Automatic matching or a
specified domain.)
▪ LDAP user name@Domain name (In this case, Domain must be Automatic
matching.)
▪ In versions earlier than iBMC V294, the maximum password length for an LDAP
user is 20 characters. In iBMC V294 and later versions, the maximum password
length for an LDAP user is 255 characters.
c. Select the LDAP user domain from the Domain drop-down list.
NO TE
▪ Automatic matching: If this option is selected, the iBMC searches for the user
from the local user list first. If no match is found, the iBMC searches from the
domain servers in the sequence displayed in the Domain drop-down list.
d. Click Log In.
After the login is successful, the Overview page is displayed, showing the
user name in the upper right corner.
----End
Operation Scenario
This section describes how to log in to the iBMC WebUI. The following uses Internet
Explorer 11.0 as an example.
● A maximum of four users can log in to the WebUI at the same time.
NO TE
● Before using Internet Explorer to log in to the iBMC WebUI, enable the compatibility view
and select Use TLS 1.2.
● Enable the compatibility view as follows:
Procedure
Step 1 Ensure that the client used to access the iBMC meets the operating environment
requirements.
If you want to use the Java Integrated Remote Virtual Console, ensure that the Java
Runtime Environment (JRE) meets requirements.
Step 2 Use a network cable to connect the Ethernet port on the local PC to the iBMC
management network port.
Step 3 Open the browser on the local PC, enter https://iBMC management network port IP
address in the address box, and press Enter.
The iBMC login page is displayed.
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 trusted certificate and a root certificate to the iBMC.
For details, see "Importing the Trust Certificate and Root Certificate" in the iBMC user
guide of the server you use.
– If no trust certificate is available and network security can be ensured, add the iBMC
to the Exception Site List on Java Control Panel or reduce the Java security level.
This operation poses security risks. Exercise caution when performing this operation.
NO TE
▪ The system provides a default user of the administrator group. The default user
is Administrator, and the default password is Admin@9000.
▪ When Domain is Local iBMC, the maximum length of the user name is 20
characters.
▪ When Domain is not Local iBMC, the maximum length of the user name is 255
characters.
c. Select Local iBMC or Automatic matching from the Domain drop-down
list.
d. Click Log In.
After the login is successful, the Home page is displayed.
NO TE
▪ If you fail to log in to the iBMC WebUI through an Internet Explorer, choose
Tools > Internet Options > Advanced in the menu bar and click Reset to
restore default settings of Internet Explorer. Then attempt to log in again.
● Log in to the iBMC as an LDAP user.
NO TICE
Before login, ensure that the following settings meet the requirements:
– A domain controller exists on the network, and a user domain and LDAP
users have been created on the domain controller.
For details about how to create a domain controller, a user domain, and
LDAP users who belong to the user domain, see related documents about the
domain controller. The iBMC provides only the access function for LDAP
users.
– On the User & Security > LDAP page of the iBMC WebUI, the LDAP
function is enabled, and the user domain and the LDAP user who belong to
the user domain are set.
a. Select a language.
b. Enter the LDAP user name and password.
NO TE
▪ LDAP user name (In this case, Domain can be Automatic matching or a
specified domain.)
▪ LDAP user name@Domain name (In this case, Domain can be Automatic
matching or a specified domain.)
c. Select the LDAP user domain from the Domain drop-down list.
NO TE
▪ Automatic matching: If this option is selected, the iBMC searches for the user
from the local user list first. If no match is found, the iBMC searches from the
domain servers in the sequence displayed in the Domain drop-down list.
d. Click Log In.
After the login is successful, the Home page is displayed.
● To log in to the WebUI as a Kerberos user, perform the following steps:
NO TE
Kerberos environment:
– The client supports the Windows 10 64-bit operating system and the Internet Explorer
11 browser.
– The Kerberos server supports the Windows Server 2012 R2 64-bit and Windows
Server 2016 64-bit OSs.
Kerberos users can log in to the WebUI in either of the following modes:
– Logging in as a Kerberos domain user
– Logging in over SSO
Before login, ensure that the following settings meet the requirements:
– Kerberos is enabled and Kerberos function and user group are configured on the
User & Security > Kerberos page of the iBMC WebUI.
– The Kerberos user group and user have been created on the Kerberos server, and
the user has been added to the Kerberos user group. This user is a user of the client
OS.
Logging In as a Kerberos Domain User
a. (Optional) On the iBMC login page, switch to the target language.
b. Enter the Kerberos user name and password.
NO TE
▪ Kerberos user name (In this case, Domain can be Automatic matching or a
specified domain.)
▪ Kerberos user name@Domain name (In this case, Domain can be Automatic
matching or a specified domain, and all letters used in the domain name must
be in upper case.)
▪ When you log in to the iBMC WebUI as a Kerberos domain user, the password
can contain a maximum of 255 characters.
c. In the Domain drop-down list, select a Kerberos user domain (for example,
ADMIN.COM(KRB)) or Automatic matching.
d. Click Log In.
After the login is successful, the Home page is displayed.
Logging In over SSO
a. Use the Kerberos user name and password configured on the Kerberos
server to log in to the client OS.
b. Enter the FQDN of the iBMC in the address box of the browser, for example,
https://host name.domain name.
The iBMC login page is displayed.
c. Click SSO.
After the login is successful, the Home page is displayed.
----End
Operation Scenario
This section describes how to log in to the iBMC WebUI. The following uses Internet
Explorer 11.0 as an example.
● A maximum of four users can log in to the WebUI at the same time.
● By default, the system timeout period is 5 minutes. If no operation is performed
on the WebUI within 5 minutes, the user will be automatically logged out of the
WebUI.
● The system locks your account if you enter incorrect passwords for consecutive
five times. You are automatically unlocked 5 minutes later, or an administrator
can unlock your account on the CLI.
● For security purposes, change the initial password upon the first login and
change the password periodically.
● If resources fail to be obtained due to unstable network connection, the iBMC
WebUI may be displayed abnormally. If this occurs, refresh the browser and log
in to the iBMC WebUI again.
NO TE
● Before using Internet Explorer to log in to the iBMC WebUI, enable the compatibility view
and select Use TLS 1.2.
● Enable the compatibility view as follows:
Procedure
Step 1 Confirm that the client using iBMC meets the operating environment requirements.
If you need to use the Java integrated remote virtual console function, you need to
have an available version of the Java runtime environment as well.
Microsoft Edge
Step 2 Use a network cable to connect the Ethernet port on the local PC to the iBMC
management network port.
Step 3 Open the browser on the local PC, enter https://iBMC management network port IP
address in the address box, and press Enter.
The iBMC login page is displayed.
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 trusted certificate and a root certificate to the iBMC.
For details, see "Importing the Trust Certificate and Root Certificate" in the iBMC user
guide of the server you use.
– If no trust certificate is available and network security can be ensured, add the iBMC
to the Exception Site List on Java Control Panel or reduce the Java security level.
This operation poses security risks. Exercise caution when performing this operation.
NO TE
▪ The system provides a default user of the administrator group. The default user
is Administrator, and the default password is Admin@9000.
▪ When Domain is Local iBMC, the maximum length of the user name is 20
characters.
▪ When Domain is not Local iBMC, the maximum length of the user name is 255
characters.
▪ If you fail to log in to the iBMC WebUI through an Internet Explorer, choose
Tools > Internet Options > Advanced in the menu bar and click Reset to
restore default settings of Internet Explorer. Then attempt to log in again.
● Log in to the iBMC as an LDAP user.
NO TICE
Before login, ensure that the following settings meet the requirements:
– A domain controller exists on the network, and a user domain and LDAP
users have been created on the domain controller.
For details about how to create a domain controller, a user domain, and
LDAP users who belong to the user domain, see related documents about the
domain controller. The iBMC provides only the access function for LDAP
users.
– On the User & Security > LDAP page of the iBMC WebUI, the LDAP
function is enabled, and the user domain and the LDAP user who belong to
the user domain are set.
a. Select a language.
b. Enter the LDAP user name and password.
NO TE
▪ LDAP user name (In this case, Domain can be Automatic matching or a
specified domain.)
▪ LDAP user name@Domain name (In this case, Domain can be Automatic
matching or a specified domain.)
c. Select the LDAP user domain from the Domain drop-down list.
NO TE
▪ Automatic matching: If this option is selected, the iBMC searches for the user
from the local user list first. If no match is found, the iBMC searches from the
domain servers in the sequence displayed in the Domain drop-down list.
Kerberos environment:
– The client supports the Windows 10 64-bit operating system and the Internet Explorer
11 browser.
– The Kerberos server supports the Windows Server 2012 R2 64-bit and Windows
Server 2016 64-bit OSs.
Kerberos users can log in to the WebUI in either of the following modes:
– Logging in as a Kerberos domain user
– Logging in over SSO
Before login, ensure that the following settings meet the requirements:
– Kerberos is enabled and Kerberos function and user group are configured on the
User & Security > Kerberos page of the iBMC WebUI.
– The Kerberos user group and user have been created on the Kerberos server, and
the user has been added to the Kerberos user group. This user is a user of the client
OS.
Logging In as a Kerberos Domain User
a. (Optional) On the iBMC login page, switch to the target language.
b. Enter the Kerberos user name and password.
NO TE
▪ Kerberos user name (In this case, Domain can be Automatic matching or a
specified domain.)
▪ Kerberos user name@Domain name (In this case, Domain can be Automatic
matching or a specified domain, and all letters used in the domain name must
be in upper case.)
▪ When you log in to the iBMC WebUI as a Kerberos domain user, the password
can contain a maximum of 255 characters.
c. In the Domain drop-down list, select a Kerberos user domain (for example,
ADMIN.COM(KRB)) or Automatic matching.
d. Click Log In.
After the login is successful, the Home page is displayed.
Logging In over SSO
a. Use the Kerberos user name and password configured on the Kerberos
server to log in to the client OS.
b. Enter the FQDN of the iBMC in the address box of the browser, for example,
https://host name.domain name.
The iBMC login page is displayed.
c. Click SSO.
After the login is successful, the Home page is displayed.
----End
9.4.1.1 iBMC
Scenario
Log in to the desktop of a server using the iBMC Remote Virtual Console.
Procedure
Step 1 Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
Step 2 On the menu bar, choose Remote Console. The Remote Console page is
displayed.
● Java Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● Java Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● HTML5 Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● HTML5 Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● For details about the virtual console, see "Virtual Console" in the iBMC user guide of the
server you use.
----End
Scenario
Log in to the desktop of a server using the iBMC Remote Virtual Console.
Procedure
Step 1 Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
Step 2 Click Start in the Virtual Console area in the lower right corner of the Home page.
● Java Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● Java Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● HTML5 Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● HTML5 Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● For details about the virtual console, see "Virtual Console" in the iBMC user guide of the
server you use.
----End
Scenario
Log in to the desktop of a server using the iBMC Remote Virtual Console.
Procedure
Step 1 Log in to the iBMC WebUI.
For details, see 9.3 Logging In to the iBMC WebUI.
Step 2 Click Start in the Virtual Console area in the lower right corner of the Home page.
● Java Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● Java Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● HTML5 Integrated Remote Console (Private): allows only one local user or VNC user to
access and perform operations on the server through the iBMC.
● HTML5 Integrated Remote Console (Shared): allows two local users or up to five VNC
users to simultaneously access and perform operations on the server through the iBMC.
The users can see each other's operations.
● For details about the virtual console, see "Virtual Console" in the iBMC user guide of the
server you use.
----End
Scenario
Log in to the desktop of a server using the Independent Remote Console.
NO TE
If the client OS and iBMC versions are compatible with the Independent Remote Console, the
Independent Remote Console provides easier operations than the Remote Virtual Console.
9.4.2.1.1 Windows
The following Windows OS versions are supported:
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
NO TE
NO TE
----End
9.4.2.1.2 Ubuntu
The following Ubuntu OS versions are supported:
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
chmod 777 KVM.sh
Step 4 Open the Independent Remote Console.
./KVM.sh
The Independent Remote Console login page is displayed.
----End
9.4.2.1.3 Mac
The following macOS version is supported:
● macOS X El Capitan
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
chmod 777 KVM.sh
Step 4 Open the Independent Remote Console.
./KVM.sh
The Independent Remote Console login page is displayed.
----End
● RHEL 6.9
● RHEL 7.3
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
chmod 777 KVM.sh
Step 4 Open the Independent Remote Console.
./KVM.sh
The Independent Remote Console login page is displayed.
● Private Mode: allows only one user to access and manage the server or node at
a time.
----End
9.4.2.2.1 Windows
The following Windows OS versions are supported:
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
● Shared Mode: allows two users to access and manage the server or node at the
same time. Each user can view the operations performed by the other user.
● Private Mode: allows only one user to access and manage the server or node at
a time.
Step 5 Click Connect.
A security warning is displayed.
----End
9.4.2.2.2 Ubuntu
The following Ubuntu OS versions are supported:
Before the operation, ensure that the IPMItool version later than 1.8.14 has been
installed.
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
./KVM.sh
NO TE
----End
9.4.2.2.3 Mac
The following macOS version is supported:
● macOS X El Capitan
Before the operation, ensure that the IPMItool version later than 1.8.14 has been
installed.
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
NO TE
----End
● RHEL 6.9
● RHEL 7.3
Before the operation, ensure that the IPMItool version later than 1.8.14 has been
installed.
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
./KVM.sh
----End
9.4.2.3.1 Windows
The following Windows OS versions are supported:
● Windows 7 32-bit or 64-bit
● Windows 8 32-bit or 64-bit
● Windows 10 32-bit or 64-bit
● Windows Server 2008 R2 32-bit or 64-bit
● Windows Server 2012 64-bit
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Double-click KVM.exe.
Open the Independent Remote Console.
----End
9.4.2.3.2 Ubuntu
The following Ubuntu OS versions are supported:
Before the operation, ensure that the IPMItool version later than 1.8.14 has been
installed.
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
----End
9.4.2.3.3 Mac
The following macOS version is supported:
● macOS X El Capitan
Before the operation, ensure that the IPMItool version later than 1.8.14 has been
installed.
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
chmod 777 KVM.sh
Step 4 Open the Independent Remote Console.
./KVM.sh
The Independent Remote Console login page is displayed.
● Private Mode: allows only one user to access and manage the server or node at
a time.
Step 7 Click Connect.
A security warning is displayed.
----End
Procedure
Step 1 Configure an IP address for the client (local PC) to enable communication with the
iBMC management network port.
Step 2 Open the console and set the folder where the Independent Remote Console is
stored as the working folder.
Step 3 Grant the execute permission on the Independent Remote Console.
chmod 777 KVM.sh
Step 4 Open the Independent Remote Console.
./KVM.sh
The Independent Remote Console login page is displayed.
NO TE
----End
Scenarios
Use PuTTY to access a server over a local area network (LAN).
NO TE
● You can obtain the PuTTY software from the chiark home page.
● You are advised to use PuTTY of the latest version. PuTTY of an earlier version may cause
login failures.
Procedure
Step 1 Set an IP address and subnet mask or add route information for the PC to
communicate with the server.
Configure Host Name and Saved Sessions, and click Save. You can double-click the saved
record in Saved Sessions to log in to the server next time.
NO TE
● If this is your first login to the server, the PuTTY Security Alert dialog box is displayed.
Click Yes to proceed.
● If an incorrect user name or password is entered, you must set up a new PuTTY session.
----End
NO TE
● You can obtain the PuTTY software from the chiark home page.
● You are advised to use PuTTY of the latest version. PuTTY of an earlier version may cause
login failures.
Procedure
Step 1 On the PC, double-click PuTTY.exe.
The PuTTY Configuration window is displayed.
Step 2 In the navigation tree, choose Connection > Serial.
Step 3 Set the login parameters.
The parameters are described as follows:
● Serial Line to connect to: COMn
● Speed (baud): 115200
● Data bits: 8
● Stop bits: 1
● Parity: None
● Flow control: None
NO TE
Set Saved Sessions and click Save. You can double-click the saved record in Saved
Sessions to log in to the server next time.
The PuTTY screen is displayed. Then the message "login as:" is displayed,
prompting you to enter a user name.
NO TE
If this is your first login to the server, the PuTTY Security Alert dialog box is displayed. Click
Yes to proceed.
If the login is successful, the user name is displayed on the left of the prompt.
----End
● Before using the VMD function, contact technical support engineers of the OS
vendor to check whether the OS supports the VMD function. If yes, check
whether the VMD driver needs to be manually installed and check the installation
method.
● To use the VMD function, the iBMC version must be V304 or later. Otherwise,
the iBMC WebUI may fail to display NVMe drive information and the fan speed
cannot be adjusted based on the NVMe drive temperature, affecting the heat
dissipation of NVMe drives.
● The VMD function must be enabled in the BIOS. The function can be enabled
only in UEFI mode.
● When the VMD function is enabled and the latest VMD driver is installed, NVMe
SSDs support surprise hot swap. When the VMD function is disabled, NVMe
SSDs support orderly hot swap.
NO TE
If the BIOS version is V758 or later, select Hot Plug to enable the surprise hot swap
function for NVMe drives in Legacy mode. This option must be used with the drive
backplane CPLD or iBMC.
Procedure
Step 1 Access the BIOS.
----End
Procedure
Step 1 Access the BIOS.
----End
Figure 9-54 Drive numbering (I/O module 1 with 2 x 3.5" SAS/SATA drives)
10-13
14-15 CPU2
16-19
44-47
12-23 CPU2
44-47
NO TICE
● A forced restart or power cycle may cause data loss or program damage.
● Before performing a forced restart or power cycle, ensure that no service
interruption risk exists.
NO TE
NO TE
----End
Procedure
Step 1 Log in to the desktop of the server.
NO TICE
● A forced restart or power cycle may cause data loss or program damage.
● Before performing a forced restart or power cycle, ensure that no service
interruption risk exists.
NO TE
NO TE
● When you log in to the system using a common user password, only the Continue and
BIOS Configuration menu options are displayed on the Front Page screen.
● On the BIOS Configuration screen, common users can only view menu options, set or
change their own passwords, and save and exit. Set User Password in the Security
screen and Save Changes & Exit in the Exit screen can be configured but other options
are dimmed and cannot be edited. You can press F10 to save and exit, but the function of
F9 (restoring default settings) is unavailable.
----End
The following describes how to clear the data on one HDD/SSD as an example. This
operation is for reference only. You can also use other methods to clear data from
storage media.
NO TICE
The cleared data cannot be restored. Exercise caution when performing this
operation.
Procedure
NO TE
Step 1 You have accessed the desktop of the server where the target drive is located.
For details, see 9.4.1 Using the Remote Virtual Console.
Step 2 Open the CLI.
Step 3 Query information about drive letters.
lsscsi
NO TE
● The drive with the * symbol in the Boot column is the system drive. As shown in Figure
9-70, sda is the system drive.
● Do not directly clear system drive data. Before clearing system drive data, clear data from
other storage media.
NO TE
● The drive letters vary with the storage media (HDD, SSD, and USB flash drive). Ensure
that the drive letter that you entered is correct.
● This operation takes time.
● If the command fails to execute, contact technical support.
After the data is cleared, do not restart or reinstall the server. Otherwise, the system will reload
data to the drives during the startup of the server.
----End
● U-Boot is a kind of underlying software used to configure basic settings, for example,
initialize hardware devices and set up memory space mapping, to prepare for
commissioning the OS.
● For security purposes, change the initial password upon the first login, and change the
password periodically.
● For security purposes, enable password complexity check.
● The password complexity check function is enabled by default.
Procedure
Step 1 Log in to the iBMC CLI.
For details, see 9.5 Logging In to the CLI.
Step 2 Restart the iBMC system.
ipmcset -d reset
Information similar to the following is displayed:
This operation will reboot IPMC system. Continue? [Y/N]:
----End
10 More Information
Cases
To obtain case study about servers, visit Knowledge Base.
Contact xFusion
xFusion provides comprehensive technical support and services. To obtain
assistance, contact xFusion technical support as follows:
● Contact Global Technical Assistance Center by phone or email. For the phone
number and email address, see Global Service Hotline.
● Contact technical support personnel at your local xFusion branch office.
11.1 iBMC
11.2 BIOS
11.1 iBMC
The intelligent baseboard management controller (iBMC) complies with IPMI 2.0 and
SNMP standards and supports various functions, including KVM redirection, text
console redirection, remote virtual media, and highly reliable hardware monitoring
and management.
The iBMC supports domain name system (DNS) and Lightweight Directory
Application Protocol (LDAP) to implement domain management and directory
service.
● Image backup
The iBMC works in active/standby mode to ensure system reliability. If the active
iBMC is faulty, the standby iBMC takes over services immediately.
● Intelligent power management
The iBMC uses dynamic power saving to reduce operational expenditure
(OPEX).
For more information about the iBMC, see the FusionServer Rack Server iBMC
User Guide.
11.2 BIOS
The basic input/output system (BIOS) is the most basic software loaded on a
computer hardware system. The BIOS provides an abstraction layer between the
computer hardware and the OS. It performs hardware initialization during the boot
process and provides runtime services for the OS and programs.
The BIOS data is stored on the Serial Peripheral Interface (SPI) flash memory. The
BIOS performs a power-on self-test (POST), initializes CPUs and memory, checks
the I/O and boot devices, and finally boots the OS. The BIOS also provides features,
such as advanced configuration and power interface (ACPI) and hot swap.
Purley-based servers are developed based on Insyde code base. They provide a
variety of in-band and out-of-band configuration functions as well as high scalability,
and support customization.
For more information about the BIOS, see the Server Purley Platform BIOS
Parameter Reference.
A Appendix
The label information and location are for reference only. For details, see the actual product.
1 Nameplate 2 Certificate
A.1.1.1 Nameplate
1 Server Model
For details, see A.4 Nameplate .
2 Device names
5 Vendor Information
6 Authentication ID
A.1.1.2 Certificate
No. Description
1 Order
2 No.
NOTE
For details, see Figure A-4 and Table A-3.
3 QC inspector
4 Production date
5 No. Barcode
No. Description
3 ● Y: indicates a server.
● B: indicates a semi-finished server.
● N: indicates a spare part.
No. Description
No. Description
No. Description
7 P/N Code
8 QR Code
NOTE
Scan the QR code to obtain technical support resources.
NO TE
For details about the warning label, see Server Safety Information.
NO TE
● The quick guide is located on the inside of the chassis cover. It describes how to remove
the mainboard components, important components of the chassis, precautions, and QR
codes of technical resources. The pictures are for reference only. For details, see the
actual product.
● The quick guide is optional. For details, see the actual product.
A.2 Product SN
The serial number (SN) on the slide-out label plate uniquely identifies a device. The
SN is required when you contact technical support. Figure A-8 and Figure A-9 show
the SN formats.
● SN example 1
● SN example 2
3 Vendor code (two characters), that is, the code of the processing
place.
No. Description
● SN example 3
No. Description
No. Description
No. Description
No. Description
NO TE
A.4 Nameplate
Certified Model Usage Restrictions
H22H-05 Global
2288H V5 Global
For details about how to configure these features, see the Server Purley Platform
BIOS Parameter Reference.
UPI Intel UPI Link Level Retry Provides a retry mechanism to improve
the reliability of UPI links.
System Core Disable For FRB Isolates a faulty CPU core during
(Fault Resilient Boot) startup to improve system reliability and
availability.
Socket disable for FRB Isolates a faulty socket during the BIOS
(Fault Resilient Boot) startup process to improve system
reliability.
BIOS Abstraction Layer for The BIOS processes errors and reports
Error Handling error information to the OS based on
specifications, improving system
serviceability.
PCIe RAID$ Temp PCIe RAID controller card PCIe RAID controller card
temperature
RAID PCIE ERR RAID controller card fault RAID controller card
diagnosis health status
Table A-11 Problems of using optical modules that have not been tested for
compatibility and corresponding causes
Symptom Cause
Data bus defects cause the Some optical modules that have not been tested for
data bus suspension of a compatibility have defects in data bus designs.
device. Using such an optical module causes suspension of
the connected data bus on the device. As a result,
data on the suspended bus cannot be read.
An optical module with If an optical module that has not been tested for
improper edge connector compatibility with improper edge connector size is
size damages electronic used on an optical interface, electronic components
components of the optical of the optical interface will be damaged by short
interface. circuits.
Improper register settings Some optical modules that have not been tested for
cause errors or failures in compatibility have improper register values on page
reading parameters or A0, which can cause errors or failures when the
diagnostic information. data bus attempts to read parameters or diagnostic
information.
Optical modules bring Some optical modules that have not been tested for
electromagnetic compatibility are not designed in compliance with
interference to nearby EMC standards and have low anti-interference
devices. capability. Additionally, they bring electromagnetic
interference to nearby devices.
Symptom Cause
Optical modules cannot Some optical modules that are not tested for
work properly when the compatibility have poor heat dissipation. Since they
temperature change rate are not adapted to the heat dissipation policy of the
exceeds the normal range server, abnormally high temperatures may occur
without adapting to the heat continuously after they are running for a period of
dissipation policy of the time. As a result, the optical modules cannot work
server. properly.
B Glossary
B.1 A-E
E
ejector lever A part on the panel of a device used to facilitate
installation or removal of the device.
B.2 F-J
G
Gigabit Ethernet (GE) An extension and enhancement of traditional shared
media Ethernet standards. It is compatible with 10M and
100M Ethernet and complies with IEEE 802.3z
standards.
H
hot swap Replacing or adding components without stopping or
shutting down the system.
B.3 K-O
K
KVM A hardware device that provides public keyboard, video
and mouse (KVM).
B.4 P-T
P
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).
R
redundancy A mechanism that allows a backup device to
automatically take over services from a faulty device to
ensure uninterrupted running of the system.
S
server A special computer that provides services for clients over
a network.
system event log Event records stored in the system used for subsequent
(SEL) fault diagnosis and system recovery.
B.5 U-Z
U
U A unit defined in International Electrotechnical
Commission (IEC) 60297-1 to measure the height of a
cabinet or chassis. 1 U = 44.45 mm
C.1 A-E
A
AC alternating current
B
BBU backup battery unit
C
CD calendar day
CE Conformite Europeenne
D
DC direct current
E
ECC error checking and correcting
EN European Efficiency
C.2 F-J
F
FB-DIMM Fully Buffered DIMM
FC Fiber Channel
G
GE Gigabit Ethernet
H
HA high availability
I
iBMC intelligent baseboard management controller
IC Industry Canada
IP Internet Protocol
C.3 K-O
K
KVM keyboard, video, and mouse
L
LC Lucent connector
M
MAC media access control
N
NBD next business day
C.4 P-T
P
PCIe Peripheral Component Interconnect Express
POK power OK
Q
QPI Quick Path Interconnect
R
RAID redundant array of independent disks
S
SAS Serial Attached Small Computer System Interface
SERDES serializer/deserializer
T
TACH tachometer signal
C.5 U-Z
U
UDIMM unbuffered dual in-line memory module
V
VCCI Voluntary Control Council for Interference by Information
Technology Equipment
W
WEEE waste electrical and electronic equipment