November 2019

By Archana Kuppuswamy, Stephen Ma, and Ramesh Satyanarayana

Reference Architecture Guide

Hitachi Solution for the SAP HANA Platform in a Scale-up Configuration using Hitachi Advanced Server DS7000

FeedbackHitachi Vantara welcomes your feedback. Please share your thoughts by sending an email message to SolutionLab@HitachiVantara.com. To assist the routing of this message, use the paper number in the subject and the title of this white paper in the text.

Revision History

Revision Changes Date

MK-SL-046-00 Initial release. April 9, 2018

MK-SL-046-01 Refreshed for mixed DIMMs T-shirt sizes. May 21, 2018

MK-SL-046-02 Added support for VSP G350. February 20, 2019

MK-SL-046-03 Updated Engineering Validation section and added support for SLES12SP4.

Updated Hitachi Virtual Storage Platform F350 (VSP F350), VSP G350, and VSP G200.

Updated Appendex1 Global.ini file for SLES12SP4.

November 21, 2019

Table of ContentsKey Solution Elements 5

Hardware Elements 5

Software Elements 7

Solution Design 8Hitachi Advanced Server DS7000 Configuration 8

Network Architecture Configuration 9

Storage Architecture Configuration 11

Storage Configuration for VSP F350 and VSP G350 19

SAP HANA Configuration 27

Engineering Validation 27

Appendix 1 28

Appendix 2 29

1

1

Hitachi Solution for the SAP HANA Platform in a Scale-up Configuration using Hitachi Advanced Server DS7000Reference Architecture Guide

This solution uses an external storage subsystem following the appliance approach to implement SAP HANA.

This SAP HANA infrastructure uses the following components:

Hardware

One Hitachi Advanced Server DS7000

External sub-system storage Hitachi Virtual Storage Platform G200 (VSP G200)

External sub-system storage Hitachi Virtual Storage Platform F350 (VSP F350) and Hitachi Virtual Storage Platform G350 (VSP G350)

Software

Preconfigured with SAP HANA to provide a converged solution for real time analytics

The validation of this environment with external storage was with Hitachi Virtual Storage Platform VSP F350, VSP G350, and VSP G200. Your needs may require other storage options and fall under a Tailored Datacenter Integration (TDI) solution. Contact your account representative for details and implementation services whenever you require using external storage.

Figure 1 shows the topology of this reference solution using external drives on a Hitachi Virtual Storage Platform VSP F350, VSP G350, or VSP G200 storage subsystem.

2

2

Figure 1

This solution for SAP HANA is a preconfigured converged system for real-time analytics. It is ready to plug into your network to provide real-time access to operational data for use in analytic models.

This system supports the configurations listed in Table 1. Slotting of memory slots is shown in Figure 2.

For more up-to-date information please see the SAP Hardware Directory.

Note — A DS7080, 6-socket configuration is configured using a “Compute Box for a 4 × 2 socket server” in which the bottom “Compute Unit” is missing (and replaced by a “2U Dummy for Compute Box”). The sockets are numbered from 0 to 5 from top to bottom.

3

3

TABLE 1. APPLIANCE SUPPORTED CONFIGURATIONS

Number of Sockets RAM Size Storage

2 × Intel Xeon Platinum 8176/8176M/8180/8180M processors using Hitachi Advanced Server DS7020

384 GB with 12 × 32 GB LRDIMMs

768 GB with 24 × 32 GB LRDIMMs

768 GB with 12 × 64 GB LRDIMMs

1152 GB with 12 × 32 GB and 12 × 64 GB LRDIMMs

1536 GB with 24 × 64 GB LRDIMMs

Hitachi Virtual Storage Platform F350, Hitachi Virtual Storage Platform G350, or G200

2 × Intel Xeon Platinum 8176M/8180M processors using Hitachi Advanced Server DS7020

1536 GB with 12 × 128 GB RDIMMs 3DS

2304 GB with 12 × 64 GB and 12 × 128 GB RDIMMs 3DS

3072 GB with 24 × 128 GB RDIMMs 3DS

4 × Intel Xeon Platinum 8176/8176M/8180/8180M processors using Hitachi Advanced Server DS7040

