iBMA V100R002 User Guide 01

iBMA
V100R002
User Guide
Issue 06
Date 2015-02-11
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. 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: http://www.huawei.com
Email: support@huawei.com
Huawei Proprietary and Confidential

Issue 06 (2015-02-11) i
Copyright © Huawei Technologies Co., Ltd.
iBMA
User Guide About This Document
About This Document
Purpose
This document describes the functions and common commands of the iBMA and explains
how to install, use, and troubleshoot the iBMA.
This document provides guidance for you to use the iBMA to manage and monitor server
components, including central processing units (CPUs), hard disks, dual in-line memory
modules (DIMMs), network interface cards (NICs), and basic input/output systems (BIOSs).
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
Symbol Conventions
The following table lists the symbols that may be found in this document.
Symbol Description
Indicates a hazard with a high level or medium level of
risk which, if not avoided, could result in death or
serious injury.
Indicates a hazard with a low level of risk which, if not
avoided, could result in minor or moderate injury.
Indicates a potentially hazardous situation that, if not

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
Indicates a tip that may help you solve a problem or save
time.
Provides additional information to emphasize or
supplement important points of the main text.
Issue 06 (2015-02-11) Huawei Proprietary and Confidential ii

iBMA
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by
vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by
vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by
vertical bars. A minimum of one item or a maximum of all
items can be selected.
[ x | y | ... ]* Optional items are grouped in brackets and separated by
vertical bars. You can select one or several items, or select
no item.
&<1-n> The parameter before the & sign can be repeated 1 to n
times.
# A line starting with the # sign is comments.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 06 (2015-02-11)
This issue is the sixth official release.
Type Change Description
Modified Modify the 2.3 Installing, Upgrading, and Uninstalling the iBMA on
Linux and 2.4 Installing, Upgrading, and Uninstalling the iBMA on
Windows.
Issue 05 (2014-12-02)
This issue is the fifth official release.
Issue 06 (2015-02-11) Huawei Proprietary and Confidential iii

iBMA

New Add the 1.4 Security Features and 4.5.3 Querying and Setting
Watchdog Parameters.
Modified Add 2.1 Verifying the Upgrade Package Integrity in 2 Installing and
Uninstalling the iBMA.
Adding the SNMP Sub-agent to the SNMP Service is updating,
renamed to 2.3.1 Configuring SNMP Service, moved to remarks before
Installing.
In 2.4.1 Installing and Uninstalling the Kbox Driver, modify the value
of Hardware lds in Kbox Devices.
Add Installing the SNMP Service in Windows 2012/2012 R2 in
2.4.2 Installing and Configuring the SNMP Service.
Issue 03 (2014-09-15)
This issue is the third official release.
Mode Change Description
Deleted "Tecal" is deleted from the product document.
Issue 02 (2014-07-20)
This issue is the second official release.
Add the method of querying events in the black box.
Add the safety information.
Issue 01 (2014-01-06)
This issue is the first official release.
Issue 06 (2015-02-11) Huawei Proprietary and Confidential iv

iBMA
User Guide Contents
Contents
About This Document .................................................................................................................... ii

1 Overview......................................................................................................................................... 1
1.1 Introduction to the iBMA ............................................................................................................................................. 1
1.2 Function Modules ......................................................................................................................................................... 2
1.3 Specifications and Features .......................................................................................................................................... 4
1.4 Security Features .......................................................................................................................................................... 5
1.4.1 Product Networking ................................................................................................................................................... 6
1.4.2 External Dependency ................................................................................................................................................. 6
1.4.3 Security Policy ........................................................................................................................................................... 6
1.4.4 Security Isolation ....................................................................................................................................................... 6
1.4.5 Anti-attack Measures for Protocols and Interfaces .................................................................................................... 6
1.4.6 Product Development, Release, and Installation Security ......................................................................................... 7
1.4.7 Security of System Management and Maintenance ................................................................................................... 7
2 Installing and Uninstalling the iBMA ...................................................................................... 8

2.1 Verifying the Upgrade Package Integrity ...................................................................................................................... 8
2.2 Precautions.................................................................................................................................................................... 8
2.3 Installing, Upgrading, and Uninstalling the iBMA on Linux ........................................................................................ 9
2.3.1 Configuring SNMP Service ....................................................................................................................................... 9
2.3.2 Installing .................................................................................................................................................................. 12
2.3.3 Upgrading ................................................................................................................................................................ 17
2.3.4 Uninstalling ............................................................................................................................................................. 19
2.4 Installing, Upgrading, and Uninstalling the iBMA on Windows ................................................................................ 20
2.4.1 Installing and Uninstalling the Kbox Driver ............................................................................................................ 20
2.4.2 Installing and Configuring the SNMP Service ......................................................................................................... 39
2.4.3 Installing Framework 4.0 ......................................................................................................................................... 52
2.4.4 Installing, Upgrading, and Uninstalling the hwBMAService .................................................................................. 54
2.4.5 Precautions for Windows Server 2012 or 2012 R2 .................................................................................................. 63
3 Using the iBMA ........................................................................................................................... 65

3.1 Common Functions ..................................................................................................................................................... 65
3.1.1 Logging In to the iBMA .......................................................................................................................................... 65
3.1.2 Setting an IP Address for the SNMP Server............................................................................................................. 66
3.1.3 Diagnosing a Hard Disk Fault.................................................................................................................................. 67
Issue 06 (2015-02-11) Huawei Proprietary and Confidential v

iBMA
User Guide Contents
3.1.4 Viewing Hard Disk Diagnosis Records ................................................................................................................... 68

3.1.5 Monitoring the SMART Status of a Hard Disk ........................................................................................................ 70
3.1.6 Monitoring DIMM ECC Status ............................................................................................................................... 74
3.1.7 Querying Platform MCE Events .............................................................................................................................. 75
3.1.8 Querying Events in the Black Box........................................................................................................................... 75
3.1.9 Controlling the Log Export Level ............................................................................................................................ 77
3.2 Common Faults and Solutions .................................................................................................................................... 78
3.2.1 Failed to Install the iBMA Software (1)................................................................................................................... 78
3.2.2 Failed to Install the iBMA Software (2)................................................................................................................... 78
3.2.3 Failed to Install the iBMA (3) .................................................................................................................................. 79
3.2.4 Failure to Find the Function Library After Running a Command ............................................................................ 80
3.2.5 Failed to Find a Command After a User Runs the Command .................................................................................. 80
3.2.6 Failed to Obtain Hard Disk Diagnosis Logs ............................................................................................................ 81
4 Command Reference .................................................................................................................. 82

4.1 Command Overview ................................................................................................................................................... 82
4.2 hwdiag Commands ..................................................................................................................................................... 82
4.2.1 Querying Hard Disk Status (disk) ............................................................................................................................ 82
4.2.2 Querying RAID Status (RAID)................................................................................................................................ 90
4.2.3 Querying DIMM Status (mem) ................................................................................................................................ 93
4.2.4 Querying Help Information ..................................................................................................................................... 95
4.2.5 Querying the Software Version ................................................................................................................................ 95
4.3 syscfg Commands ....................................................................................................................................................... 96
4.3.1 Querying Hard Disk Status ...................................................................................................................................... 96
4.3.2 Querying RAID Status ............................................................................................................................................. 97
4.3.3 Querying DIMM Status ........................................................................................................................................... 99
4.3.4 Querying CPU Status ............................................................................................................................................. 100
4.3.5 Querying BIOS Status ........................................................................................................................................... 101
4.3.6 Querying and Configuring Server System Information ......................................................................................... 102
4.3.7 Querying NIC Status .............................................................................................................................................. 106
4.3.8 Querying Basic Information About All Components ............................................................................................. 107
4.3.9 Performing Operations by Using the Monitor Module .......................................................................................... 111
4.3.10 Querying Help Information ................................................................................................................................. 117
4.3.11 Querying the Software Version ............................................................................................................................ 120
4.3.12 Obtaining and Configuring iBMC Information ................................................................................................... 121
4.3.13 Obtaining and Configuring Server Power Information ........................................................................................ 131
4.3.14 Obtaining and Configuring Server Fan Information ............................................................................................ 133
4.3.15 Sending the Raw IPMI Command ....................................................................................................................... 135
4.4 hwkbox Commands .................................................................................................................................................. 136
4.4.1 Viewing Help Information ..................................................................................................................................... 136
4.4.2 Viewing the Software Version................................................................................................................................ 137
4.4.3 Managing and Parsing the Kbox Image File .......................................................................................................... 138
Issue 06 (2015-02-11) Huawei Proprietary and Confidential vi

iBMA
User Guide Contents
4.4.4 Managing the Kbox User Area .............................................................................................................................. 140

4.5 hwwatchdog Commands ........................................................................................................................................... 141
4.5.1 Viewing Help Information ..................................................................................................................................... 142
4.5.2 Viewing the Software Version................................................................................................................................ 142
4.5.3 Querying and Setting Watchdog Parameters .......................................................................................................... 143
4.5.4 Starting, Restarting, and Stopping the Watchdog ................................................................................................... 144
5 Alarm Reference ........................................................................................................................ 146

5.1 #327686_The DIMM ECC Value Increases at a Rate Higher Than the Threshold or an Uncorrectable ECC Error Has
Occurred ......................................................................................................................................................................... 148
5.2 #327688_Memory ECC Value Increase Speed Restored to the Acceptable Range .................................................. 148
5.3 #196610_CPU Detected an MCE ............................................................................................................................. 149
5.4 #196612_CPU Detected That an MCE Rectified ..................................................................................................... 150
5.5 #196618_CPU Temperature Restored to the Acceptable Range ............................................................................... 150
5.6 #196620_CPU Temperature Higher Than the Major Alarm Threshold and Lower Than the Critical Alarm Threshold
........................................................................................................................................................................................ 151
5.7 #196622_CPU Sensor Detected Error or Temperature Too High ............................................................................. 151
5.8 #196624_Failed to Detect the CPU Temperature ..................................................................................................... 152
5.9 #262182_Hard Disk Inserted .................................................................................................................................... 153
5.10 #262184_Hard Disk Removed ................................................................................................................................ 153
5.11 #262190_Hard Disk Reported a Predictable Error ................................................................................................. 154
5.12 #262196_Hard Disk Score Lower Than 80 ............................................................................................................ 155
5.13 #262198_Hard Disk Offline ................................................................................................................................... 155
5.14 #262206_Failed to Detect Hard Disk Temperature ................................................................................................. 156
5.15 #262210_Hard Disk Temperature Restored to the Acceptable Range .................................................................... 157
5.16 #262212_Hard Disk Temperature Higher Than the Major Alarm Threshold and Lower Than the Critical Alarm
Threshold ........................................................................................................................................................................ 157
5.17 #262214_Hard Disk Temperature Higher Than the Critical Alarm Threshold ....................................................... 158
5.18 #262216_Direct Phyisical Hard Disk Inserted ........................................................................................................ 159
5.19 #262218_Direct Physical Hard Disk Removed ...................................................................................................... 159
5.20 #262224_Direct Physical Hard Disk Reported a Predictable Error ........................................................................ 160
5.21 #262228_Failed to Detect the Direct Physical Hard Disk Temperature ................................................................. 160
5.22 #262232_Direct Physical Hard Disk Temperature Restored to the Acceptable Range ........................................... 161
5.23 #262234_Direct Physical Hard Disk Temperature Higher Than the Major Alarm Threshold and Lower Than the
Critical Alarm Threshold ................................................................................................................................................ 162
5.24 #262236_Direct Physical Hard Disk Temperature Higher Than the Critical Alarm Threshold .............................. 162
5.25 #262242_Direct Physical Hard Disk Score Lower Than 80 ................................................................................... 163
5.26 #262146_RAID Controller Card Battery Charged Properly ................................................................................... 164
5.27 #262150_The RAID Controller Card Battery Learning Cycle Started ................................................................... 164
5.28 #262154_RAID Controller Card Battery Learning Cycle Delayed ........................................................................ 165
5.29 #262156_RAID Controller Card Battery Learning Cycle Ended ........................................................................... 165
5.30 #262158_Controller Batter Low ............................................................................................................................. 166
5.31 #262160_RAID Controller Card Battery Temperature Higher Than the Threshold ............................................... 167
Issue 06 (2015-02-11) Huawei Proprietary and Confidential vii

iBMA
User Guide Contents
5.32 #262162_RAID Controller Card Battery Removed ................................................................................................ 167

5.33 #262164_RAID Controller Card Battery Learning Timed Out .............................................................................. 168
5.34 #262166_Rebuilding a Virtual Disk Started ........................................................................................................... 168
5.35 #262168_Rebuilding a Virtual Disk Finished ......................................................................................................... 169
5.36 #262172_Consistency Check or Another Operation Failed on Virtual Disk .......................................................... 170
5.37 #262174_A Virtual Disk has been Created. ............................................................................................................ 170
5.38 #262176_Virtual Disk Deleted ............................................................................................................................... 171
5.39 #262178_Virtual Disk Degraded ............................................................................................................................ 171
5.40 #262180_Virtual Disk Failed .................................................................................................................................. 172
5.41 #65538_Memory Usage Upper Than Threshold ..................................................................................................... 172
5.42 #65540_Memory Usage Restored Normally .......................................................................................................... 173
5.43 #65542_CPU Usage Upper Than Threshold ........................................................................................................... 174
5.44 #65544_CPU Usage Restored Normally ................................................................................................................ 174
5.45 #65546_Disk Usage Upper Than Threshold ........................................................................................................... 175
5.46 #65548_Disk Usage Restored Normally................................................................................................................. 175
5.47 #65550_SWAP Usage Upper Than Threshold ........................................................................................................ 176
5.48 #65552_SWAP Usage Restored Normally .............................................................................................................. 176
5.49 #65554_Assigned Process Abnormal ..................................................................................................................... 177
5.50 #65566_Assigned Process Ok ................................................................................................................................ 177
5.51 #524290_The Monitor Service Started ................................................................................................................... 178
5.52 #393218_Service System Network Port Properly Connected ................................................................................. 179
5.53 #393220_Service System Network Port Not Connected ........................................................................................ 179
A Appendix ................................................................................................................................... 181

A.1 Obtaining Help ......................................................................................................................................................... 181
A.1.1 Preparing to Contact Huawei Technical Support .................................................................................................. 181
A.1.2 Obtaining Help from Huawei Support Website .................................................................................................... 182
A.2 Glossary ................................................................................................................................................................... 182
A.3 Acronyms and Abbreviations ................................................................................................................................... 184
Issue 06 (2015-02-11) Huawei Proprietary and Confidential viii

iBMA
User Guide 1 Overview
1 Overview
About This Chapter

This topic describes the basic functions, overall architecture, and features of the intelligent
server management software iBMA. It enables you to have a basic understanding of this
product.
1.1 Introduction to the iBMA
The iBMA enables you to manage and monitor server components, such as CPUs, hard disks,
dual in-line memory modules (DIMMs), network interface cards (NICs), and basic
input/output systems (BIOSs).
1.2 Function Modules
The iBMA consists of the command-line interface (CLI) module, monitor module, trap
module, and subfunction library that manages CPUs, dual in-line memory modules (DIMMs),
hard disks, network interface cards (NICs), and basic input/output systems (BIOSs). This
topic describes the functions of these modules and their relationships.
1.3 Specifications and Features
This topic describes the operating systems (OSs) supported by the iBMA and the features of
the iBMA.
1.4 Security Features
This topic describes the security features of the iBMA.
1.1 Introduction to the iBMA

The iBMA enables you to manage and monitor server components, such as CPUs, hard disks,
dual in-line memory modules (DIMMs), network interface cards (NICs), and basic
input/output systems (BIOSs).
Background
The iBMA is developed to meet the following customer requirements:
 Manages Huawei server components.
Issue 06 (2015-02-11) Huawei Proprietary and Confidential 1

iBMA
 Manages multiple servers on a local area network (LAN) by using the Simple Network
Management Protocol (SNMP) service.
Application Scenario
The iBMA provides the following management functions:
 Promptly detects the installation status and changes of components.
 Promptly monitors component health status.
 Promptly captures, reports, and stores alarms and events.
 Manages and operates hardware devices.
 Provides the command-line interface (CLI) for ease of management.
1.2 Function Modules

The iBMA consists of the command-line interface (CLI) module, monitor module, trap
module, and subfunction library that manages CPUs, dual in-line memory modules (DIMMs),
hard disks, network interface cards (NICs), and basic input/output systems (BIOSs). This
topic describes the functions of these modules and their relationships.
Figure 1-1 shows the iBMA architecture.
Figure 1-1 iBMA architecture
The relationships between the iBMA function modules, hardware platform, software platform,
and application layer are as follows:

iBMA
 The iBMA is located between the iBMC and operating system (OS).
 The iBMA provides some of the drivers on the software platform.
 The subfunction library obtains real-time information about the hardware platform by
invoking the shared library or drivers on the software platform.
 The monitor module provides real-time alarms and historical alarms of various
components based on the subfunction library.
 The monitor module sends alarms to the destination over the Simple Network
Management Protocol (SNMP) by invoking the trap module interface.
The destination refers to a client that receives SNMP trap information.
 The CLI module obtains real-time information about the hardware platform by invoking
the subfunction library and queries historical logs by connecting to the monitor module.
Table 1-1 describes the iBMA function modules.
Table 1-1 iBMA function modules
Module Function
CLI Allows users to manage and monitor devices by using commands to
promptly obtain information about component status, changes, and
faults.
Monitor  Obtains exception event information about subfunction modules,
such as hard disks, DIMMs, and CPUs, and records the
information as logs or reports the information over SNMP.
 Receives requests from local clients and sends back log
information about historical events.
Trap Provides an interface for the monitor module to send event
information.
CPU management  Obtains information about each CPU, including the CPU model,
CPU frequency, external clock frequency, number of CPU cores,
number of enabled cores, number of threads, and socket ID.
 Checks for correctable CPU machine check exceptions (MCEs)
based on device files provided by the OS in /dev/mcelog, and
reports alarms when detecting exceptions.
 Reports major MCEs to the OS kernel for handling.
DIMM  Queries information about each DIMM, including the slot
management number, voltage, model, capacity, serial number, and
manufacturer.
 Checks for DIMM error checking and correcting (ECC)
exceptions, and reports alarms when detecting exceptions.
 Supports online diagnosis of double data rate 3 (DDR3)
registered DIMMs (RDIMMs).
Hard disk  Queries the model and firmware version of each redundant array
management of independent disks (RAID) controller card.
 Obtains information about each RAID battery, including the
battery type, serial number, designed capacity, current capacity,
designed voltage, current voltage, current, status, number of
charges and discharges, and manufacturer.

iBMA
Module Function
 Obtains information about each hard disk, including the disk
capacity, manufacturer, type, serial number, and slot number.
 Obtains the RAID levels and status (normal, degraded, or offline)
of RAID logical disks, slot numbers of hard disks in each RAID
group, and mapping between OS drive letters and RAID groups.
 Supports hard disk assessment, background short self-test,
background extended self-test, and self-test record query.
 Monitors hard disk status (online or offline) and self-monitoring,
analysis and reporting (SMART) information, and reports alarms
when detecting exceptions.
NIC management  Obtains basic information about each network interface card
(NIC), including the manufacturer, model, firmware version,
driver name, and driver version.
 Obtains the status of each network port, including the Peripheral
Component Interconnect Express (PCIe) device number, working
rate, duplex status, auto-negotiation mode, and link status.
BIOS management  Queries the BIOS vendor, version number, and release date.
 Reads and modifies BIOS configuration.
 Upgrades the BIOS.
BIOS configuration remains unchanged after an upgrade.
Black box The black box records exceptions when the system crashes and
allows you to view the records by running commands.
1.3 Specifications and Features

This topic describes the operating systems (OSs) supported by the iBMA and the features of
the iBMA.
Hardware Specifications
Table 1-2 lists the OSs and functions supported by the iBMA. Typical server configurations
can meet iBMA installation requirements.
Table 1-2 Supported OSs
OS Function
SUSE 11.1/11.2/11.3 Command-line Interface (CLI), Simple Network
Redhat 5.7/6.1/6.2/6.3/6.4/6.5 Management Protocol (SNMP), Monitor, and
Hardware Platform Interface (HPI).
CentOS 6.3
VMWare 4.1 u2 CLI and Monitor
UVP V100R003C00SPC220B020 CLI

iBMA
OS Function
Windows 2008 SP2/Windwos 2008 Windows Management Instrumentation (WMI),
R2 SNMP, and CLI
Windows 2012/Windwos 2012 R2
 Windows CLI supports only some commands. For details, see the command reference.
 The black box function supports only Red Hat Enterprise Linux 6.1 or later and SUSE Linux
Enterprise Server 11 SP1 2.6.32.59 or later.
Product Features
The iBMA has the following features:
 Real-time capability
The iBMA provides WMI and Hardware Platform Interface (HPI) Application
Programming Interface (API) libraries to provide real-time information about the
operating status of hardware for the upper-layer platform.
 Availability
The iBMA can promptly detect the installation status and changes of components,
monitor the health status of components, and capture, report, and store alarms. The
iBMA can also allow you to manage and monitor components, such as CPUs, hard disks,
DIMMs, NICs, and BIOSs.
 Support for multiple software and hardware platforms
The iBMA supports various OSs. For details, see Table 1-2.
 Low system resource usage
The CPU and memory usage is lower than or equal to 3%.
 You must select the HPI service of a secure edition; otherwise, unauthorized users may
remote access the iBMA over the HPI port. For details about HPI service, contact Huawei
technical support.
 The security and performance vary according to SNMP versions. Select an appropriate
SNMP version and obtain the SNM software.
 WMI stands for Windows management instrumentation. It is a standard Windows interface,
