Cisco UCS, SAP and HANA on Cloud
Click here to load reader
-
Upload
cisco-data-center-sdn -
Category
Technology
-
view
3.256 -
download
1
description
Transcript of Cisco UCS, SAP and HANA on Cloud
What you need to know about HANA and SAP on the clouds
Dr. Michael Missbach
Cisco SAP Competence Center
2012
© 2012 Cisco and/or its affiliates. All rights reserved. 2
What you should know about the speaker
Manager Cisco SAP Competence Center Walldorf
More than 15 years of experience with SAP infrastructures
Author of:
© 2012 Cisco and/or its affiliates. All rights reserved. 3
IO intensive applications may have performance issues with virtualization
Applications with fixed IP addresses and hardware dependent License Keys may have issues with
Cloud architectures
What you should know about the Cloud
© 2012 Cisco and/or its affiliates. All rights reserved. 4
removing the I/O bottleneck enables virtualization of large SAP databases
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
© 2012 Cisco and/or its affiliates. All rights reserved. 5
Iozone benchmark: “Read” performance on bare metal (16 MB of data different block sizes from 4 kb to 16 MB)
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
© 2012 Cisco and/or its affiliates. All rights reserved. 6
IOzone benchmark: “Read” performance on VMware(16 MB of data different block sizes from 4 kb to 16 MB)
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
© 2012 Cisco and/or its affiliates. All rights reserved. 7
IOzone benchmark: “Write” performance on VMware (16 MB of data different block sizes from 4 kb to 16 MB)
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
© 2012 Cisco and/or its affiliates. All rights reserved. 8
IO Latency Benefits• 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,12
VM-FEX 4000 10,00 20,52 -1,12 25,75 -5,20
© 2012 Cisco and/or its affiliates. All rights reserved. 9
Cisco Unified IO grant Bandwidth
• 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 Traffic3G/s
2G/s
3G/sLAN Traffic3G/s
3G/s
Storage Traffic4G/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
© 2012 Cisco and/or its affiliates. All rights reserved. 10
Cisco Unified IO reduce cabling
Traditional approach Unified approach
40% cost savings in cabling, fiber, patch cords and labor
© 2012 Cisco and/or its affiliates. All rights reserved. 11
SAP Labs Israel before Cisco UCS implementation
© 2012 Cisco and/or its affiliates. All rights reserved. 12
SAP Labs Israel after Cisco UCS implementation
© 2012 Cisco and/or its affiliates. All rights reserved. 13
Full Hardware Abstraction & Service Profiles
• 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 assituation demands
DB node 2
HTTP Server
Spare
ERP
DB node 1 DB node 4DB node 3
ERP
© 2012 Cisco and/or its affiliates. All rights reserved. 14
Full Hardware Abstraction & Service Profiles
• 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 assituation demands
DB node 2 HTTP Server ERP
DB node 1 DB node 4DB node 3
ERP
© 2012 Cisco and/or its affiliates. All rights reserved. 15
Full Hardware Abstraction & Service Profiles
• 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 assituation demands
DB node 2 HTTP Server ERP
DB node 1 DB node 4DB node 3
Service ProfileProfile Name = vmhost-cluster1-1
UUID = 12345678-ABCD-9876-5432-ABCDEF123456
Description = ESX4-1 – Host in Cluster 1
Network Side LAN Config
Adapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..
Number of NIC’s = VMware-Static-NIC-Policy
vNIC0 Switch = Switch A
vNIC0 Pin Group = SwitchA-pingroupA
vNIC0 VLAN Trunking = Disabled
vNIC0 Native VLAN = VLAN 100
vNIC0 MAC Address = 00:25:B5:00:01:01
vNIC0 Hardware Failover Enabled = No
vNIC0 QoS policy = VMware-QoS-policy
vNIC1 Switch = Switch B
vNIC1 Pin Group = SwitchB-pingroupA
vNIC1 VLAN Trunking = Disabled
vNIC1 Native VLAN = VLAN 100
vNIC1 MAC Address = 00:25:B5:00:01:02
vNIC1 Hardware Failover Enabled = No
vNIC1 QoS policy = VMware-QoS-policy
Policy 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 = RAID1
Scrub Policy = Scrub local disks only
•ç
© 2012 Cisco and/or its affiliates. All rights reserved. 16
Full Hardware Abstraction & Service Profiles
• 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 assituation demands
DB node 2 HTTP Server ERP
DB node 1 DB node 4DB node 3
Service ProfileProfile Name = vmhost-cluster1-1
UUID = 12345678-ABCD-9876-5432-ABCDEF123456
Description = ESX4-1 – Host in Cluster 1
Network Side LAN Config
Adapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..
Number of NIC’s = VMware-Static-NIC-Policy
vNIC0 Switch = Switch A
vNIC0 Pin Group = SwitchA-pingroupA
vNIC0 VLAN Trunking = Disabled
vNIC0 Native VLAN = VLAN 100
vNIC0 MAC Address = 00:25:B5:00:01:01
vNIC0 Hardware Failover Enabled = No
vNIC0 QoS policy = VMware-QoS-policy
vNIC1 Switch = Switch B
vNIC1 Pin Group = SwitchB-pingroupA
vNIC1 VLAN Trunking = Disabled
vNIC1 Native VLAN = VLAN 100
vNIC1 MAC Address = 00:25:B5:00:01:02
vNIC1 Hardware Failover Enabled = No
vNIC1 QoS policy = VMware-QoS-policy
Policy 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 = RAID1
Scrub Policy = Scrub local disks only
•ç
© 2012 Cisco and/or its affiliates. All rights reserved. 17
Full Hardware Abstraction & Service Profiles
• 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 assituation demands
DB node 2 HTTP Server
ERP
DB node 1 DB node 4DB node 3
© 2012 Cisco and/or its affiliates. All rights reserved. 18
Full Hardware Abstraction & Service Profiles 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
Prd EP
Prd CRM
Prd BW
Prd ECC
Prd XI
Prd SRM
© 2012 Cisco and/or its affiliates. All rights reserved. 19
Full Hardware Abstraction & Service Profiles 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
Prd EP
Prd CRM
Prd BW
Prd ECC
Prd XI
Prd SRM
Service ProfilesProfile Name = vmhost-cluster1-1
UUID = 12345678-ABCD-9876-5432-ABCDEF123456
Description = ESX4-1 – Host in Cluster 1
Network Side LAN Config
Adapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..
Number of NIC’s = VMware-Static-NIC-Policy
vNIC0 Switch = Switch A
vNIC0 Pin Group = SwitchA-pingroupA
vNIC0 VLAN Trunking = Disabled
vNIC0 Native VLAN = VLAN 100
vNIC0 MAC Address = 00:25:B5:00:01:01
vNIC0 Hardware Failover Enabled = No
vNIC0 QoS policy = VMware-QoS-policy
vNIC1 Switch = Switch B
vNIC1 Pin Group = SwitchB-pingroupA
vNIC1 VLAN Trunking = Disabled
vNIC1 Native VLAN = VLAN 100
vNIC1 MAC Address = 00:25:B5:00:01:02
vNIC1 Hardware Failover Enabled = No
vNIC1 QoS policy = VMware-QoS-policy
Policy 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 = RAID1
Scrub Policy = Scrub local disks only
© 2012 Cisco and/or its affiliates. All rights reserved. 20
Full Hardware Abstraction & Service Profiles 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
Prd EP
Prd CRM
Prd BW
Prd ECC
Prd XI
Prd SRM
Service ProfilesProfile Name = vmhost-cluster1-1
UUID = 12345678-ABCD-9876-5432-ABCDEF123456
Description = ESX4-1 – Host in Cluster 1
Network Side LAN Config
Adapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..
Number of NIC’s = VMware-Static-NIC-Policy
vNIC0 Switch = Switch A
vNIC0 Pin Group = SwitchA-pingroupA
vNIC0 VLAN Trunking = Disabled
vNIC0 Native VLAN = VLAN 100
vNIC0 MAC Address = 00:25:B5:00:01:01
vNIC0 Hardware Failover Enabled = No
vNIC0 QoS policy = VMware-QoS-policy
vNIC1 Switch = Switch B
vNIC1 Pin Group = SwitchB-pingroupA
vNIC1 VLAN Trunking = Disabled
vNIC1 Native VLAN = VLAN 100
vNIC1 MAC Address = 00:25:B5:00:01:02
vNIC1 Hardware Failover Enabled = No
vNIC1 QoS policy = VMware-QoS-policy
Policy 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 = RAID1
Scrub Policy = Scrub local disks only
© 2012 Cisco and/or its affiliates. All rights reserved. 21
Full Hardware Abstraction & Service Profiles 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
QA EP
QA CRM
QA BW
QA ECC
QA XI
QA SRM
no need for complex scripts to make cluster SAP “aware”
no need for cluster software to grant HW availability
© 2012 Cisco and/or its affiliates. All rights reserved. 22
• 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 applications
Unified IO, Unified Management, Stateless Computing
DB node 2
HTTP Server
Spare
ERP
DB node 1 PIDB node 3
ERP
Cloud on UCS
BW
CRMPrint
SharePoint
© 2012 Cisco and/or its affiliates. All rights reserved. 23
What is the strategy behind HANA ?
integration
SOA
R/3 3.1
in-Memory
Business Suite & NetWeaver on HDB
BI on HANA
ECC on HANA LVM
mySAP.com
new dimension
mySAP
NetWeaver
Enjoy
B2B
CRM 4
Online Store SFA
BI 3.x XI R/3 4.7 SCM 4
R/3 4.5
R/3 4.6
CCMS
EP 7
BCITSBBP
EBP
SCM 7 SRM 7 CRM 7
MI PIMDM ACC
ECC 6.x
R/3 4.0
WP
BI 7
APOlifeCache
Business Suite
SSM
EP 4.0TREX
BWA
BW
MSA
CRM on HANA MP
Sybase, Afaria, NW Gateway
Ariba
“Great unification”
© 2012 Cisco and/or its affiliates. All rights reserved. 24
From the drawing boardUnder the hood:
What is the technology that make HANA so fast?
© 2012 Cisco and/or its affiliates. All rights reserved. 25
hybrid raw/column orientation
© 2012 Cisco and/or its affiliates. All rights reserved. 26
What makes HANA so fast?
The right mix of technologies
• In memory: approx 10 times faster
Any DB becomes faster if you run it in memory
• The right architecture for analytics: 100 times faster
Sybase IQ (disk based) is approx 100 times faster than traditional row orientated databases
Transactional load (ECC, CRM) becomes only 2 to 3 times faster
• Optimization for the Intel E7 Cache structure
Tests on E5 show sub-optimal performance (approx 20% less)
• Best of both worlds: Two databases under one hood
© 2012 Cisco and/or its affiliates. All rights reserved. 27
The HANA challengesSAP defines HANA as a „appliance like“
• ready to run solution like a instant soup: power up, add license, consume
• The mandatory HW and SW components didn’t fit to most datacenter standards: not an island but an alien in most datacenter’s
Only Intel Xeon X7560 or E7-X870 CPUs and Suse Linux Enterprise Server 11
Switches and storage, even the rack is a fixed part of the solution
• As soon the appliance is handed over to the customer it has to be maintained and patched like any SAP system
• No resource sharing with other applications, no multi-tenantServer, Network and Storage resources are dedicated for SAP HANA
• One Appliance per SAP HANA System (SID)For a usual PRD-QAS-DEV landscape three “appliances” are recommended.At least two “appliances” are required if QAS and DEV runs on one together.
© 2012 Cisco and/or its affiliates. All rights reserved. 28
What can HANA do for yourbusinessGlobal 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
© 2012 Cisco and/or its affiliates. All rights reserved. 29
why HANA?
• Performance, Performance, Performance!!!
In-Memory: removes I/O overhead – even with the best storage technology, this is the #1 culprit for performance issues
Columnar: fastest query operations for typical reporting workloads
Low-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
29
© 2012 Cisco and/or its affiliates. All rights reserved. 30
HANA Infrastructure• 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
© 2012 Cisco and/or its affiliates. All rights reserved. 31
Why Cisco?
• Innovative software solutions requires innovative infrastructure
• Cisco Unified Computing System (UCS)
Simplifies Management and scalability of X86 based architecture
Quick install (5 HANA systems installed in 5 days at 2 locations)
• SAP Global Technology Partner
Cisco has been working with SAP on HANA since 2010
Resourcing in Walldorf, San Jose, Bangalore
Medium configuration deployed by top SAP customers
Deployment in Cisco internal IT on the way
• Faster delivery than all other HW vendors
© 2012 Cisco and/or its affiliates. All rights reserved. 32
Cisco HANA Solutions
© 2012 Cisco and/or its affiliates. All rights reserved. 33
Cisco Servers Details
Cisco UCS C260 M2 Rack Server
2 x 2.4 GHz Intel Xeon E7-2870 CPU
256 or 128 GB 1066 MHz RDIMM
6 x 100 GB SSD SAS Drive
2 x LSI MegaRAID Controller 9261-8i
10 x 600 GB SAS Drive
Will be also validated for 32 GB licensed memory
Cisco UCS C460 M2 Rack Server
4 x 2.4 GHz Intel Xeon E7-4870 CPU
512 GB 1066 MHz RDIMM
2 x FusionIO 320GB MLC PCI-X card
1 x LSI MegaRAID Controller 9260-8i
12 x 300 GB SAS Drive
Also validated for 256 GB licensed memory
Balanced infrastructure for SAP HANA systems up to 512 GB
Validated since Q2 2011
SAP S, XS size
SAP M-size
© 2012 Cisco and/or its affiliates. All rights reserved. 34
Cisco scale out-solutions for unlimited scalability and availability
Blades RAMloadable dataset
3-to-1Compression
5-to-1 compression
7-to-1 compression
2 active + stand-by 1 TB 3 TB 5 TB 7 TB
3 active + stand-by 1.5 TB 4.5 TB 7.5 TB 10.5 TB
4 active + stand-by 2 TB 6 TB 10 TB 14 TB
8 active + stand-by 4 TB 12 TB 20 TB 28 TB
16 active + stand by 8 TB 24 TB 40 TB 56 TB
40 active + stand-by 20 TB 60 TB 100 TB 140 TB
240 active + stand-by 120 TB 360 TB 600 TB 840 TB
© 2012 Cisco and/or its affiliates. All rights reserved. 35
Typical HANA scale out architecture• Plenty of nodes and switches to manage and maintain
• Complex cabling
10 GbE data
1 GbE Mgmt
Mgmt Point
1 GE switches for mgt
10 GE switches for Data & GPFS
10 GbE GPFS
© 2012 Cisco and/or its affiliates. All rights reserved. 36
Cisco HANA scale out architecture
UCS
Max 16 active servers - 1-4x active or standby server per Chassis
Mgmt Point
Storage array Storage array Storage array Storage array
ManagementCorp-LAN
1 GbE
10 GbE
© 2012 Cisco and/or its affiliates. All rights reserved. 37
Example with EMC: 6 TB usable memory for 18 to 42 TB data
Cisco Components2 * Nexus 5548UP 10 GB Switches2 * Nexus 2224 Fabric Extender2 * UCS 6248UP Fabric Interconnect12 *Cisco Blades B440 M2
4 * E7-4870 (10 cores) 512GB DRAM, 2VIC cards
3 * 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
© 2012 Cisco and/or its affiliates. All rights reserved. 38
Example with NetApp storage : 16 TB usable memory for 48 to 112 TBCisco Components2 * Nexus 5548UP 10 GB Switches2 * Nexus 2224 Fabric Extender2 * UCS 6248UP Fabric Interconnectx*Cisco Blades B440 M2
4 * E7-4870 (10 cores) 512GB DRAM, 2VIC cards
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
© 2012 Cisco and/or its affiliates. All rights reserved. 39
Driving collaborative Innovation!
HANA CoE LAB
© 2012 Cisco and/or its affiliates. All rights reserved. 40
From the drawing boardUnder the hood:
availabilityfor HANA
“Because main memory is volatile you need something where data persists when power goes down and memory get‘s Alzheimer disease.” Michael Missbach
© 2012 Cisco and/or its affiliates. All rights reserved. 41
SAP HANA Architecture Overview
• 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
Click icon to add pictureHANA
In-Memory Database
Calculation and Planning
Engine
Row and Columnar Storage
LogData
Persistence Layer (Disk)
Persistence Layer
© 2012 Cisco and/or its affiliates. All rights reserved. 42
External Storage
Single HANA Instance
HANA Node
HA for HANA
D L
DB
HANA Node
D L
DB
HANA Node
D L
DB
HANA Node
DB
Worker Worker Worker Standby
© 2012 Cisco and/or its affiliates. All rights reserved. 43
External Storage
Single HANA Instance
HANA Node
HA for HANA
DB
HANA Node
DB
HANA Node
DB
HANA Node
DB
Worker Worker Worker Standby
D L D L D L
© 2012 Cisco and/or its affiliates. All rights reserved. 44
External Storage
Single HANA Instance
HANA Node
HA for HANA
DB
HANA Node
DB
HANA Node
DB
HANA Node
DB
Worker Worker Worker
D L D L D L
© 2012 Cisco and/or its affiliates. All rights reserved. 45
Hardware Abstraction & Service Profiles
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-1
UUID = 12345678-ABCD-9876-5432-ABCDEF123456
Description = HANA node 1
Network Side LAN Config
Adapter PCI Order = vNIC0 first, then vNIC1, then vHBA…..
Number of NIC’s = HANA-Static-NIC-Policy
vNIC0 Switch = Switch A
vNIC0 Pin Group = SwitchA-pingroupA
vNIC0 VLAN Trunking = Disabled
vNIC0 Native VLAN = VLAN 100
vNIC0 MAC Address = 00:25:B5:00:01:01
vNIC0 Hardware Failover Enabled = No
vNIC1 QoS policy = HANA-QoS-policy
Policy 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.
© 2012 Cisco and/or its affiliates. All rights reserved. 46
Cisco HANA Disaster Tolerance setup• 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 disaster
1. Stop Non-PRD
2. deploy service profile
3. 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
© 2012 Cisco and/or its affiliates. All rights reserved. 47
HANA monitoring by Cisco intelligent automation
• Cisco Intelligent Automation software supports the daily operation of a HANA appliance by:
• Monitoring the CPU and memory workload, and the average index read time at blade level
• Automating quarterly maintenance, including firmware updates and file system validation
• Ensuring configuration management assurance for all appliance components
• Monitoring data services availability
• Proactively monitoring HANA subsystem components status
• Monitoring query execution response times using the HANA index for the query execution HANA Query Response Time
• Executing sample queries and recording total execution time and query component performance breakdown
• Proactively monitoring the TREX services statistics based on thresholds
• Alerting CPU, memory, or throughput thresholds for TREX services
• Automating Cisco UCS blade and rack server provisioning for use in the appliance in minutes, instead of days
BW on HANA requiresBW release 7.3
BW 7.0,7.1, 7.2
Upgrade to BW 7.3
BW on HANA Implementation
Business users must wait, because a BW 7.3 upgrade can take many months
SAP’s global BW installed base has 12,000 companies
750 of these companies are on BW 7.3, the rest are on earlier versions
Ready for BW on HANA
Need Cisco’s Bridge To
SAP HANA Appliance
© 2012 Cisco and/or its affiliates. All rights reserved. 50
Switching & managementSwitching & management
Switching & management
Bridge to SAP HANA : Transition Example
BW 7.0 BW 7.36-12 Months
Functional Upgrade plus Data ModelRestructureDB2 DB2 HDB
BWA
BW 7.3
HDB
FAS3240FAS3240FAS3240FAS3240
QA and Regression Testing
E5 on B200
BWA, 1 Ch
E5 on B200
HANA, 1 Ch
E7 on B440
HANA
E7 on B440
E5 B200 The only HW component not transitioned to HANA Scaleout
Before During After
BW 7.3
© 2012 Cisco and/or its affiliates. All rights reserved. 51
Intelligent Automation for Cisco’s Bridge to SAP HANA BWAFor CIO’s
Streamline installation and setup
Fewer staff required to manage the appliance
Field-upgradable from the smallest appliance to the largest, and to HANA Scaleout
Multiple BWA instances in the same appliance
Minimizes down time
Lower operating costs and streamline support
Investment preservation in migrating to HANA
For Business Executives and Users
Provides in-memory query performance now
Ensures that loads are performed without incident
Maximizes performance and utilization
Minimizes down timeDual 40 Blade Configuration
© 2012 Cisco and/or its affiliates. All rights reserved. 52
5 main points for cost reduction• Unified Fabric
Less 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
© 2012 Cisco and/or its affiliates. All rights reserved. 53
Uniqueness of UCS for HANA 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
© 2012 Cisco and/or its affiliates. All rights reserved. 54
Uniqueness of UCS• 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
© 2012 Cisco and/or its affiliates. All rights reserved. 55
Summary: what customer like on UCS• 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 Tidal, 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