HANA and all the rest of SAP on Cisco UCS · HANA and all the rest of SAP on Cisco UCS Dr. Michael Missbach Cisco SAP Competence Center. 2012

HANA and all the rest of SAP on Cisco UCS

Dr. Michael Missbach

Cisco SAP Competence Center

2012

© 2012 Cisco and/or its affiliates. All rights reserved. 2

Manager Cisco SAP Competence Center WalldorfMore than 15 years of experience with SAP infrastructures

Author of:


mySAP.com

new dimension

mySAP

NetWeaver

integration

Enjoy

SOA

B2B

CRM 4

Online Store SFA

BI 3.x XIR/3 4.7 SCM 4

R/3 3.1

R/3 4.5

R/3 4.6

CCMS

EP 7.0

BCITSBBP

EBP

SCM 7 SRM 7 CRM 7

MI PIMDM ACC

ECC 6.x

R/3 4.0

WP

BI 7

in-Memory

APOlifeCache

Business Suite

SSM

Business Suite & NetWeaver on HDB

BI on HANA

EP 4.0TREX

BWA

BW

SCM on HANA LVM

MPSybase, Afaria, NW Gateway

MSA

Presenter

Presentation Notes

What is Service Oriented Architecture (SOA)? SOA provides a modularity of logic that can be presented as a service for a client (client as in client-server architecture) and at the same time function as a client for other services. XML has been used extensively in SOA to create data which is wrapped in a nearly exhaustive description container. Analogously, the services themselves are typically described by WSDL, and communications protocols by SOAP. The goal of SOA then is to allow fairly large chunks of functionality to be strung together to form ad-hoc applications which are built almost entirely from existing software services. The great promise of SOA though, is that in this world, the marginal cost of creating the nth application is zero, as all of the software required already exists to satisfy the requirements of other applications. Only orchestration is required to produce a new application.


Cisco Servers Details

Cisco UCS C260 M2 Rack Server2 x 2.4 GHz Intel Xeon E7-2870 CPU256 or 128 GB 1066 MHz RDIMM6 x 100 GB SSD SAS Drive2 x LSI MegaRAID Controller 9261-8i10 x 600 GB SAS DriveWill be also validated for 32 GB licensed memory

Cisco UCS C460 M2 Rack Server4 x 2.4 GHz Intel Xeon E7-4870 CPU512 GB 1066 MHz RDIMM2 x FusionIO 320GB MLC PCI-X card1 x LSI MegaRAID Controller 9260-8i12 x 300 GB SAS DriveAlso validated for 256 GB licensed memory

Validated since Q2 2011

SAP S, XS size

SAP M-size

Presenter

Presentation Notes

Fusion i/o – 90k iops read / 60kiops random access


Global Complaint Handling (GCH)• A complaint is any communication that

alleges deficiencies related to the identity, quality, durability, reliability, safety, effectiveness or performance of a distributed device, and it’s associated labeling, packaging, or training materials.

• Analysis of 100.000 complaints to long even on a big AIX database machine because of long text handling

• No Single field storage and search capabilities


• Outperforming large AIX database servers

1 Cisco UCS C460 M1 – 32 Core 512GB 5 Cisco UCS C460s M2 – 40 Core 512GB

• Cisco Advanced Services installed and setup 5 HANA appliances at two different locations in 5 days.

• From first device install to go live in 20 weeks


• Performance, Performance, Performance!!!In-Memory: removes I/O overhead – even with the best storage technology, this is the #1 culprit for performance issuesColumnar: fastest query operations for typical reporting workloadsLow-Maintenance - no more maintenance for aggregates and indexes

• Multi-Source Data Acquisition – Best of Both Worlds!SAP & Non-SAP Sources - BW weakness overcome

• Long Text Handling – No problem!Large amounts of unstructured text data not easily handled by BW

Single field storage and search capabilities

7

Presenter

Presentation Notes

Performance - The clear #1 reason for adopting HANA at Medtronic was the performance gains we believe it will bring. This not only allows for faster response time, but also removes the IT overhead of maintaining aggregates, indexes and other activities to try to make the traditional systems perform. While there are a variety of reasons for the performance gains, I believe firmly in 2 of them: In-Memory - Even with the best storage technology available in the market, we continue to see I/O as the number one culprit for performance issues in our existing systems. By removing the disk access we believe a significant leap in performance will be attained. Columnar Database - There is no doubt that a columnar database provides a better structure for the types of database requests made on a data warehouse platform.


