vale - indicative price - sap bpc, srm & mobile - technical presentation - v-2.3

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.

One Sap Vale BW-BPC, SRM and Mobile Infrastructure Solutions

August 06 , 2012 Carlos Arca, Edmar Borges, Alexandre Benini

© Copyright 2012 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.2

AgendaBW-BPC, SRM and Moblie infrastructure

• Alignment of the technical solution;

• Macro timeline for implementation;

• RU / Volume alignment;


DisclaimersCONFIDENTIALITY STATEMENT

This statement ensures Vale that HP shall maintain absolute secrecy of the facts (Procedures and Values) that shall be disclosed to HP. This information shall be used for HP procedures only. The activities comply with the Installment of Service Contract, which shall not be disclosed to others without prior consent from Vale.PROPERTY STATEMENT

The information contained in this document, especially prepared for Vale, is confidential and belongs to HP. HP presents this document on the understanding that it shall be maintained in strict confidentiality by Vale, which shall only use it for evaluation of the services proposed.Vale should not disclose the subject matter of this document or the items here described, including organizational concepts, and should neither duplicate it nor use it for other purposes without formal consent from HP. Upon confirmation of the proposed service as here described, through an HP contract, such contract shall establish the conditions for usage of such information.PROPOSAL STATEMENT

This document was prepared in order to provide general information about the services that HP shall be able to offer. More specific terms and conditions shall be defined in the agreement for the services.This document is not a legally binding offer of services. Therefore, its acceptance does not constitute any contractual obligation. HP has the commitment to negotiate in good faith an agreement that fairly represents a business contract of mutual acceptance. No legal obligation for HP shall exist until the agreement is duly signed by HP.


BW-BPC


Sizing x Servers configurationBW-BPC

Sizing:

Servers configurations:

Important: Memory are adjusted 16GB/Core because hardware performance, and core for Apps are based (N, N +N), where +N is stand-by server, then 16 cores will be configuration (8, 8 +8) = 24 are needed;

SAP application

System Role

Target Server Qty O.S. Recommended

Config/server Scenario 1

BW-LSA + BPC

DB/CI Cluster

SD-2 1 vPar

HP-UX 14 cores, 128GB

SD-2 1 vPar


APP Servers Bl890 i2 2 HP-

UX 16 cores, 256GB Scenario 2

BW-LSA + BPC

DB/CI Cluster

SD-2 1 vPar


SD-2 1 vPar


APP Servers Bl890 i2 2 HP-

UX 28 cores, 256GB

Phase Action Item

TypeEnvir

.Instanc

e Function Platform Hostname O.S.Core Initia

lMemory Initial

Core Sized

Memory Sized

Core Adde

d

Memory

AddedHardware required RU by

socket

1(+) add HW PRD LP0, LPJ db SD2-1 CATOR2ENCLUS011/

VLUNX045HP-UX 8 128 14 224 6 961/2 - SD2 BL - 2 quad proc. x 128gb Small

1 (+) add HW PRD LP0, LPJ db SD2-3 CATOR2ENCLUS013/

VLUNX046HP-UX 8 128 14 224 6 961/2 - SD2 BL - 2 quad proc. x 128gb Small

1 (+) add HW DR LP0, LPJ db SD2-5 CAMKH1ENCLUS003/

CAVACN36HP-UX 8 128 14 224 6 961/2 - SD2 BL - 2 quad proc. x 128gb Small

1 (+) add HW DR LP0, LPJ apps Bl890C i2 -

stacked NEWSERVER01 HP-UX 6 48 16 256 10 208 Using BL890C I2 ordered @ Mobile

Phase 1 (MCC) Medium

1(+) add HW PRD LP0, LPJ apps Bl890C i2 -

stacked NEWSERVER02 HP-UX 9 72 24 384 15 312 1x Physical BL890C I2 to SCC Medium

2(+) expand HW PRD LP0,

LPJ db SD2-1 CATOR2ENCLUS011/VLUNX045

HP-UX 14 224 16 256 2 32Using Blades SD-2 ordered @ Phase 1 Small

2 (+) expand HW PRD LP0,

LPJ db SD2-3 CATOR2ENCLUS013/VLUNX046


2 (+) expand HW DR LP0,

LPJ db SD2-5 CAMKH1ENCLUS003/CAVACN36


2 (+) expand HW DR LP0,

LPJ apps Bl890C i2 - stacked NEWSERVER01 HP-

UX 16 256 28 384 12 128 1x Physical BL890C I2 Medium

2(+) expand HW PRD LP0,

LPJ apps Bl890C i2 - stacked NEWSERVER02 HP-

UX 24 384 42 576 18 192 1x Physical BL890C I2 Large


Core and memory configuration for LP0/LPJ AppsBW-BPC

Current Scenario 1Scenario 2

PRD:

DR:

vlunx003 vlunx010 cavavs0

803cores x 24GB

03cores x 24GB

03cores x 24GB

= 06 cores x 48 GB (sizing) HA (N+1)

vlunx027 vlnux02503cores x

24GB03cores x

24GB= 06 cores x 48GB (sizing)

vlnux003/010 cavavs08 newserver

02

08cores x 128GB

08cores x 128GB

08cores x 128GB


vlunux027/025

newserver01

08cores x 128GB

08 cores x 128GB

= 16 cores x 256GB (sizing)

Vlnux003/010 cavavs08 newserver

02

14cores x 192GB

14cores x 192GB

14cores x 192GB

= 28 cores x 384GB (sizing) HA (N+1)

vlunx027/025

newserver01

14cores x 192GB

14cores x 192GB



BW-BPCPhase 1

Hardware:• Installation of 03 Physical SD-2 blade on PRD/DR for LP0/LPJ DB/CI;• Installation of 02 Physical BL890Ci2 blade on PRD/DR for LP0/LPJ Apps

Operating Systems:• Installation of 02 (two) O.S. Instances in PRD/DR LP0/LPJ Apps;• Support for hardware installation of 02 Physical SD-2 blade on PRD/DR

for LP0/LPJ DB/CI;

Sap DB/CI and Apps:• Support for hardware installation for 02 Physical SD-2 blade on

PRD/DR for LP0/LPJ DB/CI;• Installation of 04 (four) APPS instances in new Physical BL890Ci2

blade on (02) PRD and (02) DR for LP0/LPJ Apps;• Adjustments in 10 (ten) APPS instances in re-size of proc. and

memory;

Installation and/or expansionPhas

eInstanc

eEnvi

r.Func

t.Action Type Action Hardware O.S

.D.B.

SAP CI

SAP App

s1 2 14

LP0, LPJ DR apps HW (+) add 1/2 - Physical BL890C I2

OS image (+) add 1