2304 GB with 24 × 32 GB and 24 × 64 GB LRDIMMs

3072 GB with 48 × 64 GB LRDIMMs

4 × Intel Xeon Platinum 8176M/8180M processors using Hitachi Advanced Server DS7040

3072 GB with 24 × 128 GB RDIMMs 3DS

4608 GB with 24 × 64 GB and 24 × 128 GB RDIMMs 3DS

6144 GB with 48 × 128 GB RDIMMs 3DS

6 × Intel Xeon Platinum 8176/8176M/8180/8180M processors using Hitachi Advanced Server DS7080

3456 GB with 36 × 32 GB and 36 × 64 GB LRDIMMs

4608 GB with 72 × 64 GB LRDIMMs

4

4

Figure 2

This technical paper assumes that you have familiarity with the following:

Storage area network (SAN)-based storage systems

General storage concepts

Common IT storage practices

SAP HANA

Note — Testing of this configuration was in a lab environment. Many things affect production environments beyond prediction or duplication in a lab environment. Follow the recommended practice of conducting proof-of-concept testing for acceptable results in a non-production, isolated test environment that otherwise matches your production environment before your production implementation of this solution.

6 × Intel Xeon Platinum 8176M/8180M processors using Hitachi Advanced Server DS7080

4608 GB with 36 × 128 GB RDIMMs 3DS

6912 GB with 36 × 64 GB and 36 × 128 GB RDIMMs 3DS

9216 GB with 72 × 128 GB RDIMMs 3DS

Hitachi Virtual Storage Platform F350, Hitachi Virtual Storage Platform G350, or G200

8 × Intel Xeon Platinum 8176/8176M/8180/8180M processors using Hitachi Advanced Server DS7080

4608 GB with 48 × 32 GB and 48 × 64 GB LRDIMMs

6144 GB with 96 × 64 GB LRDIMMs

8 × Intel Xeon Platinum 8176M/8180M processors using Hitachi Advanced Server DS7080

6144 GB with 48 × 128 GB RDIMMs 3DS

9216 GB with 48 × 64 GB and 48 × 128 GB RDIMMs 3DS

12288 GB with 96 × 128 GB RDIMMs 3DS

TABLE 1. APPLIANCE SUPPORTED CONFIGURATIONS (CONTINUED)

Number of Sockets RAM Size Storage

Capacity (GB)controller # per CPU

chanel # 2 4 6 8DIMM slot # 1 2 3 4 5 6 7 8 9 10 11 12 DS7020 DS7040 DS7080 DS7080

2DPC 32/64G mix 64 32 64 32 64 32 64 32 64 32 64 32 576 1152 2304 3456 4608

2DPC 64/128G mix 128 64 128 64 128 64 128 64 128 64 128 64 1152 2304 4608 6912 9216

2DPC 128GB DIMM 128 128 128 128 128 128 128 128 128 128 128 128 1536 3072 6144 9216 12288

Capacity (GB) with #CPU0 1

0 1 2 0 1 2

5

5

Key Solution ElementsThe following are the key hardware and software components used in this reference architecture.

Note — Do not change the layout of any of the components in this environment without consulting your Hitachi Vantara account representative. Changing this layout can require manual configuration of the network and/or using different components.

Hardware ElementsTable 2 lists the hardware used to deploy the specific scale-up configuration of Hitachi Solution for the SAP HANA platform for the different sized solutions.

Hitachi Advanced Server DS7000 uses an external storage sub-system, as indicated in Table 2.

TABLE 2. HARDWARE ELEMENTS

Hardware Quantity Configuration Role

Hitachi Advanced Server DS7020

1 CPU per SAP HANA node:

2 Intel Xeon Platinum 8176/8176M Processor 28-core, 2.1GHz, 165W*

Or 2 Intel Xeon Platinum 8180/8180M Processor 28-core, 2.5GHz, 205W*

2 heat sinks CPU 0/1

RAM per SAP HANA node, refer to

SAP HANA server

Mellanox Technologies MT27710 Family [ConnectX-4 Lx]

2 Mellanox Connectx4 dual port PCIe card per compute module

For SAP HANA 10 GbE client network and additional 10 GbE network