and the security features are controlled by Windows.
1.4 Security Features

This topic describes the security features of the iBMA.

iBMA
1.4.1 Product Networking

The iBMA is a software-only product, which is installed on the server blade. The networking
varies according to the server application scenarios.
1.4.2 External Dependency

 The iBMA obtains the PSU, fan module, and iBMC information using the iBMC.
 The iBMA obtains system performance information in the OS, and obtains the
component model, manufacturer, and running status using the component drivers.
 The iBMA obtains the basic information about products and components in the
SMBIOS.
1.4.3 Security Policy

 CLI port: To invoke the CLI, you need to obtain the OS super user's right. The OS has
provided the user permission management mechanism.
 SNMP port: SNMP provides a certain access control security mechanisms which vary
according to the SNMP version. SNMP V3 provides high security, and SNMP V1 and
V2c are vulnerable.
 WMI port: To invoke the WMI remotely, you need to obtain the OS user's right. The OS
has provided the user permission management mechanism.
1.4.4 Security Isolation

 The iBMA is logically isolated from the user plane to ensure that user services are not
affected by the faulty iBMA.
 The iBMA that is an in-band management plane is running on the OS.
1.4.5 Anti-attack Measures for Protocols and Interfaces

 The iBMA provides only the necessary in-band management communication ports, such
as the SNMP, HPI, WMI, and CLI ports for the external system.
 The CLI and WMI ports use the OS access control mechanism. The users that can log in
to the server OS can access the CLI and WMI ports.
 The SNMP port uses the standard access authentication mechanisms. The actual
mechanism is provided by the SNMP agent service in the OS.
SNMP provides a certain access control security mechanisms which vary according to the SNMP
version. SNMP V3 provides high security, and SNMP V1 and V2c are vulnerable. You are advised to use
SNMP V3.
 The HPI access control mechanism is provided by the HPI service instead of the HPI
plug-in on the iBMA.
 The HPI service software is obtained from the OS installation package. Currently only the
openhpi-2.12 can be used.
 The HPI service software authentication mechanism is not strong. You are advised to develop a new
port or use the SNMP port to replace the HPI port of the same function, to meet the key data server
requirements.

iBMA
1.4.6 Product Development, Release, and Installation Security

 All external ports of the iBMA are required by users.
 The iBMA has been scanned by the antivirus software and no virus is found.
 The digital signature is added to ensure the software integrity.
 The static check, including the static security check, is performed on the iBMA code.
1.4.7 Security of System Management and Maintenance

 A functional access control mechanism is provided in the iBMA log modules or files to
control the accesses to user names and passwords. Users have obtained the administrator
or independent log administrator rights before deleting logs.
 The iBMA records the local device fault and important event logs.
 The important maintaining operation logs are recorded by the OS.

iBMA
User Guide 2 Installing and Uninstalling the iBMA
2 Installing and Uninstalling the iBMA
About This Chapter

This topic describes how to install and uninstall the iBMA, including the precautions,
procedures, and verification methods.
2.1 Verifying the Upgrade Package Integrity
2.2 Precautions
This topic describes the precautions for installing the iBMA.
2.3 Installing, Upgrading, and Uninstalling the iBMA on Linux
This topic describes how to install, upgrade, and uninstall the iBMA on Linux.
2.4 Installing, Upgrading, and Uninstalling the iBMA on Windows
This topic describes how to install and uninstall the iBMA on Windows.
2.1 Verifying the Upgrade Package Integrity

Verify that the obtained upgrade package is consistent with the original one at the website
http://support.huawei.com/enterprise.
Click and , load the digital certificate and software package respectively.
For details about the verification tool and method, visit the following link:
Software digital signature (OpenPGP) validation tool
2.2 Precautions
This topic describes the precautions for installing the iBMA.
Take the following precautions before the installation:
 Check the operating system (OS) version. Table 1-2 lists the OSs supported by iBMA.
The OSs are all 64-bit.
 Upload the iBMA installation package to the server.

iBMA
To download the iBMA installation package, log in to Huawei enterprise website and
choose Support > Software Downloads > IT Infrastructure > Server > APP Server >
BMA > V100R002.
2.3 Installing, Upgrading, and Uninstalling the iBMA on

Linux
This topic describes how to install, upgrade, and uninstall the iBMA on Linux.
2.3.1 Configuring SNMP Service

Procedure
Step 1 Log in to the OS as user root.
Step 2 Open the snmpd.conf file.
linux-suse11:/opt/huawei/bma/bin # cd /etc/snmp
linux-suse11:/opt/huawei/bma/bin # vim snmpd.conf
Step 3 Add a user.

1. Configure users for the V1 and V2C versions.
####
# First, map the community name "public" into a "security name"
# sec.name source community

com2sec notConfigUser default public
com2sec snmpV3User default public
com2sec abc default public
com2sec ismUser default public
com2sec ismV3User default public
com2sec ropublic default public
In the command output, ismUser specifies a user name, default requests the source IP
address, and public specifies a community name.
Step 4 Add the user to a user group.
####
# Second, map the security name into a group name:
# groupName securityModel securityName

group notConfigGroup v1 notConfigUser
group notConfigGroup v2c notConfigUser
group snmpV3Group tcm snmpV3User
group snmpV3Group tcm abc
group ismGroup v1 ismUser
group snmpV3Group tcm ismV3User
Step 5 Add the MIB view of the iBMA software.

iBMA
The hwismsnmpd sub-agent manages the objects defined in the MIB library. The OIDs of
these objects must be added to the snmpd.conf file.
####
# Third, create a view for us to let the group have rights to:
# Make at least snmpwalk -v 1 localhost -c public system fast again.

# name incl/excl subtree mask(optional)
view systemview included .1
view systemview included .1.3.6.1.2.1.1
view systemview included .1.3.6.1.2.1.25.1.1
view ismview included .1.3.6.1.4.1.2011.2.235.4.1
Step 6 Set the access control rights.

####
# Finally, grant the group read-only access to the systemview view.
# group context sec.model sec.level prefix read write notif

access notConfigGroup "" any noauth exact systemview none none
access snmpV3Group "" tcm priv exact systemview systemview none
access ismGroup "" usm priv exact ismview none none
Add a login user.

#xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxv3
#rwuser snmpV3User priv
#rwuser -s usm abc priv #-V systemview
#xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxV3
createUser snmpV3User MD5 "12345678" DES "12345678"
createUser abc SHA "12345678" DES "12345678"
createUser ismV3User MD5 "12345678" DES "12345678"
or
createUser ismV3User SHA "12345678" DES "12345678"
rwuser ismV3User
rwuser abc
rwcommunity ropublic
rwuser snmpV3User
MD5 and SHA indicates the authentication algorithm, and DES indicates the encryption
algorithm.
Step 7 Configure SNMP Service in the snmpd.conf file.

iBMA
 Run the dlmod bmaSNMP /opt/huawei/bma/lib64/libbmaSNMP.so command if the

iBMA version is 5.11 or later.
 Run the master agentx command if the iBMA version is 5.10 or earlier.
# For specific usage information, see the man/snmpd.conf.5 manual page # as well as
the local/passtest script used in the above example.
# add by huc. #snmp master agent (iBMA 5.11 and later versions) dlmod bmaSNMP
/opt/huawei/bma/lib64/libbmaSNMP.so
#snmp sub-agent (iBMA 5.10 and earliest versions) #master agentx
Configure the user access permission.

rwuser ismV3User
rwuser abc
rwcommunity ropublic
rwuser snmpV3User
Run the syscfg -v command to view the iBMA version.
Step 8 Save the configuration file and exit.

wq
Step 9 Set the SNMP port.

Start the firewall and set the following information for the SNMP port:
1. Red Hat OSs:
Run the vi /etc/sysconfig/iptables command to open the iptables file and add the
command displayed in the following screen to the file.
[root@localhost ~]# cat /etc/sysconfig/iptables
# Generated by iptables-save v1.4.7 on Tue Apr 29 20:09:28 2014
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [22:2712]
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -p udp --dport 161 -j ACCEPT
-A OUTPUT -p udp --sport 161 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A FORWARD -j REJECT --reject-with icmp-host-prohibited
COMMIT
# Completed on Tue Apr 29 20:09:28 2014

iBMA
The command is added only before the -A INPUT -j REJECT --reject-with

icmp-host-prohibited command.
Run the /etc/init.d/iptables restart command to restart the firewall and enable the
setting to take effect.
2. SUSE OSs:
Open the /etc/sysconfig/SuSEfirewall2 file, check for
FW_SERVICES_EXT_UDP="", and set it to 161 as shown below.
FW_SERVICES_EXT_UDP="161"
Run the rcSuSEfirewall2 restart command to restart the firewall and enable the setting
to take effect.
----End
2.3.2 Installing
Prerequisites
The iBMA installation packages huawei-ISM-server-management-x.x.tar.gz and
huawei-ISM-server-management-driver-x.x.tar.gz have been uploaded to any directory on
the server.
This topic uses huawei-ISM-server-management-5.18.tar.gz and
huawei-ISM-server-management-drivers-5.18.tar.gz as examples.
Context
This topic assumes that the iBMA is to be installed on a server running SUSE 11 and that the
installation packages are in /tmp.
You can use the same method to install the iBMA on a server running another type of
operating system (OS).
Procedure
Step 1 Log in to OS as user root.
Step 2 Go to the directory where the installation packages are stored.
linux-suse11:/tmp # cd iBMA$linux$\ v5.18/app/

linux-suse11:/tmp/iBMA(linux) v5.18/app # ls
huawei-ISM-server-management-5.1.8.tar.gz
Step 3 Install the iBMA software package.

1. Decompress the software package.
linux-suse11:/tmp/iBMA(linux) v5.18/app # tar -zxvf

huawei-ISM-server-management-5.1.8.tar.gz

iBMA
huawei-ISM-server-management-5.1.8/
huawei-ISM-server-management-5.1.8/selinux.sh
huawei-ISM-server-management-5.1.8/ESX4/
huawei-ISM-server-management-5.1.8/ESX4/ISM-service-5.1.8-1.el5.i386.rpm
huawei-ISM-server-management-5.1.8/ESX4/ISM-cli-5.1.8-1.el5.i386.rpm
huawei-ISM-server-management-5.1.8/ESX4/upgrade.sh
huawei-ISM-server-management-5.1.8/ESX4/install.sh
huawei-ISM-server-management-5.1.8/ESX4/ISM-lib-5.1.8-1.el5.i386.rpm
huawei-ISM-server-management-5.1.8/utils.sh
huawei-ISM-server-management-5.1.8/uninstall.sh
huawei-ISM-server-management-5.1.8/README
huawei-ISM-server-management-5.1.8/SLES11/
huawei-ISM-server-management-5.1.8/SLES11/ISM-service-5.1.8-1.sles11.x86_64.rpm
huawei-ISM-server-management-5.1.8/SLES11/ISM-lib-5.1.8-1.sles11.x86_64.rpm
huawei-ISM-server-management-5.1.8/SLES11/ISM-cli-5.1.8-1.sles11.x86_64.rpm
huawei-ISM-server-management-5.1.8/SLES11/upgrade.sh
huawei-ISM-server-management-5.1.8/SLES11/install.sh
huawei-ISM-server-management-5.1.8/setup.sh
huawei-ISM-server-management-5.1.8/RHEL5/
huawei-ISM-server-management-5.1.8/RHEL5/ISM-service-5.1.8-1.el5.x86_64.rpm
huawei-ISM-server-management-5.1.8/RHEL5/ISM-lib-5.1.8-1.el5.x86_64.rpm
huawei-ISM-server-management-5.1.8/RHEL5/upgrade.sh
huawei-ISM-server-management-5.1.8/RHEL5/install.sh
huawei-ISM-server-management-5.1.8/RHEL5/ISM-cli-5.1.8-1.el5.x86_64.rpm
huawei-ISM-server-management-5.1.8/RHEL5U4/
huawei-ISM-server-management-5.1.8/RHEL5U4/upgrade.sh
huawei-ISM-server-management-5.1.8/RHEL5U4/install.sh
huawei-ISM-server-management-5.1.8/RHEL6/
huawei-ISM-server-management-5.1.8/RHEL6/upgrade.sh
huawei-ISM-server-management-5.1.8/RHEL6/ISM-cli-5.1.8-1.el6.x86_64.rpm
huawei-ISM-server-management-5.1.8/RHEL6/install.sh
huawei-ISM-server-management-5.1.8/RHEL6/ISM-lib-5.1.8-1.el6.x86_64.rpm
huawei-ISM-server-management-5.1.8/RHEL6/ISM-service-5.1.8-1.el6.x86_64.rpm
linux-suse11:/tmp/iBMA(linux) v5.18/app # cd huawei-ISM-server-management-5.
2. Go to the iBMA installation directory.

linux-suse11:/tmp/iBMA(linux) v5.18/app # cd huawei-ISM-server-management-5.1.8/
linux-suse11:/tmp/iBMA(linux) v5.18/app/huawei-ISM-server-management-5.1.8 # ls
ESX4 README RHEL5 RHEL5U4 RHEL6 SLES11 selinux.sh setup.sh uninstall.sh
utils.sh
linux-suse11:/tmp/iBMA(linux) v5.18/app/huawei-ISM-server-management-5.1.8 #
3. Install the iBMA.
linux-suse11:/tmp/iBMA(linux) v5.18/app/huawei-ISM-server-management-5.1.8 # sh
setup.sh install monitor=yes snmp=yes
Preparing... ########################################### [100%]
1:ISM-lib ########################################### [100%]
[ OK ]: install ISM-lib successfully :)

Preparing... ########################################### [100%]
1:ISM-cli ########################################### [100%]
[ OK ]: install ISM-cli successfully :)

iBMA
Preparing... ########################################### [100%]

1:ISM-service ########################################### [100%]
insserv: Service network is missed in the runlevels 4 to use service hwismmonitord
insserv: Service syslog is missed in the runlevels 4 to use service hwismmonitord
hwismmonitord 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[ OK ]: install ISM-service successfully :)

[ OK ]: Start ISM service successfully :)
[ OK ]: Start ISM snmpd successfully :)
The iBMA commands is saved in /opt/huawei/bma/bin.

linux-suse11:~ # cd /opt/huawei/bma/bin/
linux-suse11:/opt/huawei/bma/bin # ls
hwdiag hwkbox hwwatchdog syscfg
Observe the following statements when you install the iBMA in Red Hat.
 The selinux script is run automatically when the iBMA is installed. Add a security policy to the
system to allow the SNMP process to communicate with the iBMA process.
 If the policycoreutils-python package does not exist, the iBMA may be not installed successfully.
For details about how to install the iBMA successfully, see 3.2.3 Failed to Install the iBMA (3).
Step 4 Install drivers.

1. Decompress the driver package.
linux-suse11:/tmp/iBMA(linux) v5.18/driver # tar -zxvf
huawei-ISM-server-management-drivers-5.1.8.tar.gz
huawei-ISM-server-management-drivers-5.1.8/
huawei-ISM-server-management-drivers-5.1.8/RHEL62/
huawei-ISM-server-management-drivers-5.1.8/RHEL62/cpu/
huawei-ISM-server-management-drivers-5.1.8/RHEL62/cpu/cpu_temp_slave.ko
huawei-ISM-server-management-drivers-5.1.8/RHEL62/cpu/cpu_diag_slave.ko
huawei-ISM-server-management-drivers-5.1.8/RHEL62/watchdog/
huawei-ISM-server-management-drivers-5.1.8/RHEL62/watchdog/bsp_wd_driver.ko
huawei-ISM-server-management-drivers-5.1.8/RHEL62/kbox/
huawei-ISM-server-management-drivers-5.1.8/RHEL62/kbox/kbox.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/cpu/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/cpu/cpu_temp_s
lave.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/cpu/cpu_diag_s
lave.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/bios/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/bios/mem_alloc
.ko

iBMA
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/kbox/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R001C03SPC300/kbox/kbox.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/cpu/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/cpu/cpu_temp_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/cpu/cpu_diag_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/watchdog/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/watchdog/bsp_wd_driver.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/kbox/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP2/kbox/kbox.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/cpu/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/cpu/cpu_te
mp_slave.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/cpu/cpu_di
ag_slave.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/bios/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/bios/mem_a
lloc.ko
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/kbox/
huawei-ISM-server-management-drivers-5.1.8/UVP-V100R003C00SPC220B020/kbox/kbox.
ko
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/cpu/
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/cpu/cpu_temp_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/cpu/cpu_diag_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/watchdog/
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/watchdog/bsp_wd_driver.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/kbox/
huawei-ISM-server-management-drivers-5.1.8/SLES11RTOS/kbox/kbox.ko

iBMA
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/cpu/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/cpu/cpu_temp_sla
ve.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/cpu/cpu_diag_sla
ve.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/watchdog/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/watchdog/bsp_wd_
driver.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/kbox/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP1/2.6.32.59/kbox/kbox.ko
ve.ko
ve.ko
driver.ko
ve.ko
ve.ko
driver.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/cpu/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/cpu/cpu_temp_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/cpu/cpu_diag_slave.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/watchdog/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/watchdog/bsp_wd_driver.ko
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/kbox/
huawei-ISM-server-management-drivers-5.1.8/SLES11SP3/kbox/kbox.ko
linux-suse11:/tmp/iBMA(linux) v5.18/driver #
2. Go to the OS directory on the server.

linux-suse11:/tmp/iBMA(linux) v5.18/driver # cd
huawei-ISM-server-management-drivers-5.1.8/
linux-suse11:/tmp/iBMA(linux)
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8 # ls
RHEL61 RHEL62 RHEL63 RHEL64 RHEL65 SLES11RTOS SLES11SP1 SLES11SP2
SLES11SP3 UVP-V100R001C03SPC300 UVP-V100R003C00SPC220B020
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8 #
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8 # cd SLES11SP3

iBMA
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8/SLES11SP3 # ls
cpu kbox watchdog
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8/SLES11SP3 #
Run the cat /etc/issue command to view the OS version, and install the drivers based on the actual OS
versions. for example:
 RHEL61 indicates Red Hat Enterprise Linux Server release 6.1.
 RHEL63 indicates Red Hat Enterprise Linux Server release 6.3.
 SLES11SP1 indicates SUSE Linux Enterprise Server 11 SP1.
 SLES11SP2 indicates SUSE Linux Enterprise Server 11 SP2.
3. Copy the drivers to the drivers directory.
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8/SLES11SP3 # cp *
/opt/huawei/bma/drivers/ -r
v5.18/driver/huawei-ISM-server-management-drivers-5.1.8/SLES11SP3 # cd
/opt/huawei/bma/drivers/
linux-suse11:/opt/huawei/bma/drivers # ls
cpu kbox watchdog
Since drivers run on the kernel, no driver is installed for the iBMA by default to ensure the security of
the service system. The .ko files are provided for drivers. The driver installation policy is determined by
the customer. The driver fails after the system resets. It cannot be installed automatically.
 kbox.ko: The file is stored in /opt/huawei/bma/drivers/kbox. Load the driver on the hwkbox CLI
before you use the blade box function.
 cpu_temp_slave.ko: The file is stored in /opt/huawei/bma/drivers/cpu. The driver is mandatory
for the V1 servers, RH5885 V2, XH310, XH311, and the servers that are not listed in the iBMA
Compatibility List.
 cpu_diag_slave.ko: The file is stored in /opt/huawei/bma/drivers/cpu. Load the driver before you
use the dynamically disabling of CPU cores function.
 bsp_wd_driver.ko: The file is stored in /opt/huawei/bma/drivers/watchdog. When a fault occurs
in the server, for example, a PCIe device or CPU is faulty, the memory is used up, or the OS stops
scheduling as the failure of key OS components, such as the file system, regularly enable the
automatic recovery function of the system by using the watchdog drive.
4. Install the kbox driver.
linux-suse11:/opt/huawei/bma/drivers/kbox # insmod kbox.ko
5. Install the watchdog driver.
linux-suse11:/opt/huawei/bma/drivers/watchdog # insmod bsp_wd_driver.ko
Other drivers are automatically loaded with applications if necessary.
----End
2.3.3 Upgrading
Prerequisite
The target version must be later than the current version.

iBMA
Procedure
Step 1 Go to the directory where the installation packages are stored.
Step 2 Decompress the software package.
Step 3 Go to the iBMA installation directory.
linux-suse11:/tmp/iBMA(linux) v5.18/app # cd huawei-ISM-server-management-5.1.8/
utils.sh
Step 4 Upgrade the iBMA.
 The iBMA is upgraded only from an earlier version to a later version.

 Check whether the iBMA is installed. An upgrade failure message will be displayed if you
perform upgrade directly.
setup.sh upgrade
Preparing... ########################################### [100%]
1:ISM-lib ########################################### [100%]
[ OK ]: upgrade ISM-lib successfully :)

Preparing... ########################################### [100%]
1:ISM-cli ########################################### [100%]
[ OK ]: upgrade ISM-cli successfully :)

Preparing... ########################################### [100%]
1:ISM-service ########################################### [100%]
insserv: Service network is missed in the runlevels 4 to use service hwismmonitord
insserv: Service syslog is missed in the runlevels 4 to use service hwismmonitord
hwismmonitord 0:off 1:off 2:on 3:on 4:on 5:on 6:off
hwismmonitord 0:off 1:off 2:off 3:off 4:off 5:off 6:off
[ OK ]: upgrade ISM-service successfully :)

[ OK ]: Restart ISM service successfully :)
[ OK ]: Restart ISM snmpd successfully :)
Step 5 Upgrade the driver.

1. Uninstall the driver manually. For details about how to uninstall the driver, see Uninstall
the driver. Run the lsmod command to check whether the uninstallation is complete.
2. Install the driver. For details about how to install the driver, see Install the driver. Run
the lsmod command to check whether the installation is complete.
----End