SAP APP (+) add 2 (+)

expand 4

db HW (+) add 1/2 - SD2 BL - 2 quad proc. x 128gb

OS image

(+) expand

PRD apps HW (+) add 1/2 - Physical BL890C I2 OS

image (+) add 1 SAP APP (+) add 2 (+)

expand 6

db HW (+) add 1/2 - SD2 BL - 2 quad proc. x 128gb

OS image

(+) expand

SAP DB/CI

(+) expand


BW-BPCPhase 2

Hardware• Expansion for LPO/LPJ DB/CI and Apps using the SD-2 blades ordered

@phase 1• Installation of 02 Physical BL890Ci2 blade on PRD/DR for LP0/LPJ Apps

Operating systems• Support for hardware expansion for LPO/LPJ DB/CI and Apps;• Installation of 02 (two) O.S. Instances in PRD/DR LP0/LPJ Apps;

SAP DB/CI and Apps: • Support for hardware expansion for LPO/LPJ DB/CI and Apps ;

Installation and/or expansionPhas

eInstan

ceEnvi

r.Func

t.Action Type Action Hardware O.

S.D.B.

SAP CI

SAP App

s2

LP0, LPJ DR apps HW (+)

expand 1x Physical BL890C I2 MCC

OS image

(+) expand

SAP APP (+) expand

db HW (+) expand

Using Blades SD-2 ordered @ Phase 1

OS image

(+) expand

PRD apps HW (+) expand 1x Physical BL890C I2 MCC

OS image

(+) expand

SAP APP (+) expand

db HW (+) expand

Using Blades SD-2 ordered @ Phase 1

OS image

(+) expand

SAP DB/CI

(+) expand


Other activitiesBW-BPC

All phases• Set up of storage and SAN networks;• Set up ofbackup agents, backup servers, tape libraries and VTL, set of tapes;• Configuration of ITSM tools, monitoring agents, threshold parameter;• BCRS, adjustments in Technical Disaster & Recovery Plan;


Servers overview @ MCC/SCCBW-BPC

DR: DB/CI Apps

PDY/QAS: DB/CI & Apps

DEV: DB/CI & Apps

PRD: DB/CI

Apps


Servers distributionBW-BPC

DB/CI currentBW-LSA Phase 1:

DB/CI with BW-LSA Phase 1 + BPC Phase 1 :

Part. Type

HostnameSD2-1Enc:

Cator2enclus011

HostnameSD2-3Enc:

Cator2enclus013

HostnameSD2-5Enc:

Camkh1enclus003SAP Application

SCC PRODSids

MCCPRE-PROD

SidsBlade total

proc (quad core)

total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

add cores

needed

Min. Proc. Needed (quad)

N vlunx001 vlunx002 vlunx043 ECC EP0 EC0 3 6 8 8 16 384 24 ~ ~N vlunx014 vlunx015 vlunx049 BI BP0 ~ 1 2 4 4 4 128 8 ~ ~N vlunx005 vlunx028 vlunx050 EP WP0 ~ 1 2 4 4 4 128 8 ~ ~V vlunx045 vlunx046 cavacn36 BW-LSA LP0/LPJ ~ 1 2 4 8 ~ 128 8 2 1 (4 core)V V

Part. Type

HostnameSD2-1Enc:

Cator2enclus011

HostnameSD2-3Enc:

Cator2enclus013

HostnameSD2-5Enc:


SCC PRODSids

MCCPRE-PROD

SidsBlade total

proc (quad core)

total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

add cores

needed


N vlunx001 vlunx002 vlunx043 ECC EP0 EC0 3 6 8 8 16 384 24 ~ ~N vlunx014 vlunx015 vlunx049 BI BP0 ~ 1 2 4 4 4 128 8 ~ ~N vlunx005 vlunx028 vlunx050 EP WP0 ~ 1 2 4 4 4 128 8 ~ ~V vlunx045 vlunx046 cavacn36 BW-LSA+BPC LP0/LPJ ~

24 14 ~ 224 14

V NEW NEW NEW MI HP0 ~ 1 4 64 V ~ ~ ~


Servers distributionBW-BPC

Applications:

MCC Blade Servers for PPR/DR 'App' Servers SCC Blade Servers for PRODUCTION 'App' Servers

BLADEBlad

e Mod

el

Processor Arch

OSProcessor

sCOREs

Threads

RAM GB

Max RAM for

iVMsTier

ABAP Dia Inst

JAVA Dia Inst

DUAL Dia Inst

max sized cores

max sized RAM comment BLADE

Blade

Model

Processor Arch

OSProcessor

sCOREs

Threads

RAM GB

Max RAM for

iVMsTier

ABAP Dia Inst

JAVA Dia Inst

DUAL Dia Inst

max sized cores

max sized RAM comment

VLUNX02

6

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PPR ER0 ~ ~ 16 128 installed

VLUNX003

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PROD EP0 ~ ~ 16 128 installed

PPR ~ ~ ~ 0 0 no longer needed PROD ~ ~ BP0 0 0 no longer

neededPPR ~ ~ PR0 3 24 needed PROD ~ ~ PP0 3 24 neededPPR NR0 ~ ~ 3 24 needed PROD NP0 ~ ~ 3 24 neededPPR ~ ~ ~ 3 24 needed PROD ~ ~ WP0 3 24 neededPPR ~ ECR ~ 3 24 needed PROD ~ ECP ~ 3 24 neededPPR LP0 LPJ ~ 14 112 new PROD LP0 LPJ ~ 0 0 newPPR HP0 ~ ~ 8 64 new PROD HP0 ~ ~ 0 0 new

CPU utilization (average, peak) v. low v. low total > 50 400 CPU utilization (average, peak) v. low v. low total > 28 224

Memory Utilization (average, peak) v. low v. low Memory Utilization (average,

peak) v. low v. low

VLUNX02

7

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PPR ER0 ~ ~ 16 128 needed

VLUNX010

Bl890C i2

ia64 HP-UX 8 32 64 512 450




CPU utilization (average, peak) v. low v. low total > 50 400 CPU utilization (average, peak) v. low v. low total > 50 400Memory Utilization (average,

peak) v. low v. low Memory Utilization (average,

peak) v. low v. low

NEWSERVER01

Bl890C i2

ia64 HP-UX 8 32 64 51

2 450

PPR ER0 ~ ~ new

CAVAVS08

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PROD EP0 ~ ~ 16 128 needed

PPR ~ ~ ~ new PROD ~ ~ BP0 0 0 no longer needed