2 Cisco SFP+ 3M Twinaxial cables

Hitachi Virtual Storage Platform VSP F350/VSP G350/VSP G200

1 Single frame Block storage

16 Gb/s F/C Dual HBA w/o cable-LPe31002 M6 Blade

2 2-port LPE31002-M6 16 Gb/s card per compute module

Connectivity to the external storage sub-system

4 16 Gb/s SFP

6

6

* M type processors are required for 128 GB DIMMs use.

Hitachi Advanced Server DS7000 SeriesA combination of extremely innovative and exclusive technologies, DS7000 x86 servers can respond flexibly, securely and cost-effectively to all your storage challenges. Based on a reliable, powerful, and modular architecture using Intel Xeon Platinum 8176/8176M or 8180/8180M processors, DS7000 addresses extreme demands that are often believed to be completely irreconcilable: performance and elasticity, reliability and cost control. Immediate, real, measurable benefits: unique in the x86 world, DS7000 reaches the highest level of quality of service, performance, availability and scalability to meet the three big challenges an IT Department is facing: Data Center optimization, IT modernization and Big Data efficient implementation.

Scalability: The same technology can be used for any SAP HANA deployment for both Business Warehouse and S/4 HANA implementations. This protects investments, by providing a migration path for any architecture using SAP HANA, at any scale.

Flexibility: DS7000 is certified for SAP HANA, whether in Tailored Datacenter Integration (TDI) mode or in appliance mode. Appliance mode provides pre-integrated hardware, storage, and software for fast deployment, backed by central support and agreed performance levels. TDI mode offers total flexibility to use any storage technology certified by SAP in its TDI program, or to reuse an existing SAN.

Quality of service: DS7000 provides unique memory protection features, essential for mission critical systems. Thanks to a patented blade system, RAM and PCIe components can be hot-plugged or hot-swapped to facilitate maintenance activities while providing best-in-class high availability.

Hitachi Virtual Storage Platform Fx00 and Gx00 Models Hitachi Virtual Storage Platform Fx00 models and Hitachi Virtual Storage Platform Gx00 models are based on industry-leading enterprise storage technology. With flash-optimized performance, these systems provide advanced capabilities previously available only in high-end storage arrays. Virtual Storage Platform Fx00 models provide three times more all-flash performance and the industry’s only 100% data-availability guarantee and help you tackle complicated business challenges. With the Virtual Storage Platform Gx00 models, you can build a high performance, software-defined infrastructure to transform data into valuable information.

Cisco Nexus 3048 switch

1 48 × 1 GbE ports Optional switch for management network

Cisco Nexus 93180YC-EX switch

2 48 × 10 GbE ports Optional switches for client network or additional backup network

Minkel Global Solutions Rack

1 1 standard rack Optional rack for mounting server

PDUs 6 Vertical PDUs Optional PDUs for solution

TABLE 2. HARDWARE ELEMENTS (CONTINUED)

Hardware Quantity Configuration Role

7

7

Hitachi Storage Virtualization Operating System provides storage virtualization, high availability, superior performance, and advanced data protection for all Virtual Storage Platform Gx00 models. This proven, mature software provides common features to consolidate assets, reclaim space, extend life, and reduce migration effort.

When validating this environment, VSP F350, VSP G350, and VSP G200 were used as the external storage sub-system.

Software ElementsTable 3 describes the software products used to deploy this solution.

SAP HANASAP HANA converges database and application platform capabilities in-memory to transform transactions, analytics, text analysis, predictive and spatial processing so businesses can operate in real-time. This combines database, data processing, and application platform capabilities in a single in-memory platform. Also, the platform provides libraries for predictive, planning, text processing, spatial, and business analytics — all on the same architecture. This architecture comes from leading hardware partners of SAP, including Hitachi.

By eliminating the divide between transactions and analytics, SAP HANA allows you to answer any business question anywhere in real time.

As a SAP customer, you can download more information on SAP HANA at the SAP Support Portal. See the installation and upgrade guides download section for SAP In-Memory Computing (SAP In-Memory Appliance — SAP HANA). The following are available:

SAP HANA Master Guide