Cisco Components2 * Nexus 5548UP10 GB Switches2 * Nexus 2224 Fabric Extender2 * UCS 6248UP Fabric Interconnect12 *Cisco Blades B440 M2

4 * E7-4870 (10 cores) 512GB DRAM, 2VIC cards3 * UCS 5108 Blade Server Chassis6 * UCS 2104 Fabric Extender2 * C200 M3 for HANA Studio/Modeler, Management etc.1 * C2811 Integrated Service Router

EMC Components3 * DPE with 25 * 300GB SAS6 * DAE with 25 * 300GB SAS each12 * Onboard IO Ports12 * additional IO Ports Slot A0 (8Gbps)1 * Control Station6 * Data Mover (one active, one standby)3 * Standby Power Supply (SPS)1 * EMC 19” Rack for VNXSoftware

VNX OE for BLOCK 5.31.000.5.509VNX OE for FILE 7.0.40.1Local Protection Suite for VNX5300

Presenter

Presentation Notes

why EMC uses 75 disks in their HANA storage EMC use the smaller drives (300GB) compared to the 600GB in the others config. So, the total capacity is pretty similar depending on the Raid configuration EMC use the 2.5” SFF drives with high density disk shelfs 1 * 25 Disks in the DPE using 3U (rack units) 2 * 25 Disks in the DAEs each using 2U So, our disks use 7Us Datamovers, ControlStation, Batterie another use another 4U Our total rack space 11U The higher number of spindles in EMC config allows to separate IO traffic for Data and Log devices For our HANA v2 approach, we test the 2.5” 600GB drives.


Cisco Components2 * Nexus 5548UP10 GB Switches2 * Nexus 2224 Fabric Extender2 * UCS 6248UP Fabric Interconnectx*Cisco Blades B440 M2

4 * E7-4870 (10 cores) 512GB DRAM, 2VICcards

x * UCS 5108 Blade Server Chassisx * UCS 2104 Fabric Extender2 * C200 M3 for HANA Studio/Modeler, Management etc.1 * C2811 Integrated Service Router

NetApp Componentsx * FAS3240 HA

Presenter

Presentation Notes

NetApp uses the 3.5” 600GB drives 2 * 24 disks in a 4U disk enclosure Dualcontroller in a 3U Chasis NetApp total rack space is same: 11U Due to the nature of NetApps WAFL filesystem on the filers, their best performance will be achieved if all drives are in one single pool


Under the hood:

availabilityfor HANA

“Because main memory is volatile you need something where dat persists when power goes down and memory get‘s Alzheimer di ” Mi h l Mi b h

Presenter

Presentation Notes

HANA - High Performance Analytic Appliance HANA is a hardware and software combination integrating the new SAP Business Analytic Engine(BAE) software and delivered as an optimized hardware appliance. SAP is partnering with leading computer hardware manufacturers to deliver this next generation business analytics solution. The new solution will allow customers to do: accelerated BI scenarios off any data source; better operational planning, simulation and forecasting; fast analysis and better decision making off accelerated SAP ECC transactional data, better storage, search and ad-hoc analysis off very large data volumes BAE – Business Analytic Engine BAE combines an in-memory data base, a calculation engine and a modeling environment that allows for fast business analysis of an organization’s transactional and Analytic data from across, as well as outside, the entECCrise in near real-time. Leveraging the intelligent use of in memory technology, columnar database design, data compression and massive parallel processing, BAE allows the processing of massive amounts of data in near real-time


• Primary PersistenceIn-MemoryContents of tables (Data and Undo Log)

• Transaction LogAll changesCollected in 1MB in-memory blocksBlocks written to disk (Log Filesystem) when block is full or transaction commitedI/O Profile: Sequential Writes, 1MB Blocksize

• SavepointComplete Image of the in-memory databaseRegularly updates (5 min default)I/O Profile: Random Writes, variable blocksize

HANA

In-Memory Database

Calculationand Planning

Engine

Row andColumnarStorage

LogData

Persistence Layer (Disk)

Persistence Layer


SAP appliances like BWA and HANA have fixed IP addresses!

Service profiles enable move of appliance nodes to spare blades

Servers become secure interchangeable hardware components

ServService ProfilesProfile Name = hana-node-1UUID = 12345678-ABCD-9876-5432-ABCDEF123456Description = HANA node 1

Network Side LAN ConfigAdapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..

Number of NIC’s = HANA-Static-NIC-PolicyvNIC0 Switch = Switch A vNIC0 Pin Group = SwitchA-pingroupAvNIC0 VLAN Trunking = DisabledvNIC0 Native VLAN = VLAN 100vNIC0 MAC Address = 00:25:B5:00:01:01vNIC0 Hardware Failover Enabled = NovNIC1 QoS policy = HANA-QoS-policyPolicy for VM vNIC’s = 101_Policy, 102_Policy, 103_Policy...

