FusionServer Pro Rack Server Upgrade Guide 35

FusionServer Pro Rack Server
Upgrade Guide
Issue 35
Date 2020-05-22
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://e.huawei.com
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. i

Upgrade Guide About This Document
About This Document
Purpose
This document describes how to upgrade the component firmware of Huawei
FusionServer Pro V2, V3, and V5 rack servers. The server types supported by each
component and firmware upgrade methods vary depending on the hardware
configuration of the V2, V3, and V5 rack servers.
Intended Audience
This document is intended for:
● Huawei technical support engineers
● Partner technical support engineers
● Enterprise administrators
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates a hazard with a high level of risk which,

if not avoided, will result in death or serious
injury.
Indicates a hazard with a medium level of risk

which, if not avoided, could result in death or
serious injury.
Indicates a hazard with a low level of risk which,

if not avoided, could result in minor or moderate
injury.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. ii

Symbol Description
Indicates a potentially hazardous situation which,

if not avoided, could result in equipment damage,
data loss, performance deterioration, or
unanticipated results.
NOTICE is used to address practices not related to
personal injury.
Supplements the important information in the

main text.
NOTE is used to address information not related
to personal injury, equipment damage, and
environment deterioration.
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue Date Description
35 2020-05-22 ● Added 1.16

Upgrading the LSI
SAS9305-24i RAID
Controller Card.
● Modified 3.2.1 Using
the iBMC Web to
Upgrade the BIOS.
34 2020-03-31 ● Modified 1.1.1.2

Update Procedure.
● Modified 2.1.1.2
Update Procedure.
Update Procedure.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. iii

33 2020-03-21 ● Added 1.12

Upgrading the MSCC
SmartRAID 3152-8i
RAID Controller
Card.
● Added 1.13
Upgrading the MSCC
SmartHBA 2100-8i
RAID Controller
Card.
● Added 3.12
Upgrading Smart
Provisioning.
Update Procedure.
32 2019-11-25 Modified 2.3.3.3 Rolling

Back the Firmware
Version.
31 2019-11-20 Modified 3.2.2 Using

SmartKit to Upgrade
the BIOS.
30 2019-10-18 ● Deleted the methods

for upgrading NICs
using DOS.
● Changed the
document name.
29 2019-05-23 ● Modified 1
Upgrading the RAID
Controller Card
Firmware.
● Modified 2
Upgrading the NIC
Firmware.
28 2019-05-22 ● Modified 1.8.3

Upgrading the
Avago SAS3416iMR
RAID Controller Card
Using CLI.
● Modified 1.7.3
Upgrading the
Avago SAS3408iMR
Using CLI.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. iv

27 2019-03-11 Added 2.8.1 Upgrading

the X557 NIC Using
FwUpgrade.
26 2019-01-16 ● Deleted the toolkit

upgrade mode of
RAID controller cards.
● Added the FwUpgrade
upgrade mode for
RAID controller cards
and NICs.
● Added reference
documents for BIOS
and iBMC upgrade
operations.
25 2018-10-11 Added precautions for

CPLD and BIOS upgrade.
24 2018-07-02 Added 1.1.3 Upgrading

the LSI SAS2208 RAID
Controller Card Using
CLI.
23 2018-05-18 Deleted "Upgrading the

LSI SAS3008 RAID
Controller Card (CLI)".
22 2018-04-20 ● Added 1.7.3

Upgrading the
Avago SAS3408iMR
Using CLI.
● Added 1.8.3
Upgrading the
Avago SAS3416iMR
Using CLI.
● Added 1.9.3
Upgrading the
Avago SAS3416IT
Using CLI.
● Added 2.5 Upgrading
the X550 NIC.
the SCM CPLD.
the LCD Firmware.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. v

21 2018-02-13 Added description of

upgrading the LSI
SAS3108 RAID control
card using CLI on the
VMware OS.
20 2017-11-28 ● Added description of

verifying the RAID
card upgrade.
● Added description of
RAID card version
rollback.

starting the NIC in
legacy mode.

upgrading the GPEA
complex programmable
logic device (CPLD) and
power supply modules of
the G5500.
17 2017-09-15 Optimized description of

the entire document.
16 2017-08-15 Updated description of

NIC firmware upgrade.

upgrading the RAID
controller card firmware.

upgrading the hard drive
backplane firmware.

the LSI SAS3008.
12 2017-01-20 Added description of the

X710 and XL710.
11 2016-12-28 Optimized description of

the entire document.
10 2016-07-13 Added description of the

PM8060 and PM8068.

upgrading the RAID
controller card and IB
card firmware.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. vi


upgrading the RAID
controller card firmware.

upgrading the
mainboard BIOS ME.
06 2014-10-25 Updated the default

password of iMana.

upgrading the
mainboard CPLD.
04 2014-09-15 Deleted the "Tecal"

trademark.

upgrading the LCD
firmware.
02 2014-04-15 Added "Preparing for the

Upgrade."
01 2014-02-15 This issue is the first

official release.
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. vii

Upgrade Guide Contents
Contents
About This Document................................................................................................................ ii

1 Upgrading the RAID Controller Card Firmware............................................................... 1
1.1 Upgrading the LSI SAS2208 RAID Controller Card...................................................................................................... 1
1.1.1 Upgrading the LSI SAS2208 RAID Controller Card Using FwUpgrade.............................................................. 1
1.1.1.1 Preparing for the Upgrade............................................................................................................................................ 2
1.1.1.1.1 Obtaining Software Packages...................................................................................................................................2
1.1.1.1.2 Verifying the Software Package Integrity............................................................................................................. 2
1.1.1.2 Update Procedure............................................................................................................................................................. 3
1.1.1.3 Rolling Back the Firmware Version............................................................................................................................ 3
1.1.1.3.1 Rollback Rules................................................................................................................................................................ 3
1.1.1.3.2 Rollback Procedure....................................................................................................................................................... 3
1.1.2 Upgrading the LSI SAS2208 RAID Controller Card Using SmartKit.................................................................... 3
1.1.2.3 Rolling Back the Firmware Version............................................................................................................................ 4
1.1.2.3.1 Rollback Rules................................................................................................................................................................ 4
1.1.2.3.2 Rollback Procedure....................................................................................................................................................... 5
1.1.3 Upgrading the LSI SAS2208 RAID Controller Card Using CLI............................................................................... 5
1.1.3.3 Rolling Back the Firmware Version.......................................................................................................................... 12
1.1.3.3.1 Rollback Rules.............................................................................................................................................................. 12
1.1.3.3.2 Rollback Procedure.....................................................................................................................................................12
1.2 Upgrading the LSI SAS2308 RAID Controller Card.................................................................................................... 12
1.2.1 Upgrading the LSI SAS2308 RAID Controller Card Using Toolkit..................................................................... 12
1.2.1.1 Preparing for the Upgrade.......................................................................................................................................... 12
1.2.1.1.1 Obtaining Software Packages................................................................................................................................ 12
1.2.1.1.2 Verifying the Software Package Integrity.......................................................................................................... 13
1.2.1.2 Update Procedure.......................................................................................................................................................... 13
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. viii

1.2.1.3 Rolling Back to the Source Version.......................................................................................................................... 19

1.2.1.3.1 Rollback Rules.............................................................................................................................................................. 19
1.2.1.3.2 Rollback Operations...................................................................................................................................................19
1.2.2 Upgrading the LSI SAS2308 RAID Controller Card Using FwUpgrade............................................................ 20
1.2.2.3.1 Rollback Rules.............................................................................................................................................................. 21
1.2.3 Upgrading the LSI SAS2308 RAID Controller Card Using SmartKit................................................................. 21
1.2.3.3.1 Rollback Rules.............................................................................................................................................................. 22
1.3 Upgrading the LSI SAS3008IR RAID Controller Card................................................................................................ 23
1.3.1 Upgrading the LSI SAS3008IR RAID Controller Card Using Toolkit................................................................. 23
1.3.1.3 Rolling Back to the Source Version.......................................................................................................................... 30
1.3.1.3.1 Rollback Rules.............................................................................................................................................................. 30
1.3.1.3.2 Rollback Operations...................................................................................................................................................30
1.3.2 Upgrading the LSI SAS3008IR RAID Controller Card Using FwUpgrade........................................................ 30
1.3.2.3.1 Rollback Rules.............................................................................................................................................................. 32
1.3.3 Upgrading the LSI SAS3008IR RAID Controller Card Using Smart Provisioning..........................................32
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. ix

1.3.3.3.1 Rollback Rules.............................................................................................................................................................. 33

1.3.4 Upgrading the LSI SAS3008IR RAID Controller Card Using SmartKit............................................................. 34
1.3.4.3.1 Rollback Rules.............................................................................................................................................................. 35
1.4 Upgrading the LSI SAS3008IT RAID Controller Card................................................................................................ 35
1.4.1 Upgrading the LSI SAS3008IT RAID Controller Card Using FwUpgrade........................................................ 35
1.4.1.3.1 Rollback Rules.............................................................................................................................................................. 37
1.4.2 Upgrading the LSI SAS3008IT RAID Controller Card Using Smart Provisioning..........................................37
1.4.2.3.1 Rollback Rules.............................................................................................................................................................. 38
1.4.3 Upgrading the LSI SAS3008IT RAID Controller Card Using SmartKit..............................................................39
1.4.3.3.1 Rollback Rules.............................................................................................................................................................. 40
1.5 Upgrading the LSI SAS3108 RAID Controller Card.................................................................................................... 40
1.5.1 Upgrading the LSI SAS3108 RAID Controller Card Using FwUpgrade............................................................ 40
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. x

1.5.1.3.1 Rollback Rules.............................................................................................................................................................. 42

1.5.2 Upgrading the LSI SAS3108 RAID Controller Card Using Smart Provisioning..............................................42
1.5.2.3.1 Rollback Rules.............................................................................................................................................................. 44
1.5.3 Upgrading the LSI SAS3108 RAID Controller Card Using SmartKit................................................................. 44
1.5.3.3.1 Rollback Rules.............................................................................................................................................................. 45
1.5.4 Upgrading the LSI SAS3108 RAID Controller Card Using CLI on Linux.......................................................... 46
1.5.4.3.1 Rollback Rules.............................................................................................................................................................. 52
1.5.5 Upgrading the LSI SAS3108 RAID Controller Card Using CLI on VMware.................................................... 52
1.5.5.3.1 Rollback Rules.............................................................................................................................................................. 57
1.5.6 Upgrading the LSI SAS3108 RAID Controller Card Using CLI on Windows...................................................57
1.5.6.3.1 Rollback Rules.............................................................................................................................................................. 65
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xi

1.6 Upgrading the Avago SAS3004iMR RAID Controller Card..................................................................................... 66

1.6.1 Upgrading the Avago SAS3004iMR RAID Controller Card Using CLI.............................................................. 66
1.6.1.3.1 Rollback Rules.............................................................................................................................................................. 71
1.6.2 Upgrading the Avago SAS3004iMR RAID Controller Card Using SmartKit................................................... 72
1.6.2.3.1 Rollback Rules.............................................................................................................................................................. 73
1.7.1 Upgrading the Avago SAS3408iMR RAID Controller Card Using Smart Provisioning............................... 74
1.7.1.3.1 Rollback Rules.............................................................................................................................................................. 75
1.7.2.3.1 Rollback Rules.............................................................................................................................................................. 76
1.7.3.3.1 Rollback Rules.............................................................................................................................................................. 88
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xii


1.8.1 Upgrading the Avago SAS3416iMR RAID Controller Card Using Smart Provisioning............................... 89
1.8.1.3.1 Rollback Rules.............................................................................................................................................................. 90
1.8.2.3.1 Rollback Rules.............................................................................................................................................................. 92
1.8.3.3.1 Rollback Rules.............................................................................................................................................................. 98
1.9 Upgrading the Avago SAS3416IT RAID Controller Card..........................................................................................99
1.9.1 Upgrading the Avago SAS3416IT RAID Controller Card Using Smart Provisioning................................... 99
1.9.1.2 Update Procedure........................................................................................................................................................ 100
1.9.1.3 Rolling Back the Firmware Version....................................................................................................................... 100
1.9.1.3.1 Rollback Rules........................................................................................................................................................... 100
1.9.1.3.2 Rollback Procedure.................................................................................................................................................. 100
1.9.2 Upgrading the Avago SAS3416IT RAID Controller Card Using SmartKit.....................................................100
1.9.2.1 Preparing for the Upgrade....................................................................................................................................... 100
1.9.2.1.1 Obtaining Software Packages.............................................................................................................................. 101
1.9.2.1.2 Verifying the Software Package Integrity........................................................................................................ 101
1.9.2.3.1 Rollback Rules........................................................................................................................................................... 102
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xiii

1.9.3 Upgrading the Avago SAS3416IT RAID Controller Card Using CLI................................................................102
1.9.3.3.1 Rollback Rules........................................................................................................................................................... 108
1.10 Upgrading the Avago SAS3508 RAID Controller Card........................................................................................ 109
1.10.1 Upgrading the Avago SAS3508 RAID Controller Card Using Smart Provisioning.................................. 109
1.10.1.1 Preparing for the Upgrade..................................................................................................................................... 109
1.10.1.1.1 Obtaining Software Packages........................................................................................................................... 109
1.10.1.1.2 Verifying the Software Package Integrity......................................................................................................110
1.10.1.2 Update Procedure..................................................................................................................................................... 110
1.10.1.3 Rolling Back the Firmware Version..................................................................................................................... 110
1.10.1.3.1 Rollback Rules......................................................................................................................................................... 110
1.10.1.3.2 Rollback Procedure................................................................................................................................................ 110
1.10.2 Upgrading the Avago SAS3508 RAID Controller Card Using SmartKit...................................................... 111
1.10.2.3.1 Rollback Rules......................................................................................................................................................... 112
1.10.3 Upgrading the Avago SAS3508 RAID Controller Card Using CLI................................................................. 112
1.10.3.3.1 Rollback Rules......................................................................................................................................................... 118
1.11 Upgrading the Avago SAS3516 RAID Controller Card........................................................................................ 119
1.11.1 Upgrading the Avago SAS3516 RAID Controller Card Using Smart Provisioning.................................. 119
1.11.1.3.1 Rollback Rules......................................................................................................................................................... 120
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xiv

1.11.2 Upgrading the Avago SAS3516 RAID Controller Card Using SmartKit...................................................... 121
1.11.2.3.1 Rollback Rules......................................................................................................................................................... 122
1.11.3 Upgrading the Avago SAS3516 RAID Controller Card Using CLI................................................................. 122
1.11.3.3.1 Rollback Rules......................................................................................................................................................... 129
1.12 Upgrading the MSCC SmartRAID 3152-8i RAID Controller Card.................................................................... 130
1.12.1 Upgrading the MSCC SmartRAID 3152-8i RAID Controller Card Using CLI............................................. 130
1.12.1.1 Before You Start......................................................................................................................................................... 130
1.12.1.2 Preparations................................................................................................................................................................ 131
1.12.1.3 Upgrade........................................................................................................................................................................ 132
1.12.1.4 Rollback........................................................................................................................................................................ 135
1.12.1.4.1 Rollback Guidelines............................................................................................................................................... 135
1.13 Upgrading the MSCC SmartHBA 2100-8i RAID Controller Card..................................................................... 136
1.13.1 Upgrading the MSCC SmartHBA 2100-8i RAID Controller Card Using CLI.............................................. 136
1.13.1.1 Before You Start......................................................................................................................................................... 136
1.13.1.2 Preparations................................................................................................................................................................ 137
1.13.1.3 Upgrade........................................................................................................................................................................ 138
1.13.1.4 Rollback........................................................................................................................................................................ 141
1.13.1.4.1 Rollback Guidelines............................................................................................................................................... 141
1.14 Upgrading the PM8060 RAID Controller Card Using CLI................................................................................... 142
1.14.1 Preparing for the Upgrade........................................................................................................................................ 142
1.14.1.1 Obtaining Software Packages............................................................................................................................... 142
1.14.1.2 Verifying the Software Package Integrity......................................................................................................... 143
1.14.2 Update Procedure......................................................................................................................................................... 143
1.14.3 Rolling Back the Firmware Version........................................................................................................................ 146
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xv

1.14.3.1 Rollback Rules............................................................................................................................................................ 146

1.14.3.2 Rollback Procedure................................................................................................................................................... 146
1.15 Upgrading the PM8068 RAID Controller Card Using CLI................................................................................... 147
1.15.1 Preparing for the Upgrade........................................................................................................................................ 147
1.15.1.1 Obtaining Software Packages............................................................................................................................... 147
1.15.1.2 Verifying the Software Package Integrity......................................................................................................... 147
1.15.2 Update Procedure......................................................................................................................................................... 148
1.15.3 Rolling Back the Firmware Version........................................................................................................................ 151
1.15.3.1 Rollback Rules............................................................................................................................................................ 151
1.15.3.2 Rollback Procedure................................................................................................................................................... 151
1.16 Upgrading the LSI SAS9305-24i RAID Controller Card....................................................................................... 151
1.16.1 Upgrading the LSI SAS9305-24i RAID Controller Card Using SmartKit..................................................... 151
1.16.1.3.1 Rollback Rules......................................................................................................................................................... 153
1.16.2 Upgrading the LSI SAS9305-24i RAID Controller Card Using CLI................................................................ 153
1.16.2.3.1 Rollback Rules......................................................................................................................................................... 157
2 Upgrading the NIC Firmware........................................................................................... 159

2.1 Upgrading the BCM5719................................................................................................................................................. 159
2.1.1 Upgrading the BCM5719 NIC Using FwUpgrade................................................................................................. 159
2.1.1.3.1 Rollback Rules........................................................................................................................................................... 160
2.2 Upgrading the 82599 NIC................................................................................................................................................161
2.2.1 Upgrading the 82599 NIC Using FwUpgrade........................................................................................................ 161
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xvi


2.2.1.3.1 Rollback Rules........................................................................................................................................................... 162
2.2.2 Upgrading the 82599 NIC Using Smart Provisioning......................................................................................... 163
2.2.2.3.1 Rollback Rules........................................................................................................................................................... 164
2.2.3 Upgrading the 82599 NIC Using SmartKit............................................................................................................. 164
2.2.3.3.1 Rollback Rules........................................................................................................................................................... 165
2.3 Upgrading the i350 NIC................................................................................................................................................... 166
2.3.1 Upgrading the i350 NIC Using FwUpgrade............................................................................................................166
2.3.1.3.1 Rollback Rules........................................................................................................................................................... 167
2.3.2 Upgrading the i350 NIC Using Smart Provisioning............................................................................................. 168
2.3.2.3.1 Rollback Rules........................................................................................................................................................... 169
2.3.3 Upgrading the i350 NIC Using SmartKit................................................................................................................. 169
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xvii


2.3.3.3.1 Rollback Rules........................................................................................................................................................... 170
2.4 Upgrading the X540 NIC.................................................................................................................................................. 171
2.4.1 Upgrading the X540 NIC Using FwUpgrade.......................................................................................................... 171
2.4.1.3.1 Rollback Rules........................................................................................................................................................... 172
2.4.2 Upgrading the X540 NIC Using Smart Provisioning............................................................................................173
2.4.2.3.1 Rollback Rules........................................................................................................................................................... 174
2.4.3 Upgrading the X540 NIC Using SmartKit................................................................................................................174
2.4.3.3.1 Rollback Rules........................................................................................................................................................... 175
2.5.1.3.1 Rollback Rules........................................................................................................................................................... 177
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xviii


2.5.2.3.1 Rollback Rules........................................................................................................................................................... 179
2.6 Upgrading the X710/XL710 NIC.................................................................................................................................... 179
2.6.1 Upgrading the X710/XL710 NIC Using FwUpgrade............................................................................................ 179
2.6.1.3.1 Rollback Rules........................................................................................................................................................... 181
2.6.2 Upgrading the X710/XL710 NIC Using Smart Provisioning.............................................................................. 181
2.6.2.3.1 Rollback Rules........................................................................................................................................................... 182
2.6.3 Upgrading the X710/XL710 NIC Using SmartKit.................................................................................................. 183
2.6.3.3.1 Rollback Rules........................................................................................................................................................... 184
2.7.1.3.1 Rollback Rules........................................................................................................................................................... 190
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xix


2.7.2.3.1 Rollback Rules........................................................................................................................................................... 192
2.8.1.3.1 Rollback Rules........................................................................................................................................................... 199
2.8.2.3.1 Rollback Rules........................................................................................................................................................... 201
2.9 Upgrading the ConnectX-3 NIC..................................................................................................................................... 201
2.9.1 Upgrading the ConnectX-3 NIC Using DOS........................................................................................................... 201
2.9.1.3.1 Rollback Rules........................................................................................................................................................... 202
2.9.2 Upgrading the ConnectX-3 NIC Using SmartKit................................................................................................... 203
2.9.2.3.1 Rollback Rules........................................................................................................................................................... 204
2.10 Upgrading the ConnectX-4 NIC................................................................................................................................... 204
2.10.1 Upgrading the ConnectX-4 NIC Using FwUpgrade........................................................................................... 205
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xx


2.10.1.3.1 Rollback Rules......................................................................................................................................................... 206
2.10.2 Upgrading the ConnectX-4 NIC Using Smart Provisioning............................................................................ 206
2.10.2.3.1 Rollback Rules......................................................................................................................................................... 207
2.10.3 Upgrading the ConnectX-4 NIC Using SmartKit................................................................................................ 208
2.10.3.3.1 Rollback Rules......................................................................................................................................................... 209
2.11 Upgrading the ConnectX-5 NIC................................................................................................................................... 209
2.11.1 Upgrading the ConnectX-5 NIC Using FwUpgrade........................................................................................... 210
2.11.1.3.1 Rollback Rules......................................................................................................................................................... 211
2.11.2 Upgrading the ConnectX-5 NIC Using SmartKit................................................................................................ 211
2.11.2.3.1 Rollback Rules......................................................................................................................................................... 212
3 Upgrading the Firmware of Chassis Components....................................................... 214

3.1 Upgrading the iBMC.......................................................................................................................................................... 214
3.1.1 Using the iBMC Web to Upgrade the iBMC...........................................................................................................214
3.1.1.1 Before You Start........................................................................................................................................................... 214
3.1.1.1.1 Impact of the Upgrade........................................................................................................................................... 214
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxi

3.1.1.1.2 Precautions................................................................................................................................................................. 215

3.1.1.1.3 Version Requirements............................................................................................................................................. 216
3.1.1.1.4 Upgrade Process....................................................................................................................................................... 216
3.1.1.2.1 Pre-upgrade Checklist............................................................................................................................................. 217
3.1.1.2.2 Obtaining the Upgrade Packages and Documents...................................................................................... 217
3.1.1.3 Upgrading the iBMC................................................................................................................................................... 218
3.1.1.3.1 Update Procedure.................................................................................................................................................... 218
3.1.1.3.2 Verifying the Upgrade............................................................................................................................................ 221
3.1.1.4 Upgrading iBMC Language Packs.......................................................................................................................... 222
3.1.1.4.1 Performing the Upgrade........................................................................................................................................ 222
3.1.1.5 Rolling Back to the Source Version....................................................................................................................... 224
3.1.1.5.1 Rollback Rules........................................................................................................................................................... 225
3.1.1.5.2 Rollback Operations................................................................................................................................................ 225
3.1.2 Using SmartKit to Upgrade the iBMC...................................................................................................................... 225
3.1.2.3.1 Rollback Rules........................................................................................................................................................... 227
3.2 Upgrading the BIOS........................................................................................................................................................... 227
3.2.1 Using the iBMC Web to Upgrade the BIOS........................................................................................................... 227
3.2.1.1 Before You Start........................................................................................................................................................... 227
3.2.1.1.1 Impact of the Upgrade........................................................................................................................................... 227
3.2.1.1.2 Precautions................................................................................................................................................................. 228
3.2.1.1.3 Version Requirements............................................................................................................................................. 228
3.2.1.1.4 Upgrade Process....................................................................................................................................................... 228
3.2.1.2.1 Pre-upgrade Checklist............................................................................................................................................. 229
3.2.1.2.2 Obtaining the Upgrade Packages and Documents...................................................................................... 229
3.2.1.3 Upgrading the BIOS.................................................................................................................................................... 230
3.2.1.3.1 Performing the Upgrade........................................................................................................................................ 230
3.2.1.4.1 Rollback Rules........................................................................................................................................................... 236
3.2.2 Using SmartKit to Upgrade the BIOS....................................................................................................................... 236
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxii


3.2.2.3.1 Rollback Rules........................................................................................................................................................... 238
3.3 Upgrading the Mainboard CPLD................................................................................................................................... 238
3.3.1 Using the iBMC Web to Upgrade the Mainboard CPLD....................................................................................238
3.3.1.3.1 Rollback Rules........................................................................................................................................................... 242
3.3.2 Using the iMana 200 to Upgrade the Mainboard CPLD................................................................................... 243
3.3.2.3.1 Rollback Rules........................................................................................................................................................... 245
3.3.3 Using SmartKit to Upgrade the Mainboard CPLD............................................................................................... 246
3.3.3.3.1 Rollback Rules........................................................................................................................................................... 247
3.4 Upgrading the Hard Disk Backplane CPLD............................................................................................................... 248
3.4.1 Using the iBMC Web to Upgrade the Hard Disk Backplane CPLD................................................................ 248
3.4.1.3.1 Rollback Rules........................................................................................................................................................... 251
3.4.2 Using the iMana 200 to Upgrade the Hard Disk Backplane CPLD................................................................252
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxiii


3.4.2.3.1 Rollback Rules........................................................................................................................................................... 255
3.4.3 Using SmartKit to Upgrade the Hard Disk Backplane CPLD........................................................................... 255
3.4.3.3.1 Rollback Rules........................................................................................................................................................... 257
3.5 Upgrading the SCM CPLD............................................................................................................................................... 257
3.5.1 Using the iBMC Web to Upgrade the SCM CPLD................................................................................................ 257
3.5.1.3.1 Rollback Rules........................................................................................................................................................... 261
3.5.2 Using SmartKit to Upgrade the SCM CPLD........................................................................................................... 261
3.5.2.3.1 Rollback Rules........................................................................................................................................................... 263
3.6 Upgrading the I/O Module CPLD.................................................................................................................................. 263
3.6.1 Using the iBMC Web to Upgrade the I/O Module CPLD.................................................................................. 263
3.6.1.2 Upgrade Procedure..................................................................................................................................................... 264
3.6.1.3.1 Rollback Rules........................................................................................................................................................... 267
3.6.2 Using SmartKit to Upgrade the I/O Module CPLD..............................................................................................267
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxiv


3.6.2.3.1 Rollback Rules........................................................................................................................................................... 269
3.7 Upgrading the Riser Card CPLD.....................................................................................................................................269
3.7.1 Using the iBMC Web to Upgrade the Riser Card CPLD..................................................................................... 269
3.7.1.3.1 Rollback Rules........................................................................................................................................................... 273
3.7.2 Using the iMana 200 to Upgrade the Riser Card CPLD..................................................................................... 273
3.7.2.3.1 Rollback Rules........................................................................................................................................................... 276
3.7.3 Using SmartKit to Upgrade the Riser Card CPLD.................................................................................................276
3.7.3.3.1 Rollback Rules........................................................................................................................................................... 278
3.8 Upgrading the LCD Firmware.........................................................................................................................................278
3.8.1 Using the iBMC Web to Upgrade the LCD Firmware......................................................................................... 278
3.8.1.3.1 Rollback Rules........................................................................................................................................................... 281
3.8.2 Using the iMana 200 to Upgrade the LCD Firmware......................................................................................... 281
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxv


3.8.2.3.1 Rollback Rules........................................................................................................................................................... 283
3.8.3 Using SmartKit to Upgrade the LCD Firmware.....................................................................................................284
3.8.3.3.1 Rollback Rules........................................................................................................................................................... 285
3.9 Upgrading the Hard Disk Backplane Firmware....................................................................................................... 285
3.9.1 Using the iBMC Web to Upgrade the Hard Disk Backplane Firmware........................................................ 285
3.9.1.3.1 Rollback Rules........................................................................................................................................................... 292
3.9.2 Using SmartKit to Upgrade the Hard Disk Backplane Firmware................................................................... 292
3.9.2.3.1 Rollback Rules........................................................................................................................................................... 294
3.10 Upgrading the SD Card Controller Firmware......................................................................................................... 294
3.10.1 Using the iBMC Web to Upgrade the SD Card Controller Firmware.......................................................... 294
3.10.1.3 Rolling Back to the Source Version..................................................................................................................... 297
3.10.1.3.1 Rollback Rules......................................................................................................................................................... 297
3.10.1.3.2 Rollback Operations.............................................................................................................................................. 297
3.10.2 Using SmartKit to Upgrade the SD Card Controller Firmware..................................................................... 297
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxvi


3.10.2.3.1 Rollback Rules......................................................................................................................................................... 299
3.11 Upgrading the Fan Module Firmware...................................................................................................................... 299
3.11.1 Using the iBMC Web to Upgrade the Fan Module Firmware....................................................................... 299
3.11.1.3 Rolling Back to the Source Version..................................................................................................................... 302
3.11.1.3.1 Rollback Rules......................................................................................................................................................... 302
3.11.1.3.2 Rollback Operations.............................................................................................................................................. 302
3.11.2 Using SmartKit to Upgrade the Fan Module Firmware.................................................................................. 302
3.11.2.3.1 Rollback Rules......................................................................................................................................................... 304
3.12 Upgrading Smart Provisioning.....................................................................................................................................304
3.12.1 Upgrade Using Smart Provisioning.........................................................................................................................304
3.12.2 Upgrade Using SmartKit............................................................................................................................................ 304
4 Common Operations.......................................................................................................... 305

4.1 Querying the IP Address of the iBMC Management Network Port.................................................................. 305
4.1.1 Querying the IP Address of the iBMC Management Network Port (Grantley Platform)...................... 305
4.1.2 Querying the IP Address of the iBMC Management Network Port (Purley Platform)...........................309
4.1.3 Querying the IP Address of the iBMC Management Network Port Using SSH.........................................314
4.1.4 Checking the IBMC IP Address................................................................................................................................... 315
4.2 Logging In to the iBMC WebUI......................................................................................................................................318
4.3 Logging In Using the iMana 200 WebUI.................................................................................................................... 321
4.4 Logging In Using the iBMC WebUI.............................................................................................................................. 325
4.5 Accessing the iBMC CLI.................................................................................................................................................... 328
4.6 Transferring Files Using the Local Directory............................................................................................................. 331
4.7 Checking Server Software Versions.............................................................................................................................. 332
4.8 Checking Server Alarms................................................................................................................................................... 334
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. xxvii

Upgrade Guide 1 Upgrading the RAID Controller Card Firmware
1 Upgrading the RAID Controller Card

Firmware
1.1 Upgrading the LSI SAS2208 RAID Controller Card

1.3 Upgrading the LSI SAS3008IR RAID Controller Card
1.4 Upgrading the LSI SAS3008IT RAID Controller Card
1.6 Upgrading the Avago SAS3004iMR RAID Controller Card
1.9 Upgrading the Avago SAS3416IT RAID Controller Card
1.10 Upgrading the Avago SAS3508 RAID Controller Card
1.11 Upgrading the Avago SAS3516 RAID Controller Card
1.12 Upgrading the MSCC SmartRAID 3152-8i RAID Controller Card
1.13 Upgrading the MSCC SmartHBA 2100-8i RAID Controller Card
1.14 Upgrading the PM8060 RAID Controller Card Using CLI
1.15 Upgrading the PM8068 RAID Controller Card Using CLI
1.16 Upgrading the LSI SAS9305-24i RAID Controller Card
1.1.1 Upgrading the LSI SAS2208 RAID Controller Card Using

FwUpgrade
Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. 1

1.1.1.1 Preparing for the Upgrade
1.1.1.1.1 Obtaining Software Packages
Scenarios
Obtain the required software packages before the upgrade.
Procedure
Obtain the required software packages using the methods described in Table 1.
Table 1-1 Software package

Software Package Operation Procedure
Type
Firmware upgrade 1. Log in to the FusionServer iDriver website.

package of the 2. Select the target version.
RAID controller
card 3. Download upgrade packages of the required
components.
NOTE
The FwUpgrade version varies depending on the firmware
package versions. For details, see the description of the
firmware package.
FwUpgrade tool 1. Log in to the FusionServer Tools website.

package 2. Select the required version.
3. Download the required FwUpgrade package.
1.1.1.1.2 Verifying the Software Package Integrity

To prevent a software package from being maliciously tampered with during
transmission or storage, download the corresponding digital signature file for
integrity verification when downloading the software package.
After the software package is downloaded, verify its PGP digital signature
according to the OpenPGP Signature Verification Guide. If the software package
fails the verification, do not use the software package, and contact Huawei
technical support engineers.
Before a software package is used in installation or upgrade, its digital signature
also needs to be verified according to the OpenPGP Signature Verification Guide
to ensure that the software package is not tampered with.
Visit either of the following websites to obtain the OpenPGP Signature Verification
Guide:
● Carrier customers: https://support.huawei.com/carrier/
digitalSignatureAction
● Enterprise customers: https://support.huawei.com/enterprise/en/tool/pgp-
verify-TL1000000054

1.1.1.2 Update Procedure

For details, see "Using FwUpgrade" in the FusionServer Tools 2.0 FwUpgrade
User Guide.
Upgrade using FwUpgrade applies to the LSI SAS2208 RAID control card only on V2 and V3
servers.
1.1.1.3 Rolling Back the Firmware Version
1.1.1.3.1 Rollback Rules

Perform a rollback only if one of the following problems occurs:
● A major fault occurs during the upgrade, and the fault cannot be rectified
within a specified period.
● The server does not function properly after the upgrade.
● An upgrade cannot be completed within a specified period, resulting in longer
service interruption.
If an upgrade fails and the version is still the source version, you do not need to
perform a rollback.
1.1.1.3.2 Rollback Procedure

Step 1 Determine the target version.
Step 2 Roll back the firmware version.
The rollback procedure is similar to the upgrade procedure. For details, see
FusionServer Tools 2.0 FwUpgrade User Guide.
----End

SmartKit
Scenarios
Procedure
Obtain the required software packages using the methods described in Table 1-2.


Type

RAID controller
components.
SmartKit tool 1. Log in to the FusionServer Tools website.

3. Download the required SmartKit package.

Guide:
verify-TL1000000054

For details, see "Upgrading PCIe Card and Hard Disk Firmware" in the
FusionServer Tools 2.0 SmartKit User Guide.
Upgrade using SmartKit applies to the LSI SAS2208 RAID control card only on V2 and V3
servers.


perform a rollback.

----End

CLI
Scenarios
Procedure

Type

RAID controller
components.


Type
Management tool 1. Log in to the page of the RAID card on the

of the RAID BROADCOM website.
controller card 2. On the DOWNLOADS tab page, click Management
Software and Tools.
The list of management software and tools is
displayed.
3. Download the MegaRAID Storcli tool of the latest
version.
4. After the decompression, the tool packages that are
applicable to different operating systems will be
obtained.

Guide:
verify-TL1000000054
Scenarios
Upgrade the LSI SAS2208 RAID controller card firmware using CLI on Linux.

NOTICE
● To avoid impact on service performance, stop all services before the upgrade.
● Do not power off the server during the upgrade. Otherwise, the upgrade may
fail.
● Unless otherwise stated, do not attempt configurations not described in this
upgrade guide.
Prerequisites
Conditions
● The server hosting the LSI SAS2208 RAID controller card is powered on.
● You have logged in to the iBMC WebUI.
Data
None
Software
● You have downloaded and decompressed the driver package (for example,
RH2288H V3-Rhel-Driver-V106) to the client (a PC) and obtained the driver
image (for example, onboard_driver_rhel7.1.iso).
● You have downloaded and decompressed the firmware upgrade package (for
example, RAID card(BC1ESMD01)-SR320BC(2208)-FW-V110(FW
3.460.165-8277).zip) to the client (a PC).
Procedure
Step 1 (Optional) Query the Bus/Device/Function (BDF) of RAID controller cards.
If the server is equipped with multiple RAID controller cards, perform this step to query
their BDF.
1. Open the Remote Virtual Console.

2. Query the BDF of RAID controller cards.
If the server is equipped with multiple RAID IMR cards or RAID MR cards, run
the lspci |grep -i LSI command on the OS CLI. The command output displays
information about the RAID controller cards according to their locations in the
server.
BDF 01:00.0corresponds to the controller whose address is c0.
Step 2 (Optional) Install the driver of the LSI SAS2208 RAID controller card.
Install the driver of the LSI SAS2208 RAID controller card when you install the OS.
For details, see Installing an OS by Loading a RAID Controller Card Driver in
the Huawei Server OS Installation Guide.

1. Mount the image (.iso).

a. Open the Remote Virtual Console.
b. Click on the toolbar.

The screen shown in Figure 1-1 is displayed.
Figure 1-1 Virtual DVD-ROM drive
c. Select Image File, and click Browse.

The Open dialog box is displayed.
d. Select the image (for example, onboard_driver_rhel7.0.iso), and click
Connect in the screen shown in Figure 1-1.
2. Install the driver.
a. On the OS CLI, run the mount /dev/sr0 /mnt command to mount the
image to the /mnt directory.
b. Run the cd /mnt command to switch to the /mnt directory, and run the
ls command to display all the files in the directory.
c. Run the cp /mnt/kmod-

megaraid_sas-06.812.07.00_e17.1-1.x86_64.rpm /root command to
copy the driver upgrade file to the /root directory.
d. Run the cd /root command to go to the /root directory.

e. Run the rpm -Uvh kmod-
megaraid_sas-06.812.07.00_e17.1-1.x86_64.rpm command to upgrade
the driver of the LSI SAS3108 RAID controller card.
If the file name or path contains any special characters of shell commands, add \
before them to turn them into common characters.
f. Run the reboot command to reboot the server.

Step 3 Mount the upgrade file.
1. Mount the upgrade file to a local directory.
a. On the toolbar of the Remote Virtual Console, click .

b. Select Directory, and click Browse.