This is the central starting point for the technical implementation of SAP HANA. Use this for basic concepts and for planning.

SAP HANA Server Installation and Update Guide

Use the various installation guides to install the required SAP In-Memory Database and the other software components for the different replication technologies. Refer to the SAP HANA Server Installation and Update Guide for an overview on how to install SAP HANA.

SAP HANA Administration Guide

This provides an end-to-end picture of the available SAP HANA administration tools and the key tasks for a system administrator to perform.

SAP Integration and Certification Center (SAP ICC)

SAP HANA hardware directory provides information about SAP HANA appliances certified by SAP hardware partners.

TABLE 3. SOFTWARE ELEMENTS

Software

Operating system SUSE Linux Enterprise Server for SAP Applications

Red Hat Enterprise Linux (alternate)

Database SAP HANA

8

8

This is a link to all SAP HANA-related documentation: https://help.sap.com/viewer/p/SAP_HANA_PLATFORM.

Operating System ChoicesThe scale-up configuration of Hitachi Solution for the SAP HANA Platform can run on the following Linux operating systems:

SUSE Linux Enterprise Server (SLES) for SAP Applications

Compete more effectively though improved uptime, better efficiency, and accelerated innovation using SUSE Linux Enterprise Server. This is a versatile server operating system for efficiently deploying highly available enterprise-class IT services in mixed IT environments with performance and reduced risk.

SUSE Linux Enterprise Server was the first Linux operating system to be certified for use with SAP HANA. It remains the operating system of choice for most SAP HANA customers.

Red Hat Enterprise Linux (RHEL) Using the stability and flexibility of Red Hat Enterprise Linux, reallocate your resources towards meeting the next challenges instead of maintaining the status quo. Deliver meaningful business results by providing exceptional reliability on military-grade security. Use Enterprise Linux to tailor your infrastructure as markets shift and technologies evolve.

Changing the configuration settings is only supported along the guidelines of SAP and the operating system distributor and may otherwise cause significant performance problems. The following SAP Notes for SLES and RHEL are a good starting point for information on this topic:

1944799 - SAP HANA Guidelines for SLES Operating System Installation

2009879 - SAP HANA Guidelines for Red Hat Enterprise Linux (RHEL) Operating System

2235581 – SAP HANA: Supported Operating System

The initially delivered configuration of the operating system should persist. Do not make any modifications to the operating system, except as noted or approved by SAP.

Solution DesignThe detailed design for this scale-up configuration of Hitachi Solution for the SAP HANA Platform for this reference solution includes the following:

Hitachi Advanced Server DS7000 Configuration

Network Architecture Configuration

Storage Architecture Configuration

Storage Configuration for VSP F350 and VSP G350

Hitachi Advanced Server DS7000 ConfigurationThe DS7000 basic building block comprises:

2 processors (28-core 8176/M or 28-core 8180/M)

12 memory DIMMs per CPU, 24 per compute module

5 IO blades for PCIe adapters

4 native 1GbE Ethernet ports

9

9

This compute module acts as master and other identical modules can be added as slaves to add more resources. Figure 3 details the PCIE components of all DS7000 configurations.

Figure 3

Hitachi Advanced Server DS7000 solution scales from 2 sockets to 8 sockets, please refer to Figure 4 for the location of network and HBA cards.

Figure 4

Network Architecture ConfigurationConnect the 1 GbE management port of Hitachi Advanced Server DS7000 to a Cisco Nexus 3048 switch or to any other external 1 GbE switch for management connectivity, as shown in Figure 5.

10

10

Figure 5

Make the following 10 GbE network connections for SAP HANA nodes, please refer to Table 4, “Network Setup,” on page 11:

Connect the following to Cisco Nexus 93180YC-EX switches or to any other external switches:

Port 0 of 10 GbE Mellanox Connect-4x LX PCIe card to two different Cisco Nexus 93180YC-EX switches.

Bond the corresponding two ports, eth9901 and eth9902, as bond0 at the operating system level using active-active network bond mode with the following options:

mode= 802.3ad miimon=100 xmit_hash_policy=2 lacp_rate=fast

This acts as the client network for the SAP HANA node.

