SAP HANA Developer Quick Start Guide en

FlexFrame® Orchestrator
Configuration Guide
V1.3A
2016-12-12
For internal use only
PR CM DC SAP
Fujitsu Technology Solutions, Germany

FlexFrame Orchestrator V1.3A
Non-Disclosure Notice
This FlexFrame Orchestrator V1.3A - Configuration Guide is for internal use of Fujitsu Company
only. This Configuration Guide has to be treated strictly company confidential and may only be
distributed to authorized FlexFrame reseller partners.
Document History
Modified by Date Description of Changes

HJH 2016-12-12 Initial Release FFO V1.3 A
New in this edition
 Configuration of 10 GbE switch groups only

 Support of RX2530 M2
 Support of Cisco Nexus 9372
 Support of SUSE Life patching
 Support of NetApp All Flash systems
 Minor adaptions
FlexFrame® Orchestrator 2 - 57
Contents
1 INTRODUCTION ................................................................................................................ 6
2 HARDWARE COMPONENTS ............................................................................................ 7
2.1 Control Nodes .................................................................................................................................................... 7

2.1.1 Physical Control Nodes .............................................................................................................................. 8
2.1.1.1 Configuration RX2540M2 (Control Node) ...................................................................................... 8
2.1.2 Virtual Control Nodes ................................................................................................................................ 9
2.1.2.1 Recommended Configuration RX2540M2 ..................................................................................... 10
2.2 Application and Hypervisor Nodes ................................................................................................................ 11

2.2.1 Certified HANA configurations ............................................................................................................... 11
2.2.2 Rack server .............................................................................................................................................. 12
2.2.2.1 PRIMERGY RX2530M2 ............................................................................................................... 12
2.2.2.2 PRIMERGY RX2540M2 ............................................................................................................... 14
2.2.2.3 PRIMERGY RX4770 M3 .............................................................................................................. 16
2.2.2.4 PRIMEQUEST PQ2800B2 ............................................................................................................ 18
2.2.2.5 PRIMEQUEST PQ2800B3 ............................................................................................................ 20
2.2.3 Blade server BX900 ................................................................................................................................. 22
2.2.3.1 System cabinet BX900 S2 .............................................................................................................. 22
2.2.3.3 PRIMERGY BX2560 M1 .............................................................................................................. 23
2.2.3.4 PRIMERGY BX2560 M2 .............................................................................................................. 24
2.2.3.5 PRIMERGY BX2580 M1 .............................................................................................................. 25
2.2.3.6 PRIMERGY BX2580 M2 .............................................................................................................. 26
2.3 Storage System ................................................................................................................................................. 27

2.3.1 NAS storage systems ............................................................................................................................... 28
2.3.2 SAN Storage systems ............................................................................................................................... 28
2.4 Switches ............................................................................................................................................................ 29

2.4.1 TCP/IP (LAN) .......................................................................................................................................... 29
2.4.1.1 Cisco 3750 Series ........................................................................................................................... 29
2.4.1.2 Cisco switch Catalyst 3750 Registration ........................................................................................ 30
2.4.1.3 Cisco Nexus 5500 series ................................................................................................................. 30
2.4.1.4 Cisco Nexus 9372 series ................................................................................................................. 31
2.4.1.5 Brocade IP ICX6430 / ICX6450 switches ...................................................................................... 32
2.4.1.6 Brocade IP VDX6740..................................................................................................................... 32
2.4.2 FC Switches ............................................................................................................................................. 33
3 FLEXFRAME MANAGEMENT SOFTWARE LICENSES ................................................. 34
3.1 End User Licenses............................................................................................................................................ 34

3.1.1 License metrics ........................................................................................................................................ 34
3.1.2 General License structure ......................................................................................................................... 34
3.1.3 FlexFrame Orchestrator – Mandatory licenses ........................................................................................ 34
3.1.4 FlexFrame Orchestrator – Optional licenses ............................................................................................ 34
3.1.5 License Exceptions .................................................................................................................................. 34
3.1.6 Demo licenses .......................................................................................................................................... 34
3.2 Offering packages and order items ................................................................................................................ 35

3.2.1 Perpetual FFO Licenses ........................................................................................................................... 35
3.2.2 One Year FFO Subscriptions ................................................................................................................... 37
4 SOFTWARE ..................................................................................................................... 38
4.1 Operating System Software ............................................................................................................................ 38
4.2 Control Node Image ........................................................................................................................................ 38

4.2.1 FlexFrame Management Software ........................................................................................................... 38
4.2.2 Operating System ..................................................................................................................................... 38
4.2.3 Linux-HA ................................................................................................................................................. 38
4.3 Application Node Images ................................................................................................................................ 38

4.3.1 PRIMERGY ............................................................................................................................................. 38
4.3.2 Operating System ..................................................................................................................................... 38
4.4 Hypervisor Nodes ............................................................................................................................................ 38
4.5 SAP and Database Software ........................................................................................................................... 39
4.6 VMware vSphere ESXi Software ................................................................................................................... 39
4.7 Linux KVM Software ...................................................................................................................................... 39
4.8 Storage Systems ............................................................................................................................................... 39

4.8.1 NetApp Filer ............................................................................................................................................ 39
5 HIGH AVAILABILITY ....................................................................................................... 41
5.1 General ............................................................................................................................................................. 41
5.2 Cluster configuration with NetApp HW ........................................................................................................ 41
6 NETWORK ....................................................................................................................... 41
7 FLEXFRAME CONFIGURATIONS (EXAMPLES) ............................................................ 42
7.1 LAN configuration........................................................................................................................................... 42
7.2 LAN/SAN configuration with NetApp Gateway ........................................................................................... 43
7.3 Configuration with SAN storage systems ...................................................................................................... 44
8 HOW TO ORDER FLEXFRAME ...................................................................................... 45
8.1 Control Nodes & FlexFrame Orchestrator ................................................................................................... 46
8.2 Application Nodes ............................................................................................................................................ 47

8.2.1 Rack server RX2530, RX2540, RX4770, PQ2800B................................................................................ 47
8.2.2 PRIMERGY BX900 Bladeserver ............................................................................................................ 48
8.3 FFO Management Software licenses .............................................................................................................. 49
8.3.1 Expandable Software license packages .................................................................................................... 49
8.3.2 Non expandable Software license packages ............................................................................................. 50
9 UPGRADE AND IMPLEMENTATION TO FLEXFRAME ORCHESTRATOR V1.3A ........ 51
10 PROFESSIONAL SERVICES FOR FLEXFRAME SOLUTIONS ...................................... 51
10.1 Mandatory Services for FlexFrame V1.3A Implementation and Update .............................................. 51
10.2 Process Description for a Service Offer .................................................................................................... 52
11 MAINTENANCE & SUPPORT ......................................................................................... 53
11.1 Integration services ..................................................................................................................................... 53
11.2 Maintenance services – Solution Contract................................................................................................ 53

11.2.1 Remote Support Access ...................................................................................................................... 54
11.2.2 How to order SolutionContract FlexFrame ......................................................................................... 55
11.3 Maintenance Service – Back level support ............................................................................................... 56

11.3.1 FlexFrame Management Software back level support ........................................................................ 56
11.3.2 Suse Linux ES Subscriptions .............................................................................................................. 56
11.3.3 VMware vSphere ESXi Service packs ................................................................................................ 56
11.3.4 Fujitsu’s Hardware Service Packs ....................................................................................................... 57
11.3.5 3rd-Party Hardware Service Packs ....................................................................................................... 57
1 Introduction
This document is intended to be used as a basis for elaborating a FlexFrame configuration.
Since a FlexFrame configuration is assembled individually for each customer, the minimum
requirements are specified. The hardware and necessary software components are listed. In
addition, the service packages required for installation are described.
For maintenance and service aspects a valid service concept and contract is
st nd rd
mandatory that covers 1 , 2 and 3 level support. Responsible for such a
Note
service offering are the individual regions or certified FlexFrame service partners.
For Germany the FlexFrame Solution Contract is available.
More detailed information about FlexFrame maintenance is available at the maintenance and
support services extranet pages.
Prescribed terminology: the 2 Control Nodes (CN) are named as one

Note
ControlCenter (CC).
It is strongly recommended to involve the Fujitsu SAP Global Competence Center in Walldorf
(expert.sap@ts.fujitsu.com) in the sizing and configuration process. Load calculation (sizing)
and a configuration proposal can be provided by the FFO Architecture Services Team.
Please send all requests to: expert.sap@ts.fujitsu.com
This document is a subject of change; we therefore strongly recommend downloading always
the current valid version, available on the PRIMEFLEX for SAP landscapes Extranet site.
Further information can be found in the FlexFrame public document Site,
 Contents Public Documents such as Public Manuals, Release Information
and at the PRIMEFLEX for SAP landscapes Extranet site,
 Contents Solution Release Announcement, Solution Release Description, set of sales
slides, Sales Guide, customer brochure, etc.
All information for service partners is available at the Service Partner Portal
 Contents Support Bulletins, technical information, etc.
2 Hardware Components
The main intention of this configuration guide is to support a FlexFrame V1.3A configuration. It
contains a list of compliant ControlCenter Nodes, Application Nodes, Storage and Network
Components and Professional Services.
A complete FlexFrame V1.3A infrastructure comprises racks, the cabling, redundant power
supplies wherever possible, redundant electric circuits, uninterruptible power supplies (UPS),
KVM switches, rack console etc. A hardware console for the application nodes and the control
nodes is urgently required. In the target locations sufficient power connection, the right power
connectors, air conditioning and floor load have to be considered.
For a complete solution you need also:
 1 x FlexFrame Identifier FTS:FFO-ID-001 (mandatory)
This is an unique label with the FlexFrame serial number and has to be ordered only
once per FlexFrame configuration.
 1 x FlexFrame staging identifier U21348-C1003 (mandatory for new configurations)
In case of very new FlexFrame configurations this identifier assures that the FlexFrame
configuration is pretested as a solution before delivery to minimize the installation efforts
at customer site.
FlexFrame owns its specific network infrastructure. The network connecting all components like
Control Nodes, physical Application Nodes, Hypervisor Nodes and storage subsystems consists
of a redundant physical cabling, running 4 logical networks: The Storage LAN, the Server LAN,
the Control LAN and the Client LAN. It is attached to the local enterprise network by switches.
All Application Nodes and Control Nodes must be equipped with redundant power supplies and
redundant fans. No other controllers than the on board controllers and those listed in this
document are supported.
For maintenance and support aspects a valid service concept and contract is mandatory that
covers 1st, 2nd and 3rd level support. Responsible for such a service offering are the individual
regions (e.g. FlexFrame SolutionContract for region DACH) or certified FlexFrame service
partners. For ordering the FlexFrame SolutionContract FlexFrame please contacts your local
service consultant. For FlexFrame partners a special 3rd level support order number is available.
The complete SW, license and identifier configuration you can find in chapter 8.
2.1 Control Nodes