c. Select the directory generated after the firmware upgrade package (for
example, RH2288H V3-RAID card(BC1ESMD01)-SR320BC(2208)-FW-
V110(FW 3.460.165-8277).zip, is decompressed.
d. Click Connect.
2. Copy the upgrade package to the server.
local directory to the /mnt directory.
b. Run cp /mnt /* /root/ -r to copy the files to the /root directory.
c. Run the cd /root command to go to the /root directory.
d. Run the chmod 777 * command to add the read and write permissions
for the files.
Step 4 Perform a pre-upgrade check.

1. Run the ./storcli64 /c0 show command to query RAID controller card and
hard drive information. See Figure 1-3 and Figure 1-4.
Figure 1-3 Querying RAID controller card information

Figure 1-4 Querying hard drive information
2. Run the ./storcli64 /c0/vall show all command to query RAID array
information.
a. View RAID array information. As shown in Figure 1-5, TYPE indicates the
RAID array level; State indicates the RAID array status; Access indicates
the read/write policy.
Figure 1-5 Viewing RAID array information
b. View hard drive locations. As shown in Figure 1-6, EID:SIt indicates hard
drive backplane ID:hard drive slot ID. In this example, the hard drives that
constitute the RAID array are located in slots 4 and 5.
Figure 1-6 Viewing hard drive locations
c. View the strip size. As shown in Figure 1-7, Strip Size indicates the strip
size of the RAID array.

Figure 1-7 Viewing the strip size
Step 5 Upgrade the firmware of the RAID controller card.
If the upgrade fails or a rollback is required, contact Huawei technical support.

1. Run ./storcli64 /cController_ID download file=2208FW8.rom noverchk to
upgrade the firmware.
In the command, Controller_ID indicates the ID of the RAID controller card.
To configure multiple RAID controller cards, change the controller IDs in the
command.
– The firmware upgrade package contains two .rom files, 2208FW8.rom and
2208FW32.rom.
– 2208FW8.rom is used to upgrade a RAID controller card that contains RAID
information.
– 2208FW32.rom is used to:
▪ Upgrade a RAID controller card that does not contain RAID information.
▪ Upgrade a RAID controller card in the DOS system.
2. Restart the server for the new firmware to take effect.

a. Click on the toolbar. Click Power Off.
b. Click Power On.
Step 6 Perform a post-upgrade check.
Repeat Step 4 to query the firmware version, RAID array, and hard drive
information.

The upgrade is successful if the firmware version of the RAID controller card is the
target version and the RAID array and hard drive information is the same as that
before the upgrade.
----End

perform a rollback.

The rollback procedure is similar to the upgrade procedure. For details, see 1.1.3.2
Update Procedure.
----End

Toolkit
Scenarios
Procedure


Type

RAID controller
components.
Toolkit tool 1. Log in to the FusionServer Tools website.

3. Download the required Toolkit package.

Guide:
verify-TL1000000054
Scenarios
Use Toolkit to upgrade the LSI SAS2308 RAID controller card firmware. This
method also applies to the LSI HBA SAS 9217–8i RAID controller card.

NOTICE
● After the Toolkit is mounted, the server must be rebooted. Services are
interrupted during the reboot process.
fail.
upgrade guide.
Prerequisites
Conditions
Software
You have downloaded and decompressed the firmware upgrade package

RAID_card(2208&2308&3008&3108)-FW-Vxxx.zip and obtained FusionServer-
RAID_card(2208&2308&3008&3108)-FW-Vxxx.iso.
Procedure
Step 1 Set the system boot device to DVD-ROM drive.
1. On the iBMC WebUI, choose Configure > Boot Option.
The Boot Option page is displayed.
2. Select DVD-ROM, and click Save.
Step 2 Mount the FusionServer Tools-Toolkit-Vxxx.iso file.

2. Click on the toolbar.

3. Select Image File, and click Browse.

4. Select FusionServer-RAID_card(2208&2308&3008&3108)-FW-Vxxx.iso, and
click Connect in the screen shown in Figure 1-8.
Step 3 Reboot the server.


The menu shown in Figure 1-9 is displayed.
Figure 1-9 Power control
2. Select the option based on the actual server status to reboot the server.
After the server reboots, the screen shown in Figure 1-10 is displayed.
Figure 1-10 Toolkit startup screen
Step 4 Switch to the Toolkit CLI.

1. Select Toolkit, and press Enter.
2. When information shown in Figure 1-11 is displayed, enter C and press Enter.

Figure 1-11 Toolkit menu
3. Enter the user name and password as prompted.

The CLI is displayed.
The default user is root, and the password is Huawei12#$.
Step 5 Upgrade the firmware.

1. Run the cd /home/Project/tools/upgrade/raid/tool/ command to go to the /
tool directory.
2. Run ./FwUpgrade.py FwUpgrade.xml to upgrade the RAID controller card
firmware.
After the upgrade is complete, information shown in Figure 1-12 is displayed.
– The LSI SAS2308 controller card can be upgraded but cannot be downgraded.
– The xxxxupgrade.log file in the /home/Project/FTK/upgrade/raid/tool/ directory
records the upgrade process of the RAID controller card. If the upgrade fails,
provide this file to Huawei technical support engineers for locating faults.
– If a rollback is required, contact Huawei technical support.
Figure 1-12 Upgrade completed

Step 6 Reboot the server for the new firmware to take effect.
During the reboot process, the RAID controller card firmware information is
displayed, as shown in Figure 1-13.
Figure 1-13 RAID controller card firmware information
Step 7 Check whether the firmware version of the RAID controller card is the target
version.
If no error information is displayed during the upgrade process and the version queried
after the upgrade is the target version, the upgrade is successful.
You can check the firmware version using one of the following methods:
● View the firmware version during the server startup process, as shown in
Figure 1-13.
● Query the firmware version on the RAID controller card Config Utility, as
shown in Figure 1-14.
Figure 1-14 Firmware version
----End

Additional Information
After upgrading the LSI SAS2308 RAID controller card firmware, activate RAID and
configure the boot device as follows:
1. When the message "Press Ctrl-C to Start LSI Corp Configuration Utility..." is
displayed during compute node startup, press Ctrl+C.
2. On the Config Utility screen, select the LSI SAS2308 RAID controller card, and
press Enter.
3. On the Adapter Properties screen, choose RAID Properties > View Existing
Volume.
The RAID array status is Inactive, as shown in Figure 1-15.
Figure 1-15 View Volume
4. Select Manage Volume, and press Enter.

The Manage Volume screen is displayed, as shown in Figure 1-16.
Figure 1-16 Manage Volume

5. Select Activate Volume, and press Enter.

A message is displayed asking you whether to activate the volume.
6. Press Y to activate the RAID array, and press Esc to return to the Manage
Volume screen.
7. Press Esc to return to the Adapter Properties screen.
8. Select SAS Topology, and press Enter.
9. Select the RAID array or disk on which the OS is installed, and press Alt+B to
set it as the boot device.
Boot is displayed in the Device Info column of the boot device, as shown in
Figure 1-17.
Figure 1-17 Setting the boot drive
10. Press Esc repeatedly to save the settings and exit the Config Utility.
11. Reboot the server.
1.2.1.3 Rolling Back to the Source Version

perform a rollback. Decide whether to perform a rollback if one of the following
problems occurs:
● A major fault occurs during the upgrade, and the fault cannot be diagnosed
and rectified within a specified period.
● A new version functions abnormally.
● An upgrade cannot be completed within a specified period. To avoid service
interruption if the upgrade proceeds during peak hours, perform a rollback.
1.2.1.3.2 Rollback Operations

To roll back the firmware of an LSI SAS2308 RAID control card, contact Huawei
technical support.


FwUpgrade
Scenarios
Procedure

Type

RAID controller
components.
NOTE
firmware package.


Guide:


verify-TL1000000054

User Guide.
servers.

perform a rollback.

technical support.

SmartKit
Scenarios
Procedure


Type

RAID controller
components.


Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the LSI SAS2308 RAID control card only on V2 and V3
servers.


perform a rollback.

technical support.
1.3 Upgrading the LSI SAS3008IR RAID Controller Card
1.3.1 Upgrading the LSI SAS3008IR RAID Controller Card Using

Toolkit
Scenarios
Procedure

Type

RAID controller
components.
Toolkit tool 1. Log in to the FusionServer Tools website.

3. Download the required Toolkit package.


Guide:
verify-TL1000000054
Scenarios
Use Toolkit to upgrade the LSI SAS3008IR RAID controller card firmware. This
method also applies to the LSI HBA SAS 9311–8i and LSI HBA SAS 9300–8i RAID
controller cards.
NOTICE
● After the Toolkit is mounted, the server must be rebooted. Services are
interrupted during the reboot process.
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the LSI SAS3008IR RAID controller card is powered on.
Software
You have downloaded and decompressed the firmware upgrade package
RAID_card(2208&2308&3008&3108)-FW-Vxxx.zip and obtained FusionServer-
RAID_card(2208&2308&3008&3108)-FW-Vxxx.iso.

Procedure
Step 2 Mount the FusionServer Tools-Toolkit-Vxxx.iso file.


4. Select FusionServer Tools-Toolkit-Vxxx.iso, and click Connect in the screen


Figure 1-20 Toolkit startup screen
Step 4 Switch to the Toolkit CLI.

1. Select Toolkit, and press Enter.
2. When information shown in Figure 1-21 is displayed, enter C and press Enter.
Figure 1-21 Toolkit menu
3. Enter the user name and password as prompted.

The CLI is displayed.
The default user is root, and the password is Huawei12#$.
Step 5 Upgrade the firmware.

1. Run the cd /home/Project/tools/upgrade/raid/tool/ command to go to the /
tool directory.

2. Run ./FwUpgrade.py FwUpgrade.xml to upgrade the RAID controller card

firmware.
After the upgrade is complete, information shown in Figure 1-22 is displayed.
– The xxxxupgrade.log file in the /home/Project/FTK/upgrade/raid/tool/ directory

records the upgrade process of the RAID controller card. If the upgrade fails,
provide this file to Huawei technical support engineers for locating faults.
– If a rollback is required, contact Huawei technical support.
Figure 1-22 Upgrade completed
Step 6 Reboot the server for the new firmware to take effect.
version.

● Obtain the firmware version during the server startup process, as shown in
Figure 1-23.
● Query the firmware version on the RAID controller card Config Utility, as
Figure 1-24 Firmware version
----End
Additional Information
Related Tasks
After upgrading the LSI SAS3008 RAID controller card firmware, activate RAID and
configure the boot option as follows:
1. When the message "Press Ctrl-C to Start LSI Corp Configuration Utility..." is
displayed during server startup, press Ctrl+C.
2. On the Config Utility screen , choose RAID Properties > View Existing
Volume.
The RAID array status is Inactive, as shown in Figure 1-25.

Figure 1-25 View Volume
3. Select Manage Volume, and press Enter.

The Manage Volume screen is displayed, as shown in Figure 1-26.
Figure 1-26 Manage Volume
4. Select Activate Volume, and press Enter.

A message is displayed asking you whether to activate the volume.
5. Press Y to activate the RAID array, and press Esc to return to the Manage
Volume screen.
6. Press Esc to return to Adaptor Properties.
7. Select SAS Topology, and press Enter.
8. Select the RAID array or disk on which the OS is installed, and press Alt+B to
set it as the boot device.
Boot is displayed in the Device Info column of the boot device, as shown in
Figure 1-27.

Figure 1-27 Setting the boot drive
9. Press Esc repeatedly to save the settings and exit the Config Utility.

problems occurs:

To roll back the firmware of an LSI SAS3008IR RAID control card, contact Huawei
technical support.

FwUpgrade

Scenarios
Procedure

Type

RAID controller
components.
NOTE
firmware package.



Guide:

verify-TL1000000054


User Guide.
Upgrade using FwUpgrade applies to the LSI SAS3008IR RAID control card only on V2 and
V3 servers.

perform a rollback.

technical support.

Smart Provisioning
Scenarios
Procedure


Type

RAID controller
components.
Smart Provisioning 1. Log in to the FusionServer Tools website.

tool package 2. Select the required version.
3. Download the required Smart Provisioning package.


Guide:

verify-TL1000000054

For details, see "Upgrading Firmware" in the Smart Provisioning User Guide.
Upgrade using smart provisioning applies to the LSI SAS3008IR RAID control card only on
V5 servers.


perform a rollback.

technical support.

SmartKit
Scenarios
Procedure
Obtain the required software packages using the methods described in Table
1-10.

Type

RAID controller
components.



Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the LSI SAS3008IR RAID control card on V2, V3, and V5
servers.

perform a rollback.

technical support.
1.4 Upgrading the LSI SAS3008IT RAID Controller Card
1.4.1 Upgrading the LSI SAS3008IT RAID Controller Card Using

FwUpgrade

Scenarios
Procedure
1-11.

Type

RAID controller
components.
NOTE
firmware package.



Guide:



verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the LSI SAS3008IT RAID control card only on V2 and
V3 servers.

perform a rollback.

To roll back the firmware of an LSI SAS3008IT RAID control card, contact Huawei
technical support.

Smart Provisioning
Scenarios
Procedure
1-12.


Type

RAID controller
components.



Guide:

verify-TL1000000054

Upgrade using smart provisioning applies to the LSI SAS3008IT RAID control card only on
V5 servers.


perform a rollback.

technical support.

SmartKit
Scenarios
Procedure
1-13.

Type

RAID controller
components.



Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the LSI SAS3008IT RAID control card on V2, V3, and V5
servers.

perform a rollback.

technical support.

FwUpgrade

Scenarios
Procedure
1-14.

Type

RAID controller
components.
NOTE
firmware package.



Guide:



verify-TL1000000054

User Guide.
servers.

perform a rollback.

----End

Smart Provisioning
Scenarios

Procedure
1-15.

Type

RAID controller
components.


Guide:
verify-TL1000000054

Upgrade using smart provisioning applies to the LSI SAS3108 RAID control card only on V5
servers.


perform a rollback.

The rollback procedure is similar to the upgrade procedure. For details, see Smart
Provisioning User Guide.
----End

SmartKit
Scenarios
Procedure
1-16.

Type

RAID controller
components.


Type



Guide:

verify-TL1000000054

Upgrade using SmartKit applies to the LSI SAS3108 RAID control card on V2, V3, and V5
servers.


perform a rollback.

----End

CLI on Linux
Scenarios
Procedure
1-17.

Type

RAID controller
components.


Type

Software and Tools.
displayed.
version.
obtained.

Guide:
verify-TL1000000054
Scenarios
Upgrade the LSI SAS3108 RAID controller card firmware using CLI on Linux.

NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Data
None
Software
example, RH2288H V3-RAID-card(BC6ESML01)-SR430C(3108)-FW-
V107(FW 4.270.00-4382).zip) to the client (a PC).
Procedure
Step 1 (Optional) Upgrade the driver of the LSI SAS3108 RAID controller card.
If the server is not installed with the LSI SAS3108 driver, the firmware cannot be
upgraded using CLI.





c. Run the cp /mnt/3008_rhel7.0_x86_x64_9.00.00.00.rpm /root command

to copy the driver upgrade file to the /root directory.

e. Run the rpm -Uvh 2208\&3108_rhel7.0_x86_x64_06.807.10.00.rpm
command to upgrade the driver of the LSI SAS3108 RAID controller card.




example, RH2288H V3-RAID-card(BC6ESML01)-SR430C(3108)-FW-
V107(FW 4.270.00-4382).zip, is decompressed.
d. Click Connect.
b. Run cp -r /mnt /root to copy the files to the /root directory.
for the files.
3. Upgrade the firmware of the RAID controller card.
Run ./storcli64 /cController_ID download file=3108FW4.rom noverchk to
command.
The firmware upgrade package contains two .rom files, 3108FW4.rom and
3108FW16.rom.
information.
– 3108FW16.rom is used to:
▪ Upgrade a RAID controller card that does not contain RAID information.
▪ Upgrade a RAID controller card in the DOS system.


b. Click Power On.
Figure 1-30 RAID controller card firmware version
version.
Figure 1-30.
● After the server reboots, use the RAID card CLI tool Storcli64 to query the
firmware version of the RAID controller card.
[root@localhost ~]# ./storcli64 /c0 show
Generating detailed summary of the adapter, it may take a while to complete.
Controller = 0
Status = Success
Description = None
Product Name = LSI MegaRAID SAS 9361-8i

Serial Number = SV332P1021
SAS Address = 500605b006decd20
PCI Address = 00:05:00:00
System Time = 12/05/2016 09:48:20
Mfg. Date = 08/07/13
Controller Time = 12/05/2016 14:48:20
FW Package Build = 24.7.0-0057
BIOS Version = 6.22.03.1_4.16.08.00_0x060B0201
FW Version = 4.270.00-4382
Driver Name = megaraid_sas
Driver Version = 06.812.07.00
Vendor Id = 0x1000
Device Id = 0x5D

SubVendor Id = 0x1000
SubDevice Id = 0x9361
Host Interface = PCI-E
Device Interface = SAS-12G
Bus Number = 5
Device Number = 0
Function Number = 0
Drive Groups = 3
......
----End

perform a rollback.

Update Procedure.
----End

CLI on VMware
Scenarios
Procedure
1-18.


Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:

verify-TL1000000054
Scenarios
Upgrade the LSI SAS3108 RAID controller card firmware using CLI on VMware.

NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Data
None
Software
You have downloaded and decompressed the firmware upgrade package (for
example, RAID card(BC6ESML01)-SR430C(3108)-FW-V110(FW
Procedure
Step 1 Install a VMware tool.
1. Obtain the VMware tool package from the official Broadcom website.
To download the VMware tool package, click Link.
2. Decompress the VMware tool package to obtain a VMware tool (for example,
vmware-esx-storcli-1.23.02.vib) from the Vmware-OP directory in
storcli_All_OS.zip, as shown in Figure 1-31.
Figure 1-31 Obtaining the VMware tool
3. Copy vmware-esx-storcli-1.23.02.vib to the /var directory in the VMware OS

by using Xftp, as shown in Figure 1-32.

Figure 1-32 Copying the tool to the VMware OS using Xftp
4. Run the Esxcli software vib install -v=/var/xxx.vib --no-sig-check command.

If "Message: Operation finished successfully" is displayed, the installation is
successful, as shown in Figure 1-33.
xxx indicates the tool package name.
Figure 1-33 Installing the tool
5. After the installation is complete, run the ./storcli /c0 show command to
query the RAID controller card firmware information in the /opt/lsi/storcli
directory, as shown in Figure 1-34.

1. Copy the firmware upgrade package RAID card(BC6ESML01)-SR430C(3108)-
FW-V110(FW 4.660.00-8270).zip to a directory in the VMware OS by using
Xftp.
2. Run the Unzip directory\xxx.zip to decompress the package, as shown in
Figure 1-35.
xxx indicates the firmware upgrade package name of the RAID controller
card.

Figure 1-35 Decompressing the firmware upgrade package
3. After decompression, run /opt/lsi/storcli/storcli /cController_IDdownload

file=3108FW4.rom noverchk to upgrade the firmware.
If "Status = Success" is displayed, the upgrade is successful, as shown in
Figure 1-36.
Controller_ID indicates the ID of the RAID controller card. To configure
multiple RAID controller cards, change the controller IDs in the command.
Figure 1-36 Upgrading the firmware

b. Click Power On.
version.
Figure 1-37.

● After the server reboots, use the RAID card CLI tool storcli to query the
firmware version of the RAID controller card, as shown in Figure 1-38.
----End

perform a rollback.

Update Procedure.
----End

CLI on Windows

Scenarios
Procedure
1-19.

Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:


verify-TL1000000054
Scenarios
Upgrade the LSI SAS3108 RAID controller card firmware using CLI on Windows.
This section uses Windows Server 2012 R2 as an example.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Software
example, RAID-card(BC6ESML01)-SR430C(3108)-FW-V110(FW
Procedure
Step 1 (Optional) Query the BDF of RAID controller cards.
Run the .\storcli64.exe show command on the OS CLI. The command output
displays information about the RAID controller cards from the top to the
bottom according to their locations in the server.
Ct1 0 corresponds to the controller whose address is c0.

Step 2 (Optional) Upgrade the driver of the LSI SAS3108 RAID controller card.

Figure 1-39 Virtual drive

d. Select an image (for example, onboard_driver_rhel7.0.iso), and click
Connect.
2. Install the RAID controller card driver.
a. Choose Start > Server Manager.
b. In the Server Manager window, choose Tools > Computer
Management.
The Computer Management window is displayed, as shown in Figure
1-40.

Figure 1-40 Computer Management
c. Choose Device Manager > WIN-V5HKO9410BQ > Storage controllers >

SAS3108, and press Enter.
The SAS3108 Properties dialog box is displayed, as shown in Figure
1-41.
Figure 1-41 SAS3108 Properties

d. Click Update Driver....

The Update Driver Software - SAS3108 dialog box is displayed.
e. Click Browse my computer for driver software.
f. Select the path where the driver package is stored, and click Next.
When the driver upgrade is complete, the dialog box shown in Figure
1-42 is displayed.
Figure 1-42 Driver upgrade completed
g. Reboot the server.

1. Launch the OS PowerShell.
2. Run the cd .\Desktop command to go to the directory where storcli64.exe is
stored.
3. Run the .\storcli64.exe /c0/v1 show all command to query RAID array
information.
Key parameters in the command output are as follows:
– TYPE: RAID level
– State: RAID array state
– Cache: RAID array read/write policy
– PDs for VD 1: hard drives that constitute the RAID array
– Strip Properties: strip size of the RAID array

Figure 1-43 Querying RAID array information
4. Run the .\storcli64.exe /c0 show bootdrive command to check whether the
RAID array has been set as the boot drive.
The command output shown in Figure 1-44 indicates that the boot drive is
VD:1.
Figure 1-44 Querying the boot drive
5. Run the .\storcli64.exe /c0 show command to query RAID array information.
In the command output, FW version indicates the firmware version of the
RAID controller card.

Figure 1-45 Querying RAID array information
6. Run the .\storcli64.exe /c0/eall/sall show command to query hard drive

information.
Run the ./storcli64.exe /CController_ID download file=3108FW4.com noverchk

command to upgrade the firmware.
In the command, Controller_ID indicates the ID of the RAID controller card. To
configure multiple RAID controller cards, change the controller IDs in the
command.

The firmware upgrade package contains two .rom files, 3108FW4.rom and 3108FW16.rom.
● 3108FW4.rom is used to upgrade a RAID controller card that contains RAID
information.
● 3108FW16.rom is used to:
– Upgrade a RAID controller card that does not contain RAID information.
– Upgrade a RAID controller card in the DOS system.
Step 5 Restart the server for the new firmware to take effect.
1. Click on the toolbar. Click Power Off.

2. Click Power On.
information.
before the upgrade.
----End

perform a rollback.

Update Procedure.
----End

1.6 Upgrading the Avago SAS3004iMR RAID Controller

Card
1.6.1 Upgrading the Avago SAS3004iMR RAID Controller Card

Using CLI
Scenarios
Procedure
1-20.

Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:
verify-TL1000000054
Scenarios
Upgrade the Avago SAS3004iMR RAID controller card firmware using CLI.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the Avago SAS3004iMR RAID controller card is powered
on.
Software
example, xxx-Rhel-Driver-V106) to the client (a PC) and obtained the driver
image (for example, 3004_rhel5.10_x86_64_07.703.05.00.iso).
example, xxx-RAID-card(BC6ESML01)-SR230-M(3004)-FW-V107(FW

● The Storcli tool has been installed in the OS.
Procedure
Step 1 (Optional) Upgrade the driver of the Avago SAS3004iMR RAID controller card.
If the server is not installed with the Avago SAS3004iMR driver, the firmware
cannot be upgraded using CLI.

c. Click the Image File option button, and then click Browse.
d. Select the image (for example, 3004_rhel5.10_x86_64_07.703.05.00.iso),
and click Connect in the screen shown in Figure 1-46.

megaraid_sas-07.703.05.00_el6.7-1.x86_64.rpm /root command to copy
the firmware upgrade file to the /root directory.

megaraid_sas-07.703.05.00_el6.7-1.x86_64.rpm command to upgrade
the driver of the Avago SAS3004iMR RAID controller card.
If the file name or directory contains special characters of Shell commands, add \
before each special character to turn it into a common one.


b. Click the Image File option button, and then click Browse.
c. Select the package obtained after the firmware upgrade package is
decompressed (for example, xxx-RAID-card(BC6ESML01)-SR230-
M(3004)-FW-V107(FW 4.680.01-8298).zip).
d. Click Connect.
d. Run chmod 777 * to add read and write permissions for the files.
a. Run the ./storcli64 /cController_ID download file=3004FW4.rom
noverchk command to upgrade the firmware.
In the command, Controller_ID indicates the ID of the RAID controller
card. To configure multiple RAID controller cards, change the controller
IDs in the command.
3004FW16.rom.
▪ 3004FW4.rom is used for upgrading the RAID controller card online.
▪ 3004FW16.rom is used for burning during production.

4. Reboot the server for the new firmware to take effect.

– In legacy mode, run the reboot command to reboot the server.
During the reboot process, the RAID controller card firmware information
is displayed, as shown in Figure 1-48.
Figure 1-48 RAID controller card firmware version - legacy
– In UEFI mode, click Power Off and then click Power On to reboot the
server.
▪ During the reboot process, the RAID controller card firmware

information is displayed.
▪ Press F11 when prompted, select Device Manager > AVAGO

MegaRAID<SAS3004–iMR>Configuration Utility-03.25.05.04 >
Main Menu > Controller Management.
The firmware information is displayed, as shown in Figure 1-49.
Figure 1-49 RAID controller card firmware version - UEFI

version.
Figure 1-48 and Figure 1-49.
● After the server reboots, use the RAID card CLI tool Storcli64 to query the
Figure 1-50 Querying RAID controller card firmware version information
----End

perform a rollback.


Update Procedure.
----End

Using SmartKit
Scenarios
Procedure
1-21.

Type

RAID controller
components.



Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the Avago SAS3004iMR RAID control card only on V5
servers.

perform a rollback.

----End

Card


Using Smart Provisioning
Scenarios
Procedure
1-22.

Type

RAID controller
components.


Guide:


verify-TL1000000054

Upgrade using smart provisioning applies to the LSI SAS3408iMR RAID control card only on
V5 servers.

perform a rollback.

----End

Using SmartKit
Scenarios
Procedure
1-23.


Type

RAID controller
components.


Guide:
verify-TL1000000054

servers.


perform a rollback.

----End

Using CLI
Scenarios
Upgrade the Avago SAS3408 RAID controller card firmware using CLI. Note that
the firmware upgrade of Avago SAS3408 can be performed only in UEFI mode, but
not legacy mode.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the Avago SAS3408 RAID controller card is powered on.
Software
● You have downloaded the OS driver package to a client (a PC) and obtained
the driver image.
example, 1288H V5 -xxx.zip) to the client (a PC).
● The Storcli tool has been installed in the OS.

Procedure
their BDF.

– If the server is equipped with multiple RAID IMR cards or RAID MR cards,
run the lspci |grep –i raid command on the OS CLI. The command
output displays information about the RAID controller cards according to
their locations in the server.
▪ BDF 1d:00.0 corresponds to the controller whose address is c0.
▪ BDF 5e:00.0 corresponds to the controller whose address is c1.
▪ BDF b2:00.0 corresponds to the controller whose address is c2.

– If the server is equipped with multiple RAID IT cards, run the storcli64
show all command on the OS CLI. The command output displays
information about the RAID controller cards from the top to the bottom
according to their locations in the server.
▪ BDF SAS3408 corresponds to the controller whose address is c0.
▪ BDF SAS3416IT corresponds to the controller whose address is c1.
Step 2 Install the driver of the Avago SAS3408 RAID controller card.

Install the driver of the Avago SAS3408 RAID controller card when you install the
OS. For details, see Installing an OS by Loading a RAID Controller Card Driver
in the Huawei Server OS Installation Guide.
Step 3 (Optional) Upgrade the driver of the Avago SAS3408 RAID controller card.


d. Select an image, and click Connect.


the driver of the Avago SAS3408 RAID controller card.



a. Use the SFTP tool to upload the firmware upgrade package of the RAID
controller card to the /root directory of the server.
b. Run the cd /root command to go to the /root directory.
c. Run chmod 777 * to add read and write permissions for the files.
Run the ./storcli64 /cController_ID download
file=HuaWei_SAS3408_nopad.rom noverchk command to upgrade the
firmware.
command.
The firmware upgrade package contains two .rom files, HuaWei_SAS3408_32MB.rom

and HuaWei_SAS3408_nopad.rom.
– If you are upgrading the firmware online, use HuaWei_SAS3408_nopad.rom.
– If you are programming the firmware of the RAID controller card using EFI Shell,
use HuaWei_SAS3408_32MB.rom or HuaWei_SAS3408_nopad.rom.
a. Run the reboot command to reboot the server. During the reboot
process, the RAID controller card firmware information is displayed.
b. Press F11, select Device Management, select the Avago SAS3408 RAID
controller card, and press Enter. The firmware information is displayed,
as shown in Figure 1-52.

version.
● View the firmware version during the server startup process, as shown Figure
1-52.
● After the server reboots, use the RAID card CLI tool storcli64 to query the

----End
Scenarios
Procedure
1-24.

Type

RAID controller
components.


Type

Software and Tools.
displayed.
version.
obtained.

Guide:
verify-TL1000000054
Scenarios
Upgrade the Avago SAS3408 RAID controller card firmware using CLI. Note that
the firmware upgrade of Avago SAS3408 can be performed only in UEFI mode, but
not legacy mode.

NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Software
the driver image.
Procedure
their BDF.

run the lspci |grep -i raid command on the OS CLI. The command output
displays information about the RAID controller cards according to their
locations in the server.


▪ BDF SAS3416IT corresponds to the controller whose address is c1.







firmware.
command.


– If you are upgrading the firmware online, use HuaWei_SAS3408_nopad.rom.

b. Click Power On.
– During the reboot process, the RAID controller card firmware information
is displayed.
– Press F11, select Device Management, select the Avago SAS3408 RAID
version.
Figure 1-55.

----End

perform a rollback.

Update Procedure.
----End


Card

Scenarios
Procedure
1-25.

Type

RAID controller
components.




Guide:

verify-TL1000000054

Upgrade using smart provisioning applies to the LSI SAS3416iMR RAID control card only on
V5 servers.

perform a rollback.

----End

Using SmartKit

Scenarios
Procedure
1-26.

Type

RAID controller
components.


Guide:
verify-TL1000000054


servers.

perform a rollback.

----End

Using CLI
Scenarios
Procedure
1-27.


Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:

verify-TL1000000054
Scenarios
Upgrade the Avago SAS3416iMR RAID controller card firmware using CLI.

NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the Avago SAS3416iMR RAID controller card is powered
on.
Software
the driver image.
Procedure
their BDF.

displays information about the RAID controller cards according to their
locations in the server.


▪ BDF SAS3416-IT corresponds to the controller whose address is c1.
Step 2 Install the driver of the Avago SAS3416iMR RAID controller card.
Install the driver of the Avago SAS3416iMR RAID controller card when you install
the OS. For details, see Installing an OS by Loading a RAID Controller Card
Driver in the Huawei Server OS Installation Guide.
Step 3 (Optional) Upgrade the driver of the Avago SAS3416iMR RAID controller card.





the driver of the Avago SAS3416iMR RAID controller card.


c. Run the mkdir test command to create the test folder.
d. Run cp /mnt/* /root/test to copy the files to the /root/test directory.
e. Run the cd test/ command to go to the /test directory, and run the ls
command to display all the files in the directory.

firmware.
In the command, Controller_ID indicates the ID of a hard drive controller. To
configure multiple hard drive controllers, change the controller IDs in the
command.


b. Click Power On.
is displayed.
– Press F11, select Device Management, select the Avago SAS3416iMR
RAID controller card, and press Enter. The firmware information is
version.
● View the firmware version during the server startup process, as shown Figure
1-58.

----End

perform a rollback.

Update Procedure.
----End

1.9 Upgrading the Avago SAS3416IT RAID Controller

Card
1.9.1 Upgrading the Avago SAS3416IT RAID Controller Card

Scenarios
Procedure
1-28.

Type

RAID controller
components.




Guide:

verify-TL1000000054

Upgrade using smart provisioning applies to the LSI SAS3416IT RAID control card only on
V5 servers.

perform a rollback.

----End

Using SmartKit

Scenarios
Procedure
1-29.

Type

RAID controller
components.


Guide:
verify-TL1000000054


Upgrade using SmartKit applies to the Avago SAS3416IT RAID control card only on V5
servers.

perform a rollback.

----End

Using CLI
Scenarios
Procedure
1-30.


Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:

verify-TL1000000054
Scenarios
Upgrade the Avago SAS3416IT RAID controller card firmware using CLI.

NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the Avago SAS3416IT RAID controller card is powered on.
Software
the driver image.
Procedure
their BDF.

displays information about the RAID controller cards from the top to the
bottom according to their locations in the server.


▪ BDF SAS3416-IT corresponds to the controller whose address is c1.
Step 2 Install the driver of the Avago SAS3416IT RAID controller card.
Install the driver of the Avago SAS3416IT RAID controller card when you install
the OS. For details, see Installing an OS by Loading a RAID Controller Card
Driver in the Huawei Server OS Installation Guide.
Step 3 (Optional) Upgrade the driver of the Avago SAS3416IT RAID controller card.



c. Run the cp /mnt/kmod-mpt3sas-22.00.00.00_e17.2–1.x86_64.rpm /root

command to copy the driver upgrade file to the /root directory.

e. Run the rpm -Uvh kmod-mpt3sas-22.00.00.00_e17.2–1.x86_64.rpm
command to upgrade the driver of the Avago SAS3416IT RAID controller
card.

d. Run cp /mnt/* /root/test to copy the files to the /root/test directory.
e. Run the cd /root/test command to go to the /test directory, and run the

a. Run the ./storcli64 /cController_ID download bios
file=mpt35sas_legacy.rom command to upgrade the firmware.
b. Run the ./storcli64 /cController_ID download file=3416IT.rom noverchk

c. Run the ./storcli64 /cController_ID download efibios

file=mpt35sas_x64.rom command to upgrade the firmware.
In the command, Controller_ID indicates the ID of the RAID controller
card. To configure multiple RAID controller cards, change the controller
IDs in the command.

– If you are upgrading the firmware online on the OS, use
HuaWei_SAS3416_nopad.rom.

b. Click Power On.
is displayed.
– Press F11, select Device Management, select the Avago SAS3416IT RAID
version.

Figure 1-61.
----End

perform a rollback.


Update Procedure.
----End
1.10 Upgrading the Avago SAS3508 RAID Controller

Card
1.10.1 Upgrading the Avago SAS3508 RAID Controller Card

Scenarios
Procedure
1-31.

Type

RAID controller
components.



Guide:
verify-TL1000000054

Upgrade using smart provisioning applies to the Avago SAS3508 RAID control card only on
V5 servers.

perform a rollback.

----End


Using SmartKit
Scenarios
Procedure
1-32.

Type

RAID controller
components.


Guide:


verify-TL1000000054

Upgrade using SmartKit applies to the Avago SAS3508 RAID control card only on V5
servers.

perform a rollback.

----End

Using CLI
Scenarios

Procedure
1-33.

Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:

verify-TL1000000054

Scenarios
Upgrade the Avago SAS3508 RAID controller card firmware using CLI.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Software
the driver image.
example, RH2288H V3 -RAID-card(BC1RLCB02)-SR450C(3508)-FW-
V106(FW 5.010.00-0755).zip) to the client (a PC).
Procedure
Step 1 (Optional) On the OS CLI, run the storcli64 show all command to query the RAID
controller card ID.

● If the server is configured with multiple RAID controller cards, perform this step to query
the ID of each RAID controller card.
● Ctl indicates the ID of each RAID controller card.


a. On the OS CLI, run the mount /dev/sr0 /mnt command.
The image is mounted to the /mnt directory.

d. Run the cd /root command.



b. Run the cd /root command.
Run the ./storcli64 /cController_ID download file=3508FW4.rom noverchk
command.
3508FW16.rom.
– If you are upgrading the firmware online on the OS, use 3508FW4.rom.
use 3508FW4.rom or 3508FW16.rom.

b. Click Power On.
displayed.

– If the boot type of the BIOS is UEFI, press F11, select Device
Management, select the Avago SAS3508 RAID controller card, and press
Enter. The firmware information is displayed, as shown in Figure 1-64.
– If the boot type of the BIOS is legacy, the firmware information is directly
Figure 1-64 RAID controller card firmware version - UEFI
Figure 1-65 RAID controller card firmware version - legacy
version.

● View the firmware version during server startup.

If the boot type of the BIOS is UEFI, the firmware information is shown in
Figure 1-64.
If the boot type of the BIOS is legacy, the firmware information is shown in
Figure 1-65.
[root@localhost ~]# ./storcli64 /c0 show
Generating detailed summary of the adapter, it may take a while to complete.
Controller = 0
Status = Success
Description = None
Product Name = SAS3508

Serial Number = FW-00000000
SAS Address = 5000000012345678
PCI Address = 00:1b:00:00
System Time = 11/14/2016 00:10:45
Mfg. Date = 00/00/00
Controller Time = 11/13/2016 16:10:45
FW Package Build = 50.1.0-0537
BIOS Version = 07.01.05.1_4.17.08.00_0x07010701
FW Version = 5.010.00-0755
Driver Name = megaraid_sas
Driver Version = 07.701.17.00
Current Personality = RAID-Mode
Vendor Id = 0x1000
Device Id = 0x16
SubVendor Id = 0x19E5
SubDevice Id = 0xD215
Host Interface = PCI-E
Device Interface = SAS-12G
Bus Number = 27
Device Number = 0
Function Number = 0
......
----End

perform a rollback.


1.10.3.2 Update Procedure.
----End
1.11 Upgrading the Avago SAS3516 RAID Controller

Card

Upgrade the firmware following instructions in Smart Provisioning User Guide.
V5 servers.
Scenarios
Procedure
1-34.

Type

RAID controller
components.



Guide:
verify-TL1000000054

V5 servers.

perform a rollback.

----End


Using SmartKit
Scenarios
Procedure
1-35.

Type

RAID controller
components.


Guide:


verify-TL1000000054

Upgrade using SmartKit applies to the Avago SAS3516 RAID control card only on V5
servers.

perform a rollback.

----End

Using CLI
Scenarios

Procedure
1-36.

Type

RAID controller
components.

Software and Tools.
displayed.
version.
obtained.


Guide:

verify-TL1000000054

Scenarios
Upgrade the Avago SAS3516 RAID controller card firmware using CLI on Linux.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
Data
None
Software
FusionServer iDriver-RHEL7.3-Driver-V008.zip) to the client (a PC) and
obtained the driver image (for example, onboard_driver_citrix7.3.iso).
example, RAID-SP460C-M-3516-FW-5.030.00-1280.zip) to the client (a PC).
Procedure
controller card ID.

Step 2 (Optional) Install the driver of the Avago SAS3516 RAID controller card.




the driver of the LSI SAS3108 RAID controller card.




example, RAID-SP460C-M-3516-FW-5.030.00-1280.zip, is decompressed.
d. Click Connect.
b. Run cp /mnt /* /root/ -r to copy the files to the /root directory.
for the files.
1. Run the ./storcli64 /c0 show command to query RAID controller card and
hard drive information. See Figure 1-68 and Figure 1-69.

Figure 1-68 Querying RAID controller card information
Figure 1-69 Querying hard drive information
2. Run the ./storcli64 /c0/vall show all command to query RAID array
information.
a. View RAID array information. As shown in Figure5 Viewing RAID array
information, TYPE indicates the RAID array level; State indicates the
RAID array status; Access indicates the read/write policy.
Figure 1-70 Viewing RAID array information
b. View hard drive locations. As shown in Figure 1-71, EID:SIt indicates hard
drive backplane ID:hard drive slot ID.

Figure 1-71 Viewing hard drive locations
c. View the strip size. As shown in Figure 1-72, Strip Size indicates the strip
size of the RAID array.
Figure 1-72 Viewing the strip size
1. Run ./storcli64 /cController_ID download file=/root/3516FW4.rom noverchk

to upgrade the firmware.
command.

3516FW16.rom.
information.
– 3516FW16.rom is used for burning during production.

b. Click Power On.
information.
before the upgrade.
Step 7 (Optional) Modify the Profile ID.
If the firmware version is 5.050.00-1933 or later, run ./storcli64 /c0 set profile
profileid=13 to modify the Profile ID.
----End

perform a rollback.


----End
1.12 Upgrading the MSCC SmartRAID 3152-8i RAID

Controller Card
1.12.1 Upgrading the MSCC SmartRAID 3152-8i RAID

Controller Card Using CLI
1.12.1.1 Before You Start
Upgrade Scope
Use the Intelligent Computing Compatibility Checker to obtain information
about the servers supported by the MSCC SmartRAID 3152-8i RAID controller card.
You are advised to download and install the driver matching the OS to prevent
compatibility issues.
Impact of the Upgrade

After the upgrade, restart the server for the latest firmware version to take effect.
The restart will interrupt services.
Precautions
Observe the precautions listed in Table 1-37 during the upgrade.
Table 1-37 Precautions for the upgrade
No. Description
1 Misoperations during the upgrade of the firmware may make the

RAID controller card unavailable due to misoperations.
2 Stop running services on the server before the upgrade.
3 Do not power off the OS during the upgrade and do not change
configurations except for those involved in the upgrade guide.

No. Description
4 Before the upgrade, read this document carefully to ensure that

you have learned all the content. For any problems or suggestions
pertaining to the document, contact Huawei technical support.
1.12.1.2 Preparations
Scenarios
Obtain the software packages required for the upgrade.
Procedure
1-38.
Table 1-38 Obtaining software packages
Software Package How to Obtain
Firmware upgrade package of 1. Visit FusionServer iDriver.

the RAID controller card 2. Select the latest version.
The software list is displayed.
3. Download the firmware upgrade package
(for example, RAID-SmartRAID-
PMC3152-8i-PM8204-FW-1.61[0].zip) of
the MSCC SmartRAID 3152-8i RAID
controller card to the local PC and
decompress the package.
NOTE
Download the current version and target version
of the RAID controller card firmware in the same
way.



Guide:

verify-TL1000000054
1.12.1.3 Upgrade
Scenarios
Upgrade the MSCC SmartRAID 3152-8i RAID controller card firmware using a CLI
tool on the OS.
Prerequisites
● You have backed up the data and programs on the server.
● You have downloaded the RAID controller card firmware upgrade package
(for example, RAID-SmartRAID-PMC3152-8i-PM8204-FW-1.61[0].zip) to
the client (for example, a PC) and decompressed the package.
● You have powered on the server hosting the MSCC SmartRAID 3152-8i RAID
controller card.
Procedure
The iBMC remote virtual console includes the Java remote virtual console and HTML5
integrated remote console. The HTML5 integrated remote console does not support a local
directory. This section uses the Java console as an example. For more information, see
Huawei Server iBMC User Guide.
1. On the toolbar of the virtual console, click to display the screen shown in
Figure 1-73.
Figure 1-73 Virtual DVD drive
2. Select Directory and click Browse.

3. Select the folder generated after the RAID controller card firmware upgrade
package is decompressed.

Select the folder of the target version for an upgrade and the folder of the source
version for a rollback.
4. Click Connect.
If the Eject icon is available, as shown in Figure 1-74, the upgrade file is
successfully mounted.
Figure 1-74 Toolbar
Step 2 Download ARCCONF.

1. Log in to the Microsemi website and download ARCCONF.
– For a VMware OS, click here to obtain ARCCONF.
– For other OSs, click here to obtain ARCCONF.
2. Click .
3. Download ARCCONF as instructed.
4. Decompress the downloaded package to obtain the tools for different OSs.
ARCCONF for the VMware OS is in the cim directory.
Step 3 Install ARCCONF.
The ARCCONF installation method varies depending on the OS type. The following
uses Windows and Linux as examples to describe how to install ARCCONF. For
details about the installation procedures for other OSs, see the ARCCONF user
guide at Microsemi website.
● Installing ARCCONF on Windows

a. Upload the tool package for Windows to the server OS.
b. Open the command line utility.
c. Switch to the directory where the ARCCONF tool package is located.
ARCCONF can be used without installation.
● Installing ARCCONF on Linux
a. Use a file transfer tool (such as WinSCP) to upload the tool for Linux to
the server OS.
b. Run the rpm -ivh Arcconf-xxx.rpm command to install ARCCONF.
You can use ARCCONF to manage RAID controller cards after the
installation is complete.
● Installing ARCCONF on VMware

a. Use a file transfer tool (such as PuTTY) to upload the package applicable
to VMware to the /temp directory on the server OS.
b. Run the esxcli software vib install -v=/temp/vmware-esx-provider-
arcconf.vib command on the VMware CLI to install ARCCONF. /temp/
vmware-esx-provider-arcconf.vib must be the full path of the ARCCONF
tool file. You can use ARCCONF to manage RAID controller cards after
the installation is complete.
The ARCCONF installation directory is /opt/pmc. You need to access the directory
and run RAID card commands.
Step 4 Copy the upgrade package to the server.

1. On Linux, run the mkdir fw command to create the fw folder in the root
directory.
2. Run the mount /dev/sr0 /mnt command to mount the local folder to
the /mnt directory.
After you enter mount /dev/sr, press Tab to display the value following sr.
3. Run the cd /mnt command to go to the /mnt directory.
4. Run the cp * -R /root/fw/ command to copy the files in the mounted local
folder to the fw directory.
5. Run the cd /root/fw/ command to go to the fw directory.
6. Run the chmod 777 * command to add read and write permissions for the
firmware upgrade package.
Step 5 Run the arcconf list command to query the controller ID of the current RAID
controller card.
Step 6 Run the arcconf romupdate Controller_ID XXX.bin noprompt command to

● Controller_ID indicates the controller ID of the RAID controller card obtained in Step 5,
that is, the value of Controller ID in Figure 1-75.
Figure 1-75 Command output
● The command is executed successfully if "Command completed successfully" is

displayed.
Step 7 Run the reboot command to restart the server for the firmware to take effect.
The restart process takes 5 to 10 minutes.
Step 8 Check whether the firmware version is the target version.
If no error message is displayed during the firmware upgrade and the version of the
upgraded firmware is the target version, the firmware is successfully upgraded.
----End
1.12.1.4 Rollback
1.12.1.4.1 Rollback Guidelines

● A rollback is required in any of the following cases:
– A major fault occurred during the upgrade, and cannot be located and
rectified within the specified time.
– The entire upgrade cannot be finished as scheduled. To prevent service
interruption in business hours caused by the upgrade, a rollback is
required.
– The upgrade is successful. However, services or the OS is abnormal after
the restart, and the new version functions abnormally.
● If the version upgrade fails and the software version is still the source version,
you do not need to perform a rollback.


The rollback procedure is the same as the upgrade procedure. For details, see Step
4 to Step 7 in 1.12.1.3 Upgrade.
If no error message is displayed during the rollback and the version number is the source
version, the rollback is successful.
----End
1.13 Upgrading the MSCC SmartHBA 2100-8i RAID

Controller Card
1.13.1 Upgrading the MSCC SmartHBA 2100-8i RAID

Controller Card Using CLI
Upgrade Scope
Use the Intelligent Computing Compatibility Checker to obtain information
about the servers supported by the MSCC SmartHBA 2100-8i RAID controller card.
You are advised to download and install the driver matching the OS to prevent
compatibility issues.
Impact of the Upgrade

After the upgrade, restart the server for the latest firmware version to take effect.
The restart will interrupt services.
Precautions
Observe the precautions listed in Table 1-39 during the upgrade.
Table 1-39 Precautions for the upgrade
No. Description
1 Misoperations during the upgrade of the firmware may make the

RAID controller card unavailable due to misoperations.
2 Stop running services on the server before the upgrade.

No. Description
3 Do not power off the OS during the upgrade and do not change
configurations except for those involved in the upgrade guide.
4 Before the upgrade, read this document carefully to ensure that

you have learned all the content. For any problems or suggestions
pertaining to the document, contact Huawei technical support.
1.13.1.2 Preparations
Scenarios
Obtain the software packages required for the upgrade.
Procedure
1-40.
Table 1-40 Obtaining software packages
Software Package How to Obtain
Firmware upgrade package of 1. Visit FusionServer iDriver.

the RAID controller card 2. Select the latest version.
The software list is displayed.
3. Download the firmware upgrade package
(for example, RAID-SmartHBA-
PMC2100-8i-PM8222-FW-1.61[0].zip) of
the MSCC SmartHBA 2100-8i RAID
controller card to the local PC and
decompress the package.
NOTE
Download the current version and target version
of the RAID controller card firmware in the same
way.


Guide:
verify-TL1000000054
1.13.1.3 Upgrade
Scenarios
Upgrade the MSCC SmartHBA 2100-8i RAID controller card firmware using a CLI
tool on the OS.
Prerequisites
● You have backed up the data and programs on the server.
● You have downloaded the RAID controller card firmware upgrade package
(for example, RAID-SmartHBA-PMC2100-8i-PM8222-FW-1.61[0].zip) to the
client (for example, a PC) and decompressed the package.
● You have powered on the server hosting the MSCC SmartHBA 2100-8i RAID
controller card.
Procedure
The iBMC remote virtual console includes the Java remote virtual console and HTML5
integrated remote console. The HTML5 integrated remote console does not support a local
directory. This section uses the Java console as an example. For more information, see
Huawei Server iBMC User Guide.
1. On the toolbar of the virtual console, click to display the screen shown in
Figure 1-76.
Figure 1-76 Virtual DVD drive
2. Select Directory and click Browse.

3. Select the folder generated after the RAID controller card firmware upgrade
package is decompressed.

Select the folder of the target version for an upgrade and the folder of the source
version for a rollback.
4. Click Connect.
If the Eject icon is available, as shown in Figure 1-77, the upgrade file is
successfully mounted.
Figure 1-77 Toolbar
Step 2 Download ARCCONF.

1. Log in to the Microsemi website and download ARCCONF.
– For a VMware OS, click here to obtain ARCCONF.
– For other OSs, click here to obtain ARCCONF.
2. Click .
3. Download ARCCONF as instructed.
4. Decompress the downloaded package to obtain the tools for different OSs.
ARCCONF for the VMware OS is in the cim directory.
Step 3 Install ARCCONF.
The ARCCONF installation method varies depending on the OS type. The following
uses Windows and Linux as examples to describe how to install ARCCONF. For
details about the installation procedures for other OSs, see the ARCCONF user
guide at Microsemi website.
● Installing ARCCONF on Windows

a. Upload the tool package for Windows to the server OS.
b. Open the command line utility.
c. Switch to the directory where the ARCCONF tool package is located.
ARCCONF can be used without installation.
● Installing ARCCONF on Linux
a. Use a file transfer tool (such as WinSCP) to upload the tool for Linux to
the server OS.
b. Run the rpm -ivh Arcconf-xxx.rpm command to install ARCCONF.
You can use ARCCONF to manage RAID controller cards after the
installation is complete.
● Installing ARCCONF on VMware

a. Use a file transfer tool (such as PuTTY) to upload the package applicable
to VMware to the /temp directory on the server OS.
b. Run the esxcli software vib install -v=/temp/vmware-esx-provider-
arcconf.vib command on the VMware CLI to install ARCCONF. /temp/
vmware-esx-provider-arcconf.vib must be the full path of the ARCCONF
tool file. You can use ARCCONF to manage RAID controller cards after
the installation is complete.
The ARCCONF installation directory is /opt/pmc. You need to access the directory
and run RAID card commands.
Step 4 Copy the upgrade package to the server.

1. On Linux, run the mkdir fw command to create the fw folder in the root
directory.
2. Run the mount /dev/sr0 /mnt command to mount the local folder to
the /mnt directory.
After you enter mount /dev/sr, press Tab to display the value following sr.
3. Run the cd /mnt command to go to the /mnt directory.
4. Run the cp * -R /root/fw/ command to copy the files in the mounted local
folder to the fw directory.
5. Run the cd /root/fw/ command to go to the fw directory.
6. Run the chmod 777 * command to add read and write permissions for the
firmware upgrade package.
Step 5 Run the arcconf list command to query the controller ID of the current RAID
controller card.
Step 6 Run the arcconf romupdate Controller_ID XXX.bin noprompt command to

● Controller_ID indicates the controller ID of the RAID controller card obtained in Step 5,
that is, the value of Controller ID in Figure 1-78.
Figure 1-78 Command output
● The command is executed successfully if "Command completed successfully" is

displayed.
Step 7 Run the reboot command to restart the server for the firmware to take effect.
The restart process takes 5 to 10 minutes.
----End
1.13.1.4 Rollback
1.13.1.4.1 Rollback Guidelines

● A rollback is required in any of the following cases:
– A major fault occurred during the upgrade, and cannot be located and
rectified within the specified time.
– The entire upgrade cannot be finished as scheduled. To prevent service
interruption in business hours caused by the upgrade, a rollback is
required.
– The upgrade is successful. However, services or the OS is abnormal after
the restart, and the new version functions abnormally.
● If the version upgrade fails and the software version is still the source version,
you do not need to perform a rollback.


The rollback procedure is the same as the upgrade procedure. For details, see Step
4 to Step 7 in 1.13.1.3 Upgrade.
If no error message is displayed during the rollback and the version number is the source
version, the rollback is successful.
----End
1.14 Upgrading the PM8060 RAID Controller Card

Using CLI
1.14.1 Preparing for the Upgrade
1.14.1.1 Obtaining Software Packages
Scenarios
Procedure
1-41.

Type

RAID controller
components.
Management tool 1. Go to the controller card page at the Microsemi

of the RAID website.
controller card 2. Click Microsemi Adaptec ARCCONF Command Line
Utility vxxx on the download list.
Download ARCCONF when prompted.
3. Decompress the downloaded file to obtain the tool
packages for different operating systems (OSs).

1.14.1.2 Verifying the Software Package Integrity
Scenarios
Verify the software package integrity before the upgrade.
Procedure
Step 1 Click to download the digital software certificate, and click to download the
software.
To obtain the verification tool and guide, click Software digital signature
(OpenPGP) validation tool.
----End
1.14.2 Update Procedure
Scenarios
Upgrade the firmware of the PM8060 RAID controller card using CLI.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the PM8060 RAID controller card is powered on.
Software
FusionServer iDriver-Rhel-Driver-V307) to the client (a PC) and obtained the
driver image (for example, onboard_driver_rhel7.0.iso).
example, FusionServer-RAID-card(IT21ITRA)-SP245(8060)-Firmware-
V101(32971).zip) to the client (a PC).
Procedure
Step 1 (Optional) Upgrade the driver of the PM8060 RAID controller card.

If the server is not installed with the PM8060 driver, the firmware cannot be
upgraded using CLI.


c. Run the cp /mnt/8060_rhel7.0_x86_x64_1.2.1-41043.rpm /root

d. Run the cd /root command to switch to the /root directory.
e. Run the rpm -ivh 8060_rhel7.0_x86_x64_1.2.1-41043.rpm command to
upgrade the driver of the PM8060 RAID controller card.





decompressed (for example, FusionServer-RAID-card(IT21ITRA)-
SP245(8060)-Firmware-V101(32971).zip).
d. Click Connect.
The local directory is mounted to the /mnt directory.
c. Run the cd /root command.
for the files.
a. Run ./update.sh to upgrade the RAID controller card firmware.
The server automatically reboots for the new firmware to take effect.

version.
Figure 1-81.
● After the server reboots, use the RAID card CLI tool arcconf to query the
[root@localhost ~]# ./arcconf getconfig 1
...... --------------------------------------------------------
Controller Version Information
--------------------------------------------------------
BIOS : 7.8-0 (32971)
Firmware : 7.8-0 (32971)
Driver : 1.2-1 (50663)
Boot Flash : 7.8-0 (32971)
CPLD (Load version/ Flash version) : 8/ 8
SEEPROM (Load version/ Flash version) : 1/ 1
FCT Custom Init String Version : 0x0
--------------------------------------------------------
Controller Cache Backup Unit Information
--------------------------------------------------------
......
----End
1.14.3 Rolling Back the Firmware Version
1.14.3.1 Rollback Rules

perform a rollback.
1.14.3.2 Rollback Procedure

The rollback procedure is similar to the upgrade procedure. For details, see 1.14.2
Update Procedure.
----End

1.15 Upgrading the PM8068 RAID Controller Card

Using CLI
1.15.1 Preparing for the Upgrade
1.15.1.1 Obtaining Software Packages
Scenarios
Procedure
1-42.

Type

RAID controller
components.
Management tool 1. Go to the controller card page at the Microsemi

of the RAID website.
controller card 2. Click Microsemi Adaptec ARCCONF Command Line
Utility vxxx on the download list.
Download ARCCONF when prompted.
3. Decompress the downloaded file to obtain the tool
packages for different operating systems (OSs).
1.15.1.2 Verifying the Software Package Integrity
Scenarios
Verify the software package integrity before the upgrade.
Procedure
Step 1 Click to download the digital software certificate, and click to download the
software.

To obtain the verification tool and guide, click Software digital signature
(OpenPGP) validation tool.
----End
1.15.2 Update Procedure

Scenarios
Upgrade the firmware of the PM8068 RAID controller card using CLI.
NOTICE
fail.
upgrade guide.
Prerequisites
Conditions
● The server hosting the PM8068 RAID controller card is powered on.
Software
FusionServer iDriver-Rhel-Driver-V307) to the client (a PC) and obtained the
driver image (for example, onboard_driver_rhel7.0.iso).
example, FusionServer-RAID-card(BC11ESMS)-SR135(8068)-Firmware-
V108(1.54[0]).zip) to the client (a PC).
Procedure
Step 1 (Optional) Upgrade the driver of the PM8068 RAID controller card.
If the server is not installed with the PM8068 driver, the firmware cannot be
upgraded using CLI.



c. Run the cp /mnt/8068_rhel7.0_x86_x64_1.2.1-50639.rpm /root

d. Run the cd /root command to switch to the /root directory.
e. Run the rpm -ivh 8068_rhel7.0_x86_x64_1.2.1-50639.rpm command to
upgrade the driver of the PM8068 RAID controller card.





decompressed (for example, FusionServer-RAID-card(BC11ESMS)-
SR135(8068)-Firmware-V108(1.54[0]).zip).
d. Click Connect.
The local directory is mounted to the /mnt directory.
c. Run the cd /root command to switch to the /root directory.
for the files.
a. Run ./update.sh to upgrade the RAID controller card firmware.
The server automatically reboots for the new firmware to take effect.
version.
Figure 1-84.
● After the server reboots, use the RAID card CLI tool arcconf to query the
[root@localhost ~]# ./arcconf getconfig 1
......
--------------------------------------------------------
Controller Version Information

--------------------------------------------------------
Firmware : 1.54[0]
Driver : 1.2.1.52011
Hardware Revision :B
----------------------------------------------------------------------
Array Information
----------------------------------------------------------------------
......
----End
1.15.3 Rolling Back the Firmware Version
1.15.3.1 Rollback Rules

perform a rollback.
1.15.3.2 Rollback Procedure

The rollback procedure is similar to the upgrade procedure. For details, see 1.15.2
Update Procedure.
----End
1.16 Upgrading the LSI SAS9305-24i RAID Controller

Card
1.16.1 Upgrading the LSI SAS9305-24i RAID Controller Card

Using SmartKit
Scenarios

Procedure
1-43.
Software Package Type Operation Procedure
Firmware upgrade package of 1. Log in to the FusionServer iDriver

the RAID controller card website.
2. Select the target version.
3. Download upgrade packages of the
required components.
SmartKit package 1. Log in to the FusionServer Tools website.

2. Select the required version.


Guide:

verify-TL1000000054

Upgrade using SmartKit applies to the LSI SAS9305-24i RAID controller card only on V5
servers.


perform a rollback. Perform a rollback only if one of the following problems
occurs:
● The entire upgrade cannot be finished as scheduled. To prevent service
interruption in business hours caused by the upgrade, a rollback is required.

----End
1.16.2 Upgrading the LSI SAS9305-24i RAID Controller Card

Using CLI
Scenarios
Procedure
1-44.
Firmware upgrade package of 1. Log in to the FusionServer iDriver

the RAID controller card website.
2. Select the target version.
3. Download upgrade packages of the
required components.

Management tool of the RAID 1. Go to the RAID controller card page at

controller card the BROADCOM website.
2. On the DOWNLOADS tab page, click
Management Software and Tools.
The management software and tools list
is displayed.
3. Click Latest MegaRAID StorCLI.
4. Decompress the downloaded package to
obtain the tool packages for different
OSs.

Guide:
verify-TL1000000054
Scenarios
Upgrade the LSI SAS9305-24i RAID controller card firmware using CLI on Linux.
LSI SAS9305-24i supports firmware update only in EFI mode.
NOTICE
● Do not power off the OS during the upgrade and do not change configurations
except for those involved in the upgrade guide.

Prerequisites
Conditions
● The server hosting the LSI SAS9305-24i RAID controller card is powered on.
Data
None
Software
● You have downloaded the OS driver package to the client (for example, a PC),
and decompressed the package to obtain the driver image.
example, 2298 V5 -xxx.zip) to the client.
Procedure
controller card ID.
1. Copy the firmware update file to the server.

b. Run the cd /root command.


d. Run cp /mnt/* /root/test to copy the file to the /root/test directory.
e. Run the cd /root/test command to go to the /test directory, and run the
a. Run the ./storcli64 /cController_ID download bios file=mptsas3.rom
b. Run the ./storcli64 /cController_IDdownload file=9305_IT.bin noverchk
c. Run the ./storcli64 /cController_ID download efibios file=mpt3x64.rom
Controller_ID indicates the ID of the RAID controller card. You need to specify this
parameter for each RAID controller card when configuring multiple RAID controller
cards.
3. Power off and then on the server for the firmware to take effect.
During the restart, the firmware information of the RAID controller card is
displayed.
Press F11, select Device Management, select the LSI SAS3224IT RAID
controller card, and press Enter. The firmware information is displayed, as
Check the firmware version using either of the following methods:

● Obtain the firmware version during server startup, as shown in Figure 1-85.
● Query the firmware version using the RAID controller card CLI tool storcli64
on the OS after the server starts, as shown in Figure 1-86.
----End

perform a rollback. Perform a rollback only if one of the following problems
occurs:


● The entire upgrade cannot be finished as scheduled. To prevent service
interruption in business hours caused by the upgrade, a rollback is required.

The rollback procedure is the same as the upgrade procedure. For details, see
----End

Upgrade Guide 2 Upgrading the NIC Firmware
2 Upgrading the NIC Firmware
2.1 Upgrading the BCM5719

2.2 Upgrading the 82599 NIC
2.3 Upgrading the i350 NIC
2.4 Upgrading the X540 NIC
2.6 Upgrading the X710/XL710 NIC
2.9 Upgrading the ConnectX-3 NIC
2.1 Upgrading the BCM5719
2.1.1 Upgrading the BCM5719 NIC Using FwUpgrade
Scenarios
Procedure


Firmware upgrade package 1. Log in to the FusionServer iDriver website.

of the NIC 2. Select the target version.
3. Download upgrade packages of the required
components.
FwUpgrade tool package 1. Log in to the FusionServer Tools website.


Guide:
verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the BCM5719 NIC only on V2 and V3 servers.



perform a rollback.

Step 1 Determine the version to be rolled back.
----End
2.2 Upgrading the 82599 NIC
2.2.1 Upgrading the 82599 NIC Using FwUpgrade
Scenarios
Procedure

components.




Guide:

verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the 82599 NIC only on V2 and V3 servers.

perform a rollback.


----End
2.2.2 Upgrading the 82599 NIC Using Smart Provisioning
Scenarios
Procedure

components.
Smart Provisioning tool 1. Log in to the FusionServer Tools website.

3. Download the required Smart Provisioning
package.

Guide:


verify-TL1000000054

Upgrade using smart provisioning applies to the 82599 NIC only on V5 servers.

perform a rollback.

----End
2.2.3 Upgrading the 82599 NIC Using SmartKit
Scenarios
Procedure



components.
SmartKit tool package 1. Log in to the FusionServer Tools website.


Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the 82599 NIC on V2, V3, and V5 servers.



perform a rollback.

----End
2.3 Upgrading the i350 NIC
2.3.1 Upgrading the i350 NIC Using FwUpgrade
Scenarios
Procedure

components.




Guide:

verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the i350 NIC only on V2 and V3 servers.

perform a rollback.


----End
2.3.2 Upgrading the i350 NIC Using Smart Provisioning
Scenarios
Procedure

components.

package.

Guide:


verify-TL1000000054

Upgrade using smart provisioning applies to the i350 NIC only on V5 servers.

perform a rollback.

----End
2.3.3 Upgrading the i350 NIC Using SmartKit
Scenarios
Procedure



components.


Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the i350 NIC on V2, V3, and V5 servers.



perform a rollback.

----End
2.4.1 Upgrading the X540 NIC Using FwUpgrade
Scenarios
Procedure

components.




Guide:

verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the X540 NIC only on V2 and V3 servers.

perform a rollback.


----End
2.4.2 Upgrading the X540 NIC Using Smart Provisioning
Scenarios
Procedure

components.

package.

Guide:


verify-TL1000000054

Upgrade using smart provisioning applies to the X540 NIC only on V5 servers.

perform a rollback.

----End
2.4.3 Upgrading the X540 NIC Using SmartKit
Scenarios
Procedure
2-10.



components.


Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the X540 NIC on V2, V3, and V5 servers.



perform a rollback.

----End
Scenarios
Procedure
2-11.

components.




Guide:

verify-TL1000000054

User Guide.
Upgrade using FwUpgrade applies to the X550 NIC only on V2 and V3 servers.

perform a rollback.


----End

Upgrade the firmware following instructions in FusionServer Tools 2.0 SmartKit
User Guide.
Scenarios
Procedure
2-12.

components.




Guide:

verify-TL1000000054


perform a rollback.

----End
2.6 Upgrading the X710/XL710 NIC
2.6.1 Upgrading the X710/XL710 NIC Using FwUpgrade

Scenarios
Procedure
2-13.

components.



Guide:

verify-TL1000000054


User Guide.
Upgrade using FwUpgrade applies to the X710/XL710 NIC only on V2 and V3 servers.

perform a rollback.

----End
2.6.2 Upgrading the X710/XL710 NIC Using Smart Provisioning
Scenarios
Procedure
2-14.



components.

package.

Guide:
verify-TL1000000054

Upgrade using smart provisioning applies to the X710/XL710 NIC only on V5 servers.



perform a rollback.

----End
2.6.3 Upgrading the X710/XL710 NIC Using SmartKit
Scenarios
Procedure
2-15.


components.



Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the X710/XL710 NIC on V2, V3, and V5 servers.

perform a rollback.

----End

Scenarios
Procedure
2-16.


components.


Guide:
verify-TL1000000054

Scenarios
Upgrade the firmware of the NIC equipped with an X557 chip.
NOTICE
fail.
● After the upgrade is complete, you need to remove and insert the power
supplies to make the firmware take effect.
● Upgrade using FwUpgrade applies to the X557 NIC only on V2 and V3 servers.
Prerequisites
Conditions
● The server hosting the X557 is powered on.
Software
● The image file tool (for example, UltraISO) has been installed on the client (a
PC).
UltraISO can be downloaded from its official website.

● Downloaded and decompressed the FwUpgrade tool package (for example,
FusionServer Tools-FwUpgrade-V100.zip) to the client (a PC) and obtained
the image (for example, FusionServer Tools-FwUpgrade-V100.iso).
● Download the X557 NIC firmware upgrade package (for example, NIC-LOM-
X557-10GE_BASE_T-FW-9.B.B.A.21.zip) to the client (a PC).
Procedure
Step 1 Obtain software packages.
1. (Optional) For a 2-socket rack server (the second digit of the product name is
2, for example, 1288H V5, 2288H V5, and 5288 V5), view the product name to
determine the optical port type and electrical port type of the server on the
iBMC WebUI, as shown in Figure 2-1.

Figure 2-1 iBMC WebUI
2. Download the FwUpgrade tool package and the X557 NIC firmware upgrade
package. For details, see 2.7.1.1.1 Obtaining Software Packages.
The firmware package must include the automatic upgrade script install.sh.
Step 2 Encapsulate the firmware upgrade package into the FwUpgrade ISO file.
1. Decompress the FwUpgrade tool package and open the FwUpgrade ISO file
(using the UltraISO tool as an example), as shown in Figure 2-2.
– The screenshots and detailed steps related to ISO file operations in this section are
based on the UltraISO tool. The operations may vary according to ISO file tools.
– The path of FusionServer Tools-FwUpgrade-V100.iso cannot contain spaces.
Figure 2-2 Opening the FwUpgrade ISO file

2. Go to the Project directory, as shown in Figure 2-3.
Figure 2-3 Project directory
3. Copy the firmware package to the Project directory of the ISO file, as shown
in Figure 2-4.
You can directly drag the files to the opened ISO image or copy and then paste the
files.
Figure 2-4 Copying files
4. Click in the UltraISO window.

The modified ISO file is saved.


Step 4 Mount the image (.iso).


4. Select the NIC firmware upgrade image (for example, FusionServer Tools-
FwUpgrade-V100.iso), and click Connect in the screen shown in Figure 2-5.


Figure 2-7 Startup screen
Step 6 Upgrade firmware.

1. Select FusionServer Tools FwUpgrade-Vxxx by using the upward or
downward arrow key on the keyboard.
FwUpgrade is loaded and the firmware is automatically upgraded, as shown
in Figure 2-8.
2. After the upgrade is complete, remove and insert the power supplies to make
the firmware take effect.
----End

perform a rollback.


Update Procedure.
----End
Scenarios
Procedure
2-17.

components.




Guide:

verify-TL1000000054


perform a rollback.

----End

Scenarios
Procedure
2-18.

components.



Guide:

verify-TL1000000054

Scenarios
Upgrade the firmware of the NIC equipped with an X722 chip.
NOTICE
fail.
● After the firmware upgrade is complete, forcibly power cycle the server for the
firmware to take effect.
● If the version of FwUpgrade is V101, you need to manually power off and
then power on the server.
● If the version of FwUpgrade is V102 or later, the tool automatically powers
off and then power on the server.
● Upgrade using FwUpgrade applies to the X722 NIC only on V2 and V3 servers.
Prerequisites
Conditions
● The server hosting the X722 is powered on.

Software
● The image file tool (for example, UltraISO) has been installed on the client (a
PC).
UltraISO can be downloaded from its official website.

● Downloaded and decompressed the FwUpgrade tool package (for example,
FusionServer Tools-FwUpgrade-V100.zip) to the client (a PC) and obtained
the image (for example, FusionServer Tools-FwUpgrade-V100.iso).
● Download the X722 NIC firmware upgrade package (for example, 2288H
V5&1288H V5&5288 V5-BC1SPSCA03-10GE BASE T-X722 FW-V102.zip) to
the client (a PC).
Procedure
Step 1 Obtain software packages.
1. (Optional) For a 2-socket rack server (the second digit of the product name is
2, for example, 1288H V5, 2288H V5, and 5288 V5), view the product name to
determine the optical port type and electrical port type of the server on the
iBMC WebUI, as shown in Figure 2-9.

Figure 2-9 iBMC WebUI
2. Download the FwUpgrade tool package and the X722 NIC firmware upgrade
package. For details, see 2.8.1.1.1 Obtaining Software Packages.
– The V5 2-socket rack servers provide optical ports or electrical ports. Before the
upgrade, select a firmware upgrade package based on the port type. The firmware
upgrade package for electrical port servers is XXXX-BC1SPSCA03-10GE BASE T-
X722 FW-Vxxx.zip, and the firmware upgrade package for optical port servers is
XXXX-BC1SPSCA03-10GE SFP T-X722 FW-Vxxx.zip.
– The firmware package must include the automatic upgrade script install.sh.
Step 2 Encapsulate the firmware upgrade package into the FwUpgrade ISO file.
1. Decompress the FwUpgrade tool package and open the FwUpgrade ISO file
(using the UltraISO tool as an example), as shown in Figure 2-10.
– The screenshots and detailed steps related to ISO file operations in this section are
based on the UltraISO tool. The operations may vary according to ISO file tools.
– The path of FusionServer Tools-FwUpgrade-V100.iso cannot contain spaces.

Figure 2-10 Opening the FwUpgrade ISO file
2. Go to the Project directory, as shown in Figure 2-11.
Figure 2-11 Project directory
3. Copy the firmware package to the Project directory of the ISO file, as shown
in Figure 2-12.

You can directly drag the files to the opened ISO image or copy and then paste the
files.
Figure 2-12 Copying files
4. Click in the UltraISO window.

The modified ISO file is saved.
Step 4 Mount the image (.iso).



4. Select the NIC firmware upgrade image (for example, FusionServer Tools-
FwUpgrade-V100.iso), and click Connect in the screen shown in Figure 2-13.

Figure 2-15 Startup screen
Step 6 Upgrade firmware.

1. Select FusionServer Tools FwUpgrade-Vxxx by using the upward or
downward arrow key on the keyboard.
FwUpgrade is loaded and the firmware is automatically upgraded, as shown
in Figure 2-16.

2. After the firmware upgrade is complete, forcibly power cycle the server for
the firmware to take effect.
– If the version of FwUpgrade is V101, manually power off and then power
on the server.
– If the version of FwUpgrade is V102 or later, the tool automatically
powers off and then power on the server.
----End

perform a rollback.

Update Procedure.
----End

Scenarios
Procedure
2-19.

components.



Guide:

verify-TL1000000054



perform a rollback.

----End
2.9.1 Upgrading the ConnectX-3 NIC Using DOS
Scenarios
Procedure
2-20.



components.


Guide:
verify-TL1000000054

Upgrade the firmware following instructions in FusionServer Tools 2.0
FwUpgrade User Guide.
Upgrade using FwUpgrade applies to the ConnectX-3 NIC only on V2 and V3 servers.



perform a rollback.

----End
2.9.2 Upgrading the ConnectX-3 NIC Using SmartKit
Scenarios
Procedure
2-21.


components.



Guide:
verify-TL1000000054

Upgrade using SmartKit applies to the ConnectX-3 NIC on V2, V3, and V5 servers.

perform a rollback.

----End

2.10.1 Upgrading the ConnectX-4 NIC Using FwUpgrade
Scenarios
Procedure
2-22.


components.


Guide:
verify-TL1000000054


User Guide.

perform a rollback.

----End
2.10.2 Upgrading the ConnectX-4 NIC Using Smart

Provisioning
Scenarios
Procedure
2-23.



components.

package.

Guide:
verify-TL1000000054

Upgrade using smart provisioning applies to the ConnectX-4 NIC only on V5 servers.



perform a rollback.

----End
Scenarios
Procedure
2-24.


components.



Guide:
verify-TL1000000054


perform a rollback.

----End

2.11.1 Upgrading the ConnectX-5 NIC Using FwUpgrade
Scenarios
Procedure
2-25.


components.


Guide:
verify-TL1000000054


User Guide.

perform a rollback.

----End
Scenarios
Procedure
2-26.



components.


Guide:
verify-TL1000000054




perform a rollback.

----End

Upgrade Guide 3 Upgrading the Firmware of Chassis Components
3 Upgrading the Firmware of Chassis

Components
3.1 Upgrading the iBMC

3.2 Upgrading the BIOS
3.3 Upgrading the Mainboard CPLD
3.4 Upgrading the Hard Disk Backplane CPLD
3.5 Upgrading the SCM CPLD
3.6 Upgrading the I/O Module CPLD
3.7 Upgrading the Riser Card CPLD
3.8 Upgrading the LCD Firmware
3.9 Upgrading the Hard Disk Backplane Firmware
3.10 Upgrading the SD Card Controller Firmware
3.11 Upgrading the Fan Module Firmware
3.12 Upgrading Smart Provisioning
3.1 Upgrading the iBMC
3.1.1 Using the iBMC Web to Upgrade the iBMC
3.1.1.1.1 Impact of the Upgrade

Before you upgrade to a new version, read this section carefully to find out the
possible impact on the system.

Impact on the System

Table 3-1 describes the impact of the upgrade on the system.
Table 3-1 Impact on the system
No. Item Impact Impact Description
1 iBMC Impact on services None
Impact on O&M No other operations are allowed

during the upgrade. You should
restart the iBMC immediately or
later after the upgrade. Services
are interrupted during the restart.
NOTE
iBMC 2.36 and later will restart
automatically after the upgrade.
2 iBMC Impact on services None

languag
e pack Impact on O&M None
Impact on the Parts

None.
3.1.1.1.2 Precautions
Table 3-2 describes the precautions for upgrading the server.
Table 3-2 Precautions for upgrading the server
No. Description
1 Read this document before upgrading the server. For any

problems or suggestions pertaining to this document, contact
technical support.
2 Perform the upgrade during off-peak hours to minimize the

impact on the system and services.
3 Time required for a software upgrade:

● iBMC: 15 to 20 minutes
NOTE
The primary and backup images of the iBMC must be upgraded separately.
Therefore, you must upgrade the iBMC twice, and each upgrade takes
about 5 to 10 minutes. For details, see 3.1.1.3 Upgrading the iBMC.
● iBMC language pack: 2 minutes

3.1.1.1.3 Version Requirements

If you need to upgrade the iBMC from a version earlier than an intermediate
version to a version later than the intermediate version, upgrade the iBMC to the
intermediate version and then the target version. If the upgrade to the
intermediate version fails, restart the iBMC and try again. Table 3-3 lists the
compute node models and their intermediate versions. For example, if the iBMC
source version of a RH2288H V3 is earlier than V257 and the target version is later
than V257, you need to upgrade the iBMC to V257 and then to the target version.
If the upgrade to V257 fails, restart the iBMC and try again.
Table 3-3 iBMC intermediate versions and compute node models
Intermediate Model
Version
257 RH2288H V3/RH1288 V3/RH5288 V3
260 RH5885H V3
262 RH2288 V3
270 RH5885 V3
276 RH8100 V3
3.1.1.1.4 Upgrade Process
iBMC Upgrade Process

Figure 3-1 shows the iBMC upgrade process.
Figure 3-1 iBMC upgrade process
The following describes the upgrade process:

1. Log in to the iBMC WebUI.

2. Run the upgrade command on the iBMC WebUI.
3. Upgrade the backup iBMC system image.
The iBMC that the user has accessed uses the primary system image.
4. Restart the iBMC system. The current login user is logged out after the system
restarts, and the image file is automatically switched to the upgraded backup
system image.
5. Log in to the iBMC WebUI again.
6. Run the upgrade command again on the iBMC WebUI.
7. Upgrade the original primary iBMC system image.
8. Restart the iBMC system.
3.1.1.2.1 Pre-upgrade Checklist

Table 3-4 lists the items to be checked before the upgrade.
Table 3-4 Pre-upgrade checklist

No. Item Operation and Expected Result
1 System 1. View and record the current iBMC versions. For details, see
softwar 4.7 Checking Server Software Versions.
e 2. Check that the source versions are earlier than target
version versions.
2 System Check iBMC system operating status:

operati ● If no minor alarm, major alarm, or critical alarm is
ng generated, continue the upgrade process. For details, see
status 4.8 Checking Server Alarms.
● If an alarm is generated, contact technical support.
3.1.1.2.2 Obtaining the Upgrade Packages and Documents

You can obtain the upgrade packages and documents as follows:
1. Log in to the Huawei Enterprise support website.
2. choose Technical Support > Product Support > Software Download >
Intelligent Servers.
3. Select the server model.
4. In the server list, select the server to be upgraded.
The server version list is displayed.
5. Download and decompress the upgrade packages to a local PC. Table 3-5 lists
the upgrade packages to be obtained.

Table 3-5 Upgrade package
Upgrade Function Required File after

Package Decompression
iBMC iBMC upgrade package image.hpm or server model-

iBMC-iBMC version.hpm, for
example, 2288_V5-iBMC-
V320.hpm
6. Download the documents required for the upgrades from the same page.
Documents to be obtained are as follows:
– Release Notes
– Upgrade Guide


Guide:

verify-TL1000000054
3.1.1.3 Upgrading the iBMC
3.1.1.3.1 Update Procedure
Scenarios
Upgrade the iBMC.
The following uses iBMC 2.50 as an example. The Upgrade Firmware page may
vary according to iBMC versions.

● The system user name and password remain unchanged after the upgrade.
● The primary and backup images of the iBMC must be upgraded separately.
● Upgrade the backup image first. After the upgrade is completed, the primary iBMC
image automatically restarts, and primary and backup iBMC images automatically
switch over. You do not need to click Image Switchover on the iBMC UI. After the
switchover, upgrade the original primary image.
● For RH8100 V3:
● If the RH8100 V3 runs in single-system mode, log in to the master iBMC WebUI
and upgrade the master iBMC. After the master iBMC is upgraded, the master
iBMC transfers the upgrade file to the slave iBMC over FTP, and the slave iBMC is
automatically upgraded.
● If the RH8100 V3 runs in dual-system mode, log in to the iBMC WebUI of system A
and upgrade the iBMC of system A; log in to the iBMC WebUI of system B and
upgrade the iBMC of system B.
If you need to upgrade the iBMC from a version earlier than an intermediate
version to a version later than the intermediate version, upgrade the iBMC to the
intermediate version and then the target version. If the upgrade to the
intermediate version fails, restart the iBMC and try again. Table 3-6 lists the
compute node models and their intermediate versions. For example, if the iBMC
source version of a RH2288H V3 is earlier than V257 and the target version is later
than V257, you need to upgrade the iBMC to V257 and then to the target version.
If the upgrade to V257 fails, restart the iBMC and try again.
Table 3-6 iBMC intermediate versions and compute node models
Intermediate Model
Version
257 RH2288H V3/RH1288 V3/RH5288 V3
260 RH5885H V3
262 RH2288 V3
270 RH5885 V3
276 RH8100 V3

Upgrading the iBMC will cause the iBMC system to restart twice. Perform the
upgrade during the off-peak hours.
Prerequisites
Conditions
● You have logged in to the iBMC WebUI. For details, see 4.2 Logging In to the
iBMC WebUI.
● No minor alarm, major alarm, or critical alarm is generated on the iBMC.

Data
Data preparation is not required for this operation.
Software
You have obtained and decompressed the upgrade package. For details, see
3.1.1.2.2 Obtaining the Upgrade Packages and Documents.
Procedure
NOTICE
If the iBMC version is earlier than 2.56, restart the iBMC before upgrading the
firmware. To restart the iBMC, do as follows:
● Log in to the iBMC WebUI, choose System > Firmware Upgrade, and click
Restart iBMC in the Firmware Version Info area. For details about how to log
in to the iBMC WebUI, see 4.2 Logging In to the iBMC WebUI.
● Log in to the iBMC CLI and run the ipmcset -d reset command to restart the
iBMC. For details about how to log in to the iBMC CLI, see 4.5 Accessing the
iBMC CLI.
Step 1 Upgrade the backup iBMC image.

1. Choose System on the main menu, as indicated by (1) in Figure 3-2.
2. In the navigation tree, choose Upgrade Firmware, as indicated by (2) in
Figure 3-2.
Figure 3-2 Upgrade Firmware page
3. In the Upgrade Firmware area, click , as indicated by (3) in Figure 3-2.

The Browse window is displayed.
4. Select the upgrade file, for example, image.hpm, from a local directory on
the PC.
5. Click Open.

The upgrade package is selected, and the Upgrade Firmware page is

displayed.
6. Click Upgrade, as indicated by (4) in Figure 3-2.
The Start Upgrade dialog box is displayed.
7. Click OK.
The iBMC then starts the upgrade.
Upgrade of the backup iBMC image takes about 5 to 10 minutes.
The upgrade is complete when the progress reaches 100%.
After the upgrade is completed, the iBMC system automatically restarts, and primary
and backup iBMC images automatically switch over. You do not need to click Image
Switchover on the iBMC UI.
Step 2 Upgrade the original primary iBMC image.

For details, see 4.2 Logging In to the iBMC WebUI.
2. Repeat Step 1 to upgrade the original primary iBMC image.
----End
3.1.1.3.2 Verifying the Upgrade
Verification Checklist
Table 3-7 describes the iBMC upgrade verification checklist.
Table 3-7 Verification checklist

No. Item Expected Result
1 Login to the iBMC WebUI You can log in to the iBMC

WebUI using the Internet
Explorer.
2 iBMC version The iBMC is of the target version.

Verification Procedure and Troubleshooting

Procedure

For details, see 4.2 Logging In to the iBMC WebUI.
2. Check the iBMC version.
For details, see 4.7 Checking Server Software Versions.
Check that the iBMC is of the target version.
Troubleshooting
If you fail to log in to the iBMC WebUI after the upgrade, contact technical
support.
If the iBMC is not of the target version or an error message is displayed, upgrade
the iBMC again. If the iBMC still cannot be upgraded successfully, record the steps
you have taken and the results, and send the information to technical support.
3.1.1.4 Upgrading iBMC Language Packs
3.1.1.4.1 Performing the Upgrade
Scenarios
Update the iBMC language packs.
● Only iBMC 2.56 and later versions allows users to install and uninstall language packs.
● Only administrators and users with common setting permissions have the rights to
install and uninstall language packs.
● The English and Chinese language packs cannot be uninstalled.

None
Prerequisites
Conditions
You have logged in to the iBMC WebUI. For details, see 4.2 Logging In to the
iBMC WebUI.
Data
Software
You have obtained XXX-iBMC-LANG-XX-Vxxx.hpm. For details, see 3.1.1.2.2

Obtaining the Upgrade Packages and Documents.

Procedure
Step 1 Update the iBMC WebUI language packs.
1. Choose System on the main menu, as indicated by (1) in Figure 3-3.
2. In the navigation tree, choose Upgrade Firmware, as indicated by (2) in
Figure 3-3.

4. Select the upgrade file, for example, image.hpm, from a local directory on
the PC.
5. Click Open.
The language pack is selected, and the Upgrade Firmware page is displayed.
The Start Upgrade dialog box is displayed.
7. Click OK.
The iBMC then starts the update.
The language pack update takes about 2 minutes.
The language pack update is complete when the progress reaches 100%.

Step 2 After the update is complete, you can change the language of the iBMC WebUI to
the language selected in the upper right corner of the page.
----End
Table 3-8 describes the iBMC language pack update verification checklist.
1 Whether the newly supported You can change the language of

languages can be selected on the iBMC WebUI to the language
the iBMC WebUI selected in the upper right corner
of the page.
2 Whether the iBMC language The iBMC language pack versions

pack version is updated are the target versions.

Procedure
1. On the iBMC WebUI, choose System > Language Update.

2. On the Language Update page, check the installed languages and language
pack versions.
3. Change the language of the iBMC WebUI to the language selected in the
upper right corner of the page.
If the iBMC system language can be changed to the selected language and
the language pack versions are the target versions, the update is successful.
Troubleshooting
If the iBMC language pack versions are not the target ones or an update failure
message is displayed, update the iBMC language packs again. If the update still
fails, record the fault information, steps you have taken, and results, and contact
technical support.


problems occurs:

Step 1 Determine the components and versions to be rolled back.
You are advised to roll back the software to the source version.
NOTICE
According to the Intel SPS version restrictions:

● if the server model is 2488 V5, 2488H V5, 5885H V5, or 8100 V5, AC power
cycle is required for the BIOS rollback from V099 to an earlier version to take
effect; otherwise, the server cannot be powered on properly.
● If the server model is 1288H V5, 2288H V5, or 5288 V5, AC power cycle is
required for the BIOS rollback from V087 to an earlier version to take effect;
otherwise, the server cannot be powered on properly.
Step 2 Roll back the software.
The operations of rolling back software to a specified version are the same as that
those of upgrading the software.
You can also use the ipmcset -d rollback command to roll back the iBMC software to the
source version.
----End
3.1.2 Using SmartKit to Upgrade the iBMC
Scenarios

Procedure
Firmware upgrade package 1. Log in to the Huawei Enterprise support

of iBMC website.
2. choose Technical Support > Product
Support > Software Download > Intelligent
Servers.
4. In the server list, select the server to be
upgraded.
5. Download the required upgrade package.



Guide:

verify-TL1000000054

For details, see "Upgrading Server Firmware" in the FusionServer Tools 2.0
SmartKit User Guide.


perform a rollback.

----End
3.2 Upgrading the BIOS
3.2.1 Using the iBMC Web to Upgrade the BIOS
3.2.1.1.1 Impact of the Upgrade

Before you upgrade to a new version, read this section carefully to find out the
possible impact on the system.

Table 3-10 describes the impact of the upgrade on the system.
Table 3-10 Impact on the system
Impact Impact Description
Impact on services The server must be restarted after the

upgrade, and services will be interrupted.
Impact on the OS If power-off upgrade is used, the OS will be

shut down and services are unavailable.

Impact Impact Description
Impact on O&M None

NOTE
The server must not be restarted during the
upgrade.
Impact on the Parts

None.
3.2.1.1.2 Precautions
Table 3-11 describes the precautions for upgrading the server.
Table 3-11 Precautions for upgrading the server

No. Description
1 Read this document before upgrading the server. For any

problems or suggestions pertaining to this document, contact
technical support.
2 Perform the upgrade during off-peak hours to minimize the

impact on the system and services.
3 The upgrade takes about 10 minutes.
3.2.1.1.3 Version Requirements

The upgrade has no version requirement.
3.2.1.1.4 Upgrade Process
BIOS Upgrade Process

Figure 3-4 shows the BIOS upgrade process.
Figure 3-4 BIOS upgrade process

The following describes the upgrade process:

1. Log in to the iBMC WebUI.
2. Run the upgrade command on the iBMC WebUI.
3. Upgrade the BIOS image.
4. Run the restart OS command on the iBMC WebUI.
5. Restart the OS.
3.2.1.2.1 Pre-upgrade Checklist

Table 3-12 lists the items to be checked before the upgrade.
Table 3-12 Pre-upgrade checklist

No. Item Operation and Expected Result
1 System 1. View and record the current BIOS versions. For details, see
softwar 4.7 Checking Server Software Versions.
e 2. Check that the source versions are earlier than target
version versions.
2 System Check iBMC system operating status:

operati ● If no minor alarm, major alarm, or critical alarm is
ng generated, continue the upgrade process. For details, see
status 4.8 Checking Server Alarms.
● If an alarm is generated, contact technical support.
3.2.1.2.2 Obtaining the Upgrade Packages and Documents

You can obtain the upgrade packages and documents as follows:
1. Log in to the Huawei Enterprise support website.
2. choose Technical Support > Product Support > Software Download >
4. In the server list, select the server to be upgraded.
5. Download and decompress the upgrade packages to a local PC. Table 3-13
lists the upgrade packages to be obtained.

Table 3-13 Upgrade package
Upgrade Function Required File after

Package Decompression
BIOS BIOS upgrade package biosimage.hpm or server

model -BIOS-BIOS
version.hpm, for example,
5885H_V5-BIOS-V117.hpm
6. Download the documents required for the upgrades from the same page.
Documents to be obtained are as follows:
– Release Notes
– Upgrade Guide


Guide:

verify-TL1000000054
3.2.1.3 Upgrading the BIOS
3.2.1.3.1 Performing the Upgrade
Scenarios
Upgrade the server BIOS on the Upgrade Firmware page of the iBMC.
The BIOS can be upgraded when the OS is powered on or powered off. After the
upgrade, the OS needs to be restarted for the upgrade to take effect. The restart
interrupts running services.
The BIOS can be upgraded in either of the following modes:
● Use the iBMC WebUI. For details, see Procedure in this section.

● Use the iBMC CLI. Run the ipmcset -d upgrade -v <filepath> command. For
details, see the Huawei Server iBMC User Guide.
The following uses iBMC 2.50 as an example. The Upgrade Firmware page may

During the BIOS upgrade, if the system does not respond, or the server is powered
on and off repeatedly during the upgrade, power off and on the server after the
upgrade.
● Due to architecture differences, the BIOS rollback to V6xx or earlier will fail
on an RH5885 V3 that users Intel E7 v4 processors. Therefore, you are not
advised to perform the rollback in this case.
● For RH8100 V3:
– Due to architecture differences, the BIOS rollback from V6xx to V3xx or
earlier will fail on an RH8100 V3 that users Intel E7 v2/v3 processors.
Therefore, you are not advised to perform the rollback in this case.
– Due to architecture differences, the BIOS rollback to V6xx or earlier will
fail on an RH8100 V3 that users Intel E7 v4 processors. Therefore, you are
not advised to perform the rollback in this case.
– If the RH8100 V3 runs in single-system mode, you only need to log in to
the master iBMC WebUI and upgrade the BIOS. After the master BIOS is
upgraded, the master iBMC transfers the upgrade file to the slave iBMC
over FTP, and the slave BIOS is automatically upgraded.
– If the RH8100 V3 runs in dual-system mode, log in to the iBMC WebUI of
system A and upgrade the BIOS of system A; log in to the iBMC WebUI of
system B and upgrade the BIOS of system B.
NOTICE
According to the Intel SPS version restrictions,

● If the server model is 2488 V5, 2488H V5, 5885H V5, or 8100 V5, AC power
effect; otherwise, the server cannot power on properly.
● If the server model is 1288H V5, 2288H V5, or 5288 V5, power off the AC
supply for the BIOS rollback to a version earlier than V087 to take effect.
Otherwise, the server cannot power on properly.
Procedure
Step 1 (Optional) On a V5 server, log in to the iBMC WebUI to query the port type of the
server by product name. See Figure 3-5. For details about how to log in to the
iBMC WebUI, see 4.2 Logging In to the iBMC WebUI.

Figure 3-5 Querying the port type by product name (using 2288H V5 as an
example)
Step 2 Obtain the BIOS upgrade package.
Obtain and decompress the upgrade package. For details about how to obtain the
upgrade package, see 3.2.1.2.2 Obtaining the Upgrade Packages and
Documents.
Step 3 Log in to the iBMC.
Log in to the iBMC WebUI. For details, see 4.2 Logging In to the iBMC WebUI.
NOTICE
● Log in to the iBMC WebUI, choose System > Firmware Upgrade, and click
in to the iBMC WebUI, see 4.2 Logging In to the iBMC WebUI.
● Log in to the iBMC CLI and run the ipmcset -d reset command to restart the
iBMC CLI.
Step 4 Upgrade the BIOS.
● Do not power on, power off, reset, or restart the server OS during the upgrade.
● The RH8100 V3 supports BIOS flashes running in redundancy mode. You need to
upgrade flash 0 and then flash 1. If either flash fails to be upgraded, an upgrade failure
message is displayed.
● During the RH8100 V3 upgrade, if flash 1 fails to be upgraded and flash 0 has been
upgraded successfully, the BIOS of the new version in flash 0 is in use after you restart
the server.
1. On the iBMC page, choose System > Upgrade Firmware, as indicated by (1)
and (2) in Figure 3-6.


3. In the displayed dialog box, select the upgrade file, for example,
biosimage.hpm, from a local directory on the PC, and click Open.
The upgrade package is selected, and the Upgrade Firmware page is
displayed.
5. Click OK.
The iBMC starts the upgrade. The upgrade preparation takes about 2 minutes.
Then, the upgrade starts.
– If the server is in power-off state during the upgrade, "The upgrade is
complete" will be displayed after the upgrade.
– If the server is in power-on state during the upgrade:
▪ For V2 servers or V3 servers whose iBMC version is earlier than V252,

"The upgrade is complete" will be displayed after the upgrade.
▪ For V5 servers or V3 servers whose iBMC version is V252 or later,

"File upload successfully. The upgrade takes effect automatically
after the next power-off or restart" will be displayed after the
upgrade.
Step 5 Make the BIOS upgrade take effect.
● If the upgrade is performed offline, power on the server to make the upgrade
take effect.
a. Choose Power > Power Control on the main menu.
b. Click Power On.
A Confirm dialog box is displayed.
c. Click Yes.
● If the upgrade is performed online, do as follows:

NOTICE
– The Power Control page varies slightly depending on the iBMC version.
For details, see the iBMC online help.
– You can use the remote virtual console to view the server power-on
process. In the navigation tree, choose Remote Control > Remote Virtual
Console (shared mode).
– If the OS has been installed on the server, forcibly restarting the server on
the iBMC WebUI may damage user programs or unsaved user data. Select
an appropriate restart mode based on actual requirements.
– If the server fails to start after a forced restart, shut down the server, roll
back the BIOS to the source version, and then upgrade the BIOS to the
target version. For details, see Step 2 to Step 5.
– If TPM is enabled, proceed depending on whether the OS has been

installed.
▪ If the OS has been installed:

○ Access the OS and restart the OS. The new BIOS version takes
effect about 10 minutes after the server is restarted.
○ If the OS cannot be accessed, forcibly restart the server on the
iBMC WebUI.
1) Choose Power > Power Control on the main menu.
2) Click Forced System Reset.
3) Click Yes.
The new BIOS version takes effect about 10 minutes after the
server is restarted.
▪ If the OS has not been installed:

○ Press Ctrl+Alt+Delete to restart the server. The new BIOS
version takes effect about 10 minutes after the server is
restarted.
○ If the server does not respond, forcibly restart the server on the
iBMC WebUI.
3) Click Yes.
– If TPM is not enabled, proceed depending on whether the OS has been
installed.
▪ If the OS has been installed:

○ Access the OS and restart the OS. The new BIOS version takes
effect about 10 minutes after the server is restarted.

○ Forcibly restart the server on the iBMC WebUI.

3) Click Yes.
▪ If the OS has not been installed:

○ Press Ctrl+Alt+Delete to restart the server. The new BIOS
version takes effect about 10 minutes after the server is
restarted.
○ Forcibly restart the server on the iBMC WebUI.
3) Click Yes.
Step 6 (Optional) If you need to modify the BIOS configuration, press Delete during
system startup to enter the BIOS.
----End
Table 3-14 describes the BIOS upgrade verification checklist.

1 BIOS operating status The server BIOS is operating

properly.
2 BIOS version The BIOS is of the target version.

Procedure
Check whether the BIOS is of the target version after system power-on. For details,
see 4.7 Checking Server Software Versions.
Troubleshooting
Contact technical support if the BIOS does not start after the upgrade.

If the BIOS is not of the target version or an error message is displayed, upgrade
the BIOS again. If the BIOS still cannot be upgraded successfully, record the steps
you have taken and the results, and send the information to technical support.

problems occurs:

You are advised to roll back the software to the source version.
NOTICE
According to the Intel SPS version restrictions:

● if the server model is 2488 V5, 2488H V5, 5885H V5, or 8100 V5, AC power
effect; otherwise, the server cannot power on properly.
● If the server model is 1288H V5, 2288H V5, or 5288 V5, power off the AC
supply for the BIOS rollback to a version earlier than V087 to take effect.
Otherwise, the server cannot power on properly.
Step 2 Roll back the software.

The operations of rolling back software to a specified version are the same as that
those of upgrading the software.
----End
3.2.2 Using SmartKit to Upgrade the BIOS
Scenarios

Procedure

of BIOS website.
Servers.
upgraded.
components.


Guide:
verify-TL1000000054



perform a rollback.

----End
3.3 Upgrading the Mainboard CPLD
3.3.1 Using the iBMC Web to Upgrade the Mainboard CPLD
Scenarios
Procedure
Step 1 Log in to the Huawei Enterprise support website.
Step 2 choose Technical Support > Product Support > Software Download >
Step 3 Select the server model.
Step 4 In the server list, select the server to be upgraded.

Step 5 Download the required upgrade package.
----End


Guide:

verify-TL1000000054
Scenarios
Upgrade the server mainboard CPLD using the iBMC WebUI.
The mainboard CPLD can be upgraded when the server is powered on or off, and
the upgrade procedures are similar. This section describes how to upgrade the
mainboard CPLD when the server is powered off.
This section uses iBMC 2.64 as an example. The Firmware Upgrade page may
Prerequisites
Conditions
You have logged in to the iBMC WebUI.
Software
You have downloaded and decompressed the mainboard CPLD upgrade package
(for example, RH2288H V3-Mainboard(BC1HGSA01)-CPLD-V200.zip) to the
client (a PC) and obtained the upgrade file (for example, cpldimage.hpm).

Procedure
NOTICE
● Log in to the iBMC WebUI, choose System > Upgrade Firmware, and click
Restart iBMC in the Firmware Version Info area. For details about how to
log in to the iBMC WebUI, see 4.4 Logging In Using the iBMC WebUI.
● Log in to the iBMC CLI, and run the ipmcset –d reset command to restart the
iBMC CLI.
Step 1 Upgrade the mainboard CPLD.
NOTICE
in to the iBMC WebUI, see 4.4 Logging In Using the iBMC WebUI.
iBMC CLI.
1. On the iBMC WebUI, choose System > Firmware Upgrade.

The Firmware Upgrade page is displayed, as shown in Figure 3-7.

Figure 3-7 Firmware Upgrade
2. In the Firmware Upgrade area, click .

3. Select the upgrade file.
4. Click Open.
The upgrade package is selected, and the Firmware Upgrade page is
displayed.
5. Click Upgrade.
A dialog box is displayed asking you whether to start the upgrade.
6. Click Yes.
During the CPLD upgrade, do not power off the server. If the server is abnormal due to an
unexpected power-off during the upgrade, log in to the iBMC and upgrade the CPLD again.
The upgrade process takes about 3 minutes. If "The upgrade is complete" is

displayed, the upgrade is successful.
Step 2 Enable the new CPLD to take effect based on the server power status:
● Server power-off status
– For a V3 server, the iBMC is automatically reset after the CPLD upgrade is
complete. After the iBMC is reset, the new CPLD takes effect. In addition,
the iBMC automatically powers on or powers off the server based on the
setting of System State Upon Power Supply.
▪ If System State Upon Power Supply is set to Power On, the iBMC
automatically powers on the server.

▪ If System State Upon Power Supply is set to Restore Previous

State or Remain Off, you need to power on the server by choosing
Power > Power Control in the navigation tree and clicking Power
On on the Power Control page.
– For a V5 server, the server automatically powers off and then powers on
after the CPLD upgrade is complete. The new CPLD takes effect upon
system startup.
● Server power-on status
After the CPLD upgrade is complete on a V3 or V5 server, power off the server
by choosing Power > Power Control in the navigation tree and clicking
Power Off on the Power Control page. The new CPLD takes effect after the
iBMC is automatically reset. The iBMC automatically powers on or powers off
the server based on the setting of System State Upon Power Supply.
– If System State Upon Power Supply is set to Power On or Restore
Previous State, the iBMC automatically powers on the server.
– If System State Upon Power Supply is set to Remain Off, you need to
power on the server by choosing Power > Power Control in the
navigation tree and clicking Power On on the Power Control page.
NOTICE
A forcible power-off may cause data loss or program damage. Forcibly power off
the server only when necessary.
Step 3 Check whether the CPLD version is the target version.

1. On the iBMC WebUI, choose Information > System Info.
2. View the mainboard CPLD version information on the page displayed.
----End

problems occurs:


Step 2 Roll back the firmware or CPLD version.

Update Procedure.
----End
3.3.2 Using the iMana 200 to Upgrade the Mainboard CPLD
Scenarios
Procedure
----End

Guide:
verify-TL1000000054

Scenarios
Upgrade the server mainboard CPLD using the iMana 200 WebUI.
The mainboard CPLD can be upgraded when the server is powered on or off, and
the upgrade procedures are similar. This section describes how to upgrade the
mainboard CPLD when the server is powered off.
Prerequisites
Conditions
You have logged in to the iMana 200 WebUI.
Software
You have downloaded and decompressed the mainboard CPLD upgrade package
(for example, RH1288 V2&RH2288H V2-Mainboard(BC1SRSG01)-CPLD-
V008.zip) to the client (a PC) and obtained the upgrade file (for example,
cpldimage.hpm).
Procedure
Step 1 Upgrade the mainboard CPLD.
1. On the iMana 200 WebUI, choose Configuration > Firmware Upgrade.
2. Click Browse, and select the upgrade file.

3. Click Upgrade.
A confirmation dialog box is displayed.
4. Click Yes.
unexpected power-off during the upgrade, log in to the iMana 200 and upgrade the CPLD
again.


After the CPLD upgrade is complete, the iMana 200 is automatically reset
after the CPLD upgrade is complete. After the iMana 200 is reset, the new
CPLD takes effect. In addition, the iMana 200 automatically powers on or
powers off the server based on the setting of System State Upon Power
Supply.
– If System State Upon Power Supply is set to Power On, the iMana 200
– If System State Upon Power Supply is set to Restore Previous State or
Remain Off, you need to power on the server by choosing Power >
Power Control in the navigation tree and clicking Power On on the
Power Control page.
After the CPLD upgrade is complete, power off the server by choosing Power
> Power Control in the navigation tree and clicking Power Off on the Power
Control page. The CPLD of the new version takes effect after the iMana 200
is automatically reset. The iMana 200 automatically powers on or powers off
Previous State, the iMana 200 automatically powers on the server.
NOTICE

1. On the iMana 200 WebUI, choose System Information > Firmware Version.
2. View the mainboard CPLD version information on the page displayed.
----End

problems occurs:



Update Procedure.
----End
3.3.3 Using SmartKit to Upgrade the Mainboard CPLD
Scenarios
Procedure
3-16.

of the chassis components website.
Servers.
upgraded.




Guide:

verify-TL1000000054


perform a rollback.

----End

3.4 Upgrading the Hard Disk Backplane CPLD
3.4.1 Using the iBMC Web to Upgrade the Hard Disk

Backplane CPLD
Scenarios
Procedure
----End

Guide:
verify-TL1000000054

Scenarios
Upgrade the hard drive backplane CPLD using the iBMC WebUI.
The hard drive backplane CPLD can be upgraded when the server is powered on or
off, and the upgrade procedures are similar. This section describes how to upgrade
the hard drive backplane CPLD when the server is powered off.
If the RH8100 V3 server is equipped with front I/O module of model B (FM-B), upgrade the
CPLD of the two hard drive backplanes respectively.
● If the RH8100 V3 server works in single-system mode, log in to the iBMC WebUI of the
server and load the upgrade file for the two hard drive backplanes respectively.
● If the RH8100 V3 server works in dual-system mode, log in to the iBMC WebUI of
system B and load the upgrade file for the two hard drive backplanes respectively.
Prerequisites
Conditions
Software
You have downloaded and decompressed the CPLD upgrade package (for
example, RH2288H V3-8HDD Backplane&12HDD&25HDD Expander
Backplane(BC1THBH01)-CPLD-V106.zip) to the client (a PC) and obtained the
upgrade file (for example, cpldimage.hpm).
Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the hard drive backplane CPLD.



4. Click Open.
displayed.
5. Click Upgrade.
6. Click Yes.

1. Server power-off status


system startup.
2. Server power-on status
Power Off on the Power Control page. The CPLD of the new version takes
effect after the iBMC is automatically reset. The iBMC automatically powers
on or powers off the server based on the setting of System State Upon
Power Supply.
NOTICE

1. On the iBMC WebUI, choose Information > System Info > Other Devices.
2. View the hard drive backplane CPLD version information on the page
displayed.
----End

problems occurs:


Update Procedure.
----End
3.4.2 Using the iMana 200 to Upgrade the Hard Disk

Backplane CPLD
Scenarios
Procedure
----End

Guide:


verify-TL1000000054
Scenarios
Upgrade the hard drive backplane CPLD using the iMana 200 WebUI.
The hard drive backplane CPLD can be upgraded when the server is powered on or
off, and the upgrade procedures are similar. This section describes how to upgrade
the hard drive backplane CPLD when the server is powered off.
Prerequisites
Conditions
Software
example, RH1288 V2&RH2288H V2&RH2285H V2&RH2288 V2&RH2285
V2-8&12&24HDD-Expander-Backplane(BC1THBA01)-CPLD-V012.zip) to the
client (a PC) and obtained the upgrade file (for example, hddcpld.hpm).
Procedure
Step 1 Upgrade the hard drive backplane CPLD.

3. Click Upgrade.

4. Click Yes.
again.

Supply.
Power Control page.
NOTICE

2. View the CPLD version information on the page displayed.
----End


problems occurs:

Update Procedure.
----End
3.4.3 Using SmartKit to Upgrade the Hard Disk Backplane

CPLD
Scenarios
Procedure


Servers.
upgraded.



Guide:

verify-TL1000000054



perform a rollback.

----End
3.5 Upgrading the SCM CPLD
3.5.1 Using the iBMC Web to Upgrade the SCM CPLD
Scenarios
Procedure
----End


Guide:
verify-TL1000000054
Scenarios
Upgrade the system compute module (SCM) CPLD of RH8100 V3 or RH8100 V5
using the iBMC WebUI.
This section uses the RH8100 V3 as an example. The upgrade procedure is similar
for the RH8100 V5.
The SCM CPLD can be upgraded when the server is powered on or off, and the
upgrade procedures are similar. This section describes how to upgrade the SCM
CPLD when the server is powered off.
NOTICE
● SCM CPLDs are upgraded at one time and cannot be upgraded one by one.
● If the RH8100 server works in single-system mode, slots 1 to 4 must be fully
populated and slots 5 to 8 must be fully populated or empty. Otherwise, the
upgrade fails.
● If the RH8100 server works in dual-system mode, slots 1 to 4 of system A and
slots 5-8 of system B must be fully populated. Otherwise, the upgrade fails.
Prerequisites
Conditions

Software
example, RH8100 V3-Processor Board(BC6BPNA01)-CPLD-V115.zip) to the
client (a PC) and obtained the upgrade file (for example, BC6BPNA01115.hpm).
Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the SCM CPLD.




4. Click Open.
displayed.
5. Click Upgrade.
6. Click Yes.


system startup.
Power Supply.
NOTICE


----End

problems occurs:

Update Procedure.
----End
3.5.2 Using SmartKit to Upgrade the SCM CPLD
Scenarios
Procedure


Servers.
upgraded.



Guide:

verify-TL1000000054



perform a rollback.

----End
3.6 Upgrading the I/O Module CPLD
3.6.1 Using the iBMC Web to Upgrade the I/O Module CPLD
Scenarios
Procedure
----End



Guide:

verify-TL1000000054
3.6.1.2 Upgrade Procedure
Scenarios
Upgrade the I/O module CPLD of the RH8100 V3 or RH8100 V5 server using the
iBMC WebUI.
This section uses the RH8100 V3 as an example to describe the upgrade method.
The upgrade method is similar for the RH8100 V5.
The I/O module CPLD can be upgraded when the server is powered on or off, and
the upgrade procedures are similar. This section describes how to upgrade the I/O
module CPLD when the server is powered off.
● If the RH8100 server works in single-system mode, both the front and rear I/O modules
can be upgraded online.
● If the RH8100 server works in dual-system mode, only the rear I/O module in system A
and the front I/O module in system B can be upgraded online.

● When the OS of system B is shut down, upgrading the front I/O module using
the iBMC of system B will shut down the OS of system A.
● When the OS of system A is shut down, upgrading the rear I/O module using
the iBMC of system A will shut down the OS of system B.

Prerequisites
Conditions
Software
example, RH8100 V3-8HDD-Front IO Board(BC6FIOB01)-CPLD-V110.zip) to the
client (a PC) and obtained the upgrade file (for example, BC6FIOB01110.hpm).
Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the I/O module CPLD.



4. Click Open.
displayed.
5. Click Upgrade.
6. Click Yes.
The upgrade process takes about 1 minute. If "The upgrade is complete" is


system startup.
Power Supply.

NOTICE

Step 4 (Optional) Upgrade the CPLDs of remaining I/O modules in the same way.
----End

problems occurs:

Upgrade Procedure.
----End
3.6.2 Using SmartKit to Upgrade the I/O Module CPLD
Scenarios
Procedure


Servers.
upgraded.



Guide:

verify-TL1000000054



perform a rollback.

----End
3.7 Upgrading the Riser Card CPLD
3.7.1 Using the iBMC Web to Upgrade the Riser Card CPLD
Scenarios
Procedure
----End


Guide:
verify-TL1000000054
Scenarios
Upgrade the riser card CPLD using the iBMC WebUI.
The riser card CPLD can be upgraded when the server is powered on or off, and
the upgrade procedures are similar. This section describes how to upgrade the riser
card CPLD when the server is powered off.
Prerequisites
Conditions
Software
You have downloaded and decompressed the riser card CPLD upgrade package
(for example, RH5885H V3-RiserCard(BC6PHPA01)-CPLD-V005.zip) to the client
(a PC) and obtained the upgrade file (for example, cpldimage_for_ibmc.hpm).

Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the riser card CPLD.


4. Click Open.
displayed.
5. Click Upgrade.


6. Click Yes.


system startup.
Power Supply.
NOTICE

----End


problems occurs:

Update Procedure.
----End
3.7.2 Using the iMana 200 to Upgrade the Riser Card CPLD
Scenarios
Procedure
----End



Guide:

verify-TL1000000054
Scenarios
Upgrade the riser card CPLD using the iMana 200 WebUI.
The riser card CPLD can be upgraded when the server is powered on or off, and
the upgrade procedures are similar. This section describes how to upgrade the riser
card CPLD when the server is powered off.
Prerequisites
Conditions
Software
You have downloaded and decompressed the riser card CPLD upgrade package
(for example, RH5885H V3-RiserCard(BC6PHPA01)-CPLD-V005.zip) to the client
(a PC) and obtained the upgrade file (for example, cpldimage_for_ibmc.hpm).
Procedure
Step 1 Upgrade the riser card CPLD.


3. Click Upgrade.
4. Click Yes.
again.

Supply.
Power Control page.

NOTICE

----End

problems occurs:

Update Procedure.
----End
3.7.3 Using SmartKit to Upgrade the Riser Card CPLD
Scenarios

Procedure

Servers.
upgraded.



Guide:

verify-TL1000000054



perform a rollback.

----End
3.8 Upgrading the LCD Firmware
3.8.1 Using the iBMC Web to Upgrade the LCD Firmware
Scenarios
Procedure

----End


Guide:

verify-TL1000000054
Scenarios
Upgrade the firmware of the liquid crystal display (LCD) using the iBMC WebUI.
The LCD firmware can be upgraded when the server is powered on or off, and the
upgrade procedures are similar. This section describes how to upgrade the LCD
firmware when the server is powered off.
Prerequisites
Conditions
Software
example, RH2288H V3-LCD(BC1LCD02)-FW-V033.zip) to the client (a PC) and
obtained the upgrade file (for example, lcdimage.hpm).

Procedure
NOTICE
● If the iBMC version is earlier than 2.56, restart the iBMC before upgrading the
● Log in to the iBMC CLI, and run the ipmcset –d reset command to restart
the iBMC. For details about how to log in to the iBMC CLI, see 4.5
Accessing the iBMC CLI.
Step 1 Upgrade the LCD firmware.


4. Click Open.
displayed.
5. Click Upgrade.


6. Click Yes.

2. View the firmware version information on the page displayed.
----End

problems occurs:

Update Procedure.
----End
3.8.2 Using the iMana 200 to Upgrade the LCD Firmware
Scenarios
Procedure

----End

Guide:
verify-TL1000000054
Scenarios
Upgrade the firmware of the LCD using the iMana 200 WebUI.
The LCD firmware can be upgraded when the server is powered on or off, and the
upgrade procedures are similar. This section describes how to upgrade the LCD
firmware when the server is powered off.
Prerequisites
Conditions
Software
You have downloaded and decompressed the LCD firmware upgrade package (for
example, RH5885H V3-LCD-V033.zip) to the client (a PC) and obtained the
upgrade file (for example, lcdimage.hpm).

Procedure
Step 1 Upgrade the LCD firmware.

3. Click Upgrade.
4. Click Yes.
If "The upgrade is complete" is displayed, the upgrade is successful. The
upgrade process takes about 1 minute.

----End

problems occurs:


Update Procedure.
----End
3.8.3 Using SmartKit to Upgrade the LCD Firmware
Scenarios
Procedure
3-21.


Servers.
upgraded.



Guide:
verify-TL1000000054


perform a rollback.

----End
3.9 Upgrading the Hard Disk Backplane Firmware
3.9.1 Using the iBMC Web to Upgrade the Hard Disk

Backplane Firmware

Scenarios
Procedure
----End


Guide:

verify-TL1000000054
Scenarios
Upgrade the firmware of the hard drive backplane.

Prerequisites
Conditions
Procedure
● Upgrading the Hard Drive Backplane Firmware for the RH5885H V3,
RH5885 V3, RH5885H V5, or RH5885 V5 Server
● Upgrading the Hard Drive Backplane Firmware for Other Servers
Upgrading the Hard Drive Backplane Firmware for the RH5885H V3, RH5885
V3, RH5885H V5, or RH5885 V5 Server
Upgrade the firmware of the front 23-drive or 24-drive Expander backplane of the
RH5885H V3, RH5885 V3, RH5885H V5, or RH5885 V5 server.
Before the upgrade, download the 23-drive backplane update package, for
example RH5885H V3-HDD Backplane(BC6HBPA02)-Firmware-V107.zip, to the
client (local PC), and decompress it.
1. Upload the upgrade package.


c. Select Directory, and click Browse.

d. Select the folder generated after the upgrade package (for example,
RH5885H V3-HDD Backplane(BC6HBPA02)-Firmware-V107.zip) is
decompressed on the client, and click Connect.
e. Upload the upgrade package to the OS, and run the chmod +x *
command to add the read and write permissions for all the files.
2. Upgrade the firmware.
a. Run the g3Xflash -i SAS address down fw FW file name to upgrade the
firmware.
SAS address is 500605b0000272bf by default. If the firmware upgrade of
the RH5885H V5 or RH5885 V5 fails, the SAS address has changed. In this
case, you need to query the new SAS address.
To query the SAS address, perform the following steps:

i. Log in to the iBMC WebUI. For details, see 4.4 Logging In Using the
iBMC WebUI.
ii. Click One-Click Info Collection to collect log information, as shown
in Figure 3-18.
Figure 3-18 One-click information collection
iii. Download and decompress the dump_info.tar.gz file. Open the

RAID_Card1_com_log file in dump_info\LogDump\storage.
iv. Search IsSata in the RAID_Card1_com_log file to obtain the SAS
address. As shown in Figure 3-19, the information in the rectangle
indicates the SAS address of the hard disk backplane.
Figure 3-19 Querying the SAS address of the hard disk backplane
b. Enter y and press Enter.

c. Run the g3Xflash -i 500605b0000272bf down mfg MFG file name

command to update the MFG file.
A message is displayed asking you whether to perform the upgrade.
d. Enter y and press Enter.
3. Power off and then power on the server for the new firmware to take effect.
4. Check whether the firmware version is the target version.
a. Run the g3Xflash -i 500605b0000272bf get ver command to query the
firmware version.

b. Run the g3Xflash -i 500605b0000272bf get ver 3 command to query

the MFG version.
----End
Upgrading the Hard Drive Backplane Firmware for Other Servers

Upgrade the front 12-drive, 24-drive, 25-drive Expander backplane of other
servers.
Before the upgrade, download the 12-drive backplane update package, for
example RH2288H V3-12HDD-Expander-Backplane(BC1THBF02)-FW-V120.zip,
to the client and decompress it.
The 12-drive backplane of the RH2288H V3 server is used as an example.
1. Upload the upgrade package.


c. Select Directory, and click Browse.

d. Select the folder generated after the upgrade package (for example,
RH2288H V3-12HDD-Expander-Backplane(BC1THBF02)-FW-V120.zip)
is decompressed on the client, and click Connect.
e. Upload the upgrade package to the OS, and run the chmod +x *
command to add the read and write permissions for all the files.
2. Run the lsscsi -g command to query the sg device number corresponding to
the drive backplane.
In the command output, "expander" indicates the drive backplane. In the
following example, "/dev/sg4" indicates the sg device number.
[root@localhost ~]# lsscsi -g
[3:0:0:0] disk ATA INTEL SSDSC2BA20 0270 /dev/sda /dev/sg0
[15:0:0:0] enclosu HUAWEI Expander 135 - /dev/sg4
If the sg device number cannot be obtained, load the modprobe sg.ko driver.
3. Upgrade the firmware.
Repeat 3.a to 3.d for each drive backplane queried in 2. The sg device number of the
expander is the sg device number of the drive backplane. The following uses the drive
backplane with the sg device No. of 4 as an example.
a. Run ./expanderTool query /dev/sg device number of the Expander to

query the firmware version.
b. Run ./expanderTool download=boot_mips.bin /dev/sg device number

of the Expander to update the boot file.
c. Run ./expanderTool download=istr_flash_pm8053.bin /dev/sg device

number of the Expander to update the firmware configuration file.

d. Run ./expanderTool download=sxp_evbd_rom.bin /dev/sg device

number of the Expander to update the firmware file.
4. Power off and then power on the server for the new firmware to take effect.
5. Check whether the firmware version is the target version.
Run ./expanderTool query /dev/sg device number of the Expander to query
the firmware version.
----End

problems occurs:

Update Procedure.
----End
3.9.2 Using SmartKit to Upgrade the Hard Disk Backplane

Firmware
Scenarios

Procedure
3-22.

Servers.
upgraded.


Guide:
verify-TL1000000054



perform a rollback.

----End
3.10 Upgrading the SD Card Controller Firmware
3.10.1 Using the iBMC Web to Upgrade the SD Card Controller

Firmware
Scenarios
Procedure

----End


Guide:

verify-TL1000000054
Scenarios
Upgrade the SD card controller firmware using the iBMC WebUI.
The SD card controller firmware can be upgraded when the operating system (OS)
is powered on or off, and the upgrade procedures are similar. This section
describes how to upgrade the SD card controller firmware when the server is
powered off.
Prerequisites
Conditions
Software
example, RH1288V3-TwinSD-V132166.zip) to the client (a PC) and obtained the
upgrade file (for example, TwinSD.hpm).

Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the SD card controller firmware.


4. Click Open.
displayed.
5. Click Upgrade.


6. Click Yes.
The iBMC restarts immediately after the upgrade is complete.

----End

problems occurs:

----End
3.10.2 Using SmartKit to Upgrade the SD Card Controller

Firmware
Scenarios

Procedure
3-23.

Servers.
upgraded.


Guide:
verify-TL1000000054



perform a rollback.

----End
3.11 Upgrading the Fan Module Firmware
3.11.1 Using the iBMC Web to Upgrade the Fan Module

Firmware
Scenarios
Procedure

----End


Guide:

verify-TL1000000054
Scenarios
Upgrade the firmware of the fan modules in the RH8100 V3 server using the iBMC
WebUI.
The fan module firmware can be upgraded when the server is powered on or off,
and the upgrade procedures are similar. This section describes how to upgrade the
fan module firmware when the server is powered off.
Prerequisites
Conditions
Software
example, RH8100 V3-FAN-V207.zip) to the client (a PC) and obtained the
upgrade file (for example, Fan_V207.hpm).

Procedure
NOTICE
iBMC CLI.
Step 1 Upgrade the fan module firmware.


4. Click Open.
displayed.
5. Click Upgrade.


6. Click Yes.
----End

problems occurs:

----End
3.11.2 Using SmartKit to Upgrade the Fan Module Firmware
Scenarios
Procedure
3-24.


Servers.
upgraded.
5. The server version list is displayed.



Guide:

verify-TL1000000054



perform a rollback.

----End
3.12 Upgrading Smart Provisioning
3.12.1 Upgrade Using Smart Provisioning

This section describes how to upgrade Smart Provisioning on a single server. For
details, see the Smart Provisioning User Guide.
3.12.2 Upgrade Using SmartKit

This section describes how to upgrade Smart Provisioning for multiple servers in
batches. For details, see the FusionServer Tools 2.0 SmartKit User Guide.

Upgrade Guide 4 Common Operations
4 Common Operations
4.1 Querying the IP Address of the iBMC Management Network Port

4.2 Logging In to the iBMC WebUI
4.3 Logging In Using the iMana 200 WebUI
4.4 Logging In Using the iBMC WebUI
4.5 Accessing the iBMC CLI
4.6 Transferring Files Using the Local Directory
4.7 Checking Server Software Versions
4.8 Checking Server Alarms
4.1 Querying the IP Address of the iBMC Management

Network Port
The method used to query the iBMC IP address varies depending on the server
platform. For details, see BIOS Parameter Reference of the specific platform. This
section uses the Grantley and Purley platforms as an example to describe how to
query the iBMC IP address using the BIOS.
4.1.1 Querying the IP Address of the iBMC Management

Network Port (Grantley Platform)
Scenarios
Query the IP address of the iBMC management network port in BIOS. The
following describes the querying procedure using the Grantley BIOS as an
example.
The default IP address of the iBMC network port is 192.168.2.100.
You can query the IP address of the iBMC management network port in BIOS
using the following menus:

● Romley BIOS
Advanced > IPMI BMC Configuration > BMC Configuration
● Brickland BIOS
Main > Server Mgmt > BMC network configuration
● Grantley BIOS
Advanced > IPMI iBMC Configuration > iBMC Configuration
● Purley BIOS
● TaiShan Server BIOS

This operation has no adverse impact on the system.
Prerequisites
Conditions
No special condition is required for this operation.
Data
For RH8100 V3, do not set the IP address to one in the segment from 10.0.0.0 to 10.0.0.3.
This IP address segment is reserved for internal communication.
Procedure
Step 1 Restart the server.
1. Upon server startup, press Delete within 3 seconds until the BIOS Setup
Utility screen is displayed.
2. Enter a BIOS password as prompted, as shown in Figure 4-1.
Figure 4-1 Entering a BIOS password

Step 2 Enter the BIOS.
The BIOS setup screen varies according to the CPU platform. For details, see the BIOS
document of the server you use.
The Main screen is displayed, as shown in Figure 4-2.
Figure 4-2 Main screen
Step 3 Select the Advanced screen using arrow keys, as shown in Figure 4-3.

Figure 4-3 Advanced screen
Step 4 On the Advanced screen, select IPMI iBMC Configuration using arrow keys and
press Enter, as shown in Figure 4-4.
Figure 4-4 IPMI iBMC Configuration screen
Step 5 On the IPMI iBMC Configuration screen, select iBMC Configuration using arrow
keys and press Enter, as shown in Figure 4-5.

Figure 4-5 iBMC Configuration screen
The server IP address is displayed on this screen.
The default BIOS password is Huawei12#$.
----End

Network Port (Purley Platform)
Scenarios
Query the IP address of the iBMC management network port in BIOS. The
following uses the Purley BIOS as an example.
The default IP address of the iBMC network port is 192.168.2.100.
You can query the IP address of the iBMC management network port in BIOS
using the following menus:
● Romley BIOS
Advanced > IPMI BMC Configuration > BMC Configuration
● Brickland BIOS
Main > Server Mgmt > BMC network configuration
● Grantley BIOS

● Purley BIOS
● TaiShan Server BIOS

Prerequisites
Conditions
No special condition is required for this operation.
Data
For RH8100 V3, do not set the IP address to one in the segment from 10.0.0.0 to 10.0.0.3.
This IP address segment is reserved for internal communication.
Procedure
Step 1 Restart the server.
1. Upon server startup, press Delete within 3 seconds until the BIOS Setup
Utility screen is displayed.
2. Enter a BIOS password as prompted, as shown in Figure 4-6.
The default BIOS password is Admin@9000.

Figure 4-6 Entering a BIOS password
Step 2 Enter the BIOS.
The BIOS setup screen varies according to the CPU platform. For details, see the BIOS
document of the server you use.
The Main screen is displayed, as shown in Figure 4-7.

Figure 4-7 Main screen
Step 3 Select the Advanced screen using arrow keys, as shown in Figure 4-8.
Figure 4-8 Advanced screen
Step 4 On the Advanced screen, select IPMI iBMC Configuration using arrow keys and
press Enter, as shown in Figure 4-9.

Figure 4-9 IPMI iBMC Configuration screen
Step 5 On the IPMI iBMC Configuration screen, select iBMC Configuration using arrow
keys and press Enter, as shown in Figure 4-10.
Figure 4-10 iBMC Configuration screen

The server IP address is displayed on this screen.
----End

Network Port Using SSH
Scenarios
Query the IP address of the iBMC management network port in the HMM.
For a full-width node, the default IP address of the management network port is
10.10.1.101.

Prerequisites
Conditions
You have logged in to the HMM CLI. For details, see the section "Logging In to the
HMM CLI Through the Management Network Port" in the FusionServer G5500
Server 1.0.0 User Guide.
Data
● Internal network segment IP addresses of the compute node:
– Slot 1: 172.31.1.129
– Slot 2: 172.31.1.130
● Default user name and password of the compute node
Procedure
Step 1 Run the SSH command to log in to the compute node using the internal network
segment IP address.
Example:
iBMC:/->ssh [email protected]
The authenticity of host '172.31.1.129 (172.31.1.129)' can't be established.
ECDSA key fingerprint is SHA256:gOgF1v/fGKzvFRkjm1axPEK85NGrfP6UOUSBzt6qx48.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '172.31.1.129' (ECDSA) to the list of known hosts.
WARNING! This system is PRIVATE and PROPRIETARY and may only be accessed by authorized users.
Unauthorized use of the system is prohibited. The owner, or its agents, may monitor any activity or
communication on the system. The owner, or its agents, may retrieve any information stored within the
system. By accessing and using the system, you are consenting to such monitoring and information retrieval
for law enforcement and other purposes.
[email protected]'s password:
Last login: Thu Nov 2 20:41:30 2017 from 192.168.10.197
iBMC:/->
Step 2 Run the ipmcget -v ipinfo command to query the IP address of the iBMC.
Example:

iBMC:/->ipmcget -d ipinfo
EthGroup ID : 1
Net Mode : Manual
Net Type : Dedicated
IPv4 Information :
IP Mode : static
IP Address : 192.168.10.206
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.10.206
MAC Address : 00:18:c0:a8:0a:cf
IPv6 Information :
IPv6 Mode : static
IPv6 Address 1 :
Default Gateway IPv6 :
Link-Local Address : fe80::218:c0ff:fea8:acf/64
VLAN Information :
VLAN State : disabled
EthGroup ID : 2
Net Mode : Manual
Net Type : Dedicated
IPv4 Information :
IP Mode : static
IP Address : 172.31.1.129
Subnet Mask : 255.255.255.0
Default Gateway :
MAC Address : 00:18:c0:a8:0a:cf
IPv6 Information :
IPv6 Mode : static
IPv6 Address 1 :
Default Gateway IPv6 :
Link-Local Address : fe80::218:c0ff:fea8:acf/64
VLAN Information :
VLAN State : enabled
VLAN ID : 4093
----End
4.1.4 Checking the IBMC IP Address

Scenarios
Query the IP address of the iBMC management network port by using the BIOS.
Procedure
Step 1 Log in to the BIOS Setup Utility. For details, see A.4 Accessing the BIOS.
Step 2 Choose Advanced > IPMI iBMC Configuration, and press Enter.
The IPMI iBMC Configuration screen is displayed, as shown in Figure 4-11 and
Figure 4-12.

Figure 4-11 IPMI iBMC Configuration screen 1
Figure 4-12 IPMI iBMC Configuration screen 2
Step 3 Select BMC Configuration and press Enter.

The iBMC Configuration screen is displayed. The iBMC IP information is similar to
Figure 4-13 and Figure 4-14.

Figure 4-13 iBMC Configuration screen 1
Figure 4-14 iBMC Configuration screen 2
----End

4.2 Logging In to the iBMC WebUI

Scenarios
Log in to the iBMC WebUI using the browser of your local PC. The following
describes the login procedure using a PC that uses Windows 7 and Internet
Explorer 8.0 as an example.

Prerequisites
Conditions
The OS, browser, and Java runtime environment (JRE) versions of the local PC that
uses the remote control function comply with the requirements listed in Table 4-1.
The local PC meets the following networking requirements:
● A network connection has been established between the local PC and the
iBMC management network port.
● IP addresses of the local PC and iBMC management network port are on the
same network segment.
Table 4-1 Running environment
OS Browser JRE
Windows 7 32-bit Internet Explorer 9.0 JRE 1.7 U45

Windows 7 64-bit to 11.0 JRE 1.8 U45
NOTE
JRE 1.8 U144
HTML5 supports only
Internet Explorer 10.0 or
later.
Mozilla Firefox 39.0 to

54.0
Google Chrome 21.0

to 44.0

Windows 8 64-bit to 11.0 JRE 1.8 U45
Mozilla Firefox 39.0 to JRE 1.8 U144
54.0
Google Chrome 21.0

to 44.0

OS Browser JRE

54.0
Windows Server 2012 R2 Internet Explorer 11.0 JRE 1.8 U45

64-bit JRE 1.8 U144
54.0
Windows Server 2016 Internet Explorer 11.0 JRE 1.8 U45

64-bit JRE 1.8 U144
54.0
Windows Server 2008 R2 Internet Explorer 9.0 JRE 1.7 U45

64-bit to 11.0 JRE 1.8 U45
NOTE
JRE 1.8 U144
HTML5 supports only
later.

54.0
Google Chrome 21.0

to 44.0
Windows Server 2012 Internet Explorer 10.0 JRE 1.7 U45

64-bit to 11.0 JRE 1.8 U45
54.0
Google Chrome 21.0

to 44.0
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
MAC X v10.7 Safari 8.0 JRE 1.7 U45

54.0 JRE 1.8 U144
You can download Java software from http://www.oracle.com/technetwork/java/javase/

downloads/index.html.
Data
You have obtained the data listed in Table 4-2.

Table 4-2 Required data

Catego Param Description Example
ry eter
User User User name used to log in to the iBMC ● Grantley: root
login name WebUI ● Purley:
inform NOTE Administrator
ation The default user name is root for the
Grantley platform and Administrator for the
Purley platform.
Passwo Password used to log in to the iBMC ● Grantley:

rd WebUI Huawei12#$
NOTE ● Purley:
The default password is Huawei12#$ for the Admin@9000
Grantley platform and Admin@9000 for the
Purley platform.
Procedure
Step 1 Use a network cable (crossover or twisted pair) to connect the local PC and the
iBMC management network port of the server.
Figure 4-15 shows the networking.
Figure 4-15 Networking diagram
Step 2 Open the Internet Explorer on your local PC.

Step 3 In the address bar, enter the iBMC IP address in the format of https://IP address
of the iBMC management network port (for example, https://192.168.2.100),
and press Enter.
For details about the IP address of the iBMC management network port, see 4.1.1
Querying the IP Address of the iBMC Management Network Port (Grantley Platform).
Step 4 Press Enter.

The iBMC login page is displayed in the Internet Explorer, as shown in Figure 4-16.

● If the Internet Explorer displays Certificate Error, click Continue to this website (not
recommended).
● If the Security Alert dialog box is displayed, click OK.
Figure 4-16 iBMC login page
Step 5 On the iBMC login page, enter your user name and password.
If you log in with incorrect passwords for five consecutive times, the system will lock your
account. Try again 5 minutes later.
Step 6 In the Domain drop-down list box, choose This iBMC.
Step 7 Click Log In.
The Information Summary page is displayed. The login user name is displayed at
the upper right corner on the page.
----End
4.3 Logging In Using the iMana 200 WebUI

Conditions
The OS, web browser, and JRE of the required versions have been installed on the
client to enable the remote control function.
Table 4-3 lists the required software versions.

Table 4-3 Required software versions
OS Browser JRE
● Windows 7 32-bit Internet Explorer 8.0 to ● Internet Explorer 8.0

● Windows 8 32-bit 10.0 to 10.0
● Windows Server 2008 Mozilla Firefox 9.0 to ● JRE 1.6.0 U25 (32-bit)
32-bit 23.0 JRE 1.7.0 U40 (32-bit)
Google Chrome 13.0 to

31.0
● Windows 7 64-bit Internet Explorer 8.0 to ● JRE 1.6.0 U25 (64-bit)

● Windows 8 64-bit 10.0 ● JRE 1.7.0 U40 (64-bit)
● Windows Server 2008 Mozilla Firefox 9.0 to
R2 64-bit 23.0
● Windows Server 2012 Google Chrome 13.0 to
64-bit 31.0
● Red Hat 4.3 64-bit Mozilla Firefox 9.0 to ● JRE 1.6.0 U25
● Red Hat 6.0 64-bit 23.0 ● JRE 1.7.0 U40
MAC X v10.7 Safari 5.1 ● JRE 1.6.0 U25
Mozilla Firefox 9.0 to ● JRE 1.7.0 U40

23.0
Procedure
Step 1 Obtain the following data:
● IP address and subnet mask for the iMana management network port
● User name and password for login to the iMana
Step 2 Configure a login environment.
1. Connect the network port of the client to the iMana management network
port of the server using a network cable.
2. Configure an IP address for the client, and connect the client to the server
iMana management network port.
Step 3 Set properties for the web browser.
1. On the menu bar of Internet Explorer, choose Tools > Internet Options.
The Internet Options dialog box is displayed.
This section uses Windows 7 with Internet Explorer 8 as an example.

2. Click the Connections tab, and then click LAN Settings.
The Local Area Network (LAN) Settings dialog box is displayed.
3. In the Proxy server area, deselect Use a proxy server for your LAN.

You can also retain the proxy server configuration and add the iMana IP address
segment in the Exceptions area in the Advanced dialog box of the proxy server.
4. Click OK.
The Local Area Network (LAN) Settings dialog box is closed.
5. Click OK.
The Internet Options dialog box is closed.
Step 4 Log in to the iMana WebUI.

1. Open Internet Explorer, enter https://IP address for the iMana management
network port in the address box, and press Enter.
The Certificate Error: Navigation Blocked page is displayed.
2. Click Continue to this website (not recommended).
The login page is displayed, as shown in Figure 4-17.
Figure 4-17 iMana login page
3. On the login page, set the parameters as follows:

a. Select a language.
b. Enter your user name and password. The default user name is root, and
the default password is Huawei12#$ or root.
c. Select This iMana from the Log on to drop-down list.
d. Click Log In.
The iMana WebUI is displayed, as shown in Figure 4-18.
You can click Reset to reset the information.

Figure 4-18 iMana WebUI
Step 5 Open the Remote Virtual Console.

1. In the navigation pane, click Remote Control.
The Remote Control page is displayed, as shown in Figure 4-19.
Figure 4-19 Remote Control page
2. On the Remote Control page, click Remote Virtual Console (requiring JRE).
The Remote Virtual Console is displayed, as shown in Figure 4-20.

Figure 4-20 Remote Virtual Console
----End
4.4 Logging In Using the iBMC WebUI

Conditions
The OS, web browser, and JRE of the required versions have been installed on the
client to enable the remote control function.
Table 5-2 lists the required software versions.
Table 4-4 Required software versions
OS Browser JRE
Windows 7 32-bit Internet Explorer 9.0 to JRE 1.7 U45

Windows 7 64-bit 11.0 JRE 1.8 U45
NOTE
JRE 1.8 U144
HTML5 supports only
later.

54.0

44.0
Windows 8 32-bit Internet Explorer 10.0 to JRE 1.7 U45

Windows 8 64-bit 11.0 JRE 1.8 U45
54.0

44.0

54.0
Windows 2012 R2 64-bit Internet Explorer 11.0 JRE 1.8 U45

54.0

JRE 1.8 U144

OS Browser JRE

54.0
Windows Server 2008 R2 Internet Explorer 9.0 to JRE 1.7 U45

64-bit 11.0 JRE 1.8 U45
NOTE
JRE 1.8 U144
HTML5 supports only
later.

54.0

44.0
Windows Server 2012 64- Internet Explorer 10.0 to JRE 1.7 U45
bit 11.0 JRE 1.8 U45
54.0

44.0
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
MAC X v10.7 Safari 8.0 JRE 1.7 U45

54.0 JRE 1.8 U144
Procedure
● IP address and subnet mask for the iBMC management network port
● User name and password for login to the iBMC
Step 2 Configure a login environment.

1. Connect the network port of the client to the iBMC management network
port of the server using a network cable.
2. Set an IP address for the PC. Ensure that this IP address is on the same
network segment as the IP address of the iBMC management network port.
For example, set the IP address to 192.168.2.10 and the subnet mask to
255.255.255.0.
Step 3 Log in to the iBMC WebUI.

1. Open Internet Explorer, enter https://ipaddress/ in the address box (ipaddress

is the IP address of the iBMC management network port), and press Enter.
The login page is displayed, as shown in Figure 4-21.
– If the Internet Explorer displays Certificate Error, click Continue to this website
(not recommended).
– If the Security Alert dialog box is displayed, click OK.
Figure 4-21 iBMC login page
2. On the login page, set the parameters as follows:

a. Select a language.
b. Enter a user name and password. For the default user name and
password, see Huawei Server iBMC User Guide.
c. Select This iBMC from the Log on to drop-down list.
d. Click Log In.
The iBMC WebUI is displayed
Step 4 Open the Remote Virtual Console.
1. Choose Remote Console from the main menu.
The Remote Console page is displayed, as shown in Figure 4-22.

Figure 4-22 Remote Console page
2. On the Remote Console page, click Remote Virtual Console (requiring

JRE).
The Remote Virtual Console is displayed, as shown in Figure 4-23.
Figure 4-23 Remote Virtual Console
----End
4.5 Accessing the iBMC CLI

Login Modes
You can log in to the iBMC CLI using any of the following methods:
● SSH

Secure Shell (SSH) is a network protocol that allows data to be exchanged

over a secure channel between two computers. A maximum of five users can
access the iBMC CLI over SSH at the same time.
SSH supports AES128-CTR, AES192-CTR, and AES256-CTR encryption algorithms. Use an

appropriate encryption algorithm when logging in to the iBMC over SSH.
● Local serial port
● For V3 servers, the default user is root, and the default password is Huawei12#$; for V5
servers, the default user is Administrator, and the default password is Admin@9000.
● The system locks a user account if the user enters incorrect passwords for consecutive
five times. The user account is automatically unlocked five minutes later. The
administrator can also unlock the user account using CLI.
● For security purposes, change the initial password after the first login and change your
password periodically.
● The default command timeout period is 15 minutes.
Prerequisites
● To open the iBMC CLI over the network port, you must connect the network
port of the configuration terminal to the network port of the server by using
a network cable, and ensure that the IP addresses of the two network ports
are on the same network segment.
Do not connect two management network ports at the same time. You can log in to the
iBMC through only one management network port.
● Before logging in to the iBMC CLI through the serial port, use a serial cable to
connect the serial port of the configuration terminal to the serial port of the
server by using a serial cable.
Accessing iBMC CLI Over SSH

Step 1 Download an SSH communication tool on to client.
Step 2 Connect the client to the server management network port directly or over the
network.
Step 3 Configure an IP address for the client to connect it to the iBMC management
network port.
Step 4 On the client, start the SSH communication tool and configure related parameters
(for example, the IP address).
Step 5 Enter the user name and password to log in to the iBMC CLI.
----End

● Both local and LDAP users can log in to the iBMC CLI over SSH. The LDAP user can log
in to the iBMC CLI without entering the domain server information.
● Before logging in to the iBMC CLI as an LDAP user, ensure that the connection between
the iBMC and the LDAP server is normal.
Accessing iBMC CLI Over the Serial Port
NOTICE
Before logging in to the iBMC CLI over the serial port, ensure that the system
serial port of the chassis is switched to the iBMC serial port. You can switch over
the serial port by running the serialdir command on the iBMC CLI or using a
jumper (see the user guide of your server).
Step 1 Connect the client and the server using a serial cable.
Step 2 Open HyperTerminal and set the following parameters:
● Bits per second: 115200
● Data bits: 8
● Parity: None
● Stop bits: 1
● Flow control: None
For details on how to set the parameters, see Figure 4-24.

Figure 4-24 HyperTerminal properties
Step 3 Click Apply.
Step 4 Enter the user name and password to log in to the iBMC CLI.
----End
4.6 Transferring Files Using the Local Directory

Use the local Directory of the Remote Virtual Console to transfer files between
the client and server. The example in this section describes how to send files from
a local directory to the server.
The operation procedure is as follows:

● IP address and subnet mask for the iBMC management network port
● User name and password of the server iBMC
Step 2 Log in to the Remote Control or Remote Console page of the server.
Depending on the management software, see one of the following sections:
● 4.3 Logging In Using the iMana 200 WebUI

● 4.4 Logging In Using the iBMC WebUI
Step 3 Open the local directory.

1. Click Remote Virtual Console (Shared Mode) or Remote Virtual Console

(Private Mode) on the Remote Control or Remote Console page.
The Remote Virtual Console is displayed.
2. Click .
The window shown in Figure 4-25 is displayed.
Figure 4-25 Accessing the local directory
3. Click Directory.
4. Click Browse to select a folder on the client, such as D:\test.
The folder cannot be empty.

5. Click Connect.
The selected directory is identified as a local directory of the server.
Step 4 Place the file to be sent in the target directory.
Copy the file (such as a driver package or script) to the target directory specified
in 4 of Step 3.
Step 5 Copy the file to the server.
1. Log in to the server as user root.
2. Find the local directory specified in 4 of Step 3.
This operation varies depending on the OS type. For details, see the official
OS documentation.
3. Copy the file in the directory found in 2 of Step 5 to a directory on the server
(for example, /tmp).
----End
4.7 Checking Server Software Versions

Scenarios
Check software versions of the iBMC, BIOS and LCD.

Prerequisites
Conditions

iBMC WebUI.
Data
Procedure
Step 1 Choose Information on the main menu.
Step 2 In the navigation tree, choose Information Summary, as shown in Figure 4-26.
Figure 4-26 Information Summary page
In the Basic Info area:

● iBMC Firmware Version: indicates the iBMC version.
● BIOS Firmware Version: indicates the BIOS version.
Step 3 In the navigation tree, choose Component Info or System Info.
If the LCD is installed, the LCD is displayed in Component Info or System Info.
You can view its version.
The LCD information page varies slightly according to iBMC versions. For details, see the
iBMC online help.
Step 4 View and record the current iBMC, BIOS, and LCD versions.
Step 5 Compare the version information obtained in Step 4 with the version of the
firmware update package.
● If the versions are the same, the current iBMC, BIOS, and LCD versions are the
latest. No upgrade is required.
● If the version numbers obtained in Step 4 are smaller than that of the
firmware update package, update the firmware.
----End

4.8 Checking Server Alarms

Scenarios
Check alarms generated by the server.

Prerequisites
Conditions
iBMC WebUI.
Data
Procedure
Step 1 Choose Information on the main menu.
Step 2 In the navigation tree, choose Information Summary, as shown in Figure 4-27.
Figure 4-27 Basic Info page
Step 3 In the Device Health Status area, check alarms of all severities.

● : indicates a critical alarm. Critical alarms are generated for faults that may power
off devices, and even interrupt the system services. Immediate corrective measures are
required.
● : indicates a major alarm. Major alarms are generated for faults that may affect
normal running of the system or interrupt services.
● : indicates a minor alarm. Minor alarms are generated for the faults that do not
have major impact on the system. Prompt corrective measures are required to prevent
more serious faults.
Step 4 Choose Alarm & SEL on the main menu.

Step 5 In the navigation tree, choose Current Alarms, view the alarm information, as
Figure 4-28 Current Alarms page
----End

FusionServer Pro Rack Server Upgrade Guide 35

Uploaded by

Copyright:

Available Formats

FusionServer Pro Rack Server Upgrade Guide 35

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FusionServer Pro Rack Server Upgrade Guide 35

Uploaded by

Copyright:

Available Formats

FusionServer Pro Rack Server

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. i

About This Document

Indicates a hazard with a high level of risk which,

Indicates a hazard with a medium level of risk

Indicates a hazard with a low level of risk which,

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. ii

Indicates a potentially hazardous situation which,

Supplements the important information in the

Issue Date Description

35 2020-05-22 ● Added 1.16

34 2020-03-31 ● Modified 1.1.1.2

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. iii

Issue Date Description

33 2020-03-21 ● Added 1.12

32 2019-11-25 Modified 2.3.3.3 Rolling

31 2019-11-20 Modified 3.2.2 Using

30 2019-10-18 ● Deleted the methods

28 2019-05-22 ● Modified 1.8.3

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. iv

Issue Date Description

27 2019-03-11 Added 2.8.1 Upgrading

26 2019-01-16 ● Deleted the toolkit

25 2018-10-11 Added precautions for

24 2018-07-02 Added 1.1.3 Upgrading

23 2018-05-18 Deleted "Upgrading the

22 2018-04-20 ● Added 1.7.3

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. v

Issue Date Description

21 2018-02-13 Added description of

20 2017-11-28 ● Added description of

19 2017-11-28 Added description of

18 2017-11-08 Added description of

17 2017-09-15 Optimized description of

16 2017-08-15 Updated description of

15 2017-07-24 Updated description of

14 2017-06-22 Updated description of

13 2017-02-27 Updated description of

12 2017-01-20 Added description of the

11 2016-12-28 Optimized description of

10 2016-07-13 Added description of the

09 2015-01-07 Updated description of

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. vi

Issue Date Description

08 2014-12-24 Updated description of

07 2014-11-27 Updated description of

06 2014-10-25 Updated the default

05 2014-10-10 Updated description of

04 2014-09-15 Deleted the "Tecal"

03 2014-08-15 Added description of

02 2014-04-15 Added "Preparing for the

01 2014-02-15 This issue is the first

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. vii

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

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. viii

1.2.1.3 Rolling Back to the Source Version.......................................................................................................................... 19

Issue 35 (2020-05-22) Copyright © Huawei Technologies Co., Ltd. ix