Server Side LAN Config•HANA Networking= vNIC tied to Port-Group:•101_Policy, 102_Policy, 103_Policy, etc.

Presenter

Presentation Notes

Example use cases if a blade fails re-map the service profile to another blade; new blade looks identical to the OS/app Scale an ERP application up from a half-width to full-width blade Pools, policies and isolation Separate firmware, addresses, and parameter settings from server hardware Servers become interchangeable hardware components Pools – MAC, WWNN, Policies – boot order,m host firmware, local disk Isolation – VLAN,m VSAN, pin groups for northbound connections


• PRD HANA Storage replicated to an dedicated storage on the 2nd side

• Additional Storage for Non-PRD systems installed at 2nd side

• PRD Service Profiles talking with PRD storage only

• Non-PRD Service Profile talking with Non-PRD storage only

• In case of a disaster1. Stop Non-PRD2. deploy service profile3. Start PRD

• DC Network is a key factor (L2 / L3)

DC LANSAP app server SAP user

Act

ive

HA

NA

N

odes

QA

+

DE

V

HA

NA

S

tora

ge

Sta

ndby

H

AN

A

Sto

rage

QA

+ D

EV

B

acku

p

Replication


Cisco Appliance for SAP HANA

HANA Checklist – The HANA Checklist process checks overall HANA operational and performance system health.HANA Threads Check – The HANA Threads Check process monitors active HANA threads for long running requests.HANA Workload Monitoring - The HANA workload Monitoring process monitors HANA workload performance metrics.

Alerts & Events

HANA Alert Monitoring – The HANA Alert Monitoring process proactively monitors and notifies of HANA alerts.HANA Alerts – Automate Actions – The HANA Alerts – Automate Actions process automates the execution of recommended HANA operational corrective actions.Automation Benefits

Focus resources on delivering quality servicesReduce operational complexity for ITReduce high effort for landscape administration

One of the Cisco Process Orchestration Packs

Presenter

Presentation Notes

Key Points This software from Cisco is one of the Cisco Process Orchestration packs. That in turn is part of CIAC – Cisco Intelligent Automation for Cloud or Compute. This is mature software sold by Tidal until they were bought by Cisco. This is another great reason why Cisco can be of relevance to SAP and SAP users.


• SAP HANA & BWA Installation/Implementation Service

• Cisco Intelligent Automation for SAP (former Tidal SAP runbook automation) – Plan, Design, Implementation Services

• SAP technology project support- SAP certified technology consultancy- SAP certified OS/DB Migration consultancy

Cisco guided RISC to X86 migration Initiative- SAP on UCS, Vblock, Flexpod expertise- SAP virtualization expertise

Contact for Cisco Services for SAP: Konrad Lang ([email protected])

BW 7.x to BW on HANAMigration in Three Cost-Effective Steps

Bridge to SAP HANA Implementation

Run BWA

Upgrade to BW 7.3Database

Conversion

BW on HANA Implementation

Run HANA

Run In-Memory Queries NowSave Up to 90%


Unified Fabric reduce cabling by ½

Scale HANA across multiple chassis without increasing IO latency

Stateless Computing make Servers freely interchangeable hardware components

Service profiles enable “bare metal” move of appliance between datacenter

HANA specific monitoring software as part of the Cisco intelligent automation


IO intensive applications may have performance issues with virtualization

Applications with hardware dependent License Keys may have issues with Cloud architectures

Cloud computing for mission critical applications


Software based Virtual Switching Hypervisor needs to switch LAN and storage I/O Consumes additional CPU cycles Adds significant latency to I/O Practically prohibitive for virtualization of larger

databases (SAP note: if you run into performance trouble with virtualization: move to bare iron. If trouble disappears, this was the right Solution)

Hypervisor Soft Switch

VM VM VM VM

standard VIC

Cisco enables virtualization of large SAP Systems

VM-FEX(Hypervisor pass through mode)

VM VM VM VM

Cisco VIC running VM-FEX mode provides ASIC based low latency VM switch

10GbE/FCoE

10GbE/FCoE 0 1 2 3 56…………

Cisco solution: VM-FEX (Fabric Extender) Hypervisor vSwitch removal result in massive I/O

throughput improvements and less latency 10 Gb links don't consume CPU resources Each VM gets a dedicated PCI device (up to 56) Each VM gets a virtual port on physical switch end-to-end QoS per VM down to storage