The Control Center of FlexFrame can either consist of physical Control Nodes or of virtual
Control Nodes (vCN). In case of a virtual Control Center (vCC) both virtual machines are hosted
on different physical PRIMERGY servers that run SUSE KVM as hypervisor.
Both Control Nodes clustered with Linux-HA are required for redundancy reasons. The services
TFTP, DHCP, LDAP, NTP etc., the administration routines for the SAP services and optionally
the SAPROUTER run on the physical Control Nodes. In case of vCC the SAPROUTER has to
be installed on a further virtual machine.
The hardware for the Control Nodes has to be ordered based on following configurations.
2.1.1 Physical Control Nodes
2.1.1.1 Configuration RX2540M2 (Control Node)
Order number Text Quantity Comment
HW Basic
S26361-K1566-V101 PY RX2540 M2 4x 3.5' expandable
or or
Hint: Two PRIMERGYs are mandatory, both from
S26361-K1566-V401 PY RX2540 M2 8x 2.5' expandable 1
same type
or or
S26361-K1566-V112 PY RX2540 M2 12x 3.5'
S26361-F3933-E103 Intel Xeon E5-2603v4 6C/6T 1.70 GHz 2 For example, according to need
S26361-F3694-E10 Independent Mode Installation 2
S26361-F3849-E100 Cooler Kit 2nd CPU 1
S26361-F3934-E511 8GB (1x8GB) 1Rx4 DDR4-2400 R ECC 4 32GB minimum
S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1
S26361-F3820-E100 HD SAS 6G 1TB 7.2K HOT PL 3.5'' BC 2 For example
S26361-F5243-E1 PRAID EP400i 1 Raid Controller
S26113-F574-E13 Modular PSU 800W platinum hp 2 2 recommended for High Availability
S26361-F4610-E202 PLAN CP 2x1Gbit Cu Intel I350-T2 LP 1 1GbE Controller
S26361-F3417-L6xx LAN cable 3 Length depends on assembly
S26361-F5302-E100 PLAN EM blind panel 1
T26139-Y1968-E100 Cable powercord rack, 4m, grey 2
S26361-F1790-E243 iRMC S4 advanced pack 1
S26361-F3120-E40 Serial Port Option 1
HW Options
S26361-F2735-E175 Rack Mount Kit F1 CMA QRL LV 1 Rack Mount Kit

S26361-F4530-E10 or Mounting in symmetrical Racks or
1 Rack mounting
S26361-F4530-E11 Mounting 1U in asymmetrical Racks
S26361-F2735-E71 Cable mgmt. lateral for asym. PC racks 1 Cable management
S26361-F1452-E100 or region kit APAC/EMEA/India or
1 Region kit
S26361-F1452-E130 region-kit America
Maintenance and Service
Please contact your local
FlexFrame SolutionContract 1 for 1st, 2nd and 3rd Level Support
Service Consultant
Option A: Mandatory to provide SUSE fixes as part
of FlexFrame support. Should be activated as
S26361-F2348-S501 SUSE LES 1-2 Sock/VM 7x24 L3 Supp. 3Y 1
contract item. Renewal will be performed as part of
SolutionContract lifecycle management.
Option A: Mandatory for using the Standard Linux
S26361-F2348-S531 SLES HA Extension 1-2 Sock L3 Supp. 3Y 1
HA
Option B: Alternative SLES4SAP instead of
SLES4SAP 1-2 Sock/VM 7x24 L3 Supp.
S26361-F2348-S521 1 “standard” SLES; In this case the SUSE Linux ES
3Y
HAE is included in SLES4SAP
Corresponding Service Pack Classic for
SUSE Linux Enterprise Server or SUSE Necessary only, if Support will be delivered via a
See System Architect 1
Linux Enterprise Server for SAP certified Partner.
Applications
2.1.2 Virtual Control Nodes
As KVM hypervisor nodes all supported FFO PY/PQ rack server – except the PRIMERGY
RX300 S5 – are allowed. The KVM Hypervisor Nodes hosting a virtual Control Node must fulfill
special requirements as described in the “HW Characteristics”. Especially the KVM Hypervisor
Nodes hosting a virtual Control Node need 4 network interfaces and 300GB hard disk minimum.
A virtual Control Node needs a portion of 60GB disk space on the physical local disk of the
underlying Hypervisor Node and a corresponding portion of 8GB memory. It is the customer’s
responsibility to care for the sufficient availability of disk and memory space of the underlying
Hypervisor Node for the virtual Control Node
If even Application Nodes should run on the vCC Hypervisor Nodes following hardware
configuration is recommended as minimum to guarantee a smooth FFO operation:
2.1.2.1 Recommended Configuration RX2540M2
HW Basic
S26361-K1566-V101 PY RX2540 M2 8x 2,5” 1
S26361-F3849-E120 Intel Xeon E5-2620v3 6C/12T 2.40 GHz 2
S26361-F3843-E516 16GB (1x16GB) 2Rx4 DDR4-2133 R ECC 6 96GB minimum
S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1
S26361-F3818-E130 HD SAS 6G 300GB 10K HOT PL 2.5'' EP 2
S26361-F2495-E440 Konfig 4: 8x 2,5" HDD 1
S26361-F1790-E243 iRMC S4 advanced pack 1
S26361-F3120-E40 Serial Port Option 1
NIC Options
S26361-F4610-E202 PLAN CP 2x1Gbit Cu Intel I350-T2 LP 1 Option A: One Dual Port Gigabit Ethernet Server
Adapter and one Ethernet Server Adapter Eth Ctrl
S26361-F3629-E202 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ 1 2x10Gbit
Option B: Two Dual Port Gigabit Ethernet Server
S26361-F4610-E202 PLAN CP 2x1Gbit Cu Intel I350-T2 LP 2
Adapter
HW Options

1 Rack mounting
1 Region kit
Service Consultant
Option A: Mandatory to provide SUSE fixes as part
SUSE LES 1-2 Sock uVirt 24x7 L3 Supp. of FlexFrame support. Should be activated as
S26361-F2348-S511 1
3Y contract item. Renewal will be performed as part of
SolutionContract lifecycle management.
Option A: Mandatory for using the Standard Linux
S26361-F2348-S531 SLES HA Extension 1-2 Sock L3 Supp. 3Y 1
HA
SLES4SAP 1-2 Sock uVirt 24x7 L3 Supp.
S26361-F2348-S524 1 “standard” SLES; In this case the SUSE Linux ES
3Y
HAE is included in SLES4SAP
SUSE Linux Enterprise Server or SUSE Necessary only, if Support will be delivered via a
See System Architect 1
Linux Enterprise Server for SAP certified Partner.
Applications
2.2 Application and Hypervisor Nodes
FlexFrame supports physical Application Nodes running Linux operating system and Hypervisor
Nodes running with Linux KVM or VMware vSphere ESXi hypervisor. So PRIMERGY Rack
server and Blade server can be used as Application or Hypervisor Nodes.
All nodes are specified with their base configuration and optional components. Beyond the
mentioned components no additional components (e.g. PCI cards) are supported as the
FlexFrame AN image may not work properly. Sole exceptions are additional power supplies and
fans.
Relevant source for supported components (nodes, cards, storage, …) is the

FlexFrame V1.3A Support Matrix available at:
Note https://partners.ts.fujitsu.com/com/products/infrastruc-
solutions/FlexFrame/Pages/default.aspx
The HW Option SAN Connectivity (HBAs) should be installed only in physical rack servers, as
HBAs are not supported with Hypervisor Nodes nor blade servers. Switching of Nodes between
physical and virtualized is not recommended.
2.2.1 Certified HANA configurations

Some of the FFO Application Nodes can be used as SAP HANA servers (10GBit connectivity is
mandatory). Detailed Information of the certified SAP HANA Hardware and certified Scale Out
configurations are available on the corresponding SAP Pages.
Server specific HANA prerequisites and conditions are listed in the corresponding FFO AN
configurations.
For support during the sizing process please contact expert.sap@ts.fujitsu.com.
2.2.2 Rack server

2.2.2.1 PRIMERGY RX2530M2
HW Basic
S26361-K1565-V101 PY RX2530 M1 4x 3.5”
or or 1
S26361-K1565-V301 PY RX2530 M2 4x 2,5” exp.
CPU: x according to SAP sizing
S26361-F3849-E100 Cooler Kit 2nd CPU 1 In case of two CPU
RAM: x according to SAP sizing
HD SAS 2 SAS only!
S26361-F1790-E243 iRMC S4 advanced pack 1 Necessary for remote console interaction
S26361-F2735-E82 Rack Cable Arm 2U 1

S26361-F3694-E10 Independent Mode Installation Recommended for Standard server
or or 2 or
S26361-F3694-E2 Performance Mode Installation for HANA server
HW Options 1 GbE
HW Options 10 GbE
S26361-F3629-E202 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ lp 1 10GbE Controller
S26361-F3986-E3 SFP+ Module Multi Mode Fiber 10GbE LC 2 SFP+ interfaces for 10GbE Controller
HW Options SAN Connectivity (only supported for physical Application Nodes, not for Hypervisor Nodes)
S26361-F4994-E(20)1or PFC EP LPe16000 (LP) or 2
FC Controller for SAN Connectivity
S26361-F4994-E(20)2 PFC EP LPe16002 (LP) 1
HW Options general
S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1 In case running as Hypervisor Node
S26361-F2735-E422 RMK F1 Slimline, Slide-In Rail, QRL 1 Rack Mount Kit

1 Rack mounting
1 Region kit
Operating System running as physical Application Node
Option A: Mandatory to provide SUSE fixes as
part of FlexFrame support. Should be activated as
contract item. Renewal will be performed as part
of SolutionContract lifecycle management.
S26361-F2348-S521 SLES4SAP 1-2 Sock/VM 7x24 L3 Supp. 3Y 1
standard SLES
Operating System running as KVM or ESXi Hypervisor Node
S26361-F2348-S511 SUSE LES 1-2 Sock uVirt 24x7 L3 Supp. 3Y 1
S26361-F2348-S524 SLES4SAP 1-2 Sock uVirt 24x7 L3 Supp. 3Y 1
standard SLES
Operating System option: SUSE life patching
Has to be ordered for each AN that will run life
S26361-F2348-S561 SLES Life patching 3Y 1
patching
VMware vSphere ESXi Licenses running as ESXi Hypervisor Node (only orderable in the EMEA region)
U21348-C1091 FFO VMware vSphere STD 2 Option A: ESXi STD Edition
U21348-C1093 FFO VMware vSphere ENT PL 2 Option C: ESXi ENT PL Edition