If additional 10 GbE network connections are required, connect Port 1 of both 10 GbE Mellanox Connect-4x LX PCIe cards to the Cisco Nexus 93180YC-EX switches or to any other external switches.

For all sizes, PCIE Slot 1 and 3 of the master module are used to create a bond. All other slots and ports can be used per customer discretion.

11

11

Note — The management network and client network can be on the same network switch or a separate network switch, depending on the network environment.

Storage Architecture Configuration

External Storage with Hitachi Virtual Storage Platform G200These are the storage components you need to implement a scale-up SAP HANA system with Hitachi Advanced Server DS7000 using Hitachi Virtual Storage Platform VSP F350/VSP G350/VSP G200:

2 × 2-port Emulex LPE31002-M6 16 Gb/s PCIe HBA cards

1 Hitachi Virtual Storage Platform F350/VSP G350/VSP G200

Storage drive box trays (DBS)

Spare drives

For a direct connection between Hitachi Virtual Storage Platform F350, Virtual Storage Platform G350, or Virtual Storage Platform G200 and the Emulex HBA on Advanced Server DS7000, use System Mode 847 to enable the following host mode options (HMO) for the corresponding storage port connected to the server:

HMO 02 - This setting is recommended when the system uses test-unit-ready (TUR) for path_checker in the /etc/multipath.conf file. This setting helps to suppress unwanted warning messages related to the reservation conflict at the operating system level.

HMO 94 - Mandatory for direct connection between Hitachi Virtual Storage Platform and the Emulex Lpe31002 HBA to work. Without setting Host Mode Option 94, SAN storage cannot be identified by the Emulex HBA.

HMO109 - Fixes the SAN boot issue where sometimes the system cannot find the boot LUN after a reboot. The Host Group ID must be 00 for SAN Boot.

TABLE 4. NETWORK SETUP

Network Card Port Network Description

PCIe_Slot_1 of Master Module

0 Client network for the SAP HANA node (eth9902)

1 Free for use as additional 10 GbE network for backup, SAP HANA system replication, or other purposes

PCIe_Slot_3 of Master Module

0 Client network for the SAP HANA node (eth9901)

1 Free for use as additional 10 GbE network for backup, SAP HANA system replication, or other purposes

12

12

Figure 6

Without setting up this option, SAN Storage cannot be identified from the Emulex HBA. Also, make sure to use the following port properties as listed in Table 5.

The SAP HANA node requires the following storage layout:

Operating system volume

SAP HANA shared volume for the SAP HANA binaries and other configuration files

Log volume

Data volume

TABLE 5. PORT PROPERTIES ON VIRTUAL STORAGE PLATFORM G200

For this setting Use this value

Port Security Disabled

Port Speed 16 Gbps

Fabric OFF

Connection Type P-to-P

13

13

This reference setup utilizes a dynamic provisioning pool design for the storage layout that ensures maximum utilization and optimization at a lower cost.

Use two dynamic provisioning pools with the specific parity groups listed in Table 6 for the storage layout.

The example layout in Table 7 uses the dynamic provisioning pool layout on Virtual Storage Platform G200 for a SAP HANA Appliance solution with a 3 TB scale-up system.

TABLE 6. DYNAMIC PROVISIONING POOLS

Dynamic Provisioning Pool Name Purpose Parity Group RAID Level and Disks

OS_SH_Data_Pool Operating system LUN

SAP HANA shared LUN

Data LUN

RAID-6 (14D+2P) on 1200 GB, 10k RPM SAS drives

Log_Pool Log LUN RAID-6 (6D+2P) on 600 GB, 10k RPM SAS drives

TABLE 7. DYNAMIC PROVISIONING POOL FOR A SAP HANA TDI SOLUTION

Dynamic Provisioning Pool

Parity Group ID

Parity Group RAID Level and Disks LDEV ID LDEV Name

LDEV Size (GB)

MPU Assignment

OS_SH_Data_Pool 1 RAID-6 (14D+2P) on 1200 GB, 10k RPM SAS drives

00:00:01 OS_SH_DA_Pool_1 1800 MPU-10

00:00:02 OS_SH_DA_Pool_2 1800 MPU-11

00:00:03 OS_SH_DA_Pool_3 1800 MPU-20