Presenter

Presentation Notes

Virtual Switching: Server virtualization allows multiple OS images to transparently share the same physical server and I/O devices. As a consequence, it introduces the need to support local switching between different virtual machines within the same server. The most common way to solve this problem has been to implement a software based switch inside the physical host, inside the hypervisor Each VM gets a vNIC from the hypervisor and the vNIC is associated with a virtual port (or vETH) on the vSwitch. Traffic between VMs on the same host is switched locally within the host but traffic to a VM on a different host needs to still go thru the external physical switch. Palo is a Cisco ASIC processor. As such it represents a sustainable competitive edge over any thing a rival might produce. And it provides unrivaled flexibility in terms of supporting multiple network protocols while maintaining consistently high levels of performance Drivers currenty available for Vmware and KVM, soon for Citrix XEN, next Open XEN, later Hyper-V


1 10 100 1000 10000 100000

IO throughput (MB/s)6.000

5.000

1.000

4.000

3.000

2.000

0 Block size (KB)

Cisco UCS

existing server

More than double IO performance


1 10 100 1000 10000 100000

IO throughput (MB/S)

3.000

1.500

2.000

1.000

0 block size (KB)

Cisco UCS

3.500

2.500

500

significant higher IO performance

existing server


1 10 100 1000 10000 100000

IO throughput (MB/S)

Cisco UCS

50100150200250300350400450500

0 block size (KB)

1.5 – 4 times the Performance

existing server


• VM-FEX dramatically reduce the IO latency

• The Result is a significant better DB response time

• Do more with the same VM

• Improve user experience with Virtualized SAP systems

Used Switch technology # Users Diff %

DB Response time / Dialog processes Diff %

DB Response time / Update

process Diff %KVM-vswitch 3600 0,00 20,75 0,00 27,09 0,00

VM-FEX 3600 0,00 14,89 -39,36 21,31 -27,12VM-FEX 4000 10,00 20,52 -1,12 25,75 -5,20


• Near Wire Speed without CPU load (other Vendors reach ½ of nominal throughput and consume a core per NIC)

• dynamical bandwidth management according to SLA’s