Please contact your local st nd rd
FlexFrame SolutionContract 1 for 1 , 2 and 3 Level Support
Service Consultant
Necessary only, if Support will be delivered via a
See System Architect SUSE Linux Enterprise Server or SUSE 1
certified Partner.
Linux Enterprise Server for SAP Applications
For running the PRIMERGY RX2530 M2as a HANA Node within FlexFrame Orchestrator
the Intel Xeon E5-26xx v4 CPU types are supported as 2-socket system with minimum 8 cores
per CPU. This hardware is not tested or certified by SAP.
DIMM setting:
 No restrictions about supported DIMMs
 Homogenous symmetric assembly of DIMMs and maximum utilization of all available
memory channels
2.2.2.2 PRIMERGY RX2540M2
HW Basic
S26361-K1566-V101 PY RX2540 M2 4x 3.5' expandable
or or
S26361-K1566-V401 PY RX2540 M2 8x 2.5' expandable 1
or or
S26361-K1566-V112 PY RX2540 M2 12x 3.5'
CPU: x according to SAP sizing
S26361-F3849-E100 Cooler Kit 2nd CPU 1 In case of two CPU
RAM: x according to SAP sizing
HD SAS 2 SAS only!

S26361-F3694-E10 Independent Mode Installation Recommended for Standard server
or or 2 or
S26361-F3694-E2 Performance Mode Installation for HANA server
HW Options 1 GbE
S26361-F3417–E500 LAN cable 3
HW Options 10 GbE
S26361-F3629-E202 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ lp 1 10GbE Controller
S26361-F3417–E500 LAN cable 1
HW Options SAN Connectivity (only supported for physical Application Nodes, not for Hypervisor Nodes)
S26361-F4994-E(20)1or PFC EP LPe16000 (LP) or 2
S26361-F4994-E(20)2 PFC EP LPe16002 (LP) 1
HW Options general
S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1 In case running as Hypervisor Node

1 Rack mounting
1 Region kit
standard SLES
standard SLES
patching
Service Consultant
certified Partner.
For running the PRIMERGY RX2540 M2 as a HANA Node within FlexFrame Orchestrator
per CPU. This hardware is not tested or certified by SAP.
DIMM setting:
memory channels
2.2.2.3 PRIMERGY RX4770 M3
HW Basic
S26361-K1504-V200 PY RX4770 M3 1 Base Unit w/ 4 Rack Unit, red. Fan
CPU according to SAP sizing
RAM: according to SAP sizing
HD SAS 2 SAS only!
S26361-F5243-E1 PRAID EP400i 1
S26113-F5295-E160 Power Supply Module 1600W w/o power cord 2
S26361-F5295-E4 Memory Independent Mode Installation 1 Recommended
S26361-F5295-E500 RX4770M1-M3 Subm.LAN 2x10Gb optic 1 10GbE Controller
HW Options 10GbE I/O
S26361-F3629-E2 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ 1
S26361-F3986-E3 SFP+ Module Multi Mode Fiber 10GbE LC 2
HW Options SAN connectivity (only supported for physical Application Nodes, not for Hypervisor Nodes)
S26361-F4994-E1 or PFC EP LPe16000 or 2
S26361-F4994-E2 PFC EP LPe16002 1
HW Options General
S26361-F3269-E2 DVD-RW supermulti slimline SATA 1 In case running as Hypervisor Node
S26361-F2735-E285 Rack Mount Kit F2-C S7 LV 1 Rack Mount Kit

1 Rack mounting
1 Region kit
standard SLES
standard SLES
patching

Service Consultant
certified Partner.
2.2.2.3.1 RX4770 M3 as a HANA Node
For running the PRIMERGY RX4770 M3 as a HANA Node within FlexFrame Orchestrator
following CPUs and DIMMs are supported:
Order number Text
Supported CPUs
S26361-F3896-E480 Xeon E7-8880v4 22C/44T 2.20GHz 55MB
S26361-F3896-E490 Xeon E7-8890v4 24C/48T 2.20GHz 60MB
Supported DIMMs
S26361-F3898-E640 16GB (2x8GB)1Rx4 DDR4-2400 R ECC
S26361-F3898-E641 32GB (2x16GB) 1Rx4 DDR4-2400 R ECC
S26361-F3897-E645 128GB (2x64GB) 4Rx4 DDR4-2133 LR ECC
For detailed information about the SAP HANA BWoH and SoH optimized RX4770 M3 Single
Node Configurations concerning the number of CPUs and RAM sizes please see to the
Configuration Guide PRIMEFLEX for SAP HANA. All other configuration has to fit the table
above!
 HANA Single Nodes, running in a FlexFrame Orchestrator environment are not allowed to use any FusionIO
card or an internal Solid State Discs (SSD). Only 2 SAS disks are necessary for swap as described above.
 DIMM setting: homogenous symmetric assembly of DIMMs and maximum utilization of all available memory
Note:
channels
 The Fujitsu PRIMEFLEX for SAP HANA licenses D:HANA-SW-00x are not necessary for the HANA Nodes
running in a FlexFrame Orchestrator environment.
2.2.2.4 PRIMEQUEST PQ2800B2
HW Basic
MCG3AC111B Base Unit PQ2800B2 1 Base Unit PQ2800B2
MC-3HSB71B System Board PQ2800B2 according to Single Node size
CPU according to Single Node size
MC-3HMB21B Memory Extension Board PQ2800B2 according to Single Node size
RAM: according to Single Node size
MC-0PMM1 Memory Mode standard Installation 1 Recommended
MC-5HDU21B PQ2800B2 Disk Unit 1
HD SAS 2 SAS only!
MC-0JSR51 PRAID EP420i 1
MC-0JFB31 RAID Ctrl FBU option with 25cm cable 1

In case of 10GB only 1 LAN cable and 2 optical
S26361-F3417–E500 LAN cable 3
cables
MC-5HPS41 Power Supply 2.880W platinum hp 4 4 Power supply Module minimum
MC-5HFA41 Fan Unit n Depends on the number of power supplies
S26361-F3151-E200 Power cord 16A IEC320 C19->16A CEE Blue 4 Or comparable power cords
HW 1GbE I/O Unit L (1GbE, 2xbaseTports) PQ2800B
MC-3HUX31B I/O Unit L (1GbE, 2xbaseTports) PQ2800B 1
MC-0JXE41 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ LP 1
MC-0JXE51 SFP+ Module Multi Mode Fiber 10GbE LC 2
HW Options 10GbE I/O Unit F (10GbE, 2xbaseTports) PQ2800B
MC-3HUX41B I/O Unit F (10GbE, 2xbaseTports) PQ2800B 1
MC-0JXE42 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ FH 1
HW Option SAN Connectivity (only supported for physical Application Nodes, not for Hypervisor Nodes)
MC-0JFC71 PFC EP LPe16000 LP 2
or or or FC Controller for SAN Connectivity
HW Options general

S26361-F4530-E14
Bracket 10U in asymmetrical racks or
or 1 Rack mounting
Mounting of RMK in sym. racks
S26361-F4530-E10
standard SLES
standard SLES
patching
Service Consultant
certified Partner.
In exception to the SUSE standard license metrics as defined by the SUSE EULA for the correct licensing of SLES
on PRIMEQUEST hardware only the available CPU sockets need to be covered by SLES subscriptions. Therefore,
the required SLES subscriptions depend on the number of configured system boards as follows:
Note:
1 SB: 1 * 1-2 socket subscription
2.2.2.4.1 PQ2800B2 as a HANA Node

For running the PRIMEQUEST PQ2800B2 as a HANA Node within FlexFrame Orchestrator
Order number Text
Supported CPUs
S26361-F3896-E380 Intel Xeon E7-8880v3 18C/36T 2.30GHz
S26361-F3896-E390 Intel Xeon E7-8890v3 18C/36T 2.50GHz
Supported DIMMs
S26361-F3897-E642 16GB (2x8GB)1Rx4 DDR4-2133 R ECC
S26361-F3897-E644 64GB (2x32GB) 4Rx4 DDR4-2133 LR ECC
For detailed information about the SAP HANA BWoH and SoH optimized PQ2800B2 Single
above!
Note:
channels
2.2.2.5 PRIMEQUEST PQ2800B3
HW Basic
MCH3AC111B Base Unit PQ2800B3 1 Base Unit PQ2800B2
MC-3HSB91B System Board PQ2800B3 according to Single Node size
CPU according to Single Node size
MC-3HMB31B Memory Extension Board PQ2800B3 according to Single Node size
RAM: according to Single Node size
MC-0PMM1 Memory Mode standard Installation 1 Recommended
MC-5HDU21B PQ2800B2 Disk Unit 1
HD SAS 2 SAS only!
MC-0JSR51 PRAID EP420i 1
MC-0JFB31 RAID Ctrl FBU option with 25cm cable 1

In case of 10GB only 1 LAN cable and 2 optical
S26361-F3417–E500 LAN cable 3
cables
MC-5HPS41 Power Supply 2.880W platinum hp 4 4 Power supply Module minimum
MC-5HFA41 Fan Unit n Depends on the number of power supplies
S26361-F3151-E200 Power cord 16A IEC320 C19->16A CEE Blue 4 Or comparable power cords
HW 1GbE I/O Unit L (1GbE, 2xbaseTports) PQ2800B
MC-3HUX31B I/O Unit L (1GbE, 2xbaseTports) PQ2800B 1
MC-0JXE41 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ LP 1
HW Options 10GbE I/O Unit F (10GbE, 2xbaseTports) PQ2800B
MC-3HUX41B I/O Unit F (10GbE, 2xbaseTports) PQ2800B 1
MC-0JXE42 Eth Ctrl 2x10Gbit PCIe x8 D2755 SFP+ FH 1
HW Option SAN Connectivity (only supported for physical Application Nodes, not for Hypervisor Nodes)
or or or FC Controller for SAN Connectivity
HW Options general

S26361-F4530-E14
Bracket 10U in asymmetrical racks or
or 1 Rack mounting
Mounting of RMK in sym. racks
S26361-F4530-E10
standard SLES
standard SLES
patching
Service Consultant
certified Partner.
In exception to the SUSE standard license metrics as defined by the SUSE EULA for the correct licensing of SLES
on PRIMEQUEST hardware only the available CPU sockets need to be covered by SLES subscriptions. Therefore,
the required SLES subscriptions depend on the number of configured system boards as follows:
Note:
2.2.2.5.1 PQ2800B3 as a HANA Node