PPR ~ ~ PR0 new PROD ~ ~ PP0 3 24 neededPPR NR0 ~ ~ new PROD NP0 ~ ~ 3 24 neededPPR ~ ~ ~ new PROD ~ ~ WP0 3 24 neededPPR ~ ECR ~ new PROD ~ ECP ~ 3 24 neededPPR LP0 LPJ ~ new PROD LP0 LPJ ~ 14 112 newPPR HP0 ~ ~ new PROD HP0 ~ ~ 8 64 new



peak) v. low v. low

NEWSERVER02

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PROD EP0 ~ ~ newPROD ~ ~ BP0 newPROD ~ ~ PP0 newPROD NP0 ~ ~ newPROD ~ ~ WP0 newPROD ~ ECP ~ newPROD LP0 LPJ ~ newPROD HP0 ~ ~ new

CPU utilization (average, peak) total > 0 0Memory Utilization (average,

peak)


SRM


Sizing x Servers configurationSRM

Sizing:

Servers configurations:

SAP app.

System Role Target Server O.S. Recommended configuration per wave

Pilot Wave 1 Wave 2 Wave 3

SRM

DB/CI Cluster

SD-2 HP-UX 1 vPar, 4 cores, 16GB

1 vPar, 8 cores, 80GB 1 vPar, 10 cores, 96GB 1 vPar, 14 cores,

128GBSD-2 HP-UX 1 vPar, 4 cores,

16GB1 vPar, 8 cores, 80GB 1 vPar, 10 cores, 96GB 1 vPar, 14 cores,

128GB

APP Servers Bl460 G7 or Gen8 Linux 2 bl460 G7 2 bl460 G7

(12c/96GB)

2 bl460 G7 (12c/96GB) + 1 bl460 Gen8 (12c/128GB)

2 bl460 G7 (12c/96GB) +2 bl460 Gen8 (12c/128GB)

Portal (wp0) BL890iC2 HP-UX 2 core, 16GB 2 core, 16GB 2 core, 16GB 3 core, 24GB

Phase Action Item

TypeEnvir

.Instanc

e Function Platform Hostname O.S. Core Initial

Memory Initial

Core Sized

Memory Sized

Core Adde

d

Memory

AddedHardware required RU by

socket

pilot (+) add HW DR WP0 web/apps

Bl890C i2 - stacked NEWSERVER03 HP-

UX 0 0 2 16 2 16 Using BL890C I2 ordered @ Mobile Phase 1 (MCC) Small

pilot (+) add HW PRD WP0 web/apps

Bl890C i2 - stacked NEWSERVER04 HP-

UX 0 0 3 24 3 24 Using BL890C I2 ordered @ BPC Phase 1 (SCC) Small

1 (+) expand HW PRD SP0,

SPJ db SD2-2 CATOR2ENCLUS012/CAVACN27

HP-UX 7 104 8 128 1 24 Using Blades SD-2 current Small




1 (+) expand HW DR SP0,

SPJ db SD2-6 CAMKH1ENCLUS004/CAVACN34


2 (+) add HW PRD SP0, SPJ db SD2-2 CATOR2ENCLUS012/

CAVACN27HP-UX 8 128 10 160 2 32 1 - SD2 BL - 2 quad proc. x 128gb Small

2 (+) add HW PRD SP0, SPJ db SD2-4 CATOR2ENCLUS014/


2 (+) add HW DR SP0, SPJ db SD2-6 CAMKH1ENCLUS004/


2 (+) add HW PRD SP0, SPJ apps Bl460C G8 -

stacked NEWSERVER05 Linux 0 0 12 128 12 128 1x bl460 Gen8 (12c/128GB) Large

2 (+) add HW DR SP0, SPJ apps Bl460C G8 -




HP-UX 10 160 14 224 4 64 Using Blades SD-2 ordered @ Phase 2 Small




3 (+) expand HW DR SP0,

SPJ db SD2-6 CAMKH1ENCLUS004/CAVACN34


3 (+) add HW PRD SP0, SPJ apps Bl460C G8 -


3 (+) add HW DR SP0, SPJ apps Bl460C G8 -


3 (+) expand HW DR WP0 web/

appsBl890C i2 - stacked NEWSERVER03 HP-

UX 2 16 3 16 1 8 Using BL890C I2 ordered @ Mobile Phase 1 (MCC) Small

3 (+) expand HW PRD WP0 web/

appsBl890C i2 - stacked NEWSERVER04 HP-

UX 3 24 4 24 1 8 Using BL890C I2 ordered @ BPC Phase 1 (SCC) Small

At superdome (SD-2) was used 16 GB of memory per Core for hardware recommendatin


Core and memory configuration for WPOSRM

Pilot Phase 2/3PRD:

DR:

vlunx003 vlunx010 cavavs0801 core x

8GB01 core x

08GB01 core x

08GB= 02 cores x 16 GB

(sizing) HA (N+1)

vlunx027 vlnux02501 core x

8GB01 core x

08GB= 02 cores x 16 GB

(sizing)

vlunx003 Vlunx010 cavavs08 newserver02

01 core x 8GB

01 core x 08GB

01 core x 08GB

01 core x 08GB


vlunx027 vlnux025 newserver01

01 core x 8GB

01 core x 08GB

01 core x 08 GB



SRMPilot

Hardware:• Expansion of hardware for 02 Physical BL890Ci2 blade on

PRD/DR for WPO;Operating Systems:• Installation of 02 (two) O.S. Instances in PRD/DR for WPO;Sap DB/CI and Apps:• Installation of 10 DB/CI instances;• Installation of 04 has done by NSSR, it will have only ongoing

costs;• Installation of 14 APPS instances;

Phase 1Hardware• Expansion of hardware for in PRD/DR(PDY) for SP0/SPJ using the

blades current; SAP DB/CI and Apps: • Support for hardware expansion in PRD/DR(PDY) for SPO/SPJ

DB/CI ;

Installation and/or expansion

.Phase

Instance

Envir. Function Action

Type Action Hardware O.S.

D.B.

SAP CI

SAP Apps

pilot 2 14 14 14

SD0, SDJ 2 2

SD1, SDG DEV apps/db SAP

DB/CI (0) keep 2 2

SP0, SPJ DR apps SAP APP (+) add 4

PRD apps SAP APP (+) add 4 db SAP

DB/CI (+) add 2 2

SQ0, SQJ QAS apps/db SAP

DB/CI (+) add 2 2

SQ1, SQG QAS apps/db SAP

DB/CI (0) keep 2 2

SR0, SRJ PPR apps/db SAP

DB/CI (+) add 2 2

SY1, SYG PDY apps SAP APP (+) add 4

db SAP DB/CI (+) add 2 2

WP0 DR web/apps HW (+) add 1/2 - Physical BL890C I2

(Same BPC)

OS image (+) add 1

SAP APP (+) add 1 PRD web/

apps HW (+) add 1/2 - Physical BL890C I2 (Same BPC)