iBMA
2.3.4 Uninstalling
Context
Uninstall the iBMA in one of the following scenarios:
 The iBMA is not required any longer.
 The iBMA is faulty and cannot be recovered by using the method described in 3.2
Common Faults and Solutions.
Procedure
Step 1 Uninstall the kbox and watchdog drivers.
Go to the iBMA installation directory, run the rmmod kbox command to uninstall the kbox
driver, and run the lsmod|grep kbox command to check whether the kbox driver is
successfully uninstalled.
linux-suse11:~ # cd /opt/huawei/bma/drivers
linux-suse11:/opt/huawei/bma/drivers # ls
cpu kbox watchdog
linux-suse11:/opt/huawei/bma/drivers # rmmod kbox
linux-suse11:/opt/huawei/bma/drivers # lsmod|grep kbox
Run the rmmod bsp_wd_driver command to uninstall the watchdog driver, and run the
lsmod|grep bsp_wd_driver command to check whether the watchdog driver is successfully
uninstalled.
linux-suse11:/opt/huawei/bma/drivers # rmmod bsp_wd_driver
linux-suse11:/opt/huawei/bma/drivers # lsmod|grep bsp_wd_driver
You need to manually uninstall the kbox and watchdog drivers. Other drivers are automatically
uninstalled with applications.
Step 2 Go to the iBMA installation directory.
utils.sh
Step 3 Uninstall the iBMA.

uninstall.sh
----End

iBMA
2.4 Installing, Upgrading, and Uninstalling the iBMA on

Windows
This topic describes how to install and uninstall the iBMA on Windows.
Prerequisites
When installing the iBMA on Windows, you need to install the kbox driver, Simple Network
Management Protocol (SNMP) service, and then hwBMAService service in sequence. If you
install the hwBMAService service before the kbox driver or SNMP service, some functions of
the iBMA are unavailable.
2.4.1 Installing and Uninstalling the Kbox Driver

Installing the iBMA on Windows Server 2008
Step 1 Ensure that the iBMC supports the kbox function and that this function is enabled.
 The iBMC V1 of the version 3.60 or later supports the black box function. You can log in
to the iBMC V1 Web, choose Download Data > Black Box on the iBMC V1 web user
interface (WebUI).
 To enable the kbox function on the iBMC V2. You can log in to the iBMC V2 Web,
choose Diagnosis > Black Box on the iBMC V2 web user interface (WebUI).
Step 2 Right-click Computer and choose Manager from the shortcut menu to open Server Manager.
See Figure 2-1.
Figure 2-1 Server Manager
Step 3 Choose Diagnostics > Device Manager, and check whether Class for kbox Devices exists in
the device list. See Figure 2-2.
 If yes, the kbox driver has been installed.
 If no, the kbox driver has not been installed. Go to Step 4.

iBMA
Figure 2-2 Device Manager
Step 4 Check for PCI Data Acquisition and Signal Processing Controller under Other Devices, If
there are multiple PCI Data Acquisition and Signal Processing Controllers in Other
Devices, right-click a PCI Data Acquisition and Signal Processing Controller, and choose
Properties from the shortcut menu, as shown in Figure 2-3.

iBMA
Figure 2-3 Other Devices
 If the server platform is iBMC V1, choose Details > Property > Hardware lds, and
select PCI\VEN_19AA&DEV_E004* in the Kbox Device Properties window, See
Figure 2-4.

iBMA
Figure 2-4 Hardware lds of the Kbox drivers on the iiBMC V1 platform
 If the server platform is iBMC V2, choose Details > Property > Hardware lds, and
select PCI\VEN_19E5&DEV_1710* in the Kbox Device Properties window, See
Figure 2-5.

iBMA
Figure 2-5 Hardware lds of the Kbox drivers on the iBMC V2 platform
Step 5 Right-click PCI Data Acquisition and Signal Processing Controller and choose Update
Driver Software from the shortcut menu. See Figure 2-6.
Figure 2-6 Update Driver Software
Step 6 Click Browse my computer for driver software. See Figure 2-7.

iBMA
Figure 2-7 Upgrade Driver Software
Step 7 Select the directory for storing the driver. See Figure 2-8.
 For Windows Server 2008 R2, select ..\kbox driver\Windows 2008 R2.
 For Windows Server 2008 SP2, select ..\kbox driver\Windows 2008.
Figure 2-8 Selecting the directory for storing the driver

iBMA
Step 8 In the dialog box shown in Figure 2-9, select Install this driver software anyway.
Figure 2-9 Install this driver software anyway
Step 9 Finish installing the driver by following the wizard.

If the information shown in Figure 2-10 is displayed, Kbox Devices are incompatible with
PCI Data Acquisition and Signal Processing Controller.
Figure 2-10 Information displayed (1)
To handle the compatiblity problem, perform the following steps:

 If the server platform is iBMC V1, choose Details > Property > Hardware lds, and select
PCI\VEN_19AA&DEV_E004* in the Kbox Device Properties window, see Figure 2-4.

iBMA
PCI\VEN_19E5&DEV_1710* in the Kbox Device Properties window, see Figure 2-5.
If the information shown in Figure 2-11 is displayed, repeat Step 4 to Step 8 for the other PCI
Data Acquisition and Signal Processing Controller.
When the installation is complete, Kbox Device is displayed in the device list. See Figure
2-12.
Figure 2-12 Installation result

iBMA
If the kbox driver is updated during use, a dialog box may be displayed, prompting you to restart the
server.
----End
Installing the iBMA on Windows Server 2012/2012 R2

Step 1 Ensure that the iBMC supports the kbox function and that this function is enabled.
 The iBMC V1 of the version 3.60 or later supports the black box function. You can log in
to the iBMC V1 Web, choose Download Data > Black Box on the iBMC V1 web user
interface (WebUI).
 To enable the kbox function on the iBMC V2. You can log in to the iBMC V2 Web,
Step 2 Install the certificate.
1. Run the Kbox-Package.cer file in the Windows 2012 driver directory. See Figure 2-13.
Figure 2-13 Windows 2012 driver directory
2. Run the KboxPackage.cer file in the Windows 2012 R2 driver directory. See Figure
2-14.
Figure 2-14 Windows 2012 R2 driver directory
The certificate installation dialog box shown in Figure 2-15 is displayed.

iBMA
Figure 2-15 Certificate installation dialog box
3. Click Install Certificate.

The Certificate Import Wizard dialog box is displayed.
4. Select Local Computer and click Next.
The certificate storage dialog box shown in Figure 2-16 is displayed.

iBMA
Figure 2-16 Certificate storage dialog box
5. Select Place all certificates in the following store.

6. Click Browse.
7. In the Select Certificate Store dialog box, select Trusted Root Certification
Authorities and click OK.
8. In the Completing the Certificate Import Wizard dialog box, click Finish.
After the certificate is successfully installed, the message "The import was successful" is
displayed.
Step 3 Click Server Manager > Tools > Computer Management, as shown in Figure 2-17.

iBMA
Figure 2-17 Device Manager
Step 4 The Figure 2-18 is displayed, check whether Class for kbox Devices exists.
Figure 2-18 Computer Management
 If yes, the kbox driver has been installed.

 If no, the kbox driver has not been installed. Go to Step 5.
Step 5 Check for PCI Data Acquisition and Signal Processing Controller under Other Devices, If
there are multiple PCI Data Acquisition and Signal Processing Controllers in Other
Devices, right-click a PCI Data Acquisition and Signal Processing Controller, and choose
Properties from the shortcut menu, as shown in Figure 2-19.

iBMA
Figure 2-19 Other Drivers
 If the server platform is iBMC V1, choose Details > Property > Hardware lds in the
Kbox Device Properties window, and select PCI\VEN_19AA&DEV_E004*, as shown
in Figure 2-20.

iBMA
Figure 2-20 Hardware lds of the Kbox drivers on the iBMC platform
 If the server platform is iBMC V2, choose Details > Property > Hardware lds in the
Kbox Device Properties window, and select PCI\VEN_19E5&DEV_1710*, as shown
in Figure 2-21.

iBMA
Figure 2-21 Hardware lds of the Kbox drivers on the iBMC platform
Step 6 Under Other devices, right-click PCI Data Acquisition and Signal Processing Controller,
and choose Update Driver Software from the shortcut menu.
The Update Driver Software dialog box is displayed, as shown in Figure 2-22.

iBMA
Figure 2-22 Update Driver Software dialog box
Step 7 Click Browse my computer for driver software.

Step 8 Click Browse, locate the required driver based on the operating system (OS) type, and click
Next.
The Windows Security dialog box is displayed.
Step 9 Click Install this driver software anyway.
Step 10 Finish installing the driver by following the wizard.
If the information shown in Figure 2-23 is displayed, Kbox Devices are incompatible with
PCI Data Acquisition and Signal Processing Controller, repeat Step 5 to Step 9 for the
other PCI Data Acquisition and Signal Processing Controller.

iBMA
To handle the compatiblity problem, perform the following steps:

PCI\VEN_19AA&DEV_E004* in the Kbox Device Properties window, see Figure 2-20, see
Figure 2-20.
PCI\VEN_19E5&DEV_1710* in the Kbox Device Properties window, see Figure 2-21.
If the information shown in Figure 2-24 is displayed, Kbox Device is successfully installed.

iBMA
When the installation is complete, Kbox Device is displayed in the device list. See Figure
2-25.
If the kbox driver is updated during use, a dialog box may be displayed, prompting you to restart the
server.
----End

iBMA
Uninstalling the Kbox Driver

This topic describes how to uninstall the kbox driver. This topic uses Windows 2008 as an
example. You can use the same method to uninstall the kbox driver on Windows 2012.
Step 1 Right-click Computer and choose Manager from the shortcut menu to open Server Manager.
See Figure 2-26.
Figure 2-26 Server Manager
Step 2 Choose Diagnostics > Device Manager, and check whether Class for kbox Devices exists in
the device list. See Figure 2-27.
Figure 2-27 Device list
Step 3 Right-click Kbox Device and choose Uninstall from the shortcut menu. See Figure 2-28.

iBMA
Figure 2-28 Choosing Uninstall
Step 4 In the displayed dialog box, select Delete the driver software for this device and click OK.
See Figure 2-29.
Figure 2-29 Uninstalling the kbox driver
----End
2.4.2 Installing and Configuring the SNMP Service

Installing the SNMP Service
The Simple Network Management Protocol (SNMP) service is supported by Windows 2008
but is not installed by default. You need to add this service manually.
Step 1 Choose Start > Computer > Manager to open Server Manager.
Step 2 Choose Server Manager > Features, and view enabled features. See Figure 2-30.

iBMA
Figure 2-30 Viewing enabled features
Step 3 If the SNMP service is unavailable, right-click Features and choose Add Features from the
shortcut menu. See Figure 2-31.

iBMA
Figure 2-31 Choosing Add Features
Step 4 In the Select Features window, select SNMP Services and click Next. See Figure 2-32.

iBMA
Figure 2-32 Select Features window
Step 5 Confirm the features to be installed, and click Install.

iBMA
Figure 2-33 Confirm Installation Selections window
When the installation is complete, the Installation Results window is displayed. See Figure
2-34.

iBMA
Figure 2-34 Installation Results window
----End
Installing the SNMP Service in Windows 2012/2012 R2

The SNMP service is supported by Windows 2012/2012 R2 but is not installed by default.
You need to add this service manually.
Step 1 Select Add roles and features in the Server ManagerDashboard window, as shown in
Figure 2-35.

iBMA
Figure 2-35 Installing the SNMP service wizard
Step 2 Click Next in the Add roles and features > Before You Begin window, as shown in Figure
2-36.
Figure 2-36 Starting the installation
Step 3 Select Role-based or feature-based installation in the Add roles and features >
Installation Type window, and click Next, as shown in Figure 2-37.

iBMA
Figure 2-37 Selecting an installation type
Step 4 Select Select a server from the server pool in the Add roles and features > Server
Selection window, and select a server, as shown in Figure 2-38.
Figure 2-38 Selecting a server
Step 5 Click Next in the Add roles and features > Server Roles window, as shown in Figure 2-39.

iBMA
Figure 2-39 Selecting a server role
Step 6 Select SNMP Service in the Add roles and features > Features window, as shown in Figure
2-40.
Figure 2-40 Selecting the SNMP service
Step 7 Select Add Features in the Add roles and features > Features window, choose SNMP
Service > SNMP WMI Provider, and then click Next, as shown in Figure 2-41.

iBMA
Figure 2-41 Adding the SNMP WMI feature
Step 8 Click install in the Add roles and features > Confirmation window, as shown in Figure
2-42.

iBMA
Figure 2-42 Confirming Installation
Step 9 The Add roles and features > Results is displayed, as shown in Figure 2-43.
Figure 2-43 Installation progress
Step 10 The installation is complete, as shown in Figure 2-44.

iBMA
----End
Configuring the SNMP Service

This topic describes the typical configuration of the SNMP service.
The configuration methods of the SNMP service are the same in Windows 2012/2012 R2 and in
Windows 2008.
 To enable the SNMP client to obtain information, configure the SNMP service as follows:
Right-click SNMP Service and choose Properties from the shortcut menu, or
double-click SNMP Service to open the SNMP Service Properties dialog box. Click
the Security tab and set the parameters. See Figure 2-45.

iBMA
Figure 2-45 Security tab page
 To enable the SNMP service to send trap information to the SNMP client, configure the
SNMP service as follows: Right-click SNMP Service and choose Properties from the
shortcut menu, or double-click SNMP Service to open the SNMP Service Properties
dialog box. Click the Traps tab and set the parameters. See Figure 2-46.
Figure 2-46 Traps tab page
----End

iBMA
2.4.3 Installing Framework 4.0

The iBMA is dependent on Framework 4.0. You can successfully install the iBMA only after
installing the Framework 4.0.
You need to install Framework 4.0 on Huawei servers to be managed. The Framework 4.0
installation package is available on the Microsoft website at the following URL:
http://www.microsoft.com/en-us/download/details.aspx?id=17718
Install Framework 4.0 for Windows Server 2008 or 2008 R2.
Step 1 Download the Framework 4.0 full installation package (for example,
dotNetFx40_Full_x86_x64.exe) from the Microsoft website.
Step 2 Run the installation package to open the installation wizard. In the window shown in Figure
2-47, select I have read and accept the license terms.
Figure 2-47 Accepting the license terms
Step 3 Click Install to start the installation.

The Installation Progress window is displayed, as shown in Figure 2-48.

iBMA
Figure 2-48 Installation Progress window
Step 4 When the installation is complete, click Finish. See Figure 2-49.

iBMA
Figure 2-49 Completing the installation
----End
2.4.4 Installing, Upgrading, and Uninstalling the hwBMAService

Installing
The hwBMAService installation package contains the Windows service program and
command-line program for the iBMA. Before installing the HwBMAService, ensure that the
black box driver, SNMP server, and FrameWork 4.0 have been installed. Otherwise, some
functions will be unavailable. Otherwise, some functions will be unavailable.
Step 1 Copy the files in the hwBMAService directory to a local directory and run the setup.exe
program in the local directory to start the installation.
The hwBMAService installation wizard is displayed, as shown in Figure 2-50.

iBMA
Figure 2-50 HwBMAService installation wizard
Step 2 Select an installation directory. See Figure 2-51.

The default installation directory is C:\Program Files\huawei\hwBMAService\. You can
click Browse to select another installation directory.

iBMA
Figure 2-51 Selecting an installation directory
Step 3 Click Next repeatedly until the installation is complete. See Figure 2-52.

iBMA
Figure 2-52 Clicking Next repeatedly
Figure 2-53 Installation progress

iBMA
Figure 2-54 Completing the installation
Step 4 Choose Start > Run. In the Run dialog box, enter services.msc in the text box and press
Enter.
The Services window is displayed, as shown in Figure 2-55.
The hwBMAService service is enabled by default after the installation is complete. If you
want to disable the service, right-click the service and click Stop on the shortcut menu that is
displayed.

iBMA
Figure 2-55 Services window
----End
Upgrading
The target version must be later than the current version.
Step 1 Run HwiBMAUpgrade.exe to upgrade the iBMA.
The displayed window is shown in Figure 2-56. After upgraded, the window is exit.
Figure 2-56 Upgrade window
----End
Uninstalling
There are two methods for uninstalling the iBMA. You are advised to stop the
hwBMAService before uninstalling the iBMA by using either of the two methods. For details
about how to stop the HwBMAService, see Step 4 in "Installing the hwBMAService."
 Uninstall the hwBMAService by using the installation program.

iBMA
1. Go to the iBMA installation directory, that is, the directory used in Step 1. Then run the
Setup.exe program.
The window shown in Figure 2-57 is displayed.
Figure 2-57 Window displayed after you run the Setup.exe program
2. Select Remove hwBMAService and click Finish. See Figure 2-58.

iBMA
Figure 2-58 Uninstalling the HwBMAService
3. After the hwBMAService is uninstalled, this service is removed from the service list on
Windows.
 Uninstall the hwBMAService by using Windows Control Panel.
1. Choose Start > Control Panel to open Control Panel.
2. Choose Programs > Uninstall a program. See Figure 2-59.
Figure 2-59 Choosing Programs > Uninstall a program
3. In the Programs and Features window, right-click hwBMAService and choose

Uninstall from the shortcut menu. See Figure 2-60.

iBMA
Figure 2-60 Choosing Uninstall
4. (Optional) In the confirmation dialog box, click Yes. See Figure 2-61.
Figure 2-61 Confirmation dialog box
5. (Optional) If this service is running, the dialog box shown in Figure 2-62 is displayed.
Click OK.

iBMA
Figure 2-62 Dialog box indicating that the service is running
6. The system automatically finishes uninstalling the hwBMAService and exits. See Figure
2-63.
Figure 2-63 Uninstalling the HwBMAService
----End
2.4.5 Precautions for Windows Server 2012 or 2012 R2

Set firewall rules to allow Intelligent Baseboard Man (iBMA) to communicate with processes
in Windows Server 2012 or 2012 R2.
Prerequisites
Simple Network Management Protocol (SNMP) service and hwBMAService service have
been installed.

iBMA
Procedure
1. Go to the hwBMAService directory and find snmp_rules_add.zip.
Figure 2-64 snmp_rules_add.zip
2. Decompress snmp_rules_add.zip to generate the directory as shown in Figure 2-65.
Figure 2-65 directory
3. Go to the snmp_rules_add directory, and run snmp_rules_add. The information is

displayed as in Figure 2-66.
Figure 2-66 Information displayed

iBMA
User Guide 3 Using the iBMA
3 Using the iBMA
About This Chapter

This chapter describes how to perform common operations on the iBMA, including logging in
to the iBMA, setting the Simple Network Management Protocol (SNMP) server IP address,
and diagnosing and monitoring server hardware.
3.1 Common Functions
This topic describes the common setting and functions of the iBMA. The common setting is
to set an IP address for the Simple Network Management Protocol (SNMP) server so that the
trap module can send information to the destination over SNMP. The common functions
include diagnosing and monitoring hard disks, dual in-line memory modules (DIMMs), and
CPUs.
3.2 Common Faults and Solutions
This topic describes the common faults that may occur during iBMA installation and use and
the solutions.
3.1 Common Functions

This topic describes the common setting and functions of the iBMA. The common setting is
to set an IP address for the Simple Network Management Protocol (SNMP) server so that the
trap module can send information to the destination over SNMP. The common functions
include diagnosing and monitoring hard disks, dual in-line memory modules (DIMMs), and
CPUs.
3.1.1 Logging In to the iBMA

This topic describes how to start the iBMA monitoring service by using the server operating
system (OS).
To start the iBMA monitoring service, perform the following steps:
Step 1 Log in to the Linux OS as user root.
Step 2 Run the following command to start the iBMA monitoring service:
linux-suse11:/opt/huawei/bma/bin # /etc/init.d/hwismmonitord start
Starting hwismmonitord: done

iBMA
Step 3 Run the following command to check the status of the iBMA monitoring service:
If the service is in the running state, the service has been successfully started:
linux-suse11:/opt/huawei/bma/bin # /etc/init.d/hwismmonitord status
Checking for hwismmonitord daemon:
running
Skip this step if the server system is Windows.
----End
3.1.2 Setting an IP Address for the SNMP Server

Prerequisites
You have logged in to the iBMA. For details, see 3.1.1 Logging In to the iBMA.
Procedure
Run the following command to set an IP address for the SNMP server:
syscfg -t monitor -s num i: ip p: port v: version c: community
Table 3-1 describes the command parameters.
Table 3-1 Parameters for setting an IP address for the SNMP server
Parameter Description Value

num Specifies the number of the This parameter is mandatory.
destination to which trap The value is an integer ranging
information is reported over from 1 to 5.
SNMP.
ip Specifies the IP address of the This parameter is mandatory.
destination. The value is an IPv4 address in
dotted decimal notation. Each
byte in the IP address cannot
exceed 255. For example,
172.164.2.100.
port Specifies the port number of the  The default value 162 is used
destination. if this parameter is left blank.
 The value is an integer
ranging from 0 to 65535, for
example, 162.
 The port to be set is not in
use.
version Specifies the SNMP Trap  The default value 1 is used if
version. this parameter is left blank.
 The value is 1 or 2.
community Specifies the SNMP  The default value public is

iBMA

communityname. used if this parameter is left
blank.
 The value is a string of up to