For running the PRIMEQUEST PQ2800B3 as a HANA Node within FlexFrame Orchestrator
Order number Text
Supported CPUs
MC-3BEE11B Xeon E7-8880v4 22C/44T 2.20GHz 55MB
MC-3BEA11B Xeon E7-8890v4 24C/48T 2.20GHz 60MB
Supported DIMMs
MC-3CD521B 16GB (2x8GB)1Rx4 DDR4-2400 R ECC
MC-3CD621B 32GB (2x16GB) 2Rx4 DDR4-2400 R ECC
MC-3CD731B 64GB (2x32GB) 2Rx4 DDR4-2400 R ECC
MC-3CD811B 128GB (2x64GB) 4Rx4 DDR4-2133 LR ECC
For detailed information about the SAP HANA BWoH and SoH optimized PQ2800B3 Single
above!
Note:
channels
2.2.3 Blade server BX900
Beyond the mentioned components no additional components (e.g. PCI cards) are supported as
the FlexFrame AN image may not work properly. Especially SAN connectivity is not supported
on blade servers.
2.2.3.1 System cabinet BX900 S2

HW Basic
S26361-K1421-V300 PY BX900 S2 System Unit without PSU 1 Chassis with 1 x MMB and no Power Supply
S26361-F3962-E500 PY BX900 Management Blade S1 1 Redundant MMB

S26113-F606-E300 BX900 PSU 2.880W platinum hp w/o power c The amount of power supplies needed depends
3+ on the stage of expansion. Not used power supply
slots must be plugged with FAN units.
2 for MMB and 2 for each switch blade minimum.
S26361-F3417–E500 LAN cable 6+ In case 10GB option 2 for MMB connection and 4
optical for data connection
HW Options
PY CB Eth Switch/IBP 1Gb 36/8+2 (Quanta
S26361-K1304-V101 2 Option A: 1GbE LAN connectivity
SB11)
PY CB Eth Switch 10/40Gb 18/8+2 (Fujitsu
S26361-K1533-V100 2 Option B: 10GbE LAN connectivity
SBAX3)1
S26361-F3986-L3 Option B: 10 GB Option ( 2 SFP for each switch),
SFP+ Module Multi Mode Fiber 10GbE LC 4
mandatory in case of usage of SBAX2
In this system cabinet you can plug in the following blade server:
1
BX920/BX924 S1/S2 blades are not supported with this connection blade
2.2.3.3 PRIMERGY BX2560 M1
HW Basic
S26361-K1466-V200 PY BX2560 M1 Dual Server Blade 1 Need 1 slot half height in BX900S2 chassis
CPU: 2 according to SAP sizing

according to SAP sizing;
HDD: 2
Needed for Swap and log-Files
S26361-F3823-E400 PRAID CM400i 1 SAS 12G RAID HDD Module w/o Cache
S26361-F3823-E20 PRAID EM400i BP 1 SAS 12G HDD Backplane for BX2560 M1

S26361-F2749-E1 Blade installation in system unit 1
S26361-F3694-E10 Independent Mode Installation 2 Recommended

standard SLES
standard SLES
patching

Service Consultant
Corresponding Service Pack Classic for SUSE
See System Architect Linux Enterprise Server or SUSE Linux 1
certified Partner.
Enterprise Server for SAP Applications
The PRIMERGY BX2560 M1 should not be used as a HANA Node as it is no SAP

supported Entry Level System!
HW Basic

HDD: 2
S26361-F3823-E400 PRAID CM400i 1 SAS 12G RAID HDD Module w/o Cache
S26361-F3823-E20 PRAID EM400i BP 1 SAS 12G HDD Backplane for BX2560 M1

S26361-F3694-E10 Independent Mode Installation 2 Recommended

standard SLES
standard SLES
patching

Service Consultant
certified Partner.
The PRIMERGY BX2560 M2 should not be used as a HANA Node as it is no SAP

supported Entry Level System!
HW Basic

S26361-F5526-E200 SSD SATA 6G 200GB Main 1.8' N H-P EP
or or 2
S26361-F5526-E400 SSD SATA 6G 400GB Main 1.8' N H-P EP
S26361-F4008-E111 SAS RAID MEZZ connection kit 2
S26361-F4481-E1 PY SAS RAID Mezz Card 6Gb 1
S26361-F4481-E30 SSD Connection Kit 1


standard SLES
standard SLES
patching

Service Consultant
certified Partner.
For running the PRIMERGY BX2580 M1as a HANA Node within FlexFrame Orchestrator
per CPU.
DIMM setting:
memory channels
HW Basic

SSD 2
S26361-F4008-E111 SAS RAID MEZZ connection kit 2
S26361-F4481-E1 PY SAS RAID Mezz Card 6Gb 1
S26361-F4481-E30 SSD Connection Kit 1


standard SLES
standard SLES
patching

Service Consultant
certified Partner.
For running the PRIMERGY BX2580 M2 as a HANA Node within FlexFrame Orchestrator
per CPU.
DIMM setting:
memory channels
2.3 Storage System
FlexFrame V1.3A supports NetApp Network Attached Storage (NAS) and Storage Area Network
(SAN). NAS storage system is a mandatory part of a FlexFrame configuration (the volume volFF
and pool-specific volumes have to be placed on a NAS system).
For the "supplementary components" like the storage products

from NetApp it is mandatory to close a service contract that has
a comparable service level like the FlexFrame "core products"
Note
at minimum, especially including the possibility of on-site
support in case of escalations. For NetApp systems e.g. the
service level “Premium” (7x24) is necessary.
Please note: If NAS equipment used for FlexFrame V1.3A should be used for other NFS based
applications in parallel, a request for special release is necessary and additional professional
services are required for both sizing and on-site configuration. Other networks than the
FlexFrame internal networks have to be connected to the Filer by separate NICs.
We recommend that the Filer is exclusively used for FlexFrame. Automated configuration scripts
within FlexFrame can interfere with other applications using the Filer, because these scripts
modify global configuration files on the Filer.
The number and size of the disks depends on the requirements of the SAP systems running on
the FlexFrame landscape. They have to be determined by a preliminary sizing process. For
support during the sizing process please contact expert.sap. At least two NICs are required to
connect the Filer redundantly to two different switches, more NICs can be used for 1GbE
connections (2, 4, 6 or 8 are recommended) or 10Gbe connections (2 or 4).
Do not build a vif with an odd number of network interfaces, otherwise the NetApp internal load
balancing algorithm does not work optimally under high load.
2.3.1 NAS storage systems
The following NetApp Systems are released for FlexFrame V1.3A
All Flash FAS AFF8040 / AFF8060 / AFF8080EX

FAS2020 / FAS2040 / FAS2050 / FAS2220 / FAS2240
FAS2552 / FAS2554
FAS3050
FAS3140 / FAS3160 / FAS3170
FAS3210 / FAS3220 / FAS3240 / FAS3250 / FAS3270
FAS6040 / FAS6080
FAS6210 / FAS6220 / FAS6240 / FAS6250 / FAS6280 / FAS6290
FAS8020 / FAS8040 / FAS8060 / FAS8080EX
V30x0 / V31x0 / V32x0 / V60x0 / V62x0
NetApp V-Series respectively FlexArray functionality are supported on a regular basis; usage of
those can be done on a customer specific project base with extra support agreements for the
storage systems behind the gateway.
 In case of MetroCluster it is mandatory to order the NetApp service

“Initial Installation” to certify the MetroCluster Configuration.
 Please do not mix NetApp quotes of different solutions for one
project. Otherwise, during staging, there will be problems
Note
assigning the right components to the appropriate solution.
 If two solutions have to be installed in one rack, and the order has
to be split into two orders, use another rack but tag it as "not order
relevant".
2.3.2 SAN Storage systems

With FFO 1.1A data bases may also be placed on a SAN storage system. The SAN storage
models (SAN storage, FC switches) are no subject of the FlexFrame release. FlexFrame only
uses so called LUNs provided by the storage administrator. Recommended current HBAs for
the Application Nodes are the Emulex LPe16000 resp. LPe16002 HBAs.
Please note: SAN is supported only for physical rack servers - blade servers and Hypervisor
Nodes (KVM or ESX) are not supported!
2.4 Switches
2.4.1 TCP/IP (LAN)
The standard FlexFrame configuration consists of 1 GbE and 10 GbE switch groups. This
configuration offers the best price per port ratio.
However FlexFrame supports configurations with 10 GbE switch groups only. This requires
using 1 GbE ports on the 10 GbE switch group for connecting the FlexFrame Control Nodes
and for hardware management (iRMC, MMB, switch oob).
Please discuss the best possibility for your project with your presales specialists before ordering
the FlexFrame configuration!
The following FlexFrame internal LAN switches are released for FlexFrame V1.3A:
2.4.1.1 Cisco 3750 Series
Text Quantity Comment
CISCO 3750X (1/10 GB Switch)
Switch Cisco Catalyst 3750X 24T-S for FF 1 FFO name: cat3750x-24t
or
Switch Cisco Catalyst 3750X 48T-S for FF 1 FFO name: cat3750x-48t
Cisco Console Cable DB9/RJ45 1 Cable for service port
Adapter angle for PRIMECENTER and DataCenter
1
rack
Catalyst 3750-x 350W AC Secondary Power Supply 1
4-post mounting (C3KX-4PT-KIT) 1 Only for 3rd party racks
Perforated panel 1U, metal, kit 1 for mounting in 19" racks
CISCO 3750X (1/10 GB Switch) Modules - optional

4x GbE SFP ports module 3750X 1 Option A: FFO name: 4x1GbE
10GbE SFP+ / 2x GbE SFP module3750X 1 Option B: FFO name: 2x10GbE
Cisco 10GbE SFP+ Module MMF 1 Option B: 10GbE SFP Module
Optional in case 30 cm cable is too
Cisco stacking cable 50 CM/1M 1
short
Due to missing SITA Agreement with Cisco, it isn’t possible anymore to order the Cisco
switches centrally in Germany and deliver them to the regions. Therefore the Cisco
Note: switches have to be bought locally in the regions. As a consequence no factory staging
is possible anymore outside of the EU. For checking the possibility of a local staging,
please contact expert.sap@ts.fujitsu.com.
 There have to be used always at least two switches of the same type.
 For the 3750X module C3KX-NM-10G it is allowed, based on a special release, to use it as
pure 1GbE module. In that case it has to be configured as 4x1GbE. A mixed usage of
1x10GbE + 2x1GbE isn’t supported.
 NetApp FAS series with two dual ports 10GbE NICs is supported in FlexFrame V1.3A.
FAS2000 supports no 10GB in high availability configurations.
 Due to performance aspects it’s strongly recommended not to use more than 4 3750-
switches per stack. Maximal number of usable switches per stack is limited to 9 by the
manufacturer. Both rules are valid for the 1GbE and the 10GbE switches.
 An adequate Service contract has to be closed with Fujitsu locally, if available, or with local