• >270,000 IOPS at SAP typical 8KB block size (if Storage can cope up, measurements are done with SSD

3G/s HPC Traf f ic3G/s

2G/s

3G/sLAN Traf f ic3G/s

3G/s

Storage Traf f ic4G/s

5G/s3G/s

t1 t2 t3

IndividualEthernets

Individual Storage(IP, Eth, FC)

Server IO isn’t a Bottleneck anymore, even for Batch and BW


reduce cabling

Traditional approach Unified approach

40% cost savings in cabling, fiber, patch cords and labor


• Servers become secure interchangeable hardware components

• Easy to move Database nodes across server hardware No LAN, SAN Zoning or any reconfiguration

• Re-purpose hardware based on changing workloads Add Application Tier components or upgrade hardware as

situation demands

DB node 2

HTTP Server

Spare

ERP

DB node 1 DB node 4DB node 3

ERP

Service ProfileProfile Name = vmhost-cluster1-1UUID = 12345678-ABCD-9876-5432-ABCDEF123456Description = ESX4-1 – Host in Cluster 1


Number of NIC’s = VMware-Static-NIC-PolicyvNIC0 Switch = Switch A vNIC0 Pin Group = SwitchA-pingroupAvNIC0 VLAN Trunking = DisabledvNIC0 Native VLAN = VLAN 100vNIC0 MAC Address = 00:25:B5:00:01:01vNIC0 Hardware Failover Enabled = NovNIC0 QoS policy = VMware-QoS-policyvNIC1 Switch = Switch BvNIC1 Pin Group = SwitchB-pingroupAvNIC1 VLAN Trunking = DisabledvNIC1 Native VLAN = VLAN 100vNIC1 MAC Address = 00:25:B5:00:01:02vNIC1 Hardware Failover Enabled = NovNIC1 QoS policy = VMware-QoS-policyPolicy for VM vNIC’s = 101_Policy, 102_Policy, 103_Policy...

Server Side LAN Config•ESX Networking= VM vNIC tied to Port-Group:•101_Policy, 102_Policy, 103_Policy, etc.

Local Storage Profile = RAID1Scrub Policy = Scrub local disks only

Presenter

Presentation Notes



Advantage for SAP Systems

Enables movement of SAP instances without invalidating license key• SAP license key generated based HW parameters, for example the HBA WWNN

• UCS Service Profiles contain 96 attributes, including HBA WWNN (and the others)

• Example where complete HW state abstraction resolves application dependencies

no need for complex scripts to make cluster SAP “aware”

no need for cluster software to grant HW availability

Prd EP

Prd CRM

Prd BW

Prd ECC

Prd XIPrd SRM

QA EP

QA CRM

QA BW

QA ECC

QA XIQA SRM

Service ProfilesProfile Name = vmhost-cluster1-1UUID = 12345678-ABCD-9876-5432-ABCDEF123456Description = ESX4-1 – Host in Cluster 1


Number of NIC’s = VMware-Static-NIC-PolicyvNIC0 Switch = Switch A vNIC0 Pin Group = SwitchA-pingroupAvNIC0 VLAN Trunking = DisabledvNIC0 Native VLAN = VLAN 100vNIC0 MAC Address = 00:25:B5:00:01:01vNIC0 Hardware Failover Enabled = NovNIC0 QoS policy = VMware-QoS-policyvNIC1 Switch = Switch BvNIC1 Pin Group = SwitchB-pingroupAvNIC1 VLAN Trunking = DisabledvNIC1 Native VLAN = VLAN 100vNIC1 MAC Address = 00:25:B5:00:01:02vNIC1 Hardware Failover Enabled = NovNIC1 QoS policy = VMware-QoS-policyPolicy for VM vNIC’s = 101_Policy, 102_Policy, 103_Policy...

Server Side LAN Config•ESX Networking= VM vNIC tied to Port-Group:•101_Policy, 102_Policy, 103_Policy, etc.

Local Storage Profile = RAID1Scrub Policy = Scrub local disks only


• UCS is fully certified for SAP (Blade and Rack server)

• Windows, Linux, Vmware, Citrix XenEnterprise, RedHat RHEV, …

• 30% better DB response time with VM-FEX vs soft switching !

• UCS infrastructure benefits are also valid for SAP applicationsUnified IO, Unified Management, Stateless Computing

DB node 2

HTTP Server

Spare

ERP

DB node 1 PIDB node 3

ERPBW

CRMPrint

SharePoint

Presenter

Presentation Notes



• Cisco Automation reduce complexity of day to day operationSAP run book automation (best practises “poured into software”)SAP System Copy to auto-refresh QA landscapes (ABAP and Java) SAP batch chain control

• ECC Satellite System RefreshFrom 2 hours every weekend including up to 50 individual operator steps for setup and confirmation to 15 min for a fully automated refresh with a summary for audit purposes of all post-copy system validations.

• SAP transaction BDLS – Logical System ConversionFrom 31 hours to perform 3 Logical system conversions on a Multi-terabyte Mainframe system with tables in the range of 60 to 94 million rows each to 7 hours on same hardware with Tidal process automation


• Unified FabricLess infrastructure components - less power, cooling, admin effort

• Unified ManagementLess devices to manageLess cost for implementation and administration

• Orchestration by Service ProfilesFast implementation and extensionEfficient distribution of compute resources

• Extended Memory TechnologyMore virtual machines - less server’sAbility to use less extensive memory

• FEX– Virtual Interface CardLess adapter per ServerAbility to virtualize complete SAP landscapes including the database


• Extreme easy to extend without changing the FC Zoning anymore– just connect fabric interconnect once to the existing DC infrastructure and add blades as you go

• 15 minutes to add Chassis or Blades (UCSM auto-discovery)• 10 minutes to configure up to 56 virtual NICs and HBAs per blade• 10 minutes to add an ESX server using Templates & PXE Boot• 10 minutes to add an SAP App server using CIA, cloning of QA systems• Application mobility through Service Profiles

– no need to generate new SAP license keys after system move– no need for cluster software to grant HW availability

• Palo Adapter: ASIC based low latency switch replaces Hypervisor soft switch• up to 56 virtual NICs and HBAs per blade dynamically configurable • 2 x 10GB (8 x 10GB mid of 2011)• Collapses virtual and physical switching layers• Massive I/O throughput improvements (less latency, interrupts, CPU cycles) • Enables end-to-end QoS per VM down to storage• Enables virtualization of large SAP databases

• I/O consolidation with standard FCoE, less Cables, less Ethernet & FC Ports


• Dynamic provisioning with service profiles and stateless blade server

• Unified Fabric: low latency & high throughput

• High available SAP operation without scripting orgies

• Virtualization without IO bottleneck

Documents

HANA and all the rest of SAP on Cisco UCS · HANA and all the rest of SAP on Cisco UCS Dr. Michael Missbach Cisco SAP Competence Center. 2012