18 characters, for example,
public.
enable Enables or disables the trap  0: disabled
service.  1: enabled
The default value is 0.
For example, if the number of the destination is 3, run the following command to set the IP
address to 19.28.37.76 for the SNMP server:
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -s 3 ip:19.28.37.76
1. unconfigured
2. unconfigured
3. ip=19.28.37.76 port=162 version=1 community=public enable=1
4. unconfigured
5. unconfigured
3.1.3 Diagnosing a Hard Disk Fault

Prerequisites
Performing a Short Diagnosis on a Hard Disk

A short diagnosis is to check some sectors on a hard disk, and takes a short time.
Run the hwdiag -t disk -c short num command to perform a short diagnosis on a hard disk.
Table 3-2 Parameters in the short-diagnosis command

num Specifies the slot number of a This parameter is mandatory.
hard disk. The value range varies
depending on server
configuration.
For example, run the following command to perform a short diagnosis on the hard disk in
slot 2 on an RH2285 server:
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t disk -c short 2
*****************************************************************************
Hard disk:2

iBMA
Start short DST in background....

Please wait 1 minutes for test to complete.
Test will complete after Wed Feb 15 10:45:30 2012
Use 'hwdiag -t disk -e' to abort test.

*****************************************************************************
Performing a Long Diagnosis on a Hard Disk

A long diagnosis is to check all sectors on a hard disk, and takes a long time.
Run the hwdiag -t disk -c long num command to perform a long diagnosis on a hard disk.
Table 3-3 Parameters in the long-diagnosis command

num Specifies the slot number of a This parameter is mandatory.
hard disk. The value range varies
depending on server
configuration.
For example, run the following command to perform a long diagnosis on the hard disk in slot
2 on an RH2285 server:
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t disk -c long 2
*****************************************************************************
Hard disk:2
Start extended DST in background....
Test will complete after Wed Feb 15 12:40:55 2012

*****************************************************************************
3.1.4 Viewing Hard Disk Diagnosis Records

Prerequisites
Procedure
Run the hwdiag -t disk -l num command to view the diagnosis records of a hard disk.
Table 3-4 Parameters in the command for viewing hard disk diagnosis records

num Specifies the slot number of a This parameter is mandatory,

iBMA

hard disk. and the value range varies
depending on server
configuration.
For example, run the following command to view diagnosis records of the hard disk in slot 7
on an RH2285 server:
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t disk -l 7
**********************************************************************************
****************
Hard disk:7
SMART Self-test log, the first one is the latest!

Num Test Status segment LifeTime LBA_first_err [SK
ASC ASQ]
Description number (hours)
# 1 Short self-test Completed without error - 1299 - [- -
-]
# 2 Short self-test Aborted (by user command) - 1299 - [- -
-]
# 3 Extended self-test Aborted (by user command) - 1297 - [- -
-]
-]
-]
-]
# 7 Extended self-test Completed without error - 742 - [- -
-]
-]
-]
#10 Short self-test Completed without error - 740 - [- -
-]
-]
-]
#13 Extended self-test Aborted (by user command) - 246 - [- -
-]
-]
-]
-]
-]
-]

iBMA
**********************************************************************************
****************
Table 3-5 describes the parameters in diagnosis records.
Table 3-5 Parameters in diagnosis records
Parameter Description
Num Indicates the sequence number of a diagnosis record
among the latest diagnosis records.
For example, the value 1 indicates the latest diagnosis
record.
Test_Description Indicates the test type. Two test types are supported:
Short self-test and Extended self-test.
Status Indicates the diagnosis result. The value Completed
without error indicates that the hard disk is normal.
3.1.5 Monitoring the SMART Status of a Hard Disk

Prerequisites
Procedure
Run the hwdiag -t disk -s num command to view the SMART status of a hard disk.
Table 3-6 Parameters for viewing the SMART status of a hard disk

num Specifies the slot number of a  If this parameter is left blank,
hard disk. the SMART status of all hard
disks is displayed.
 If this parameter is set, the
SMART status of the hard
disk in the specified slot is
displayed.
 The value range varies
depending on server
configuration.
For example, run the following command to view the SMART status of the Serial Advanced
Technology Attachment (SATA) hard disk in slot 2 of an RH2285 server:

iBMA
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t disk -s 2
The command output is similar to the following:
*****************************************************************************
Hard disk:2
Physical ID :14
Vendor :ATA
ProductID :ST9500620NS
FW Version :SN01
Serial Number :9XF0HKWR
Type :SATA
FW State :UNCONFIGURED GOOD
Is Path Broken :NO
Capacity :499 GB
Media Error Count :0
Other Error Count :0
Pred Fail Count :0
Last Pred Fail Event SeqNum :0
SMART Attributes Data Structure revision number: 10

Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 082 065 044 Pre-fail Always -
182085045
3 Spin_Up_Time 0x0003 097 096 000 Pre-fail Always -
0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always -
150
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always -
0
7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always -
68719745644
9 Power_On_Hours 0x0032 100 100 000 Old_age Always -
520
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always -
0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always -
134
184 End-to-End_Error 0x0032 100 100 099 Old_age Always -
0
187 Reported_Uncorrect 0x0032 099 099 000 Old_age Always -
1
188 Command_Timeout 0x0032 100 100 000 Old_age Always -
1
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always -
0
190 Airflow_Temperature_Cel 0x0022 065 048 045 Old_age Always -
35 (Lifetime Min/Max 19/36)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always -
0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always -
127
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always -

iBMA
267
194 Temperature_Celsius 0x0022 035 052 000 Old_age Always -
35 (0 17 0 0)
195 Hardware_ECC_Recovered 0x001a 118 100 000 Old_age Always -
182085045
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always -
0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline -
0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always -
0
*****************************************************************************
Table 3-7 describes the parameters in the SMART status of a SATA hard disk.
Table 3-7 Parameters in the SMART status of a SATA hard disk
Spin_Up_Time Indicates the time that the hard disk motor takes to spin
at a specified rate.
Start_Stop_Count Indicates the number of times the hard disk motor
starts and stops. In general, this parameter indicates the
number of times for a hard disk to turn on and off its
power supply. The hard disk motor is worn badly
during the startup or stop. This parameter reflects the
hard disk service life.
Reallocated_Sector_Ct Indicates the number of reallocated sectors. When
detecting a weak sector, the hard disk reallocates
materials in the weak sector to the backup sector.
Power_On_Hours Indicates the total power-on time of a hard disk. This
parameter reflects the hard disk service life.
Spin_Retry_Count Indicates the number of times the hard disk motor spins
at the specified rate.
Power_Cycle_Count Indicates the number of times a hard disk turns on and
turns off its power supply. The hard disk motor is worn
badly during the startup or stop. This parameter reflects
the hard disk service life.
G-Sense_Error_Rate Indicates the error rate caused by mechanical
collisions.
Power-Off_Retract_Count Indicates the number of power-off times.
Temperature_Celsius Indicates the interior temperature of a hard disk.
Hardware_ECC_Recovered Indicates that hardware errors are corrected by using
the error checking and correcting (ECC) technology. If
the number of tracks to be corrected by using the ECC
technology increases and the tracks are deteriorating,
aging or other problems have occurred.

iBMA
Current_Pending_Sector Indicates the number of sectors to be allocated.
UDMA_CRC_Error_Count Indicates the transmission error rate.
Run the following command to view the SMART status of the Serial Attached Small
Computer System Interface (SAS) hard disk in slot 7 of an RH2285 server:
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t disk -s 7
*****************************************************************************
Hard disk:7
Physical ID :3
Vendor :SEAGATE
ProductID :ST9300603SS
FW Version :0006
Serial Number :6SE50CSA
Type :SAS
FW State :ONLINE
Is Path Broken :NO
Capacity :299 GB
Pred Fail Count :0
Current Drive Temperature: 30 C

Drive Trip Temperature: 68 C
Elements in grown defect list: 1
Elements in primary defect list: 5098
Get Manufactured in week of year failed!
Get Specified cycle count over device lifetime failed!
Get Accumulated start-stop cycles failed
Get Specified load-unload count over device lifetime failed!
Get Accumulated load-unload cycles failed!
Vendor (Seagate) cache information
Blocks sent to initiator = 2531491577
Blocks received from initiator = 481246019
Blocks read from cache and sent to initiator = 31498356
Number of read and write commands whose size <= segment size = 6377160
Number of read and write commands whose size > segment size = 4
Vendor (Seagate/Hitachi) factory information
number of hours powered up = 1503.80
number of minutes until next internal SMART test = 44
*****************************************************************************
Table 3-8 describes the parameters in the SMART status of a SAS hard disk.
Table 3-8 Parameters in the SMART status of a SAS hard disk

iBMA
Physical ID Indicates the physical ID of a hard disk.
Vendor Indicates the hard disk manufacturer.
ProductID Indicates the product ID of a hard disk.
FW Version Indicates the firmware version of a hard disk.
Serial Number Indicates the serial number of a hard disk.
Type Indicates the hard disk type.
FW State Indicates the firmware status of a hard disk.
Is Path Broken Indicates whether a track is damaged.
Capactiy Indicates the available storage space.
3.1.6 Monitoring DIMM ECC Status

Prerequisites
Procedure
Run the hwdiag -t mem -d command to view dual in-line memory module (DIMM) error
checking and correcting (ECC) status.
For example, run the following command to view DIMM ECC status on an RH2285 server.
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t mem -d
If the values of ECC_Status in the command output are all Ok, the DIMM ECC is normal.
*****************************************************************************
DIMM_Slot CHID Type Size ECC_Status ECC_Value
DIMM000 000 DDR3 8192 MB Ok 0
DIMM001 001 DDR3 4096 MB Ok 0
DIMM002 002 DDR3 4096 MB Ok 0
DIMM010 010 DDR3 4096 MB Ok 0
DIMM011 011 DDR3 8192 MB Ok 0
DIMM012 012 NO MEM
DIMM020 020 DDR3 4096 MB Ok 0
DIMM021 021 NO MEM
DIMM022 022 NO MEM
DIMM030 030 DDR3 4096 MB Ok 0
DIMM031 031 NO MEM
DIMM032 032 NO MEM
DIMM100 100 NO MEM
DIMM101 101 NO MEM
DIMM102 102 NO MEM
DIMM110 110 DDR3 4096 MB Ok 0

iBMA
DIMM111 111 NO MEM

DIMM112 112 NO MEM
DIMM120 120 NO MEM
DIMM121 121 NO MEM
DIMM122 122 NO MEM
DIMM130 130 DDR3 4096 MB Ok 0
DIMM131 131 NO MEM
DIMM132 132 NO MEM
*****************************************************************************
3.1.7 Querying Platform MCE Events

Prerequisites
Procedure
Run the syscfg -t monitor -l command to query platform machine check exception (MCE)
events. For example, you can query the CPU MCE events.
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -l | grep CPU | grep MCE
linux-susell:/opt/huawei/bma/bin # {CPU}{0}{major}{2014-10-10 16:59:12}{MCE
error,this is a hardware error,not a software problem,please check your hardware!
MCi_STATUS:0x310e0f.(processor id:0,core id:1,socket id:0)}
Obtain the hardware alarm events from the MCE logs. Obtain the detailed information from the alarm
reference using MCE alarm status codes.
3.1.8 Querying Events in the Black Box

Prerequisites
 You have logged in to the iBMA. For details, see 3.1.1 Logging In to the iBMA.
 Ensure that the iBMC supports the black box function and that this function is enabled.
− The iBMC V1 of the version 3.60 or later supports the black box function. You can
log in to the iBMC V1 Web, choose Download Data > Black Box on the iBMC V1
web user interface (WebUI).
− To enable the kbox function on the iBMC V2. You can log in to the iBMC V2 Web,
 The kdump service in the OS must be disabled.
For details about the command, see Table 3-9.
Table 3-9 Command for disabling the kdump service
OS Type Black Box Function Command
Redhat 6.1 Supported service kdump stop

Redhat6.2
Redhat 6.3

iBMA
OS Type Black Box Function Command

Redhat6.4
Redhat6.5
SUSE11 SP1 Supported service boot.kdump stop
SUSE11 SP2
SUSE11 SP3
UVP-V100R001C03SPC30 Supported service boot.kdump stop
0
UVP-V100R003C00SPC22
0B020
Windows 2008 Not supported N/A
Windows 2012
VMWare 4.1 u2 Not supported N/A
The black box driver is related with the system kernel version. The prededing OSs must use standard
kernels. Otherwise, a problem may occur.
Procedure
Step 1 Install the black box driver.
For details, see 2 Installing and Uninstalling the iBMA.
[root@rh-2285-r1-rhel6 ~]# cd /opt/huawei/bma/drivers/kbox
[root@rh2285H kbox]# ls
kbox.ko
[root@rh2285H kbox]# insmod kbox.ko
[root@rh2285H kbox]# lsmod | grep kbox
kbox 32219 0
The preceding command output indicates that the black box driver is successfully installed.
Step 2 Read the original data from the black box.
[root@rh2285H kbox]# cd /opt/huawei/bma/bin/
linux-susell:/opt/huawei/bma/bin # ls
hwdiag hwkbox syscfg uniCfg uniCfg64 unicfgJDM
linux-susell:/opt/huawei/bma/bin # ./hwkbox -r
Read data from the kbox successfully!!
hwdiag kbox_data__2014-2-14_18-1-3.img uniCfg unicfgJDM
hwkbox syscfg uniCfg64
kbox_data__2014-2-14_18-1-3.img is the original data file.

Step 3 Parse the original data read from the black box.

iBMA
linux-susell:/opt/huawei/bma/bin # ./hwkbox -p kbox_data__2014-2-14_18-1-3.img

Parse kbox data succeed!
hwdiag kbox_data__2014-2-14_18-1-3.img syscfg uniCfg64
hwkbox Result.txt uniCfg unicfgJDM
Result.txt contains the parsed original data in the black box.

Step 4 View the parsed data.
linux-susell:/opt/huawei/bma/bin # cat Result.txt
************Abstract Information*****************************
print all record profile
Total panics 1
Record panics 1
**************Thread information for RecordNo 0*****************
Panic Time (1392401279)(s)[2014-02-14 18:07:59]
Record Length [350(byte)]
====kbox begin dumping...====
panic string: Fatal exception
OS : Linux
Release : 2.6.32-279.el6.x86_64
Version : #1 SMP Wed Jun 13 18:24:36 EDT 2012
Machine : x86_64
Nodename : rh2285H
KBOX_VERSION : 2.9
Current time : 2014-02-14 18:07:59
====kbox end dump====.
***************The current printk information********************
***************The last printk information***********************
SysRq : Trigger a crash
BUG: unable to handle kernel NULL pointer dereference at (null)
¡-¡-
----End
3.1.9 Controlling the Log Export Level

Prerequisite
The log export level control is used only for fault locating by R&D and maintenance
personnel.
Procedure
Only on the Linux client:
1. Connect the client to the management network port on a server.
2. Run the following commands to obtain the debugging information and error logs on the
client.
− export MIDWARE_DEBUG=YES

iBMA
− export MIDWARE_ERROR=YES
3.2 Common Faults and Solutions

This topic describes the common faults that may occur during iBMA installation and use and
the solutions.
3.2.1 Failed to Install the iBMA Software (1)

Symptom
The iBMA software fails to be installed.
Alarm Information
After you run the sh ./setup.sh install x command, the system displays the following
information:
[ WARNING ]: ISM-lib require libltdl library. Install libtool-ltdl RPM from RHEL6
Operating System DVD and try again.
Possible Causes
The required library file does not exist in the system.
Procedure
Step 1 Install the RPM 64-bit package based on the displayed alarm information.
----End
3.2.2 Failed to Install the iBMA Software (2)

Symptom
The iBMA software fails to be installed.
Alarm Information
After you run the sh ./setup.sh install x command, the system displays the following
information:
error: Failed dependencies:
libltdl.so.7()(64bit) is needed by ISM-lib-1.3.1-8.x86_64.
Possible Causes

iBMA
Procedure
Step 1 Contact Huawei technical support. For details, see A.1 Obtaining Help.
----End
3.2.3 Failed to Install the iBMA (3)

Symptom
The iBMA fails to be installed.
Alarm Information
In the installation directory of the iBMA, run the sh setup.sh install monitor=yes snmp=yes
command. The following information is displayed:
Preparing... ########################################### [100%]
1:ISM-lib ########################################### [100%]
[ OK ]: install ISM-lib successfully :)

Preparing... ########################################### [100%]
1:ISM-cli ########################################### [100%]
[ OK ]: install ISM-cli successfully :)

Preparing... ########################################### [100%]
1:ISM-service ########################################### [100%]
[ OK ]: install ISM-service successfully :)

[ OK ]: Start ISM service successfully :)
audit2allow cmd not found. snmpd can not work well !
please mount ISO and install package policycoreutils-python, and then execute the bash:
selinux.sh
for example: mount /dev/cdrom /mnt/cdrom
yum update
yum install policycoreutils-python
Possible Causes
Procedure
Step 1 Install the RPM 64-bit package as prompted.
Step 2 In the installation directory of the iBMA, run the sh selinux.sh script.
----End

iBMA
3.2.4 Failure to Find the Function Library After Running a

Command
Symptom
After a user runs the iBMA command to view device information, the system displays a
message indicating that the function library cannot be found.
Alarm Information
After you run the hwdiag or syscfg command, the following information is displayed:
hwdiag: error while loading shared libraries: libhw_mid_disk.so: cannot open shared
object file: No such file or directory
Possible Causes
The dynamic library path /opt/huawei/bma/lib64 is not added to the hw_ism.conf file in
/etc/ld.so.conf.d/.
Procedure
Step 1 Check whether the hw_ism.conf file exists in /etc/ld.so.conf.d/. If this file does not exist,
reinstall the iBMA.
Step 2 If the hw_ism.conf file exists in /etc/ld.so.conf.d/, check whether the dynamic library path
/opt/huawei/bma/lib64 is added to the hw_ism.conf file. If this path is not added, add it to
the hw_ism.conf file.
Step 3 Run the ldconfig command for the change to take effect.
----End
3.2.5 Failed to Find a Command After a User Runs the Command

Symptom
After a user runs a iBMA command to view device information, the system displays a
message indicating that the command cannot be found.
Alarm Information
After you run the hwdiag or syscfg command (use a complete path in the UVP environment,
for example, /opt/huawei/bma/bin/hwdiag), the system displays the following information:
If 'hwdiag' is not a typo you can run the following command to look up the package that
contains the binary:
command-not-found hwdiag
-bash: hwdiag: command not found

iBMA
Possible Causes
/opt/huawei/bma/bin does not exist in the operating environment.
Procedure
Step 1 Check whether /opt/huawei/bma/bin exists. If no, go to Step 2. If yes, please connect
Huawei technical support personnel. For details about how to obtain help from Huawei
technical supports, see A.1 Obtaining Help.
Step 2 Run the export PATH=$PATH:/opt/huawei/bma/bin command to add
/opt/huawei/bma/bin to the PATH.
Step 3 Run the echo $PATH command to check whether /opt/huawei/bma/bin is added
successfully.
 /opt/huawei/bma/bin is generated after the BMA is installed completely.

 When you restart the server and connect the terminal tool or Remote Virtual Console to the system,
you need to add the path again. For details about how to re-add the path, see Step 1 to Step 2.
----End
3.2.6 Failed to Obtain Hard Disk Diagnosis Logs

Symptom
Some Western Digital hard disks cannot obtain short- or long-diagnosis logs.
Alarm Information
After a short or long diagnosis starts, the system does not display a message indicating that
the diagnosis is in process or display the diagnosis time length.
Possible Causes
Some Western Digital hard disk firmware does not support short or long diagnosis.
Procedure
Step 1 When the short or long diagnosis is complete, run the hwdiag –t disk –l num command to
view hard disk diagnosis records.
----End

iBMA
User Guide 4 Command Reference
4 Command Reference
About This Chapter

This topic describes how to use the hwdiag, syscfg, and hwkbox commands provided by the
iBMA.
4.1 Command Overview
4.2 hwdiag Commands
4.3 syscfg Commands
4.4 hwkbox Commands
4.5 hwwatchdog Commands
4.1 Command Overview

The hwdiag commands are used to diagnose and query information about hardware, including
dual in-line memory modules (DIMMs) and storage devices. The syscfg commands are used
to query and configure basic hardware information, upgrade the basic input/output system
(BIOS), query and configure iBMC information, write and export information, and send the
raw Intelligent Platform Management Interface (IPMI) command. The hwkbox commands
are used to manage the kbox image file and user area.
If there is no specified description, the command line does not supported by Windows system.
4.2 hwdiag Commands

4.2.1 Querying Hard Disk Status (disk)
Obtaining Hard Disk Diagnosis Information (-d)
Function
This command is used to obtain diagnosis information of hard disks in all slots, including the
interface type, slot number, serial number, health score, and capacity of each hard disk.

iBMA
Format
hwdiag -t disk -d
Parameters
None
Usage Guidelines
None
Example
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -d
*****************************************************************************
SlotNum Type SN Capacity Score
0 NO DISK
1 NO DISK
2 NO DISK
3 NO DISK
4 NO DISK
5 SATA 9XF0HKKY 499 GB 100.00
6 NO DISK
7 SAS 6SD3YP61 146 GB 100.00
8 NO DISK
9 NO DISK
10 NO DISK
11 NO DISK
*****************************************************************************
Obtaining Basic Information About Hard Disks (-i)
Function
This command is used to obtain information about hard disks in all slots, including the
manufacturer, interface type, slot number, firmware version, serial number, and capacity of
each hard disk.
Format
hwdiag -t disk -i
Parameters
None
Usage Guidelines
None