00:00:04 OS_SH_DA_Pool_4 1800 MPU-21

00:00:05 OS_SH_DA_Pool_5 1800 MPU-10

00:00:06 OS_SH_DA_Pool_6 1800 MPU-11

00:00:07 OS_SH_DA_Pool_7 1800 MPU-20

00:00:08 OS_SH_DA_Pool_8 1800 MPU-21

Log_Pool 2 RAID-6 (6D+2P) on 600 GB, 10k RPM SAS drives

00:01:01 Log_Pool_1 750 MPU-10

00:01:02 Log_Pool_2 750 MPU-11

00:01:03 Log_Pool_3 750 MPU-20

00:01:04 Log_Pool_4 750 MPU-21

14

14

Provision the virtual volumes for the operating system, SAP HANA shared, data, and log volumes following Table 8 for a SAP HANA TDI solution with a 3 TB scale-up system.

Table 9 lists the LUN path assignment used when validating this environment.

TABLE 8. VIRTUAL VOLUMES FOR THE SAP HANA NODES

Dynamic Provisioning Pool

Virtual Volume ID Virtual Volume Name

Virtual Volume Size

MPU Assignment

OS_SH_Data_Pool 00:02:00 HANA_OS 100 GB MPU-10

00:02:01 HANA_SH 3100 GB MPU-20

Log_Pool 00:02:02 HANA_LOG_1 150 GB MPU-10

00:02:03 HANA_LOG_2 150 GB MPU-11

00:02:04 HANA_LOG_3 150 GB MPU-20

00:02:05 HANA_LOG_4 150 GB MPU-21

OS_SH_Data_Pool 00:02:06 HANA_DATA_1 2320 GB MPU-10

00:02:07 HANA_DATA_2 2320 GB MPU-11

00:02:08 HANA_DATA_3 2320 GB MPU-20

00:02:09 HANA_DATA_4 2320 GB MPU-21

TABLE 9. EXAMPLE LUN PATH ASSIGNMENT

LUN ID LDEV ID LDEV Name

0000 00:02:00 HANA_OS

0001 00:02:01 HANA_SH

0002 00:02:02 HANA_LOG_1

0003 00:02:03 HANA_LOG_2

0004 00:02:04 HANA_LOG_3

0005 00:02:05 HANA_LOG_4

0006 00:02:06 HANA_DATA_1

0007 00:02:07 HANA_DATA_2

0008 00:02:08 HANA_DATA_3

0009 00:02:09 HANA_DATA_4

15

15

Two pools are sufficient to provide storage and throughput for all supported storage sizes. Pool 0 is used to create virtual volumes (V-Vols) for OS, data and shared binaries. Pool 1 is used to create virtual volumes for log. Additional RAID groups and pool volumes can be added to increase the size of Pool 0 to support higher memory configurations. Table 10 shows the disk configuration of the storage subsystem for the different memory sizes of this solution. Mixed memory DIMM solutions will leverage the same storage design.

TABLE 10. DISK CONFIGURATION FOR DIFFERENT MEMORY SIZES

Memory Sizes Figure

384, 768, 1536, and 3072 GB Figure 7 on page 16

Greater than 3072 GB to 6144 GB Figure 8 on page 17

Greater than 6144 GB to 9216 GB Figure 9 on page 18

12288 GB Figure 10 on page 19

16

16

Figure 7

17

17

Figure 8

18

18

Figure 9

19

19

Figure 10

Storage Configuration for VSP F350 and VSP G350The SAP HANA node requires the following storage layout:

Operating system volume

SAP HANA shared volume for the SAP HANA binaries and other configuration files

Log volume

Data volume

This reference setup utilizes a dynamic provisioning pool design for the storage layout that ensures maximum utilization and optimization at a lower cost.

20

20

Use two dynamic provisioning pools with the specific parity groups listed in Table 11 for the storage layout.

The example layout in Table 12 uses the dynamic provisioning pool layout on Virtual Storage Platform F350 or VSP G350 for a SAP HANA Appliance solution with a 3 TB scale-up system.

TABLE 11. DYNAMIC PROVISIONING POOLS