Cisco service provider.
2.4.1.2 Cisco switch Catalyst 3750 Registration
Registration of service contract for Cisco Switch Catalyst 3750 in FlexFrame projects:
The FlexFrame service concept also includes service offerings for the Cisco switches included
in FlexFrame installations. In order to ensure Cisco delivers the service, a valid back level
service contract has to be closed and registered with Cisco right after installing the systems.
1. Mandatory service offerings

We offer the following switches for a FlexFrame installation:
 WS-C3750X-24T-S Switch Cisco Catalyst 3750X 24T-S
 WS-C3750X-48T-S Switch Cisco Catalyst 3750X 48T-S
The respective service offers for these switches are mandatory and part of the FlexFrame
Solution service. The service levels are described in the service support plan (SSP).
2.4.1.3 Cisco Nexus 5500 series

A Cisco Nexus 5500 switch group can be used for 10GbE LAN connectivity.
Quantity Text Comment

CISCO Nexus 5500 (10 GB Switch)
Chassis 32 ports(req SFP+), 2PSU
plus optionally 16 ports via one extension module N55- 32 or 48 x 10 GB
2 per switch M16UP
group Chassis 48 ports(req SFP+), xPSU
plus optionally 16, 32 or 48 ports via 1-3 extension 48, 64, 80 or 96 x 10 GB
modules N55-M16UP
According to number of
n Cisco 10GbE SFP+ Module MMF
used ports
2 per switch
SFP+ passive Twinax Cable 1, 3 or 5 meter
group
1 Cisco Console Cable DB9/RJ45 Cable for service port
Adapter angle for PRIMECENTER and DataCenter
1
rack
SFP 1Gb/s MMF, max
500m
2 Cisco 1000BASE-SX Module (GLC-SX-MMD)
optionally, to connect 2
3750G’s
CISCO Nexus 5500 (10 GB Switch) Options
Cisco Nexus 5596UP PSU Front-to-Back Airflow
1 per sw Redundancy
module spare, A/C, 100-240V, 1100W
Due to missing SITA Agreement with Cisco, it isn’t possible anymore to
order the Cisco switches centrally in Germany and deliver them to the
regions. Therefore the Cisco switches have to be bought locally in the
Note:
regions. As a consequence no factory staging is possible anymore outside
of the EU. For checking the possibility of a local staging, please contact
expert.sap@ts.fujitsu.com.
Please clarify before ordering how the peer keep alive between the Nexus
5500 switches of a switch group shall be implemented:
1. Using the FlexFrame 1 GbE switch group (CISCO 3750-X or BROCADE
ICX6430). This requires 1 additional 1 GbE port on each switch of the 1
GbE switch group for each Nexus switch.
Note:
2. Using FlexFrame-external 1 GbE customer switches. This requires 1
additional 1 GbE port per Nexus 5500 switch on customer side.
3. Connecting the management ports of both Nexus 5500 switches
directly to each other. This requires no additional 1 GbE switch ports.
However this requires configuration of inband management.
 An adequate Service contract has to be closed with Fujitsu locally, if available, or with local
Cisco service provider.
2.4.1.4 Cisco Nexus 9372 series
Order Number Quantity Text Comment
CISCO Nexus 9372
2 per switch Nexus 9372PX-E with 8 QSFP-40G-SR-BD

N9K-C9372PX-E-B18Q
group
According to number of
GLC-T n 1000BASE-T SFP
used ports
SFP-H10GB-CUxM= n 10GBASE-CU SFP+ Cable x Meter 1, 3 or 5 meter
CISCO Nexus 9372 Options
Necessary for
SFP-H10GB-CU1M= 1 10GBASE-CU SFP+ Cable 1 Meter
interconnect
2.4.1.5 Brocade IP ICX6430 / ICX6450 switches
Order number Quantity Text Comment

Brocade ICX 6450 (Example)
S26361-K1477-V110 Brocade ICX 6450-24, 24x 1GbE RJ45
2 per switch Or
or
group
S26361-K1477-V111 Brocade ICX 6450-48, 48x 1GbE RJ45
E500 -> correct lengths
will be chosen during
manufacturing (1/3/5m).
NOT released for
ICX6430 (pure 1GbE
2 per switch
S26361-F3873-E500 SFP+ active Twinax Cable Brocade 1m Switch); only usable for
group
ICX 6450 switch w/
proper 10GbE ports
enabled (2x ex works;
additional 2x w/ additional
license)
1x per ICX 6430 / 6450
S26361-F4530-E144 2 Mounting kit SW2 for BROCADE switches
switch
S26361-F2735-E10 2 Adapter angle PC/DC-Rack, till 50Kg
Valid for up to two ICX
64xx switches. Has to be
S26361-F2735-E600 1 Universal Shelf-Plate for PRIMECENTER M1 selected as virtual
component in sysarc
(XXX-V600)
Fixing or attachment of RMK in symmetrical
S26361-F4530-E10 OR racks without support bracket. OR
2
(S26361-F4530-E11) (Mounting or attachment of RMK in asymmetrical
rack incl. 1U support bracket.)
Proper SP required
2 ensuring break.fix
support.
2.4.1.6 Brocade IP VDX6740
Order number Quantity Text Comment

Brocade VDX6740 (Example)
S26361-K1540-V24 Brocade VDX6740, 24x SFP+

or 2 or
S26361-K1540-V48 Brocade VDX6740, 48x SFP+
S26361-F3873-E500 14 SFP+ active Twinax Cable Brocade custom

S26361-F3873-E310 16 Eth SFP+ MMF 10Gb LC (Brocade)
S26361-F5317-E500 2 4-Post RMK Brocade VDX6740
S26361-F4530-E141 2 Perforated panel 1U, metal, kit
Fixing or attachment of RMK in symmetrical
S26361-F4530-E10 OR racks without support bracket. OR
2
(S26361-F4530-E11) (Mounting or attachment of RMK in asymmetrical
rack incl. 1U support bracket.)
Proper SP required
2
ensuring break.fix support
The Brocade IP VDX6720 switch is only possible based on a special release request.
2.4.2 FC Switches
The FC switches are no subject of the FlexFrame release. FlexFrame only uses so called LUNs
provided by the storage administrator. Recommended current HBAs for the Application Nodes
are the Emulex LPe16000/LPe16002 HBAs.
For the FFO development and QA the ETERNUS DX200S3 storage systems and the Brocade
BR6505 FC switches have been used.
3 FlexFrame Management Software Licenses
With FlexFrame Orchestrator V1.0A a complete new license model for the FlexFrame runtime
licenses was introduced.
3.1 End User Licenses

3.1.1 License metrics
For the FlexFrame Orchestrator Software following license metrics are applicable:
 Number of FlexFrame System IDs (SIDs) running in parallel within one customer
FlexFrame environment
 Number of Server Nodes.
3.1.2 General License structure

The general license structure consists of two types of license packages:
 Base package that enable the functionality and covers an initial number of license units.
 Extension packages, necessary, if the number of the license units covered with the base
packages is not sufficient for the used units. Extension packages of one license type are
unrestricted combinable, e.g. FFO SID extension S and/or FFO SID extension M.
3.1.3 FlexFrame Orchestrator – Mandatory licenses

For each FlexFrame Orchestrator environment all FlexFrame System IDs (SIDs) have to be
licensed.
3.1.4 FlexFrame Orchestrator – Optional licenses

Additive optional functionalities like Accounting, RBAC (Role Based Access Control),
virtualization via VMware ESX, virtualization via Linux KVM or usage of SAN storage systems
are available by purchasing further runtime licenses. Therefore following license rules are valid:
 Accounting and RBAC are licensed based on the number of SIDs. All SIDs of customer’s
FlexFrame environment must be considered.
 SAN option is also licensed based on the number of the SIDs that are connected to the
SAN storage system. SAN option is only possible with physical rack servers; Blade
server and virtual machines (KVM od ESX) are not supported!
 Virtualization based on VMware ESX or Linux KVM is licensed based on the number of
server nodes that are configured as Hypervisor Nodes.
3.1.5 License Exceptions

 SIDs for the Solution Manager Diagnostics Services (SMD) are not counted at all.
 SIDs of so called “NoDBUsed” services - e.g. Web Dispatcher, TREX, … - are only
counted with factor “0.1”. NoDBUsed SIDs of the Flex-Frame environment can be listed
via the com-mand “ff_sid_adm.pl --op list-sids”.
3.1.6 Demo licenses

With FlexFrame Orchestrator it is possible to get a Demo license for all FFO Features for a
certain time period of 90 days. Therefore please order the FFO Demo license, U21348-C1002,
and the FFO license key media, U21348-C1000. You will get then license keys for all FFO Base
licenses. The demo licenses are not allowed for productive usage.
3.2 Offering packages and order items
All order items listed below are available in SystemArchitect by configuring the FlexFrame
Control Nodes RX2540 M2.
In case of extend an existing FlexFrame system, this software items has to be configured via
RX2540 M2 as an upgrade component.
Please be aware when ordering any FFO Software license that

always the FFO License key media, U21348-C1000, has to be
Note !!!
ordered additionally once within the same order!!! Otherwise
customer won’t get any FFO license key!
3.2.1 Perpetual FFO Licenses

