Beneficios de combinar el poder de Cisco y SAP HANA

Descubra los beneficios de combinar

el poder de Cisco y SAP HANA Roxana Diaz / Cisco Systems

Month 02, 2013

© 2013 SAP AG. All rights reserved. 2

Agenda

• Introducing SAP HANA

• Introducing Cisco for SAP HANA

• Cisco Single Server Solution for SAP HANA

• Cisco Scale-Out Solution with EMC for SAP HANA

• Cisco Scale-Out Solution with NetApp for SAP HANA

© 2013 SAP AG. All rights reserved. 3

Why Cisco for SAP HANA?

Innovative software solutions requires innovative infrastructure

Blade Server based Scale-Out Solution

Simplified Management for 40+ SAP HANA nodes

No internal Storage

Solutions with two key storage vendors (EMC and Netapp)

Proven storage technology with all nice features around Backup, HA and DR (or DT as called from SAP)

Cisco Orchestration Software

© 2013 SAP AG. All rights reserved. 4

Typical Blade architectures plenty of components to configure, managed and fail

• Redundant LAN and SAN Switches per enclosure

• Enclosure management system (typically a SPoF)

• Redundant top of the rack / end of the row LAN / SAN Switches

• Redundant System management servers

• Complex to configure and to extend without changing FC Zoning …

• Complex application specific cluster solution

• SAP Licence keys still bound to physical hardware

Mgmt Server

© 2013 SAP AG. All rights reserved. 5

Cisco UCS reduce complexity

what's not there must not be managed and can’t fail

Cisco architecture eliminates complete layers

• Integrated LAN/SAN ports extended down to the enclosure – “one

hop” switching

• Fabric-Switches manage the whole row

• Extreme easy to extend without changing the FC

Zoning using Service profiles

• 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 Software

© 2013 SAP AG. All rights reserved. 6

Distributed Architecture

•Wire once for bandwidth, not connectivity

•Policy-driven bandwidth allocation

•All links can be active all the time

•Integrates as a single system into your data center

20Gb/s 40Gb/s 80Gb/s 2x 4 Link 80 Gbps per Chassis

2x 8 Links 160 Gbps per Chassis

2x 2 Link 40 Gbps per Chassis

2x 1 Link 20 Gbps per Chassis

© 2013 SAP AG. All rights reserved. 7

Unified, Embedded Management Aligns People, Policy, and Configuration With Workload

Server Policy…

Storage Policy…

Network Policy…

Virtualization Policy…

Application Profiles…

Subject Matter Experts Define Policies

Storage SME

Server SME

Network SME

Policies Used to Create

Service Profile Templates

Service Profile Templates

Create Service Profiles

Associating Service Profiles with Hardware

Configures Servers Automatically

Unified Management

ECC (Prod)

UUID, MAC, WWN Boot Information

LAN, SAN Config

Firmware Policy

CRM (PROD) UUID, MAC, WWN

Boot Information

LAN, SAN Config

Firmware Policy

BPM / Portals (QA) UUID, MAC, WWN

Boot Information

LAN, SAN Config

Firmware Policy

BI (DEV) UUID, MAC, WWN

Boot Information

LAN, SAN Config

Firmware Policy

Server Name

UUID, MAC,

WWN

Boot Information

LAN, SAN Config

Firmware Policy

© 2013 SAP AG. All rights reserved. 8

Hardware State 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 as

situation demands

ServService Profiles Profile 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

vNIC0 QoS policy = HANA-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 = 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.

© 2013 SAP AG. All rights reserved. 9

Uniqueness of UCS

Dynamic provisioning with service

profiles and stateless blade server

SAP License Key is bound to the Service Profile

and not to the physical blade

Unified Fabric: low latency & high

throughput

Scale SAP HANA across multiple

Chassis without increasing IO latency

High available SAP operation without

scripting orgies

© 2013 SAP AG. All rights reserved. 10

Scale-Out concept with UCS

UCS

Max 16 active servers - 1-4x active or standby server per Chassis

Mgmt Point

Storage array Storage array Storage array Storage array

Management

Server

© 2013 SAP AG. All rights reserved. 11

Sample Configuration with 12 Blades

12* UCS B440 M2

3* EMC VNX5300

© 2013 SAP AG. All rights reserved. 12

Configuration details

• Redundant Infrastructure

No additional components for up to 36 server

Up to 60 server with Nexus 5596 and UCS 6296

• 1 Storage per 4 Active nodes

• PXE boot with NFS, no FC, no iSCSI

Validated for, but not limited to:

2 – 16 Active nodes

1 – X Standby nodes

© 2013 SAP AG. All rights reserved. 13

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

Thank You!

Contact information:

Roxana Diaz

CSE DC

[email protected]

52671823

© 2013 SAP AG. All rights reserved. 15

HANA monitoring by

Cisco Intelligent Automation

Supports the daily operation of a HANA appliance by:

Monitoring the CPU, memory, and the average index read time at blade level

Automating 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