OS image (+) add 1

SAP APP (+) add 11

SP0, SPJ DR db HW (+)

expand Using Blades SD-2 current

PRD db HW (+) expand Using Blades SD-2 current

SAP DB/CI

(+) expand


SRMPhase 2Hardware:• Installation of 03 Physical SD-2 blade in PRD/DR (PDY) for

SP0/SPJ DB/CI;• Installation of 02 BL460 Gen8 in PRD/DR (PDY) for SP0/SPJ AppsOperating Systems:• Installation of 02 O.S. instances in PRD/DR(PDY) for SPO/SPJ

Apps;Sap DB/CI and Apps:• Support for hardware expansion in PRD/DR(PDY) for SPO/SPJ

DB/CI;• Installation of 04 APPS instances in PRD/DR (PDY) for SPO/SPJ;Phase 3Hardware:• Expansion of hardware SD-2 blade in PRD/DR(PDY) for SP0/SPJ

DB/CI;• Installation of 02 BL460 Gen8 in PRD/DR(PDY) for SP0/SPJ AppsOperating Systems:• Installation of 02 O.S. instances in PRD/DR (PDY) for SPO/SPJ

Apps;Sap DB/CI and Apps:• Support for hardware expansion in PRD/DR(PDY) for SPO/SPJ

DB/CI;• Installation of 04 APPS instances in PRD/DR(PDY) for SPO/SPJ;

Installation and/or expansion.Phas

eInstanc

eEnvi

r. Function Action Type Action Hardware O.

S.D.B.

SAP CI

SAP Apps

2 2 4 SP0,

SPJ DR apps HW (+) add 1x bl460 Gen8 (12c/128GB)

OS image (+) add 1

SAP APP (+) add 2 db HW (+) add 1 - SD2 BL - 2 quad proc. x

128gb PRD apps HW (+) add 1x bl460 Gen8 (12c/128GB) OS

image (+) add 1 SAP APP (+) add 2 db HW (+) add 1 - SD2 BL - 2 quad proc. x

128gb

SAP DB/CI

(+) expand

3 2 4 SP0,

SPJ DR apps HW (+) add 1x bl460 Gen8 (12c/128GB)

OS image (+) add 1

SAP APP (+) add 2 db HW (+)

expandUsing Blades SD-2 ordered @ Phase 2

PRD apps HW (+) add 1x bl460 Gen8 (12c/128GB) OS

image (+) add 1 SAP APP (+) add 2 db HW (+)

expandUsing Blades SD-2 ordered @ Phase 2

SAP DB/CI

(+) expand

WP0 DR web/apps HW (+)

expand1/2 - Physical BL890C I2 (Same BPC)

PRD web/apps HW (+)

expand1/2 - Physical BL890C I2 (Same BPC)


Other activitiesSRM



Servers overview @ MCC/SCCSRM

PDY (DR): DB/CI Apps

QAS: DB/CI & Apps

DEV: DB/CI & Apps

PRD: DB/CI

Apps

PRD: Portal

SY1 app xxSYG app xx

SP0 app DRSPJ app DR

SP0 app DRSPJ app DR

SY1 app xxSYG app xx


Servers distributionSRM

DB/CI Current:

DB/Ci with SRM :

Part. Type

HostnameSD2-2Enc:

Cator2enclus012

HostnameSD2-4Enc:

Cator2enclus014

HostnameSD2-6Enc:


SCC PRODSids

MCCPRE-PROD

SidsBlade total proc

total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

addit. cores

needed


N vlunx008 vlunx009 vlunx011 PI/GRC-NFE PP0/NP0 PR0/NR0 1 2 4 4 4 128 8 ~ ~V vlunx047 vlunx030 vlunx052 EC ECP ECR

4

2 4 8 ~ 128 8 ~ ~V cavacn25 cavacn26 cavacn33 CRM/MI CP0/CPJ/HP0 CR0/CRJ 1 1 4 ~ 64 4 ~ ~V cavacn27 cavacn27 cavacn34 EP WPE WRE 2 3 8 ~ 128 14 6 2 (8core)V cavacn29 cavacn30 cavacn35 MDM/Search-UI MPC/SCP MRC/SCR 2 5 8 ~ 128 13 5 1 (4core)V cavacn31 cavacn32 ~ GRC-AC GP0 ~ 1 3 4 ~ 64 6 2 1 (4core)V ~ ~ ~ N vlunx019 vlunx020 vlunx053 MDM MP0 1 2 4 4 4 128 8 ~ ~

Part. Type

HostnameSD2-2Enc:

Cator2enclus012

HostnameSD2-4Enc:

Cator2enclus014

HostnameSD2-6Enc:


SCC PRODSids

MCCPRE-PROD


total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

addit. cores

needed


N vlunx008 vlunx009 vlunx011 PI/GRC-NFE PP0/NP0 PR0/NR0 1 2 4 4 4 128 8 ~ ~V vlunx047 Vlunx030 vlunx052 EC ECP ECR

4

2 4 8 ~ 128 8 ~ ~V cavacn25 Cavacn26 cavacn33 CRM CP0/CPJ CR0/CRJ 1 1 4 ~ 64 4 ~ ~V cavacn27 Cavacn27 cavacn34 EP/and SRM WPE/SP0/SPJ WRE/SY1/SYG 1 8 8 ~ 128 16 8 2(8cores)V cavacn29 Cavacn30 cavacn35 MDM/Search-UI MPC/SCP MRC/SCR 2 5 8 ~ 128 13 5 1 (4core)V cavacn31 Cavacn32 ~ GRC-AC GP0 ~ 1 3 4 ~ 64 6 2 1 (4core)V ~ ~ ~ N vlunx019 Vlunx020 vlunx053 MDM MP0 1 2 4 4 4 128 8 ~ ~


Servers distributionSRM

Applications

Intel Blades for SAP Dia Inst [CRM/EP/SRM] @ MCC Intel Blades for SAP Dia Inst [CRM/EP/SRM] @ SCC

BLADEBlade Mode

l

Processor Arch

OS Processors

COREs

Threads

RAM GB

Max RAM for SAP

Tier ABAP DIA Inst

JAVA Dia Inst

Max Cores Sized

Max RAM Sized Comments BLADE

Blade Mode

l

Processor Arch

OS Processors

COREs

Threads

RAM GB

Max RAM for

iVMsTier ABAP

DIA InstJAVA

Dia InstMax

Cores Sized

Max RAM Sized Comments

cavaas39

BL460C G7

x86_64

RHEL

Server 5.7

2 12 24 96 85

PPR CR0 CRJ installed

cavaas37

BL460C G7

x86_64

RHEL

Server 5.7

2 12 24 96 85