Product Identifier
FTS:FFO-ID-001 FFO Solution Identifier 1 Mandatory for each new FFO Installation
Mandatory in case the complete FFO infrastructure has to be
U21348-C1003 FFO Staging Identifier 1
assembled within the factory
Product and license media
U21348-C1000 FFO License key media 1 Mandatory with each FFO license order
U21348-C1301 FFO V1.3A Media set 1 FFO Software, images and documentation
Mandatory License Packages
U21348-C1017 FFO Entry XS Runtime License 1 Entry XS Package, covers running FFO maximum 5 SID
U21348-C1018 FFO Entry S Runtime License 1 Entry S Package, covers running FFO maximum 10 SID
U21348-C1010 FFO Entry Runtime License 1 Entry Package, covers running FFO maximum 15 SID
U21348-C1011 FFO Base Runtime License 1 Option 1: For running FFO, covers running the first 40 SID
U21348-C1015 FFO Base S Runtime License 1 Option 2: For running FFO, covers running the first 15 SID
U21348-C1012 FFO Extension S Runtime licenses n According to need, running further 10 Runtime SID
U21348-C1013 FFO Extension M Runtime licenses n According to need, running further 20 Runtime SID
U21348-C1014 FFO Extension L Runtime licenses n According to need, running further 40 Runtime SID
Optional Accounting License Packages
Entry XS Package, covers running Accounting Feature
U21348-C1027 FFO Entry XS Accounting License 1
maximum 5 SID
Entry S Package, covers running Accounting Feature
U21348-C1028 FFO Entry S Accounting License 1
maximum 10 SID
Entry Package, covers running Accounting Feature maximum
U21348-C1020 FFO Entry Accounting License 1
15 SID
Option 1: For running Accounting Feature, covers running the
U21348-C1021 FFO Base Accounting License 1
first 40 SID
Option 2: For running Accounting Feature, covers running the
U21348-C1025 FFO Base S Accounting License 1
first 15 SID
U21348-C1022 FFO Extension S Accounting licenses n According to need, running further 10 Accounting SID
U21348-C1023 FFO Extension M Accounting licenses n According to need, running further 20 Accounting SID
U21348-C1024 FFO Extension L Accounting licenses n According to need, running further 40 Accounting SID
Optional RBAC License Packages
Entry XS Package, covers running RBAC Feature maximum
U21348-C1037 FFO Entry XS RBAC License 1
5 SID
Entry S Package, covers running RBAC Feature maximum 10
U21348-C1038 FFO Entry S RBAC License 1
SID
Entry Package, covers running RBAC Feature maximum 15
U21348-C1030 FFO Entry RBAC License 1
SID
Option 1: For running RBAC Feature, covers running the first
U21348-C1031 FFO Base RBAC License 1
40 SID
Option 2: For running RBAC Feature, covers running the first
U21348-C1035 FFO Base S RBAC License 1
15 SID
U21348-C1032 FFO Extension S RBAC licenses n According to need, running further 10 RBAC SID
U21348-C1033 FFO Extension M RBAC licenses n According to need, running further 20 RBAC SID
U21348-C1034 FFO Extension L RBAC licenses n According to need, running further 40 RBAC SID
Optional Linux KVM License Packages
Mandatory for running Linux KVM Feature, covers running
U21348-C1051 FFO Base Linux KVM licenses 1 the first KVM Host
U21348-C1052 FFO Extension Linux KVM licenses According to need, Extension for running one further KVM
n
Host
Optional VMware ESX License Packages
Mandatory for running VMware ESX Feature, covers running
U21348-C1061 FFO Base VMware ESX licenses 1 the first ESX Host
U21348-C1062 FFO Extension VMware ESX licenses According to need, Extension for running one further ESX
n
Host
Optional SAN License Packages
Mandatory for running SAN Feature, covers running the first
U21348-C1071 FFO Base SAN licenses 1 2
SID connected to SAN storage
U21348-C1072 FFO Extension SAN licenses According to need, Extension for running one SID connected
n 2
to SAN storage
FlexFrame Orchestrator Demo license
U21348-C1002 FFO Demo licenses 1 Running FFO features for e time period of 90 days
 In case of running Servers as ESX Hosts, the corresponding FlexFrame specific VMWare vSphere ESXi
Note:
runtime licenses (U21348-C109x) according to number of CPUs for each ESX host has to be ordered!
2
Only possible with physical rack servers! No Blade server or virtual machines are supported!
3.2.2 One Year FFO Subscriptions
To reduce the initial investment and allow adapting the license needs year by year, for all
“Extension Licenses” (FFO RunTime and optional functionality) so called FFO subscriptions that
are valid for one year were introduced. These subscriptions can be ordered instead of the
perpetual licenses. Following preconditions to run these licenses are necessary:
 For each FFO environment perpetual Base Licenses for the mandatory FFO RunTime and
desired optional functionality have to be acquired
 After the end of the subscription period new subscriptions can be ordered for the concrete
number of licenses needed for the next year
 Corresponding SolutionPacks valid for 1 year are offered
 All FFO license rules and FFO license checks also apply to the FFO subscriptions
 Any mix of perpetual licenses and subscriptions is allowed
Following FFO subscriptions are available:

Product and license media
U21348-C1000 FFO License key media 1 Mandatory with each FFO license order
U21348-C1301 FFO V1.3A Media set 1 FFO Software, images and documentation
Mandatory License Packages
U21348-C1012-S1 FFO Extension S Runtime licenses n According to need, running further 10 Runtime SID
U21348-C1013-S1 FFO Extension M Runtime licenses n According to need, running further 20 Runtime SID
U21348-C1014-S1 FFO Extension L Runtime licenses n According to need, running further 40 Runtime SID
Optional Accounting License Packages
U21348-C1022-S1 FFO Extension S Accounting licenses n According to need, running further 10 Accounting SID
U21348-C1023-S1 FFO Extension M Accounting licenses n According to need, running further 20 Accounting SID
U21348-C1024-S1 FFO Extension L Accounting licenses n According to need, running further 40 Accounting SID
Optional RBAC License Packages
U21348-C1032-S1 FFO Extension S RBAC licenses n According to need, running further 10 RBAC SID
U21348-C1033-S1 FFO Extension M RBAC licenses n According to need, running further 20 RBAC SID
U21348-C1034-S1 FFO Extension L RBAC licenses n According to need, running further 40 RBAC SID
Optional Linux KVM License Packages
U21348-C1052-S1 FFO Extension Linux KVM licenses According to need, Extension for running one further KVM
n
Host
Optional VMware ESX License Packages
U21348-C1062-S1 FFO Extension VMware ESX licenses According to need, Extension for running one further ESX
n
Host
Optional SAN License Packages
U21348-C1072-S1 FFO Extension SAN licenses According to need, Extension for running one SID connected
n
to SAN storage
 In case of running Servers as ESX Hosts, the corresponding FlexFrame specific VMWare vSphere ESXi
Note:
runtime licenses (U21348-C109x) according to number of CPUs for each ESX host has to be ordered!
4 Software
4.1 Operating System Software

FlexFrame Orchestrator V1.3A supports even “SUSE Linux Enterprise Server for SAP
applications” (SLES4SAP) alternatively to the standard “SUSE Linux Enterprise Server” (SLES).
The main advantage of SLES4SAP in a FlexFrame Orchestrator configuration is the extended
support period of 18 month after release of a new Service Pack.
The delivered operating system images for Control Nodes and Application nodes are prepared
to run either as SLES4SAP or as standard SLES. To make use of the advantages of
SLES4SAP the customer has to order the corresponding SUSE Linux subscription & service
packages, e.g. SLES4SAP 1-2 Sock/VM 7x24 L3 Supp. 3Y.
A mixture of SLES and SLES4SAP within one FFO configuration

Note
is not allowed.
4.2 Control Node Image

The FlexFrame Orchestrator Control Node image contains following Software parts:
4.2.1 FlexFrame Management Software

 Version V1.3A
4.2.2 Operating System

 SLES11/SLES4SAP SP4. The Linux image is included in the FlexFrame DVD media set.
4.2.3 Linux-HA
 SLES 11 SP4 HA Extension (Heartbeat 2 cluster software, included in FF software)
4.3 Application Node Images

4.3.1 PRIMERGY
4.3.2 Operating System

The Linux images are included in the FlexFrame DVD media set. The support upgrade
protection has to be ordered with each AN and CN.
 SLES11 64 Bit SP4 or SLES4SAP SP4 (AN)
 SLES12 64 Bit SP2 or SLES4SAP 12 SP2
4.4 Hypervisor Nodes

 KVM Hypervisor Node image is contained on the Control Node DVD.
 ESX Hypervisor Node image is preinstalled or the official PRIMERGY ESX Image could be
used for Installation.
4.5 SAP and Database Software
The delivery of SAP software (binaries as well as licenses) is not part of the FlexFrame delivery
and has to be ordered separately from SAP.
SAP kernels for MaxDB (previously SAPDB), Oracle Database, IBM DB2, HANA DB, Sybase
ASE and Sybase IQ are supported.
Components:
All SAP Application components like ECC, CRM, SRM, BW, EP and others, that make use of
the Basic Components mentioned above, are tested to run on FlexFrame.
Please note:
Detailed information about supported SAP components and database releases is available in
the FlexFrame support matrix at https://partners.ts.fujitsu.com/com/products/infrastruc-
solutions/FlexFrame/Pages/default.aspx.
4.6 VMware vSphere ESXi Software

The support of VMware virtual machines as FFO Application Nodes is integrated part of
FlexFrame. For using this feature extra FFO license options are necessary (see chapter 3.1.4).
Beside these license packages the VMware vSphere 5 licenses are necessary in the needed
numbers. For running VMware vSphere ESX within FlexFrame a special discount of the
VMware licenses are available, therefore the VMware vSphere ESX licenses are capsulated by
FlexFrame order IDs (U21348-C1091/C1092/C1093) according to the requested VMware
vSphere edition (STD, Enterprise and Enterprise Plus).
4.7 Linux KVM Software

The support of Linux KVM virtual machines as FFO Application Nodes is integrated part of
FlexFrame. For using this feature extra FFO license options are necessary (see chapter 3.1.4).
To run SLES with KVM Hypervisor you have to order the “SUSE Linux Enterprise Server for 1-2
sockets, unlimited virtual machines” SNS. The “SUSE Linux Enterprise Server for 1-2 sockets or
2 virtual machines” SNS does NOT include the right to run SLES with KVM as hypervisor.
4.8 Storage Systems

4.8.1 NetApp Filer
With FlexFrame Orchestrator even ONTAP Cluster mode is supported. For the minimally
supported ONTAP versions and mode in FlexFrame see the FlexFrame support matrix.
Following compatibility agreement is effective for NetApp Disk-Storage HW:

1) The Operating System Data ONTAP remains upward compatible
2) All NAS systems with Data ONTAP are supported by FlexFrame with the for customers
currently available functionality
The functionality of aggregates, FlexVol and FlexClone is supported. The usage of virtual Filers
(MultiStore™ license [vfiler])) is supported. For FlexFrame the volumes for system data and
management information for the Filer must be reachable using the same Filer name.
Mandatory software licence:
 NFS
Optional software licences:
 MetroCluster
 Syncmirror
 Snapmirror
 SnapRestore
 SnapVault
 FlexClone
5 High Availability
5.1 General
High availability (HA) is inherent for FFO by means of spare servers, FlexFrame Agent
functionality, switch HW configuration, NAS storage etc.
Storage providers offer additive options (like MetroCluster from NetApp).
Fujitsu provides a document, which presents generic information for the design of possible
HA/DR configurations based on available solutions from our supported storage HW providers.
5.2 Cluster configuration with NetApp HW

NetApp clustered failover constantly monitors the health of the clustered filers. If it detects a
hardware failure on a Filer, it automatically initiates a failover operation to transfer the data
service to its partner Filer.
NetApp cluster provides protection against failure of one head. The configuration is meant only
for hardware redundancy and not for data redundancy. In cases where both, hardware and data
redundancy are required a MetroCluster configuration must be used, which
 provides continuous data availability for an unavailable Filer
 enables planned maintenance on a Filer without impacting data availability
 realizes an active/active configuration
Note:
Clustered Filer heads are fully supported by FlexFrame V1.3A.
More information about NetApp MetroCluster can be found at www.netapp.com.
6 Network
A very detailed description about FlexFrame Orchestrator network design and configuration is
available in the „FlexFrame Network Design and Configuration Guide“ manual, available at the
FlexFrame manual pages.
7 FlexFrame Configurations (Examples)

