Beruflich Dokumente
Kultur Dokumente
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: https://e.huawei.com
Overview
This document describes how to install and configure the SAP HANA single-node system on
the CH121 V5, CH242 V5, 2288H V5, 2488H V5, or 9008 V5 server.
By reading this document, you can learn the SAP HANA single-node solution and installation
planning, OS installation and configuration, external storage configuration, and SAP HANA
database installation.
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 11 (2019-11-04)
This issue is the eleventh official release:
Issue 10 (2019-08-23)
This issue is the tenth official release. Modified 12.2 Problem Handling Process.
Issue 09 (2019-06-13)
This issue is the ninth official release:
Issue 08 (2019-05-10)
This issue is the eighth official release. Modified 3.5 Software Planning (SLES) and 11 OS
Lifecycle.
Issue 07 (2019-03-28)
This issue is the seventh official release:
l Added the content of SLES 15.
l Deleted the content of 8100 V5.
l Added the content of 9008 V5.
l Added the contents of SLES 12 SP4.
l Added the database version HANA2.0 SPS03.
Issue 06 (2018-12-26)
This issue is the sixth official release. Modified 9.3.1 Modifying HANA Database 1.0
Parameters.
Issue 05 (2018-09-25)
This issue is the fifth official release. Added 12 Responsibility Matrix and Problem
Handling Process.
Issue 04 (2018-08-10)
This issue is the fourth official release. Added 10 Registering and Activating the OS.
Issue 03 (2018-07-09)
This issue is the third official release. Modified 9.3.2 Modifying HANA Database 2.0
Parameters.
Issue 02 (2018-05-15)
This issue is the second official release. Added the contents of SLES 12.3 and RHEL 7.4.
Issue 01 (2018-04-03)
This is the first official release.
Contents
11 OS Lifecycle.............................................................................................................................. 242
11.1 SLES for SAP Lifecycle........................................................................................................................................... 242
11.2 RHEL for SAP Lifecycle..........................................................................................................................................244
1 Solution Overview
This section list the SAP HANA configurations, including the CPU quantity, memory
capacity, storage resource type, and storage capacity, for the CH121 V5, CH242 V5, 2288H
V5, 2488H V5, and 9008 V5.
1.1 SAP HANA configuration (CH121 V5)
1.2 SAP HANA configuration (CH242 V5)
1.3 SAP HANA configuration (2288H V5)
1.4 SAP HANA configuration (2488H V5)
1.5 SAP HANA configuration (9008 V5)
Information such as the OS and certification configuration is continuously changing. The above table are
for reference only. Find the latest information at the SAP HANA certification website (http://
global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html).
Information such as the OS and certification configuration is continuously changing. The above table are
for reference only. Find the latest information at the SAP HANA certification website (http://
global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html).
Information such as the OS and certification configuration is continuously changing. The above table are
for reference only. Find the latest information at the SAP HANA certification website (http://
global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html).
Information such as the OS and certification configuration is continuously changing. The above table are
for reference only. Find the latest information at the SAP HANA certification website (http://
global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html).
Information such as the OS and certification configuration is continuously changing. The above tables
are for reference only. Find the latest information at the SAP HANA certification website (http://
global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/appliances.html).
For details about the OS and SAP HANA compatibility, see the official SAP documents:
https://launchpad.support.sap.com/#/notes/2235581.
3 Installation Planning
The default iBMC IP address is the default IP address, without being changed by a customer, of the
network port on the host. You can use the default IP address to log in to the iBMC WebUI and change
the default IP address as required.
iBMC 192.168.2.100
udev-228-150.32.1.x86_64.r
pm
You can perform the following operations to find the OS software desired:
Step 1 Enter https://www.suse.com/ in the address box of the browser to go to the SUSE official
website.
Step 2 Click Free Downloads on the right and download the OS as required. The related kernel can
be searched and downloaded in the search box above.
----End
l tuned-
utils-2.8.0-5.el7.noarch.r
pm
Step 3 To download the corresponding kernel or RPM package, click RPM Package Search on the
right and enter the software package name, for example,
kernel-3.10.0-957.10.1.el7.x86_64.rpm. Do not enter any space or other characters along
with the software package name.
You can also enter a keyword for fuzzy search (for example, kernel and resource-agents).
Select the corresponding version and architecture to browse and download the kernel or RPM
package of the corresponding version.
----End
This part uses Internet Explorer 11 as an example to describe how to log in to the iBMC
WebUI.
l A maximum of four users can log in to the iBMC WebUI at the same time.
l By default, the system timeout period is 5 minutes. If no operation is performed on the WebUI
within 5 minutes, the user will be automatically logged out of the WebUI. If this happens, you need
to enter the user name and password to log in again.
l The system locks a user account if the user enters incorrect passwords for consecutive five times.
The user account is automatically unlocked 5 minutes later. The system administrator can also
unlock a user account using the command-line interface (CLI).
l For security purposes, change the initial password after the first login and change your password
periodically.
Step 1 Check that the OS and browser versions of the iBMC client (a local PC) are as per
requirements. If the remote control function needs to be used, ensure that the Java Runtime
Environment (JRE) version is as per requirements.
Step 2 Set an IP address for the PC, and ensure that the IP address is on the same network segment as
the iBMC management network port.
Step 3 Connect the PC to the iBMC management network port using a network cable.
Step 4 Enter https://ipaddress/ in the address box of a browser, in which ipaddress is the IP address
of the iBMC management network. The default IP address is 192.168.2.100.
Step 5 If the security alert dialog box shown in Figure 4-1 is displayed, click Continue to this
website (not recommended).
If you do not want this dialog box to be displayed, add iBMC to Exception Site List on Java Control
panel or set the Java security level to a lower level. This operation may reduce user security. Exercise
caution when performing this operation.
On the login page that is displayed, enter the default user name and password (the default user
name is Administrator and the default password is Admin@9000).
The Overview page is displayed, showing the user name in the upper right corner.
On the displayed Remote Console page, click Java Integrated Remote Console (Shared) or
HTML5 Integrated Remote Console (Shared).
To use the remote virtual console, you must have a running environment of Java 1.6 U25 or later. You
can download the Java running environment from http://www.java.com.
Click . If the server is not powered on, click Power On. If the server is powered on, click
Forced System Reset.
----End
Step 1 Power on the server. When the screen shown in the following figure is displayed, press F11 to
enter the BIOS setup screen.
Step 2 In the displayed dialog box, enter the password and press Enter.
Step 3 Select Setup Utility and press Enter to start the BIOS Setup Utility program.
Step 5 Select Processor Configuration and press Enter. The configuration screen is displayed.
Step 6 Select Hyper-Threading [ALL], press Enter, and select Enabled. Press Esc to return to the
previous screen.
Step 10 Select EIST(P-State), press Enter, and select Enabled. Select Turbo Mode, press Enter,
and select Disabled. Press Esc to return to the previous screen.
Step 12 Select CPU C6 report, press Enter, and select Disabled. Select Enhanced Halt State
(C1E), press Enter, and select Disabled. Press Esc to return to the previous screen.
Step 14 Select Package C State, press Enter, select C0/C1 state, and press Esc to return to the
previous screen.
Step 15 Select Boot > Boot Type, press Enter, select UEFI Boot Type, and press Esc to return to the
previous screen.
Step 16 Select Exit > Save Changes & Exit, select Yes, and press Enter to restart the server.
BIOS parameter configuration is complete.
----End
There are multiple disk configuration schemes for the HANA database. If SAS HDDs are
used, CacheCade must be configured. If SAS SSDs are used, CacheCade is not required. The
RAID configuration methods for other solutions are the same with only differences in the disk
type, capacity, and quantity. This document uses the 9008 V5 using SAS HDDs as an example
to describe how to configure RAID arrays. For details about how to configure other models of
servers, see 1 Solution Overview.
The disk planning for the 9008 V5 is as follows:
1. Two 600 GB SAS HDDs in slots 0 and 1 are configured as RAID 1 for installing the OS.
2. Two 800 GB SSDs are configured as RAID 10 to function as the HANA database
CacheCade.
3. Other disks are configured as RAID 5 or RAID 50 for the HANA database.
Step 1 Power on the server. When the screen shown in the following figure is displayed, press F11 to
enter the BIOS setup screen.
Step 2 Enter the BIOS password in the displayed dialog box. The default BIOS password is
Admin@9000.
Step 3 On the BIOS screen, select Device Management and press Enter.
Step 4 On the Device Manager page, select the LSI SAS3108 controller to be operated, and press
Enter.
Step 7 Select Clear Configuration to clear the previously configured RAID settings. For a new
environment, skip Step 8 to Step 14.
Step 8 Select Confirm and press Enter. When Disabled changes to Enabled, select Yes.
Step 9 If the operation is successful, press Esc to return to the previous screen.
Step 10 Select Manage Foreign Configuration to clear external configuration. If this option is not
displayed, skip Step 11 to Step 14.
Step 12 Select Confirm and press Enter. When Disabled changes to Enabled, select Yes.
Step 13 If the operation is successful, press Esc to return to the previous screen.
Step 17 Select the RAID level desired (RAID1 in this example) and press Enter.
Step 19 Select the disks to be added and press Enter. (In this example, select two 600 GB SAS
HDDs.)
Step 21 If the operation is successful, press Esc to return to the previous screen.
Step 24 Select Write Policy and press Enter. In the displayed list, select Write Back and press
Enter.
Step 26 Select Confirm and press Enter. When Disabled changes to Enabled, select Yes.
Step 27 If the operation is successful, press Esc to return to the previous screen.
Step 28 Repeat Step 15 to Step 27 to create another virtual disk. Set RAID Level to RAID5 and Size
to 9*1.8T. The configuration specifications are as follows.
Step 29 Choose Create CacheCade Virtual Drive and use the remaining two disks to create the SSD
CacheCade virtual disk by repeating Step 15 to Step 27.
Step 30 Choose Main Menu > Virtual Drive Management. On the screen displayed, you can see the
newly created virtual disks.
Step 35 Select Confirm and press Enter. When Disabled changes to Enabled, select Yes.
Step 36 If the operation is successful, press Esc to return to the previous screen.
Step 37 Press Esc to return to the Main Menu screen. Virtual disk information is displayed.
Step 38 Ensure that the configuration is successful. Press Esc to go back to the home screen and
choose Setup Utility.
Step 39 Press the up or down arrow key to select Exit. Select Save Changes & Exit and press Enter.
On the screen displayed, Select Yes to restart the server.
----End
7 Installing the OS
Step 1 Mount the OS ISO file to the virtual DVD drive. On the KVM screen, click on the
toolbar, select Image File, select an image file to be mounted, and click Connect.
Step 2 Restart the server. During the startup, press F11 as prompted. In the displayed dialog box,
enter the password (default password: Admin@9000).
Step 5 In the initial installation window, select Installation and press Enter.
Step 7 Select Skip Registration, click OK in the displayed dialog box, and click Next.
Step 8 Select SUSE Linux Enterprise Server for SAP Applications and click Next.
Step 9 Retain the default settings and click Next if you do not install other software.
For initial installation, click Add. For OS reinstallation, click Delete to delete existing
partitions one by one.
Step 12 Select Custom Size, set Size to 1 GiB, and click Next.
Step 16 Select Maximum Size under New Partition Size and click Next.
Step 18 Choose Do not format partition, set File system ID to 0x8E Linux LVM, and click Finish.
Step 19 In the System View area on the left, select Volume Management, click Add, and select
Volume Group.
Step 20 Enter a name (for example, vg_os) in Volume Group Name, select /dev/sda2 from Available
Physical Volumes on the left, click Add, and click Finish.
Step 21 In the System View area on the left, select the created vg_os volume group and click Add.
Step 22 Enter swap in the Logical Volume text box and click Next.
Step 23 Select Custom Size, set Size to 20 GiB, and click Next.
Step 27 Enter usr_sap in the Logical Volume text box and click Next.
Step 28 Select Custom Size, set Size to 200.00 GiB, and click Next.
Step 30 Choose Format partition and set File System to Ext4. Choose Mount partition, set Mount
Point to /usr/sap, and click Finish.
Step 32 Enter root in the Logical Volume text box and click Next.
Step 35 Choose Format partition and set File System to Ext4. Choose Mount partition, set Mount
Point to /, and click Finish.
Step 36 Repeat Step 19 to Step 35 to create /dev/sdb. During partition creation, set Role to Data and
ISV Applications and click Next.
For details about the size of the /dev/sdb partition, see 1 Solution Overview. The sizes of the
partitions used in this step are as follows:
No. Partition File Mount Point Description
Size System
2 1 TB xfs /hana/log -
Step 40 Set a password for the root user and click Next.
The password must contain uppercase letters, lowercase letters, digits, and special characters,
for example, Huawei_123.
Step 43 In the Firewall and SSH area, click disable to disable the firewall. Click Install.
----End
If you need to uninstall the existing SAP HANA database, perform operations in 9.5 Uninstalling the
Database and then change the host name. Otherwise, uninstalling the database will fail.
Step 1 Run the vim /etc/hostname command to open the hostname file. Enter i to enter the editing
mode. Change the local host name of the server to hw00001.
Step 2 Press Esc and enter :wq to save the configuration and exit.
Step 4 Run the following commands for the configuration to take effect:
/etc/rc.d/boot.local stop
/etc/rc.d/boot.local start
Step 5 Exit and use the changed host name hw00001 to log in.
----End
Step 2 Enter Network in the search box and select Network Settings in the search result.
Step 3 Select the network port (eth2 in this example) in the Connection state, and click Edit. For
details about how to confirm the network port, see the following NOTE.
You can choose System Info > Network on the iBMC Web page to view the network port status, as
shown in the following figure. Use the MAC address displayed on the iBMC and the MAC address
displayed on the YaST2 to confirm the network port to be configured with an IP address.
Step 4 Set IP Address to 192.168.2.200 and Subnet Mask to 255.255.0.0 according to the plan. Set
the IP address based on site requirements. Click Next and OK in sequence.
Step 5 Run the ifconfig eth2 command and press Enter to check whether the IP address is set
successfully. If the command output is similar to the information shown in the following
figure, the IP address is set successfully.
Step 6 Run the rcSuSEfirewall2 stop command to disable the firewall. If the firewall is not disabled
during the OS installation, click disable next to Firewall will be enabled under Firewall and
SSH. If the firewall is not disabled, the network connection using tools such as Xshell may be
abnormal.
Step 7 Use the Xshell tool to connect to the OS and check whether the network configuration is
successful.
1. Double-click the Xshell icon (download and install the Xshell software in advance),
enter ssh 192.168.2.200, and press Enter.
2. In the dialog box shown in the preceding figure, choose Accept and Save. In the SSH User
Name dialog box, enter the user name for logging in to the OS, for example, root.
4. Enter the login password. The password is the one set for the root user during the OS
installation.
Step 8 Log in to the server as the root user, run yast2, enter Network in the search box, and choose
Network Settings.
Step 8 to Step 16 are performed to configure the bond network port for connecting to the service
network. If you do not need to configure the bond network port, skip these steps.
Step 10 Select No Link and IP Setup (Bonding Slaves) and click Next.
Step 11 Repeat Step 8 to Step 10 to configure the second 10GE network port.
Step 13 Select Bond from the Device Type drop-down list box and click Next.
Step 14 Select Statically Assigned IP Address, and enter the planned IP address, subnet mask, and
host name.
Step 15 Click the Bond Slaves tab, select the two network ports (one from each NIC) to be bonded. In
Bond Driver Options, select mode=2 (or mode=balance-xor), and click Next.
Step 16 The bond0 network port is displayed on the Overview tab page. Repeat the preceding steps to
configure other bond network ports. After the configuration is complete, click OK to save the
settings and make them take effect.
----End
l This section describes how to activate the Linux OS and how to install a patch package and update
the operating system online. If the customer network cannot connect to the Internet directly or
through the proxy server, skip this section.
l Huawei is responsible for OS installation and patch package installation and upgrade during project
implementation. After Huawei completes project delivery (after the system officially goes live on
the customer site), the customer is responsible for system upgrade, security update, and patch
package installation. The customer needs to add software components and modify the OS
configuration according to SAP notes to ensure system security and stability.
Step 2 Use YaST to update the kernel (or download the kernel patch package to manually update the
kernel).
Step 3 Check the GRUB file and the boot sector (menu.lst). If command lines have been configured
in the GRUB file before the kernel update, check the GRUB configuration again after the
kernel update takes effect upon restart.
----End
Step 1 Online upgrade requires the Linux system to access the Internet directly or through a proxy
server. To configure the proxy server, set PROXY_ENABLED to yes and configure the host
IP address and port number of the proxy server.
hw00001:~ # cd /etc/sysconfig/
hw00001:/etc/sysconfig # vi proxy
PROXY_ENABLED="yes"
HTTP_PROXY="http://<Proxy_server_IP>:<Proxy_Service_port>"
HTTPS_PROXY="http://<Proxy_server_IP>:<Proxy_service_port>"
FTP_PROXY="http://<Proxy_server_IP>:<Proxy_service_port>"
Step 2 Run the yast command as the root user. Choose Software > Online Update. Then select Yes
and press Enter on the screen displayed.
Step 3 Use the official SUSE website account and password that have been activated to register with
the current Linux server. Then click Next.
For details about how to activate the official SUSE website account, see 10.1.2 Activating SLES
Subscriptions.
Step 4 On the Extension and Module Selection screen, select Next and press Enter.
Step 5 On the Available Extensions and Modules screen, select Accept and press Enter.
Step 6 The system automatically downloads the patch packages for update. On the screen shown in
Figure 7-1, select OK and press Enter. On the screen shown in Figure 7-2, select Accept
and press Enter.
Step 7 After certain patch packages are installed, you need to restart the system for the patches to
take effect. Select Continue and press Enter on the confirmation screen. Then select Accept
and press Enter.
Step 8 The system starts downloading and installing the patch packages. When the download is
complete, select Finish and press Enter.
Step 11 Exit YaST. The configuration takes effect after the system is restarted.
----End
For two-node HA or cluster networking, see the corresponding installation guide to modify the hosts
file.
Edit the hosts file as follows to enable the HANA server host name and IP address parsing:
Step 2 Press i to make the hosts file editable and add the following information to the file.
In the following information, the host names and IP addresses are examples only. Change them based on
the actual situation. The IP addresses must be the service port IP addresses.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.5.2.10 hw00001 hw00001
Step 3 Press Esc to switch the vi editor to the CLI mode. Press the colon (:) key to switch to the
bottom line mode. Enter wq and press Enter to save the configuration and exit.
----End
If the online upgrade has been performed in the preceding sections, you do not need to upgrade the
kernel and other patch packages separately.
Upgrade the kernel package and required patch packages (see Software Planning (SLES)). This section
uses the kernel and patch packages of SLES12 SP2 as examples to describe the upgrade procedure. For
SLES12 SP3, see Installing OS Patch Packages and Running the OS Configuration Script and skip
Installing the Kernel and Other Patch Packages to Checking the Configurations.
Step 1 Use the XFTP tool to copy the kernel and other gcc patch packages to the server.
Step 2 Use the Xshell tool to connect to the server and log in to the server as the root user.
Step 3 Run the cd command to switch the path. For example: cd /home/kernel/ or cd /home/GCC).
Step 4 Run the rpm -ivh kernel-default-4.4.74-92.35.1.x86_64.rpm command to install the kernel
patch package. See the following information:
Step 5 Run the cd/home/GCC command to switch to the directory where other packages are stored,
and run the rpm -Uvh <patch> command to perform the upgrade. See the following
information:
dracut: resume=/dev/mapper/vg_os-swap
dracut: root=/dev/mapper/vg_os-root rootfstype=ext4
rootflags=rw,relatime,data=ordered
dracut: *** Creating image file '/boot/initrd-4.4.21-69-default' ***
dracut: *** Creating initramfs image file '/boot/initrd-4.4.21-69-default' done
***
Step 6 After the installation is complete, restart the system for patch package installation to take
effect.
----End
----End
Step 3 Press i to enter the editing mode, move the cursor to the end of the file and add the following
content:
cpupower set -b 0
Step 4 Press Esc, enter :wq, and press Enter to save the settings and exit.
Step 5 Run the vim /usr/lib/tuned/sap-hana/tuned.conf command, press i to enter the editing mode,
change the value of force_latency to 70, and change the value of script, as shown in the
following:
[script]
script = /usr/lib/tuned/sap-hana/script.sh
Step 6 Press Esc, enter :wq, and press Enter to save the settings and exit.
Step 7 Run the mkdir /etc/tuned/sap-hana command to create a directory, and then run the
cp /usr/lib/tuned/sap-hana/tuned.conf /etc/tuned/sap-hana/tuned.conf command to copy
the tuned.conf file.
hw00001:~ # mkdir /etc/tuned/sap-hana
hw00001:~ # cp /usr/lib/tuned/sap-hana/tuned.conf /etc/tuned/sap-hana/tuned.conf
Step 8 Run the mkdir /etc/systemd/logind.conf.d command to create a directory, and run the
vim /etc/systemd/logind.conf.d/sap.conf command to create the sap.conf file.
hw00001:~ # mkdir /etc/systemd/logind.conf.d
hw00001:~ # vim /etc/systemd/logind.conf.d/sap.conf
Step 9 Press i to enter the editing mode and add the content shown as below. Press Esc, enter :wq,
and press Enter to save the settings and exit.
[Login]
UserTasksMax=infinity
----End
The sap-hana configuration file of the tuned service provided by SLES 12 for SAP includes various
hardware configurations, including power regulator and efficiency mode. The configuration in this file
will overwrite the OS configuration.
Step 2 Run the vi /etc/default/grub command to open the grub file. Add four parameters between
GRUB_CMDLINE_LINUX_DEFAULT and showopts.
transparent_hugepage=never numa_balancing=disable intel_idle.max_cstate=1
processor.max_cstate=1
Step 3 On the CLI, press Esc, type :wq, and press Enter to save the settings and exit.
----End
This chapter applies only to SLES 12 SP2/SLES 12 SP3/SLES 12 SP4/SLES 15. For other OS versions,
skip this chapter.
Step 2 Disable the automatic startup of the fstrim.timer service upon system startup.
hw00001:~ # systemctl disable fstrim.timer
Step 4 Disable the automatic startup of the fstrim.service service upon system startup.
hw00001:~ # systemctl disable fstrim.service
Step 5 Run the following command to check the status of the fstrim.timer service, and ensure that
the Active is inactive (dead).
hw00001:~ # systemctl status fstrim.timer
Step 6 Run the following command to check the status of the fstrim.service service, and ensure that
the Active is inactive (dead).
hw00001:~ # systemctl status fstrim.service
Step 7 Run the following command to check the automatic startup of the fstrim.timer service upon
system startup, and ensure that the Loaded is disabled.
hw00001:~ # systemctl list-unit-files | grep fstrim.timer
Step 8 Run the following command to check the automatic startup of the fstrim.service service upon
system startup, and ensure that the Loaded is static.
hw00001:~ # systemctl list-unit-files | grep fstrim.service
----End
Step 3 Run the cat /proc/cpuinfo |grep MHz command to check that the CPU working frequency is
normal.
hw00001:~ # cat /proc/cpuinfo |grep MHz
----End
Step 1 Mount the OS ISO file to the virtual DVD drive. On the KVM screen, click on the
toolbar, select Image File, select the SLE-15-Installer-DVD-x86_64-GM-DVD1.iso image
file to be mounted, and click Connect.
Step 2 Restart the server. During the startup, press F11 as prompted. In the displayed dialog box,
enter the password (default password: Admin@9000).
Step 5 In the initial installation window, select Installation and press Enter.
Step 6 Select SUSE Linux Enterprise Server for Sap Applications 15 and click Next.
Step 8 Select Skip Registration, click OK in the displayed dialog box, and click Next.
Step 9 Select I would like to Install an additional Add On Product, and select DVD.
Step 12 Select modules based on site requirements and click Next. Available modules include:
l Basesystem-Module 15-0
l Desktop-Applications-Module 15-0
l Development-Tools-Module 15-0
l Legacy-Module 15-0
l SAP-Applications-Module 15-0
l SLE-15-SAP 15-0
l SLEHA15 15-0
l Server-Applications-Module 15-0
Step 15 Deselect Launch SAP product installation wizard right after operating system is
installed and click Next.
Step 16 Select Start with Current Proposal from the Expert Partitioner drop-down list box and
press Enter.
For initial installation, click Add. For OS reinstallation, click Delete to delete existing
partitions one by one.
Step 18 Select Custom Size, set Size to 1 GiB, and click Next.
Step 22 Select Maximum Size under New Partition Size and click Next.
Step 24 Choose Do not format partition, set File system ID to Linux LVM, and click Next.
Step 25 In the System View area on the left, select Volume Management, click Add, and select
Volume Group.
Step 26 Enter a name (for example, vg_os) in Volume Group Name, select /dev/sda2 from Available
Devices on the left, click Add, and click Next.
Step 27 In the System View area on the left, select the created vg_os volume group and click Add.
Step 28 Enter swap in the Logical Volume text box and click Next.
Step 29 Select Custom Size, set Size to 20 GiB, and click Next.
Step 33 Enter usr_sap in the Logical Volume text box and click Next.
Step 34 Select Custom Size, set Size to 200.00 GiB, and click Next.
Step 36 Choose Format partition and set File System to Ext4. Choose Mount partition, set Mount
Point to /usr/sap, and click Finish.
Step 38 Enter root in the Logical Volume text box and click Next.
Step 41 Choose Format partition and set File System to Ext4. Choose Mount partition, set Mount
Point to /, and click Finish.
Step 42 Repeat Step 19 to Step 35 to create /dev/sdb. During partition creation, set Role to Data and
ISV Applications and click Next.
For details about the size of the /dev/sdb partition, see 1 Solution Overview. The sizes of the
partitions used in this step are as follows:
Step 46 Set a password for the root user and click Next.
The password must contain uppercase letters, lowercase letters, digits, and special characters,
for example, Huawei_123.
Step 49 In the Firewall and SSH area, click disable to disable the firewall. Click Install.
----End
If you need to uninstall the existing SAP HANA database, perform operations in 9.5 Uninstalling the
Database and then change the host name. Otherwise, uninstalling the database will fail.
Step 1 Run the vim /etc/hostname command to open the hostname file. Enter i to enter the editing
mode. Change the local host name of the server to hw00001.
Step 2 Press Esc and type :wq and press Enter to save the configuration and exit.
Step 4 Exit and use the changed host name hw00001 to log in.
----End
Step 1 Click Activites in the upper left corner and enter enterminal in the search box.
Step 4 On the page that is displayed, select the first four items in the left pane. Then enter ifconfig in
the search box and click Search. In the right pane, the search results are displayed, select the
net-tools-deprecated installation package and click Accept to complete the installation.
----End
Step 2 Enter Network in the search box and select Network Settings in the search result.
Step 3 Select the network port (eth2 in this example) in the Connection state, and click Edit. For
details about how to confirm the network port, see the following NOTE.
You can choose System Info > Network on the iBMC Web page to view the network port status, as
shown in the following figure. Use the MAC address displayed on the iBMC and the MAC address
displayed on the YaST2 to confirm the network port to be configured with an IP address.
Step 4 Set IP Address to 192.168.2.200 and Subnet Mask to 255.255.0.0 according to the plan. Set
the IP address based on site requirements. Click Next and OK in sequence.
Step 5 Run the ifconfig eth2 command and press Enter to check whether the IP address is set
successfully. If the command output is similar to the information shown in the following
figure, the IP address is set successfully.
Step 6 Use the Xshell tool to connect to the OS and check whether the network configuration is
successful.
1. Double-click the Xshell icon (download and install the Xshell software in advance),
enter ssh 192.168.2.200, and press Enter.
2. In the dialog box shown in the preceding figure, choose Accept and Save. In the SSH User
Name dialog box, enter the user name for logging in to the OS, for example, root.
4. Enter the login password. The password is the one set for the root user during the OS
installation.
Step 7 Log in to the server as the root user, run yast2, enter Network in the search box, and choose
Network Settings.
l Step 8 to Step 16 are performed to configure the bond network port for connecting to the service
network. If you do not need to configure the bond network port, skip these steps.
Step 9 Select No Link and IP Setup (Bonding Slaves) and click Next.
Step 10 Repeat Step 8 to Step 10 to configure the second 10GE network port.
Step 12 Select Bond from the Device Type drop-down list box and click Next.
Step 13 Select Statically Assigned IP Address, and enter the planned IP address, subnet mask, and
host name.
Step 14 Click the Bond Slaves tab, select the two network ports (one from each NIC) to be bonded. In
Bond Driver Options, select mode=2 (or mode=balance-xor), and click Next.
Step 15 The bond0 network port is displayed on the Overview tab page. Repeat the preceding steps to
configure other bond network ports. After the configuration is complete, click OK to save the
settings and make them take effect.
----End
For two-node HA or cluster networking, see the corresponding installation guide to modify the hosts
file.
Edit the hosts file as follows to enable the HANA server host name and IP address parsing:
Step 2 Press i to make the hosts file editable and add the following information to the file.
In the following information, the host names and IP addresses are examples only. Change them based on
the actual situation. The IP addresses must be the service port IP addresses.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.5.2.10 hw00001 hw00001
Step 3 Press Esc to switch the vi editor to the CLI mode. Press the colon (:) key to switch to the
bottom line mode. Enter wq and press Enter to save the configuration and exit.
----End
Upgrade the kernel package and required patch packages (see Software Planning (SLES)).
Step 1 Use the XFTP tool to copy the kernel and other patch packages to the server.
Step 2 Use the Xshell tool to connect to the server and log in to the server as the root user.
Step 3 Run the cd command to switch the path. For example: cd /home/ospatch.
Step 5 Run the rpm -Uvh <patch> command to perform the upgrade. See the following
information:
hw00001:/home/ospatch # rpm -Uvh SAPHanaSR*
Preparing... ################################# [100%]
Updating / installing...
1:SAPHanaSR-doc-0.152.22-4.3.2 ################################# [ 50%]
2:SAPHanaSR-0.152.22-4.3.2 ################################# [100%]
Updating / installing...
1:SAPHanaSR-0.152.22-4.3.2 ################################# [100%]
Step 6 After the installation is complete, restart the system for patch package installation to take
effect.
----End
Step 2 Run the chmod +x suse15_hana_host.sh command to grant the execute permission on the
OS configuration script.
Step 3 Run the ./ suse15_hana_host.sh command to complete the OS configuration and restart the
OS for the configuration to take effect.
----End
Step 3 Press i to enter the editing mode, move the cursor to the end of the file and add the following
content:
cpupower set -b 0
Step 4 Press Esc, enter :wq, and press Enter to save the settings and exit.
----End
The sap-hana configuration file of the tuned service provided by SLES 15 for SAP includes various
hardware configurations, including power regulator and efficiency mode. The configuration in this file
will overwrite the OS configuration.
Step 2 Run the vi /etc/default/grub command to open the grub file. Add four parameters between
GRUB_CMDLINE_LINUX_DEFAULT and showopts.
Step 3 On the CLI, press Esc, type :wq, and press Enter to save the settings and exit.
Step 4 Run the grub2-mkconfig -o /boot/grub2/grub.cfg command to generate the grub
configuration file.
This chapter applies only to SLES 12 SP2/SLES 12 SP3/SLES 12 SP4/SLES 15. For other OS versions,
skip this chapter.
Step 2 Disable the automatic startup of the fstrim.timer service upon system startup.
hw00001:~ # systemctl disable fstrim.timer
Step 4 Disable the automatic startup of the fstrim.service service upon system startup.
hw00001:~ # systemctl disable fstrim.service
Step 5 Run the following command to check the status of the fstrim.timer service, and ensure that
the Active is inactive (dead).
hw00001:~ # systemctl status fstrim.timer
Step 6 Run the following command to check the status of the fstrim.service service, and ensure that
the Active is inactive (dead).
hw00001:~ # systemctl status fstrim.service
Step 7 Run the following command to check the automatic startup of the fstrim.timer service upon
system startup, and ensure that the Loaded is disabled.
hw00001:~ # systemctl list-unit-files | grep fstrim.timer
Step 8 Run the following command to check the automatic startup of the fstrim.service service upon
system startup, and ensure that the Loaded is static.
hw00001:~ # systemctl list-unit-files | grep fstrim.service
----End
Step 4 Run the cat /proc/cpuinfo |grep MHz command to check that the CPU working frequency is
normal.
hw00001:~ # cat /proc/cpuinfo |grep MHz
Step 5 Run the uname -r command to check whether the kernel version is the upgrade target
version.
HW00001:~ # uname -r
4.12.14-25.25-default
----End
Step 1 Mount the OS ISO file to the virtual DVD drive. On the KVM screen, click on the
toolbar, select Image File, select an image file to be mounted, and click Connect.
Step 2 Restart the server. During the startup, press F11 as prompted. In the displayed dialog box,
enter the password (default password: Admin@9000).
Step 5 On the initial installation screen, select Install Red Hat Enterprise Linux 7.3 and press
Enter.
Step 6 Set the language to English (United States) and click Continue.
Step 8 Set the date and time based on site requirements, for example, Shanghai. Click Done.
Step 10 Perform the following settings and click Done to save the configuration:
1. In the Base Environment pane, select Infrastructure Server.
2. In the Add-Ons for Selected Environment pane, select the following options:
– Large Systems Performance
– Network File System Client
– Performance Tools
– Compatibility Libraries
Step 12 In the Local Standard Disks pane, select sda. In the Other Storage Options pane, select I
will configure partitioning. Click Done in the upper left corner.
If other partitions exist on the disk, perform the following steps to delete the partitions and then create
the /boot/ partition:
1. Select an existing partition and click –.
1. In the partitioning scheme area, select Standard Partition from the drop-down list
box, and click +.
2. In the Add A NEW MOUNT POINT dialog box, set Mount Point to /boot and
Desired Capacity to 1 GiB, and click Add mount point.
3. Select the created /boot partition, set Mount Point to /boot, Desired Capacity to 1024
MiB, Device Type to Standard Partition, and File System to ext4. Click Update
Settings to update the configuration.
2. Select the created /boot/efi partition, set Mount Point to /boot/efi, Desired Capacity to
1024 MiB, Device Type to Standard Partition, and File System to EFI System
Partition.
2. Select the created swap partition, set Desired Capacity to 20 GiB, Device Type to
LVM, and File System to swap, and Select Create a new volume group in the Volume
Group area.
3. In the CONFIGURE VOLUME GROUP dialog box, set Name to vg_os, select LSI
MR9361-8i, and click Save.
4. Check the configuration of the swap partition and click Update Settings.
2. Select the /usr/sap partition. Set Device Type to LVM, Volume Group to vg_os, and
File System to ext4. Click Update Settings.
2. Select the created / partition. Set Desired Capacity to the remaining size of sda, Device
Type to LVM, Volume Group to vg_os, and File System to ext4. Click Update
Settings.
Step 19 On the INSTALLATION SUMMARY page that is displayed, click NETWORK & HOST
NAME.
Step 20 In the Host name text box in the lower left corner, enter the host name, for example,
hw00001. Click Apply.
The configured host name is displayed in the lower right corner. Click Done in the upper left
corner to complete the configuration.
Step 21 On the INSTALLATION SUMMARY page that is displayed, click Begin Installation to
start the installation.
Step 22 Click ROOT PASSWORD and set the root user password. Click Done.
----End
Perform the operations described in this section when the Red Hat operating system is installed and the
log, data, and shared volumes use the local disk scheme.
Step 3 Run the following commands to create data, shared, and log LVs: For details about volume
sizes, see 1 Solution Overview. In this example, the log LV is 1 TB, the data LV is 4.5 TB,
and the shared LV is 3 TB.
#mkfs.xfs /dev/mapper/vg_hana-lv_data
#mkfs.xfs /dev/mapper/vg_hana-lv_log
#mkfs.xfs /dev/mapper/vg_hana-lv_shared
Step 6 Run the following commands to mount the LVs to the new folder:
# mount -o noatime,nodiratime /dev/mapper/vg_hana-lv_log /hana/log
# mount -o noatime,nodiratime /dev/mapper/vg_hana-lv_data /hana/data
# mount -o noatime,nodiratime /dev/mapper/vg_hana-lv_shared /hana/shared
Step 7 Run the vim /etc/fstab command, press i to enter the editing mode, and add the following
information: Press Esc, type :wq, and press Enter to save the settings and exit.
If an SSD disk is used as the log volume, you do not need to mount the log volume. Set this parameter
based on the site requirements. The configuration described in this section is for reference only.
----End
If you need to uninstall the existing SAP HANA database, perform operations in 9.5 Uninstalling the
Database and then change the host name. Otherwise, uninstalling the database will fail.
Step 1 Run the vim /etc/hostname command to open the hostname file. Enter i to enter the editing
mode. Change the local host name of the server to hw00001.
Step 2 Press Esc and type :wq and press Enter to save the configuration and exit.
Step 4 Run the logout command to exit the system. After the login, the host name is hw00001.
----End
Step 3 Log in to the iBMC and check the MAC address of the network port in the Connection state.
Run the ifconfig command in the system to find the network port corresponding to the MAC
address.
Step 4 Set BOOTPROTO to static, ONBOOT to yes, the IP address to 192.168.2.200, and the
subnet mask to 255.255.255.0.
Step 5 Run the service network restart command for the network configuration to take effect.
[root@hw00001 network-scripts]# service network restart
Restarting network (via systemctl): [ OK ]
Step 6 Run the systemctl stop firewalld and systemctl disable firewalld commands to disable the
firewall so that errors do not occur in subsequent connections through tools such as Xshell.
[root@hw00001 home]# systemctl stop firewalld
[root@hw00001 home]# systemctl disable firewalld
l Steps 7 to 11 are performed to configure the bond network port connected to the service network. If
you do not need to configure the bond network port, skip these steps.
Step 12 Check the configuration information. If the following information is displayed, the
configuration is successful:
[root@hw00001 network-scripts]# nmcli connection show
NAME?????????????????????? UUID????????????????????????????????? TYPE???????????
DEVICE
bond-bond0???????????????? d0d5d0ef-067a-4cdc-87b6-60336b9fcded? bond???????????
bond0
enp4s0f0?????????????????? 42aa6733-4226-458c-bc27-017b1a07d712? 802-3-ethernet?
enp4s0f0
bond-slave-ifcfg-enp4s0f1? 1be67cf4-db38-4ce9-9890-96e79aa4e1af? 802-3-ethernet?
--
bond-slave-ifcfg-enp4s0f2? 55874086-3afe-46e7-9d02-06534ed46fd3? 802-3-ethernet?
--
----End
For two-node HA or cluster networking, see the corresponding installation guide to modify the hosts
file.
Edit the hosts file as follows to enable the HANA server host name and IP address parsing:
Step 2 Press i to make the hosts file editable and add the following information to the file.
In the following information, the host names and IP addresses are examples only. Change them based on
the actual situation. The IP addresses must be the service port IP addresses.
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
10.5.2.10 hw00001 hw00001
Step 3 Press Esc to switch the vi editor to the CLI mode. Press the colon (:) key to switch to the
bottom line mode. Enter wq and press Enter to save the configuration and exit.
----End
This section describes how to activate the Linux OS and how to install a patch package and update the
operating system online. If the customer network cannot connect to the Internet directly or through the
proxy server, skip this section.
OS upgrade and maintenance
Huawei is responsible for OS installation and patch package installation and upgrade during project
implementation. After Huawei completes project delivery (after the system officially goes live on the
customer site), the customer is responsible for system upgrade, security update, and patch package
installation. The customer needs to add software components and modify the OS configuration
according to SAP notes to ensure system security and stability.
Step 1 The customer registers an account with the Red Hat portal and activates the account.
For details about how to activate the official Red Hat website account, see section 1.2 "Registering and
Activating OS Subscriptions" in the Huawei SAP HANA Appliance Single Node and Two Node HA
Maintenance Guide.
Step 2 Run the subscription-manager register --auto-attach+ command to activate the Linux
operating system. During the activation, use the user name and password of the Red Hat
portal.
#subscription-manager register --auto-attach+
Username: <<username>>
Password: <<password>>
Step 3 Run the yum install yum-utils command to install yum repository components.
# yum install yum-utils
Step 6 Run the subscription-manager release –set=7.3 command to set the updated version
number.
#subscription-manager release –set=7.3
Step 8 Run the yum install yum-utils command to install the yum components.
#yum install yum-utils
Step 9 Run the yum -y groupinstall base command to install the basic package.
#yum -y groupinstall base
Step 10 Run the following command to install components required by SAP and Red Hat:
#yum install –y kernel cairo expect krb5-workstation krb5-libs libcanberra-gtk2
libaio libicu libpng12 libssh2 libtool-ltdl ntp ntpdate numactl openssl
PackageKit-gtk3-module rsyslog sudo tcsh xorg-x11-xauth xulrunner gtk2 graphviz
iptraf-ng lm_sensors nfs-utils gcc glibc glibc-devel kernel-devel libstdc++-devel
redhat-rpm-config rpm-build zlib-devel compat-sap-c++-6 compat-sap-c++-5
pacemaker corosync pcs tuned-profiles-sap-hana yum-utils fence-agents-all
resource-agents-sap-hana resource-agents
----End
If the online upgrade has been performed in the preceding sections, you do not need to upgrade the
kernel and other patch packages separately.
Upgrade the kernel package and required patch packages (see 3.6 Software Planning (RHEL)). This
section uses the kernel and patch packages of RHEL 7.3 as examples to describe the upgrade procedure.
For RHEL 7.4, see 7.1.7 Running the OS Configuration Script.
Step 1 Download the following patch packages from the Red Hat official website:
l compat-sap-c++-6-6.3.1-1.el7_3.x86_64.rpm
l dracut-033-502.el7.x86_64.rpm
l dracut-config-generic-033-502.el7.x86_64.rpm
l dracut-config-rescue-033-502.el7.x86_64.rpm
l dracut-network-033-502.el7.x86_64.rpm
l glibc-2.17-196.el7.x86_64.rpm
l glibc-common-2.17-196.el7.x86_64.rpm
l glibc-devel-2.17-196.el7.x86_64.rpm
l glibc-headers-2.17-196.el7.x86_64.rpm
l kernel-3.10.0-693.2.2.el7.x86_64.rpm
l kexec-tools-2.0.14-17.el7.x86_64.rpm
l linux-firmware-20170606-56.gitc990aae.el7.noarch.rpm
l python-linux-procfs-0.4.9-3.el7.noarch.rpm
l python-schedutils-0.4-6.el7.x86_64.rpm
l tuned-2.8.0-5.el7.noarch.rpm
l tuned-profiles-sap-hana-2.8.0-5.el7.noarch.rpm
l tuned-utils-2.8.0-5.el7.noarch.rpm
Step 2 Use the XFTP tool to copy the kernel and other patch packages to the server.
Step 3 Enter the path of the file to be uploaded. Run the rpm -Uvh <patches> command to upgrade
the patch package.
Step 4 Run the rpm -ivh <kernel> command to upgrade the kernel.
----End
----End
The tuned service configuration file sap-hana provided by Red Hat Enterprise Linux 7 for SAP HANA
includes many of the following settings and some additional settings. Therefore, the tuned file must be
activated on all the systems running SAP HANA.
Step 1 Run the rpm -qa | grep tuned-profiles-sap-hana command to check whether the tuned
service is installed on the OS. If the tuned service is not installed, run the yum install tuned-
profiles-sap-hana command to install it.
[root@hw00001 ~]# rpm -qa | grep tuned-profiles-sap-hana
tuned-profiles-sap-hana-2.8.0-5.el7_4.2.noarch
[root@hw00001 ~]#
Step 2 Enable the tuned service and automatically configure the sap-hana file.
# systemctl start tuned
# systemctl enable tuned
# tuned-adm profile sap-hana
----End
Step 2 Run the vim /usr/lib/tuned/sap-hana/tuned.conf command and press i to enter the editing
mode. Ensure that the value of force_latency is set to 70.
Step 3 Press Esc, type :wq, and press Enter to save the settings and exit.
Step 4 Run the mkdir /etc/tuned/sap-hana command to create a directory, and then run the
cp /usr/lib/tuned/sap-hana/tuned /etc/tuned/sap-hana/tuned.conf command to copy the
tuned.conf file.
hw00001:~ # mkdir /etc/tuned/sap-hana
hw00001:~ # cp /usr/lib/tuned/sap-hana/tuned.conf /etc/tuned/sap-hana/tuned.conf
Step 5 Run the vim /etc/sysctl.d/sap_hana.conf command, press i to enter the editing mode, and add
kernel.numa_balancing = 0 to the file. If the file already contains kernel.numa_balancing
= 0, skip this step.
Step 6 Press Esc, type :wq, and press Enter to save the settings and exit.
Step 8 Run the systemctl stop numad and systemctl disable numad commands to disable the
numad service.
Step 10 Run the echo 0 > /sys/kernel/mm/ksm/run command to stop the KSM immediately.
Step 11 Run the vim /etc/init.d/boot.local command to enter the editing mode of the boot.local file or
create the file if it does not exist. Add the following statements to the file, save the changes
and exit:
cpupower set -b 0
Step 12 Run the chmod +x /etc/init.d/boot.local command to grant the execute permission on the
boot.local file.
Step 13 Run the vim /etc/sysconfig/selinux command, press i to enter the editing mode, and change
the value of SELINUX to disabled. Change the value of SELINUX to disabled in /etc/
selinux/config in the same way.
Step 14 Press Esc, type :wq, and press Enter to save the settings and exit.
----End
Step 3 On the CLI, press Esc, enter :wq, and press Enter to save the settings and exit.
Step 4 Run the grub2-mkconfig -o /boot/efi/EFI/redhat/grub.cfg command to generate the grub
configuration file.
----End
In the displayed information, never indicates that the transparent huge page has been
disabled.
HW00001:~ # cat /sys/kernel/mm/transparent_hugepage/enabled
always madvise [never]
Step 4 Run the cat /proc/cpuinfo |grep MHz command to check that the CPU working frequency is
normal.
hw00001:~ # cat /proc/cpuinfo |grep MHz
Step 5 Run the cat /etc/rc.d/boot.local command to check whether the cpupower frequency-set -g
performance is configured successfully.
hw00001:~ # cat /etc/rc.d/boot.local
cpupower frequency-set -g performance
Step 7 Run the cat /etc/init.d/boot.local command to check whether the cpupower set -b 0 and echo
0 > /sys/kernel/mm/ksm/run are configured successfully.
hw00001:~ # cat /etc/init.d/boot.local
cpupower set -b 0
echo 0 > /sys/kernel/mm/ksm/run
Step 8 Run the cat /etc/selinux/config and cat /etc/sysconfig/selinux commands to check whether
the SELINUX=disabled is configured successfully.
hw00001:~ # cat /etc/selinux/config
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are
protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
Step 9 Run the uname -r command to check whether the kernel version is the upgrade target
version.
HW00001:~ # uname -r
3.10.0-957.10.1.el7.x86_64
----End
Storage devices are classified into built-in hard disks and external storage devices. The
multipathing service must be configured when external storage devices are used. You need to
configure external storage devices only when a server (such as CH121 V5 and CH242 V5)
does not have local storage.
8.1 Preparing for the Configuration
8.2 Configuring OceanStor 5500 V3
8.3 Configuring the Multipathing Service
Step 2 Run the fdisk -l /dev/sd* command to check the status of sda and sdb.
----End
This section uses the external storage of CH242 V5 (30x1.2T SAS HDD RAID5 from OceanStor 5500
V3) as an example to describe how to configure external storage.
Step 1 Enter https://ipaddress:8088 in the address box of your browser, in which ipaddress is the IP
address of the management network port on the storage system controller. Change ipaddress
to the actual IP address.
Step 2 Enter a user name and password to log in to OceanStor 5500 V3. (The default user name is
admin and the default password is Admin@storage.)
Step 3 In the navigation tree on the right, choose Provisioning. The resource configuration page is
displayed.
Step 4 Before the configuration, the storage resources allocated are 0. Click Create Disk Domain to
create a disk domain.
Step 5 In the displayed dialog box, enter the disk domain name and click Manually select and select
a disk.
Step 6 In the left pane of the Select Disk dialog box that is displayed, select thirty 1.2 TB SAS disks
(the actual available capacity of each 1.2 TB SAS disk is less than 1.2 TB), and click to
add them to Selected Disks on the right. The number of selected disks is displayed in the
lower part. After confirming that the information is correct, click OK.
Step 7 In the Create Disk Domain dialog box, check information about the selected disks, including
disk type, quantity, and hot spare policy (default value: High). After confirming that the
information is correct, click OK.
Step 8 In the displayed dialog box, click OK to create and initialize a disk domain.
Step 9 To view disk domain initiation status, choose Huawei.Storage > Provisioning > Disk
Domain. Select the created disk domain and click Properties. View the formatting progress
in the Format area of the dialog box that is displayed.
Step 10 After the initialization is complete, choose Huawei.Storage > Provisioning and click Create
Storage Pool to create a log storage pool.
Step 11 In the displayed dialog box, enter the storage pool name, set Disk Domain to the name of the
created disk domain, and set RAID Policy to RAID 5 and 13D+1P. (The capacity of the three
volumes is 25 TB. The size of the created storage pools must be greater than 25 TB. The 13D
+1P option meets this requirement.) In Capacity, set the capacity unit to GB, and enter 1050.
After confirming that the information is correct, click OK.
In this example, create three storage pools, namely, 1 TB log storage pool, 18 TB data storage pool, and
6 TB shared storage pool based on the plan. Ensure that the actual capacity of each created storage pool
is a little larger than the planned capacity so that the capacity of LVs to be created on the OS side can
meet the capacity requirements.
Step 13 Repeat the preceding steps to create the data and shared storage pools.
Step 15 In the Create LUN dialog box that is displayed, enter a name, for example, LUN_log. Set
Owning Storage Pool to the name of the created log storage pool. In Capacity, select Use all
of the available capacity of the owing storage pool, and click Advanced. The advanced
settings are displayed.
Step 16 On the Properties tab page, set the parameters as shown in the following figure. After the
configuration is complete, click OK.
Step 17 Return to the Create LUN dialog box and click OK.
Step 19 Repeat the preceding steps to create a data LUN. The advanced configuration of the data LUN
is as follows:
Step 20 Repeat the preceding steps to create a shared LUN. The advanced configuration of the shared
LUN is as follows:
Step 21 Choose Huawei.Storage > Provisioning and click Create LUN Group to create a LUN
group.
Step 22 On the Create LUN Group page that is displayed, enter a LUN group name. Select the three
new LUNs and click to add the LUNs to the right pane. After confirming that all the
LUN information is correct, click OK.
Step 25 In the displayed dialog box, enter a host name, set OS to Linux, and click Next.
Step 26 Select FC from the Initiator Type drop-down list box, select four online FC links, click
, and click Next. (To ensure that the FC link status is online, check that the server
connected to the storage is powered on.)
Step 27 Check that the four FC links are normal and click Finish.
Step 28 In the Danger dialog box, select I have read and… and click Next.
Select I have read and… and click OK. The host is created.
Click Close.
Step 29 Choose Huawei.Storage > Provisioning > Host, select the created host. On the Initiator tab
page, select an FC link and click Modify. In the displayed dialog box, select Enable ALUA
and click OK. In the Success dialog box that is displayed, click OK.
Repeat the preceding steps to make the same settings for the other FC links.
Step 30 Choose Huawei.Storage > Provisioning and click Create Host Group.
Step 31 In the Create Host Group dialog box that is displayed, enter a host group name, select the
created host, click to add it to the right pane, and click OK.
Step 33 Choose Huawei.Storage > Provisioning and click Create Mapping View to create a
mapping.
Step 34 In the Create Mapping View dialog box, enter a mapping view name and click ... in LUN
Group. In the displayed dialog box, select the created LUN group and click OK.
Step 35 Repeat the preceding steps to add Host Group. On the Create Mapping View page, click
OK. In the Danger dialog box that is displayed, select I have read and … and click OK.
----End
Step 2 Create the multipath.conf file in /etc, and add the following information to the end of the
file:
You need to manually create the multipath.conf file because it is not automatically generated after the
SAP HAHA installation.
HW00001:~ # vi /etc/multipath.conf
devices {
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy group_by_prio
failback immediate
path_selector "round-robin 0"
path_checker tur
prio alua
fast_io_fail_tmo 5
detect_prio no
dev_loss_tmo 30
retain_attached_hw_handler "no"
hardware_handler 0
}
}
Step 3 Run the systemctl restart multipathd.service command to restart the multipathing service.
HW00001:~ # systemctl restart multipathd.service
If an error message similar to the figure below is displayed after you run the multipath command,
comment out the getuid_callout line in the multipath.conf file.
Step 7 Add the WWIDs to the multipath.conf file, and add the WWID of the disk where the
operating system is installed to the blacklist of multipath.conf.
To check the local WWNs of the LUNs on the storage side, choose Huawei.Storage > Provisioning >
LUN and check LUN properties. The WWIDs to be added to the multipath.conf file are those next to
scsi in /dev/disk/by-id/.
The following is an example for viewing the WWIDs of local disks:
After the ll /dev/disk/by-id/ command is run, the following information is displayed: Search for disks
with partitions. The preceding figure shows that only the sda disk has partitions. Therefore, sda is a
local disk. Add the WWID of sda to the blacklist. The preceding figure is for reference only. Configure
the WWID based on the site requirements.
HW00001:~ # vi /etc/multipath.conf
blacklist {
wwid 36100008858def07421c2040b1a79a556
}
multipaths {
multipath {
wwid 3648fd8e100e4035d0b6f7d3b00000000
alias hana_log
}
multipath {
wwid 3648fd8e100e4035d0b70065600000002
alias hana_data
}
multipath {
wwid 3648fd8e100e4035d0b7053ce00000004
alias hana_shared
}
}
devices {
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy group_by_prio
failback immediate
path_selector "round-robin 0"
path_checker tur
prio alua
fast_io_fail_tmo 5
detect_prio no
dev_loss_tmo 30
retain_attached_hw_handler "no"
hardware_handler 0
}
}
Step 8 Run the service multipathd reload command to reload the multipathing service. In /dev/
mapper, the WWIDs are replaced with the corresponding aliases.
HW00001:~ # service multipathd reload
HW00001:/dev/mapper # ll
total 0
crw------- 1 root root 10, 236 Dec 27 11:03 control
lrwxrwxrwx 1 root root 7 Dec 27 11:57 hana_data -> ../dm-8
lrwxrwxrwx 1 root root 7 Dec 27 11:57 hana_log -> ../dm-6
lrwxrwxrwx 1 root root 7 Dec 27 11:57 hana_shared -> ../dm-7
lrwxrwxrwx 1 root root 7 Dec 27 11:03 vg_os-root -> ../dm-0
lrwxrwxrwx 1 root root 7 Dec 27 11:03 vg_os-swap -> ../dm-1
lrwxrwxrwx 1 root root 7 Dec 27 11:03 vg_os-usr_sap -> ../dm-5
Step 9 Run the following commands to create the PVs corresponding to the LUNs:
HW00001:/dev/mapper # pvcreate /dev/mapper/hana_data
Physical volume "/dev/mapper/hana_data" successfully created
HW00001:/dev/mapper # pvcreate /dev/mapper/hana_log
Physical volume "/dev/mapper/hana_log" successfully created
HW00001:/dev/mapper # pvcreate /dev/mapper/hana_shared
Physical volume "/dev/mapper/hana_shared" successfully created
Step 11 Run the following commands to create the VGs corresponding to the LUNs:
HW00001:/dev/mapper # vgcreate hana_log /dev/mapper/hana_log
Volume group "hana_log" successfully created
HW00001:/dev/mapper # vgcreate hana_data /dev/mapper/hana_data
Volume group "hana_data" successfully created
HW00001:/dev/mapper # vgcreate hana_shared /dev/mapper/hana_shared
Volume group "hana_shared" successfully created
Step 13 Run the following commands to create the LVs corresponding to the LUNs. For the size of
each LV, see the configuration requirements.
HW00001:/dev/mapper # lvcreate -L 1T -n lv_log hana_log
Logical volume "lv_log" created.
Step 18 Add the storage mounting directories to the /etc/fstab file so that the path can be
automatically mounted after the restart. The path varies according to the actual situation.
HW00001:~ # vim /etc/fstab
----End
If the downloaded database file has already been decompressed on the local host, directly upload it to
the server.
Instance Number A HANA instance number, for example, 00, is used to identify
a HANA system from others in a server.
----End
Step 2 Run the cd command to switch to the directory where the SAP HANA database software is
saved. The directory where the SAP HANA database software is saved is cd /hana/shared/
hana2.0 in this section.
Choose installation
------------------------------------------------------------------------------
-----------------
1 | single_container | The system contains one database
2 | multiple_containers | The system contains one system database and
1..n tenant databases
Select Database Mode / Enter Index [1]: //In this example, set this parameter
to a single tenant.
------------------------------------------------------------------------------
-
1 | production | System is used in a production environment
2 | test | System is used for testing, not production
3 | development | System is used for development, not production
4 | custom | System usage is neither production, test nor
development
Select System Usage / Enter Index [4]: 1 //Enter the database usage. In this
example, the system is used as the production environment and therefore enter
1.
Enter Location of Data Volumes [/hana/data/S01]: //Enter the HANA data save
path. In this example, use the default value.
Enter Location of Log Volumes [/hana/log/S01]: //Enter the HANA log save
path. In this example, use the default value.
Restrict maximum memory allocation? [n]: n //Specify whether to limit the
HANA memory size. In this example, a single instance is used. Enter n.
Enter Certificate Host Name For Host 'hw00001' [hw00001]: //Use the default
value.
Enter System Administrator (s01adm) Password: //Enter the password of the
database administrator <sid>adm.
Confirm System Administrator ((s01adm) Password: //Confirm the password of
the database administrator <sid>adm.
Enter System Administrator Home Directory [/usr/sap/S01/home]: //Use the
default value.
Enter System Administrator Login Shell [/bin/sh]: //Use the default value.
Enter System Administrator User ID [1001]: //Use the default value.
Enter ID of User Group (sapsys) [79]: //Use the default value.
Enter Database User (SYSTEM) Password: //Enter the password of the database
user SYSTEM. This password can be the same as that of the <sid>adm
administrator.
Confirm Database User (SYSTEM) Password: //Confirm the password of the
database user SYSTEM. This password can be the same as that of the <sid>adm
administrator.
Restart system after machine reboot? [n]: //Use the default value.
Do you want to continue? (y/n): y //Confirm the information and continue the
installation.
Installing components...
Installing SAP HANA Database...
? Preparing package 'Saphostagent Setup'...
? Preparing package 'Python Support'...
? Preparing package 'Python Runtime'...
? Preparing package 'Product Manifest'...
? Preparing package 'Binaries'...
? Preparing package 'Data Quality'...
? Preparing package 'Krb5 Runtime'...
? Preparing package 'Installer'...
? Preparing package 'Ini Files'...
? Preparing package 'HWCCT'...
? Preparing package 'Emergency Support Package'...
? Preparing package 'EPM'...
? Preparing package 'Documentation'...
? Preparing package 'Delivery Units'...
? Preparing package 'DAT Languages'...
? Preparing package 'DAT Configfiles'...
? Creating System...
? Extracting software...
? Installing package 'Saphostagent Setup'...
? Installing package 'Python Support'...
? Installing package 'Python Runtime'...
? Installing package 'Product Manifest'...
? Installing package 'Binaries'...
? Installing package 'Data Quality'...
? Installing package 'Krb5 Runtime'...
? Installing package 'Installer'...
? Installing package 'Ini Files'...
? Installing package 'HWCCT'...
? Installing package 'Emergency Support Package'...
? Installing package 'EPM'...
? Installing package 'Documentation'...
? Installing package 'Delivery Units'...
? Installing package 'DAT Languages'...
? Installing package 'DAT Configfiles'...
? Creating instance...
? Starting SAP HANA Database system...
? Starting 1 process on host 'hw00001' (worker):
????? Starting on 'hw00001': hdbdaemon
? Starting 7 processes on host 'hw00001' (worker):
????? Starting on 'hw00001': hdbcompileserver, hdbdaemon, hdbindexserver,
hdbnameserver, hdbpreprocessor, hdbwebdispatcher, hdbxsengine
????? Starting on 'hw00001': hdbcompileserver, hdbdaemon, hdbindexserver,
hdbpreprocessor, hdbwebdispatcher, hdbxsengine
????? Starting on 'hw00001': hdbdaemon, hdbindexserver, hdbwebdispatcher,
hdbxsengine
????? Starting on 'hw00001': hdbdaemon, hdbwebdispatcher, hdbxsengine
Choose an action
------------------------------------------------------------------------------
-
1 | production | System is used in a production environment
2 | test | System is used for testing, not production
3 | development | System is used for development, not production
4 | custom | System usage is neither production, test nor
development
Select System Usage / Enter Index [4]: 1 //Enter the database usage. In this
example, the system is used as the production environment and therefore enter
1.
Enter Location of Data Volumes [/hana/data/S00]: //Enter the HANA data save
path. In this example, use the default value.
Enter Location of Log Volumes [/hana/log/S00]: //Enter the HANA log save
path. In this example, use the default value.
Restrict maximum memory allocation? [n]: n //Specify whether to limit the
HANA memory size. In this example, a single instance is used. Enter n.
Enter Certificate Host Name For Host 'hw00001' [hw00001]: //Use the default
value.
Enter System Administrator (s00adm) Password: //Enter the password of the
database administrator <sid>adm.
Confirm System Administrator ((s00adm) Password: //Confirm the password of
the database administrator <sid>adm.
Enter System Administrator Home Directory [/usr/sap/S00/home]: //Use the
default value.
Enter System Administrator Login Shell [/bin/sh]: //Use the default value.
Enter System Administrator User ID [1001]: //Use the default value.
Enter ID of User Group (sapsys) [79]: //Use the default value.
Enter System User (SYSTEM) Password: //Enter the password of the database
user SYSTEM. This password can be the same as that of the <sid>adm
administrator.
Confirm System User (SYSTEM) Password: //Confirm the password of the database
user SYSTEM. This password can be the same as that of the <sid>adm
administrator.
Restart system after machine reboot? [n]: //Use the default value.
Do you want to continue? (y/n): y //Confirm the information and continue the
installation.
Installing components...
Installing SAP HANA Database...
Preparing package 'Saphostagent Setup'...
If the database installation fails, uninstall the database that fails to be installed (see section 9.5
Uninstalling the Database) before the next installation.
4. Run the ps -le |grep hdb command to check whether the database main process is
running properly.
s00adm@hw00001:/usr/sap/S00/HDB00> ps -le |grep hdb
0 S 1001 439505 439497 0 80 0 - 79296 - ? 00:00:00
hdb.sapS00_HDB0
0 S 1001 439521 439505 66 80 0 - 9889652 - ? 00:05:25 hdbnameserver
0 S 1001 439704 439505 2 80 0 - 2915642 - ? 00:00:13
hdbcompileserve
0 S 1001 439706 439505 99 80 0 - 14534411 - ? 00:54:56
hdbpreprocessor
0 S 1001 439746 439505 81 80 0 - 11347338 - ? 00:06:15 hdbindexserver
0 S 1001 439748 439505 3 80 0 - 5819535 - ? 00:00:15 hdbxsengine
0 S 1001 440986 439505 2 80 0 - 2757016 - ? 00:00:10
hdbwebdispatche
5. Run the following commands to start and stop the database service:
hw00001:/hana/shared/hana2.0/SAP_HANA_DATABASE # su - s00adm
s00adm@HW00001:/usr/sap/S00/HDB00> HDB start //Start the SAP HANA database.
----End
async_read_submit=on
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
2288H V5:
Parameters for DATA volume:
async_write_submit_active=on
async_read_submit=on
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
Parameters for LOG volume:
async_write_submit_active=on
async_read_submit=on
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
2488H V5:
Parameters for DATA volume:
async_write_submit_active=on
async_read_submit=on
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
Parameters for LOG volume:
async_write_submit_active=on
async_read_submit=on
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
9008 V5:
parameters for DATA volume:
async_write_submit_active:on
async_read_submit:on
async_write_submit_blocks:all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
parameters for LOG volume:
async_write_submit_active:on
async_read_submit:on
async_write_submit_blocks:all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
Log in using <sid>adm in PuTTY and run the following commands to modify HANA
database 1.0 parameters.
[root@hw00001 HDB00]# su - s00adm
Last login: Wed Mar? 7 15:30:00 CST 2018 on pts/0
s00adm@hw00001:/usr/sap/S00/HDB00> HDB start
StartService
Impromptu CCC initialization by 'rscpCInit'.
See SAP note 1266393.
OK
OK
Starting instance using: /usr/sap/S00/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00
-function StartWait 2700 2
07.03.2018 16:35:15
Start
OK
07.03.2018 16:35:25
StartWait
OK
s00adm@hw00001:/usr/sap/S00/HDB00> hdbparam --paramset
fileio[DATA].async_write_submit_active=on
s00adm@hw00001:/usr/sap/S00/HDB00> hdbparam --paramset
fileio[DATA].async_write_submit_blocks=all
s00adm@hw00001:/usr/sap/S00/HDB00> hdbparam --paramset
fileio[DATA].async_read_submit=on
hdbparam --paramset fileio[DATA].max_parallel_io_requests=256
fileio[DATA].min_submit_batch_size=32
async_write_submit_blocks=all
max_parallel_io_requests=256
max_submit_batch_size=128
min_submit_batch_size=32
9008 V5:
parameters for DATA volume:
async_write_submit_active:on
async_read_submit:on
async_write_submit_blocks:all
max_parallel_io_requests = 256
max_submit_batch_size= 128
min_submit_batch_size= 32
parameters for LOG volume:
async_write_submit_active:on
async_read_submit:on
async_write_submit_blocks:all
max_parallel_io_requests = 256
max_submit_batch_size= 128
min_submit_batch_size= 32
Log in using <sid>adm in PuTTY and run the following commands to modify HANA
database 2.0 parameters:
[root@hw00001 HDB00]# su - s00adm
Last login: Wed Mar? 7 15:30:00 CST 2018 on pts/0
s00adm@hw00001:/usr/sap/S00/HDB00> HDB start
StartService
Impromptu CCC initialization by 'rscpCInit'.
See SAP note 1266393.
OK
OK
Starting instance using: /usr/sap/S00/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00
-function StartWait 2700 2
07.03.2018 16:35:15
Start
OK
07.03.2018 16:35:25
StartWait
OK
s00adm@hw00001:/usr/sap/S00/HDB00> hdbsql -n localhost:30015 -u SYSTEM -p
HUAWEI12#$ //In the multi-tenant scenario, the port number is 30013.
Welcome to the SAP HANA Database interactive terminal.
0 rows affected (overall time 5343 usec; server time 2955 usec)
----End
The Huawei SAP HANA solution offers two types of Linux OS, SLES and RHEL, for you to
select. For both types, Huawei engineers download the OS license (key) at the customer site
and provide the license for the customer so that the customer can use it to activate the OS
subscription. The warranty period of the OS subscription starts when the OS subscription is
activated.
To activate the subscription service by using the OS license, perform the following steps:
1. Frontline service engineers (from GTS or TAC/GTAC) download the OS license from
the ESDP platform and email the OS license to the customer.
2. The customer registers an SLES/RHEL account (free of charge).
3. The customer uses the OS license to activate the OS subscription. (The SLES warranty
period starts when the OS subscription is activated. The RHEL warranty period starts
upon OS subscription.)
4. The OS warranty period can be one, three, or five years, depending on the order terms.
In this document, activating an OS is to activate the user account subscription on the SLES or
RHEL website.
Step 1 Enter your subscription number on the page shown in the following figure.
Step 3 Read the terms and conditions, and click AGREE. The new subscription or subscription
renewal is complete, and you will receive an email indicating that your subscription has been
activated.
Note: If you do not have a Red Hat login account, visit https://rhn.redhat.com and click
Register to create a login account.
----End
If you do not have a SUSE account, you must create one (free of charge) when logging in to
the SUSE Customer Center for the first time.
Step 3 Configure the account information and click Create Login at the bottom of the page.
Step 4 Verify your email address to further manage your account (for example, restore your
password).
Step 5 Use the registered username to log in and accept the policy clauses.
Step 6 Use the subscription code to activate the subscription on the SUSE Customer Center.
Step 7 On the dashboard, switch to Management tools, and click Manually activate subscription.
Step 10 After the registration is successful, check the subscription information on the subscription
page.
----End
11 OS Lifecycle
13-year lifecycle
A total of 13-year support period is provided, 10 years of general & ESPOS support, and
3 years of LTSS.
l For each of the SPs:
– Generally the SPs are released in a around 12-month cadence. When the new SP is
released, the last SP will be continue supported for about 18 months, provide
enough time for the customer to test and migrate to the new SP.
– Each SP, except the last one, has around 18 months of general support and 12
months of Extended SP Overlay Support (ESPOS) period. After that, 2 years of
LTSS support can be provide by SUSE if the customer purchases the LTSS support
in addition to their subscription.
– The last SP will receive longer general & ESPOS support than previous SPs, till the
end of the 10th year since the release of the major version.
For detail information about the SLES for SAP lifecycle, visit:
https://scc.suse.com/docs/userguide
13-year lifecycle
– Generally the SPs are released in a around 12-month cadence. When the new SP is
released, the last SP will be continue supported for about 3.5 years, provide enough
time for the customer to test and migrate to the new SP.
– Each SP, except the last one, has around 18 months of general support and 42
months of Extended SP Overlay Support (ESPOS) period. The ESPOS included in
SLES for SAP subscription now.
– The last SP will receive longer general support than previous SPs, till the end of the
10th year since the release of the major version. There will be a 3-year LTSS
support for the last SP.
– Release plan of SP5 & 6, including whether there will be such SP and when, are
subject to change according to the actual situation around the time of SP3/4.
For detail information about the SLES for SAP lifecycle, visit:
https://scc.suse.com/docs/userguide
For detail information about the RHEL for SAP lifecycle, visit:
https://access.redhat.com/support/policy/updates/errata/
Provisioning/Setup
Maintenance
Operations
Support
Huawei
Mainland China: 400-822-9999 (enterprise); 400-830-2118 (carrier)
Support website: https://support.huawei.com
SUSE
Mainland China: 400-810-6500
Support website: https://scc.suse.com/
Red Hat
Mainland China: 800 810 2100; 400 890 2100
Support website: https://access.redhat.com
Step 3 Click Report an incident. The page for generating a trouble ticket is displayed.
Step 4 Enter any character string in Enter search term and press Enter. Click Contact SAP
Support at the lower right corner.
Step 5 Select a product, for example, SAP ERP, and click Search.
Step 6 Go to the problem description page, fill in the trouble ticket details, and click Submit at the
lower right corner.
----End
l Contact the Huawei service hotline. For details about the contact information, visit http://
e.huawei.com/en/service-hotline.
For enterprise users in China, contact Huawei in either of the following ways:
– Hotline: 400-822-9999
– Customer service email: support_e@huawei.com
Enterprise customers: Global Service Hotline
For carrier users in China, contact us in the following ways:
– Hotline: 400-830-2118
– Email: support@huawei.com
Enterprise customers: Global Service Hotline
l Contact the technical support personnel of your local Huawei office.
Step 2 On the Support Tickets page, click Open a new ticket, as shown in Figure 12-3.
Step 3 On the New Support Ticket page, fill in the ticket and submit it.
1. Set Account, Entitlement, and Product, and click Next.
3. Select Platform and Severity, describe the problem in the Description text box, and
click Next.
4. Select a contact method and click Create Support Ticket to create the ticket.
----End
News
For notices about product life cycles, warnings, and updates, visit Product Bulletins.
Cases
Learn about server applications at Knowledge Base.
audit-2.8.1-3.el7.x86_64.rpm
audit-libs-2.8.1-3.el7.x86_64.rpm
audit-libs-python-2.8.1-3.el7.x86_64.rpm
autogen-libopts-5.18-5.el7.x86_64.rpm
checkpolicy-2.5-6.el7.x86_64.rpm
clufter-bin-0.77.0-2.el7.x86_64.rpm
clufter-common-0.77.0-2.el7.noarch.rpm
compat-sap-c++-5-5.3.1-10.el7_3.x86_64.rpm
compat-sap-c++-6-6.3.1-1.el7_3.x86_64.rpm
corosync-2.4.3-2.el7_5.1.x86_64.rpm
corosynclib-2.4.3-2.el7_5.1.x86_64.rpm
cpp-4.8.5-28.el7_5.1.x86_64.rpm
dbus-1.10.24-7.el7.x86_64.rpm
dbus-libs-1.10.24-7.el7.x86_64.rpm
dwz-0.11-3.el7.x86_64.rpm
expect-5.45-14.el7_1.x86_64.rpm
fence-agents-all-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-amt-ws-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-apc-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-apc-snmp-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-bladecenter-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-brocade-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-cisco-mds-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-cisco-ucs-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-common-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-compute-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-drac5-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-eaton-snmp-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-emerson-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-eps-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-heuristics-ping-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-hpblade-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ibmblade-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ifmib-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ilo2-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ilo-moonshot-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ilo-mp-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ilo-ssh-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-intelmodular-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ipdu-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-ipmilan-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-kdump-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-mpath-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-rhevm-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-rsa-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-rsb-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-sbd-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-scsi-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-vmware-rest-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-vmware-soap-4.0.11-86.el7_5.2.x86_64.rpm
fence-agents-wti-4.0.11-86.el7_5.2.x86_64.rpm
fence-virt-0.3.2-13.el7.x86_64.rpm
flac-libs-1.3.0-5.el7_1.x86_64.rpm
gcc-4.8.5-28.el7_5.1.x86_64.rpm
gd-2.0.35-26.el7.x86_64.rpm
ghostscript-9.07-28.el7_4.2.x86_64.rpm
ghostscript-fonts-5.50-32.el7.noarch.rpm
glibc-2.17-222.el7.x86_64.rpm
glibc-common-2.17-222.el7.x86_64.rpm
glibc-devel-2.17-222.el7.x86_64.rpm
glibc-headers-2.17-222.el7.x86_64.rpm
gnutls-dane-3.3.26-9.el7.x86_64.rpm
gnutls-utils-3.3.26-9.el7.x86_64.rpm
graphviz-2.30.1-21.el7.x86_64.rpm
gsm-1.0.13-11.el7.x86_64.rpm
gstreamer1-1.10.4-2.el7.x86_64.rpm
ipmitool-1.8.18-7.el7.x86_64.rpm
iptraf-ng-1.1.4-6.el7.x86_64.rpm
kernel-3.10.0-862.2.3.el7.x86_64.rpm
kernel-devel-3.10.0-862.2.3.el7.x86_64.rpm
kmod-kvdo-6.1.0.168-16.el7_5.x86_64.rpm
krb5-libs-1.15.1-19.el7.x86_64.rpm
krb5-workstation-1.15.1-19.el7.x86_64.rpm
libasyncns-0.8-7.el7.x86_64.rpm
libcanberra-0.30-5.el7.x86_64.rpm
libcanberra-gtk2-0.30-5.el7.x86_64.rpm
libcanberra-gtk3-0.30-5.el7.x86_64.rpm
liberation-fonts-common-1.07.2-16.el7.noarch.rpm
liberation-sans-fonts-1.07.2-16.el7.noarch.rpm
libfontenc-1.1.3-3.el7.x86_64.rpm
libgcc-4.8.5-28.el7_5.1.x86_64.rpm
libgomp-4.8.5-28.el7_5.1.x86_64.rpm
libICE-1.0.9-9.el7.x86_64.rpm
libicu-50.1.2-15.el7.x86_64.rpm
libkadm5-1.15.1-19.el7.x86_64.rpm
libmpc-1.0.1-3.el7.x86_64.rpm
libqb-1.0.1-6.el7.x86_64.rpm
libselinux-2.5-12.el7.x86_64.rpm
libselinux-python-2.5-12.el7.x86_64.rpm
libselinux-utils-2.5-12.el7.x86_64.rpm
libsemanage-2.5-11.el7.x86_64.rpm
libsemanage-python-2.5-11.el7.x86_64.rpm
libsepol-2.5-8.1.el7.x86_64.rpm
libSM-1.2.2-2.el7.x86_64.rpm
libsndfile-1.0.25-10.el7.x86_64.rpm
libstdc++-4.8.5-28.el7_5.1.x86_64.rpm
libstdc++-devel-4.8.5-28.el7_5.1.x86_64.rpm
libvpx-1.3.0-5.el7_0.x86_64.rpm
libwsman1-2.6.3-3.git4391e5c.el7.x86_64.rpm
libXaw-1.0.13-4.el7.x86_64.rpm
libXfont-1.5.2-1.el7.x86_64.rpm
libXmu-1.1.2-2.el7.x86_64.rpm
libXpm-3.5.12-1.el7.x86_64.rpm
libXt-1.1.5-3.el7.x86_64.rpm
libyaml-0.1.4-11.el7_0.x86_64.rpm
linux-firmware-20180220-62.git6d51311.el7.noarch.rpm
lm_sensors-3.4.0-4.20160601gitf9185e5.el7.x86_64.rpm
mozilla-filesystem-1.9-11.el7.x86_64.rpm
mpfr-3.1.1-4.el7.x86_64.rpm
net-snmp-libs-5.7.2-33.el7_5.2.x86_64.rpm
net-snmp-utils-5.7.2-33.el7_5.2.x86_64.rpm
nfs-utils-1.3.0-0.54.el7.x86_64.rpm
ntp-4.2.6p5-28.el7.x86_64.rpm
ntpdate-4.2.6p5-28.el7.x86_64.rpm
numactl-2.0.9-7.el7.x86_64.rpm
OpenIPMI-modalias-2.0.23-2.el7.x86_64.rpm
openssl-1.0.2k-12.el7.x86_64.rpm
openssl-libs-1.0.2k-12.el7.x86_64.rpm
openwsman-python-2.6.3-3.git4391e5c.el7.x86_64.rpm
overpass-fonts-2.1-1.el7.noarch.rpm
pacemaker-1.1.18-11.el7_5.2.x86_64.rpm
pacemaker-cli-1.1.18-11.el7_5.2.x86_64.rpm
pacemaker-cluster-libs-1.1.18-11.el7_5.2.x86_64.rpm
pacemaker-libs-1.1.18-11.el7_5.2.x86_64.rpm
PackageKit-glib-1.1.5-2.el7_5.x86_64.rpm
PackageKit-gtk3-module-1.1.5-2.el7_5.x86_64.rpm
patch-2.7.1-10.el7_5.x86_64.rpm
pcs-0.9.162-5.el7_5.1.x86_64.rpm
perl-srpm-macros-1-8.el7.noarch.rpm
perl-Thread-Queue-3.02-2.el7.noarch.rpm
perl-TimeDate-2.30-2.el7.noarch.rpm
pexpect-2.3-11.el7.noarch.rpm
policycoreutils-2.5-22.el7.x86_64.rpm
policycoreutils-python-2.5-22.el7.x86_64.rpm
poppler-data-0.4.6-3.el7.noarch.rpm
pulseaudio-libs-10.0-5.el7.x86_64.rpm
python-clufter-0.77.0-2.el7.noarch.rpm
python-inotify-0.9.4-4.el7.noarch.rpm
python-IPy-0.75-6.el7.noarch.rpm
python-suds-0.4.1-5.el7.noarch.rpm
PyYAML-3.10-11.el7.x86_64.rpm
redhat-rpm-config-9.1.0-80.el7.noarch.rpm
resource-agents-3.9.5-124.el7.x86_64.rpm
resource-agents-sap-hana-3.9.5-124.el7.x86_64.rpm
rpm-4.11.3-32.el7.x86_64.rpm
rpm-build-4.11.3-32.el7.x86_64.rpm
rpm-build-libs-4.11.3-32.el7.x86_64.rpm
rpm-libs-4.11.3-32.el7.x86_64.rpm
rpm-python-4.11.3-32.el7.x86_64.rpm
rsyslog-8.24.0-16.el7_5.4.x86_64.rpm
ruby-2.0.0.648-33.el7_4.x86_64.rpm
rubygem-bigdecimal-1.2.0-33.el7_4.x86_64.rpm
rubygem-io-console-0.4.2-33.el7_4.x86_64.rpm
rubygem-json-1.7.7-33.el7_4.x86_64.rpm
rubygem-psych-2.0.0-33.el7_4.x86_64.rpm
rubygem-rdoc-4.0.0-33.el7_4.noarch.rpm
rubygems-2.0.14.1-33.el7_4.noarch.rpm
ruby-irb-2.0.0.648-33.el7_4.noarch.rpm
ruby-libs-2.0.0.648-33.el7_4.x86_64.rpm
setools-libs-3.3.8-2.el7.x86_64.rpm
sg3_utils-1.37-12.el7.x86_64.rpm
sound-theme-freedesktop-0.8-3.el7.noarch.rpm
startup-notification-0.12-8.el7.x86_64.rpm
subscription-manager-1.20.11-1.el7_5.x86_64.rpm
subscription-manager-plugin-container-1.20.11-1.el7_5.x86_64.rpm
subscription-manager-rhsm-1.20.11-1.el7_5.x86_64.rpm
subscription-manager-rhsm-certificates-1.20.11-1.el7_5.x86_64.rpm
sudo-1.8.19p2-13.el7.x86_64.rpm
tcl-8.5.13-8.el7.x86_64.rpm
telnet-0.17-64.el7.x86_64.rpm
tuned-2.9.0-1.el7.noarch.rpm
tuned-profiles-sap-hana-2.9.0-1.el7.noarch.rpm
unbound-libs-1.6.6-1.el7.x86_64.rpm
urw-fonts-2.4-16.el7.noarch.rpm
vdo-6.1.0.168-18.x86_64.rpm
xcb-util-0.4.0-2.el7.x86_64.rpm
xorg-x11-font-utils-7.5-20.el7.x86_64.rpm
xorg-x11-xauth-1.0.9-1.el7.x86_64.rpm
xulrunner-31.6.0-2.el7_1.x86_64.rpm
yum-utils-1.1.31-45.el7.noarch.rpm
zlib-devel-1.2.7-17.el7.x86_64.rpm
kernel-default-4.4.162-94.72.1.x86_64.rpm