Dynamic Provisioning Pool Name Purpose Parity Group RAID Level and Disks

OS_SH_Data_Pool Operating system LUN

SAP HANA shared LUN

Data LUN

RAID-6 (6D+2P) on 1.92 TB, SSD drives

Log_Pool Log LUN RAID-10 (2D+2D) on 1.92 TB, SSD drives

TABLE 12. DYNAMIC PROVISIONING POOL FOR SAP HANA VSP F350 AND VSP G350

Dynamic Provisioning Pool

Parity Group ID

Parity Group RAID Level and Disks LDEV ID LDEV Name

LDEV Size (GB)

MPU Assignment

OS_SH_Data_Pool 1 RAID-6 (6D+2P) on 1.92 TB SSD drives

00:00:01 OS_SH_DA_Pool_1 2640 MPU-10

00:00:02 OS_SH_DA_Pool_2 2640 MPU-20

00:00:03 OS_SH_DA_Pool_3 2640 MPU-10

00:00:04 OS_SH_DA_Pool_4 2640 MPU-20

OS_SH_Data_Pool 3 RAID-6 (6D+2P) on 1.92 TB SSD drives

00:00:05 OS_SH_DA_Pool_5 2640 MPU-10

00:00:06 OS_SH_DA_Pool_6 2640 MPU-20

00:00:07 OS_SH_DA_Pool_7 2640 MPU-10

00:00:08 OS_SH_DA_Pool_8 2640 MPU-20

Log_Pool 2 RAID-10 (2D+2D) on 1.92 TB, SSD drives

00:01:01 Log_Pool_1 878 MPU-10

00:01:02 Log_Pool_2 878 MPU-20

00:01:03 Log_Pool_3 878 MPU-10

00:01:04 Log_Pool_4 878 MPU-20

21

21

Provision the virtual volumes for the operating system, SAP HANA shared, data, and log volumes following Table 13 for a SAP HANA solution with a 3 TB scale-up system.

Table 14 lists the LUN path assignment used when validating this environment.

TABLE 13. VIRTUAL VOLUMES FOR THE SAP HANA NODES

Dynamic Provisioning Pool

Virtual Volume ID Virtual Volume Name

Virtual Volume Size

MPU Assignment

OS_SH_Data_Pool 00:02:00 HANA_OS 100 GB MPU-10

00:02:01 HANA_SH 4608 GB MPU-20

Log_Pool 00:02:02 HANA_LOG_1 150 GB MPU-10

00:02:03 HANA_LOG_2 150 GB MPU-20

00:02:04 HANA_LOG_3 150 GB MPU-10

00:02:05 HANA_LOG_4 150 GB MPU-20

OS_SH_Data_Pool 00:02:06 HANA_DATA_1 4060 GB MPU-10

00:02:07 HANA_DATA_2 4060 GB MPU-20

00:02:08 HANA_DATA_3 4060 GB MPU-10

00:02:09 HANA_DATA_4 4060 GB MPU-20

TABLE 14. EXAMPLE LUN PATH ASSIGNMENT

LUN ID LDEV ID LDEV Name

0000 00:02:00 HANA_OS

0001 00:02:01 HANA_SH

0002 00:02:02 HANA_LOG_1

0003 00:02:03 HANA_LOG_2

0004 00:02:04 HANA_LOG_3

0005 00:02:05 HANA_LOG_4

0006 00:02:06 HANA_DATA_1

0007 00:02:07 HANA_DATA_2

0008 00:02:08 HANA_DATA_3

0009 00:02:09 HANA_DATA_4

22

22

Two pools are sufficient to provide storage and throughput for all supported storage sizes. Pool 0 is used to create virtual volumes (V-Vols) for OS, data and shared binaries. Pool 1 is used to create virtual volumes for log. Additional RAID groups and pool volumes can be added to increase the size of Pool 0 to support higher memory configurations. Table 15 shows the disk configuration of the storage subsystem for the different memory sizes of this solution. Mixed memory DIMM solutions will leverage the same storage design.

TABLE 15. DISK CONFIGURATION FOR DIFFERENT MEMORY SIZES ON VSP F350 AND VSP G350

Memory Sizes Figure

384, 768, 1536, and 2304 GB Figure 11 on page 23