Please consider the following configurations are just examples. Therefore shown the port-
numbers only have an exemplary character - they can be bigger when needed.
7.1 LAN configuration

2 Control Nodes, n Application Nodes, 1 NetApp Filer, 2 Ethernet switches
Example for n=10 (10 Application Nodes, rack type):
Number of ports: 2 x 3 (CN) + 10 x 3 (AN) +2 (Filer) = 38 ports from total 48 ports are used (in
case of two 24-port switches). The remaining 10 ports (48 ports in case of two 48-port switches)
are free for connections outside the FlexFrame configuration (e.g. connection to the clients).
LAN Configuration
Control Node 1 Control Node 2
Switch 1 Switch 2
Application Node 1 Application Node n
NetApp Filer
7.2 LAN/SAN configuration with NetApp Gateway

2 Control Nodes, n Application Nodes, 1 NetApp Gateway, 2 Ethernet switches,
1 SAN storage system according to the NetApp Hardware compatibility list
Number of ports: 2 x 3 (CN) + 10 x 3 (AN) + 2 (Gateway) = 38 ports from total 48 ports are used
(in case of two 24-port switches). The remaining 10 ports (48 ports in case of two 48-port
switches) are free for connections outside the FlexFrame configuration (e.g. connection to the
clients).
LAN Configuration with NetApp-Gateway
Switch 1 Switch 2
NetApp Gateway
SAN
SAN RAID system
7.3 Configuration with SAN storage systems
2 Control Nodes, n Application Nodes including HBA, 2 IP switches, 2 FC switches, 1
SAN storage system (e.g. Ethernus),
Number of LAN ports: 2 x 3 (CN) + 10 x 3 (AN) + 4 (switch connection) = 40 ports from total 48
ports are used. The remaining 10 ports are free for connections outside the FlexFrame
configuration (e.g. connection to the clients).
SAN Configuration
NAS Storage
Ethernet-Switch 1 Ethernet-Switch 2
HBA
HBA
FC-Switch
SAN FC-Switch
LAN
FC
SAN Storage
8 How to Order FlexFrame
Incoming orders comprising more than one SAP solution (HANA Power, FlexFrame
Orchestrator) occasionally cause assignment problems of parts (server, storage, network
components, ...) to the right solution.
It is essential to follow the internal ordering process rules. A customer order can contain several
of the following Solution Identifiers:
 FTS:HANA-ID-V101: ID HANA APPLIANCE SINGLE NODE PY
 FTS:HANA-ID-V301: ID HANA APPLIANCE SINGLE NODE PQ
 FTS:HANA-ID-MN: ID HANA MULTI NODE
 FTS:FFO-ID-001: FLEXFRAME ORCHESTRATOR IDENTIFIER
but the factory system allows just one Solution Identifier per order.
For this reason it is mandatory to split the customer order with more than one of the above
Solution Identifiers into single factory orders with only ONE Solution Identifier per order.
Further on, the ordered items within the factory orders have to be logically "grouped":
1. Items not part of the SAP solution, e.g. backup components, must be located above the
Solution Identifier, if they are not already in a separate order.
2. All items of the SAP solution must be entered directly below the SAP Solution Identifier.
3. Furthermore the usual rules for entering orders in a standardized FTS order must be
observed. For example:
 All systems and components that have to be delivered separately (without rack
assembly) must be entered above the first rack entry.
 The creation of clear “rack blocks”, i.e. all the systems and components to be
assembled/integrated explicitly into a particular rack must be entered after that rack
entry.
 SystemArchitect supports this procedure automatically and should always be used as
basis for customer orders
Absolute recommendation is to create a single SAR file for each unique solution and datacenter
location, e.g. if you are building a DR scenario.
8.1 Control Nodes & FlexFrame Orchestrator
Updated:
How to order FlexFrame Orchestrator Version 1.2A00
May 23rd, 2016
Please follow the arrows Start
Hardware
Mandatory No vCC Yes
Optional 2x RX2540M2 (Control 2x PY/PQ Rack Server

Nodes) (KVM Hyper Nodes)
FFO Base/Ext KVM Option

U21348-C1051/C1052
SUSE Linux SNS

S26361-F2348-S5xx
FFO Identifier
FTS:FFO-ID-001
FF0 Media Set

U21348-C1201
FFO License key medium

U21348-C1000
FFO Staging Identifier

U21348-C1003
Solution Contract FlexFrame
Continue with Application Nodes
8.2 Application Nodes
8.2.1 Rack server RX2530, RX2540, RX4770, PQ2800B
How to order Application Nodes Updated:

Version 1.3A00
(RX2530, RX2540, RX4770, PQ2800) November 21st, 2016
Please follow the arrows!

Start
Hardware
Mandatory
RX2530/40M2 RX4770M3 PQ2800B3
Application Node Application Node Application Node
optional
SUSE Linux SNS SUSE Linux SNS SUSE Linux SNS

S26361-F2348- S26361-F2348- S26361-F2348-
S5xx S5xx S5xx
VMware STD VMware STD VMware STD
yes yes yes
2 * FF VMware STD 4 * FF VMware STD 8 * FF VMware STD

Yes Yes Yes
License License License
No No No
U21348-C1091 U21348-C1091 U21348-C1091
VMware ENT VMware ENT VMware ENT
yes yes yes
2 * FF VMware ENT 4 * FF VMware ENT 8 * FF VMware ENT

License License License
No No No
U21348-C1092 U21348-C1092 U21348-C1092
VMware VMware VMware

ENT PL ENT PL ENT PL
yes yes yes
2 * FF VMware ENT PL 4 * FF VMware ENT PL 8 * FF VMware ENT PL

License No License License
No No
U21348-C1093 U21348-C1093 U21348-C1093
Another Another Another

Yes Yes Yes
RX2540? RX4770? PQ2008?
Continue with FFO Software Licenses
8.2.2 PRIMERGY BX900 Bladeserver
How to order Application Node Updated:

Version 1.3A00
(BX900 Bladeserver) November 21st, 2016
Please follow the arrows! Hardware Mandatory optional
BX900S2 System unit
10GbE SBAX3 switch blade
BX2560M2 BX2580M2
Application Node Application Node
SUSE Linux SNS SUSE Linux SNS

S26361-F2348- S26361-F2348-
S5xx S5xx
VMware VMware
STD STD
yes yes
2 * FF VMware STD 2 * FF VMware STD

License No License No
U21348-C1091 U21348-C1091
VMware VMware
Yes ENT Yes
ENT
yes yes
2 * FF VMware ENT 2 * FF VMware ENT

No No
License License
U21348-C1092 U21348-C1092
VMware VMware
ENT PL ENT PL
yes yes
2 * FF VMware ENT PL 2 * FF VMware ENT PL

License No License No
U21348-C1093 U21348-C1093
Another Another
Blade? Blade?
Continue with FFO Software Licenses
8.3 FFO Management Software licenses
8.3.1 Expandable Software license packages
How to order FlexFrame Management Software Updated:

Version 1.3A00
Runtime licenses November 21st, 2016
Start
Mandatory
1 * FFO Base (S) Runtime SID license
U21348-C1011/-C1015
optional
n * FFO Extension S/M/L Runtime SID licenses

U21348-C1012/C1013/C1014
FFO Accounting Option FFO RBAC Option
1 * FFO Base (S) Accounting license 1 * FFO Base (S) RBAC license
U21348-C1021/-C1025 U21348-C1031/-C1035
n * FFO Extension S/M/L Accounting licenses n * FFO Extension S/M/L RBAC licenses
U21348-C1022/C1023/C1024 U21348-C1032/C1033/C1034
FFO VMware ESX option FFO Linux KVM option
1 * FFO Base VMware ESX license 1 * FFO Base Linux KVM license
U21348-C1061 U21348-C1051
n * FFO Extension VMware EESX licenses n * FFO Extension Linux KVM licenses
U21348-C1062 U21348-C1052
FFO SAN Option
1 * FFO Base SAN license

U21348-C1071
n * FFO Extension SAN licenses

U21348-C1072
End
8.3.2 Non expandable Software license packages
How to order FlexFrame Management Software Updated:

Version 1.3A00
Runtime licenses November 21st, 2016
Start
Mandatory
1 * FFO Entry (XS/S) Runtime SID license
U21348-C1010/C1017/C1018
optional
FFO Accounting Option FFO RBAC Option
1 * FFO Entry (XS/S) Accounting license 1 * FFO Entry (XS/S) RBAC license
U21348-C1020/C1027/C1028 U21348-C1030/C1037/C1038
FFO VMware ESX option FFO Linux KVM option
1 * FFO Base VMware ESX license 1 * FFO Base Linux KVM license
U21348-C1061 U21348-C1051
n * FFO Extension VMware EESX licenses n * FFO Extension Linux KVM licenses
U21348-C1062 U21348-C1052
FFO SAN Option
1 * FFO Base SAN license

U21348-C1071
n * FFO Extension SAN licenses

U21348-C1072
End
9 Upgrade and Implementation to FlexFrame Orchestrator
V1.3A
Detailed information about the possible upgrade processes and the economical details are
available on the Service Partner Portal
FUJITSU has developed an upgrade process for customers to upgrade from existing FlexFrame
Orchestrator V1.1A/ V1.2A configurations to FFO V1.3A.
Upgrades from former FlexFrame for SAP Versions are only possible via upgrade and migrate
to FlexFrame orchestrator V1.0A.
For more information please contact expert.sap@ts.fujitsu.com.
10 Professional Services for FlexFrame Solutions

The service offering and prices are subject to the individual countries/regions, so there may be
differences. Establishment of an experienced project management is always required for the
implementation phase of a FlexFrame project.
Staging for FlexFrame configurations is strongly recommended to ensure high quality and fast
implementation and is included in the software license (no separate order number!). For more
details please contact expert.sap@ts.fujitsu.com.
10.1 Mandatory Services for FlexFrame V1.3A Implementation and Update

The following picture gives an overview of the professional service offer in the FlexFrame area.
The red marked services are mandatory for a FlexFrame implementation project. The red doted
marked services are highly recommended.
10.2 Process Description for a Service Offer
The next picture visualizes the process to get a service and product offer. In general the Service
Manager in a country is responsible to enable sales and presales people to prepare a complete
service offer in terms of professional services as well as in term of product related services and
solution service.
11 Maintenance & Support
11.1 Integration services

Customers are not allowed to upgrade their FlexFrame installation. Therefore they will get an
offer for additional services at local prices.
11.2 Maintenance services – Solution Contract