PPR CR0 CRJ installedPPR ~ WRE installed PPR ~ WRE installedPPR SR0 SRJ # # new PPR SR0 SRJ # # new

CPU utilization (average, peak) ? ? CPU utilization (average, peak) ? ? Memory Utilization (average,

peak) ? ? Memory Utilization (average, peak) ? ?

cavaas40

BL460C G7

x86_64

RHEL

Server 5.7

2 12 24 96 85


cavaas38

BL460C G7

x86_64

RHEL

Server 5.7

2 12 24 96 85


CPU utilization (average, peak) ? ? CPU utilization (average, peak) ? ? Memory Utilization (average,

peak) ? ? Memory Utilization (average, peak) ? ?

new wave 1

BL460C G8

x86_64

RHEL

Server 5.7

2 12 24 128 85


new

wave 1

BL460C G8

x86_64

RHEL

Server 5.7

2 12 24 128 85


CPU utilization (average, peak) na na CPU utilization (average, peak) na na Memory Utilization (average,

peak) na na Memory Utilization (average, peak) na na

new wave 2-3

BL460C G8

x86_64

RHEL

Server 5.7

2 12 24 128 85


new

wave 2-3

BL460C G8

x86_64

RHEL

Server 5.7

2 12 24 128 85


CPU utilization (average, peak) na na CPU utilization (average, peak) na na Memory Utilization (average,

peak) na na Memory Utilization (average, peak) na na


Mobile


Sizing x Servers configurationMobile

Sizing:System

Role Target Server Recommended Config per Phase

Phase 1 Phase 2 Phase 3 Phase 4 Phase 5

DB/CI Cluster

SD-2 1 vPar, 4 cores, 48GB

1 vPar, 4 cores, 48GB




SD-2 1 vPar, 4 cores, 48GB





APP Servers 2 x BL890 i2 (shared APP svr) 03 cores, 32GB 04 cores, 48GB 06 cores, 64GB 08 cores, 80GB 08 cores, 80GB

Sup data tier vwmare 1 vM, 4 cores, 32GB 1 vM, 4 cores,

32GB1 vM, 4 cores,

32GB1 vM, 4 cores,

32GB1 vM, 4 cores,

32GBSup Apps vwmare 2 vM, 4 cores, 32GB 2 vM, 4 cores,

32GB2 vM, 4 cores,

32GB2 vM, 4 cores,

32GB2 vM, 4 cores,

32GBRelay server vwmare 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GBAfaria server vwmare 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB 2 vM, 2 cores, 8GB


Sizing x Servers configurationMobile

Servers configurations:Phas

e Action Item Type

Envir.

Instance Function Platform Hostname O.S. Core

InitialMemory Initial

Core Sized

Memory Sized

Core Adde

d

Memory

AddedHardware required

RU by socke

t1(+) add HW PRD HP0 nw/db SD2-1 CATOR2ENCLUS

011 HP-UX 4 64 4 64 1/2 - SD2 BL - 2 quad proc. x 128gb (Same BPC) Small

1(+) add HW PRD HP0 nw/db SD2-3 CATOR2ENCLUS013 HP-UX 4 64 4 64 1/2 - SD2 BL - 2 quad proc. x 128gb

(Same BPC) Small

1(+) add HW DR HP0 nw/db SD2-5 CAMKH1ENCLUS003 HP-UX 4 64 4 64 1/2 - SD2 BL - 2 quad proc. x 128gb

(Same BPC) Small

1(+) add HW PRD HP0 nw/apps Bl890C i2 - stacked NEWSERVER09 HP-UX 6 48 6 48 Using BL890C I2 ordered @ BPC

Phase 1 (SCC) Small

1(+) add HW DR HP0 nw/apps Bl890C i2 - stacked NEWSERVER10 HP-UX 4 32 4 32 1x Physical BL890C I2 to MCC Small

1(+) expand HW PRD AP0,

UPO sup/afaria/db Vmware CAVAAS50 Windows 2 16 4 32 2 16 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW PRD UP0 sup/apps Vmware NEWSERVER11 Windows 4 32 4 32 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW PRD UP0 sup/apps Vmware NEWSERVER12 Windows 4 32 4 32 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) expand HW DR AP0,

UPO sup/afaria/db Vmware CAVAAS45 Windows 2 16 4 32 2 16 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW DR UP0 sup/apps Vmware NEWSERVER13 Windows 4 32 4 32 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW DR UP0 sup/apps Vmware NEWSERVER14 Windows 4 32 4 32 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) expand HW QAS UQ0,

AQ0sup/afa/apps/db Vmware CAVAAS46 Window

s 2 16 4 32 2 16 VMWare Farm > BL620C HW (05 = 3 prd, 03 dr) virtual

1(+) expand HW DEV UD0,

AD0sup/afa/apps/db Vmware CAVAAS44 Window

s 2 16 4 32 2 16 VMWare Farm > BL620C HW (05 = 3 prd, 03 dr) virtual

1(+) add HW PRD AP0 afaria/apps Vmware NEWSERVER15 Windows 2 8 2 8 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW PRD AP0 afaria/apps Vmware NEWSERVER16 Windows 2 8 2 8 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW DR AP0 afaria/apps Vmware NEWSERVER17 Windows 2 8 2 8 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW DR AP0 afaria/apps Vmware NEWSERVER18 Windows 2 8 2 8 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW PRD RP0 relay Vmware NEWSERVER21 Windows 2 8 2 8 VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) virtual

1(+) add HW PRD ctl VMWARE Site RM. Vmware NEWSERVER24 Window

s 2 8 2 8 VMWare Farm > BL620C HW (05 = 3 prd, 03 dr) virtual

1(+) add HW DR ctl VMWARE Site RM. Vmware NEWSERVER25 Window

s 2 8 2 8 VMWare Farm > BL620C HW (05 = 3 prd, 03 dr) virtual

2(+) expand HW PRD HP0 nw/apps Bl890C i2 -

stacked NEWSERVER09 HP-UX 6 48 9 72 3 24 28% BL890C I2 to SCC Small

2(+) expand HW DR HP0 nw/apps Bl890C i2 -

stacked NEWSERVER10 HP-UX 4 32 6 48 2 16 28% BL890C I2 to MCC Small


stacked NEWSERVER09 HP-UX 9 72 18 144 9 72 42% BL890C I2 to SCC Medium




stacked NEWSERVER09 HP-UX 18 144 24 192 6 48 30% BL890C I2 to SCC Small




Core and memory configuration for HP0 AppsMobile

Phase 1, Phase 2,Phase 3, Phase 4/5

PRD:

DR:

vlunx003 /

vlunx010newserver

02 newserver09

02 cores x 16GB