3072 GB to 4068 GB Figure 12 on page 24

6144 GB to 6912 GB Figure 13 on page 25

9216GB to 12288 GB Figure 14 on page 26

23

23

Figure 11

24

24

Figure 12

25

25

Figure 13

26

26

Figure 14

SAP HANA ConfigurationThis describes how to configure SAP HANA in this solution.

File SystemThe implementation of this solution uses an external storage sub-system:

BTRFS Filesystem

Operating system volume

XFS Filesystem

SAP HANA shared volume

Data volume

Log volume

27

27

Device-Mapper Multipath This solution uses Device-Mapper Multipath to consolidate the multiple connections coming from external storage sub-systems.

SAP HANA Software InstallationAfter configuring the file system for the SAP HANA data volume and log volume, install the latest SAP HANA 2.0 SPS stack on the server.

Install the following SAP HANA software components on the server:

Database

Client

Agent

Engineering ValidationTThe test methodology for validating the appliance configuration using Hitachi Advanced Server DS7000 on enterprise storage configuration with Hitachi Virtual Storage Platform F350, VSP G350, and VSP G200 used the following:

SAP HANA Hardware Configuration Check Took (HWCCT) using FSPERF revision hwcct-212_5 tested on these volumes for SLES 12 SP3, SLES 12 SP4, RHEL 7.4, and RHEL 7.6 Data volume:

Data volume

Log volume

For optimal use of SAP HANA database, use the parameters listed in the corresponding appendix for your operating system release. Follow SAP Note 2399079 to set up these parameters defined in global.ini for SAP HANA 2.0.

28

28

Appendix 1The following is a sample global.ini file configured and used for validation on SLES12SP3 and SLES12SP4 appliance solution:

[communication]

tcp_backlog = 2048

[fileio]

max_parallel_io_requests[data] = 64

max_submit_batch_size[data] = 64

size_kernel_io_queue[data] = 512

async_read_submit[data] = on

async_write_submit_blocks[data] = all

min_submit_batch_size[data] = 16

async_write_submit_active[data] = auto

max_parallel_io_requests[log] = 64

max_submit_batch_size[log] = 64

size_kernel_io_queue[log] = 512

async_read_submit[log] = on

async_write_submit_blocks[log] = all

min_submit_batch_size[log] = 16

async_write_submit_active[log] = auto

[multidb]

mode = multidb

database_isolation = low

singletenant = yes

[persistence]

basepath_datavolumes = /hana/data/HIT

basepath_logvolumes = /hana/log/HIT

29

29

Appendix 2 The following is a sample global.ini file configured and used for validation on RHEL 7.4 and RHEL 7.6 appliance solution:

[communication]

tcp_backlog = 2048

[fileio]

max_parallel_io_requests[data] = 64

max_submit_batch_size[data] = 64

size_kernel_io_queue[data] = 512

async_read_submit[data] = on

async_write_submit_blocks[data] = all

min_submit_batch_size[data] = 16

async_write_submit_active[data] = auto

max_parallel_io_requests[log] = 64

max_submit_batch_size[log] = 64

size_kernel_io_queue[log] = 512

async_read_submit[log] = on

async_write_submit_blocks[log] = all

min_submit_batch_size[log] = 16

async_write_submit_active[log] = auto

[multidb]

mode = multidb

database_isolation = low

singletenant = yes

[persistence]

basepath_datavolumes = /hana/data/HIT

basepath_logvolumes = /hana/log/HIT

1

Corporate Headquarters2535 Augustine DriveSanta Clara, CA 95054 USAHitachiVantara.com | community.HitachiVantara.com

Contact InformationPhone: 1-800-446-0744Sales: 1-858-225-2095HitachiVantara.com/contact

Hitachi Vantara

© Hitachi Vantara Corporation, 2019. All rights reserved. HITACHI is a trademark or registered trademark of Hitachi, Ltd. All other trademarks, service marks, and company names are properties of their respective owners

Notice: This document is for informational purposes only, and does not set forth any warranty, expressed or implied, concerning any equipment or service offered or to be offered by Hitachi Vantara Corporation.

MK-SL-046-03, November 2019