iBMA
Example
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -i
*****************************************************************************
SlotNum Manufacturer Type FW.Rev SN Capacity
0 NO DISK
1 NO DISK
2 NO DISK
3 NO DISK
4 NO DISK
5 ATA SATA SN01 9XF0HKKY 499 GB
6 NO DISK
7 SEAGATE SAS 0006 6SD3YP61 146 GB
8 NO DISK
9 NO DISK
10 NO DISK
11 NO DISK
*****************************************************************************
Obtaining Hard Disk SMART Information (-s)
Function
This command is used to obtain the self-monitoring, analysis and reporting (SMART)
information of a hard disk.
The command is supported by linux and windows systems.
Format
hwdiag -t disk -s
hwdiag -t disk -s num
Parameters
num Specifies the slot number of a The value range varies depending on server
hard disk. configuration.
Usage Guidelines
 If num is left blank, the SMART information of all hard disks is displayed.
 If num is set, the SMART information of the hard disk in the specified slot is displayed.
Example
View the SMART information of the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -s 7
*****************************************************************************
Hard disk:7
Physical ID :1
Vendor :SEAGATE

iBMA
ProductID :ST9146803SS
FW Version :0006
Serial Number :6SD3YP61
Type :SAS
FW State :UNCONFIGURED GOOD
Is Path Broken :NO
Capactiy :146 GB
Pred Fail Count :0
Current Drive Temperature: 27 C

Drive Trip Temperature: 68 C
Elements in grown defect list: 0
Elements in primary defect list: 224
Get Manufactured in week of year failed!
Get Specified cycle count over device lifetime failed!
Get Accumulated start-stop cycles failed
Get Specified load-unload count over device lifetime failed!
Get Accumulated load-unload cycles failed!
Vendor (Seagate) cache information
Blocks sent to initiator = 2749542545
Blocks received from initiator = 483274713
Blocks read from cache and sent to initiator = 24954573
Number of read and write commands whose size <= segment size = 5195596
Number of read and write commands whose size > segment size = 0
Vendor (Seagate/Hitachi) factory information
number of hours powered up = 2137.92
number of minutes until next internal SMART test = 28
*****************************************************************************
Performing a Short Diagnosis on a Hard Disk (-c or -c short)
Function
This command is used to perform a short diagnosis on the hard disk in a specified slot.
Format
hwdiag -t disk -c num
hwdiag -t disk -c short num
Parameters

iBMA
Usage Guidelines
 The parameter num is mandatory. Its value must be a valid hard disk slot number.
 short is optional. The hwdiag -t disk -c num command has the same effect as the
hwdiag -t disk -c short num command.
Example
Perform a short diagnosis on the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -c 7
*****************************************************************************
Hard disk:7
Start short DST in background....
Test will complete after Fri Feb 17 10:13:52 2012

*****************************************************************************
Performing a Long Diagnosis on a Hard Disk (-c long)
Function
This command is used to perform a long diagnosis on the hard disk in a specified slot.
Format
hwdiag -t disk -c long num
Parameters
Usage Guidelines
The parameter num is mandatory. Its value must be a valid hard disk slot number.
Example
Perform a long diagnosis on the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -c long 7
*****************************************************************************
Hard disk:7
Start extended DST in background....
Test will complete after Fri Feb 17 11:26:49 2012

*****************************************************************************

iBMA
Viewing Records on a Short or Long Diagnosis of a Hard Disk (-l)
Function
This command is used to query records on a short or long diagnosis of the hard disk in a
specified slot.
Format
hwdiag -t disk -l num
Parameters
Usage Guidelines
Example
View the diagnosis records of the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -l 7
**********************************************************************************
****************
Hard disk:7
SMART Self-test log, the first one is the latest!

Num Test Status segment LifeTime LBA_first_err [SK
ASC ASQ]
Description number (hours)
-]
-]
-]
-]
-]
-]
# 7 Extended self-test Completed without error - 742 - [- -
-]
-]
-]

iBMA
-]
-]
-]
#13 Extended self-test Aborted (by user command) - 246 - [- -
-]
-]
-]
-]
-]
-]
**********************************************************************************
****************
Stopping a Hard Disk Diagnosis (-e)
Function
This command is used to stop the short or long diagnosis of the hard disk in a specified slot.
Format
hwdiag -t disk -e num
Parameters
Usage Guidelines
Example
Stop the diagnosis of the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -e 7
*****************************************************************************
Hard disk:7
Self test was stopped
*****************************************************************************

iBMA
Turning On an Indicator for a Hard Disk (-o)
Function
This command is used to turn on an indicator for a hard disk.
Format
hwdiag -t disk -o
hwdiag -t disk -o num
Parameters
Usage Guidelines
 If num is left blank, the indicators for all hard disks are turned on.
 If num is set, the indicator for the hard disk in the specified slot is turned on.
Example
Turn on the indicator for the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -o 7
*****************************************************************************
Hard disk:7
Set locate led : ON
*****************************************************************************
Turning Off an Indicator for a Hard Disk
Function
This command is used to turn off an indicator for a hard disk.
Format
hwdiag -t disk –x
hwdiag -t disk –x num
Parameters

iBMA
Usage Guidelines
 If num is left blank, the indicators for all hard disks are turned off.
 If num is set, the indicator for the hard disk in the specified slot is turned off.
Example
Turn off the indicator for the hard disk in slot 7.
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -t disk -x 7
*****************************************************************************
Hard disk:7
Set locate led : OFF
*****************************************************************************
4.2.2 Querying RAID Status (RAID)

Obtaining RAID Diagnosis Information (-d)
Function
This command is used to obtain the redundant array of independent disks (RAID) levels and
status (normal, degraded, or offline) of RAID logical disks, slot numbers of hard disks in each
RAID group, and mapping between operating system (OS) drive letters and RAID groups.
Format
hwdiag -t raid -d
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t raid -d
*****************************************************************************
Logical Disk Count : 2
Mapped Device : 0
Raid Level : RAID0
Mapped Device : 1
Raid Level : RAID1
*****************************************************************************
*****************************************************************************
Mapped Device : 0
Raid Level : RAID0
OS Drive Name : /dev/sda
Logical Device State : OPTIMAL

iBMA
Physical Disk number : 1

-----------------------------------------------------------------------------
Slot Number : 7
ProductId : ST9300603SS
FW Version : 0006
State : ONLINE
Serial Number : 6SE50CSA
Capactiy : 299GB
*****************************************************************************
*****************************************************************************
Mapped Device : 1
Raid Level : RAID1
OS Drive Name : /dev/sdb
-----------------------------------------------------------------------------
Slot Number : 2
ProductId : ST9500620NS
FW Version : SN01
State : ONLINE
Serial Number : 9XF0HKWR
Capactiy : 499GB
-----------------------------------------------------------------------------
Slot Number : 3
FW Version : SN01
State : ONLINE
Serial Number : 9XF0HJN6
Capactiy : 499GB
*****************************************************************************
The values of Logical Device State are explained as follows:

OPTIMAL: The logical disk is operating properly.
DEGRADED: The redundant logical disk is in degraded state.
PARDEGERADED: The redundant logical disk is in partially degraded state.
OFFLINE: The logical disk is in offline state and cannot be used by the system.
Obtaining Basic Information About the RAID Controller Card (-i)
Function
This command is used to obtain basic information about the redundant array of independent
disks (RAID) controller card, including the controller model, firmware version, basic
input/output system (BIOS) version, ID, and manufacturer.
Format
hwdiag -t raid -i
Parameters
None

iBMA
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t raid -i
*****************************************************************************
Number : 0
Type : SAS2308
Manufacturer : LSI
FW Version : 10.100.06.00
BIOS Version : 07.19.08.00
Driver Name : mpt2sas
Driver Version : 12.101.00.00
*****************************************************************************
Obtaining RAID Controller Card Battery Information (-b)
Function
This command is used to obtain information about each redundant array of independent disks
(RAID) controller card battery, including the battery type, serial number, designed capacity,
current capacity, designed voltage, current voltage, current, status, number of charges and
discharges, manufacturer, and temperature.
Format
hwdiag -t raid -b
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t raid -b
*****************************************************************************
Battery Information:
Status : Ready
Manufacturer : LS36681
Name : iBBU-09
Type : iBBU-09
Serial Number : 154
Design Voltage : 4100 mV
Current Voltage : 4099 mV
Design Capacity : 1530 mAh
Remaining Capacity : 1342 mAh
Current Now : 0 mA

iBMA
Charge Cycle Count : 8

Temperature : 24 C
*****************************************************************************
4.2.3 Querying DIMM Status (mem)

Obtaining DIMM Diagnosis Information (-d)
Function
This command is used to obtain dual in-line memory module (DIMM) diagnosis information,
including the slot number, channel ID (CHID), model, capacity, error checking and correcting
(ECC) status, and ECC value of each DIMM.
Format
hwdiag -t mem -d
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t mem -d
*****************************************************************************
DIMM_Slot CHID Type Size ECC_Status ECC_Value
DIMM000 000 DDR3 8192 MB Ok 0
DIMM001 001 DDR3 4096 MB Ok 0
DIMM002 002 DDR3 4096 MB Ok 0
DIMM010 010 DDR3 4096 MB Ok 0
DIMM011 011 DDR3 8192 MB Ok 0
DIMM012 012 NO MEM
DIMM020 020 DDR3 4096 MB Ok 0
DIMM021 021 NO MEM
DIMM022 022 NO MEM
DIMM030 030 DDR3 4096 MB Ok 0
DIMM031 031 NO MEM
DIMM032 032 NO MEM
DIMM100 100 NO MEM
DIMM101 101 NO MEM
DIMM102 102 NO MEM
DIMM110 110 DDR3 4096 MB Ok 0
DIMM111 111 NO MEM
DIMM112 112 NO MEM
DIMM120 120 NO MEM
DIMM121 121 NO MEM
DIMM122 122 NO MEM
DIMM130 130 DDR3 4096 MB Ok 0
DIMM131 131 NO MEM

iBMA
DIMM132 132 NO MEM

*****************************************************************************
Obtaining Basic Information About DIMMs (-i)
Function
This command is used to obtain basic information about dual in-line memory modules
(DIMMs), including the slot number, model, capacity, serial number, manufacturer, and
channel ID (CHID) of each DIMM.
Format
hwdiag -t mem -i
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -t mem -i
*****************************************************************************
DIMM_Slot CHID Type SN Manufactory Size
DIMM000 000 DDR3 0xE088792D Micron 4096MB
DIMM001 001 NO MEM
DIMM002 002 NO MEM
DIMM010 010 DDR3 0xE0887921 Micron 4096MB
DIMM011 011 NO MEM
DIMM012 012 NO MEM
DIMM020 020 DDR3 0x31428F22 Hynix 4096MB
DIMM021 021 NO MEM
DIMM022 022 NO MEM
DIMM030 030 DDR3 0x3230565D Hynix 4096MB
DIMM031 031 NO MEM
DIMM032 032 NO MEM
DIMM101 101 NO MEM
DIMM102 102 NO MEM
DIMM111 111 NO MEM
DIMM112 112 NO MEM
DIMM121 121 NO MEM
DIMM122 122 NO MEM
DIMM130 130 DDR3 0x32105678 Hynix 4096MB
DIMM131 131 NO MEM
DIMM132 132 NO MEM
*****************************************************************************

iBMA
4.2.4 Querying Help Information

Obtaining Help Information (-h)
Function
This command is used to obtain help information about hwdiag commands.
Format
hwdiag -h
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwdiag -h
useage:hwdiag <-v> | <-t> | <-h>
-v:output software version information
-t <target> <-d|-i|-b|-s [num]|-c [short|long] num|-e num|-l num|-x [num]|-o [num]>
-t <target>
disk operate with disk
raid operate with raid (include battery)
mem operate with mem
-d output diagnose information of the hardware
-i output all information of the hardware
-b output the battery information
-s [num] output SMART information of the disk,num is the disk's slotnum,if
the disk is not ap
-c long num output long diagnose information of the disk which is appointed
-c [short] num output short diagnose information of the disk which is appointed
-e num stop diagnose of the disk which is appointed
-l num look over the log of the disk which is appointed
-o [num] start locate led
-x [num] stop locate led
-h:output help information
4.2.5 Querying the Software Version

Obtaining the Software Version (-v)
Function
This command is used to obtain the software version of hwdiag commands.

iBMA
Format
hwdiag -v
Parameters
None
Usage Guidelines
None
Example
linux-suse11:/opt/huawei/bma/bin # ./hwdiag -v
The software version is:4.6
4.3 syscfg Commands

4.3.1 Querying Hard Disk Status
Obtaining Basic Information About Hard Disks (-i or --info)
Function
This command is used to obtain information about hard disks in all slots, including the
manufacturer, interface type, slot number, firmware version, serial number, and capacity of
each hard disk.
Format
syscfg -t disk -i (short command)
syscfg --target disk --info (long command)
Parameters
None
Usage Guidelines
The short and long commands can be used together.
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t disk -i
HDD backplane information:
*****************************************************************************
Board Name : BC11EHBA
Board ID : 0xaa4a
*****************************************************************************

iBMA
physical disks information:

*****************************************************************************
0 NO DISK
1 NO DISK
2 NO DISK
3 NO DISK
5 NO DISK
6 NO DISK
7 NO DISK
*****************************************************************************
There is a low probability that the hard disk capacity fails to be obtained due to low compatibility
between the hard disks and RAID controller card. If this issue occurs, repeat this command once or
twice. If the hard disk capacity fails to be obtained for three consecutive times, check whether all hard
disks are operating properly. If all hard disks are operating properly, contact Huawei technical support.
For details, see A.1 Obtaining Help.
4.3.2 Querying RAID Status

Obtaining RAID Information (-i or --info)
Function
 Obtains information about each redundant array of independent disks (RAID) controller
card, including the ID, controller type, manufacturer, firmware version, and basic
input/output system (BIOS) version.
 Obtains information about each logical disk, including the number of logical disks, status
(normal, degraded, or offline), slot numbers of hard disks in each RAID group, serial
number, and mapping between operating system (OS) drive letters and RAID groups.
 Obtains information about each RAID controller card battery, including the battery type,
name, serial number, designed capacity, designed voltage, current capacity, current
voltage, current, status, number of charges and discharges, and temperature.
Format
syscfg -t raid -i (short command)
syscfg --target raid --info (long command)
Parameters
None
Usage Guidelines

iBMA
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t raid -i
raid information:
*****************************************************************************
Number : 0
Type : SAS2308
Manufacturer : LSI
FW Version : 10.100.06.00
BIOS Version : 07.19.08.00
Driver Name : mpt2sas
Driver Version : 12.101.00.00
*****************************************************************************
battery information:
*****************************************************************************
Battery not supported!
*****************************************************************************
logic disks information:

*****************************************************************************
Mapped Device : 0
Raid Level : RAID1
*****************************************************************************
*****************************************************************************
Mapped Device : 0
Raid Level : RAID1
-----------------------------------------------------------------------------
Slot Number : 0
ProductId : MBF2300RC
FW Version : 0109
State : ONLINE
Serial Number : EB00PC40AM0P
Capactiy : 299GB
-----------------------------------------------------------------------------
Slot Number : 1
ProductId : MBF2300RC
FW Version : 0109
State : ONLINE
Serial Number : EB00PC40ALVF
Capactiy : 299GB
*****************************************************************************

iBMA
4.3.3 Querying DIMM Status

Obtaining Basic Information About DIMMs (-i or --info)
Function
This command is used to obtain basic information about dual in-line memory modules
(DIMMs), including the slot number, model, capacity, serial number, manufacturer, and
channel ID (CHID) of each DIMM.
Format
syscfg -t mem -i (short command)
syscfg --target mem --info (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t mem -i
*****************************************************************************
DIMM_Slot CHID Type SN Manufactory Size
DIMM000 000 DDR3 0xE088792D Micron 4096MB
DIMM001 001 NO MEM
DIMM002 002 NO MEM
DIMM011 011 NO MEM
DIMM012 012 NO MEM
DIMM020 020 DDR3 0x31428F22 Hynix 4096MB
DIMM021 021 NO MEM
DIMM022 022 NO MEM
DIMM030 030 DDR3 0x3230565D Hynix 4096MB
DIMM031 031 NO MEM
DIMM032 032 NO MEM
DIMM101 101 NO MEM
DIMM102 102 NO MEM
DIMM111 111 NO MEM
DIMM112 112 NO MEM
DIMM121 121 NO MEM
DIMM122 122 NO MEM
DIMM130 130 DDR3 0x32105678 Hynix 4096MB
DIMM131 131 NO MEM
DIMM132 132 NO MEM
*****************************************************************************

iBMA
4.3.4 Querying CPU Status

Obtaining Basic Information About CPUs (-i or --info)
Function
This command is used to obtain basic information about CPUs, including the CPU model,
frequency, external clock frequency, number of CPU cores, number of enabled cores, number
of threads, and socket ID.
Format
syscfg -t cpu -i (short command)
syscfg --t cpu --info (long command)
Parameters
None
Usage Guidelines
The command output is displayed by logical CPU. The short and long commands can be used
together.
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t cpu -i
*****************************************************************************
Cpu Manufacturer : Intel(R) Corporation
Cpu Type : Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Cpu Clock Frequency : 2700 MHz
Cpu External Frequency : 100 MHz
Cpu Core Numbers : 12
Cpu Enable Core Numbers : 12
Cpu Thread Numbers : 24
Cpu Socket ID : 0
cpu Temperature : 72
-----------------------------------------------------------------------------
Cpu Type : Intel(R) Xeon(R) CPU E5-2697 v2 @ 2.70GHz
Cpu Socket ID : 1
*****************************************************************************

iBMA
4.3.5 Querying BIOS Status

Obtaining Basic Information About the BIOS (-i or --info)
Function
This command is used to obtain basic information about the basic input/output system (BIOS),
including the BIOS vendor, version number, and compiling date.
Format
syscfg -t bios -i (short command)
syscfg --target bios --info (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t bios -i
*****************************************************************************
Vendor: American Megatrends Inc.
Version: THSCV013
Release Date: 06/14/2011
*****************************************************************************
Upgrading the BIOS (-u or --update)
Function
This command is used to upgrade the basic input/output system (BIOS).
Format
syscfg -t bios -u file (short command)
syscfg --target bios --update file (long command)
Parameters
file Specifies the path to the upgrade file. File path

iBMA
Usage Guidelines
Before running this command, ensure that the path to the upgrade file is correct and that the
upgrade file exists.
When running this upgrade command for an R1 board, ensure that the Intelligent Platform
Management Interface (IPMI) driver and the /dev/ipmi0 device exist. Otherwise, the upgrade
fails due to a loading error.
 After an upgrade, the boot sequence configured in the BIOS is changed to the default one.
 E9000 compute nodes do not support the command.
Example
linux-susell：/opt/huawei/bma/bin/syscfg -t bios -u ./ biosimage.hpm
Performing preparation stage...

OK
Performing Upgrade stage...

Upgrading CONFIG [Total 1712 bytes]
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] sent 1712 bytes
Upgrading BIOS [Total 5606485 bytes]
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] sent 5606485 bytes
OK
Performing activation stage
OK
BIOS UPGRADE SUCCESSFUL.
4.3.6 Querying and Configuring Server System Information

Obtaining Server Asset Information (-i or --info)
Function
This command is used to obtain server hardware asset information, including the hardware
manufacturer, version, serial number, universally unique identifier (UUID), asset label, and
operating system (OS) information.