02 cores x 16GB

02 cores x 16GB


newserver01 newserver10

02 cores x 16GB

02 cores x 16GB

= 04 cores x 32 GB (sizing)


03 cores x 24GB

03 cores x 24GB



06 cores x 48GB

06 cores x 48GB



08 cores x 64GB

08 cores x 64GB


vlunx003 /

vlunx010newserver

04 newserver09

03 cores x 24GB

03 cores x 24GB

03 cores x 48GB


vlunx003 /

vlunx010newserver

04 newserver09

06 cores x 48GB

06 cores x 48GB

06 cores x 48GB


vlunx003 /

vlunx010newserver

04 newserver09

08 cores x 64GB

08 cores x 64GB

08 cores x 64GB



MobilePhase 1

Hardware:• Installation of 02 Physical BL890C I2 (Share BPC) in PRD/DR for

HPO Netweaver Mobile;• Installation of VMWare Farm > BL620C HW (05 = 3 prd, 03 dr) to

support PRD/DR for SUP, Afaria, Relay and utility servers;

Operating Systems:• Installation of 13 O.S. Instances in PRD/DR;

Sap DB/CI and Apps:• Migration of 01 DB instances, 01 NetWeaver PRD to new vPar;• Installation of 06 DB instances, 02 NetWeaver DR/TRN, 02 sup, 02

Afaria in PRD/DR;• Installation of 05 CI “like” instances ctrl, vmware, relay, and

NetWeaver; • Installation of 15 APPS instances;

Installation and/or expansion.

Phase

Instance

Envir. Function Action

Type Action Hardware O.S.

D.B.

SAP CI

SAP App

1 13 6 5 15 HP0 DR nw/apps HW (+) add 1x Physical BL890C I2 OS image (+) add 1 SAP APP (+) add 3 nw/db HW (+) add 1/2 - SD2 BL - 2 quad proc. x 128gb

(Same BPC) OS image (+) add PRD nw/apps HW (+) add 1x Physical BL890C I2 OS image (+) add 1 SAP APP (+) add 4 nw/db HW (+) add 1/2 - SD2 BL - 2 quad proc. x 128gb

(Same BPC) OS image (+) add SAP DB/CI (+) add 1 1 HT0 TRN nw/apps/db SAP DB/CI (+) add 1 1 ctl DR VMMARE Site

RM. HW (+) add VMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

OS image (+) add 1 SAP DB/CI (+) add 1 PRD VMWARE Site

RM. HW (+) add VMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

OS image (+) add 1 SAP DB/CI (+) add 1 UP0 DR sup/apps HW (+) add VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) OS image (+) add 2 SAP APP (+) add 2 PRD sup/apps HW (+) add VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) OS image (+) add 2 SAP APP (+) add 2 UQ0,

AQ0 QAS sup/afa/apps/db HW (+)

expandVMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

UD0, AD0 DEV sup/afa/

apps/db HW (+) expand

VMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

AP0 DR afaria/apps HW (+) add VMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

OS image (+) add 2 SAP APP (+) add 2 PRD afaria/apps HW (+) add VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) OS image (+) add 2 SAP APP (+) add 2 RP0 PRD relay HW (+) add VMWare Farm > BL620C HW (05 = 3

prd, 03 dr) OS image (+) add 1 SAP CI (+) add 1 AP0,

UPO DR sup/afaria/db HW (+) expand

VMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

SAP DB (+) add 2 PRD sup/afaria/db HW (+)

expandVMWare Farm > BL620C HW (05 = 3 prd, 03 dr)

SAP DB (+) add 2


MobilePhase 2, 3 and 4

Hardware:• Installation/Expansion of hardware using BL890C I2 in PRD/DR for

HP0; Operating Systems:• Support expansion of hardware in PRD/DR for HPO O.S. instances;Sap DB/CI and Apps:• Support for hardware expansion in PRD/DR for HPO Apps instances;

Phase 5Hardware:• There isn´t no change, the sizing is the same of Phase 4;Operating Systems:• There isn´t no change, the sizing is the same of Phase 4;Sap DB/CI and Apps:• There isn´t no change, the sizing is the same of Phase 4;

Installation and/or expansion.Phas

eInst

Envir.

Function

Action Type Action Hardware O.

S.D.B.

SAP CI

SAP App

s2

HP0 DR nw/

apps HW (+) add 1x BL890C I2 to MCC (shared with BPC phase 2)

OS image (+) expand

SAP APP (+) expand

PRD nw/apps HW (+) add 1x BL890C I2 to SCC (shared with BPC

phase 2)

OS image (+) expand

SAP APP (+) expand

3 HP

0 DR nw/apps HW (+)

expandUsing BL890C I2 ordered @ Phase before

OS image (+) expand

SAP APP (+) expand

PRD nw/apps HW (+)


OS image (+) expand

SAP APP (+) expand

4 HP

0 DR nw/apps HW (+)


OS image (+) expand

SAP APP (+) expand

PRD nw/apps HW (+)


OS image (+) expand

SAP APP (+) expand


Other activitiesMobile


Important: • Vale need to provide network infra-structure for the deploy of Mobile Environment;• 2 x 2 connections 10GB networks ports for connect mobile SD2 vPar;


Servers overview @ MCC/SCCMobile

QAS: DB/CI & Apps

DEV: DB/CI & Apps

PRD: DB/CI

Apps

DR: DB/CI Apps

SD2-1CATOR2ENCLUS0

11vPAR

newserverTBD

HP-UX

SD2-3CATOR2ENCLUS0

13vPAR

newserverTDB

HP-UX

SD2-5CATOR2ENCLUS00

3vPAR

newserverTBD

HP-UX

HP0

HP0

HP0

HP0

HP0

HP0

HP0


Servers distributionMobile

DB/CI Current:

DB/Ci with SRM :

Part. Type

HostnameSD2-2Enc:

Cator2enclus012

HostnameSD2-4Enc:

Cator2enclus014

HostnameSD2-6Enc:


SCC PRODSids

MCCPRE-PROD


total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

addit. cores

needed


N vlunx008 vlunx009 vlunx011 PI/GRC-NFE PP0/NP0 PR0/NR0 1 2 4 4 4 128 8 ~ ~V vlunx047 vlunx030 vlunx052 EC ECP ECR

4

2 4 8 ~ 128 8 ~ ~V cavacn25 cavacn26 cavacn33 CRM/MI CP0/CPJ/HP0 CR0/CRJ 1 1 4 ~ 64 4 ~ ~V cavacn27 cavacn27 cavacn34 EP WPE WRE 2 3 8 ~ 128 14 6 2 (8core)V cavacn29 cavacn30 cavacn35 MDM/Search-UI MPC/SCP MRC/SCR 2 5 8 ~ 128 13 5 1 (4core)V cavacn31 cavacn32 ~ GRC-AC GP0 ~ 1 3 4 ~ 64 6 2 1 (4core)V ~ ~ ~ N vlunx019 vlunx020 vlunx053 MDM MP0 1 2 4 4 4 128 8 ~ ~