To provide most effective product related services one SolutionContract for one FlexFrame
Infrastructure is mandatory as well as service contracts for network and storage products.
The Solution Contract FlexFrame provides the following service elements:
4. Technical solution support for the complete FlexFrame infrastructure,
inclusive prequalification of problems regarding storage and network
5. Software break fix 2nd Level Diagnosis for operating system and FlexFrame Management
software
6. Hardware break fix 2nd Level Diagnosis and onsite support for server CC, AN and HN
7. Proactive services
8. Provision of software patches and service packs for operating system and FlexFrame
Management software
9. Upgrade the FlexFrame license to next FlexFrame release.
Customer with a SolutionContract calls the technical solution support team regardless if SW or
HW, FUJITSU, SUSE, NetApp or Cisco (see also chapter 2.4.1). The technical solution support
is delivered by the FUJITSU central support organization. A team of FlexFrame trained
specialists will offer a one stop FlexFrame infrastructure support FlexFrame management
software related issues will either be fixed through already existing patches or are escalated to
the FlexFrame development team.
FUJITSU software and operating system related issues will be fixed through patches or updates
offered as a download on the respective servers.
Issues related to FUJITSU hardware will be isolated and forwarded to the local country service
organization according to respective break fix process.
Issues related to non-FUJITSU soft- or hardware will be forwarded to the appropriate service
provider if appropriate information is provided through the Read-to-Service process.
Prerequisites are valid back level support packages for every system in the configuration.
More details concerning FlexFrame SolutionContract are available on the Solution Support
pages.
11.2.1 Remote Support Access
Due to the discontinuation of the Fujitsu Support Gateway as of April 1st, 2016, the remote
access, trap forwarding and auto call function requires the installation and usage of the Fujitsu
Software AIS Connect Gateway, which runs as application on a physical or virtual Linux Server.
Please consult the Remote Services site below for further detailed information:
https://partners.ts.fujitsu.com/remoteservice_en
This software is free of charge and it is available via the Remote Services site (-> AIS Connect -
> Downloads). One AIS Gateway can be used for all Fujitsu products and solutions at customer
site. The AIS Gateway is not required for staging process.
Components to be ordered if required:

Note A physical or a virtual Linux server with SLES or RHEL Linux operating system released for the AIS
Gateway is required. The required server components and services need to be ordered separately if not
provided by customer.
11.2.2 How to order SolutionContract FlexFrame
Updated:
How to order Maintenance service for FlexFrame Version 1.3A00
November 21st, 2016
Sales/ presales
Configuration
Customer discuss support
by CoE
request requirements with the
customer
Sizing by CoE
Configuration
Offer creation
and Service order number
by sales backoffice
information
Storage
service offer
Service offer
Product offer FlexFrame for SAP Network
Infrastructure service offer
Service offer
SolutionContract
FlexFrame
Customer
order
Primergy & service order

FlexFrame SW service order
SUSE SnS storage &
product order and FlexFrame
product order network
delivery SolutionContract
and delivery
Service contract
SolutionContract
FlexFrame service order to change HW or SW
Serviceschedule II
Service schedule I
core component to add new list items as
1.) FFO Solution Identifier contracted asset when
delivery note 2.) FFO Base SID Runtime FlexFrame configuration
serial no
3.) SUSE SnS grows
4.) Server HW
renewal SUSE &
optional component VMware SnS per
5.) FFO Accounting server after
6.) FFO RBAC inital 3 year
7.) FFO Linux KVM
8.) FFO Vmware ESX
9.) FFO SAN support
Contract activation / Asset management / Accounting
Mainly in the German sales region, the sales back office (SBO) will provide a product offer as
well as the necessary service offers for a FlexFrame infrastructure, based on the configuration
and service information provided by FUJITSU sales / presales experts.
Maintenance services for storage and network products will be offered according to the
available FUJITSU service portfolio or from an external supplier.
SolutionContract FlexFrame is based on a service contract document, as defined within the
FUJISTU service portfolio, to cover the general legal issues. The product details are usually
outlined in a service schedule. Please ensure that one “Solution Identifier” is part of the initial
order for a FlexFrame infrastructure. This unique identifier (serial number) is used as a bracket
for all assets within the SolutionContract. One list item for every hardware or software product
according to the configuration information is shown with the respective service level and service
prices. FUJITSU central price office provides the SolutionContract service pricelist.
The finance back office in the country coordinates the product and service delivery after the
customer ordered the FlexFrame infrastructure. The delivery note contains the serial numbers
for the respective line items in the service schedule and is necessary to active the service
contract.
11.3 Maintenance Service – Back level support

In some cases it is not possible to provide a SolutionContract for a FlexFrame
infrastructure. These cases could be caused by:
 First and second level support is provided through a FlexFrame Service Partner.
 Country region isn’t able to deliver a complete SolutionContract.
In those cases all order automatism covered through the SolutionContract like prolongation
of SUSE or VMware SNS have to be managed through the Service Partner or the Country
region. The FlexFrame back level support has to be ordered through service partner /
country region separately for each FlexFrame installation.
11.3.1 FlexFrame Management Software back level support

The FlexFrame management Software back level support comprises the following activities:
 Error correction by providing patches for a supported release in which the error
occurred or in a new release.
 Provision of patches, service packs, upgrades to new releases and FlexFrame
management software updates to new versions.
For each FlexFrame Orchestrator license package (see chapter 3.2) corresponding back
level support packages – either one year duration or three year duration – are available and
have to be ordered correspondingly. Syntax of the order items is even very simple: U21348-
C10xx-W1/-W3.
11.3.2 Suse Linux ES Subscriptions

The initial SLES subscriptions have to be ordered together with the server hardware. In
case of a SolutionContract the costs are covered with the SolutionContract fees. In cases
without a SolutionContract the costs have to be covered by customer or service provider.
Prolongation of the SLES subscriptions has to be managed by the customers or the service
provider.
11.3.3 VMware vSphere ESXi Service packs

Similar as the SLES subscriptions is the behavior concerning the VMware vSphere ESXi
service packs. Initial service pack has to be ordered together with the licenses, costs have
to be covered by customer or service provider. Even the prolongation of the service packs
has to be managed by the customer or service provider.
11.3.4 Fujitsu’s Hardware Service Packs

The standard Fujitsu hardware service packs and prolongations have to be used.
11.3.5 3rd-Party Hardware Service Packs

Valid back level support packages for every 3rd party system in the configuration are
prerequisite and in responsibility of customer or service provider. Forwarding of issues to
the 3rd party provider has to be managed by customer or service provider.

SAP HANA Developer Quick Start Guide en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP HANA Developer Quick Start Guide en

Uploaded by

Copyright:

Available Formats

FlexFrame® Orchestrator

For internal use only

Fujitsu Technology Solutions, Germany

Modified by Date Description of Changes

New in this edition

 Configuration of 10 GbE switch groups only

2 HARDWARE COMPONENTS ............................................................................................ 7

2.1 Control Nodes .................................................................................................................................................... 7

2.2 Application and Hypervisor Nodes ................................................................................................................ 11

2.3 Storage System ................................................................................................................................................. 27

2.4 Switches ............................................................................................................................................................ 29

3 FLEXFRAME MANAGEMENT SOFTWARE LICENSES ................................................. 34

3.1 End User Licenses............................................................................................................................................ 34

3.2 Offering packages and order items ................................................................................................................ 35

4.1 Operating System Software ............................................................................................................................ 38

4.2 Control Node Image ........................................................................................................................................ 38

4.3 Application Node Images ................................................................................................................................ 38

4.4 Hypervisor Nodes ............................................................................................................................................ 38

4.5 SAP and Database Software ........................................................................................................................... 39

4.6 VMware vSphere ESXi Software ................................................................................................................... 39

4.7 Linux KVM Software ...................................................................................................................................... 39

4.8 Storage Systems ............................................................................................................................................... 39

5 HIGH AVAILABILITY ....................................................................................................... 41

5.1 General ............................................................................................................................................................. 41

5.2 Cluster configuration with NetApp HW ........................................................................................................ 41

7 FLEXFRAME CONFIGURATIONS (EXAMPLES) ............................................................ 42

7.1 LAN configuration........................................................................................................................................... 42

7.2 LAN/SAN configuration with NetApp Gateway ........................................................................................... 43

7.3 Configuration with SAN storage systems ...................................................................................................... 44

8 HOW TO ORDER FLEXFRAME ...................................................................................... 45

8.1 Control Nodes & FlexFrame Orchestrator ................................................................................................... 46

8.2 Application Nodes ............................................................................................................................................ 47

9 UPGRADE AND IMPLEMENTATION TO FLEXFRAME ORCHESTRATOR V1.3A ........ 51

10 PROFESSIONAL SERVICES FOR FLEXFRAME SOLUTIONS ...................................... 51

10.2 Process Description for a Service Offer .................................................................................................... 52

11 MAINTENANCE & SUPPORT ......................................................................................... 53

11.1 Integration services ..................................................................................................................................... 53

11.2 Maintenance services – Solution Contract................................................................................................ 53

11.3 Maintenance Service – Back level support ............................................................................................... 56

Prescribed terminology: the 2 Control Nodes (CN) are named as one

2.1 Control Nodes

S26361-F3694-E10 Independent Mode Installation 2

S26361-F3849-E100 Cooler Kit 2nd CPU 1

S26361-F3934-E511 8GB (1x8GB) 1Rx4 DDR4-2400 R ECC 4 32GB minimum

S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1

S26361-F3820-E100 HD SAS 6G 1TB 7.2K HOT PL 3.5'' BC 2 For example

S26361-F5243-E1 PRAID EP400i 1 Raid Controller

S26113-F574-E13 Modular PSU 800W platinum hp 2 2 recommended for High Availability

S26361-F4610-E202 PLAN CP 2x1Gbit Cu Intel I350-T2 LP 1 1GbE Controller

S26361-F3417-L6xx LAN cable 3 Length depends on assembly

S26361-F5302-E100 PLAN EM blind panel 1

T26139-Y1968-E100 Cable powercord rack, 4m, grey 2

S26361-F1790-E243 iRMC S4 advanced pack 1

S26361-F3120-E40 Serial Port Option 1

S26361-F2735-E175 Rack Mount Kit F1 CMA QRL LV 1 Rack Mount Kit

S26361-K1566-V101 PY RX2540 M2 8x 2,5” 1

S26361-F3849-E120 Intel Xeon E5-2620v3 6C/12T 2.40 GHz 2

S26361-F3694-E10 Independent Mode Installation 2

S26361-F3849-E100 Cooler Kit 2nd CPU 1

S26361-F3843-E516 16GB (1x16GB) 2Rx4 DDR4-2133 R ECC 6 96GB minimum

S26361-F3778-E1 DVD-RW supermulti ultraslim SATA 1

S26361-F3818-E130 HD SAS 6G 300GB 10K HOT PL 2.5'' EP 2

S26361-F5243-E1 PRAID EP400i 1 Raid Controller