iBMA
Format
syscfg -t system -i (short command)
syscfg --target system --info (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -i
*****************************************************************************
Manufacturer : Huawei Technologies Co., Ltd.
Product Name : RH2288 V2-8S
Version : V100R002
Serial Number: To be filled by O.E.M.
UUID : 3A266AFE-BF15-11D3-BDC0-000000821800
Assert Tag : testttt
OS Version : Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r
(\l).
*****************************************************************************
Turning On or Off the Server UID Indicator (-s or --set uid)
Function
This command is used to turn on or off the server unit identification (UID) indicator.
Format
syscfg -t system -s uid <operate> [time]
syscfg -target system --set uid <operate> [time]
Parameters
operate Specifies the operation to be performed to  on

the UID indicator.  off
time Specifies the duration in which the UID The value is a positive integer,
indicator is on. in seconds.
Usage Guidelines
 If the value of operate is off, time is not required.

iBMA
 If the value of operate is on, time is optional. If the command does not contain time, the
UID indicator is on permanently.
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -s uid off
Set the uid off successfully.
Setting the Server Power-On Policy (-s or --set poweronpolicy)
Function
This command is used to set the server power-on policy.
Format
syscfg -t system -s poweronpolicy <policy> (short command)
syscfg -target system --set poweronpolicy <policy> (long command)
Parameters
policy Specifies the server power-on The options are as follows:
policy.  0: stays off the server.
 1: restores the server to the previous
state.
 2: turns on the server automatically.
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -s poweronpolicy 0
Set system power policy success.
Obtaining the Server Power-On Policy (-g or --get poweronpolicy)
Function
This command is used to obtain the server power-on policy.
Format
syscfg -t system -g poweronpolicy (short command)
syscfg -target system --get poweronpolicy (long command)

iBMA
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -g poweronpolicy
PowerOn Policy: Turn On
Setting the Graceful Power-Off Timeout Period for the Server (-s or --set
shutdowntimeout)
Function
This command is used to set the graceful power-off timeout period for the server.
Format
syscfg -t system -s shutdowntimeout <timeout> (short command)
syscfg -target system --set shutdowntimeout <timeout> (long command)
Parameters
timeout Specifies the graceful The value of the power-off
power-off timeout period for timeout period varies with
the server. the iBMC platform and is
set based on command
instructions.
NOTE
Set the value based on actual
requirements. The default unit
is ms.
You need to set the power-off timeout period to ON before setting the graceful power-off timeout period
on the iBMC V2 platform. Log in to the iBMC V2 WebUI and choose Power > Power Control. On the
displayed page, set the power-off timeout period to ON.
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -s shutdowntimeout 10
Set system shutdowntimeout success.

iBMA
Obtaining the Graceful Power-Off Timeout Period for the Server (-g or --get
shutdowntimeout)
Function
This command is used to obtain the graceful power-off timeout period for the server.
Format
syscfg -t system -g shutdowntimeout (short command)
syscfg -target system --get shutdowntimeout (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t system -g shutdowntimeout
Poweroff Timeout: 10 seconds
4.3.7 Querying NIC Status

Obtaining NIC Basic Information About NICs (-i or --info)
Function
This command is used to obtain basic information about network interface cards (NICs),
including the manufacturer, model, firmware version, driver name, driver version, status of
network ports, Peripheral Component Interconnect Express (PCIe) device number, working
rate, duplex status, auto-negotiation mode, and link status of each NIC.
Format
syscfg -t eth -i (short command)
syscfg --target eth --info (long command)
Parameters
None
Usage Guidelines

iBMA
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t eth -i
*****************************************************************************
Physical Interface: Intel Corporation 82580 Gigabit Network Connection
Vendor : Intel Corporation
Device Name : 82580 Gigabit Network Connection
Function : Network controller
Driver Name : igb
Driver Version : 2.1.0-k2
Fireware Version : 3.2-9
Interface: eth0
PCI-E : 0000:02:00.0
Speed : 100Mb/s
Duplex : Full
Auto-negotiation : On
Link Status : Yes
Interface: eth1
PCI-E : 0000:02:00.1
Speed : Unknown
Duplex : Unknown
Link Status : No
*****************************************************************************
4.3.8 Querying Basic Information About All Components

Obtaining Basic Information About All Components (-a or --all)
Function
This command is used to obtain basic information about all components, including
information about the server, hard disks, redundant array of independent disks (RAID)
controller card, dual in-line memory modules (DIMMs), CPUs, basic input/output system
(BIOS), and network interface cards (NICs).
Format
syscfg -a (short command)
syscfg --all (long command)
Parameters
None
Usage Guidelines
None

iBMA
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -a
server information:
*****************************************************************************
Manufacturer : Huawei Technologies Co., Ltd.
Product Name : RH2288 V2-8S
Version : V100R002
Serial Number: To be filled by O.E.M.
UUID : 3A266AFE-BF15-11D3-BDC0-000000821800
Assert Tag : testttt
OS Version : Welcome to SUSE Linux Enterprise Server 11 SP2 (x86_64) - Kernel \r
(\l).
*****************************************************************************
disk information:
HDD backplane information:
*****************************************************************************
Board Name : BC11EHBA
Board ID : 0xaa4a
*****************************************************************************
physical disks information:

*****************************************************************************
0 NO DISK
1 NO DISK
2 NO DISK
3 NO DISK
5 NO DISK
6 NO DISK
7 NO DISK
*****************************************************************************
raid information:
*****************************************************************************
Number : 0
Type : SAS2208
Manufacturer : LSI
FW Version : 3.190.05-1669
BIOS Version : 5.33.00_4.12.05.00_0x05160000
Driver Name : megaraid_sas
Driver Version : 00.00.05.38-rc1
*****************************************************************************
battery information:
*****************************************************************************
Battery is not present!
*****************************************************************************
logic disks information:

*****************************************************************************

iBMA
Mapped Device : 0
Raid Level : RAID0
*****************************************************************************
*****************************************************************************
Mapped Device : 0
Raid Level : RAID0
-----------------------------------------------------------------------------
Slot Number : 4
FW Version : SN01
State : ONLINE
Serial Number : 9XF0HKKY
Capactiy : 499GB
*****************************************************************************
memory information:
*****************************************************************************
DIMM_Slot CHID Type SN Manufacturer Size
DIMM000 000 DDR3 0xE7078322 Kingston 8192MB
DIMM001 001 DDR3 0x829E5A25 Samsung 4096MB
DIMM010 010 DDR3 0xE088791B Micron 4096MB
DIMM011 011 DDR3 0xE7078522 Kingston 8192MB
DIMM012 012 NO MEM
DIMM021 021 NO MEM
DIMM022 022 NO MEM
DIMM030 030 DDR3 0xE088791A Micron 4096MB
DIMM031 031 NO MEM
DIMM032 032 NO MEM
DIMM100 100 NO MEM
DIMM101 101 NO MEM
DIMM102 102 NO MEM
DIMM110 110 DDR3 0xE088792F Micron 4096MB
DIMM111 111 NO MEM
DIMM112 112 NO MEM
DIMM120 120 NO MEM
DIMM121 121 NO MEM
DIMM122 122 NO MEM
DIMM130 130 DDR3 0xE088790B Micron 4096MB
DIMM131 131 NO MEM
DIMM132 132 NO MEM
*****************************************************************************
cpu information:
*****************************************************************************
Cpu Type : Genuine Intel(R) CPU @ 2.60GHz

iBMA

Cpu Socket ID : 0
-----------------------------------------------------------------------------
Cpu Type : Genuine Intel(R) CPU @ 2.60GHz
Cpu Socket ID : 1
*****************************************************************************
bios information:
*****************************************************************************
Vendor: Insyde Corp.
Version: RMISV053
Release Date: 01/18/2013
*****************************************************************************
ethernet information:
*****************************************************************************
Physical Interface: Intel Corporation 82580 Gigabit Network Connection
Vendor : Intel Corporation
Device Name : 82580 Gigabit Network Connection
Function : Network controller
Driver Name : igb
Driver Version : 3.0.6-k2
Firmware Version : 3.2-9
Interface: eth0
PCIE : 0000:02:00.0
Speed : 100Mb/s
Duplex : Full
Link Status : Yes
HWaddr : 00:25:9E:00:11:12
Gateway : 192.168.55.1
IP Address : 192.168.52.111
Net Mask : 255.255.0.0
Interface: eth1
PCIE : 0000:02:00.1
Speed : Unknown
Duplex : Unknown
Link Status : No
HWaddr : 00:25:9E:00:11:13
Gateway : 0.0.0.0
IP Address : Unspecified
Net Mask : Unspecified
*****************************************************************************

iBMA
bmc information:
*****************************************************************************
Host Name : yfei11111
IPMI Version : 2.0
iMana Version : (U1029)5.83
FPGA Version : (U1011)024
CPLD Version : (U1005)001
*****************************************************************************
power information:
*****************************************************************************
Current Power : 154 watts
Max Power : 245 watts
Average Power : 151 watts
Total Consume : 99.846333 kilowatt-hour
*****************************************************************************
4.3.9 Performing Operations by Using the Monitor Module

Querying Historical Log Information (-l or --last)
Function
This command is used to obtain all historical logs.
Format
syscfg -t monitor -l (short command)
syscfg --target monitor --last (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -l
1. {SYSTEM}{0}{minor}{2013-10-24 14:10:44}{system cpu occupy normal : current=0.0%,
pre=0.0%, threshold = 60}
2. {SYSTEM}{0}{minor}{2013-10-24 14:10:32}{system disk occupy normal : current=1.7%,
3. {SYSTEM}{0}{minor}{2013-10-24 14:10:29}{system memory occupy normal : current=4.0%,
4. {ETH}{1}{major}{2013-10-24 14:10:26}{eth1 status has changed from init to fail}
5. {ETH}{0}{minor}{2013-10-24 14:10:26}{eth0 status has changed from init to ok}
6. {DISK}{4}{major}{2013-10-24 14:10:26}{physical disk 4 smart status has changed from
SMART INIT to SMART Warning}
7. {DISK}{4}{minor}{2013-10-24 14:10:25}{physical disk 4 predictive status has

iBMA
changed from PREDICTION INIT to PREDICTION OK}

8. {DISK}{4}{minor}{2013-10-24 14:10:25}{physical disk 4 current temperature is 27C,
the minor is 55C, major is 60C, critical is 68C}
Configuring Trap Information (-s or --settrap)
Function
This command is used to configure trap information of a specified destination.
Format
syscfg -t monitor -s num i: ip p: port v: version c: community (short command)
syscfg --target monitor --settrap num ip: ip port: port version: version community:
community (long command)
Parameters
num Specifies the number of the 1~5

destination to which trap information
is reported over the Simple Network
Management Protocol (SNMP).
ip Specifies the IP address of the The value is an IPv4 address in
destination. dotted decimal notation. Each byte
in the IP address cannot exceed 255.
For example, 172.164.2.100.
port Specifies the port number of the The value is an integer with a
destination. maximum of 10 digits, for example,
162. The default value is 162.
version Specifies the SNMP Trap version. The value is 1 or 2. The default
value is 1.
community Specifies the SNMP communityname. The value contains a maximum of
18 characters, for example, public.
The default value is public.
Usage Guidelines
 The parameters num and ip are mandatory, and other parameters are optional.
 The system uses the default values if the parameters port, version, and community are
left blank.
 Enter the values in the specified sequence.
 The short and long commands can be used together.
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -s 1 ip:192.168.20.1

iBMA
1. ip=192.168.20.1 port=162 version=1 community=public

2. unconfigured
3. unconfigured
4. unconfigured
5. unconfigured
Obtaining Trap Configuration Information (-g or --gettrap)
Function
This command is used to obtain the trap configuration information of a specified destination
(num behind -g) or all destinations (all behind -g).
Format
syscfg -t monitor -g num (short command)
syscfg -t monitor -g all (short command)
syscfg --target monitor --gettrap num (long command)
syscfg --target monitor --gettrap all (long command)
Parameters
num Specifies the number of the destination to which trap information is 1~5
reported over the Simple Network Management Protocol (SNMP).
all Indicates all destinations to which trap information is reported over -
SNMP.
Usage Guidelines
This command must contain either num or all.
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -g all
1. ip=192.168.20.1 port=162 version=1 community=public
2. unconfigured
3. unconfigured
4. unconfigured
5. unconfigured
Deleting Trap Configuration Information (-d or --deltrap)
Function
This command is used to delete trap configuration information of a specified destination.

iBMA
Format
syscfg -t monitor -d num (short command)
syscfg --target monitor --deltrap num (long command)
Parameters
num Specifies the number of the destination to which trap information is 1~5
reported over the Simple Network Management Protocol (SNMP).
Usage Guidelines
num is mandatory.
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -d 1
1. unconfigured
2. unconfigured
3. unconfigured
4. unconfigured
5. unconfigured
Setting the Hardware Event Severity (-r or --rating)
Function
This command is used to set the severity of events to be reported for a specified hardware
component.
Format
syscfg -t monitor -r type rating (short command)
syscfg --target monitor --rating type rating (long command)
Parameters
type Specifies the hardware The value is disk, raid, bat, cpu, or
component type. mem.

iBMA

rating Specifies the severity of events  -1: None event report.
to be reported.  0: Events of the critical or higher
level are reported.
 1: Events of the warning or higher
level are reported.
 2: Events of the information or
higher level is reported.
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -r cpu 2
disk = 2
raid = 2
raid battery = 2
memory = 2
cpu = 2
Obtaining the Hardware Event Severities (-r or --rating)
Function
This command is used to obtain the severities of events to be reported for all hardware
components.
Format
syscfg -t monitor -r (short command)
syscfg --target monitor --rating (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor -r
disk = 2
raid = 2
raid battery = 2
memory = 2

iBMA
cpu = 2
Setting System Resource Alarm Thresholds (-u or --utilize)
Function
This command is used to set alarm thresholds for the CPU usage, memory usage, disk space
usage, and SWAP usage.
Format
syscfg -t monitor -u type utilization (short command)
syscfg --target monitor -- utilize type utilization (long command)
Parameters
type Specifies the system resource The value is cpu, disk, mem or swap.
type.
utilization Specifies the resource usage. The value is an integer ranging from 1 to
100.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t monitor -u cpu 50
system_cpu occupy threshold 50.
Obtaining the System Resource Alarm Thresholds (-u)
Function
This command is used to obtain alarm thresholds of the system resource usage, such as the
CPU, memory, hard disks, and swap partition usage.
Format
syscfg -t monitor -u
Parameters
None

iBMA
Usage Guidelines
None
Example
rh2285-r2-sless11-1:～# syscfg -t monitor -u
system_cpu occupy threshold 100.
system_mem occupy threshold 100.
system_swap occupy threshold 100.
stem_disk occupy threshold 100.
Sending a Trap Test Message (-m or --message)
Function
This command is used to send a trap test message to a specified client.
Format
syscfg -t monitor -m num (short command)
syscfg --target monitor -message num (long command)
Parameters
num Identifies the client to which a trap test The value is an integer
message is to be sent. ranging from 1 to 5.
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t monitor –m 1
send test trap success.
4.3.10 Querying Help Information

Obtaining Help Information (-h or --help)
Function
This command is used to obtain help information about syscfg commands.

iBMA
Format
syscfg -h (short command)
syscfg --help (long command)
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -h
usage:syscfg <-v | -a | -t | -h>
-v,--version:output software version information
-a,--all: output information of all the hardware
-t,--target <target><option>
<target> <option>
system operate with server system
-i,--info output the information of system
-s,--set <argument> set system configuration
uid <on [time]|off> turn on or turn off uid led
poweronpolicy <policy> set the server power on policy
0 Stay Off
1 Restore Previous State
2 Turn On
shutdowntimeout <timeout> set the server shutdown timeout
-g,--get <argument> get system configuration
poweronpolicy get the server power on policy
shutdowntimeout get the server shutdown timeout
disk operate with disk
-i,--info output the information of disk
raid operate with raid (include battery)
-i,--info output the information of raid
-u,--update <file> update raid
mem operate with memory
-i,--info output the information of memory
cpu operate with cpu
-i,--info output the information of cpu
bios operate with bios
-i,--info output the information of bios
-r,--read read bios configuration
-w,--write <file> write configuration file to bios
-u,--update <file> update bios
eth operate with eth
-i,--info output the information of eth
monitor operate with monitor
-l,--last look over the history log of database
-g,--gettrap <num|all> get trap client configuration,num is client
serial number,if input all,output all trap client configuration
-d,--deltrap <num> delete trap client configuration

iBMA
-s,--settrap <num> <ip,i:ip> [port,p:port] [version,v:version]

[community,c:community] [enable,e:enable]
set trap client configuration,if you input
empty,use the default configuration
example:syscfg -t monitor -s 1 ip:192.168.1.1 port:162 version:1
community:public enable:1
syscfg -t monitor -s 1 i:192.168.1.1 p:162 v:1 c:public e:1
-r,--rating get configuration about the hardware event
level which trap report
-r,--rating <type> <rating>
set configuration about the hardware event level which trap report
disk set disk event level
raid set raid event level
bat set raid battery event level
mem set memory event level
cpu set cpu event level
system set system event level
-1 no event report
0 the event which level beyond critical report
1 the event which level beyond warning report
2 the event which level beyond information report
example:syscfg -t monitor -r disk 2
-m,--message <num> tests whether the trap channel is available.
example:syscfg -t monitor -m 1
-u,--utilize <type> <utilization>set the threshold of hardware utilization
rate, <utilization>(1 - 100)
cpu set the threshold of cpu utilization rate
disk set the threshold of disk utilization rate
mem set the threshold of memory utilization rate
example:syscfg -t monitor -u cpu 50
bmc operate with bmc
-i,--info output the information of bmc
-s,--set <argument> set bmc configuration
eth0 ipaddr <ipaddr> <mask> set eth0 ipv4 address and mask
eth0 gateway <gateway> set eth0 ipv4 gateway
eth0 mode <dhcp|static> set eth0 ipv4 mode
eth0 ipaddr6 <ipaddr6/prefix> set eth0 ipv6 address
eth0 gateway6 <gateway6> set eth0 ipv6 gateway
eth0 mode6 <dhcp|static> set eth0 ipv6 mode
eth0 state <enable|disable> enable or disable eth0 function
adduser <username> add user
deluser <username> delete user
password <username> modify password
privilege <username> <privilege> modify user privilege
15 no access
2 user
3 operator
4 administrator
rename <username> <new username> rename user name
-g,--get <argument> get bmc configuration
eth0 get eth0 information
userlist get user list information
-r,--reboot reboot bmc
-u,--update <file> update bmc firmware
power operate with power

iBMA
-i,--info output the information of power

-s,--set <argument> set power configuration
capping enable <value> enable power capping function and set
the capping value
capping disable disable power capping function
-g,--get <argument> get power configuration
capping get power capping information
fan operate with fan
-s,--set <argument> set fan configuration
mode auto set fan mode to auto
mode manual [timeout] set fan mode to manual,timeout
value:0-100000000,if you input timeout value empty,use the default value
level <value> set fan rotate speed,value is percent
-g,--get <argument> get fan configuration
mode get fan mode information
level get fan rotate speed information
-h,--help:output help information
4.3.11 Querying the Software Version

Obtaining the Software Version (-v or --version)
Function
This command is used to obtain the software version of syscfg commands.
Format
syscfg -v (short command)
syscfg --version (long command)
Parameters
None
Usage Guidelines
None
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -v

iBMA
4.3.12 Obtaining and Configuring iBMC Information

Obtaining Basic Information About the iBMC (-i or --info)
Function
This command is used to obtain basic information about the iBMC.
Format
syscfg -t bmc –i (short command)
syscfg --target bmc --info (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./syscfg -t bmc -i
*****************************************************************************
Host Name : huaweitest
IPMI Version : 2.0
iMana Version : (U1029)5.83
FPGA Version : (U1011)024
CPLD Version : (U1005)001
*****************************************************************************
Setting the IPv4 Address and Subnet Mask for the iBMC Network Port (-s or --set
eth0 ipaddr)
Function
This command is used to set the IPv4 address and subnet mask for the iBMC network port.
Format
syscfg -t bmc –s eth0 ipaddr <ipaddr> <mask> (short command)
syscfg --target bmc --set eth0 ipaddr <ipaddr> <mask> (long command)
Parameters
ipaddr Specifies the IPv4 address for the iBMC network port. -

iBMA

mask Specifies the IPv4 subnet mask. -
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 ipaddr 192.168.50.221
255.255.0.0
Set BMC eth0 ipv4 address success.
Setting the IPv4 Gateway Address for the iBMC Network Port (-s or --set eth0
gateway)
Function
This command is used to set the IPv4 gateway address for the iBMC network port.
Format
syscfg -t bmc -s eth0 gateway <gateway> (short command)
syscfg --target bmc --set eth0 gateway <gateway> (long command)
Parameters
gateway Specifies the IPv4 gateway address. -
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 gateway 192.168.50.1
Set BMC eth0 ipv4 gateway success.
Setting the IPv6 Address for the iBMC Network Port (-s or --set eth0 ipaddr6)
Function
This command is used to set the IPv6 address for the iBMC network port.
Format
syscfg -t bmc –s eth0 ipaddr6 <ipaddr6/prefix> (short command)
syscfg --target bmc --set eth0 ipaddr6 <ipaddr6/prefix> (long command)

iBMA
Parameters
ipaddr6/prefix Specifies the IPv6 address. -
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 ipaddr6 1234::123/63
Set BMC eth0 ipv6 address success.
Setting the IPv6 Gateway Address for the iBMC Network Port (-s or --set eth0
gateway6)
Function
This command is used to set the IPv6 gateway address for the iBMC network port.
Format
syscfg -t bmc -s eth0 gateway6 <gateway6> (short command)
syscfg --target bmc --set eth0 gateway6 <gateway6> (long command)
Parameters
gateway6 Specifies the IPv6 gateway address. -
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 gateway6 2011::32
Set BMC eth0 ipv6 gateway success.
Setting the IPv4 Address Mode for the iBMC Network Port (-s or --set eth0 mode)
Function
This command is used to set the IPv4 address mode for the iBMC network port.
Format
syscfg -t bmc -s eth0 mode <mode> (short command)

iBMA
syscfg --target bmc --set eth0 mode <mode> (long command)
Parameters
Mode Specifies the IPv4 address mode. The value is dhcp or static.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 mode static
Set BMC eth0 ipv4 mode success.
Setting the IPv6 Address Mode for the iBMC Network Port (-s or --set eth0
mode6)
Function
This command is used to set the IPv6 mode for the iBMC network port.
Format
syscfg -t bmc -s eth0 mode6 <mode>
syscfg --target bmc --set eth0 mode6 <mode>
Parameters
Mode Specifies the IPv6 address mode. The value is dhcp or static.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s eth0 mode6 static
Set BMC eth0 ipv6 mode success.
Restarting the iBMC (-r or --reboot)
Function
This command is used to restart the iBMC.

iBMA
Format
syscfg -t bmc –r (short command)
syscfg --target bmc --reboot (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -r
Set BMC reboot success.
Upgrading the iBMC Firmware (-u or --update)
Function
This command is used to upgrade the iBMC firmware.
Format
syscfg -t bmc -u <file> (short command)
syscfg --target bmc --update <file> (long command)
Parameters
Parameter Description Remarks
file Specifies the iBMC Ensure that the upgrade file

firmware upgrade file. exists and is correct.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -u /home/zxx/image.hpm
Performing preparation stage...
OK
Performing Upgrade stage...
Upgrading SUPPORT [Total 4335 bytes]
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] sent 4335 bytes
Upgrading IPMC [Total 24367616 bytes]
[>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>] sent 24367616 bytes
OK

iBMA
Performing activation stage...

..................................................................................
..........................
OK
BMC UPGRADE SUCCESSFUL.
Adding an iBMC User (-s or --set adduser)
Function
This command is used to add an iBMC user.
Format
syscfg -t bmc -s adduser <username> (short command)
syscfg --target bmc --set adduser <username> (long command)
Parameters
username Identifies the new user. -
Usage Guidelines
After you run this command, you need to enter the password for the new user and confirm the
password. The two passwords must be the same.
Add a BMC user name, and the new password must meet the complexity requirements.
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s adduser testuser
Password:********
Confirm password:********
Set BMC user(testuser) success.
Deleting an iBMC User (-s or --set deluser)
Function
This command is used to delete an iBMC user.
Format
syscfg -t bmc -s deluser <username> (short command)

iBMA
syscfg --target bmc --set deluser <username> (long command)
Parameters
username Identifies the user to be -
deleted.
Usage Guidelines
Example
Changing the Password for an iBMC User (-s or --set password)
Function
This command is used to change the password for an iBMC user.
Format
syscfg -t bmc -s password <username> (short command)
syscfg --target bmc --set password <username> (long command)
Parameters
username Identifies the user whose -
password is to be changed.
Usage Guidelines
After you run this command, you need to enter a new password for the user and confirm the
password. The two passwords must be the same.
Change the password of a iBMC user, and the new password must meet the complexity requirements.
The operation command is the invoked standard IPMI command protocol.

iBMA
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s password testuser
New password:*********
Confirm password:*********
Change BMC user password success.
Modifying Rights of an iBMC User (-s or --set privilege)
Function
This command is used to modify rights of an iBMC user.
Format
syscfg -t bmc -s privilege <username> <privilege> (short command)
syscfg --target bmc --set privilege <username> <privilege> (long command)
Parameters
rights are to be modified.
privilege Specifies the user rights.  15: no access
 2: user
 3: operator
 4: administrator
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s privilege testuser 3
Change BMC user(testuser) privilege success.
Changing the Name for an iBMC User (-s or --set rename)
Function
This command is used to change the name for an iBMC user.
Format
syscfg -t bmc -s rename <username> <new_username> (short command)

iBMA
syscfg --target bmc --set rename <username> <privilege> (long command)
Parameters
name is to be changed.
new_username Specifies the new user -
name.
privilege Specifies the user rights.  15: no access
 2: user
 3: operator
 4: administrator
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -s rename testuser huawei
Change BMC user name success.
Obtaining IP Information for the iBMC Network Port (-g or --get eth0)
Function
This command is used to obtain IP information for the iBMC network port.
Format
syscfg -t bmc -g eth0 (short command)
syscfg --target bmc --get eth0 (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -g eth0
*****************************************************************************
Enabled : enable

iBMA
Mode : static
IP Address : 192.168.3.200
Subnet Mask : 255.255.255.0
Default Gateway : 192.168.3.200
MAC Address : 00-18-82-18-19-12
IPv6 information:
Mode : static
IPv6 Address : ::
Default Gateway : ::
Local Link Addr : fe80::218:82ff:fe18:1912/64
*****************************************************************************
Obtaining Information About the iBMC User List (-g or --get userlist)
Function
This command is used to obtain information about the iBMC user list.
Format
syscfg -t bmc –g userlist (short command)
syscfg --target bmc --get userlist (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t bmc -g userlist
ID Name Privilege
1
2 root ADMINISTRATOR
3 huawei OPERATOR
4
5
6
7
8
9
10
11
12
13
14
15
16

iBMA
17
4.3.13 Obtaining and Configuring Server Power Information

Obtaining Basic Server Power Information (-i or --info)
Function
This command is used to obtain basic server power information.
Format
syscfg -t power –i (short command)
syscfg --target power --info (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t power -i
*****************************************************************************
Current Power : 83 watts
Max Power : 347 watts
Average Power : 84 watts
Total Consume : 179.580667 kilowatt-hour
*****************************************************************************
Setting the Power Capping Value for the Server (-s or --set)
Function
This command is used to set the power capping value for the server.
Format
syscfg -t power –s capping <operate> [value] (short command)
syscfg --target power --set capping <operate> [value] (long command)
Parameters

iBMA

operate Enables or disables  enable
power capping.  disable
value Specifies the power  If the value of Operate is disable, value is
capping value. unavailable.
 If the value of Operate is enable, value is
available. For details about the range of value, see
the prompt information on the iBMC WebUI.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t power -s capping enable 9988
Set power capping success.
Obtaining the Power Capping Value for the Server (-g or --get)
Function
This command is used to obtain the power capping value for the server.
Format
syscfg -t power –g capping (short command)
syscfg --target power --get capping (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t power -g capping
*****************************************************************************
Power Capping : Enable
Power Budget : 9988 watts
*****************************************************************************

iBMA
4.3.14 Obtaining and Configuring Server Fan Information

Setting the Fan Operating Mode for the Server (-s or --set mode)
Function
This command is used to set the fan operating mode for the server.
Format
syscfg -t fan -s mode <mode> [timeout] (short command)
syscfg --target fan --set mode <mode> [timeout] (long command)
Parameters
mode Specifies the fan  manual: indicates the manual mode.

operating mode.  auto: indicates the automatic mode.
timeout Specifies the timeout  If the value of mode is auto, timeout is
period, in seconds. unavailable.
 If the value of mode is manual, timeout is
optional. If you do not specify timeout, the
default value 30 is used.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t fan -s mode manual 200
Set fan mode success.
Current Mode: manual, timeout 200 seconds
Setting the Fan Speed Percentage for the Server (-s or --set level)
Function
This command is used to set the fan speed percentage for the server.
Format
syscfg -t fan -s level <value> (short command)
syscfg --target fan --set level <value> (long command)

iBMA
Parameters
value Specifies the fan speed The value is an integer ranging from 30 to
percentage. 100.
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t fan -s level 90
Set fan level 90 success.
Obtaining the Fan Operating Mode for the Server (-g or --get mode)
Function
This command is used to obtain the fan operating mode for the server.
Format
syscfg -t fan -g mode (short command)
syscfg --target fan --get mode (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t fan -g mode
*****************************************************************************
Current Mode: manual, timeout 182 seconds
*****************************************************************************
Obtaining the Fan Speed Percentage for the Server (-g or --get level)
Function
This command is used to obtain the fan speed percentage for the server.

iBMA
Format
syscfg -t fan -g level (short command)
syscfg --target fan --get level (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./syscfg -t fan -g level
*****************************************************************************
Fan Level : 90%
*****************************************************************************
4.3.15 Sending the Raw IPMI Command

Sending the Raw IPMI Command (-r)
Function
This command is used to send the raw Intelligent Platform Management Interface (IPMI)
command.
Format
syscfg -t ipmi -r rawcmd (short command)
Parameters
rawcmd Specifies the raw IPMI The value is represented in hexadecimal notation,
command. for example, 0x06 0x01 or 06 01.
Usage Guidelines
Only the short command is supported.
This command is available only on Windows.
Example
c:\Program Files\huawei\HwBMAService>syscfg -t ipmi -r 06 01
recv 16 bytes
0x00 0x01 0x81 0x05 0x8b 0x02 0x8f 0xdb 0x07 0x00 0x11 0xaa 0x06 0xaa 0x00 0x00

iBMA
Querying the FRU Information (-fru)
Function
This command is used to send the raw Intelligent Platform Management Interface (IPMI)
command to query the fru information.
Format
syscfg -t ipmi -fru
Parameters
None
Usage Guidelines
Only the short command is supported.
This command is available only on Windows.
Example
c:\Program Files\huawei\HwBMAService>syscfg -t ipmi -fru
FRU Device Description:Builtin FRU Device (ID 0, Mainboard)
Mfg. Date :1996/01/01 Mon 00:00:00
Board Manufacturer :Huawei Technologies Co., Ltd.
Board Product Name :
Board Serial Number :
Product Manufacturer :Huawei Technologies Co., Ltd.
Product Serial Number :333
Product Asset Tag :333
4.4 hwkbox Commands

4.4.1 Viewing Help Information
Function
This command is used to obtain help information about hwkbox commands.
Precautions
 Install the kbox driver.
 Disable the kdump service.For details, see table 3-9 in 3.1.8 Querying Events in the
Black Box.

iBMA
Format
hwkbox -h (short command)
hwkbox --help (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox -h
Usage:
hwkbox <-r|-w|-c|-p|-v|-h>
hwkbox user <-r|-w|-c> : operate with user region of kbox
-r,--read [output filename]: read data from kbox
-w,--write <input filename>: write data to kbox
-c,--clear: clear data of kbox
-p,--parse <data filename> [parse filename]: write kbox original data
-v,--version: display the software version information
-h,--help: display the help information
4.4.2 Viewing the Software Version

Function
This command is used to obtain the software version of hwkbox commands.
Format
hwkbox -v (short command)
hwkbox --version (long command)
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./hwkbox -v

iBMA
4.4.3 Managing and Parsing the Kbox Image File

Reading Data from the Kbox Area (-r or --read)
Function
This command is used to read data from the kbox area.
Format
hwkbox -r [output filename]
hwkbox --read [output filename]
Parameters
output filename Identifies the file to be read from the kbox area. -
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox -r
read date from kbox succeed!
Writing Data to the Kbox Area (-w or --write)
Function
This command is used to write data to the kbox area.
Format
hwkbox -w [input filename] (short command)
hwkbox --write [input filename] (long command)
Parameters
input filename Identifies the file to be written to the kbox area. -
Usage Guidelines
When running the short or long command, ensure that the file specified by input filename
exists.

iBMA
Example
linux-susell:/opt/huawei/bma/bin # ./hwkbox -w kbox_result.txt
write date to kbox succeed!
Clearing the Kbox Area (-c or --clear)
Function
This command is used to clear the kbox area.
Format
hwkbox -c (short command)
hwkbox --clear (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox -c
clear kbox date succeed!
Analysing the Kbox Original Image File (-r or --read)
Function
This command is used to analyse the kbox original image file.
Format
hwkbox -p <data filename> <parse filename>
hwkbox --parse <data filename> <parse filename>
Parameters
data indicates the kbox original –
filename image file.
parse indicates the readable file If input the value, the value is used, then
filename after analysed. the default file is used.

iBMA
Usage Guidelines
Ensure that the data filename is existed. If the parse filename is user defined file, please
ensure the path is correct.
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox -p kbox_data_2012-5-3_19-32-27.img
parse kbox data succeed!
4.4.4 Managing the Kbox User Area

Reading Data from the Kbox User Area (-r or --read)
Function
This command is used to read data from the kbox user area.
Format
hwkbox user -r [output filename] (short command)
hwkbox user --read [output filename] (long command)
Parameters
output Identifies a data file in If you do not specify output filename, the system
filename the kbox user area. reads the default data file. If you specify output
filename, the system reads the specified file.
Usage Guidelines
exists.
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox user -r
read date from kbox user log succeed!
Writing Data to the Kbox User Area (-w or --write)
Function
This command is used to write data to the kbox user area.

iBMA
Format
hwkbox user -w <input filename> (short command)
hwkbox user --write <input filename> (long command)
Parameters
input filename Specifies the file to be written to the kbox user area. -
Usage Guidelines
exists.
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox user -w Result.txt
write date to kbox user log succeed!
Clearing the Kbox User Area (-c or --clear)
Function
This command is used to clear the kbox user area.
Format
hwkbox user -c (short command)
hwkbox user --clear (long command)
Parameters
None
Usage Guidelines
Example
linux-suse11:/opt/huawei/bma/bin # ./hwkbox user -c
clear kbox user log succeed!
4.5 hwwatchdog Commands

Precautions

iBMA
The watchdog driver in the /opt/huawei/bma/drivers/watchdog/bsp_wd_driver.ko directory

is installed before you use the hwwatchdog command-line interface (CLI). Run the following
command on the shell CLI.
insmod /opt/huawei/bma/drivers/watchdog/bsp_wd_driver.ko
4.5.1 Viewing Help Information

Function
This command is used to obtain help information about hwwatchdog commands.
Format
hwwatchdog -h
hwwatchdog --help
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog -h
Usage:
hwwatchdog <set|get|start|stop|restart>
set <enable/disable> <timeout=900> <feedtime=180> set watchdog
get display watchdog config
start start watchdog
restart restart watchdog
stop stop watchdog
-v,--version: display the software version
information
-h,--help: display the help information
4.5.2 Viewing the Software Version

Function
This command is used to obtain the software version of hwwatchdog commands.

iBMA
Format
hwwatchdog -v
hwwatchdog --version
Parameters
None
Usage Guidelines
Example
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog -v
4.5.3 Querying and Setting Watchdog Parameters

Reading Watchdog Parameters (get)
Function
The get command is used to read watchdog parameters.
Format
hwwatchdog get
Parameters
None
Usage Guidelines
None
Example
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog get
disable,timeout=900,feedtime=180
If the driver has not been installed, the following error information is displayed after
the get command is executed:
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog get
insmod: can't read '/opt/huawei/bma/drivers/bsp_wd_driver.ko': No such file or
directory
insmod: can't read '/opt/huawei/bma/drivers/bsp_wd_driver.ko': No such file or
directory

iBMA
Setting Watchdog Parameters (set)
Function
The set command is used to set watchdog parameters.
Format
hwwatchdog set <enable/disable> <timeout=900> <feedtime=180>
Parameters
enable/disable Enables or disables the watchdog -

function.
timeout=900 Specifies the watchdog timeout interval, -
which is 15 minutes by default.
feedtime=180 Specifies the interval for restarting the The value of feedtime must
watchdog timer, which is 3 minutes by be less than the value of
default. timeout
Usage Guidelines
1. You can modify one or more of the three parameters. For a parameter that is not
modified, its previous value is used. For a parameter that has not been set, its default
value is used.
2. After the parameters are set, the settings are saved to /etc/bsp_watchdog.conf.
3. After the parameters are set, the system prompts you to restart the watchdog for the
settings to take effect.
Example
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog set enable timeout=800 feedtime=90
set watchdog config ok,please restart watchdog!
4.5.4 Starting, Restarting, and Stopping the Watchdog

Function
The start command is used to start the watchdog, the restart command is used to restart the
watchdog, and the stop command is used to stop the watchdog.
Format
hwwatchdog start
hwwatchdog restart
hwwatchdog stop

iBMA
Parameters
None
Usage Guidelines
1. The start command reads the previously configured watchdog parameters, and then
starts the watchdog and watchdog timer restart thread. If the watchdog function is
disabled, a failure message is displayed.
2. The restart command stops the watchdog and watchdog timer restart thread, and then
restarts them based on the watchdog configuration file.
3. The stop command stops the watchdog and watchdog timer restart thread.
Example
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog start
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog restart
linux-susell:/opt/huawei/bma/bin # ./hwwatchdog stop
linux-susell:/opt/huawei/bma/bin #

iBMA
User Guide 5 Alarm Reference
5 Alarm Reference
About This Chapter

5.1 #327686_The DIMM ECC Value Increases at a Rate Higher Than the Threshold or an
Uncorrectable ECC Error Has Occurred
5.2 #327688_Memory ECC Value Increase Speed Restored to the Acceptable Range
5.3 #196610_CPU Detected an MCE
5.4 #196612_CPU Detected That an MCE Rectified
5.5 #196618_CPU Temperature Restored to the Acceptable Range
5.6 #196620_CPU Temperature Higher Than the Major Alarm Threshold and Lower Than
the Critical Alarm Threshold
5.7 #196622_CPU Sensor Detected Error or Temperature Too High
5.8 #196624_Failed to Detect the CPU Temperature
5.9 #262182_Hard Disk Inserted
5.10 #262184_Hard Disk Removed
5.11 #262190_Hard Disk Reported a Predictable Error
5.12 #262196_Hard Disk Score Lower Than 80
5.13 #262198_Hard Disk Offline
5.14 #262206_Failed to Detect Hard Disk Temperature
5.15 #262210_Hard Disk Temperature Restored to the Acceptable Range
5.16 #262212_Hard Disk Temperature Higher Than the Major Alarm Threshold and Lower
Than the Critical Alarm Threshold
5.17 #262214_Hard Disk Temperature Higher Than the Critical Alarm Threshold
5.18 #262216_Direct Phyisical Hard Disk Inserted
5.19 #262218_Direct Physical Hard Disk Removed
5.20 #262224_Direct Physical Hard Disk Reported a Predictable Error
5.21 #262228_Failed to Detect the Direct Physical Hard Disk Temperature

iBMA
5.22 #262232_Direct Physical Hard Disk Temperature Restored to the Acceptable Range
5.23 #262234_Direct Physical Hard Disk Temperature Higher Than the Major Alarm
Threshold and Lower Than the Critical Alarm Threshold
5.24 #262236_Direct Physical Hard Disk Temperature Higher Than the Critical Alarm
Threshold
5.25 #262242_Direct Physical Hard Disk Score Lower Than 80
5.26 #262146_RAID Controller Card Battery Charged Properly
5.27 #262150_The RAID Controller Card Battery Learning Cycle Started
5.28 #262154_RAID Controller Card Battery Learning Cycle Delayed
5.29 #262156_RAID Controller Card Battery Learning Cycle Ended
5.30 #262158_Controller Batter Low
5.31 #262160_RAID Controller Card Battery Temperature Higher Than the Threshold
5.32 #262162_RAID Controller Card Battery Removed
5.33 #262164_RAID Controller Card Battery Learning Timed Out
5.34 #262166_Rebuilding a Virtual Disk Started
5.35 #262168_Rebuilding a Virtual Disk Finished
5.36 #262172_Consistency Check or Another Operation Failed on Virtual Disk
5.37 #262174_A Virtual Disk has been Created.
5.38 #262176_Virtual Disk Deleted
5.39 #262178_Virtual Disk Degraded
5.40 #262180_Virtual Disk Failed
5.41 #65538_Memory Usage Upper Than Threshold
5.42 #65540_Memory Usage Restored Normally
5.43 #65542_CPU Usage Upper Than Threshold
5.44 #65544_CPU Usage Restored Normally
5.45 #65546_Disk Usage Upper Than Threshold
5.46 #65548_Disk Usage Restored Normally
5.47 #65550_SWAP Usage Upper Than Threshold
5.48 #65552_SWAP Usage Restored Normally
5.49 #65554_Assigned Process Abnormal
5.50 #65566_Assigned Process Ok
5.51 #524290_The Monitor Service Started
5.52 #393218_Service System Network Port Properly Connected
5.53 #393220_Service System Network Port Not Connected

iBMA
5.1 #327686_The DIMM ECC Value Increases at a Rate

Higher Than the Threshold or an Uncorrectable ECC Error
Has Occurred
Description
This alarm is generated when the dual in-line memory module (DIMM) error checking and
correcting (ECC) value increases at a rate higher than the threshold or an uncorrectable ECC
error has occurred.
Attribute
Alarm ID Alarm Severity Alarm Type
327686 Critical Fault alarm
Impact on the System

The system is operating abnormally or may even crash. Data may be damaged.
Possible Causes
The capacitor charging status is changed and a fault may occur in the DIMM due to adjacent
electronic interference caused by alpha particles from radioactive substances or high-energy
neutrons from cosmic rays. This alarm does not necessarily indicate a DIMM hardware fault.
The system attempts to reset the DIMM or rewrite data to the DIMM. If the DIMM is not
recovered after reset or rewriting, short circuits may occur in data line pins.
Procedure
Step 1 Shut down the operating system (OS) and replace the faulty DIMM.
Step 2 Restart the OS. Then check whether this alarm is cleared. If this alarm persists, repeat steps 1
and 2.
----End
5.2 #327688_Memory ECC Value Increase Speed Restored

to the Acceptable Range
Description
This alarm is generated when the iBMA detects that the memory error checking and
correcting (ECC) value increase speed is restored to the acceptable range.
Attribute

iBMA

327688 Info Info

None
Possible Causes
The fault is rectified.
Procedure
Step 1 No action is required.
----End
5.3 #196610_CPU Detected an MCE

Description
This alarm is generated when the CPU detects a machine check exception (MCE).
Attribute
196610 Major Warning

All MCEs detected by the software can be rectified and will not cause a system crash.
Possible Causes
An error has occurred in some hardware or an area in the hardware system.
Procedure
Step 1 Determine the hardware error type based on the MCE error code. Replace the faulty hardware
by referring to product documents or contact the hardware manufacturer for help.
----End

iBMA
5.4 #196612_CPU Detected That an MCE Rectified

Description
This alarm is generated when the CPU detects that a machine check exception (MCE) is
rectified.
Attribute
196612 Info Info

This alarm has no adverse impact on the system.
Possible Causes
An error in some hardware or an area in the hardware system has been corrected.
Procedure
----End
5.5 #196618_CPU Temperature Restored to the Acceptable

Range
Description
This alarm is generated when the iBMA detects that its temperature is restored to the
acceptable range.
Attribute
196618 Info Info

The CPU temperature is restored to the normal range. This alarm has no adverse impact on
the system.
Possible Causes
The CPU heat dissipation error has been corrected.

iBMA
Procedure
----End
5.6 #196620_CPU Temperature Higher Than the Major

Alarm Threshold and Lower Than the Critical Alarm
Threshold
Description
This alarm is generated when the iBMA detects that the CPU temperature is higher than the
major alarm threshold and lower than the critical alarm threshold.
Attribute

The hardware system is critical. The continuous increase in temperature may result in a
critical alarm.
Possible Causes
An error has occurred in CPU heat dissipation or some hardware or an area in the hardware
system.
Procedure
Step 1 Determine the hardware error type based on the machine check exception (MCE) error code.
Replace the faulty hardware by referring to product documents or contact the hardware
manufacturer for help.
Step 2 If the temperature is high, move the device to a low-temperature environment and increase the
fan speed.
----End
5.7 #196622_CPU Sensor Detected Error or Temperature

Too High
Description
This alarm is generated when the CPU temperature exceeds the threshold.

iBMA
Attribute

The machine check exceptions (MCEs) detected by the software are recoverable and will not
result in system breakdown.
This alarm indicates that the system hardware is faulty and the high temperature may result in
the CPU restart.
Possible Causes
An exception occurs in a hardware component or in the CPU heat sink.
Procedure
Step 1 Determine the error type based on MCE error codes. Replace the faulty devices by referring
to related product documents or contact the vendor for help.
Step 2 If the temperature is higher than the threshold, move the device to the low-temperature
environment and increase the fan speed. If the alarm is not cleared, repeat step 2.
----End
5.8 #196624_Failed to Detect the CPU Temperature

Description
This alarm is generated when the operating system (OS) fails to detect the CPU temperature.
Attribute

This alarm does not cause a system crash.
Possible Causes
CPU temperature detection is not supported or the CPU fails.

iBMA
Procedure
Step 1 Ask Huawei maintenance engineers to check whether the OS can detect CPU temperature.
Step 2 Replace the CPU.
----End
5.9 #262182_Hard Disk Inserted

Description
This alarm is generated when the iBMA detects that a hard disk is inserted.
Attribute
262182 Info Info

None
Possible Causes
 A physical hard disk is inserted.
 A physical hard disk gets online.
 A SMART status error is corrected.
Procedure
----End
5.10 #262184_Hard Disk Removed

Description
The alarm is generated when the hard disk drive (HDD) backplane is not detected.
Attribute

iBMA

 If the hard disk is straight-through or is in a non-redundant virtual disk group, the system
cannot detect this storage device.
 If the hard disk is in the redundant virtual disk group, this disk group is degraded and the
system storage security deteriorates.
Possible Causes
 A hard disk is removed.
 A hard disk is offline.
 A SMART exception is detected.
 The health score of a hard disk is lower than 80.
Procedure
Step 1 Query the virtual disk group status. If the status is offline, set the disk group to the online
status. Turn to step 2 if this operation fails.
Step 2 Replace the faulty hard disks and recover the virtual disk.
----End
5.11 #262190_Hard Disk Reported a Predictable Error

Description
This alarm is generated when a hard disk reports a predictable error.
Attribute

 If the hard disk is a pass-through one or in a non-redundant virtual disk, the system
cannot detect this hard disk.
 If the hard disk is in a redundant virtual disk, this virtual disk is degraded and system
storage security decreases.
Possible Causes
A hard disk error has occurred.
Procedure
Step 1 Replace the faulty hard disk and recover the virtual disk.
----End

iBMA
5.12 #262196_Hard Disk Score Lower Than 80

Description
This alarm is generated when the score of a hard disk is lower than 80.
Attribute

Possible Causes
Procedure
----End
5.13 #262198_Hard Disk Offline

Description
This alarm is generated when the iBMA detects that a hard disk is offline.
Attribute


iBMA
Possible Causes
A physical hard disk is faulty or offline.
Procedure
Step 1 Query the status of the virtual disk. If the virtual disk is offline, configure it to enter online
state.
If the operation fails, go to Step 2.
----End
5.14 #262206_Failed to Detect Hard Disk Temperature

Description
This alarm is generated when the iBMA failed to detect the hard disk temperature.
Attribute

High temperature may cause damage to the hard disk or shorten the hard disk service time.
Possible Causes
 The iBMA is faulty or the hard disk does not support temperature detection.
 The hard disk is faulty.
Procedure
Step 1 Reinstall the iBMA.
----End

iBMA
5.15 #262210_Hard Disk Temperature Restored to the

Acceptable Range
Description
This alarm is generated when the iBMA detects that the hard disk temperature is restored to
the acceptable range.
Attribute
262210 Info Info

None
Possible Causes
The hard disk temperature is restored to the acceptable range.
Procedure
----End
5.16 #262212_Hard Disk Temperature Higher Than the

Major Alarm Threshold and Lower Than the Critical
Alarm Threshold
Description
This alarm is generated when the iBMA detects that the hard disk temperature is higher than
the major alarm threshold and lower than the critical alarm threshold.
Attribute

High hard disk temperature may cause damage to the hard disk and shorten the hard disk
service time.

iBMA
Possible Causes
 An error has occurred in server heat dissipation.
Procedure
Step 1 Check whether the heat dissipation system of the server is operating properly. If an error has
occurred in this system, contact Huawei technical support.
Step 2 Replace the faulty hard disk.
----End
5.17 #262214_Hard Disk Temperature Higher Than the

Critical Alarm Threshold
Description
This alarm is generated when the iBMA detects that the hard disk temperature is higher than
the critical alarm threshold.
Attribute
262214 Critical Warning

service time.
Possible Causes
Procedure
----End

iBMA
5.18 #262216_Direct Phyisical Hard Disk Inserted

Description
This alarm is generated when the iBMA detects that a direct physical hard disk is inserted.
Attribute
262216 Info Info

None
Possible Causes
 A direct physical hard disk is inserted.
 A direct physical hard disk gets online.
Procedure
----End
5.19 #262218_Direct Physical Hard Disk Removed

Description
The alarm is generated when the direct Physical hard disk drive backplane is not detected.
Attribute

The system cannot detect this storage device.
Possible Causes
A hard disk is removed.
Procedure
Step 1 Insert a hard disk.

iBMA
----End
5.20 #262224_Direct Physical Hard Disk Reported a

Predictable Error
Description
This alarm is generated when a direct physical hard disk reports a predictable error.
Attribute

The system cannot detect this hard disk.
Possible Causes
Procedure
----End
5.21 #262228_Failed to Detect the Direct Physical Hard

Disk Temperature
Description
This alarm is generated when the iBMA failed to detect the direct physical hard disk
temperature.
Attribute

High temperature may cause damage to the hard disk or shorten the hard disk service time.

iBMA
Possible Causes
 The iBMA is faulty or the hard disk does not support temperature detection.
Procedure
Step 1 Reinstall the iBMA.
----End
5.22 #262232_Direct Physical Hard Disk Temperature

Restored to the Acceptable Range
Description
This alarm is generated when the iBMA detects that the direct physical hard disk temperature
is restored to the acceptable range.
Attribute
262232 Info Info

None
Possible Causes
The hard disk temperature is restored to the acceptable range.
Procedure
----End

iBMA

Higher Than the Major Alarm Threshold and Lower Than
the Critical Alarm Threshold
Description
is higher than the major alarm threshold and lower than the critical alarm threshold.
Attribute

service time.
Possible Causes
Procedure
Step 2 If the warning cannot be cleared, replace the faulty hard disk.
----End

Higher Than the Critical Alarm Threshold
Description
is higher than the critical alarm threshold.
Attribute

iBMA

service time.
Possible Causes
Procedure
Step 2 If the warning cannot be cleared, replace the faulty hard disk.
----End
5.25 #262242_Direct Physical Hard Disk Score Lower Than

80
Description
This alarm is generated when the score of a direct physical hard disk is lower than 80.
Attribute

The system cannot detect this hard disk.
Possible Causes
Procedure
----End

iBMA
5.26 #262146_RAID Controller Card Battery Charged

Properly
Description
This alarm is generated when the iBMA detects that the redundant array of independent disks
(RAID) controller card battery is charged properly.
Attribute
262146 Info Info

None
Possible Causes
The RAID controller card battery is working properly.
Procedure
----End
5.27 #262150_The RAID Controller Card Battery Learning

Cycle Started
Description
(RAID) controller card battery learning cycle starts.
Attribute
262150 Info Info

None
Possible Causes
The RAID controller card battery learning cycle starts.

iBMA
Procedure
----End
5.28 #262154_RAID Controller Card Battery Learning

Cycle Delayed
Description
(RAID) controller card battery learning cycle is delayed.
Attribute
262154 Info Info

None
Possible Causes
The RAID controller card battery learning cycle is deployed.
Procedure
----End

Cycle Ended
Description
(RAID) controller card battery learning cycle ends.
Attribute
262156 Info Info

iBMA

None
Possible Causes
The RAID controller card battery learning cycle ends.
Procedure
----End
5.30 #262158_Controller Batter Low

Description
This alarm is generated when the battery is low in power.
Attribute

The cache data in the RAID controller card may be lost.
Possible Causes
The RAID battery discharges, fails, or is faulty.
Procedure
Step 1 Start the system. Charge the controller card battery properly for a while. If this alarm is not
cleared, the battery is faulty. Go to step 2.
Step 2 Shut down the operating system. Replace the controller card battery and go to step 1.
----End

iBMA
5.31 #262160_RAID Controller Card Battery Temperature

Higher Than the Threshold
Description
(RAID) controller card battery temperature is higher than the threshold.
Attribute

The RAID controller card battery may be damaged.
Possible Causes
 The RAID controller card battery is faulty or fails.
Procedure
Step 1 Verify that the heat dissipation system of the server is operating properly.
Step 2 Replace the RAID controller card battery.
----End
5.32 #262162_RAID Controller Card Battery Removed

Description
(RAID) controller card battery is removed.
Attribute


iBMA
Possible Causes
 The RAID controller card battery is faulty or fails.
 The RAID controller card battery is removed.
Procedure
Step 1 Install the RAID controller card battery properly.
Step 2 If the alarm persists, replace the RAID controller card battery.
----End

Timed Out
Description
This alarm is generated when the iBMA detects that redundant array of independent disks
(RAID) controller card battery learning times out.
Attribute

Possible Causes
The RAID controller card battery is faulty or fails.
Procedure
Step 1 Restart the server and ensure that the RAID controller card battery is properly charged for a
while. If this alarm persists, the battery is faulty. Go to Step 2.
Step 2 Replace the RAID controller card battery.
----End
5.34 #262166_Rebuilding a Virtual Disk Started

Description
This alarm is generated when the iBMA detects that rebuilding a virtual disk starts.

iBMA
Attribute
262166 Info Info

The access to the virtual disk is affected.
Possible Causes
The virtual disk is rebuilt manually.
Procedure
----End
5.35 #262168_Rebuilding a Virtual Disk Finished

Description
This alarm is generated when the iBMA detects that rebuilding a virtual disk finishes.
Attribute
262168 Info Info

None
Possible Causes
The virtual disk is rebuilt manually.
Procedure
----End

iBMA
5.36 #262172_Consistency Check or Another Operation

Failed on Virtual Disk
Description
This alarm is generated when consistency check or another operation fails on the virtual disk.
Attribute

A redundant array of independent disks (RAID) error has occurred.
Possible Causes
The virtual disk is manually deleted, or some or all physical hard disks in this virtual disk fail.
Procedure
Step 1 Install the physical hard disks properly or replace the faulty hard disks.
Step 2 Rebuild a virtual disk or recover the virtual disk.
----End
5.37 #262174_A Virtual Disk has been Created.

Description
A virtual disk has been created.
Attribute
262174 Info Info

None
Possible Causes
A virtual disk has been created.

iBMA
Procedure
----End
5.38 #262176_Virtual Disk Deleted

Description
A virtual disk is deleted.
Attribute

The storage device security decreases or even the system may fail to detect the storage device.
Possible Causes
Procedure
Step 1 Insert hard disks or replace the faulty hard disks.
Step 2 Re-create a virtual disk or recover the virtual disk.
----End
5.39 #262178_Virtual Disk Degraded

Description
This alarm is generated when the iBMA detects that the virtual disk is degraded.
Attribute

Storage device security decreases.

iBMA
Possible Causes
Procedure
----End
5.40 #262180_Virtual Disk Failed

Description
This alarm is generated when the iBMA detects that the virtual disk fails.
Attribute

The virtual disk is inaccessible and the system may crash.
Possible Causes
Procedure
----End
5.41 #65538_Memory Usage Upper Than Threshold

Description
This alarm is generated when the iBMA detects that the memory usage is upper than the
preset threshold.
Attribute

iBMA

65538 Major Warning

System performance is affected.
Possible Causes
 The system memory capacity is small.
 The memory usage of some processes is high.
Procedure
Step 1 Expand the memory capacity of the server, or use the tool provided by the system to identify
the processes with high memory usage and end these processes.
----End
5.42 #65540_Memory Usage Restored Normally

Description
This alarm is generated when the iBMA detects that the memory usage restored normally.
Attribute
65540 Info Info

None
Possible Causes
The memory usage is restored to the acceptable range.
Procedure
----End

iBMA
5.43 #65542_CPU Usage Upper Than Threshold

Description
This alarm is generated when the iBMA detects that the CPU usage is upper than the preset
threshold.
Attribute
65542 Major Warning

Possible Causes
 The system CPU resources are limited.
 The CPU usage of some processes is high.
Procedure
Step 1 Use the tool provided by the system to identify the processes with high CPU usage and end
these processes.
----End
5.44 #65544_CPU Usage Restored Normally

Description
This alarm is generated when the iBMA detects that the CPU usage restored normally.
Attribute
65544 Info Info

None
Possible Causes
The processes with high CPU usage have released CPU resources.

iBMA
Procedure
----End
5.45 #65546_Disk Usage Upper Than Threshold

Description
This alarm is generated when the iBMA detects that the disk usage is upper than the preset
threshold.
Attribute
65546 Major Warning

Possible Causes
 The total hard disk capacity of the server is small.
 Too many files are stored on the hard disk.
Procedure
Step 1 Expand the disk capacity of the server, or delete the unneeded files.
----End
5.46 #65548_Disk Usage Restored Normally

Description
This alarm is generated when the iBMA detects that the disk usage restored normally.
Attribute
65548 Info Info

None

iBMA
Possible Causes
The disk usage is restored to the acceptable range.
Procedure
----End
5.47 #65550_SWAP Usage Upper Than Threshold

Description
This alarm is generated when the iBMA detects that the swap usage is upper than the preset
threshold.
Attribute
65550 Major Warning

Possible Causes
 The total swap capacity of the server is small.
Procedure
Step 1 Expand the swap capacity of the server.
----End
5.48 #65552_SWAP Usage Restored Normally

Description
This alarm is generated when the iBMA detects that the swap usage restored normally.
Attribute
65552 Info Info

iBMA

None
Possible Causes
The swap usage is restored to the acceptable range.
Procedure
----End
5.49 #65554_Assigned Process Abnormal

Description
This alarm is generated when the iBMA detects that the system assigned process abnormal.
Attribute
65554 Major Warning

The specified process cannot function properly.
Possible Causes
 The specified process is running abnormally.
Procedure
Step 1 Restart this process.
----End
5.50 #65566_Assigned Process Ok

Description
This alarm is generated when the iBMA detects that the .system assigned process recovered
from an error.

iBMA
Attribute
65566 Info Info

None
Possible Causes
The process is recovered from an error.
Procedure
----End
5.51 #524290_The Monitor Service Started

Description
This alarm is generated when the iBMA detects that the monitor service is started.
Attribute
524290 Info Info

None
Possible Causes
The monitor service is restarted.
Procedure
----End

iBMA
5.52 #393218_Service System Network Port Properly

Connected
Description
This alarm is generated when the iBMA detects that the network port of the service system is
properly connected.
Attribute
393218 Info Info

None
Possible Causes
The network port is enabled, or a network cable is properly connected to it.
Procedure
----End
5.53 #393220_Service System Network Port Not Connected

Description
This alarm is generated when the iBMA detects that the network port of the service system is
not connected.
Attribute

The network communication of the service system is affected.
Possible Causes
 The network port is disabled or the network cable is disconnected.

iBMA
Procedure
Step 1 Enable the network port or reconnect the network cable.
----End

iBMA
User Guide A Appendix
A Appendix
A.1 Obtaining Help

This topic describes how to contact Huawei for technical support if a fault persists during
routine maintenance or troubleshooting.
A.2 Glossary
A.3 Acronyms and Abbreviations
A.1 Obtaining Help

This topic describes how to contact Huawei for technical support if a fault persists during
routine maintenance or troubleshooting.
A.1.1 Preparing to Contact Huawei Technical Support

This topic describes how to prepare to contact Huawei technical support, including collecting
fault information and preparing for debugging.
If a fault persists during routine maintenance or troubleshooting, contact Huawei technical
support.
To rectify a fault, make the following preparations before you contact Huawei technical
support.
Collecting Fault Information

You need to collect the following information:
 Your company name and detailed address
 Name and telephone number of the contact person
 Time when the fault occurred
 Fault symptom
 Device type and software version
 Measures taken after the fault occurred and results
 Fault severity and deadline for rectifying the fault

iBMA
Preparing for Debugging

When you seek technical support, Huawei technical support may ask you to perform some
operations to further collect fault information or even rectify the fault. You need to make
preparations before seeking technical support. For example, prepare spare server parts and
controller cards, screwdrivers, screws, serial cables, network cables, and other necessary
objects.
A.1.2 Obtaining Help from Huawei Support Website

This topic describes how to obtain help from http://support.huawei.com.
Huawei provides timely and efficient technical support over local offices, secondary technical
support systems, telephones, remote technologies, and onsite instructions.
Huawei technical support system consists of:
 Technical Support Department at Huawei Headquarters
 Technical support centers in local offices
 Huawei support website
 Customer service center
Huawei support website: http://support.huawei.com/enterprise
To view the latest product documentation at http://support.huawei.com, perform the following
steps:
1. Log in to http://support.huawei.com/enterprise.
2. Click Login. The Login page is displayed.
3. Enter your user name, password, and verification code, and click Login. The Technical
Support page is displayed.
4. In the navigation tree, click Documentation and select a product manual based on the
product name.
Alternatively, you can quickly locate a product manual by entering a keyword in the Search text box in
the upper right corner of the web page.
A.2 Glossary
C
clock The speed at which a computer
frequency performs basic operations, usually
represented in megahertz (millions of
cycles per second).
D
destination A client that receives Simple Network
Management Protocol (SNMP) trap
information.

iBMA
F
firmware The programmable, upgradable
software part of a hardware
component.
I
interface A boundary used for data exchange and interworking between a server and
other devices on the network, for example, a virtual local area network
(VLAN) interface.
IP address A 32-bit (four-byte) binary number
that uniquely identifies a host (a
computer) on a computer network that
uses the Internet Protocol for
communication, which enables
transmitting data in form of packet. An
IP address consists of four decimal
numbers, which are separated by dots
(.). For example, 127.0.0.1. The first
one to three bytes of an IP address
indicate the network to which the host
is connected and the remaining bits
indicate the host.
L
log file A file that records information about
system events generated during the
operating of the system. System event
information includes operating
information, input/output (I/O)
operations, abnormal operations, and
security information. A log file helps
you maintain and query the system.
R
redundanc The ability of a system to automatically replace the failed device with a
y backup one to keep functioning normally in the event of a device failure.
S
serial A number used for identifying a data
number block, an operation, or part of an
operation.
server A special computer that provides
services for clients over a network.
slot A position defined by an upper guide rail and a lower guide rail in a chassis.

iBMA
A slot houses a board.
T
trap A message sent from a managed device to the network management system
(NMS) without receiving a request to report critical events, for example, a
device restart.
A.3 Acronyms and Abbreviations

B
BIOS basic input/output system
C
CLI command-line interface
CPU central processing unit
E
ECC error checking and correcting
I
IP Internet Protocol
O
OS operating system
R
RAID redundant array of independent disks
S
SAS Serial Attached Small Computer System Interface
SATA Serial Advanced Technology Attachment
SMART Self-Monitoring, Analysis and Reporting Technology

SNMP Simple Network Management Protocol

iBMA


iBMA V100R002 User Guide 01

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

iBMA V100R002 User Guide 01

Uploaded by

Copyright:

Available Formats

iBMA

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Proprietary and Confidential

About This Document

Indicates a potentially hazardous situation that, if not

Issue 06 (2015-02-11) Huawei Proprietary and Confidential ii

Boldface The keywords of a command line are in boldface.

Type Change Description

Type Change Description

Issue 06 (2015-02-11) Huawei Proprietary and Confidential iii

Type Change Description

Mode Change Description

Deleted "Tecal" is deleted from the product document.

Issue 06 (2015-02-11) Huawei Proprietary and Confidential iv

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

2 Installing and Uninstalling the iBMA ...................................................................................... 8

3 Using the iBMA ........................................................................................................................... 65

Issue 06 (2015-02-11) Huawei Proprietary and Confidential v

3.1.4 Viewing Hard Disk Diagnosis Records ................................................................................................................... 68

4 Command Reference .................................................................................................................. 82

Issue 06 (2015-02-11) Huawei Proprietary and Confidential vi

4.4.4 Managing the Kbox User Area .............................................................................................................................. 140

5 Alarm Reference ........................................................................................................................ 146

Issue 06 (2015-02-11) Huawei Proprietary and Confidential vii

5.32 #262162_RAID Controller Card Battery Removed ................................................................................................ 167

A Appendix ................................................................................................................................... 181

Issue 06 (2015-02-11) Huawei Proprietary and Confidential viii

About This Chapter

1.1 Introduction to the iBMA

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 1

1.2 Function Modules

Figure 1-1 iBMA architecture

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 2

Table 1-1 iBMA function modules

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 3

1.3 Specifications and Features

Table 1-2 Supported OSs

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 4

1.4 Security Features

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 5

1.4.1 Product Networking

1.4.2 External Dependency

1.4.3 Security Policy

1.4.4 Security Isolation

1.4.5 Anti-attack Measures for Protocols and Interfaces

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 6

1.4.6 Product Development, Release, and Installation Security

1.4.7 Security of System Management and Maintenance

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 7

2 Installing and Uninstalling the iBMA

About This Chapter

2.1 Verifying the Upgrade Package Integrity

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 8

2.3 Installing, Upgrading, and Uninstalling the iBMA on

2.3.1 Configuring SNMP Service

Step 3 Add a user.

# sec.name source community

# groupName securityModel securityName

Step 5 Add the MIB view of the iBMA software.

Issue 06 (2015-02-11) Huawei Proprietary and Confidential 9

# Make at least snmpwalk -v 1 localhost -c public system fast again.

Step 6 Set the access control rights.