iBMA 2.0 User Guide 06 PDF
iBMA 2.0 User Guide 06 PDF
2.0
User Guide
Issue 06
Date 2019-04-02
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.
Website: http://e.huawei.com
Preface
Purpose
This document describes iBMA functions, and how to install and uninstall the iBMA software
and resolve common problems.
Intended Audience
This document is intended for:
l Enterprise administrators
l Enterprise end users
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 06 (2019-04-02)
l Modified 1.2 Software and Hardware Compatibility.
l Modified H.1 Description of the iBMA.ini Configuration File.
Issue 05 (2019-03-15)
l Added 4.2 Log Collection.
l Modified 1.1.2 Function Description.
l Modified 1.2 Software and Hardware Compatibility.
Issue 04 (2019-01-08)
l Modified 4.1 Common Troubleshooting.
l Modified H.1 Description of the iBMA.ini Configuration File.
l Modified M Compiling the iBMA Driver (Linux OS).
l Modified G Environmental Requirements.
Issue 03 (2018-10-31)
l Modified 1.1.2 Function Description.
l Modified 1.2 Software and Hardware Compatibility.
l Modified the command output and screenshots of installation in 2 Installing and
Uninstalling the iBMA.
l Modified H.1 Description of the iBMA.ini Configuration File.
l Added 1.1.1 System Architecture.
Issue 02 (2018-09-06)
Modified 1.2 Software and Hardware Compatibility.
Issue 01 (2018-06-30)
This issue is the first official release.
Contents
Preface................................................................................................................................................ ii
1 Product Description...................................................................................................................... 1
1.1 Overview........................................................................................................................................................................ 1
1.1.1 System Architecture.................................................................................................................................................... 1
1.1.2 Function Description................................................................................................................................................... 2
1.2 Software and Hardware Compatibility........................................................................................................................... 6
1.3 Security Features.......................................................................................................................................................... 10
1.4 Communication Matrix.................................................................................................................................................11
3 iBMA Operations.........................................................................................................................73
3.1 Querying, Starting, Stopping, and Restarting the iBMA Service (Linux OS)............................................................. 73
3.2 Querying, Starting, Stopping, and Restarting the iBMA Service (Windows OS)........................................................76
3.3 Querying, Starting, Stopping, and Restarting the iBMA Service (VMware OS).........................................................78
4 Troubleshooting.......................................................................................................................... 79
4.1 Common Troubleshooting............................................................................................................................................ 79
4.2 Log Collection.............................................................................................................................................................. 89
I Enabling IPv6..............................................................................................................................162
J Enabling PCIe Devices..............................................................................................................166
K Black Box Function Usage Description (Linux OS)........................................................... 170
K.1 Obtaining Help Information (-h or --help).................................................................................................................170
K.2 Querying the Software Version (-v or --version)....................................................................................................... 171
K.3 Reading the Black Box Image (-r or --read).............................................................................................................. 171
K.4 Parsing Black Box Original Image (-p or --parse).....................................................................................................172
L Installing and Uninstalling the DKMS Source Code Package (Linux OS)................... 174
L.1 Installing the DKMS Source Code Package.............................................................................................................. 174
L.2 Uninstalling the DKMS Source Code Package..........................................................................................................175
L.3 Upgrading the DKMS Source Code Package............................................................................................................ 175
P Glossary...................................................................................................................................... 186
Q Acronyms and Abbreviations................................................................................................ 188
1 Product Description
1.1 Overview
1.2 Software and Hardware Compatibility
1.3 Security Features
1.4 Communication Matrix
1.1 Overview
Function Description
Providing system Provides OS, NIC, hard disk, and RAID controller card information
information to the iBMC.
Uploading files Allows eSight and other tools to upload files to the server where the
iBMA is running by using Redfish interfaces of the iBMC. For
details, see Huawei Server iBMC Redfish API Description.
Upgrading drivers Allows eSight and other tools to upgrade drivers using Redfish
interfaces of the iBMC. For details, see Huawei Server iBMC
Redfish API Description.
NOTE
l You must stop services before you upgrade the driver.
l You are not allowed to power off or reset the system during the driver
upgrade process.
Function Description
Monitoring system Periodically monitors system information and health status changes,
status and reports the changes to the iBMC for alarm reporting.
Managing software Allows AtlasDirector and other tools to query, install, and upgrade
software using Redfish interfaces of the iBMC.
bob bob is a forwarding tool that helps a remote host in the in-band
network communicate with the local iBMC through in-band
networking. It provides functions such as service connection (using
SSH, SNMP, IPMI, and HTTPS) and event reporting (using SNMP
traps).
bob supports service management (starting, stopping, and restarting)
but does not support independent deployment and working.
bob provides the bobCmd CLI to start, stop, and restart the bob
services and other related configurations. The forwarding function
can be configured online without restarting services. The
configuration supports persistency. That is, the configuration is not
lost after the system is restarted.
Redfish service The Redfish service can be started by using HTTPS or HTTP.
compatible with NOTE
HTTPS iBMC V3.16 or later is required.
NIC fault alarm On Linux OSs, the internal error detection of Mellanox NICs is
supported, and detected error information is recorded in the log/
common.log file of the iBMA installation directory.
NOTE
The driver of Mellanox NIC 4.2 or later is required.
Function Description
Storage diagnosis Periodically monitors storage diagnosis information about hard disk
I/O performance deterioration, hard disk Sense Code errors, and
read-only file systems. The information is reported to the iBMC for
alarms. RAID controller card hard disk logs can be collected for
hard disk loss analysis.
NOTE
l The detection of hard disk I/O performance deterioration and read-only
file systems supports only Linux OSs.
l The detection of hard disk Sense Code errors supports Linux OSs.
By using the RESTful interfaces of the iBMA, the iBMC can implement the query functions
of server system information. Table 1-2 describes the query functions.
CPU Queries basic CPU information, including the system CPU usage,
number of CPUs, model, and single CPU usage.
NIC Queries the number of NICs, rate, link status, duplex mode, firmware
version information, driver name, NIC driver information, PCIe device
ID, function ID, network port name, network port IP address, subnet
mask, gateway, MAC address, VLAN information, and received/sent
packet statistics as well as the system VLAN, team, and bridge
information.
Hard disk Queries the number of physical hard disks, manufacturer, model,
firmware version, serial number, capacity, rotation speed, interface rate,
physical slot, and silkscreen information.
Queries the capacity, used size, and usage of a logical disk in the system.
RAID Supports mainstream RAID controller cards and scenarios where servers
are configured with multiple RAID controller cards. For supported
RAID controller card models, see 1.2 Software and Hardware
Compatibility.
Component Description
Queries the RAID battery health status, type, name, serial number, rated
capacity and voltage, current capacity and voltage, number of charge
and discharge times, and temperature information.
Queries the logical disk RAID level and status (normal, degraded, or
offline), RAID group configuration status, RAID group physical slot
information, relationship between the OS drive letter and RAID group,
RAID group stripe depth, access policies, read/write policies, logical
disk cache status, and boot disk information.
Queries RAID controller card link bit errors and expander link bit errors.
NVMe Queries the NVMe SSD manufacturer, model, firmware version, and
driver version information.
Optical module Displays basic information about optical modules. The information
includes the manufacturer name, manufacturing component number,
serial number, production date, optical module type (10GBASE_SR),
wavelength, multi-mode/single-mode (Linux), temperature, voltage, and
power consumption threshold.
The optical module diagnosis functions include optical module LOS
detection, temperature detection, voltage detection, and power
consumption threshold detection.
The optical module matching detection (type matching and rate
matching) function is supported. The iBMA reports the optical module
type and rate.
OAM link Detects blade server OAM (802.3ah) and OAM link faults, including
detection link status information (bit error threshold crossing, error frame
threshold crossing, or error frame second threshold crossing).
NOTE
Only Linux OSs are supported and E9000 switch modules are used.
NOTE
The iBMA also provides the black box function, which records the system status and debugging
information before the server is down. For details, see K Black Box Function Usage Description
(Linux OS). The iBMA provides the event reporting function. The iBMA periodically detects status
change events of physical disks, logical disks, and RAID controller cards. If status change events occur,
the iBMA reports the event information through Redfish event subscription interfaces to the upper-layer
management software.
SLES 15 4.12.14-23-default
NOTE
l The VMware OSs listed in the table are 32- or 64-bit OSs, and the other OSs are 64-bit OSs.
l The sub-versions of the Red Hat/SUSE/CentOS/Ubuntu/FusionSphere OS version listed in the table
are supported.
l The SUSE system driver supports the KMP function and kernel updates in the same version. For
details about the supported kernel versions, visit https://wiki.microfocus.com/index.php/SUSE/
SLES/Kernel_versions.
l The iBMA driver of the Linux OS supports the dynamic kernel module support (DKMS) function. If
the system needs to dynamically update the kernel, install the DKMS driver by seeing L Installing
and Uninstalling the DKMS Source Code Package (Linux OS).
l For the iBMA of the Linux OS, if the OS version is listed in Table 1-3 but the kernel version is not
listed in the table, manually compile the iBMA driver for adaptation by seeing M Compiling the
iBMA Driver (Linux OS).
l When the kernel version of a Red Hat/CentOS/FusionSphere system is upgraded, the iBMA driver
may write data into the initramfs file, which does not affect the proper running of the system.
RH2288 V3
RH2288H V3
5288 V3
1288H V5
2288 V5
2288H V5
2488 V5
2488H V5
5288 V5
5885H V5
CH140L V3
CH121 V3
CH121H V3
CH121L V3
CH220 V3
CH222 V3
CH225 V3
Category Server
CH226 V3
CH242 V3 DDR4
CH121 V5
CH121L V5
CH242 V5
CH225 V5
CH221 V5
XH321 V3
XH620 V3
XH622 V3
XH628 V3
XH321 V5
XH321L V5
XH628 V5
RH5885H V3 (iBMC)
RH8100 V3
8100 V5
G530 V5
G560 V5
G560
Security Policies
l The iBMA runs on the OS and communicates with the iBMC through dedicated PCIe
channels in the server. The dedicated PCIe channels ensure data channel security.
l The iBMA supports verification of the digital signature of the upgrade file during the
driver upgrade process.
l The iBMA implements proper configurations for the operation permission on installation
files to avoid misoperations.
l The iBMA queries only hardware information and does not change system settings. It
does not involve the collection and processing of personal data.
Security Description
l When the iBMA is in use, virtual devices will be generated. The virtual devices will be
used by the iBMA and have no impact on the OS.
– On a Linux OS or a VMware OS, four character devices (only one of them is used
by the iBMA service) and one virtual NIC will be generated.
– On a Windows OS, one character device and one virtual NIC will be generated.
l After the iBMA is installed, the following processes are generated:
– Manager: protects processes.
– Monitor: detects changes in system resources.
– iBMA_RedfishMain: provides Redfish services for the management software
through the virtual NIC.
NOTE
Use system service commands to stop iBMA processes. The iBMA may become abnormal if processes
are stopped manually.
On the download page, click to obtain the digital certificate, and click to
download the software. For details about how to obtain the verification tool and method,
see Software Digital Signature (OpenPGP) Validation Tool.
3. Enable PCIe devices. For details, see J Enabling PCIe Devices.
4. Check whether the software installation environment meets the requirements listed in G
Environmental Requirements.
5. Enable the port that the iBMA uses to listen HTTP requests (TCP/IPv6/IPv4) on the
firewall. The default port number is 8090. Ensure the port number 8090 is not used by
another program. For details, see F Performing Operations on the System Firewall.
NOTE
l If IPv6 addresses are to be used, you need to enable the IPv6 function on virtual NICs. For
details, see I Enabling IPv6.
l If IPv4 addresses are to be used, perform the configuration after the iBMA installation is
complete. For details, see H.9 Configuring IP Addresses.
6. Check software and hardware compatibility. For details, see 1.2 Software and
Hardware Compatibility.
7. Upload the iBMA software package to the server. (You can upload the software package
by using Xshell or deploying an FTP server.)
NOTE
l It is recommended that at least 2 GB space be reserved on the disk for iBMA installation.
l To delete entered characters when you enter information, press Ctrl+Backspace.
You can install the iBMA using either of the following methods:
Redfish service port 8090 An unused port specified by the user from
number port number 1024 to 65535.
NOTE
This port must also be enabled on the firewall.
For details, see 4.1 Common Troubleshooting.
Socket service port 8091 An unused port specified by the user from
number port number 1024 to 65535.
Protocol used by the HTTP Set by the user. The value can be HTTP or
Redfish service HTTPS.
Scenarios
Install the iBMA on a Linux OS, for example CentOS 7.2, in silent mode.
iBMA2.0-Linux-pkg-V2.0.3.010.zip is used as an example.
Prerequisites
Conditions
You have uploaded the iBMA installation package, for example iBMA2.0-Linux-pkg-
V2.0.3.010.zip, to a directory on the server.
You have enabled the PCIe device. For details, see J Enabling PCIe Devices.
Data
No data preparation is required for this operation.
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
[root@localhost src]# cd package/
[root@localhost package]# unzip iBMA2.0-Linux-pkg-V2.0.3.010.zip
Archive: iBMA2.0-Linux-pkg-V2.0.3.010.zip
inflating: iBMA 2.0 FOSS License Information.doc
extracting: iBMA2.0-Linux-V2.0.3.010.tar.gz
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.crl
inflating: software.xml
[root@localhost package]# ls
iBMA2.0-Linux-V2.0.3.010.tar.gz iBMA2.0-Linux-V2.0.3.010.tar.gz.cms iBMA2.0-
Linux-V2.0.3.010.tar.gz.crl iBMA2.0-Linux-pkg-V2.0.3.010.zip software.xml iBMA
2.0 FOSS License Information.doc
[root@localhost package]#
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMS verification file provided by the iBMA is stored in the ./lib/Linux/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Linux-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
NOTE
You can edit the configuration file before the installation. For details, see H Modifying Configuration
Files.
[root@localhost iBMA2.0]# ./install.sh -s
-----------------------------------------------------------------
Starting to install iBMA in silent mode.
System is CentOS
Kernel version is 3.10.0-327.el7.x86_64
Driver package version is 0.2.9
Driver package is already installed.
Installing iBMA ...
-----------------------------------------------------------------
iBMA installed successfully.
-----------------------------------------------------------------
Starting iBMA service.
Start iBMA service successfully.
-----------------------------------------------------------------
Manually enable port 8090 via the veth interface
on the firewall (TCP/IPv6).
[root@localhost iBMA2.0]#
NOTE
Step 7 Go to the /opt/huawei/ibma directory to view the files generated after the installation.
[root@localhost iBMA2.0]# cd /opt/huawei/ibma/
[root@localhost ibma]#
[root@localhost ibma]# ls
bin bob.sh config iBMA.sh lib lib64 log script tools uninstall.sh
[root@localhost ibma]#
NOTE
----End
Scenarios
Install the iBMA on a Linux OS, for example CentOS 7.2, in custom mode.
iBMA2.0-Linux-pkg-V2.0.3.010.zip is used as an example.
Prerequisites
Conditions
You have uploaded the iBMA installation package, for example iBMA2.0-Linux-pkg-
V2.0.3.010.zip, to a directory on the server.
Data
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
[root@localhost src]# cd package/
[root@localhost package]# ls
iBMA2.0-Linux-pkg-V2.0.3.010.zip
[root@localhost package]# unzip iBMA2.0-Linux-pkg-V2.0.3.010.zip
Archive:iBMA2.0-Linux-pkg-V2.0.3.010.zip
inflating: iBMA 2.0 FOSS License Information.doc
extracting: iBMA2.0-Linux-V2.0.3.010.tar.gz
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.crl
inflating: software.xml
[root@localhost package]#
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMS verification file provided by the iBMA is stored in the ./lib/Linux/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Linux-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
arguments:
-s Silent installation mode, recommended
options:--enable-iBMC_event=true|false
Enable/Disable the feature of logging iBMC events
--enable-iBMA_https=true|false
Redfish Server starts with HTTPS/HTTP protocol
true indicates that HTTPS is selected
false indicates that HTTP is selected
-c Custom installation mode
-f Force installation mode, used with -s or -c,
overwrite the configuration files
-u Upgrade iBMA, reserve the configuration files
-h Show this help
-----------------------------------------------------------------
[root@localhost iBMA2.0]#
NOTE
l For details about parameter settings in the installation process, see Table 2-1.
l During custom installation, if the PCIe device is not enabled, the system automatically attempts to
send an IPMI command to enable the PCIe device. If the command fails to be sent, you need to
manually enable the black box function on the iBMC WebUI, restart the OS, and install the iBMA.
For details, see J Enabling PCIe Devices.
[root@localhost iBMA2.0]# ./install.sh -c
-----------------------------------------------------------------
Starting to install iBMA in custom mode.
Press Ctrl + C to abort the installation.
System is RedHat
Kernel version is 3.10.0-693.el7.x86_64
Driver package version is 0.2.9
Driver package is already installed.
-----------------------------------------------------------------
STEP 1: Set the Redfish server user
-----------------------------------------------------------------
The default user is <root>
1) Use the default user (recommended)
2) Enter another existing user
Enter your choice:1
-----------------------------------------------------------------
STEP 2: Set the Redfish server port
-----------------------------------------------------------------
The default port number is <8090>
1) Use the default port number (recommended)
2) Set a port number
Enter your choice:1
-----------------------------------------------------------------
STEP 3: Set the socket server port
-----------------------------------------------------------------
The default port number is <8091>
1) Use the default port number (recommended)
2) Set a port number
Enter your choice:1
-----------------------------------------------------------------
STEP 4: Set the Redfish server protocol
-----------------------------------------------------------------
The default protocol is <HTTP>
1) Use the default protocol
2) Use HTTPS protocol
Enter your choice:1
-----------------------------------------------------------------
STEP 5: Start iBMA service immediately
-----------------------------------------------------------------
iBMA will start after installation
1) Start after installation (recommended)
2) Start iBMA manually
Enter your choice:1
-----------------------------------------------------------------
STEP 6: Confirm settings
-----------------------------------------------------------------
Settings summary:
1. Redfish server user: root
2. Redfish server port: 8090
3. Socket server port: 8091
4. Redfish server protocol type: HTTP
5. Start iBMA immediately: Yes
NOTE
Step 7 Go to the /opt/huawei/ibma directory to view the files generated after the installation.
[root@localhost iBMA2.0]# cd /opt/huawei/ibma/
[root@localhost ibma]#
[root@localhost ibma]# ls
bin bob.sh config iBMA.sh lib lib64 log script tools uninstall.sh
[root@localhost ibma]#
NOTE
----End
Scenarios
Uninstall the iBMA from a Linux OS, for example, CentOS 7.2.
Prerequisites
Conditions
The iBMA has been installed.
Data
No data preparation is required for this operation.
Procedure
Step 1 Log in to the server OS as user root.
NOTE
NOTE
NOTE
l ./uninstall.sh is used to uninstall the iBMA in a customized manner (this mode is recommended).
Go to Step 4.
l ./uninstall.sh -s is used to uninstall the iBMA in silent mode. Go to Step 5.
l ./uninstall.sh -a is used to uninstall the iBMA and the driver. Go to Step 6.
l The iBMA cannot be uninstalled when an out-of-band upgrade task (except the iBMA upgrade) is
being executed by the iBMA.
----End
NOTE
l If you want to roll back the iBMA from 2.0 to C50 or earlier, you need to uninstall the
software of 2.0 and then install the software of another version.
l If iBMA 2.0 of an earlier version has been installed, compatibility check will not be
performed during the upgrade.
l Uninstall the software of the source version and install the software of the target version
(this mode is recommended). For details, see 2.1.2 Uninstalling the iBMA and 2.1.1
Installing the iBMA.
l Install the software of the target version to overwrite the software of the source version.
For details, see 2.1.1 Installing the iBMA.
In this mode, the iBMA uses the configuration information of the source version.
l Upgrade the software to the target version. The newly added parameters in the
Monitor.ini and iBMA.ini configuration files of the software of the target version will
use the configuration information of the software of the target version. The parameters
that already exist in the software of the source version will still use the configuration
information of the software of the source version.
During the iBMA upgrade process, the driver upgrade scenarios are as follows:
l If the target version is later than the source version, the source version will be
automatically uninstalled, and then the target version will be installed.
l If the target version is earlier than the source version, the driver will not be upgraded.
l If the target version is the same as the source version, the driver will not be upgraded.
Scenarios
Upgrade the iBMA on a Linux OS, for example, CentOS 7.2.
Prerequisites
Conditions
You have uploaded the iBMA installation package, for example iBMA2.0-Linux-pkg-
V2.0.3.010.zip, to a directory on the server.
Data
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
[root@localhost src]# cd package/
[root@localhost package]# ls
iBMA2.0-Linux-pkg-V2.0.3.010.zip
[root@localhost package]# unzip iBMA2.0-Linux-pkg-V2.0.3.010.zip
Archive: iBMA2.0-Linux-pkg-V2.0.3.010.zip
inflating: iBMA 2.0 FOSS License Information.doc
extracting: iBMA2.0-Linux-V2.0.3.010.tar.gz
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-Linux-V2.0.3.010.tar.gz.crl
inflating: software.xml
[root@localhost package]# ls
iBMA2.0-Linux-V2.0.3.010.tar.gz iBMA2.0-Linux-V2.0.3.010.tar.gz.cms iBMA2.0-
Linux-V2.0.3.010.tar.gz.crl iBMA2.0-Linux-pkg-V2.0.3.010.zip software.xml
iBMA 2.0 FOSS License Information.doc
[root@localhost package]#
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMS verification file provided by the iBMA is stored in the ./lib/Linux/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Linux-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
NOTE
For details about parameter settings in the installation process, see Table 2-1.
During upgrade installation, if the PCIe device is not enabled, the system automatically attempts to send
an IPMI command to enable the PCIe device. If the command fails to be sent, you need to manually
enable the black box function on the iBMC WebUI, restart the OS, and install the iBMA. For details, see
J Enabling PCIe Devices.
[root@localhost iBMA2.0]# ./install.sh -u
-----------------------------------------------------------------
Starting to upgrade iBMA.
NOTE
Step 7 Go to the /opt/huawei/ibma directory to view the files generated after the installation.
[root@localhost iBMA2.0]# cd /opt/huawei/ibma/
[root@localhost ibma]#
[root@localhost ibma]# ls
bin bob.sh config iBMA.sh lib lib64 log script tools uninstall.sh
[root@localhost ibma]#
[root@localhost ibma]#
NOTE
----End
On the download page, click to obtain the digital certificate, and click to
download the software. For details about how to obtain the verification tool and method,
see Software Digital Signature (OpenPGP) Validation Tool.
l If IPv6 addresses are to be used, you need to enable the IPv6 function on virtual NICs. For
details, see I Enabling IPv6.
l If IPv4 addresses are to be used, perform the configuration after the iBMA installation is
complete. For details, see H.9 Configuring IP Addresses.
6. Check software and hardware compatibility. For details, see 1.2 Software and
Hardware Compatibility.
7. Upload the driver package and the iBMA software package to the server.
Redfish service 8090 An unused port specified by the user from port
port number number 1024 to 65535.
NOTE
This port must also be enabled on the firewall. For details,
see 4.1 Common Troubleshooting.
Socket service 8091 An unused port specified by the user from port
port number number 1024 to 65535.
Protocol used HTTP Set by the user. The value can be HTTP or HTTPS.
by the Redfish
service
Scenarios
Install the iBMA using the GUI on Windows. Windows Server 2008 R2 is used as an
example.
Prerequisites
Conditions
Data
Procedure
Step 1 Log in to the server OS as the system administrator.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, space, and dots) in which the installation package is stored, and
decompress the package, as shown in Figure 2-1.
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMSVerify file provided by the iBMA is stored in the ./lib/Windows/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Windows-V2.0.3.010.zip file generated after the decompression is the installation
package file. To distinguish the files before and after the decompression, save the files generated
after the decompression to another directory.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
If iBMA 1.0 has been installed, a dialog box asking you to uninstall iBMA 1.0 will be displayed after
you double-click iBMA2.0setup.exe.
The Welcome to the iBMA 2.0 Setup Wizard window is displayed, as shown in Figure 2-3
Step 6 Retain the default installation path C:\Huawei\iBMA2.0 or click Browse to reselect an
installation path, and click Next.
NOTE
l If the remaining space on the selected disk is insufficient for iBMA installation (it is recommended
that at least 4 GB space be reserved on the disk for iBMA installation), click Next to go to the Out
of Disk Space window and reselect a disk for installation.
l The installation path contains a maximum of 200 characters. The folder name supports digits, letters,
underscores (_), hyphens (-), and dots (.).
Step 7 Change the port numbers and protocol type of the Redfish service as prompted, and click
Next.
NOTE
On Windows, you can change the port numbers in this window. Ensure that the two ports are not
occupied by other programs. If the value of Redfish server port number is changed, you need to enable
the corresponding port of the firewall. If HTTPS is selected, you need to use iBMC V3.16 or later.
After the installation is complete, the iBMA service is automatically started, as shown in
Figure 2-8.
Step 10 Check whether iBMA Service exists on the Services page. For details, see b to c.
----End
Scenarios
Install the iBMA using the CLI on Windows. Windows Server 2008 R2 is used as an
example.
Prerequisites
Conditions
Data
Procedure
Step 1 Log in to the server OS as the system administrator.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package, as shown in Figure 2-10.
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMSVerify file provided by the iBMA is stored in the ./lib/Windows/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Windows-V2.0.3.010.zip file generated after the decompression is the installation
package file. To distinguish the files before and after the decompression, save the files generated
after the decompression to another directory.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
Step 5 Run the following command to access the iBMA 2.0 directory:
cd
Step 6 Run the following command to view help information:
iBMA2.0setup.exe /?
The help information is displayed, as shown in Figure 2-12.
The installation commands are classified into the following types. For details about the
installation commands, see Table 2-5. The parameters in the installation commands are case
insensitive.
NOTE
--enable-iBMC_event is used to determine whether to record iBMC events and cannot be used together
with the /UPGRADE parameter, and the default value of this parameter is false. --enable-iBMA_https
is used to determine whether to start the Redfish service of the iBMA by using HTTPS and cannot be
used together with the /UPGRADE parameter. You are advised to use this parameter together with the /
VERYSILENT parameter, and the default value of it is false.
Step 7 Click OK, and run the installation commands in the CLI (the silent installation mode is used
as an example).
C:\iBMA2.0>iBMA2.0Setup.exe /VERYSILENT
C:\iBMA2.0>
Step 8 Run the following command to check whether the iBMA service is started:
sc query iBMA
C:\Huawei\iBMA2.0\bin>sc query iBMA
SERVICE_NAME: iBMA
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE, ACCEPTS_PRESHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
----End
Scenarios
Uninstall the iBMA using the GUI on Windows. Windows Server 2008 R2 is used as an
example.
Prerequisites
Conditions
Data
Procedure
l Uninstall the iBMA by using the installation program.
a. Log in to the server OS as the system administrator.
NOTE
c. Double-click unins000.exe.
A confirmation dialog box is displayed, as shown in Figure 2-14.
d. Click Yes.
The window shown in Figure 2-15 is displayed, prompting you to determine
whether to uninstall the driver.
If the iBMA service is running, a dialog box is displayed, asking you whether to stop the
iBMA service. Click Yes to uninstall the iBMA.
The iBMA uninstallation starts, as shown in Figure 2-16.
After the uninstallation is complete, the dialog box shown in Figure 2-17.
f. Click OK.
The uninstallation is complete.
l Uninstall the iBMA by using Control Panel.
a. Log in to the server OS as the system administrator.
NOTE
e. Click Yes.
The window shown in Figure 2-21 is displayed, prompting you to determine
whether to uninstall the driver.
If the iBMA service is running, a dialog box is displayed, asking you whether to stop the
iBMA service. Click Yes to uninstall the iBMA.
The iBMA uninstallation starts, as shown in Figure 2-22.
After the uninstallation is complete, the dialog box shown in Figure 2-23.
g. Click OK.
The uninstallation is complete.
Scenarios
Uninstall the iBMA using the CLI on Windows. Windows Server 2008 R2 is used as an
example.
Prerequisites
Conditions
The iBMA has been installed.
Data
No data preparation is required for this operation.
Procedure
Step 1 Log in to the server OS as the system administrator.
NOTE
Step 3 Access the iBMA installation directory. The default installation directory is C:\Huawei
\iBMA2.0.
C:\Users\Administrator>cd /
C:\>cd huawei/iBMA2.0
C:\Huawei\iBMA2.0>dir
Volume in drive C is System
Volume Serial Number is DE35-FFF8
Directory of C:\Huawei\iBMA2.0
C:\Huawei\iBMA2.0>
NOTE
l unins000.exe is used to uninstall the iBMA in customized mode (this mode is recommended).
l unins000.exe/REMOVEDRIVER (the parameter is case insensitive) is used to uninstall the iBMA
and the driver.
l unins000.exe /VERYSILENT (the parameter is case insensitive) is used to uninstall the iBMA in
silent mode.
l The iBMA cannot be uninstalled when an out-of-band upgrade task (except the iBMA upgrade) is
being executed.
Step 5 Click OK and run uninstallation commands in the CLI. The silent mode is used as an
example.
C:\Huawei\iBMA2.0>sc stop iBMA
C:\Huawei\iBMA2.0>unins000.exe /VERYSILENT
C:\Huawei\iBMA2.0>
----End
l If you want to roll back the iBMA from 2.0 to C50 or earlier, you need to uninstall the
software of 2.0 and then install the software of another version.
l If iBMA 2.0 of an earlier version has been installed, compatibility check will not be
performed during the upgrade.
l Uninstall the software of the source version and install the software of the target version
(this mode is recommended). For details, see 2.2.2 Uninstalling the iBMA and 2.2.1
Installing the iBMA.
l Upgrade the software to the new version by using the GUI or running the
iBMA2.0Setup.exe /UPGRADE command.
The newly added parameters in the Monitor.ini and iBMA.ini configuration files of the
software of the target version will use the configuration information of the software of
the target version. The parameters that already exist in the software of the source version
will still use the configuration information of the software of the source version.
During the iBMA upgrade process, the driver upgrade scenarios are as follows:
l If the target version is later than the source version, the source version will be
automatically uninstalled, and then the target version will be installed.
l If the target version is earlier than the source version, the driver will not be upgraded.
l If the target version is the same as the source version, the driver will not be upgraded.
Scenarios
Upgrade the iBMA using the GUI on Windows. Windows Server 2008 R2 is used as an
example.
Prerequisites
Conditions
Data
Procedure
Step 1 Log in to the server OS as the system administrator.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package, as shown in Figure 2-25.
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMSVerify file provided by the iBMA is stored in the ./lib/Windows/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-Windows-V2.0.3.010.zip file generated after the decompression is the installation
package file. To distinguish the files before and after the decompression, save the files generated
after the decompression to another directory.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
Step 6 Click .
The Ready to Install window is displayed, as shown in Figure 2-29.
After the installation is complete, the iBMA service is automatically started, as shown in
Figure 2-31.
Step 9 Check whether iBMA Service exists on the Services page. For details, see b to c.
----End
NOTE
The VMware installation package is divided into the following two packages to support the
VMware ESXi OSs of different versions:
l iBMA-ESXi5.5-ESXi6.0-pkg-***.zip: supports VMware ESXi 5.5.x and VMware ESXi
6.0.x.
l iBMA-ESXi-pkg-***.zip: supports VMware ESXi 6.5.x and secure boot at the community
and partner security levels.
2. Verify software package integrity.
On the download page, click to obtain the digital certificate, and click to
download the software. For details about how to obtain the verification tool and method,
see Software Digital Signature (OpenPGP) Validation Tool.
3. Enable PCIe devices. For details, see J Enabling PCIe Devices.
4. Check whether the software installation environment meets the requirements listed in G
Environmental Requirements.
5. Enable the port that the iBMA uses to listen HTTP requests (TCP/IPv6/IPv4) on the
firewall. The default port number is 8090. Ensure the port number 8090 is not used by
another program. For details, see F Performing Operations on the System Firewall.
NOTE
l If IPv6 addresses are to be used, you need to enable the IPv6 function on virtual NICs. For
details, see I Enabling IPv6.
l If IPv4 addresses are to be used, perform the configuration after the iBMA installation is
complete. For details, see H.9 Configuring IP Addresses.
6. Check software and hardware compatibility. For details, see 1.2 Software and
Hardware Compatibility.
7. Run the esxcli software acceptance set --level=PartnerSupported command to set the
program acceptance level of the OS to PartnerSupported.
esxcli software acceptance set --level=PartnerSupported
Host acceptance level changed to 'PartnerSupported'.
It is recommended that the remaining space of the partition where the /scratch/ directory for OS
installation is located be at least 2 GB. (The /scratch/ partition is used to save iBMA log files.)
The forcible installation indicates that the -f parameter is added to the custom or silent
installation process. During forcible installation, the compatibility check will be skipped.
The iBMA software installed in this mode may be unstable (if the PCIe device of which
the device ID is 0x1710 and vendor ID is 0x19e5 in the running environment is occupied
by the driver, the iBMA cannot be successfully installed in forcible installation mode).
Therefore, this mode is not recommended.
Redfish service port 8090 An unused port specified by the user from
number port number 1024 to 65535.
NOTE
This port must also be enabled on the firewall.
For details, see 4.1 Common
Troubleshooting.
Socket service port 8091 An unused port specified by the user from
number port number 1024 to 63486.
Protocol used by the HTTP Set by the user. The value can be HTTP
Redfish service or HTTPS.
NOTE
When the iBMA is installed for the first time, the configured parameters do not take effect. After
the installation is complete, you need to manually modify the iBMA.ini configuration file in the
installation directory. For details, see H.1 Description of the iBMA.ini Configuration File.
Scenarios
Install the iBMA on a VMware OS in silent mode, for example VMware ESXi 5.5.0.
Prerequisites
Conditions
You have uploaded the iBMA installation package, for example iBMA2.0-VMware-pkg-
V2.0.3.010.zip, to the server OS.
Data
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
/vmfs/volumes/package # ls
iBMA2.0-VMware-pkg-V2.0.3.010.zip
/vmfs/volumes/package # unzip iBMA2.0-VMware-pkg-V2.0.3.010.zip
Archive: iBMA2.0-VMware-pkg-V2.0.3.010.zip
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.crl
inflating: software.xml
inflating: iBMA 2.0 FOSS License Information.doc
/vmfs/volumes/package # ls
iBMA2.0-VMware-V2.0.3.010.tar.gz iBMA2.0-VMware-V2.0.3.010.tar.gz.cms iBMA2.0-
VMware-V2.0.3.010.tar.gz.crl iBMA2.0-VMware-pkg-V2.0.3.010.zip software.xml
iBMA 2.0 FOSS License Information.doc
/vmfs/volumes/package #
/vmfs/volumes/package # /etc/cim/huawei/iBMA2.0/lib/VMware/upgrade/CMSVerify
iBMA2.0-VMware-V2.0.3.010.tar.gz.cms iBMA2.0-VMware-V2.0.3.010.tar.gz iBMA2.0-
VMware-V2.0.3.010.tar.gz.crl
verify succeed.
/vmfs/volumes/package #
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMSVerify file provided by the iBMA is stored in the ./lib/VMware/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-VMware-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
NOTE
NOTE
Step 7 If "You need to reboot the OS to run iBMA service" is contained in the displayed information,
restart the OS. Otherwise, skip this step.
/vmfs/volumes/package/iBMA2.0 # reboot
Step 8 Go to the /etc/cim/huawei/iBMA2.0 directory to view the files generated after the
installation.
/vmfs/volumes/package/iBMA2.0 # cd /etc/cim/huawei/iBMA2.0
/etc/cim/huawei/iBMA2.0 #
/etc/cim/huawei/iBMA2.0 # ls
bin bob.sh config drivers iBMA.sh lib
lib64 script tools uninstall.sh
NOTE
----End
Scenarios
Install the iBMA on a VMware OS in custom mode, for example VMware ESXi 5.5.0.
Prerequisites
Conditions
You have uploaded the iBMA installation package, for example iBMA2.0-VMware-pkg-
V2.0.3.010.zip, to the server OS.
Data
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
[root@localhost src]# cd package/
[root@localhost package]# ls
iBMA2.0-VMware-pkg-V2.0.3.010.zip
/vmfs/volumes/package # unzip iBMA2.0-VMware-pkg-V2.0.3.010.zip
Archive: iBMA2.0-VMware-pkg-V2.0.3.010.zip
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.crl
inflating: software.xml
inflating: iBMA 2.0 FOSS License Information.doc
/vmfs/volumes/package # ls
iBMA2.0-VMware-V2.0.3.010.tar.gz iBMA2.0-VMware-V2.0.3.010.tar.gz.cms iBMA2.0-
VMware-V2.0.3.010.tar.gz.crl iBMA2.0-VMware-pkg-V2.0.3.010.zip software.xml
iBMA 2.0 FOSS License Information.doc
/vmfs/volumes/package #
/vmfs/volumes/package # /etc/cim/huawei/iBMA2.0/lib/VMware/upgrade/CMSVerify
iBMA2.0-VMware-V2.0.3.010.tar.gz.cms iBMA2.0-VMware-V2.0.3.010.tar.gz iBMA2.0-
VMware-V2.0.3.010.tar.gz.crl
verify succeed.
[root@localhost package]#
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMS verification file provided by the iBMA is stored in the ./lib/VMware/upgrade directory.
You can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-VMware-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
NOTE
NOTE
l For details about parameter settings in the installation process, see Table 2-7.
l During custom installation, if the PCIe device is not enabled, you need to manually enable the black
box function on the iBMC WebUI, restart the OS, and install the iBMA. For details, see J Enabling
PCIe Devices.
[root@localhost iBMA2.0]# ./install.sh -c
-----------------------------------------------------------------
Starting to install iBMA in custom mode.
Press Ctrl + C to abort the installation.
-----------------------------------------------------------------
STEP 1: Set the Redfish server port
-----------------------------------------------------------------
The default port number is <8090>
Enter your choice:
1) Use the default port number (recommended)
2) Set a port number
1
-----------------------------------------------------------------
STEP 2: Set the socket server port
-----------------------------------------------------------------
The default port number is <8091>
Enter your choice:
1) Use the default port number (recommended)
2) Set a port number
1
-----------------------------------------------------------------
STEP 3: Set the Redfish server protocol
-----------------------------------------------------------------
The default protocol is <HTTP>
Enter your choice:
1) Use the default protocol
2) Use HTTPS protocol
1
-----------------------------------------------------------------
STEP 4: Confirm settings
-----------------------------------------------------------------
Settings summary:
1. Redfish server port: 8090
2. Socket server port: 8090
3. Redfish server protocol type: HTTP
1
Installing driver package ...
Install driver package successfully.
Installing iBMA ...
The iBMA service registered successfully.
-----------------------------------------------------------------
iBMA installed successfully.
You need to reboot the OS to run iBMA service.
-----------------------------------------------------------------
Manually enable port 8090 on the firewall (TCP/IPv6).
[root@localhost iBMA2.0]#
NOTE
Step 7 If "You need to reboot the OS to run iBMA service" is contained in the displayed information,
restart the OS. Otherwise, skip this step.
/vmfs/volumes/package/iBMA2.0 # reboot
Step 8 Go to the /etc/cim/huawei/iBMA2.0 directory to view the files generated after the
installation.
/vmfs/volumes/package/iBMA2.0 # cd /etc/cim/huawei/iBMA2.0
/etc/cim/huawei/iBMA2.0 #
/etc/cim/huawei/iBMA2.0 # ls bin bob.sh config
drivers iBMA.sh lib lib64 script
tools uninstall.sh
NOTE
----End
Scenarios
Uninstall the iBMA from a VMware OS, for example, VMware 5.5.0.
Prerequisites
Conditions
Data
Procedure
l Use the uninstall.sh script to uninstall the iBMA. (This mode is recommended.)
a. Log in to the server OS as user root.
NOTE
NOTE
NOTE
NOTE
l The iBMA cannot be uninstalled when an out-of-band upgrade task (except the
iBMA upgrade) is being executed by the iBMA.
l You must uninstall the iBMA before you uninstall the driver.
After the driver is uninstalled, restart the OS for the uninstallation to take effect.
If iBMA 2.0 of an earlier version has been installed, compatibility check will not be
performed during the upgrade.
Scenarios
Install the iBMA of the target version directly from a VMware OS, for example, VMware
5.5.0.
Prerequisites
Conditions
The iBMA has been installed.
Data
No data preparation is required for this operation.
Procedure
Step 1 Log in to the server OS as user root.
NOTE
Step 2 Open the directory (the names of all folders in the directory support digits, letters,
underscores, hyphens, and dots) in which the installation package is stored, and decompress
the package.
/vmfs/volumes/package # ls
iBMA2.0-VMware-pkg-V2.0.3.010.zip
/vmfs/volumes/package # unzip iBMA2.0-VMware-pkg-V2.0.3.010.zip
Archive:iBMA2.0-VMware-pkg-V2.0.3.010.zip
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.cms
inflating: iBMA2.0-VMware-V2.0.3.010.tar.gz.crl
inflating: software.xml
inflating: iBMA 2.0 FOSS License Information.doc
/vmfs/volumes/package #
NOTE
l The CMS and CRL files generated after the ZIP file is decompressed are used for CMS verification
on the file package.
l The CMSVerify file provided by the iBMA is stored in the ./lib/VMware/upgrade directory. You
can use this tool to verify the downloaded installation package.
l The software.xml file describes version information of the installation package.
l The iBMA2.0-VMware-V2.0.3.010.tar.gz file generated after the decompression is the installation
package file.
l iBMA 2.0 FOSS License Information.doc is a statement of use for open-source software.
NOTE
NOTE
The iBMA driver upgrade scenarios are as follows (you need to perform operations as
prompted):
l If the target version is later than the source version, uninstall the driver of the source
version, and install the driver of the target version.
l If the target version is earlier than the source version, determine whether to perform the
upgrade during the upgrade process.
l If the target version is the same as the source version, you do not need to upgrade the
driver.
NOTE
Step 7 During the upgrade process, restart the OS if a driver needs to be installed. Perform operations
as prompted. (You do not need to restart the OS is no driver needs to be installed.)
Step 8 Go to the /etc/cim/huawei/iBMA2.0 directory to view the files after the upgrade.
/vmfs/volumes/package/iBMA2.0 # cd /etc/cim/huawei/iBMA2.0
/etc/cim/huawei/iBMA2.0 #
/etc/cim/huawei/iBMA2.0 # ls
bin bob.sh config drivers iBMA.sh
lib lib64 script tools uninstall.sh
----End
3 iBMA Operations
l The iBMA service restarts automatically if it occupies more than 500 MB memory for 10
minutes consecutively.
l The iBMA service cannot be stopped if an out-of-band driver or firmware upgrade is
being performed.
l After the iBMA service is started or restarted, the iBMA information can be displayed on
the iBMC WebUI only after the resource initialization is complete.
NOTE
The duration for iBMA resource initialization is related to the hardware configuration and OS.
Generally, the duration ranges from 30 seconds to 5 minutes. When a high-performance server is
in full configuration and the OS is Windows, the duration for iBMA resource initialization is about
20 minutes.
3.1 Querying, Starting, Stopping, and Restarting the iBMA Service (Linux OS)
3.2 Querying, Starting, Stopping, and Restarting the iBMA Service (Windows OS)
3.3 Querying, Starting, Stopping, and Restarting the iBMA Service (VMware OS)
NOTE
After the iBMA is installed, the service system is automatically registered. The iBMA service is
automatically started upon each startup. Users do not need to start the service manually. (On Red Hat 7.0
or later, CentOS 7.0 or later, SUSE 12.0 or later, and Ubuntu 16.04.0 or later, the iBMA supports only
the systemctl startup configuration item. Some OSs support both service and systemctl commands. The
system must use service or systemctl in a unified manner to manage the iBMA service, which prevents
the service status from being affected by different commands.)
l Query the iBMA service status.
– Run the service command.
[root@Redhat6 iBMA2.0]# service iBMA status
iBMA service is running.
– Run the systemctl command. (You need to run the systemctl status iBMA
command to query the command execution results after you run the systemctl start
iBMA command.)
[root@Redhat6 iBMA2.0]# systemctl start iBMA
[root@Redhat6 iBMA2.0]# systemctl status iBMA
● iBMA.service - LSB: Activates/Deactivates restful api agent service
Loaded: loaded (/etc/rc.d/init.d/iBMA)
Active: active (running) since Wed 2017-05-17 00:33:09 CST; 10s ago
Docs: man:systemd-sysv-generator(8)
Process: 13991 ExecStop=/etc/rc.d/init.d/iBMA stop (code=exited,
status=0/SUCCESS)
Process: 14162 ExecStart=/etc/rc.d/init.d/iBMA start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/iBMA.service
├─14265 python /opt/huawei/ibma/bin/Manager.py
├─14271 python bin/Monitor.py
├─14294 python bin/RedfishServer/iBMA_RedfishMain.py
├─15063 lspci -s 05 00 0
– Run the systemctl command. (You need to run the systemctl status iBMA
command to query the command execution results after you run the systemctl stop
iBMA command.)
[root@Redhat6 iBMA2.0]# systemctl stop iBMA
[root@Redhat6 iBMA2.0]# systemctl status iBMA
● iBMA.service - LSB: Activates/Deactivates restful api agent service
Loaded: loaded (/etc/rc.d/init.d/iBMA)
Active: inactive (dead) since Wed 2017-05-17 00:31:52 CST; 22s ago
Docs: man:systemd-sysv-generator(8)
Process: 13991 ExecStop=/etc/rc.d/init.d/iBMA stop (code=exited,
status=0/SUCCESS)
Process: 2294 ExecStart=/etc/rc.d/init.d/iBMA start (code=exited,
status=0/SUCCESS)
NOTE
If the iBMA service fails to be stopped, start the iBMA service and try again.
l Restart the iBMA service.
– Run the service command.
[root@Redhat6 iBMA2.0]# service iBMA restart
iBMA service stopped successfully.
iBMA service started successfully.
Restart iBMA service successfully.
– Run the systemctl command. (You need to run the systemctl status iBMA
command to query the command execution results after you run the systemctl
restart iBMA command.)
[root@Redhat6 iBMA2.0]# systemctl restart iBMA
[root@Redhat6 iBMA2.0]# systemctl status iBMA
● iBMA.service - LSB: Activates/Deactivates restful api agent service
Loaded: loaded (/etc/rc.d/init.d/iBMA)
Active: active (running) since Wed 2017-05-17 00:34:48 CST; 4s ago
Docs: man:systemd-sysv-generator(8)
Process: 16470 ExecStop=/etc/rc.d/init.d/iBMA stop (code=exited,
status=0/SUCCESS)
Process: 16602 ExecStart=/etc/rc.d/init.d/iBMA start (code=exited,
status=0/SUCCESS)
CGroup: /system.slice/iBMA.service
├─16660 python /opt/huawei/ibma/bin/Manager.py
├─16666 python bin/Monitor.py
├─16689 python bin/RedfishServer/iBMA_RedfishMain.py
├─17151 python /opt/huawei/ibma/lib/Linux/raidAndDisk/
PrintSmart.py RAID 0 0
NOTE
systemd uses the internal management mode on the service. After the iBMA is stopped by using another
mode, you will find that the iBMA service is still in running status after you run the systemctl
command.
Scenarios
Query, start, stop, and restart the iBMA service on a Windows OS. Windows Server 2012 R2
is used as an example.
Prerequisites
Conditions
Data
Procedure
l GUI
a. Log in to the server OS as the system administrator.
NOTE
Ensure that you start or stop the iBMA service as the system administrator.
b. Choose Start > Run, enter services.msc, and click OK.
The Service window is displayed, as shown in Figure 3-1.
c. Right-click iBMA and choose Start (Stop or Restart) from the shortcut menu.
The iBMA service starting (stopping or restarting) process begins, as shown in
Figure 3-2.
SERVICE_NAME: iBMA
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
ACCEPTS_PRESHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Huawei\iBMA2.0>
SERVICE_NAME: iBMA
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(STOPPABLE, NOT_PAUSABLE,
ACCEPTS_PRESHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x1c9c380
PID : 70848
FLAGS :
C:\Huawei\iBMA2.0>
SERVICE_NAME: iBMA
TYPE : 10 WIN32_OWN_PROCESS
STATE : 4 RUNNING
(STOPPABLE, NOT_PAUSABLE,
ACCEPTS_PRESHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x0
WAIT_HINT : 0x0
C:\Huawei\iBMA2.0>
NOTE
After the iBMA is installed, the service system is automatically registered. The iBMA service is
automatically started upon each startup. Users do not need to start the service manually.
l Query the iBMA service status.
[root@localhost:~] /etc/init.d/iBMA status
iBMA service is running.
NOTE
If the iBMA service is running, "iBMA service is already running" will be displayed after the start
command is executed.
l Stop the iBMA service.
[root@localhost:~] /etc/init.d/iBMA stop
iBMA service stopped successfully.
4 Troubleshooting
Driver Failed to enable the PCIe device. The PCIe device is Enable the PCIe
installati Enable Black Box on the iBMC disabled. device on the iBMC
on first. WebUI. For details,
see J Enabling
PCIe Devices.
A Black Box module of an The black box driver Uninstall the driver
earlier version has been loaded. of iBMA 1.0 has of iBMA 1.0 first
You need to unload it first. been installed, and then reinstall the
affecting the driver of iBMA 2.0.
installation of the For details about the
driver of iBMA 2.0. iBMA installation,
see 2.1.1 Installing
the iBMA.
iBMA Failed to register iBMA service. The iBMA service Check the OS
installati registration fails. compatibility
on according to 1.2
Software and
Hardware
Compatibility.
You need to reboot the OS to run The iBMA service Restart the OS.
iBMA service. runs only after the
OS is restarted after
successful
installation.
An older version of iBMA iBMA 1.0 has been Uninstall iBMA 1.0
(iBMA1.0) has been installed. installed and is first or perform the
You need to uninstall it first. incompatible with forcible installation
iBMA 2.0. (which is not
recommended).
A Black Box module of an older The black box driver Run the rmmod
version has been loaded. of an earlier version kbox command to
You need to unload it first. has been loaded, uninstall the black
affecting the proper box driver of an
running of iBMA earlier version.
2.0.
IPv6 is disabled for veth in this IPv6 is disabled on Enable IPv6 on the
host. the system, which virtual NIC of the
You need to change your settings may result in an iBMA, or change
or use IPv4 instead. iBMA running the iBMA startup
failure. mode to the one that
uses IPv4.
iBMA Could not find log.sh. The installation file Download the latest
service is missing. installation package
startup again.
PCIe device is being used by *** The PCIe device is Uninstall the driver
driver. You need to unload it occupied by another that occupies the
first. driver. PCIe device, and run
the iBMA service.
Redfish server user *** does not The user name Change the value of
exist. configured in HTTP server port
iBMA.ini does not in iBMA.ini in the
exist. config directory. For
details, see H
Redfish server port *** is The value of HTTP Modifying
invalid. server port Configuration
configured in Files.
iBMA.ini is not in
the range from 1024
to 65535.
Socket server port *** is invalid. The value of Socket Change the value of
server port Socket server port
configured in in iBMA.ini in the
iBMA.ini is not in config directory. For
the range from 1024 details, see H
to 65535. Modifying
NOTE Configuration
For VMware, the Files.
value of Socket
server port ranges
from 1024 to 63486.
NIC *** does not exist. The value of Reinstall the iBMA
iBMA_nic driver.
configured in
iBMA.ini does not
exist. The NIC
driver may be
damaged.
File *** does not exist. The iBMA file is Reinstall the iBMA.
lost. For details about
File *** is not executable. The operation how to install the
permission on the iBMA, see:
iBMA file is l Linux: 2.1.1
changed. Installing the
iBMA
l Windows: 2.2.1
Installing the
iBMA
l VMware ESXi:
2.3.1 Installing
the iBMA
Redfish server user is not root. The setfacl tool that Change the Redfish
You need to install 'setfacl' tool the iBMA depends server name to root,
to run iBMA service. on is not installed in or run the yum
the environment, install setfacl
which results in a command to install
startup failure. the setfacl tool.
Redfish server user is not root. The ACL function Change the Redfish
Failed to set ACL rules for of the partition server user name to
Redfish server user ***. where the iBMA root or enable the
installation directory ACL function in the
is located is not partition where the
enabled. iBMA installation
directory is located.
Failed to start Black Box. You The kdump function Disable the kdump
need to stop kdump service first. needs to be disabled function first and
before the black box then enable the
function is enabled. black box function.
For details, see H
Modifying
Configuration
Files.
The iBMA IP address format is The first digit of the Change the first
invalid. The first digit of an IP iBMA IP address in digit of the value of
address must be greater than 0 the configuration iBMA_http_server
and smaller than 223 and it file is smaller than _ip in iBMA.ini to a
cannot be 127. or equal to 0, greater digit greater than 0,
than 223, or equal to smaller than 223,
127. and not equal to 127.
The iBMC IP address format is The first digit of the Change the first
invalid. The first digit of an IP iBMC IP address in digit of the value of
address must be greater than 0 the configuration iBMC_ip in
and smaller than 223 and it file is smaller than iBMA.ini to a digit
cannot be 127. or equal to 0, greater greater than 0,
than 223, or equal to smaller than 223,
127. and not equal to 127.
The iBMA subnet mask format The iBMA subnet Change the value of
is invalid. mask format in the iBMA_netmask in
configuration file is iBMA.ini to the
invalid. correct subnet mask
format.
The iBMC subnet mask format The iBMC subnet Change the value of
is invalid. mask format in the iBMC_netmask in
configuration file is iBMA.ini to the
invalid. correct subnet mask
format.
Failed to verify the IP address. The iBMA and Change the iBMA
The iBMA and iBMC are on iBMC in the and iBMC IP
different network segments. configuration file addresses and subnet
are on different masks in iBMA.ini
network segments. at the same time.
Failed to verify the IP address. The iBMA and Change the iBMA
The iBMA and iBMC host IDs iBMC host IDs in and iBMC IP
are the same. the configuration addresses and subnet
file are the same. masks in iBMA.ini
at the same time.
Failed to configure the iBMC IP. Failed to configure Check whether the
the iBMC IP address iBMC is running
because the iBMC is properly.
being restarted or
the iBMC version is
incompatible.
Nic index is invalid. The NIC index does Restart the iBMA.
not exist because the
iBMA is not running
properly.
iBMA Failed to stop iBMA service. The iBMA service Stop the iBMA
service iBMA is upgrading, try again cannot be stopped service again after
stopping later! when the iBMA is the upgrade is
being upgraded. complete.
iBMA iBMA service is running. Stop it During iBMA Stop the iBMA
uninstall first. uninstallation, it is service first and then
ation detected that the uninstall the iBMA.
iBMA service is
running.
General This script must be run as root. This script is Run this script as
executed as a non- user root.
root user.
DKMS Failed to install the DKMS. The DKMS tool Install the DKMS
source must be installed tool first, and ensure
code and run properly that the tool is
package before the source running properly.
installati code package is
on installed.
Hard disk df
partition
name
Total hard df
disk partition
size (GB)
Hard disk df
partition used
capacity
(GB)
Link status ip addr show ethX, ethtool ethX | grep 'Link detected:'
Opti Vendor name Obtain the EEPROM data of the optical module by using
cal the ioctl interface of the NIC driver, and then resolve the
mod data based on the optical module protocol.
ule
Vendor Obtain the EEPROM data of the optical module by using
component the ioctl interface of the NIC driver, and then resolve the
name data based on the optical module protocol.
Vendor serial Obtain the EEPROM data of the optical module by using
number the ioctl interface of the NIC driver, and then resolve the
data based on the optical module protocol.
Type Compare the rate supported by the NIC and the rate
matching supported by the optical module. If there is an intersection,
the rates match.
Presence Read the EEPROM data of the optical module by using the
status ioctl interface of the NIC driver. If the data can be read
successfully, the optical module is properly installed.
High voltage Obtain the EEPROM data of the optical module by using
alarm the ioctl interface of the NIC driver, and then resolve the
threshold data based on the optical module protocol.
Low voltage Obtain the EEPROM data of the optical module by using
alarm the ioctl interface of the NIC driver, and then resolve the
threshold data based on the optical module protocol.
High voltage Obtain the EEPROM data of the optical module by using
warning the ioctl interface of the NIC driver, and then resolve the
threshold data based on the optical module protocol.
Low voltage Obtain the EEPROM data of the optical module by using
warning the ioctl interface of the NIC driver, and then resolve the
threshold data based on the optical module protocol.
FC/ Basi BDF number Call the base class self.getBdfInfo()function (ll /sys/class/
FCo c fc_host)
E infor
mati Manufacturer lspci|grep BDF
on Description lspci|grep BDF
iSCS Basi BDF number call base class self.getBdfInfo()function (ll /sys/class/
I c fc_host)
infor
mati Manufacturer lspci|grep BDF
on Description lspci|grep BDF
Interface NVMe
protocol type
Model l For the Huawei NVMe, use the hioadm tool to obtain
the information.
Firmware
l For the Intel NVMe, use the isdct tool to obtain the
version
information.
Serial NOTE
number l Download link of the ES3000 V2 hioadm tool: https://
support.huawei.com/enterprise/en/servers/es3000-v2-
Hard disk pid-21242728/software
status l Download link of the ES3000 V3 hioadm tool: https://
support.huawei.com/enterprise/en/server/es3000-v3-
Capacity pid-21500649/software/
(unit: byte) l Download link of the ES3000 V5 hioadm tool: https://
support.huawei.com/enterprise/en/servers/es3000-v5-
Power-on pid-22936194/software
duration
l Download link of the isdct tool: https://
downloadcenter.intel.com/download/27248/Intel-SSD-Data-
Used life
Center-Tool
Temperature
(unit: °C)
Number of
data errors
Critical alarm
Redundant
space
proportion
Warning
threshold of
the redundant
space
proportion
Total read
data volume
(unit: MB)
Total write
data volume
(unit: MB)
Total number
of host read
times
Total number
of host write
times
Busy period
of the
controller
(unit: minute)
Number of
power-on
times
Number of
unsafe
shutdown
times
Number of
error log
entries
System drive l Obtain the system drive letter of the logical disk under a
letter RAID from storelib
l Obtain the system drive letter of the logical disk of a
directly-connected disk from /sys/block
Boot disk Use storelib to obtain (LSI SAS3008 and LSI SAS2308 are
not supported)
Phys Basi Manufacturer Use storelib to obtain (the supported manufacturers include
ical c Seagate, WDC, HGST, SanDisk, Toshiba, Intel, Micron,
drive infor and Samsung)
mati
on RAID Use storelib to obtain
controller
card slot
number
Hard drive Use storelib to turn on the hard disk indicator and use IPMI
silkscreen commands to obtain
Hard disk Obtain from the SMART information (only SSD disks are
wear rate supported)
Usage of a Win32_Processor.LoadPercentage
single CPU
Swap psutil.swap_memory()
partition
usage
Manufacturer Win32_NetworkAdapter.Manufacturer
Driver Win32_PnPSignedDriver.DriverVersion
version
Bandwidth Win32_PerfFormattedDa-
usage ta_Tcpip_NetworkInterface.CurrentBandwidth
Auto- CIM_NetworkPort.AutoSense
negotiation MSFT_NetAdapter. AutoSense
mode
Number of psutil.net_io_counters(pernic=True)
lost packets
Number of psutil.net_io_counters(pernic=True)
sent packets
Number of psutil.net_io_counters(pernic=True)
received
packets
Team/Team MSFT_NetLbfoTeamMember
VLAN MSFT_NetLbfoTeamNic
information
MSFT_NetLbfoTeam
Driver devcon.exe
version
FC ID MSFC_FibrePortHbaAttributes.Attributes.FcID
Model MSFC_FCAdapterHBAAttributes.Model
Driver devcon.exe
version
Interface NVMe
protocol type
Model l For the Huawei NVMe, use the hioadm tool to obtain
the information (after the hioadm tool is installed, you
Firmware need to configure environment variables).
version
l For the Intel NVMe, use the isdct tool to obtain the
Serial information (after the isdct tool is installed, you need to
number configure environment variables)
NOTE
Hard disk
l Download link of the ES3000 V2 hioadm tool: https://
status support.huawei.com/enterprise/en/servers/es3000-v2-
pid-21242728/software
Capacity
(unit: byte) l Download link of the ES3000 V3 hioadm tool: https://
support.huawei.com/enterprise/en/server/es3000-v3-
Power-on pid-21500649/software/
duration l Download link of the ES3000 V5 hioadm tool: https://
support.huawei.com/enterprise/en/servers/es3000-v5-
Used life pid-22936194/software
l Download link of the isdct tool: https://
Temperature downloadcenter.intel.com/download/27248/Intel-SSD-Data-
(unit: °C) Center-Tool
Number of
data errors
Critical alarm
Redundant
space
proportion
Warning
threshold of
the redundant
space
proportion
Total read
data volume
(unit: MB)
Total write
data volume
(unit: MB)
Total number
of host read
times
Total number
of host write
times
Busy period
of the
controller
(unit: minute)
Number of
power-on
times
Number of
unsafe
shutdown
times
Number of
error log
entries
System drive Obtain the system drive letter of the logical disk under a
letter RAID from storelib
Boot disk Use storelib to obtain (LSI SAS3008 and LSI SAS2308 are
not supported)
Phys Basi Manufacturer Use storelib to obtain (the supported manufacturers include
ical c Seagate, WDC, HGST, SanDisk, Toshiba, Intel, Micron,
drive infor and Samsung)
mati
on RAID Use storelib to obtain
controller
card slot
number
Hard drive Use storelib to turn on the hard disk indicator and use IPMI
silkscreen commands to obtain
Hard disk Obtain from the SMART information (only SSD disks are
wear rate supported)
NOTE
1:
EtrackID: 800009FA
Firmware Version: DATE:2-5-12 REV:27.210
MAC Address: 2C-9D-1E-C1-D0-E2
NVM Version: 1.63
----End
Resource
-----------
Bus Type PCI-E (4X)
Slot Number 18
Hardware
-----------
ASIC Version BCM5719 A1
Firmware Version 5719-v1.43
Management Firmware NCSI 1.2.12
----End
l To obtain the firmware version of the Mellanox NIC by running commands using
mlxfwmanager.exe in the installation path, perform the following operations:
mlxfwmanager
-d|--dev DeviceName : Perform operation for specified mst
device(s).
Run 'mst status' command to list the
available
devices. Multiple devices can be specified
delimited by semicolons. A device list
containing
semicolons must be quoted.
-h|--help : Show this message and exit
-v|--version : Show the executable version and exit
--query : Query device(s) info
--query-format Format : (Query | Online query) output format, XML
| Text - default Text
-u|--update : Update firmware image(s) on the device(s)
-i|--image-file FileName : Specified image file to use
-D|--image-dir DirectoryName : Specified directory instead of default to
locate image files
-f|--force : Force image update
-y|--yes : Answer is yes in prompts
--no : Answer is no in prompts
--clear-semaphore : Force clear the flash semaphore on the
device,
No command is allowed when this flag is
used. NOTE: May result in system
instability
or flash corruption if the device or
another
application is currently using the flash.
Exercise caution.
--exe-rel-path : Use paths relative to the location of the
executable
-l|--list-content : List file/Directory content, used with --
image-dir
and --image-file flags
--archive-names : Display archive names in listing
--nofs : Burn image in a non failsafe manner
--log : Create log file
-L|--log-file LogFileName : Use specified log file
--no-progress : Do not show progress
-o|--outfile OutputFileName : Write to specified output file
--online : Fetch required FW images online from
Mellanox
server
--online-query-psid PSIDs : Query FW info, PSID(s) are comma separated
--key key : Key for custom download/update
--download DirectoryName : Download files from server to a specified
directory
--download-default : Use Default values for download
--get-download-opt OPT : Get download options for OS or Device
Options are: OS, Device
--download-device Device : Use '--get-download-opt Device' option to
view available devices for device specific
downloads
--download-os OS : Only for self_extractor download: Use '--
get-download-opt
OS' option to view available OS for sfx
download
--download-type Type : MFA | self_extractor - default All
--ssl-certificate Certificate : SSL certificate For secure connection
Examples:
1. Query specific device or all devices (if no device were supplied)
>> mlxfwmanager [-d <device>] [--query]
2. Burn device with specific image / MFA / images directory
>> mlxfwmanager -d <device> [-i <image file/MFA file> | -D <images dir>]
3. Update the card's firmware
>> mlxfwmanager -u
4. Update the card's firmware from latest version on the web
>> mlxfwmanager --online -u
Step 2 Query the Mellanox NIC firmware version by using the MAC address and GUID.
C:\Huawei\iBMA2.0\tools\mellanox>mlxfwmanager.exe
Querying Mellanox devices firmware ...
Device #1:
----------
----End
OS version vmware -l
OS main The value is split by dots. Obtain the first digit of the value
version of KernelVersion.
OS sub- The value is split by dots. Obtain the second digit of the
version value of KernelVersion.
Patch main The value is split by dots. Obtain the third digit of the
version value of KernelVersion.
Patch sub- The value is split by dots. Obtain the fourth digit of the
version value of KernelVersion and exclude 0.
OS uname -m
architecture
Memory esxtop -l
usage (%)
Hard disk df -k
partition
information
list
Driver name df -k
Total hard df -k
disk partition
size (GB)
Hard disk df -k
partition used
capacity
(GB)
Hard disk df -k
partition
usage (%)
VLAN ID esxcfg-vswitch -l
Working loadbalance
mode
Basic esxcfg-vmknic -l
information
Firmware /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a
version (FC)
Firmware /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a
version (FC)
Driver /usr/lib/vmware/vmkmgmt_keyval/vmkmgmt_keyval -a
version (FC)
Interface NVMe
protocol type
Model l For the Huawei NVMe, use the hioadm tool to obtain
the information.
Firmware
version
Serial l For the Intel NVMe, use the isdct tool to obtain the
number information (after the isdct tool is installed, you need to
run the ln -s /opt/intel/isdct/isdct /bin/isdct command
Hard disk to create a soft link).
status NOTE
Capacity l Download link of the ES3000 V2 hioadm tool: https://
support.huawei.com/enterprise/en/servers/es3000-v2-
(unit: byte)
pid-21242728/software
Power-on l Download link of the ES3000 V3 hioadm tool: https://
duration support.huawei.com/enterprise/en/server/es3000-v3-
pid-21500649/software/
Used life l Download link of the ES3000 V5 hioadm tool: https://
support.huawei.com/enterprise/en/servers/es3000-v5-
Temperature pid-22936194/software
(unit: °C) l Download link of the isdct tool: https://
downloadcenter.intel.com/download/27248/Intel-SSD-
Number of Data-Center-Tool
data errors
Critical alarm
Redundant
space
proportion
Warning
threshold of
the redundant
space
proportion
Total read
data volume
(unit: MB)
Total write
data volume
(unit: MB)
Total number
of host read
times
Total number
of host write
times
Busy period
of the
controller
(unit: minute)
Number of
power-on
times
Number of
unsafe
shutdown
times
Number of
error log
entries
Boot disk Use storelib to obtain (LSI SAS3008 and LSI SAS2308 are
not supported)
Phys Basi Manufacturer Use storelib to obtain (the supported manufacturers include
ical c Seagate, WDC, HGST, SanDisk, Toshiba, Intel, Micron,
drive infor and Samsung)
mati
on RAID Use storelib to obtain
controller
card slot
number
Hard drive Use storelib to turn on the hard disk indicator and use IPMI
silkscreen commands to obtain
Hard disk Obtain from the SMART information (only SSD disks are
wear rate supported)
This topic describes the internal programs of the iBMA software package on Linux.
l log.sh in the script directory of the installation directory is internally invoked scripts of
the iBMA and cannot be used independently.
l PGPVerify and CMSVerify in the lib/Linux/upgrade directory of the installation
directory are tools used for file verification of the iBMA upgrade function. They can also
be used independently.
This topic describes the internal programs of the iBMA software package on Windows.
l PGPVerify.exe
a. You can double-click PGPVerify.exe in the C:\Huawei\iBMA2.0\lib\Windows
\upgrade directory to verify the .asc digital signature file, as shown in Figure C-1.
b. You can click Single Verify (used for verifying a single .asc digital signature file)
or Multiple Verify (used for verifying multiple .asc digital signature files) to select
one or multiple local digital signature files for verification.
If the verification result is PASS in green and the value of public key finger is
B1000AC3 8C41525A 19BDC087 99AD81DF 27A74824, the verification is
passed, as shown in Figure C-2.
CMSVerify.exe is used for CMS verification. The usage is similar to that on Linux.
This topic describes the internal programs of the iBMA software package on VMware.
PGPVerify and CMSVerify in the /etc/cim/huawei/iBMA2.0/lib/VMware/upgrade
directory are tools used for file verification of the iBMA upgrade function. They can also be
used independently. The usage is similar to that on Linux.
E Introduction to bob
Overview
bob is a forwarding tool used to help the in-band network remote host communicate with the
local BMC by using the in-band networking. It supports service management (starting,
stopping, or restarting the bob service). It is integrated in the iBMA installation package and
depends on the iBMA process. It cannot be deployed or work independently.
bob provides a CLI bobCmd. It is used to start, stop, or restart the bob service and related
configuration. The forwarding configuration supports online configuration and does not
require service restart. The configuration supports persistence, that is, the configuration will
not be lost after system restart.
File Location
l Location of the main bob process
– Linux: /opt/huawei/ibma/bin/bob
– Windows: C:\Huawei\iBMA2.0\bin\bob.exe
– VMware: /etc/cim/huawei/iBMA2.0/bin/bob
l Location of bobCmd
– Linux: /opt/huawei/ibma/tools/bob/bobCmd
– Windows: C:\Huawei\iBMA2.0\bin\bobCmd.exe
– VMware: /etc/cim/huawei/iBMA2.0/tools/bob/bobCmd
positional arguments:
{service,bmc-server,bmc-client}
sub-command help
service service sub-command help
bmc-server bmc-server sub-command help
bmc-client bmc-client sub-command help
optional arguments:
-h, --help show this help message and exit
[root@localhost bin]#
l service subcommand
bobCmd service {start,stop,restart}
positional arguments:
{start,stop,restart}
optional arguments:
-h, --help show this help message and exit
[root@localhost bin]#
l bmc-server subcommand
bobCmd bmc-server {show,set,del} [-b BMC_PORT] [-a ADDR [ADDR ...]] [-p
PORT] [-t {TCP,UDP}] [-w WHITE_LIST [WHITE_LIST ...] | -aw
ADD_WHITE_LIST [ADD_WHITE_LIST ...] | -dw DEL_WHITE_LIST
[DEL_WHITE_LIST ...]] [-e {0,1}]
NOTE
l Services related to the iBMC must be started. The configured service port number (the -b
parameter) must be the same as that configured on the iBMC.
l The configured listening port number (the -p parameter) cannot conflict with other services of
the iBMA.
-a ADDR [ADDR ...] IP address used for forwarding on the OS. Multiple IP
addresses can be entered.
positional arguments:
{show,set,del}
optional arguments:
-h, --help show this help message and exit
-b BMC_PORT, --bmc-port BMC_PORT
-a ADDR [ADDR ...], --addr ADDR [ADDR ...]
-p PORT, --port PORT
-t {TCP,UDP}, --trans-protocol {TCP,UDP}
-e {0,1}, --enable {0,1}
-w WHITE_LIST [WHITE_LIST ...], --white-list WHITE_LIST [WHITE_LIST ...]
-aw ADD_WHITE_LIST [ADD_WHITE_LIST ...], --add-white-list ADD_WHITE_LIST
[ADD_WHITE_LIST ...]
-dw DEL_WHITE_LIST [DEL_WHITE_LIST ...], --del-white-list DEL_WHITE_LIST
[DEL_WHITE_LIST ...]
[root@localhost bin]#
Query the configuration of the forwarding service when the BMC is used as the server.
[root@localhost bin]# ./bobCmd bmc-server show
BMC-SERVER-PORT: 22
ENABLE: False
OS-LISTEN-PORT: 1022
OS-LISTEN-IP: [u'******']
TRANS-PROTOCOL: None
WHITE-LIST: []
[root@localhost bin]#
l bmc-client subcommand
bobCmd bmc-client {show,enable,disable}
NOTE
positional arguments:
{show,enable,disable}
optional arguments:
-h, --help show this help message and exit
[root@localhost bin]#
Display the configuration of the forwarding service when the BMC is used as the client.
[root@localhost bin]# ./bobCmd bmc-client show
ENABLE: True
BMC-CLIENT-PORT: 30003
SERVER-PORT: 162
SERVER-IP: ******
ACTIVE: False
TRANS-PROTOCOL: UDP
BMC-CLIENT-PORT: 30002
SERVER-PORT: 1234
SERVER-IP: ******
ACTIVE: False
TRANS-PROTOCOL: UDP
BMC-CLIENT-PORT: 30001
SERVER-PORT: 162
SERVER-IP: ******
ACTIVE: False
TRANS-PROTOCOL: UDP
BMC-CLIENT-PORT: 30000
SERVER-PORT: 162
SERVER-IP: ******
ACTIVE: False
TRANS-PROTOCOL: UDP
[root@localhost bin]#
The iBMA can be used properly after the firewall is disabled or a firewall rule is added.
Linux
l Disable the firewall. The following commands can only be used to temporarily disable
the firewall. After the OS is restarted, the firewall is enabled again.
– Red Hat 6.8: service ip6tables stop
– Red Hat 7.2, Red Hat 7.3 and CentOS 7.2: systemctl stop firewalld
– SUSE 12.1: rcSuSEfirewall2 stop
l Add firewall rules permanently, and restart the OS for the configuration to take effect.
Edit the /etc/rc.d/rc.local script and add the following rules in IPv6 mode:
ip6tables -I INPUT -i veth -p tcp --dport 8090 -j ACCEPT
ip6tables -I OUTPUT -o veth -p tcp --sport 8090 -j ACCEPT
ip6tables -I INPUT -i veth -p icmpv6 --icmpv6-type neighbour-solicitation -j
ACCEPT
ip6tables -I INPUT -i veth -p icmpv6 --icmpv6-type neighbour-advertisement -j
ACCEPT
ip6tables -I INPUT -i veth -p icmpv6 --icmpv6-type neighbour-advertisement -j
ACCEPT
Add the following rule in IPv4 mode:
iptables -I INPUT -i veth -p tcp --dport 8090 -j ACCEPT
iptables -I OUTPUT -o veth -p tcp --sport 8090 -j ACCEPT
NOTE
VMware
l Disable the firewall.
esxcli network firewall set -e false -d true
l Add firewall rules permanently.
a. Compile the iBMA_server.xml script, as shown in Figure F-1, and save the script
to the /scratch/iBMA/ directory on the hard disk of the server.
Windows
This section describes how to permanently disable the firewall. The method is applicable to
Windows Server 2016, Windows Server 2012, and Windows Server 2012 R2.
----End
G Environmental Requirements
OS Environmental Requirements
NOTE
If the modification of the configuration file does not comply with the rules or the values are set in
incorrect formats, an iBMA startup failure may occur.
iBMA_k Whether the black box false You can change the
box function is enabled. value to true.
iBMA_s Whether iBMA logs are false You can change the
yslog recorded in syslog. value to true.
Currently, only Linux
OSs support this
parameter.
actual_m Memory usage The default value is true You can change the
emory_u calculation method. when the iBMA is installed. value to false.
sage NOTE When the iBMA is
l If this parameter is set upgraded, the value of the
to true, the source iBMA version will be
calculation method is used. If the source iBMA
the same as that for version does not have this
the procps tool
package of the 3.3.15
parameter, the default value
version. If this is false.
parameter is set to
false, the calculation
method is the same as
that for the procps tool
package of the 3.3.9
version and earlier
versions.
l Currently, only Linux
OSs support this
configuration item.
interval Monitoring interval of the timer (unit: The value ranges from
Time second). minIntervalTime to
maxIntervalTime.
NOTE
If the modification of the file does not comply with the modification rules or is in an incorrect format,
the watchdog function will become unavailable.
Enable Whether OAM functions false The value can be true or false.
are enabled. The default value is false.
PassiveMode Whether the passive true The value can be true or false.
mode is used. The default value is true.
SendPktInterval Interval for sending 200 The unit is ms, and the value
OAM discovery packets. ranges from 100 to 1200. The
minimum interval that can be
identified is 100 ms.
LostLinkTime OAM discovery timeout 1200 The unit is ms. The timeout
interval. interval cannot be smaller than the
packet sending interval. The
minimum interval that can be
identified is 100 ms.
After the OAM.ini configuration file is modified, you can invoke and install ReloadOAM in
the config or bin directory to load OAM modules.
NOTE
Currently, only Linux OSs (including Red Hat, CentOS, SUSE, Ubuntu, Citrix, and FusionSphere) of
E9000 servers support OAM and have this configuration file.
Nic_broadcom_ Path of the Broadcom Set this parameter to the actual path, and use
dir NIC firmware tool. the slash (/) as the path separator.
FC_QConverge Path of the Qlogic FC Set this parameter to the actual path, and use
ConsoleCLI_pa firmware tool. the slash (/) as the path separator.
th
l You can download the Broadcom NIC firmware tool from the official website.
l You can download the Qlogic FC firmware tool from the official website.
port Local syslog listening 514 The value is the same as the syslog
port service listening port of the current
system. The value ranges from 1 to
65535.
type Log type used when user The value can be auth, cron, daemon,
iBMA logs are recorded kernel, mail, syslog, lpr, or user.
in syslog
Only correct configuration takes effect. If the configuration is incorrect, default values are
used. The actual port and log type are recorded in logs.
iBMA logs are recorded in syslog and depend on the syslog service of the current system. You
need to enable the function of listening to UDP connections in the following way:
/etc/rsyslog.conf
# Listen to UDP connections.
$ModLoad imudp
$UDPServerRun 514
"maxMajorMillisecond" : 300,
"majorWeight" : 2,
"minMajorWeight" : 0,
"maxMajorWeight" : 10,
"periodSecond" : 600,
"minPeriodSecond" : 60,
"maxPeriodSecond" : 86400,
"intervalSecond" : 1,
"minIntervalSecond" : 1,
"maxIntervalSecond" : 10,
"alarmPercent" : 15,
"minAlarmPercent" : 0,
"maxAlarmPercent" : 100,
"recoverAlarmPercent" : 13,
"minRecoverAlarmPercent" : 0,
"maxRecoverAlarmPercent" : 100
}
}
minMinorMillise Minimum I/O latency 10 You are advised not to change the
cond determining a minor value.
I/O performance
decrease of the
sampling point
maxMinorMillise Maximum I/O latency 100 You are advised not to change the
cond determining a minor value.
I/O performance
decrease of the
sampling point
minMajorMillise Minimum I/O latency 10 You are advised not to change the
cond determining a major value.
I/O performance
decrease of the
sampling point
maxMajorMillise Maximum I/O latency 300 You are advised not to change the
cond determining a major value.
I/O performance
decrease of the
sampling point
periodSecond Detection period 600 The unit is s. The value is in the range
from minPeriodSecond to
maxPeriodSecond.
maxPeriodSecon Maximum detection 8640 You are advised not to change the
d period 0 value.
intervalSecond Interval of hard disk 1 The unit is s. The value is in the range
I/O sampling from minIntervalSecond to
maxIntervalSecond.
minAlarmPercen Minimum weight ratio 0 You are advised not to change the
t determining that the value.
hard disk I/O
performance decreases
maxAlarmPercen Maximum weight ratio 100 You are advised not to change the
t determining that the value.
hard disk I/O
performance decreases
minRecoverAlar Minimum weight ratio 0 You are advised not to change the
mPercent determining that the value.
hard disk I/O
performance restores
maxRecoverAlar Maximum weight ratio 100 You are advised not to change the
mPercent determining that the value.
hard disk I/O
performance restores
Category Sense Key error type of - Modify the parameter based on see t10
the hard disk to be specifications.
detected
Sense Hard disk sense code - Modify the parameter based on see t10
Code determined by Sense specifications.
Key, ASC, and ASCQ
– VMware
– Windows
l IPv4
To implement the IPv4 configuration, you need to set the iBMA_http_server_ip
configuration item in the iBMA.ini configuration file to an IPv4 address and add the
iBMC_ip, iBMA_netmask, and iBMC_netmask configuration files. The configuration
item names in the configuration file are case-insensitive. Table H-9 describes the
parameters. After iBMA.ini is modified, you need to restart the iBMA for the
configuration to take effect. You do not need to manually run commands to configure
virtual network port IP addresses. Upon the iBMA startup, the iBMA and iBMC virtual
network port IP addresses are configured automatically.
iBMC_ip IP address for the This parameter can be left empty when
communications the iBMA uses IPv6. Otherwise, you
between the iBMC and need to set this parameter to a value in
the iBMA. correct IPv4 format.
iBMA_netmas iBMA subnet mask. This parameter can be left empty when
k the iBMA uses IPv6. Otherwise, you
need to set this parameter to a value in
correct subnet mask format.
iBMC_netmas iBMC subnet mask. This parameter can be left empty when
k the iBMA uses IPv6. Otherwise, you
need to set this parameter to a value in
correct subnet mask format.
For example, modify the Linux configuration file (as shown in Figure H-5) to
implement the IPv4 configuration.
NOTE
For details about how to resolve the problems that occur during the IP address configuration process, see
4.1 Common Troubleshooting.
I Enabling IPv6
This chapter describes how to enable IPv6 on Linux, Windows, and VMware.
l Linux
NOTE
a. Check whether IPv6 is disabled. 0 indicates that IPv6 is enabled. 1 indicates that
IPv6 is disabled.
[root@localhost iBMA2.0]# sysctl net.ipv6.conf.veth.disable_ipv6
net.ipv6.conf.veth.disable_ipv6 = 0
[root@localhost iBMA2.0]#
e. Select Use the following IPv6 address and set IPv6 address and Subnet prefix
length, as shown in Figure I-3.
f. Click OK.
The settings are saved.
l VMware
a. View the IPv6 enabling status.
[root@localhost:~] esxcli network ip get
IPv6Enabled: false
b. Enable IPv6 (this operation is valid permanently, and the configuration takes effect
after the OS is restarted).
[root@localhost:~] esxcli network ip set -e true
[root@localhost:~]
This topic describes how to enable PCIe devices on the Black Box page of the iBMC WebUI.
Scenarios
Internet Explorer 11 is used as an example to describe how to enable PCIe devices on the
iBMC WebUI.
Prerequisites
Data
l IP address and subnet mask of the server iBMC management network port
l User name and password of the server iBMC
Procedure
Step 1 Connect the PC to the iBMC.
1. Use a network cable to connect the network port on the PC and the iBMC management
network port on the server.
2. Set an IP address for the PC to enable communication between the PC and the iBMC.
The server IP address must be on the same network segment as the IP address of the
iBMC management network port.
For example, set the IP address to 192.168.2.10 and the subnet mask to 255.255.255.0.
Set the web browser properties.
3. Open Internet Explorer, choose Tools > Internet Options from the menu bar.
The Internet Options dialog box is displayed.
4. Click the Connections tab, and click LAN Settings.
The Local Area Network (LAN) Settings dialog box is displayed.
5. In the Proxy server area, deselect Use a proxy server for your LAN.
6. Click OK.
The Local Area Network (LAN) Settings dialog box closes.
7. Click OK.
The Internet Options dialog box is closed.
Step 2 Log in to the iBMC WebUI.
1. Open Internet Explorer, enter the IP address of the iBMC management network port in
the address box, and press Enter.
The URL is in the format of http://IP address of the iBMC management network port.
A dialog box is displayed.
2. Click Continue to this website (not recommended).
The login page is displayed, as shown in Figure J-1.
4. Click Yes.
The server is powered on.
----End
The black box image file records the system status and debugging information before the
system is down. A .txt file will be generated after the black box image file is read and parsed.
This .txt file can be used to locate the cause of the system down. The file supports only Linux
OSs.
NOTE
To use the black box function, change the value of iBMA_kbox in the iBMA.ini file to true. For details,
see H.1 Description of the iBMA.ini Configuration File.
Before using the black box function, you need to disable the kdump function.
Function
Obtain information about how to use hwkbox commands.
Format
hwkbox -h
hwkbox --help
Parameters
None
Usage Guidelines
The short and long commands can be used together.
Example
[root@master ~]#cd /opt/huawei/ibma/bin/
[root@master bin]# ./hwkbox -h
Usage:
hwkbox <-r|-p|-v|-h>
-r,--read [output filename]: read data from kbox
-p,--parse <data filename> [parse filename]: parse kbox original data
-v,--version: display the software version
information
-h,--help: display the help information
Function
To query software version information about the hwkbox commands, run the hwkbox -v or
hwkbox --version command.
Format
hwkbox -v
hwkbox --version
Parameters
None
Usage Guidelines
The short and long commands can be used together.
Example
[root@master bin]# ./hwkbox -v
The software version is:5.39
Function
Read the black box image.
Format
hwkbox -r [output filename]
Parameters
Parameter Description Value
output filename Specifies the black box If this parameter is not specified, a file
image. named kbox_data+date will be
automatically generated in the current
directory.
Usage Guidelines
The short and long commands can be used together.
Example
[root@master bin]# ./hwkbox -r
Read data from the kbox successfully!!
Function
Parse the black box original image.
Format
hwkbox -p <data filename> [parse filename]
hwkbox --parse <data filename> [parse filename]
Parameters
Parameter Description Value
parse filename Specifies the file generated after If this parameter is not specified,
the original image is parsed. the default file name Result.txt
will be used.
Usage Guidelines
The short and long commands can be used together.
Ensure that the original image exists and the specified parse filename is correct.
Example
[root@master bin]# ./hwkbox -p kbox_data__2016-12-20_4-51-15.img
Parse kbox data succeed!
This chapter describes how to install, uninstall, and upgrade the DKMS source code package.
SUSE 12.1 is used as an example. The DKMS source code package does not support SUSE
11.3 and SUSE 11.4.
Download the DKMS source code package of the latest version from the Support E website.
On the download page, click to obtain the digital certificate, and click to download
the software. For details about how to obtain the verification tool and method, see Software
Digital Signature (OpenPGP) Validation Tool.
Step 3 Check that the DKMS tool and kernel development package have been installed.
linux-nm7b:/ # rpm -qa | grep dkms
dkms-2.2.0.3_git20141020-5.1.noarch
Step 4 Decompress the source code package to obtain the .rpm and .deb installation packages.
linux-nm7b:/home/dkmssrc # tar xzvf iBMA_Driver-dkms-0.2.7-src.x86_64.tar.gz
iBMA_Driver-dkms-0.2.7-src.x86_64.rpm
ibmasrc-dkms-0.2.7.amd64.deb
Step 5 Install the corresponding package based on the support status of .rpm or .deb package of the
system (the .rpm package is used as an example).
linux-nm7b:/home/dkmssrc # rpm -ivh iBMA_Driver-dkms-0.2.7-src.x86_64.rpm
Preparing...
################################# [100%]
Updating / installing...
1:iBMA_Driver-dkms-0.2.7-src
################################# [100%]
Installing the DKMS...
Installation successful.
----End
NOTE
If the iBMA has been installed, the DKMS source code package installation will fail. You need to
uninstall the iBMA first and then install the DKMS source code package.
Step 2 Uninstall the package according to the method corresponding to the .rpm or .deb package
(the .rpm package is used as an example).
linux-nm7b:/ # rpm -e iBMA_Driver-dkms-0.2.7-src.x86_64
Uninstalling... Please wait for a moment.
Uninstall the DKMS successfully.
----End
On the download page, click to obtain the digital certificate, and click to download
the software. For details about how to obtain the verification tool and method, see Software
Digital Signature (OpenPGP) Validation Tool.
Step 3 Decompress the source code package to obtain the .rpm and .deb installation packages.
Step 4 Install the corresponding package based on the support status of .rpm or .deb package of the
system.
----End
The following uses SUSE 12.1 as an example to describe how to compile the iBMA driver.
Save the compiled iBMA driver to the corresponding directory of the OS of the driver. Then
the iBMA can be installed properly. The iBMA driver cannot be compiled on SUSE 11.3 and
SUSE 11.4.
Step 1 Check whether the system environment meets the compiling requirements.
l On Ubuntu, you can use the following method to query whether the gcc, make, and dpkg
tools and kernel development packages are installed in the system.
root@ubuntu14:~# root@ubuntu14:~# dpkg -l |grep gcc
ii gcc 4:4.8.2-1ubuntu6
amd64 GNU C root@ubuntu14:~# dpkg -l |grep make
ii make 3.81-8.2ubuntu3
amd64 An utility for Directing compilation.
l On a non-Ubuntu system, you can use the following method to query whether the gcc,
make, and rpm-build tools and kernel packages are installed in the system.
linux-ij6i:~ # rpm –qa |grep gcc
gcc-4.8-6.189.x86_64
linux-ij6i:~ # rpm -qa |grep make
make-4.0-4.1.x86_64
linux-ij6i:~ # rpm -qa |grep rpm-build
rpm-build-4.11.2-10.1.x86_64
linux-ij6i:~ # rpm -qa |grep kernel-devel
kernel-devel-3.12.49-11.1.noarch
Step 2 (Optional) In the kernel-ml kernel environment, check whether retpoline is enabled on the
target host. Skip this step for other kernel versions.
Run the following command to check whether retpoline is enabled in the environment where
the iBMA is to be installed.
l If the command output does not contain "retpoline", retpoline is not enabled.
[root@localhost /]# modinfo igb | grep vermagic
vermagic: 4.14.15-1.el7.elrepo.x86_64 SMP mod_unload modversions
a. Go to the root directory of the kernel source code in the compilation environment.
[root@localhost /]# cd /usr/src/kernels/4.14.15-1.el7.elrepo.x86_64
[root@localhost 4.14.15-1.el7.elrepo.x86_64]#
i. Find the Processor type and features option, select <Select>, and press
Enter to access the submenu.
ii. Find the Avoid speculative indirect branches in kernel option, and set it to
the same value as that in the environment. The asterisk (*) in the brackets
indicates that the function is enabled. Otherwise, the function is disabled. You
can press the space bar to modify the configuration. After the configuration is
complete, select <Save>, and press Enter to save the configuration.
v. After the driver is compiled, run the following command to check whether the
compiled driver is consistent with that in the environment:
[root@localhost Linux]# modinfo host_edma_drv.ko | grep vermagic
vermagic: 4.14.15-1.el7.elrepo.x86_64 SMP mod_unload
modversions
Download the DKMS source code package of the latest version from the Support E website.
On the download page, click to obtain the digital certificate, and click to download
the software. For details about how to obtain the verification tool and method, see Software
Digital Signature (OpenPGP) Validation Tool.
Step 5 Copy the software package to the server OS directory, such as /home/dkmssrc/.
Step 6 Log in to the server OS and go to the directory where the software package is located.
Step 7 Decompress the source code package to obtain the .rpm and .deb installation packages.
linux-ij6i:/home/dkmssrc # tar xzvf iBMA_Driver-dkms-0.2.7-src.x86_64.tar.gz
iBMA_Driver-dkms-0.2.7-src.x86_64.rpm
ibmasrc-dkms-0.2.7.amd64.deb
The Ubuntu OS has only the .deb package. Therefore, you need to run the following
command on Ubuntu to decompress ibmasrc-dkms-0.2.7.amd64.deb:
cd usr/src/iBMA_Driver-0.2.7/
Step 10 Run the following command to add the operation permission for build_manual.sh command:
chmod +x build_manual.sh
linux-ij6i:/home/dkmssrc/usr/src/iBMA_Driver-0.2.7 # chmod +x build_manual.sh
linux-ij6i:/home/dkmssrc/usr/src/iBMA_Driver-0.2.7 #
Step 11 Run the following command to compile the iBMA driver and package the compiled iBMA
driver:
./build_manual.sh sles-12sp1
The parameter in the same position as sles-12sp1 in the command varies according to the OS,
as shown in Table M-1.
Table M-2 Mapping relationship between the driver package storage path and the OS type
OS Driver Package Storage Path
SUSE iBMA2.0/drivers/SUSE/
CentOS iBMA2.0/drivers/CentOS/
Citrix iBMA2.0/drivers/Citrix/
EulerOS iBMA2.0/drivers/EulerOS/
Ubuntu iBMA2.0/drivers/Ubuntu/
Step 13 Install the iBMA. For details, see 2.1.1 Installing the iBMA.
----End
N iBMA Commands
This section describes the iBMA commands on Linux and Windows OSs.
positional arguments:
{version,service} sub-command help
version show iBMA version information
service service sub-command help
optional arguments:
-h, --help show this help message and exit
[root@Redhat6 iBMA2.0]# ibmacli –help
usage: ibmacli [-h] {version,service} …
positional arguments:
{version,service} sub-command
help
version show iBMA version information
service service sub-command help
optional arguments:
-h, --help show this help message and exit
[root@Redhat6 iBMA2.0]# ibmacli service –h
usage: ibmacli [-h] {status,start,stop,restart} …
positional arguments:
{status,start,stop,restart}
optional arguments:
-h, --help show this help message and exit
Parameter Description
l service subcommand
service {status,start,stop,restart}
NOTE
If the iBMA service is running, "iBMA service is already running" is displayed after you run the start
command.
O Obtaining Help
This topic describes how to contact Huawei for technical support if a fault persists during
routine maintenance or troubleshooting.
NOTE
You can also quickly locate a product document by entering a keyword in the search text box at the
upper right corner of the web page.
P Glossary
black box Used to store system status and debugging information before system resets.
digital A message signed with a sender's private key that can be verified by anyone
signature who has access to the sender's public key. Digital signature gives the receiver
the reason to believe the message was sent by the claimed sender. A proper
implementation of digital signature is computing a message digest for the
message sent from the sender to the receiver, and then signing the message
digest. The result is called digital signature and is sent to the receiver together
with the original message.
log A file that records information about system events generated during the
system running. System event information includes system running
information, input/output (I/O) operations, abnormal operations, and security
information. Log information helps system O&M and troubleshooting.
port 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) port.
server A special computer that provides services for clients in the network
environment.
slot A position defined by a pair of upper and lower guide rails in a chassis for
holding a board.
This topic list the acronyms and abbreviations used in this document.
OS Operating System