Part. Type

HostnameSD2-1Enc:

Cator2enclus011

HostnameSD2-3Enc:

Cator2enclus013

HostnameSD2-5Enc:


SCC PRODSids

MCCPRE-PROD

SidsBlade total

proc (quad core)

total cores sized

Phase1

cores ACTIVE

cores iCAPed ram

total cores sized

add cores

needed


N vlunx001 vlunx002 vlunx043 ECC EP0 EC0 3 6 8 8 16 384 24 ~ ~N vlunx014 vlunx015 vlunx049 BI BP0 ~ 1 2 4 4 4 128 8 ~ ~N vlunx005 vlunx028 vlunx050 EP WP0 ~ 1 2 4 4 4 128 8 ~ ~V vlunx045 vlunx046 cavacn36 BW-LSA+BPC LP0/LPJ ~

24 14 ~ 224 14

V NEW NEW NEW MI HP0 ~ 1 4 64 V ~ ~ ~



Applications

MCC Blade Servers for PPR/DR 'App' Servers SCC Blade Servers for PRODUCTION 'App' Servers

BLADEBlad

e Mod

el

Processor Arch

OSProcessor

sCOREs

Threads

RAM GB

Max RAM for

iVMsTier

ABAP Dia Inst

JAVA Dia Inst

DUAL Dia Inst

max sized cores

max sized RAM comment BLADE

Blade

Model

Processor Arch

OSProcessor

sCOREs

Threads

RAM GB

Max RAM for

iVMsTier

ABAP Dia Inst

JAVA Dia Inst

DUAL Dia Inst

max sized cores

max sized RAM comment

VLUNX02

6

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PPR ER0 ~ ~ 16 128 installed

VLUNX003

Bl890C i2

ia64 HP-UX 8 32 64 512 450




CPU utilization (average, peak) v. low v. low total > 50 400 CPU utilization (average, peak) v. low v. low total > 28 224

Memory Utilization (average, peak) v. low v. low Memory Utilization (average,

peak) v. low v. low

VLUNX02

7

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PPR ER0 ~ ~ 16 128 needed

VLUNX010

Bl890C i2

ia64 HP-UX 8 32 64 512 450






peak) v. low v. low

NEWSERVER01

Bl890C i2

ia64 HP-UX 8 32 64 51

2 450

PPR ER0 ~ ~ new

CAVAVS08

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PROD EP0 ~ ~ 16 128 needed

PPR ~ ~ ~ new PROD ~ ~ BP0 0 0 no longer needed

PPR ~ ~ PR0 new PROD ~ ~ PP0 3 24 neededPPR NR0 ~ ~ new PROD NP0 ~ ~ 3 24 neededPPR ~ ~ ~ new PROD ~ ~ WP0 3 24 neededPPR ~ ECR ~ new PROD ~ ECP ~ 3 24 neededPPR LP0 LPJ ~ new PROD LP0 LPJ ~ 14 112 newPPR HP0 ~ ~ new PROD HP0 ~ ~ 8 64 new



peak) v. low v. low

NEWSERVER02

Bl890C i2

ia64 HP-UX 8 32 64 512 450

PROD EP0 ~ ~ newPROD ~ ~ BP0 newPROD ~ ~ PP0 newPROD NP0 ~ ~ newPROD ~ ~ WP0 newPROD ~ ECP ~ newPROD LP0 LPJ ~ newPROD HP0 ~ ~ new

CPU utilization (average, peak) total > 0 0Memory Utilization (average,

peak)



VMWareVIRTUAL MACHINES - Non-Prod - MCC VMWARE Farm VIRTUAL MACHINES - PRODUCTION - SCC VMWARE Farm

Environment Virtual Machine Role SAP Sids Tier OS vCPU RAM Temp or Perm Comments Environment Virtual Machine Role SAP Sids Tier OS vCPU RAM Temp or Perm CommentsTIBCO CAMKH1TIBCAS001 Agent ~~~~ NSSR W2K8 2 8 temp or perm installed TREX cator2valeas076 SAP Trex - Slave 1 TP0 PROD RHEL 2 8 Perm installedTIBCO CAMKH1TIBCAS002 Ems #1 ~~~~ NSSR W2K8 4 16 temp or perm installed TREX cator2valeas077 SAP Trex - Slave 2 TP0 PROD RHEL 2 8 Perm installed

DocumentumCAMKH1TIBCAS003 Test Server #1 ~~~~ NSSR RHEL 4 16 temp or perm installed TREX cator2valeas084 SAP Trex Master TP0 PROD RHEL 2 8 Perm installedTIBCO CAMKH1TIBCAS004 BW/BC #1 ~~~~ NSSR W2K8 4 16 temp or perm installed TREX cator2valeas085 SAP Trex Master Backup TP0 PROD RHEL 2 8 Perm installedTIBCO CAMKH1TIBCAS005 BW/BC #2 ~~~~ NSSR W2K8 4 16 temp or perm installed VMWARE cator2valeus484 VMWare Virtual Center ~~~~ PROD W2K8 8 24 Perm installedTIBCO CAMKH1TIBCAS006 BC (DMZ) ~~~~ NSSR W2K8 1 1 temp or perm installed EP Web Disp cavaas31 Web Dispatcher (DMZ) DP0 PROD RHEL 2 8 Perm installedTIBCO CAMKH1TIBCAS007 Mgmt ~~~~ NSSR W2K8 2 8 temp or perm installed EP Web Disp cavaas32 Web Dispatcher (DMZ) DP0 PROD RHEL 2 8 Perm installedTIBCO CAMKH1TIBCAS008 Agent ~~~~ NSSR W2K8 2 8 temp or perm installed SYBASE cavaas49 Sysbase Relay Server (DMZ) ~~~~ PROD W2K8 2 8 Perm installedTIBCO CAMKH1TIBCAS009 EMS #1 ~~~~ NSSR W2K8 4 16 temp or perm installed SYBASE cavaas50 Unwired Platform / Afaria ~~~~ PROD W2K8 2 16 Perm installed

DocumentumCAMKH1TIBCAS010 Test Server #2 ~~~~ NSSR RHEL 4 16 temp or perm installed SYBASE new SUP Data tier PROD W2K8 4 32 Perm newTIBCO CAMKH1TIBCAS011 BW/BC #1 ~~~~ NSSR W2K8 4 16 temp or perm installed SYBASE new SUP Server #1 PROD W2K8 4 32 Perm newTIBCO CAMKH1TIBCAS012 BW/BC #2 ~~~~ NSSR W2K8 4 16 temp or perm installed SYBASE new SUP Server #2 PROD W2K8 4 32 Perm newTIBCO CAMKH1TIBCAS013 BC (DMZ) ~~~~ NSSR W2K8 1 1 temp or perm installed SYBASE new Sybase Relay Server (DMZ) #1 PROD W2K8 2 8 Perm newTIBCO CAMKH1TIBCAS014 Mgmt ~~~~ NSSR W2K8 2 8 temp or perm installed SYBASE new Sybase Relay Server (DMZ) #2 PROD W2K8 2 8 Perm newTREX CAMKH1VALEAS018 SAP Trex TP0 dr DR RHEL 2 8 perm installed SYBASE new Afaria Server#1 PROD W2K8 2 8 Perm newTREX CAMKH1VALEAS019 SAP Trex TQ0 QAS RHEL 2 8 perm installed SYBASE new Afaria Server#2 PROD W2K8 2 8 Perm newTREX CAMKH1VALEAS020 SAP Trex TD0 DEV RHEL 2 8 perm installed SYBASE new Sybase Control Center PROD W2K8 2 8 Perm new

VMWARE camkh1valeus042 VMWare Virtual Center ~~~~ NonP, DR W2K8 1 8 perm installed VMWARE new VMWARE Site Recovery Mgr PROD W2K8 2 8 Perm newEP Web Disp cavaas41 Web Dispatcher (DMZ) DQ0, DP0 DR NonP, DR RHEL 2 8 perm installed Mercury BPM new SAP Business Process Monitor ~~~~ PROD XP ? 2 4 Perm

SYBASE cavaas43 Sysbase Relay Server (DMZ) ~~~~ DEV W2K8 2 8 perm installed SYBASE cavaas44 Unwired Platform / Afaria ~~~~ DEV W2K8 2 16 perm installed SYBASE cavaas45 Unwired Platform / Afaria ~~~~ DR W2K8 2 16 perm installed SYBASE cavaas46 Unwired Platform / Afaria ~~~~ QAS W2K8 2 16 perm installed SYBASE cavaas47 Sysbase Relay Server (DMZ) ~~~~ DR W2K8 2 8 perm installed SYBASE cavaas48 Sysbase Relay Server (DMZ) ~~~~ QAS W2K8 2 8 perm installed

BO Explorer CAVAAS51 BO Explorer POC ~~~~ NSSR W2K8 4 16 temp installed VMWARE new VMs for DR with SRM (?) PROD W2K8 2 8 Perm new

total vCPU and RAM Assigned 69 136 total vCPU and RAM Assigned 50 244


Overview of all components in PRD: NetWeaver Mobile, Sybase Relay, SUP and Afaria

Mobile


Macro timeline


Macro timeline

Macro timelineMacro timeline


Clustering


HP ServiceGuardSet-up a high-availability clustering solution


Downtime/outages


BW-BPC Downtime (and MI)

• In BPC phase 1 we will need to add new HW (SD2 blade). • This requires a reboot to add the HW to the nPAR. • Estimated downtime for the reboot is 02 hours• It will impact BW-LSA, no impact to ECC (EP0), BI

(BP0) or EP (WP0).

• In BPC phase 2 we will need to re-assign the SD2 blade HW released from BI (BP0) Decomisioning.

• This requires a reboot to add this HW to the BW-LSA and MI nPAR.

• Estimated downtime for the reboot is 02 hours • it will impact BW-LSA and MI, no impact to ECC (EP0)

or EP (WP0).


SRM Downtime

• During installation and cluster configuration / testing we will have 10-20 hours (estimated) of downtime;

• • It will impact all applications

running on hosts cavacn27 and cavacn28: EP and TREX (nfs share) environment.

• And in the future wave 2 will be need to add new HW (SD2 blade) and then will have another downtime (at least 2 hours) for the nPar

• it will impact all the vPARs running in it: SRM-MDM Catalog, SearchUI, GRC-AC ,CRM and EC environment, EP TREX and SRM.

• In future Phase 2 for SRM project, when the other SD2 blade hw is added, this would also require downtime (for a reboot, at least 2 hours) unless both blades were added at the same time.


Mobile Downtime

• In this case will need to move Mobile to new and dedicated vPar to segregate from CRM environment.

• And will have a downtime (3-6 hour estimated) in current mobile environment.

• Note: a second downtime will be needed to add HW to the BW-LSA/MI nPAR after it is released from BI.

• Estimate is aproximately 2 hours. (See slide from BPC).


Impact of CRM on the IP


Impact of SRM on the PI1. PI is currently running stacked with GRC on a SD-2 partition. Below is the current nPar config:

This means that the current nPar supports ~5,000 SAPS, and can support ~10,000 SAPS after the activation of the 4 iCAP cores;

2. Additional interfaces will be added to the PI system as part of the SRM implementation. The table below summarizes the requirements to handle these new interfaces:

3. We considerate a 3-tier PI deployment, with the PI APP servers running on HP-UX, we can assume that the current nPar can support current PI + GRC + new interfaces, after the activation of the iCAP cores:

• GRC Phase 2 DB: 6,400 SAPS• Current PI: SAPS (assuming 2,000 SAPS)• New interfaces: 1000 SAPS• Total: ~9,400 SAPS (ok on the 8-way nPar, but will be use 04 cores ICAPed, and add new SAP Dialog instances for PP0, in

vnlux003, vnlux010 and cavavs08);4. The cost of this expansion of PI (04 cores ICAPed and new SAP Dialog) is not included in

this project;

SAP Application SCC PROD Sids MCC PRE-PROD Sids Blade total proc total cores sized

Phase1 cores ACTIVE cores iCAPed ramPI/GRC-NFE PP0/NP0 PR0/NR0 1 2 4 4 4 128

Release SAPS (total) Memory (GB)PI 7.1 5,200 42


List of hardware


Components of hardware

System SCC MCC

BPC Scenario 1/ Mobile Phase 1 1x BL890c i2 1x BL890c i22x CB900 1x CB900

Mobile Phase 1 3x BL620 x86 3x BL620 x86

BPC Scenario 2/ Mobile Phase 2 1x BL890c i2 1x BL890c i2

SRM Phase 2 1x BL460 x86 1x BL460 x862x Cb900 1x CB900

SRM Phase 3 1x BL460 x86 1x BL460 x86


Next steps


Next steps

• Clear all technical doubts

• Make some technical adjusts

• Guarantee that the volume x RU is correct


Thank you

vale - indicative price - sap bpc, srm & mobile - technical presentation - v-2.3

Documents