Version 1 - Fujitsu Technology Solutionsmanuals.ts.fujitsu.com/file/12556/FF12A00_Management_Tool.pdf · 6.2.1 "Add" / "Delete" ... The FlexFrame Management Tool works together with

FlexFrame® Orchestrator

Version 1.2A

Management Tool

Edition November 2015 Document Version 1.0

Fujitsu Limited

© Copyright 2015 Fujitsu Technology Solutions GmbH

PRIMEFLEX® is a registered trademark of Fujitsu Limited in Europe and other countries.

FlexFrame® and PRIMERGY™ are trademarks or registered trademarks of Fujitsu Limited in

Japan and other countries.

SAP®, SAP NetWeaver®, SAP HANA® and other SAP products and services mentioned

herein are trademarks or registered trademarks of SAP SE in Germany and in several other

countries.

Linux® is a registered trademark of Linus Torvalds

SUSE is a registered trademark of SUSE LLC in the United States and other countries.

Oracle™ and Java™ are trademarks of ORACLE Corporation and/or its affiliates

Intel® and PXE

® are registered trademarks of Intel Corporation in the United States and other

countries

MaxDB® is a registered trademark of MySQL AB, Sweden

MySQL® is a registered trademark of MySQL AB, Sweden

NetApp® and the Network Appliance® logo are registered trademarks and Network

Appliance™ and Data ONTAP™ are trademarks of NetApp, Inc. in the U.S. and other

countries.

VMware®, ESX

®, ESXi, VMware vCenter, VMware vSphere are registered trademarks or

trademarks of VMware, Inc. in the United States and/or other jurisdictions.

Ethernet® is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel

Corporation

Windows® and Word

® are registered trademarks of Microsoft Corporation

All other hardware and software names used are trademarks of their respective companies.

All rights, including rights of translation, reproduction by printing, copying or similar methods,

in part or in whole, are reserved.

Offenders will be liable for damages.

All rights, including rights created by patent grant or registration of a utility model or design,

are reserved. Delivery subject to availability. Right of technical modification reserved.

Management Tool

Contents

1 Introduction ..................................................................................................... 1 1.1 Notational Conventions ..................................................................................... 2 1.2 Document History .............................................................................................. 3 1.3 Related Documents ........................................................................................... 3 1.4 Naming Information ........................................................................................... 3

2 Network Concept ............................................................................................. 3 2.1 Brief Abstract of the Network Concept .............................................................. 3 2.1.1 Mandatory Network Segments .......................................................................... 3 2.1.2 Optional Network Segments .............................................................................. 3 2.2 FlexFrame Network External Connections ........................................................ 4 2.2.1 External Connectivity ......................................................................................... 4 2.2.2 Client LAN Connectivity ..................................................................................... 4 2.2.2.1 Global Connectivity - Client LAN Connection .................................................... 4 2.2.2.2 Core Switch Client LAN Connection .................................................................. 4 2.2.3 Core Switch Connectivity for Devices ................................................................ 5 2.2.4 Uplinks for Switch Groups ................................................................................. 5 2.2.4.1 Uplinks to the corporate network using the Core Switch ................................... 5 2.2.4.2 Uplinks between FlexFrame Switch Groups ...................................................... 6 2.3 Define SNMP Communities ............................................................................... 6 2.4 Host Names....................................................................................................... 7

3 Storage Concept .............................................................................................. 9 3.1 Supported Storage ............................................................................................ 9 3.2 SAN Storage ..................................................................................................... 9 3.3 NAS Storage ................................................................................................... 10 3.3.1 ONTAP operating mode .................................................................................. 10 3.3.2 cDOT operating mode ..................................................................................... 10 3.3.3 cDOTSingle operating mode ........................................................................... 11 3.3.4 VNX operating mode ....................................................................................... 11

4 Working with the Management Tool ............................................................ 13 4.1 Supported Administration Commands ............................................................. 13 4.2 Operating Mode Differences............................................................................ 17 4.2.1 Features Overview .......................................................................................... 17 4.2.2 Differences in Performing Actions ................................................................... 19 4.3 Starting the Management Tool ........................................................................ 20 4.4 Exit the Management Tool .............................................................................. 21 4.5 Screen Layout of the Management Tool ......................................................... 22 4.6 Error Logging ................................................................................................... 25

5 Brief Instruction for Creating a New FlexFrame Configuration ................. 27

Contents

Management Tool

6 Menu Functions ............................................................................................. 31 6.1 "File" Menu ...................................................................................................... 31 6.1.1 Creating a New Configuration .......................................................................... 31 6.1.1.1 "New Configuration" Function .......................................................................... 32 6.1.1.2 "Open LDAP Connection" Function ................................................................. 36 6.1.1.3 "Open Local LDAP Connection" Function........................................................ 38 6.1.1.4 "Open Configuration File" Function ................................................................. 38 6.1.2 Modifying an Existing Configuration ................................................................ 39 6.1.3 Saving a Configuration .................................................................................... 40 6.1.4 Saving for Installation ...................................................................................... 41 6.1.5 Printing a Configuration ................................................................................... 42 6.2 "Edit" Menu ...................................................................................................... 42 6.2.1 "Add" / "Delete" ................................................................................................ 43 6.2.2 "Undo" / "Redo" ............................................................................................... 43 6.2.3 "Update Views" ................................................................................................ 44 6.2.4 "Options/Preferences" ..................................................................................... 45 6.3 "Tools" Menu ................................................................................................... 47 6.3.1 Validating a Configuration................................................................................ 47 6.3.2 Erasing the LDAP and XML Validation Errors ................................................. 48 6.3.3 Generating a Network Wiring Plan .................................................................. 49 6.3.3.1 Automatic Generation ...................................................................................... 49 6.3.3.2 Manual Generation .......................................................................................... 49 6.3.4 Generating Global Connectivity ....................................................................... 50 6.3.4.1 Automatic Generation ...................................................................................... 51 6.3.4.2 Manual Generation .......................................................................................... 52 6.3.5 Generating Host Parts of IP Addresses ........................................................... 53 6.3.5.1 Generate Host Parts Automatically .................................................................. 54 6.3.5.2 Generate Host Parts Manually ......................................................................... 54 6.4 "Mode" Menu ................................................................................................... 54

7 Object Tree ..................................................................................................... 55 7.1 General Features ............................................................................................. 55 7.2 "FlexFrame" Object.......................................................................................... 56 7.3 "Control Center" Object ................................................................................... 57 7.4 "Network" Object ............................................................................................. 59 7.5 "Storage" Object .............................................................................................. 62 7.5.1 NAS Storage .................................................................................................... 62 7.5.2 SAN Storage .................................................................................................... 63 7.6 "Pools" Object .................................................................................................. 64 7.7 "Hypervisor Nodes" Object .............................................................................. 71 7.8 "Chassis" Object .............................................................................................. 74 7.8.1 Switch Blades .................................................................................................. 75 7.9 "Global Connectivity" Object ............................................................................ 75

8 View Area ....................................................................................................... 77

Contents

Management Tool

8.1 General Features ............................................................................................ 77 8.2 "General Information" ...................................................................................... 79 8.3 "Pools" ............................................................................................................. 80 8.4 "Networks" ....................................................................................................... 82 8.5 "Controlling" ..................................................................................................... 83 8.6 "Application Nodes" ......................................................................................... 86 8.7 "NAS Storage" ................................................................................................. 89 8.8 "Volumes" ........................................................................................................ 91 8.8.1 "Volumes / Volume groups" ............................................................................. 91 8.8.2 "Volume groups / LUNs" .................................................................................. 92 8.8.3 "Pool / SID / Node Mount" ............................................................................... 92 8.9 "SAP Services" ................................................................................................ 94 8.10 "Users Groups Services" ................................................................................. 97 8.11 "External Connectivity" .................................................................................... 98 8.12 "Chassis" ....................................................................................................... 101 8.13 "Hypervisor Nodes" ....................................................................................... 102 8.14 "Wiring".......................................................................................................... 103 8.15 "IPs" .............................................................................................................. 105

9 Execution Area ............................................................................................ 107 9.1 General Overview .......................................................................................... 107 9.2 Administration Commands Overview ............................................................ 108 9.3 Validation....................................................................................................... 110

10 Actions ......................................................................................................... 113 10.1 Actions Overview ........................................................................................... 114 10.1.1 Actions Overview Table ................................................................................. 114 10.1.2 Other administrative commands available in Administration Mode ............... 117 10.2 Context Menu of Selected Objects ................................................................ 118 10.3 Adding Hypervisor Nodes .............................................................................. 119 10.4 Adding Complete Configuration..................................................................... 120 10.5 Adding Application Nodes ............................................................................. 121 10.6 Adding New AN (Create an AN Image) ......................................................... 124 10.7 Adding Blade Server Chassis ........................................................................ 125 10.8 Adding Data NICs .......................................................................................... 126 10.9 Adding External Connectivities (Pool-specific) .............................................. 126 10.10 Adding LAN Interfaces .................................................................................. 127 10.11 Adding Mount Points for Volumes ................................................................. 128 10.12 Adding NAS Systems .................................................................................... 129 10.12.1 Configuring a cDOT cluster in planning mode ............................................... 133 10.12.2 Configuring a cDOT cluster in administration mode ...................................... 137 10.13 Adding Networks ........................................................................................... 138 10.14 Adding Pool Groups ...................................................................................... 139 10.15 Adding Pools ................................................................................................. 140 10.16 Adding SAP Services .................................................................................... 142

Contents

Management Tool

10.16.1 Classic ........................................................................................................... 143 10.16.1.1 Classic Service with external HANA or R-HANA-DB ..................................... 144 10.16.2 LiveCache Service (LC) ................................................................................. 147 10.16.3 Business Objects Enterprise Service (BOBJ/SBOP) ..................................... 148 10.16.4 Content Management Server Service (CMS) ................................................ 149 10.16.5 Search and Classification Service (TRX) ....................................................... 150 10.16.6 Master Data Management Service Type (MDM) ........................................... 151 10.16.7 Solution Manager Diagnostics Service Type (SMD) ...................................... 152 10.16.8 Web Dispatcher Service Type (WD) .............................................................. 155 10.16.9 HANA and HANA-MN DB Service Type (HANA/HANA-MN) ......................... 156 10.16.10 R-HANA and R-HANA-MN DB Service Type (R-HANA/R-HANA-MN) .......... 158 10.17 Adding Switches ............................................................................................ 160 10.18 Adding Switch Groups ................................................................................... 161 10.19 Uplinks ........................................................................................................... 162 10.19.1 Adding Uplinks ............................................................................................... 162 10.19.2 Deleting Uplinks ............................................................................................. 162 10.19.3 Extend Uplinks ............................................................................................... 163 10.20 Adding Switch Ports ...................................................................................... 163 10.21 Adding Volumes ............................................................................................ 164 10.22 Adding Volume Groups ................................................................................. 165 10.23 Adding LUNs ................................................................................................. 166

11 Abbreviations ............................................................................................... 167

12 Glossary ....................................................................................................... 171

13 Index ............................................................................................................. 177

Management Tool 1

1 Introduction

The FlexFrame Management Tool is the successor of the FlexFrame for SAP Planning

Tool. It takes over all the functions of the former Planning Tool and moreover offers a

variety of new functions as well as the potential to further basic extensions of the

functionality in the future. Although its implementation compared with the predecessor is

based on fundamentally different technologies (Java and XML versus Microsoft Excel),

one aim was to give a familiar and as far as possible compatible look and feel for its

users.

The FlexFrame Management Tool works together with FlexFrame for SAP versions

4.2A.

This manual describes how to work with the FlexFrame Management Tool which enables

the certified FlexFrame consultant to enter the necessary configuration data for a

customer-specific FlexFrame environment on a Windows® PC with Java SE 6 and newly

also on other platforms, e.g. Linux.

With the Management Tool you can either work in Planning Mode or in Administration

Mode:

Planning Mode:

● create an initial FlexFrame configuration file.

● modify an existing FlexFrame configuration file .

● open an LDAP connection to a server to get a current FlexFrame configuration to be

used as initial configuration .

● create/modify the network cabling plan.

After the data has been entered correctly, it is stored in an XML file on an approved

external data medium (e.g. an USB stick) and later read in by the installation scripts

during the installation of the FlexFrame Control Center. The required FlexFrame

configuration is implemented automatically using this configuration data.

Among other things, the configuration files contain information on the:

● Network switch configuration ● DHCP parameters

● Hosts ● User and group parameters

● Services ● FlexFrame pool and group definitions

● NAS/SAN storage configuration ● SAP services

● Network boot parameters ● Database systems

● LDAP parameters ● Network wiring plan

Introduction Notational Conventions

2 Management Tool

Administration Mode:

The Administration Mode provides an easy and comfortable way to administrate the

FlexFrame system environment. The CLI commands are generated automatically by the

Management Tool and needn’t be typed in manually.

All commands are listed in the new execution area and are executed consecutively. In

Administration Mode you can directly access the FlexFrame environment. The executed

commands directly affect the FlexFrame environment.

As a technical requirement the Management Tool has to run on the Control Node to use

the administration functionality.

General Hints

The two Control Nodes (CN) of FlexFrame are also named the FlexFrame

Control Center (CC).

In this documentation the notation Control Node (CN) is used as a synonym for

Control Center (CC) and the other way round.

This document is only to be used by Certified FlexFrame Consultants who have

completed FlexFrame and Network Appliance® Filer training. They also should have

expert knowledge of Linux® OS.

SAP system installations should only be performed by consultants who are certified for

your operating system, your database, and the SAP system you are installing.

1.1 Notational Conventions

The following conventions are used in this manual:

Additional information that should be observed.

Warning that must be observed.

fixed font Names of paths, files, commands, and system output.

<fixed font> Names of variables.

fixed font User inputs in command examples

(if applicable using <> with variables).

Document History Introduction

Management Tool 3

1.2 Document History

Document Version Changes Date

1.0 First Edition 2015-11-16

1.3 Related Documents

FlexFrame® – Administration and Operation

FlexFrame® – HW Characteristics Quickguides

FlexFrame® – Installation and Configuration of LVM 2.1 Standard Edition

FlexFrame® – Installation Guide for SAP Solutions

FlexFrame® – Installation of a FlexFrame Environment

FlexFrame® – Agents Installation and Administration

FlexFrame® – Messenger Concepts and Usage

FlexFrame® – LogAgent Concepts and Usage

FlexFrame® – Network Design and Configuration Guide

FlexFrame® – Security Guide

FlexFrame® – Technical White Paper

FlexFrame® – Upgrading FlexFrame Orchestrator 1.0A or 1.1A to 1.2A

ServerView Documentation

SUSE Linux Enterprise Server Documentation

1.4 Naming Information

PRIMEFLEX for SAP Landscapes enables simplified, fast and secure implementation

and operation of SAP applications and databases. The infrastructure solution is designed,

delivered and supported as one product and supplemented by a broad services portfolio.

The integrated FlexFrame Orchestrator software offers consistent and standardized ad-

ministration of infrastructure, databases and applications.

Management Tool 1

Management Tool 3

2 Network Concept

The FlexFrame "Network Design and Configuration Guide" defines valid FlexFrame

Network configurations. In the “Management Tool Guide” you will just find a description

how to enter a valid configuration into the Management Tool.

If you are already familiar with the network concept of FlexFrame, please continue with

chapter 3 "Storage Concept" on page 9.

2.1 Brief Abstract of the Network Concept

The network is the backbone of the FlexFrame solution. Communication between the

various nodes is done exclusively over the IP network infrastructure. This is used both for

communication between server(s) and client(s) and for delivering data from the NAS

(Network Attached Storage) to the server.

The IP network infrastructure is essential for every FlexFrame configuration. FlexFrame is

designed with a dedicated network for connections between server and storage that is

reserved for FlexFrame traffic only.

The FlexFrame internal physical network configuration is fully redundant to ensure high

availability. Based on this physical network, a number of virtual network segments are

configured.

2.1.1 Mandatory Network Segments

One virtual LAN (VLAN) is used for FlexFrame infrastructure management and is called

the Control LAN. Three further VLANs, the Client LAN, the Server LAN and the Storage

LAN, are added for each pool. A pool is a set of Application Nodes in a FlexFrame

environment plus a set of preconfigured SAP services that belong to the same customer.

A pool is usually related to a client. By assigning separate VLANs to every pool these

clients are well separated. This multi-client capability of FlexFrame is an essential

feature.

2.1.2 Optional Network Segments

In addition to the mandatory Networks / LANs it is possible to add optional network

definitions to a FlexFrame installation. These optional LANs have either a global scope or

they are defined within pool scope.

Using IPs defined within these networks it is possible to assign some network traffic to

dedicated ports on a server.

Reserved names for the currently available networks are: admin, backup, hanaint,

hanarep, sapdata, saplog and livemig.

Network Concept

4 Management Tool

These networks and a short description of their usage can be found in the "FlexFrame® –

Administration and Operation" manual.

2.2 FlexFrame Network External Connections

For network connections of the internal FlexFrame networks to the customer corporate

LAN the following features are provided.

2.2.1 External Connectivity

With External Connectivity you are able to define abstract devices with one or two NICs

and with one to four LAN Addresses for the Pool specific LANs and the Control LAN.

External Connectivity exists in a pool scope.

A more detailed description of this feature is given in section 8.11 "External Connectivity"

on page 98.

2.2.2 Client LAN Connectivity

2.2.2.1 Global Connectivity - Client LAN Connection

With Global Connectivity you are able to define device independent global connectivity.

Using this feature you can define switch ports that provide access to certain (Client)

LANs. Since you are able to provide access to several Client LANs of different pools on

one redundant pair of switch ports, global connectivity is defined in a global scope, not in

a pool specific scope.

A more detailed description of this feature is given in section 7.9 "Global Connectivity"

Object on page 75.

This method for defining Client LAN connections is obsolete as of Version 5.2 of

FlexFrame. The method described in 2.2.2.2 Core Switch Client LAN Connection

should be used instead.

2.2.2.2 Core Switch Client LAN Connection

All connections between ports of a switch group and ports in the "Client LAN Uplinks"

object build a Client LAN Uplink Channel from the respective SWG to the customer

corporate LAN that handles the traffic of Client LAN VLANs only.

This method for defining Client LAN connections is recommended as of Version

5.2 of FlexFrame.

Network Concept

Management Tool 5

2.2.3 Core Switch Connectivity for Devices

You can connect NAS devices and servers to a connectivity cloud that is named "Core or

Direct".

Connecting FlexFrame devices to the "Core or Direct" cloud just means, that FlexFrame

is not configuring any switches for these devices.

“Core or Direct” in the Management Tool is just like an abstract switch positioned directly

under the Network Object (see section 7.4 "Network" Object on page 59). If not yet

existing, you can “right-click” on the Network Object and add a “Core or Direct” object. As

children of the “Core or Direct” object the two portlist objects "Ports default" and "Client

Lan Uplinks" are predefined. You can add additional portlist objects with right-click on the

“Core or Direct” object. As children of these portlist objects you can add different kinds of

switch ports, as many as you need. Via the link property of the switchport object or the

link property of a data NIC object you are able to relate the NIC of a device with the SWP

of the “Core or Direct” cloud.

All devices in a FlexFrame installation may be connected to any portlist of “Core or

Direct”.

2.2.4 Uplinks for Switch Groups

In contrast to Client LAN Uplinks the connections between ports of a switch group and

ports in the "Ports default" object build an Uplink Channel from the respective SWG to the

customer corporate LAN that handles the traffic not only of Client LAN VLANs but of any

used VLAN (additionally Server, Storage and Control LAN).

2.2.4.1 Uplinks to the corporate network using the Core Switch

Automatic creation of uplinks is done by calling the wiring menu function (see section

8.14 "Wiring" on page 103) after having set the networking properties (see Miscellaneous

Network Settings on page 60).

Uplinks for 3750 SWGs will be created as described in the networking properties. Nexus

5000 SWGs will use uppermost switch ports just below the switch ports that are used as

VPC peer links.

The wiring menu function creates uplinks. The wiring function does not

necessarily create plug compatible uplinks that you can use for any

possible direct connection of switch groups.

Manually you can create uplinks in the Management Tool by linking switch ports of a

switch group to switch ports of “Core or Direct”. To be able to set the “link” property of a

SWP to point to another SWP the “portUse” property of the SWP has to be set to “Swp

connect”. To configure uplinks to “Core or Direct” you should use different switches of a

switch group to have a failsafe uplink connection of your switch group. All connections of

a SWG to the same portlist of “Core or Direct” form one link aggregate.

Network Concept

6 Management Tool

If you want to configure more than one uplink for a switch group, you have

to use a different portlist object of “Core or Direct” for each uplink

channel, e.g. "Ports add. LAG 1".

“Core or Direct” is just an abstract, not really existing switching device that represents

network connectivity not in the responsibility of FlexFrame. If you use uplinks of two

switch groups to the same portlist of “Core or Direct” to connect these two switch groups

directly with each other, then you have to take care, that the uplinks of one switch group

use the same kind of switch ports as the uplinks of the other switch group.

To put the attention of the certified FlexFrame consultant, who is planning network

connectivity, to this fact, a warning will be displayed when validating and switch ports of

different type are found in the same portlist.

If the pointed out uplinks will not be used for a direct connection, you can ignore this

warning.

The uplinks, you want to use for a direct connection of two switch groups,

have to be plug compatible.

2.2.4.2 Uplinks between FlexFrame Switch Groups

Uplinks between FlexFrame Switch Groups can be established in two ways:

● Using the Core Switch

See section 2.2.3 Core Switch Connectivity for Devices on page 5.

● Via direct connection

In FlexFrame as of version 5.2 switch ports of different switch groups can be

connected directly. This method is recommended in the current version of

FlexFrame.

2.3 Define SNMP Communities

In order to be able to send SNMP traps to the control center, the switches of a switch

group and the switch blades of the blade chassis need a specified SNMP community.

This community is defined via the Management Tool. As default value "public" (read only)

is set. The community is set at the following locations in the object tree:

● for the control center in the "control center" object, see section 7.3 "Control Center"

Object on page 57)

● for the switches of a switch group in every switch group object

● for every switch blade object of a blade chassis

In FlexFrame select the same community for all three kinds of devices.

Network Concept

Management Tool 7

2.4 Host Names

The host names of the individual VLANs are derived from the general host names of the

respective components (e.g. Application Nodes). With exception of the Client LAN the

host names are provided with a suffix to permit an individual addressing via a VLAN

segment:

Control LAN:

Server LAN:

Storage LAN:

<general_host_name>-co

<general_host_name>-se

<general_host_name>-st

Additionally to the mandatory LANs mentioned above, in the current version the following

optional LANs are available (see also the "FlexFrame® – Administration and Operation"

manual and 2.1.2 Optional Network Segments on page 3).

Admin LAN:

Backup LAN:

Hanaint LAN:

Hanarep LAN:

Sapdata LAN:

Saplog LAN:

Livemig LAN:

<general_host_name>-adm

<general_host_name>-bak

<general_host_name>-hni

<general_host_name>-hnr

<general_host_name>-sd

<general_host_name>-sl

<general_host_name>-lm

In SAP environments host names are currently limited to 13 alpha numeric

characters including the hyphen ("-"). The first character must be a letter. In the

SAP environment host names are case-sensitive (see SAP Note No. 611361).

Management Tool 9

3 Storage Concept

3.1 Supported Storage

Storage is used on a FlexFrame global scope, at a FlexFrame pool scope and at a SAP

system scope.

FlexFrame supports the use of NAS Storage and, as of FlexFrame Orchestrator V1.1, the

use of SAN storage.

If you are already familiar with the storage concept of FlexFrame, please continue with

chapter 4 "Working with the Management Tool" on page 13.

NAS Storage is used for FlexFrame infrastructure, e.g. application node Images and

installed SAP Systems, and also as database storage for the installed SAP Systems.

Database Storage for the installed SAP Systems is storage for “sapdata” or “saplog” use.

NAS Storage, if assigned to FlexFrame global or in pool scope or in SAP system scope,

has a directory structure that allows the use by several SAP systems or pools.

SAN Storage may only be used as database storage for SAP systems, only for “sapdata”

and “saplog”. SAN Storage is only available at SAP system scope. SAN storage is

assigned to one dedicated SAP system.

Further details on the use of NAS and SAN Storage you will find later in the document

where the definition of pools and SAP services is explained.

3.2 SAN Storage

SAN storage is assigned to a SAP service by the definition of a volume group. Once a

volume group is defined you can assign this volume group to be used as “sapdata” or

“saplog” storage to a SAP system. Wherever SAN storage is a possible option it appears

for selection in the same place as NAS storage.

The definition of a volume group is sufficient for the use of SAN storage in the

Management Tool. Further details on how to use SAN storage in FlexFrame is part of the

FlexFrame® – Administration and Operation.

A volume group may be defined in more detail by assigning one or more LUN definitions

to a volume group.

No information about a SAN storage system is stored in FlexFrame except a storage

system ID. In the Management Tool the storage system ID is used to collect LUNs with

the same storage system ID in the object tree of the Management Tool.

When SAN storage is used in FlexFrame it is referenced using the name of the volume

group. NAS storage is referenced by the name of the volume.

Storage Concept

10 Management Tool

3.3 NAS Storage

NAS storage is absolutely necessary for FlexFrame. All FlexFrame system relevant

information is stored in NAS storage. As mentioned above only storage for “sapdata”,

“saplog” for installed SAP Systems may be stored in SAN storage.

NAS storage is used in the Management Tool by the definition of a volume. Just looking

at the Management Tool aspect of assigning storage to SAP systems you can use NAS

volumes instead of SAN volume groups or vice versa.

NAS Storage systems are handled in FlexFrame in more detail than SAN storage

systems. This allows better support of administration of NAS storage. In FlexFrame there

are NAS storage systems that can have volumes and NAS storage systems that must not

have any volumes. For some NAS systems it depends on the operating mode if they can

or must not have volumes. In FlexFrame NAS systems that can have volumes are called

“NAS end point”. In the Management Tool you may only create volumes on NAS end

points.

FlexFrame NAS systems may have two operating modes: ONTAP or cDOT. Relations

may only exist between NAS systems in the same operating mode.

3.3.1 ONTAP operating mode

In ONTAP operating mode FlexFrame NAS storage systems always can have volumes.

There is one virtual NAS storage system: a VFILER. A VFILER always has a “parent”

relation to the physical NAS system in ONTAP mode that it resides on.

ONTAP mode NAS systems may be clustered in HA Pairs. In this case both physical

NAS systems reference each other via a “partner” relation.

3.3.2 cDOT operating mode

In cDOT operating mode there are only the virtual NAS devices SVM and LIFthat can

have volumes. Only SVM or LIF may be a “NAS end point”.

The definition of a SVM defines already the first LIF that is necessary to access the

storage. More relations of IP addresses to physical ports can be defined by using LIF

objects in the MgmtTool.

All other NAS devices that are dealt with in cDOT mode, the physical HA pairs as well as

the virtual cDOTCluster serve only to define the physical environment for SVMs or LIFs.

Several HA pairs build one cDOTCluster, a cDOTCluster can home several SVMs.

In the Management Tool you have to define one or more HA pairs, each pair has the

same partner relations as a HA pair in ONTAP mode. The cDOTCluster is defined by the

parent relations of all HA pairs that point to the virtual cDOTCluster.

Since FlexFrame may need locality information, all SVMs defined for the cDOTCluster

Storage Concept

Management Tool 11

have a parent relation to one of the HA pairs, that build the cDOTCluster – the homing

cluster is referenced indirectly by SVMs.

3.3.3 cDOTSingle operating mode

The cDOTsingle operating mode is equivalent to the cDOT operating mode except that

there is no HA pair necessary to operate a SVM. In this operating mode only a few NAS

systems (e.g. FAS8040) can be configured.

3.3.4 VNX operating mode

VNX operating mode is only available on special release . This operating mode is

designed to support EMC Celerras / VNX Systems.

Using partner, parent and interface relations it is possible to configure a Celerra system

with Control Stations and Data Movers.

For a more detailed description of the hardware and the terms used to configure a

Celerra system in FlexFrame see the “HW Characteristics EMC® VNX2® Series” or the

“HW Characteristics EMC® VNX2® Series – Virtual DATA MOVERS on VNX®” quick

guide.

Management Tool 13

4 Working with the Management Tool

The Management Tool comprises two modes:

● Planning Mode

● Administration Mode:

You can choose the mode in the menu bar in the Mode menu.

The Planning Mode comprises all known features. The Administration Mode provides

access to most of the features and commands known from the Planning Mode.

The fundamental difference between the Planning Mode and the Administration Mode

is the direct access of the Management Tool to the FlexFrame environment when using

the Administration Mode.

To use Administration Mode, the Management Tool must run on the FlexFrame Cluster

Node with root privileges.

If you use the Management Tool offline, with no direct access to the FlexFrame environment, the Mode menu is not displayed. The Management Tool can then

just be used in Planning Mode.

4.1 Supported Administration Commands

ff_pool_adm.pl --op add/rem --name <poolname> …

Accessible via:

● Add: Context menu of: /FlexFrame/Pools

● Delete: Context menu of: /FlexFrame/Pools/<poolname>

● Add/Delete Pool Button in the Pools table

ff_poolgroup_adm.pl --op add/rem --group <groupname>…

Accessible via:

● Add: Context menu of: /FlexFrame/Pools/<poolname>/Groups

● Delete: Context menu of: /FlexFrame/Pools/<poolname>/Groups/<groupname>

● Add/Delete Group Button in Application Nodes Tabelle

ff_sid_adm.pl --op add/del --pool <poolname> --sid <sidname> …

Accessible via:

Working with the Management Tool

14 Management Tool

● Add: Context menu of: /FlexFrame/Pools/<poolname>/SIDs

● Delete: Context menu of: /FlexFrame/Pools/<poolname>/SIDs/<sidname>

● Add/Delete SAP Service Button in SAP Services table

● Add/Delete SAP Instance Button in SAP Services table

ff_setup_sid_folder.sh –p <poolName> -s <sidName> .......

Is also generated when adding a new SID.

Only as Administration Command available, always executable .

Accessible via:

● Context menu of: /FlexFrame/Pools/<poolname>/SIDs/<sidName>

ff_sid_mnt_adm.pl --op add --sid <sidName> --sapdata <volume> --

saplog<volume> …

Is generated when adding a new SID with sapdta and saplog volumes for this SID.

Only as Administration Command available.

ff_an_adm.pl --op add/rem --name <serverName> --type <type> …

Accessible via:

● Add: Context menu of: /FlexFrame/Pools/<poolname>/Groups/<groupName>/Servers

● Delete: Context menu of: …/<poolname>/Groups/<groupName>/Servers/<serverName>

● Add / Delete Application Node button in the Application Nodes table

ff_new_an.sh -n <name>…


Accessible via:

● Context menu of: /FlexFrame/Pools/<poolname>/Groups/<groupName>/Servers/<se

rverName>


Management Tool 15

ff_bx_cabinet_adm.pl --op add/del --name <cabName> --type <type> …

Accessible via:

● Add: Context menu of: /FlexFrame/Chassis

● Delete: Context menu of: /FlexFrame/Chassis/<chassisName>

● Add Chassis button in the Chassis table

ff_hn_adm.pl --op add/rem --name <hypervisorNodeName> --type

<type> …

Accessible via:

● Add: Context menu of: /FlexFrame/Hypervisor Nodes/Server List

● Delete: Context menu of: /FlexFrame/Hypervisor Nodes/Server

List/<hypervisorNodeName>

● Add / Delete Hypervisor Node button in the Hypervisor Nodes table

ff_hn_adm.pl --op complete-config –name <hypervisorNodeName>

Only as Administration Command available

Accessible via:

● Context menu of: /FlexFrame/Hypervisor Nodes/Server List

/<hypervisorNodeName>

ff_nas_adm.pl --op add/rem --name <nasName> --type <type> …

Accessible via:

● Add: Context menu of: /FlexFrame/Storage/NAS

● Delete: Context menu of: /FlexFrame/Storage/NAS/<nasName>

● Add / Delete NAS button in the NAS Storage table

ff_nas_adm.pl --op add-pool/rem-pool --name <nasName> …

Accessible via:

● Add (Netapp Filer): Context menu of: /FlexFrame/Storage/NAS/<nasName>/Storage LANs

● Delete (Netapp Filer):Context menu of: /…/NAS/<nasName>/Storage LANs/<stlanName>

● Add / Delete Pool to / from NAS button in the NAS Storage table


16 Management Tool

ff_network_adm.pl --op add/rem --name <> --network <> --pool

<pool>

Accessible via:

● Add: Context menu of: /FlexFrame/Control Center

Context menu of: /FlexFrame/Pools/<pool>

● Delete: Context menu of: /FlexFrame/Control Center/Livemig LAN

Context menu of: /FlexFrame/Pools/<pool>/<LAN name>

● Add / Delete Network button in the Networks table

ff_swgroup_adm.pl --op add/rem --name <swgName> …

Accessible via:

● Add: Context menu of: /FlexFrame/Network/Switch Groups

● Delete: Context menu of: FlexFrame/Network/Switch Groups/<swgName>

● Add / Delete Switchgroup button in the Controlling table

ff_swgroup_adm.pl --op add-sw/rem-sw --type <type> …

Accessible via:

● Add (Sw): Context menu of: /FlexFrame/Network/Switch Groups/<swgName>/Switches

● Delete (Sw): Context menu of: …/Network/Switch Groups/<swgName>/Switches/<swName>

● Add / Delete Switch button in the Controlling table

ff_swgroup_adm.pl --op add-uplink/rem-uplink/ext-uplink …


Accessible via:

● Context menu of: /FlexFrame/Network/Switch Groups/<swgName>


Management Tool 17

4.2 Operating Mode Differences

4.2.1 Features Overview

This section describes the differences between the two operating modes concerning the

menu bar and the object tree.

An additional list, comparing the individual actions that can be performed in different

object tree submenus and within the view area is provided in section 10.1 Actions

Overview on page 114.

Menu bar overview:

The following table provides an overview of the available features in the menu bar in the

two operating modes Planning Mode and Administration Mode.

"x" indicates that this feature is available, "o" indicates, that this feature is not available if

you are working in this operating mode.

Menu bar Submenu 1 Submenu 2 Planning

Mode

Administration

Mode

File New

Configuration

x o

Open Configuration File x o

LDAP Connection x o

Local LDAP Connection X

Only on CN

o

Save x o

Save for

Installation

x o

Print All x o

Wiring x o

Exit x x

Edit Add / Delete Pool x x

Switch Group x x

Application Node x x

Hypervisor Node x x


18 Management Tool

Menu bar Submenu 1 Submenu 2 Planning

Mode

Administration

Mode

Chassis x x

NAS x x

Volume x o

Mount x o

SAP Service x x

External Connectivity x o

Undo x o

Redo x o

Update Views x x

Options /

Preferences

x x

Tools Validate

Configuration

x x

Erase LDAP /

XML Read

Validation

x x

Wiring Clear Wiring x o

Clear Client LAN

Connectivity

x o

Perform Wiring x x

IP Addresses Reset All Hostparts To '0' x o

Initialize '0' Hostparts x x

Initialize '1' Hostparts x x

Initialize '0' And '1' Hostparts x x

Reload from

LDAP

x x

Mode Planning x x

Administration x x

Help About x x


Management Tool 19

4.2.2 Differences in Performing Actions

Main difference between the Planning Mode and the Administration Mode is the direct

access of the Management Tool to the FlexFrame environment when working in

Administration Mode. This includes that working in Administration Mode is a very tender

subject.

Therefore objects are highlighted prior to the execution, so you can reconsider your

decision:

● Adding objects:

Objects to be added are highlighted in yellow in the object tree. Every field which is

editable can still be modified.

● Deleting objects:

Objects to be deleted are highlighted in red in the object tree. The fields cannot be

modified anymore.

Example:

In this example the pool "testpool" should be deleted. The pool and all objects are highlighted in red. You can reconsider your decision prior to the execution.

In Administration Mode every action (modification, adding, deleting) has to be executed

via the button Execute. Only then the action is performed directly on the FlexFrame

environment. For more details see chapter 9 Execution Area on page 107.


20 Management Tool

4.3 Starting the Management Tool

The Management Tool is shipped on the Service CD in the directory /config.

To start the Management Tool in an already existing FlexFrame environment open the

following directory on the Cluster Node: /opt/FlexFrame/MgmtTool .

The Management Tool consists of the following files:

● MgmtTool.jar

● xercesImpl.jar

● xml-apis.jar

● ff_hardware.xml

● ff_globals.xml

● ff_sap.xml

On the Cluster node the ff_….xml files are located in the directory

/opt/FlexFrame/etc. However, if a ff_….xml file exists in the current

directory it is used instead of the equivalent in the directory

/opt/FlexFrame/etc.

Copy the files into the same directory under Windows or Linux.

You can start the Management Tool in the Windows Explorer doing a double click on MgmtTool.jar.

● You also can start the Management Tool on the command line interface in the

following way:

● Navigate to the directory which contains the MgmtTool.jar.

● Type java –jar MgmtTool.jar

The Management Tool will run under JRE 1.6 or higher.

The screen of the Management Tool opens. For an explanation of the different areas see

section 4.5 Screen Layout of the Management Tool on page 22.

When started the Management Tool initially shows the Planning Mode.


Management Tool 21

The Management Tool in Planning Mode supports a recovery function

(Undo/Redo). For this purpose each action is stored in an undo buffer. If

the undo buffer is full the oldest stored action is deleted from the buffer

and the newest one is stored.

If you delete an object by mistake, you can repair it by performing the Undo

function in the Edit menu or

if the action that deleted the object is no longer stored in the undo buffer, you

can repair the deleted object by

● adding it again or

● saving frequently to a configuration file and reading in the configuration file again with the Open -> Configuration File function.

In the latter case, all input that you made previously is lost.

Attention when working in Administration Mode!

In Administration Mode you have direct access to the FlexFrame environment.

4.4 Exit the Management Tool

You exit the Management Tool by selecting Exit in the File menu.


22 Management Tool

4.5 Screen Layout of the Management Tool

The screen of the Management Tool consists of three different areas, in which you can

execute the configuration tasks.

The following figure displays the screen layout in Administration Mode. The

screen layout in Planning Mode is structured the same way, but without area

no.


Management Tool 23

Menu bar:

In the menu bar you find administrative functions of the Management Tool.

Additionally the menu bar comprises all edit functions, available via the Edit

menu.

Some of these edit functions are also available via right mouse click from the

Object Tree).

If you use the Management Tool offline, with no direct access to

the FlexFrame environment, the Mode menu is not displayed. The

Management Tool can just be used in Planning Mode.

Object tree:

Here you find an abstract object tree that represents a FlexFrame installation.

When you select an object tree element in this area with a left mouse click

you get a differentiated view on this in the view area .

This means, the selected object in the object tree determines the content of

the view area. In other words, every object has an object view that is

displayed in the view area.

Generally every object displays in its object view the information that is

displayed within the leaf objects of its sub-tree. If you select a leaf object only

the properties of the selected object are displayed in the view area.

Depending on the selected object you can open a context menu with a right

mouse click on the object. Via context menus you can perform object

dependent actions. Generally the actions are "delete" and "add".

View area:

If you are working in Planning Mode, the View area will be

displayed throughout the whole screen left. In Administration

Mode however, this area is split in an upper part, displaying the

View area und a lower part, displaying the Execution area (see

no. below).

Depending on the selected object in the object tree, an object view is opened

in this area. Generally an object view displays information of the sub-tree of

the selected object.

Objects and object views are loosely coupled. The available views are

described in section 8.1 General Features on page 77.

In all views you will find editable fields or dropdown combo boxes, where you

can change the values of the related properties.


24 Management Tool

If applicable, there are buttons above a table for performing actions. Each

action either produces a new object-dependent sub-tree in the object tree

(add) or deletes an object (delete).

When you select the FlexFrame object, the root object of the FlexFrame

object tree, you get information on the whole FlexFrame installation in the

FlexFrame object view. To group this information, the FlexFrame object view

contains an additional tab bar.

Depending on the selected tab in this bar, you get a global view on the

configuration, grouped by the kind of FlexFrame object, e.g. application

nodes, volumes or NAS devices.

For defining a basic FlexFrame configuration most of the settings are set in

these tabs.

For defining details of a configuration, which are not visible or

changeable in the global views, you have to select the

corresponding object in the object tree – mostly leaf objects - and

set the properties right at the objects itself.

Execution area:

If you are working in Planning Mode, the View area will be

displayed throughout the whole screen left. In Administration

Mode however, this area is split in an upper part, displaying the

View area (see no. ) and a lower part, displaying the Execution

area.

The execution area comprises a command line and four administrative

buttons.

Every configuration that is set, results in one to several commands, which are

displayed in the command line. Several commands can be listed

consecutively.

Executing the listed commands with Execute will affect the real FlexFrame

environment in real time.

Prior to the execution each command is validated. If the command is not

valid, the Execute button is highlighted in red; the action cannot be

performed.

After executing a command the current status of the performed steps is

displayed.

Prior to the execution it is recommended to reload the LDAP configuration by Reload LDAP, because the same FlexFrame environment can be

administered at the same time by two or more people, which may affect the

system configuration.


Management Tool 25

The configuration is not reloaded automatically! Changes

performed by another administrator are not visible unless you

click on Reload LDAP. Otherwise this could result in severe

errors, when executing the own commands.

4.6 Error Logging

ManagementToolLog.txt

In case of unexpected behavior of the Management Tool, information of the available

ff_hardware.xml and other files parsed and in case of an error more detailed

information on the error is logged in the file ManagementToolLog.txt. The file

ManagementToolLog.txt is located in the directory from where the Management Tool

was started.

In case the ff_config.xml or the LDAP content of a FlexFrame installation to be

evaluated contains hardware which is not available in the ff_hardware.xml this

information can be found only here in ManagementToolLog.txt.

If a "java call stack" is logged, this means that a not yet handled error situation occurred.

In such a case it is strongly recommended to save the configuration, terminate the

Management Tool and call the Fujitsu service.

For all Management Tool sessions the information is accumulated in this log file.

Management Tool 27

5 Brief Instruction for Creating a New FlexFrame Configuration

This chapter applies only in case that you use the Planning Mode.

For the Administration Mode, you can skip this chapter.

To create a new FlexFrame configuration, perform the following steps:

1. After starting the Management Tool (see section 4.3 Starting the Management Tool

on page 20), select New Configuration in the File menu (see section 6.1.1

Creating a New Configuration on page 31).

A dialog box opens in which you have to specify the parameters for the first pool of

the new FlexFrame environment. The input fields of this dialog box contain default

values, which you can adapt according to your needs. Having done this, the new

configuration consists of one switch group, one pool with one group and one NAS

storage.

2. Add switches to the switch group (see section 10.17 Adding Switches on page 160).

3. Add one or more blade server chassis (see section 10.7 Adding Blade Server

Chassis on page 125).

4. Add one or more Hypervisor Nodes (see section 10.3 10.3 Adding Hypervisor Nodes

on page 119).

5. Add one or more application nodes (rack servers, blade servers, VMs, see section

10.5 Adding Application Nodes on page 121)

6. Add SAP services (see section 10.16 Adding SAP Services on page 142).

7. Generate the IP addresses (see section 6.3.5 Generating Host Parts of IP Addresses

on page 53).

8. Generate the network wiring plan (see section 6.3.3 Generating a Network Wiring

Plan on page 49).

9. Validate the configuration (see section 6.3.1 Validating a Configuration on page 47).

In case of errors you have to correct them and validate the configuration again.

10. Save the valid configuration (see section 6.1.3 Saving a Configuration on page 40).

If you want to use the configuration for later installation, the file name must be ff_config.xml.

11. You can print the settings of the configuration (see section 6.1.3 Saving a

Configuration on page 40).

Brief Instruction for Creating a New FlexFrame Configuration

28 Management Tool

12. Optional activities:

● Add other switch groups to the desired configuration (see section 10.18 Adding

Switch Groups on page 161).

● Add other pools to the desired configuration (see section 10.15 Adding Pools

on page 140).

● Add other groups to the existing pool(s) (see section 10.14 Adding Pool

GroupsFehler! Verweisquelle konnte nicht gefunden werden. on page 139).

● Add pool-specific external connectivities (see section 10.9 Adding External

Connectivities (Pool-specific) on page 126).

● Add other NAS storages (see section 10.12 Adding NAS Systems on page

129).

● Add volumes to the NAS storage(s) (see section 10.21 Adding Volumes on

page 164).

● Add volume groups and LUNs if you want to use SAN storage for the

databases of some SAP Systems (see sections 10.22 Adding Volume Groups

on page 165 and 10.23 Adding LUNs on page 166).

● Add mount points for the added volumes (see section 10.11 Adding Mount

Points for Volumes on page 128).

● Add global connectivities either manually or automatically with optional

additional Client LANs (see section 6.3.4 Generating Global Connectivity on

page 50).

Optional activities make it necessary that you perform steps 7 to 10 again.

Brief Instruction for Creating a New FlexFrame Configuration

Management Tool 29

The validation of a complete FlexFrame configuration is done by using the

Validate Configuration function (see section 6.3.1 Validating a Configuration on

page 47).

First add all your devices to the configuration then configure all IP addresses

and then do the wiring of the whole configuration. Name conflicts and conflicting

IP addresses are much better resolved when having the global view on all

devices of a FlexFrame configuration.

Before writing a FlexFrame configuration into a configuration file (Save for

Installation) the validation is always performed automatically and the

resulting number of errors will be written into the configuration file. If there are

validation errors you will not be able to use the configuration file for installing a

FlexFrame system.

Therefore it is necessary to use the Validate Configuration function at the

end of a FlexFrame configuration setup. It is also recommended to validate a

configuration several times before.

Of course you can save an intermediate state with existing errors. But to use the configuration file for installation purposes (Save For Installation in the

File menu), it must be bug-free.

Management Tool 31

6 Menu Functions

6.1 "File" Menu

The File menu is different comparing both operating modes:

Planning Mode Administration Mode

Functions available for creating, opening,

and saving a configuration. You can even

print the configuration settings.

There is no need to create a new

configuration or open an existing

configuration file, because the

Management Tool has a direct access to

the FlexFrame environment. The functions

additionally available in Planning Mode are

therefore irrelevant for the Administration

Mode.

6.1.1 Creating a New Configuration

Creating a new configuration is only possible in Planning Mode.

A new configuration can be created in the following three ways:

● Select New Configuration from the File menu, see section 6.1.1.1 "New

Configuration" Function on page 32.

● Open an existing configuration from LDAP via the File menu and save it as an XML

file, see sections 6.1.1.2 "Open LDAP Connection" Function on page 36 and 6.1.1.3

"Open Local LDAP Connection" Function on page 38.

● Open an existing configuration via the File menu, modify and save it under a

different name, see section 6.1.1.4 "Open Configuration File" Function on page 38.

Menu Functions "File" Menu

32 Management Tool

6.1.1.1 "New Configuration" Function

With this function you can create the basic objects for an initial configuration.

The following dialog box is displayed in which you have to specify the parameters for the first pool of the new FlexFrame environment. The input fields of this dialog box contain default values, which you can adapt according to your needs.

"File" Menu Menu Functions

Management Tool 33

Control Node Type Pull down menu with valid Control Node types, either

the hardware model for a physical or the type KVMVM

for a virtual Control Node (vCN).1

1 The Control Node type KVMVM starts a virtual Control Center (vCC) configuration and additonally affords the configuration of two Hypervisor nodes of type KVM. Further information to a virtual Control Center is given in the FlexFrame Administration &_Operation Manual.


34 Management Tool

First Pool Name The name of the first pool.

The name must start with a letter and may only contain

numbers and letters.

NOTE: It's recommended to use short pool names,

because the Pool Name is used as part of the host

name. Long Pool Names make the host name illegible.

First Group Name The name of the first pool group.


numbers, letters, "-" and "_".

First Switch Group Name The name of the first switch group.


numbers, letters or "-".

DNS Domain Name The DNS domain name for the first pool.

The name has to conform to RFC1035. This means, the

domain parts have to be separated by a dot and must

consist of alphanumerical characters and dashes. The

parts may not begin with a number or a dash.

DNS Server IPv4 address of the DNS Domain Server for the first

pool. The name has to conform to RFC1035 (see

above). No entry is required for this field. If this field is

empty, fully qualified domain names outside of

FlexFrame cannot be resolved by neither the Control

Nodes nor the Application Nodes.

Network (LANs) The relevant network in IPv4 format. In binary, the

network address must contain a zero at the same

position as the netmask of the individual LAN segments.

The individual networks must be different from each

other.

Netmask (LANs) The relevant netmask in IPv4 format. In the network

section the netmask must consist of binary ones, and in

the host section of binary zeros. You are recommended

to use the same netmask for all network segments.

VLAN ID (LANs) The relevant VLAN ID. The VLAN ID is an integer

between 2 and 4094. The VLAN IDs must be unique

over all LAN segments.

Depending on the actual switching hardware (switch

blades or switchgroup switches) further restrictions may

apply.

Details you will find in the "HW Characteristics

Quickguides" of these devices.


Management Tool 35

NAS System NAS system relevant properties, the choice of editable

properties depends on the NAS System Type.

Refer also to the section 3.3 NAS Storage on page 10.

Type Pull down menu with valid NAS types.

Name Name of the NAS System

For NAS names only lower case letters should be used

because upper case letters will result in serious

problems when applying administration commands

later.

Use Pull down menu with the values ONTAP (for ONTAP 7-

mode) and cDOT (for clustered DATA ONTAP) or

another possible operating mode (see the section 3.3

NAS Storage on page 10).

For details about the cDOT mode see section 10.12.1

Configuring a cDOT cluster in planning mode on page

133.

10 GB Data NICs Pull down menu indicating the used NIC’s ethernet data

rate.

Number of NICs Number of used Network Interface Cards (2-6).

After you have completed your input or for the assumption of the default values, click on the OK button. The structured object list for this configuration will be displayed in the

object tree.


36 Management Tool

6.1.1.2 "Open LDAP Connection" Function

The function "Open LDAP Connection" is only available in Planning Mode.

With this function you can create a new configuration by reading in an existing

configuration from LDAP and saving it in an XML file.

In Administration Mode, you can read the existing configuration from LDAP via

the function "Reload from LDAP", available in the Execution Area.

Configuration data for an initial configuration is not all stored in LDAP. There is a

very little amount of information missing. The missing data must be added after

reading in a configuration from LDAP.

Before adding the missing data, a validation of the current configuration will

always show errors (see section 6.3.1 Validating a Configuration on page 47).

Even when the missing data has been added and no validation errors are

indicated anymore, you should be aware, that the data read from the LDAP

might be erroneous due to improper handling before. Data obtained by reading

from LDAP should always be carefully verified. The Management Tool can only

verify consistency. It cannot detect changed IP addresses or similar

modifications.

The following dialog box opens in which you can select a properties file.


Management Tool 37

To open an LDAP connection, click on the corresponding file and then click on the Open

button. The structured object list for this configuration will be displayed.

To modify the properties of the selected file, click on the Edit LDAP Properties button.

The following dialog box opens:

Click on Save to save the modified properties.

By clicking on the Set LDAP Properties button the same dialog box is

displayed with blank input fields.


38 Management Tool

LDAP URL Address of the server for LDAP access.

Base DN The Base DN (Distinguished Name) is the root for the

LDAP name space for this FlexFrame environment.

This can be a subset of a higher LDAP hierarchy. This

field may be empty if the DNS domain name is

specified. If a DNS domain is set and no Base DN

exists, it is formed from the DNS domain when the

Control Nodes are installed. The entry is not checked

for plausibility!

User DN User DN of the LDAP user.

Password Password of the LDAP user.

6.1.1.3 "Open Local LDAP Connection" Function

The function "Open Local LDAP Connection" is only available in Planning Mode

and if the Management Tool is executed on a cluster node.

With this function you can create a new configuration by reading in an existing

configuration from LDAP and saving it in an XML file. As the configuration is read from

the local FlexFrame LDAP here it is not necessary to select an LDAP properties file.

6.1.1.4 "Open Configuration File" Function

With this function you can create a new configuration by modifying an existing

configuration file and saving it under a new name. For further details see the following

section 6.1.2 Modifying an Existing Configuration on page 39.


Management Tool 39

The following dialog box is displayed in which you can select a configuration (XML file).

To open a configuration file, click on the corresponding XML file and then click on the

Open button. The structured object list for this configuration will be displayed.

6.1.2 Modifying an Existing Configuration

To modify an existing configuration, use the Open Configuration File function,

modify the parameters and save it under the same name.


40 Management Tool

6.1.3 Saving a Configuration

You save a configuration by selecting the Save function.

The following dialog box is displayed in which you can save the new/modified

configuration in an XML file.

To save a new configuration, type <file_name>.xml in the File Name field and click

on the Save button.

To save a modified configuration, click on the corresponding XML file and then click on

the Save button.

The configuration file should be copied under the name ff_config.xml to the root

directory of a USB stick. This external medium will be used for the installation.

Within the Management Tool the file name is arbitrary. For the installation the file name must be ff_config.xml.


Management Tool 41

6.1.4 Saving for Installation

You save a configuration for an installation by selecting the Save For Installation

function. Save For Installation is nothing but a combined validation and saving

into the file ff_config.xml.

The following dialog box is displayed in which you can save the new/modified

configuration for an installation in an XML file.

The file name ff_config.xml preset for this name is necessary for installation.

Before saving for installation a validation of the data is performed.

The "Save configuration" dialog box only opens if no error is found.

Warnings are tolerated.

Menu Functions "Edit" Menu

42 Management Tool

6.1.5 Printing a Configuration

You can print the current settings of the selected configuration by selecting the Print

function. The views of all tabs or the wiring plan are printed.

6.2 "Edit" Menu

Not all functions are available in both operating modes. A detailed overview of the

differences is provided in section 4.2 Operating Mode Differences on page 17.


"Edit" Menu Menu Functions

Management Tool 43

6.2.1 "Add" / "Delete"

With the functions Add and Delete in the Edit menu you can execute the same

actions, which are offered as buttons in different views. For more information see chapter

8 View Area on page 77.


6.2.2 "Undo" / "Redo"

The functions "Undo" and "Redo" are only available in Planning Mode.

With the Undo function you can undo the actions that are stored in the undo buffer. With

Redo you can perform undone actions again.


44 Management Tool

6.2.3 "Update Views"

With the Update Views function you can refresh the displayed view. Especially if you

changed the sorting of the columns, the sorting is reinitialized.


"Edit" Menu Menu Functions

Management Tool 45

6.2.4 "Options/Preferences"

With the function Options/Preferences in the Edit menu you can select options

which are to be appended to each executed administration command.


By clicking this function the following dialog box is opened. You can select the options

required by activating the corresponding checkboxes.

The selected options debug, verbose and/or dryrun are appended to the

administration commands. The meaning and effect of these options is described in the

"FlexFrame® – Administration and Operation" manual.


46 Management Tool

On the General tab you can change the views of objects with properties and more

objects in a sub-tree. If you activate the checkbox in the view of those objects only the

property list is shown and the output of the corresponding table is suppressed.

"Tools" Menu Menu Functions

Management Tool 47

6.3 "Tools" Menu

In the Tools menu you can:

● check whether the current configuration is valid,

● generate a network wiring plan,

● plan a device independent global connectivity,

● generate the host part of the IP addresses of the Client LAN, Server LAN and

Storage LAN,

● reload the FlexFrame environment settings (only in Administration Mode).

6.3.1 Validating a Configuration

With the Validate Configuration function yon can check whether the current

configuration is valid and may be used by the installation script.

By clicking this function the following message box displays the check results. By default, errors and warnings are displayed. You can reduce the output by activating the Show

only errors checkbox.

The Validate Configuration function additionally displays the errors coming up

while reading the LDAP or XML configuration.

Menu Functions "Tools" Menu

48 Management Tool

The validation of the data input is done by using the Validate

Configuration function. It is recommended to use the Validate

Configuration function also while entering data to check and correct it, not

only at the end of the complete configuration.

This dialog box is non-modal, i.e. it can be left open while you correct the

configuration in the main window.

6.3.2 Erasing the LDAP and XML Validation Errors

With this function you can delete the errors coming up while reading the LDAP or XML configuration from the list created by the Validate Configuration function.

To delete the error list, select Erase LDAP / XML Read Validation. The error list is

deleted; no dialog is displayed.


Management Tool 49

6.3.3 Generating a Network Wiring Plan

You can generate a network wiring plan automatically or manually. The automatic

generation is recommended because it is the most comfortable and safest method to

generate a correct network wiring plan.

After the network wiring plan is generated, it is displayed under the Wiring tab in the

FlexFrame object view (see page 103).

6.3.3.1 Automatic Generation

You generate a network wiring plan automatically with the Perform Wiring function.

Before you generate a network wiring plan with the Perform Wiring function, you

must delete an existing network wiring plan with the Clear Wiring function. Only if

the existing wiring is manually preconfigured and supposed to remain, you may

call Perform Wiring without first resetting it.

All open NICs will be connected automatically to the related switch ports. The icons of the

connected NICs and switch ports are marked green in the object tree (for an example see

the figure in the following section).

If there is more than one switch group these switch groups will be connected to ports of

an abstract network cloud called "Core or Direct". This "Core or Direct" cloud stands for

networking in the responsibility of FlexFrame customer networking environment, not

anymore in the responsibility of FlexFrame. For a device connected to "Core or Direct"

FlexFrame will not configure any ports at FlexFrame switches.

In FlexFrame as of version 5.2 switch ports of different switch groups can be connected

directly. Therefore you have to set the “portUse” property of the SWP “Swp connect”.

This method is recommended in the current version of FlexFrame.

6.3.3.2 Manual Generation

To modify a network wiring plan manually, navigate to a switch pot or a NIC object in the

object tree and select a value from the pull-down menu (see the example below). If the

switch port or NIC is connected, its icon is marked green in the object tree.


50 Management Tool

Modification of a network wiring plan manually is only available in Planning

Mode.

The portUse parameter can have the following values:

Nic connect link is wired to a NIC. The icon is marked green.

Swp connect link is wired to another SWP. The icon is marked

green.

Member connect Port is reserved for connecting members of a switch group; the details of the wiring are part of the documentation of the switches, wiring is in the responsibility of the user. The icon is marked purple.

GW Port is used as a gateway. A list of the corresponding VLANs can be entered in the

portVLans parameter. The icon is marked red.

6.3.4 Generating Global Connectivity

With the Management Tool device independent global connectivity can be planned. It

leads to configuration of abstract external connectivity usually in form of switch ports that

provide access to certain Client LANs.

For a device specific external connectivity see section 8.11 "External Connectivity" on

page 98.

The global connectivity is responsible for the global network connections which connect

the internal FlexFrame network with the "outside world" (e.g. corporate network).

After the global connectivity is generated, it is displayed in the object tree (see page 71) and under the Wiring tab in the FlexFrame object view (see section 8.14 "Wiring" on

page 103).


Management Tool 51

6.3.4.1 Automatic Generation

You generate the global connectivity automatically with the Perform Wiring function.

Before you generate the global connectivity with the Perform Wiring function,

you must delete an existing connectivity with the function Clear Client LAN

Connectivity.

With the automatic generation a standard wiring will be generated according to the

following settings in the Network object (see also section 7.4"Network" Object on page

59):

Client LANs on SWG ports = true

One Client VLAN per SWP = false

One common connection with two NICs for all existing pools

Client LANs on SWG ports = true

One Client VLAN per SWP = true

One separate connection with two NICs for each existing pool

Though global connectivity configures only switch ports, NICs are getting involved be-

cause abstract global connectivity objects with NICs are configured in the object tree –

just to visualize with Management Tool means, what the switch ports are used for.

These abstract global connectivity objects you can imagine as abstract as the further

above mentioned "Core or Direct" networking cloud which stands for networking infra-

structure only in the responsibility of the FlexFrame customer. Here also the switch ports

of the FlexFrame switches are configured by FlexFrame, the abstract global connectivity

is completely in the responsibility of the FlexFrame customer.


52 Management Tool

6.3.4.2 Manual Generation

Generating the global connectivity manually is only available in Planning Mode.

To generate the global connectivity manually, perform the following steps:

1. If the entry Global Connectivity

is not available in the object

tree, create it:

2. Add a Client LAN Connection

entry:

3. Under ClLanCons add (at

least) one Client LAN entry:

A dialog box is opened, in

which you must link the

Client LAN to the desired

pool.

If the desired pool does not exist yet, you can link the Client LAN later after you

have created the pool:


Management Tool 53

4. To connect the NICs to the related switch ports, execute the Perform Wiring

function (without executing Clear Client LAN Connectivity before), or set the

connection manually (see below):

6.3.5 Generating Host Parts of IP Addresses

You can generate the host part of the IP addresses of the Client LAN, Server LAN and

Storage LAN automatically or manually. The automatic generation is a comfortable and

safe method to generate IP addresses. The addresses must be unique within a

FlexFrame environment.

An IPv4 address consists of a network section and a host section. In the network

section the netmask consists of binary ones and in the host section of binary

zeros. Example (the host part of the IP address is underlined):

netmask: 255.255.255.0 Host IP: 192.168.100.234

netmask: 255.255.0.0 Host IP: 192.168.100.234

Menu Functions "Mode" Menu

54 Management Tool

6.3.5.1 Generate Host Parts Automatically

To generate the host parts automatically, first you have to reset them to a default value

with the Reset All function. Then you can generate them with the Set All function.

6.3.5.2 Generate Host Parts Manually

You can generate the host parts manually in the view area, by entering the values into

the white highlighted fields of the corresponding columns or when setting the host

property of a selected IP interface object.

6.4 "Mode" Menu

Select the operating mode in the "Mode" menu. Details concerning the two operating

modes are described in section 4.2 Operating Mode Differences on page 17.

If you use the Management Tool offline, with no connection available to the real

FlexFrame environment, the Mode menu is not displayed. The Management Tool

can just be used in Planning Mode.

Management Tool 55

7 Object Tree

The object tree is an abstraction of the FlexFrame reality.

7.1 General Features

Depending on the selected object in the object tree you get a differentiated view on this

object or on the sub-tree of this object in the view area. This means, the selected object

determines the content of the view area and the more deeply you are in the structure the

more differentiated is the display of the parameters.

Every object in the object tree has its object view in the view area.

When you select a leaf Object in the object tree, the object view is an editable view on all

properties of this object. Then you can modify certain settings of this object. When you

select another object in the object tree you get - depending on the object - an editable

view of properties of all objects in the sub-tree.

Depending on the object in the object tree you can open a context menu by doing a right

mouse click on the object. Via context menus you can perform object dependent actions.

Each action modifies / produces an object-dependent sub-tree in this area.

In section 10.1 Actions Overview on page 113 you find an overview of all

actions.

With the Delete action you can delete all objects in the object tree.

This action is carried out directly, no safety inquiry will take place!

If you delete an object by mistake, you can repair it:

● perform the Undo function in the Edit menu (only in Planning mode and as

long as the action is stored in the undo buffer) or

● add it again in the object immediately above or

● read in the configuration file again with the

Open -> Configuration File function.

In the latter case, all input that you made previously is lost (if you did not

accomplish a backup in the meantime).

The object tree consists of the major object FlexFrame and seven basic objects

described in the following sections 7.2 to 7.8.1.

Object Tree "FlexFrame" Object

56 Management Tool

7.2 "FlexFrame" Object

If you select FlexFrame in the object view, the view area is a tabbed pane, with the

single tabs containing tables, that resemble the tabs and the tables of the old Excel

based Planning Tool.

The FlexFrame object view is the most global view. Selecting a tab you select global

information on a certain kind of FlexFrame objects, e.g. all application nodes, all NAS

systems or all SAP services.

The Execution area is only displayed if you are working in Administration Mode;

Administration option in the Menu bar.

The display of the view area is not affected and remains the same for Planning

Mode and Administration Mode.

"Control Center" Object Object Tree

Management Tool 57

7.3 "Control Center" Object

The Control Center consists of two clustered servers (Control Nodes) whose task is to

monitor and manage FlexFrame (e.g.: Storage, ANs, SIDs), i.e. to supply them with

information on the boot procedure, directory services (LDAP for hosts, services, etc.) and

more (FlexFrame Control Agents).

The figure on the left side shows the Control

Center object as an example.

By selecting this object, the Control Center view is

displayed. It consists of the following tabs:

Properties, Controlling and Networks (see

section 8.4 "Networks" on page 82).

The Properties tab shows a list of properties

necessary for the Control Center (see

Miscellaneous Control Center settings below).

The Controlling tab shows the Control Node

part of the Controlling table a table where

more properties of the Control Center are shown in

a similar way as properties of NAS systems or

Application Nodes (see section 8.5 "Controlling" on

page 83).

If a NIC is already connected to a switch port, the

icon of the NIC is marked green. The relation then

also appears in the wiring view.

Miscellaneous Control Center Settings Control Node DNS Domain DNS domain name of the Control Nodes. The name

has to exist already in the customer’s network (e.g. myFlexFrame.ts.fujitsu.com).

The DNS domain name is required and has to

conform to RFC1035. This means, the domain parts

have to be separated by a dot and have to consist of

alphanumerical characters and dashes. Domain

parts may not begin with a number or a dash.

Object Tree "Control Center" Object

58 Management Tool

DNS Servers IPv4 addresses for DNS Domain Server (separated

by blanks). No entry is required for this field. If this

field is empty, fully qualified domain names outside

of FlexFrame cannot be resolved by neither the

Control Nodes nor the Application Nodes.

LDAP Base DN The LDAP Base Distinguished Name is the root for

the LDAP name space for this FlexFrame environment (e.g. DC=myFlexFrame,

DC=fujitsu, DC=com). This can be a subset of a

higher LDAP hierarchy. This field may be empty if

the DNS Domain Name is specified. If a DNS

Domain is set and no LDAP Base DN exists, it is

formed from the DNS Domain when the Control

Nodes are installed.

NTP Time Servers One or more Network Time Protocol Servers (IPv4

addresses separated by blanks). No entry is required

in this field. If this field is left empty, the first Control

Node becomes the NTP master server and the

second Control Node will be a backup NTP server.

Time Zone Time zone of the FlexFrame environment to be

installed.

Default Router Default router for the Control Nodes (IPv4 address).

This router does not apply for the Application Nodes.

The router must be in one of the Client, Server or

Storage LAN segments. No entry is required in this

field.

LDAP Root User Root user (default: root).

LDAP Root Password Root password (default: password).

SNMP RO Community Name SNMP read only community name (default: public).

For more information see section 2.3 Define SNMP

Communities on page 6.

"Network" Object Object Tree

Management Tool 59

7.4 "Network" Object

In this object the network infrastructure of the entire FlexFrame environment which is

used to implement redundant connection of all the FlexFrame components using

integrated switches is managed.

The figure on the left side shows the Network object

as an example.

If a switch port is already connected to a NIC (PortUse = Nic connect) or another switch port

(Portuse = Swp connect), the icon of the switch

port is marked green. The relation then also appears

in the wiring view.

If a switch port is reserved for manual wiring

(PortUse = Member connect) the icon is marked

purple. Member connects are used to connect

members of a SWG.

If a switch port is used as a gateway (PortUse =

GW) the icon is marked red. VLANs can be configured

on the Swp object directly.

You will find details on the usage of the PortUse

parameter in section 6.3.3.2 Manual Generation (of a

Network Wiring Plan) on page 49.

By selecting the Network object, the switch group

part of the Controlling view is displayed in the

lower part of the split pane (see section 8.5

"Controlling" on page 83).

The upper part of the split pane shows

miscellaneous settings concerning the network (see

Miscellaneous Network settings below).

Right-click on Switches to add switches, see

section 10.17 Adding Switches on page 160.

For every Switch Group a tree view is available

displaying the Path, Name and Value for the

corresponding switch group.

Object Tree "Network" Object

60 Management Tool

Miscellaneous Network Settings

Client LANs on SWG ports true

Client LAN switch ports are configured on the

FlexFrame switches.

false

Client LAN switch ports are configured on core

switches.

One Client LAN per SWP2 true

For each Client LAN there is a pair of switch

ports with the untagged LAN.

false

For all Client LANs there is only one pair of

switch ports with the tagged LANs.

Client LANs on several SWGs3 true

The pair of Client LAN switch ports is

configured on the first two switch groups, one

port on the first switch group and the other port

on the second switch group.

false

The pair of Client LAN switch ports is

configured on the first switch group only.

Use 1GBit SWPs as uplinks true

1Gbit switch ports (the standard twisted pair

1GBit ports) are used for uplinks

false

Either SFP switch ports or 10GBit switch ports

are used for uplinks.

Use 1GBit SWPs for Client LANs4 true

1Gbit switch ports (the standard twisted pair

1GBit ports) are used for configured Client

LANs

false

Either SFP switch ports or 10GBit switch ports

are used for Client LANs.

Number of ports for uplinks Number of uplink ports (2 - 8).

2 corresponds to former „Separate VLANs to corporate LAN“

3 corresponds to former „Distribute corporate LAN ports to different switch groups”

4 corresponds to former “Use Fiber Optic port to corporate LAN“

"Network" Object Object Tree

Management Tool 61

Switch Group Tree View

A switch group is typically used as a network unit for the redundant connection of the

hosts for each system cabinet (19" rack). This is intended to reduce the cabling outside

the system cabinet to a minimum.

The switches within a group are connected in such a way that the hosts are connected

with redundancy. The first two switches of a group are connected redundantly with the

neighboring switch groups across switch group boundaries. Connecting switch groups to

each other is in the responsibility of the customer. FlexFrame only provides uplink ports

at the switch groups. For information about adding, deleting or extending uplinks, see

section 10.19 Uplinks on page 162.

Object Tree "Storage" Object

62 Management Tool

7.5 "Storage" Object

In this object the central storage systems of the entire FlexFrame environment which can

be accessed by all Application Nodes are managed. Operating systems (shared OSs)

and application software are also stored centrally. Only the operating systems of the two

servers of the Control Center are stored on their local disks and not in the NAS storage.

The database datafiles and logfiles of the SAP systems can be stored on NAS storage or

on SAN storage.

The Storage object consists of two subtrees: NAS and SAN.

7.5.1 NAS Storage

The figure on the left side shows the NAS subtree of the

Storage object as an example.

If a NIC is already connected to a switch port, the icon of

the NIC is marked green. The relation then also appears

in the wiring view.

By selecting this object, the NAS Storage table is

displayed (see section 8.7 "NAS Storage" on page 89).

The NAS Storage table view is also displayed as object

view for the Storage – NAS object.

For every NAS a tree view is available displaying the

Path, Name and Value for the corresponding NAS.

The figure below shows the Volumes object as an example. In Planning Mode three

standard volumes volFF, sapdata, saplog are preconfigured with their default names,

which as of FlexFrame 5.2 may be modified as required.

"Storage" Object Object Tree

Management Tool 63

7.5.2 SAN Storage

The figure on the left side shows the SAN subtree of

the Storage object as an example.

By selecting the Volume groups or the LUNs

object, the Volume groups / LUNs table is

displayed (see section 8.8.2 "Volume groups / LUNs"

on page 92).

With a right mouse click on the Volume groups or

the LUNs object, you can add Volume groups or

LUNs (see sections 10.22 Adding Volume Groups on

page 165 and 10.23 Adding LUNs on page 166).

The storage system (here dx200) is used to collect

LUNs with the same storage system name in the

object tree. It is added automatically with the first

LUN of the respective storage system.

If the SAN subtree does not yet exist you can

add it manually with a right mouse click on

the Storage object and selecting the

function as shown in the figure on the right.

If not already present, you can add the

Volume groups and LUNs objects by a right

mouse click on the SAN object and selecting

the required object.

Object Tree "Pools" Object

64 Management Tool

7.6 "Pools" Object

In this object the features of a pool within a FlexFrame environment are managed.

Depending on the chosen object an appropriate view is opened.

Pools are of central importance and have to be defined first.

A pool contains multiple systems and is separated and protected from other pools by

different network addresses and access controls (multi-client capability). All systems in a

pool belong to exactly one client. This is, for example, the client of a service provider who

has a number of systems made available to him to use exclusively.

Each pool contains one or more pool groups. A pool group is an additional grouping level

within a pool. All Application Nodes with common characteristics may be included in the

same pool group, e.g. servers with the same operating systems or performance classes.

In case of a failure the Application Nodes can replace themselves mutually (a SAP

instance is then started on another Application Node of the group). For each new pool

one pool group is automatically created.

The figures below show the individual sub-objects of the Pools object as examples.

By selecting the Pools object, the pool volume defaults are

displayed in the upper part of the split pane and in the lower part the Pools table is displayed (see section 8.3 "Pools"

on page 80).

Pool volume defaults:

“Common volFF” refers to the volume playing the volFF

role. The default volumes are defaults for the poolspecific

volumes.

"Pools" Object Object Tree

Management Tool 65

In Administration mode for every single pool a tree view

displays the hierarchy structure of the pool and the

individual objects (Path), together with the properties Name

and Value:

In Planning mode for every single pool a view consisting of the following tabs is displayed: Properties, Networks

(see section 8.4 "Networks" on page 82), Application

Nodes (see section 8.6 "Application Nodes" on page 86)and

SAP Services (see section 8.9 "SAP Services" on page

94).


66 Management Tool

With a right mouse click on the pool object, you can add

optional LANS in the scope of this pool such as a Backup

LAN, a Hanaint LAN etc. (see sections 10.22 Adding

Volume Groups on page 165 and 10.23 Adding LUNs on

page 166).

By selecting the External Connectivity object the

pool-specific External Connectivity table is displayed

(see section 8.11 "External Connectivity" on page 98).

If a NIC is already connected to a switch port, the icon of

the NIC is marked green. The relation then also appears in

the wiring view.


Management Tool 67

By selecting the SIDs object the SIDs object view is

displayed (see section 8.9 "SAP Services" on page

94) which show the SID table with SAP services

belonging to this pool.


68 Management Tool

By selecting the Users Groups Services object a

view is displayed where you can manage the pool-

specific UIDs and GIDs that might be necessary when

installing and running the SAP services in the given

pool. When migrating an existing SAP Installation to

FlexFrame, the existing UIDs and GIDs should be used

here. Empty or double values will result in validation

errors.

Sub-object tree:

Click on the Users, Groups or Services

sub-object and all User names, Group names and

Services are displayed in the object tree.

Concurrently the corresponding view opens and Location, User Name and User ID are listed in a

table, e.g. see section 8.10, "Users Groups Services" on

page 97.

If you click on a specific user, group or service the

properties are displayed in the view area.

During installation default values are set for "empty"

user IDs.


Management Tool 69

By selecting a pool (e.g. pool1) or the Groups object

(and sub-objects below), the object views of these

object is the Application Nodes table that displays

the scope of information defined by the position of the

object in the object tree. For a pool object you have

additionally in the upper part of a split pane of the pool

object view the properties of the pool itself

The Application Node table (see section 8.6

"Application Nodes" on page 86) displays only

application nodes sorted by pool and then by group.

Application nodes are rack servers, VMs or blade

servers. Management blade and switch blades are not

displayed in the Application Node table.

The management blade and the switch blades are managed in the Chassis object (see section 7.8

"Chassis" Object on page 74 ). The Chassis object

view is the Chassis table.


70 Management Tool

With a right mouse click on the application node object,

you can add additional connections for the distribution

of the traffic.

"Hypervisor Nodes" Object Object Tree

Management Tool 71

7.7 "Hypervisor Nodes" Object

Instead of being used directly as Application Nodes, PRIMERGY servers may also be

used in FlexFrame as Hypervisor Nodes. A Hypervisor Nodecan host a number of virtual

machines which are used as Application Nodes.

VMware ESXi and VMware ESX are "bare-metal" hypervisors that form the foundation of

VMware vSphere. The VMware vSphere 4 product line supports three different types of

hypervisors - ESX classic, ESXi installable and ESXi embedded. In FlexFrame, only ESXi

installable and ESXi embedded are supported.

The terms "ESX" and "ESXi" are both used in the FlexFrame documentation and

code to denote the VMware hypervisor and always mean "ESXi" unless explicitly

stated otherwise.

With FlexFrame Orchestrator, SUSE Linux KVM is also supported as an additional

hypervisor type.

When starting a new FlexFrame configuration, the Hypervisor Nodes object is not yet

present in the object tree. It is created only after adding a first Hypervisor Nodes, for

example by using the Add Hypervisor Nodes button of the Hypervisor Nodes table

that can be activated via the Hypervisor Nodes tab of the FlexFrame root object view.

Object Tree "Hypervisor Nodes" Object

72 Management Tool

When selecting the Hypervisor Nodes

object, hypervisor node related global

FlexFrame parameters are displayed in the view

area (see table below) and can be modified

according to the configuration's needs.

When selecting the VCenter subobject, data

related to the usage of a vCenter server in

FlexFrame is displayed in the view area and can

be modified there.

You can add a new hypervisor node via the

Server List object with a right mouse-click. A

dialog box opens and you can add a hypervisor

nodes in exact the same way as you add an

Application node to a Server List object

inside a Group object.

If the hypervisor node is a blade server you have

to relate blade with chassis via the Connector

and Slot object in the same way you relate a

NIC to a SWP of a Switch via Data NIC and

switch port object. When these objects are

connected the connecting objects will be marked

green.

For further information on this topic, see section

7.8 "Chassis" Object on page 74.

For every hypervisor node a tree view is

available displaying the Path, Name and Value

for the corresponding hypervisor nodes.

Hypervisor node related global FlexFrame parameters

FlexFrame Systemcode A numeric value between 0 and 63 used to

generate MAC addresses for FlexFrame virtual

machines and to build names of some

hypervisor related resources such as port

groups/networks and datastores/storage pools.

Use a different system code for each

FlexFrame system in your environment.

"Hypervisor Nodes" Object Object Tree

Management Tool 73

vCenter Server usage

If FlexFrame hypervisor nodes are administrated by a vCenter Server, the name and IP

address of the vCenter Server have to be known to FlexFrame.

To enter this information you have to use VCenter object.

The IP address can be an address in the FlexFrame Control LAN (select Control

Center / Control LAN in the link drop-down box) or an address outside

FlexFrame, which is reachable from the Control Nodes (select --- in the link drop-

down box).

If no vCenter Server is used, remove the VCenter object from the object tree: right-click

on the VCenter object and select Delete.

Object Tree "Chassis" Object

74 Management Tool

7.8 "Chassis" Object

In this object the management blade and the switch blades of all blade servers within a

FlexFrame environment are managed. The Chassis object view is the chassis table.

The Chassis table resembles the Application Node table and has some additional

chassis related information for blade servers (e.g. slot number) and additionally the

infrastructure objects for chassis, like switch blades and management blades. Whereas

the Application Node table sorts objects by pool and by group in the Chassis table

the objects are sorted by chassis and by slot.

The figure on the left side shows the Chassis object as an

example.

With right-click action Add or Delete you can modify the

type of switch blades if you have to modify your initial

choice in the Add Chassis dialog.

The switch blade types include the type Pass-Thru, which

enables dedicated connections to specific server blades

and (only if the customer has an accepted Request for

special Release for this feature) also enables to use part of

the server blades within FlexFrame and part of it outside of

FlexFrame.

The server blades for a blade server must be specified

hereafter as Application Nodes or Hypervisor Nodes with a

Connector – Slot relation to the chassis.

For a server blade that occupies more than one slot, see

the "HW Characteristics Quickguides" to identify the main

slot object and which connector - slot object relations have

to be established to create a valid configuration.

When you add a server blade via the Add AN dialog you

will only have to relate the main connector object with a slot

object. The other connector - slot relations will be

established automatically.

If a NIC is connected to a switch port, the icon of the NIC is

marked green. The relation then also appears in the wiring

view.

If a server blade is connected to a slot, the icon of the slot is

marked green.

For every Chassis a tree view is available displaying the

Path, Name and Value for the corresponding chassis.

"Global Connectivity" Object Object Tree

Management Tool 75

7.8.1 Switch Blades

The view area of a switch blade shows the properties of the switch blade.

Ensure to choose user and password of the switch blade according to the

restrictions in the “User Interface Description” of this switch blade.

7.9 "Global Connectivity" Object

In this object the Client LAN connections (see section 2.2.2.1 Global Connectivity - Client

LAN Connection on page 4) are managed.

For further information regarding the automatic generation of these Client LAN

connections see section 6.3.4 Generating Global Connectivity on page 50.

Manually you can add these Client LAN connections with a right mouse-click on the

"Global Connectivity" object and selecting “Add” in the context menu.

In Administration Mode, the "Global Connectivity" object cannot be added to the

Object Tree.

But if the "Global Connectivity" already exists, it is displayed greyed out

(disabled) in the object tree.

The figure on the left side shows the

Global Connectivity object as an example.

Under the ClLanCons object you can define

global client LANs.

Management Tool 77

8 View Area

8.1 General Features

Depending on the selected object in the object tree, a view is opened in this area. This

view is generally called the object view. Every object has its own object view. For a Pool

object this view is called the pool object view, for the pool list object, Pools, this is called

the pools view.

For the convenience of the user the different kinds of views are very restricted in the

Management Tool.

● Most common are tables, like Chassis table, Application Node table or Pool

table. These tables are used to display the object view of different kinds of objects.

The Object views always use these tables to display information that is related to the

position of the object in the object tree, which means they generally only display

information in the sub-tree of the object (e.g.: the Application Node table in a

pool object view displays only the application nodes in this pool)

● As common as tables are property lists. Property lists are always used to display

the views of leaf objects. In property lists you have just a list of names with input

components (edit or combo boxes) to modify the property values.

Property values are only editable if they are currently added.

Property values of objects to be deleted or property values of already

existing objects cannot be modified.

● Combinations of the first two kinds of displaying an object view are used when you

have an object with properties and more objects in a sub-tree. A table and a property

list are then combined using a split pane. An example for this is a pool object view

for a certain pool. A property list and the Application Node table are combined here

using a split pane. With the function Options/Preferences in the Edit menu you can suppress the

output of the table in such cases. If you activate the checkbox on the General tab

only the properties list will be displayed.

● Another kind of combining the two standard views is a tabbed pane, as it is used in

the FlexFrame object view. Here the tabs are used to select the information to

display. The information behind the tabs groups FlexFrame global information by the

kind of FlexFrame object (e.g.: server, pool, SID).

View Area General Features

78 Management Tool

● Freely styled views are the Wiring view and the General Information view. The

Wiring view displays a text document that is a wiring plan. The Wiring view is always

related to a Wiring object, an abstract object that you can find in several positions of

the object tree, and that will then always display the wiring information of the objects

in the sub-tree.

The General Information view displays information about the current FlexFrame

project, i.e. customer, project name, person, origin of data and the FlexFrame

Identifier. Additionally you can add comments to the General Information view.

● The tree view offers a simple and quick overview of the object hierarchy including

the corresponding properties (name and value).

The tree view corresponds one-to-one to the object tree, but provides essential

information at a glance. For more information see section 7.1 General Features on

page 55.

Since the different kind of views behind the tabs of the FlexFrame object view is a

collection of all kinds of information that can be found in the Management Tool, it will be

used to describe FlexFrame views generally in the following chapter.

"General Information" View Area

Management Tool 79

8.2 "General Information"

Displays general information related to the Management Tool.

Customer Name of the customer

Project Name Name of the customer project

Contact Person Information to the contact person at the customer (e.g. name,

phone number, email address)

Origin of Data Original database of the configuration

Comments Any comments (not stored in the configuration file)

FlexFrame

Identifier

FlexFrame specific code starting with YKRA and followed by a

six-digit number.

(YK means "factory ident" and RA means "product group")

NOTE: A default FlexFrame Identifier may be used

(YKRA000000) in case that the real FlexFrame Identifier is not

available at the time of installation.

View Area "Pools"

80 Management Tool

8.3 "Pools"

The pools table is shown here. All existing pools with their current LAN parameters for the

mandatory (non optional) LANs as well as the DNS information are displayed.

● You can see a pools table also via the Pools object in the object tree (see section

7.6 "Pools" Object on page 64).

Due to the table size the presentation of the Pools table is divided into a left

part (first figure) and a right part (second figure) of the screen.

Pool Name of the pool

Network Network address of the individual LAN

Netmask Netmask of the individual LAN

VLAN VLAN ID of the individual LAN

Default Router Network address of the default router for the client LAN

DNS Domain Name DNS domain name for the pool (alphanumeric, "." and "-" are

allowed)

DNS Server DNS server for the pool (IPv4 format), a list of DNS Servers

separated by spaces is also allowed.

● With the actions Add Pool and Delete Pool you can add or delete pools.

"Pools" View Area

Management Tool 81

● In the fields highlighted in white you can modify the general pool names, the host

part of the IP addresses, the netmasks and the VLAN IDs of the different LANs as

well as the DNS domain name and the DNS server by direct input.

Failover concept for Application Nodes related to FlexFrame Agents:

If a node in a pool group fails and no adequate spare node is found in the group of the

failed node, the FlexFrame Agent can search a spare node in the special pool

adminpool. This pool has a SPARE group, which provides global spare nodes for all

pools of a FlexFrame landscape. The adminpool must not serve as a normal production

pool.

View Area "Networks"

82 Management Tool

8.4 "Networks"

In the Networks table all existing Networks/LANs are displayed with their current

parameters.

● You can display this table also via the Control Center object (see section 7.3

"Control Center" Object on page 57).

Pool Name of the pool if the LAN is in the scope of a pool,

“-“ if the LAN exists in FlexFrame scope (global scope)

LAN Name Type of the individual LAN

Suffix Suffix

Network Network address of the individual LAN

Netmask Netmask of the individual LAN

Vlan VLAN ID

Router Network address of the router for the client LAN

● With the actions Add Network and Delete Network you can add or delete

Networks, see section 10.13 Adding Networks on page 138 .

● In the fields highlighted in white you can modify the entries by direct input.

"Controlling" View Area

Management Tool 83

These changes are only available in Planning Mode.

8.5 "Controlling"

The controlling table is displayed. In this table the switch groups, the Control Nodes and

associated pools are displayed with their current LAN parameters.

● You can open a Controlling table also via the Control Center object concerning

the Control Node entries (see section 7.3 "Control Center" Object on page 57) and

via the Network object concerning the switch group entries (see section 7.4

"Network" Object on page 59) in the object tree.

If you open this view via the Control Center object, an additional area is

displayed above the table. Here you can enter miscellaneous settings

concerning the Control Center.

Due to the table size the presentation of the Controlling table is divided into

a left part (first figure) and a right part (second figure) of the screen.

View Area "Controlling"

84 Management Tool

When opening an FFO 1.0 config file the Management Tool inserts Control

Node Type "RX2540M1" no matter what type the current hardware has. If the

real model is e.g. RX300S8, there is no need to change the default type.

Host Name Name of the component

Type Type of the component

Swg / HN Associated switch group for CNs of SWGs

or

Associated hypervisor node for VMs

CN Role Role of CN

Host Common host part of all VLAN segments for the component in

the relevant row

Location [Pool] Associated pool

Network Type of the individual LAN

Host Name / IP Host name and IP address of the individual LAN

● With the actions Add Switch Group and Delete Switch Group you can add or

delete switch groups, see section 10.18 Adding Switch Groups on page 161.

● With the actions Add Switch and Delete Switch you can add or delete

switches, see section 10.17 Adding Switches on page 160.

"Controlling" View Area

Management Tool 85

● In the Swg column you can change the association of switch groups to Control

Nodes. A left mouse-click on the appropriate field opens a pull-down menu, in which

you can select the desired association.

● In the other fields highlighted in white you can modify the host names of the switch

groups and Control Nodes as well as the host parts of the IP addresses of the

different LANs by direct input.

View Area "Application Nodes"

86 Management Tool

8.6 "Application Nodes"

The Application Nodes table is displayed. In this table all existing Application Nodes

of the FlexFrame environment on which the SAP services run are displayed with their

current parameters.

● You can display the table also via different sub-entries of the Pools object in the

object tree (see section 7.6 "Pools" Object on page 64), e.g. the information for a single pool is displayed under Pools/<pool_name>

and for a single group under

Pools/Pools/<pool_name>/Groups/<group_name>/Servers/

<server_name>:

If you open this view for a single Application Node via the object

Pools/<pool_name>/Groups/<group_name>/Servers <server_name>,

an additional area is displayed above the table. Here you can enter

miscellaneous settings concerning the Application Node, depending on its type.

This is particularly important for Application Nodes with type ESXVM.

All host names generated are used by FlexFrame system software. These host names

are physical host names and not restricted by SAP conventions like virtual host names.

So they may not be used by SAP applications.

Due to the table size the presentation of the Application Nodes table is

divided into a left part (first figure) and a right part (second figure) of the screen.

"Application Nodes" View Area

Management Tool 87

Host Name Name of the Application Node / hostname for this LAN

Type Type of the Application Node

Swg/HN Associated switch group/hypervisor node

Pool Associated pool

Group Associated pool group

OS Operating system of the component

Host Common host part of all VLAN segments for the component in the

relevant row

Network Type of the individual LAN and the “Network Connection” where

the VLAN / IP address is configured on


● With the actions Add Application Node and Delete Application Node you

can add or delete Application Nodes.

● With the actions Add Group and Delete Group you can add or delete pool groups.

● With the action Change to Hypervisor Node you can change an Application

Node to a hypervisor node.

The action Change to Hypervisor Node is only available in Planning

Mode.

● In the Swg/HN, Pool, Group and OS columns you can change the association of a

switch group or hypervisor node, pool, pool group and operating system to an

Application Node, respectively. A left mouse-click on the appropriate field opens a

pull-down menu, in which you can select the desired association.

View Area "Application Nodes"

88 Management Tool

● In the other fields highlighted in white you can modify the host names of the

Application Nodes and the host part of the IP addresses of the different LANs by

direct input.


"NAS Storage" View Area

Management Tool 89

8.7 "NAS Storage"

In the NAS Storage table all existing physical and virtual Network Attached Storage

systems are displayed with their current parameters.

● You can display this table also via the Storage and Storage/NAS objects in the

object tree (see section 7.5 "Storage" Object on page 62).

Due to the table size the presentation of the NAS Storage table is divided into

a left part (first figure) and a right part (second figure) of the screen.

View Area "NAS Storage"

90 Management Tool

Host Name Name of the NAS system

For NAS names only lower case letters should be used because

upper case letters will result in serious problems when applying

administration commands later.

Type Type and operating mode of the NAS system

(FAS… = NetApp Filer, VFILER = Virtual Filer)

The operating mode (ONTAP or cDOT) is shown in parentheses.

Swg Associated switch group

Relation

Name

Type of the relation, e.g. partner, parent or Interface

Reference Name of the related system, e.g. name of the remote partner of

this NAS system or name of the parent of a NAS

Host Host part of the IP address

Name Type of the individual LAN

Pool Name of the associated pool of the individual LAN


● With the actions Add NAS and Delete NAS you can add or delete NAS systems.

● With the actions Add Pool to NAS and Delete Pool from NAS you can add or

delete an IP address in the storage LAN of the selected pool.

● In the Swg column you can change the association of switch groups to NAS systems.

A left mouse-click on the appropriate field opens a pull-down menu, in which you can

select the desired association.

● In the other fields highlighted in white you can modify the host names of the NAS

systems and the host part of the IP addresses of the different LANs by direct input.


"Volumes" View Area

Management Tool 91

8.8 "Volumes"

The Volumes table is divided into three tabs:

● The "Volumes / Volume groups" tab, see page 91.

● The "Volume groups / LUNs" tab, see page 92.

● The "Pool / SID / Node Mount" tab, see page 92.

8.8.1 "Volumes / Volume groups"

In this view all existing volumes and volume groups are displayed with their current Mount

usage.

● For a NAS storage system you can open this view also object dependent via the

Storage/NAS/<NAS_name>

object in the object tree (see section 7.5 "Storage" Object on page 62).

Name Name of the volume or volume group

Host Name Name of the NAS system

Component Component of the NAS system on which the volume lies

Common VolFF

Device

NAS system is VolFF device (true) or not (false)

In a FlexFrame environment must be exactly one VolFF device

Storage Type Type of the storage system

Type Type of the mount point and the volume

Location Mount path of the volume

● With the actions Add Volume and Delete Volume you can add or delete volumes,

see section 10.21 Adding Volumes on page 164.

● In the fields highlighted in white you can modify volume names by direct input.

The actions Add Volume and Delete Volume are only available in Planning

Mode.

A manual input is also only possible in Planning Mode.

View Area "Volumes"

92 Management Tool

8.8.2 "Volume groups / LUNs"

In this view all existing volume groups and the related LUNs are displayed with their

current parameters.

Pool Name of the related pool to which the volume group is assigned

Pool group Name of the related pool group

VG name Name of the volume group

Referenced VG Name of the volume group referenced by the LUN

LUN Name Name of the LUN

Storage system Name or identification of the storage system

GUID Globally unique LUN ID as assigned by the storage system

ID Storage Storage system specific LUN ID

ID Host LUN ID (number) as seen on the host where the LUN is accessed

● With the actions Add Volume Group and Delete Volume Group you can add or

delete volume groups, see section 10.22 Adding Volume Groups on page 165.

● With the actions Add LUN and Delete LUN you can add or delete LUNs, see

section 10.23 Adding LUNs on page 166.

8.8.3 "Pool / SID / Node Mount"

In this table all existing Pool-to-Volume and SID-to-Volume relationships that differ from

the default relationship are displayed with their current parameters.

SID mounts Each SAP instance may mount a volume or a volume group for its saplog sub-directories or for its sapdata sub-directories. This

mounting of a volume is represented here as a relation from an SID

specific mount point to a volume or volume group.

"Volumes" View Area

Management Tool 93

Pool mounts Each pool may mount a volume for its sapdata, saplog and for pool

specific volFF sub-directories. This mounting of a volume is also

represented as a relation from a pool specific mount point to a volume.

All this mount relations may point to the same volume.

SID specific mounts always prevail. If there is no pool specific mount and no SID specific

mount the data will reside in the common volFF.

Mount Type Type of the mount point: Pool or SID

Pool Name of the associated pool

SID SID from SAP Services if Mount Type is SID

Node Number of the node of HANA DBs (reserved for future extensions,

currently only Singlenode configurations are supported, so the

value is always 1).

VolFF /

Sapdata /

Saplog /

Sapshared

Path and description of the related volume

● With the actions Add Mount Point and Delete Mount Point you can add or

delete mount points of volumes, see section 10.11 Adding Mount Points for Volumes

on page 128.

● With the Show all mounts checkbox you can display all volumes including the

default volumes and all locations where a mount point can be added in order to use a

volume other than the default volume.

The actions Add Mount Point and Delete Mount Point are only available

in Planning Mode.

View Area "SAP Services"

94 Management Tool

8.9 "SAP Services"

In this table SAP services are displayed with their current parameters.

● You can display this table object dependent via the Pools/<pool_name>/SIDs

object in the object tree (see page 64).

Due to the table size the presentation of the SAP Services table is divided

into a left part (first figure) and a right part (second figure) of the screen.

"SAP Services" View Area

Management Tool 95

SID ID of the SAP system

(up to three characters or digits, in accordance with SAP rules;

starts with a character)

RId Replication Id of R-HANA Service

Inst Instance number of a SAP system. It is in some cases used to

make resources (e.g. service ports) unique. Therefore a

warning is issued if the instance number is not unique.

Service Type Is also used to build the virtual host names (see also "Virtual

host names and virtual IP addresses" below)

Node NodeID of the node of HANA DBs.

DB / SAP Database type and SAP version of the service type

UIDs / GIDs SID specific user and group ID

Pool Name of the associated pool


the relevant row

Network Type of the individual LAN

Host Name Virtual host name of the individual LAN

IP Virtual IP address of the individual LAN

● With the actions Add SAP Service and Delete SAP Service you can add or

delete SAP systems, see section 10.16 Adding SAP Services on page 142.

● With the actions Add Instance and Delete Instance you can add or delete SAP

instances.

● In the fields highlighted in white you can modify the SIDs, instance numbers, DB user

IDs, SAP user IDs as well as the host part of the virtual IP addresses of the different

LANs by direct input.

A manual input is only possible in Planning Mode.

Virtual host names and virtual IP addresses

Virtual host names and the corresponding virtual IP addresses are used by applications

to address the server on which an SAP instance is running.

The virtual IP address is assigned to a physical host dynamically before an SAP instance

is started. Thus, it identifies the actual host on which the SAP instance is running. If an

SAP instance is moved to another server, this SAP instance always is addressable using

the same virtual IP address. Virtual IP addresses are also used for communication from

applications outside FlexFrame systems, i.e. SAP front ends such as SAPGUI.

View Area "SAP Services"

96 Management Tool

Virtual host names are formed as follows:

<service_type>[<ID>]<SID>[<-LAN_type>]

service_type db

ci

app

ascs

scs

jc

j

lc

ers

mdis

mds

mdss

trx

cms

bobj

smd

hdb

hdb-mn

wd

pai

database instance

central instance (ABAP, until SAP release 7.3)

application instance (ABAP)

ABAP central services instance (message server)

JAVA central services instance (message server)

JAVA central instance

JAVA application instance

LiveCache instance

Enqueue Replication Service Instance

MDM Import Server Instance

MDM Server instance

MDM Syndication Server instance

TREX Application Server instance

Content Management Service instance

Business Objects Enterprise instance

Solution Manager Diagnostic agent

HANA or R-HANA DB instance

HANA-MN or R-HANA-MN DB instance

Web Dispatcher instance

Primary Application Server Instance (former used ci,

used from SAP release 7.4 and higher)

ID Instance number from 00 to 97 for the service type (left empty for db

and lc).

SID System ID of an SAP system.

LAN_type -se Server LAN

empty string Client LAN

This host name formation rule for virtual services is mandatory. Some components rely

on this rule.

"Users Groups Services" View Area

Management Tool 97

8.10 "Users Groups Services"

The "Users Groups Services" table gives you an overview over the Location, the User

Name and User ID of all SAP services in the related scope (pool scope or global scope).

● In the fields highlighted in white you can modify the User IDs by direct input.

A manual input is only possible in Planning Mode.

Only the users, groups and services that are known to FlexFrame are shown

here. If no user ID is assigned, an appropriate user ID is generated during

installation.

View Area "External Connectivity"

98 Management Tool

For users or groups that are reserved with ff_user_adm.pl or ff_group_adm.pl the

Location column contains the poolname only.

8.11 "External Connectivity"

With the Management Tool a pool-specific external connectivity can be planned. It leads

to configuration of abstract external connectivity devices. For a pool-independent global

connectivity see section 6.3.4 Generating Global Connectivity on page 50.

The switch ports connected to NICs of this external connectivity devices are configured

with untagged VLAN switch ports in case of a single VLAN. In case of multiple VLANs, all

will be configured as tagged. If tagged, devices plugged into these ports require

interfaces using tagged VLANs. To be able to communicate, these VLANs have to be

configured with the same VLAN IDs like the switch port and as configured with the

Management Tool. A link aggregation for load balancing will not work and may block the

entire network!

"External Connectivity" View Area

Management Tool 99

In the External Connectivity table all network connections of the internal FlexFrame

networks to the operator’s corporate network are displayed with their current parameters.

Entries in the various LAN segments may, for example, be necessary for backup servers

or servers outside the FlexFrame environment.

● You can also open this view object dependent by selecting the

Pools/<pool_name>/External Connectivity object in the object tree (see

section 7.6 "Pools" Object on page 64).

To open the External Connectivity view via the object tree is only possible in

Planning Mode.

Due to the table size the presentation of the SAP Services table is divided

into a left part (first figure) and a right part (second figure) of the screen.

Host Name Host name of the external device

Swg Associated switch group

Pool Associated pool

NICs Number of NICs

View Area "External Connectivity"

100 Management Tool


the relevant row


● With the actions Add External Connectivity and Delete External

Connectivity you can add or delete a connection (see section 10.9 Adding

External Connectivities (Pool-specific) on page 126).

● In the Swg column you can change the association of a switch group to the external

device. A left mouse-click on the appropriate field opens a pull-down menu, in which

you can select the desired association.

● In the fields highlighted in white you can modify the host names as well as the host

part of the IP addresses of the different LANs by direct input.

The actions Add External Connectivity and Delete External

Connectivity are only available in Planning Mode.

A manual input is also only possible in Planning Mode.

"Chassis" View Area

Management Tool 101

8.12 "Chassis"

In this table all chassis from the chassis list are listed one after another: SWB, MGMT

blades and server blades in the order of the slots. The slot number is displayed in the

Slot column.

Due to the table size the presentation of the Chassis table is divided into a left

part (first figure) and a right part (second figure) of the screen.

View Area "Hypervisor Nodes"

102 Management Tool

8.13 "Hypervisor Nodes"

In this table, all hypervisor nodes are displayed with their current parameters. You can

also add a hypervisor node, delete a hypervisor node or change a hypervisor node to an

Application Node.

The action Change to AN is only available in Planning Mode.

"Wiring" View Area

Management Tool 103

8.14 "Wiring"

In the Wiring view a document comprising the generated network wiring plan is

displayed.

Wiring plan in Planning Mode

The wiring plan is available in several places in the object tree. Click right and add an

wiring object. The wiring plan will be displayed as related view, showing you the wiring

plan of the objects in the sub-tree.

Places where you can add a Wiring object:

FlexFrame

Storage

Pools – <pool>

Pools – <pool> –- Groups – <group>

View Area "Wiring"

104 Management Tool

Wiring plan in Administration Mode

In Administration Mode, the wiring plan is not available via the object tree. The wiring plan

can be displayed via the Wiring tab in the FlexFrame overview.

In contrast to the Planning Mode the Channel IDs are shown in the Administration mode.

"IPs" View Area

Management Tool 105

8.15 "IPs"

In the IPs view a table with all IP addresses in this scope is displayed. The IPs view with

the IP table is displayed in the context of all LAN definitions (Control LAN, Client Lan,

Server Lan, Storage Lan).

If an IP address is reserved with ff_hosts_sh the Node column contains "---".

You can print the IP table by clicking the Print button or you can write the table as

comma separated values into a text file by clicking the Write text file button.

View Area "IPs"

106 Management Tool

To display all IPs in a global FlexFrame scope you may also add, similar to the Wiring

View, an IPs View object directly as a child of the FlexFrame object.

General Overview Execution Area

Management Tool 107

9 Execution Area

9.1 General Overview

Command line:

Every action you perform in Administration Mode results in one or more

commands. These commands are displayed in the command line.

The commands are explained in detail in the "FlexFrame® –

Administration and Operation" guide.

Every command generated automatically by the Management Tool

corresponds one-to-one to a command you can type in manually in

the command prompt of your FlexFrame system.

If you click on the button Execute, these commands are directly executed on

the control nodes.

Standard streams (standard input, standard output and standard error) are

logged in the status area below.

Execution Area Administration Commands Overview

108 Management Tool

Status area:

In the status area the progress of the executed commands and the response

of the FlexFrame environment are displayed.

The Execution area is only displayed if you are working in Administration Mode;

Administration option in the Menu bar.

The display of the view area is not affected and remains the same for Planning

Mode and Administration Mode.

9.2 Administration Commands Overview

Setting of Options and Preferences

With the functions Options/Preferences in the Edit menu (see section 6.2.4

"Options/Preferences" on page 45) you can select the options debug, verbose and

dryrun which are to be appended to each executed administration command.

Adding and Deleting Objects

The paths given in the column “via context menu in the named object” in the “Actions

Overview Table” below are valid for adding an object. Perform a right mouse-click on the

higher-level container object and select “Add” in the context menu.

To delete an object you have to select the specific object itself and select “Delete” in the

context menu.

Example for adding an Application Node:

To add an application node select Pools/<pool>/Groups/<group>/Servers and

perform a right mouse-click on Servers. From the Add context menu select an

Application Node.

Example for deleting an Application Node:

To delete an Application Node select

Pools/<pool>/Groups/<group>/Servers/<server> and perform a right mouse-

click on the specific server. Select Delete from the context menu.

Command Overview

The following table gives an overview of all administration commands and how the

commands can be created.

Administration Commands Overview Execution Area

Management Tool 109

You can add/delete Administration command Creation via button

in the table named:

Creation via context menu in

the named object

Application Nodes ff_an_adm.pl Application

Nodes

FlexFrame/Pools/<pool>/

Groups/<group>/Servers

Application Node image ff_new_an.sh -- FlexFrame/Pools/<pool>/

Groups/<group>/Servers/

<server>

Hypervisor Nodes ff_hn_adm.pl Hypervisor

Nodes

FlexFrame/Hypervisor

Nodes/Server List

Blade Server Chassis ff_bx_cabinet_adm.pl Chassis FlexFrame/Chassis

LANs

Storage LANs

ff_nas_adm.pl NAS Storage FlexFrame/Storage/NAS/

<filer>/Storage LANs

LUNs ff_volgroup_adm.pl Volume groups /

LUNs

FlexFrame/Storage/SAN/

LUNs

Networks/LANs ff_network_adm.pl Networks FlexFrame/Pools/<pool>

FlexFrame/Control Center

NAS Systems ff_nas_adm.pl NAS Storage FlexFrame/Storage/NAS

Pool Groups ff_poolgroup_adm.pl Application

Nodes

FlexFrame/Pools/<pool>/

Groups

Pools ff_pool_adm.pl Pools FlexFrame/Pools

SAP Services ff_sid_adm.pl

ff_setup_sid_folder.sh

SAP Services FlexFrame/Pools/<pool>/

SIDs/<sid>

SAP Instances ff_sid_adm.pl SAP Services FlexFrame/Pools/<pool>/

SIDs

Switches ff_swgroup_adm.pl Controlling FlexFrame/Network/Switch

Groups/<swg>/Switches

FlexFrame/Network/Switch

Groups/<swg>

Switch Groups ff_swgroup_adm.pl Controlling FlexFrame/Network/Switch

Groups

Execution Area Validation

110 Management Tool

You can add/delete Administration command Creation via button

in the table named:

Creation via context menu in

the named object

Volume Groups ff_volgroup_adm.pl Volume groups /

LUNs

FlexFrame/Storage/SAN/

Volume Groups

9.3 Validation

Previously a validation of the commands is performed before you can click on Execute

and start running the commands.

If any error occurs, e.g. a variable is missing and you have to define it in advance, the Execute button is disabled and highlighted in red.

● Click on Show Errors.

The window Validation results opens. A table is listing the corresponding

errors.

The Message column displays a message containing a problem description.

Example:

In this case no switch group has been defined (no associated Swg and no "Core

or Direct" connection).

● Click on OK to close the Validation results window.

● Select a switch group in the View area above the Execution area.

Validation Execution Area

Management Tool 111

After you have selected the Swg, the command is updated and validated again.

Now that the switch group is defined, the validation passed and you can execute the

commands by clicking on Execute.

Management Tool 113

10 Actions

How to Perform Actions

Actions are performed via action buttons within the views or via context menus (right

mouse click on an object) within the structured object tree.

Add actions always generate a new sub-tree in the structured object tree like storage

objects with their sub-components, Application Nodes with their NICs and LAN addresses

or switch groups.

Add actions, which are invoked for example using the buttons in tables, like the

Application Node table or the Pool table always will show a dialog. This kind of dialogs –

when terminated with the "OK" button – will provide standard FlexFrame device objects

with their sub-trees. In most cases this will be sufficient to configure your FlexFrame

installation.

For a more detailed editing of FlexFrame objects you have to navigate in the structured

object tree to the object you want to modify and edit the properties in the view area or

delete or add objects via the right-click context menu. Like this you can modify default

settings or object sub-trees as they were built using higher level dialogs.

Not all right-click add or delete actions in the object tree will open a dialog box. Some

objects are just added to the object tree with their properties having default values and

you will have to modify these properties later to your needs.

How to Complete Actions in Administration Mode

If you want to modify the existing FlexFrame environment in Administration Mode you

have to execute the commands, created by the Management Tool.

The procedure is described in section 9 Execution Area on page 107.

Not all actions that can be performed in Planning Mode are available in

Administration Mode. An overview of the possible actions that can be performed

is provided in section 4.2.1 Features Overview on page 17.

Actions Actions Overview

114 Management Tool

10.1 Actions Overview

Adding and Deleting Objects

The paths given in the column “via context menu in the named object” in the “Actions

Overview Table” below are valid for adding an object. Perform a right mouse-click on the

higher-level container object and select “Add” in the context menu.

To delete an object you have to select the specific object itself and select “Delete” in the

context menu.

Example for adding an Application Node:

To add an application node select Pools/<pool>/Groups/<group>/Servers and

perform a right mouse-click on Servers. From the Add context menu select an

Application Node.

Example for deleting an Application Node:

To delete an Application Node select Pools/<pool>/Groups/<group>/Servers/<server> and perform a right mouse-

click on the specific server. Select Delete from the context menu.

10.1.1 Actions Overview Table

The following table gives an overview where actions can be performed and an object is

added or deleted.

PM: Planning Mode AM: Administration Mode

x: available o: not available

Further actions which do not result in adding or deleting a visible object in the

object tree are listed in section 10.1.2 Other administrative commands available

in Administration Mode on page 117.

You can add/delete via button in the table

named: via context menu in the named object

PM A

M

PM AM

Actions Overview Actions

Management Tool 115



PM A

M

PM AM

Wiring View

This is a special view

object which displays the

wiring for the

corresponding object in

the view area.

o o FlexFrame

Storage

Pools/<pool>

Pools/<pool>/Groups/

<group>

x o

Application Nodes Application

Nodes x x

Pools/<pool>/Groups/

<group>/Servers x x

Hypervisor Nodes Hypervisor

Nodes x x

Hypervisor Nodes/Server

List x x

Blade Server Chassis Chassis x x Chassis x x

Data NICs o

o

Control

Center/<control_node>

Chassis/<blade_server>/

<swb>

Global Connectivity/

Client LAN Connection

<n>/ClLanCons

Storage/NAS/<filer>

External Connectivities

(pool-specific)

External

Connectivity x x

Pools/<pool> (first

call)

Pools/<pool>/External

Connectivity

(further calls)

LUNs

Volume

groups /

LUNS

x x Storage/SAN/LUNs x x

Mount Points for

Volumes

Pool / SID

Node mount x o

NAS Systems NAS Storage x x Storage/NAS x x

Networks/LANs Networks x x Pools/<pool>

Control Center x x

Actions Actions Overview

116 Management Tool



PM A

M

PM AM

Network Connections o o

Pools/<pool>/

Groups/<group>/Servers/

<server>

x o

Pool Groups Application

Nodes x x Pools/<pool>/Groups x x

Pools Pools x x Pools x x

SAP Instances SAP Services x x Pools/<pool>/SIDs/<sid>/

Instances x x

SAP Services SAP Services x x Pools/<pool>/SIDs x x

SAP Service nodes o o

Pools/<pool>/SIDs/<sid>/

HDB Instances/<instance>

/Nodes

x

Switches Controlling x x Network/Switch Groups/

<swg>/Switches x x

Switch Groups Controlling x x Network/Switch Groups x x

Switch Ports o o Network/Core or Direct/

Ports Core or Direct x o

Volumes Volumes x o Storage/NAS/<filer>/

Volumes x o

Volume Groups

Volume

groups /

LUNS

x x Storage/SAN/Volume

groups x x

Deleting in Planning Mode:

In Planning Mode the Delete action deletes all objects in the object tree.

This action is carried out directly in Planning Mode, no safety inquiry will

take place!

If you delete an object by mistake in Planning Mode, you can repair it:

● perform the Undo function in the Edit menu or

● add it again in the object immediately above or

● read it in the configuration file again with the

Actions Overview Actions

Management Tool 117

Open -> Configuration File function.

In the last case, all input that you made previously is lost (if you did not

accomplish a backup in the meantime).

Deleting in Administration Mode:

In AdministrationMode you always have to confirm the Delete action by

"Execute".

Be aware: if you delete an object by mistake in Administration Mode and confirm

the deletion, you cannot repair it!

In case of delete actions which are carried out via a dialog box, you must specify

the object to be deleted. These boxes have all the same structure and are not

described explicitly.

10.1.2 Other administrative commands available in Administration Mode

Some other administrative commands available in the context menu are related to

objects, which are not visible in the object tree.

These administrative commands are only available in Administration Mode.

To this, the following commands belong:

Action Path in the Object Tree

New AN (Create AN Image) Pools/<pool>/Groups/<group>/Servers/

<server>

Complete Installation Hypervisor Nodes /Server List/<server>

Setup SID Folder Pools/<pool>/SIDs/<sid>

Add SWG Uplink

Delete SWG Uplink

Extend SWG Uplink

Network/Switch Groups/<switch group>

Actions Context Menu of Selected Objects

118 Management Tool

10.2 Context Menu of Selected Objects

The context menu of selected objects is the best choice to perform actions on an object.

Some possibilities to modify an object you will only find in the context menu of an object.

Some context menus are only available in Planning Mode or in

Administration Mode respectively.

For more information see section 10.1 Actions Overview on page 114.

● Essential context menu functions are Add and Delete; they are available in the

context of nearly every object.

● Another important function that is available in the context menu of some object is the convert to function.

With the convert to function you are able to convert objects in compatible objects

while keeping the information in the subtree of the converted objects.

For Netapp NAS devices e.g. this means, that you can convert a specific filer type to

a compatible other filer type and wiring and network addresses are kept the same.

The action convert to is only available in Planning Mode.

Adding Hypervisor Nodes Actions

Management Tool 119

10.3 Adding Hypervisor Nodes

The action for adding a Hypervisor Node opens a dialog box in which the type of the

Hypervisor Nodes and the corresponding parameters are selected.

Add Hypervisor Node Dialog Box (example for Blade Server only available in

Administration Mode):

Add Hypervisor Node Dialog Box (example for Rack Server):

Actions Adding Complete Configuration

120 Management Tool

Type Type of the Hypervisor Node.

Hypervisor ESX or KVM (Kernel-based Virtual Machine)

Chassis Slot Slot number of the server blade.

Switch Group Available switch group

Host Name Host name of the Hypervisor Node

10 GBit Data NICs true / false

macAddress1 (Only available in Administration Mode)

macAddress2 (Only available in Administration Mode)

10.4 Adding Complete Configuration

The action Add Complete Configuration is only available in Administration

Mode.

To add a Complete Configuration type in administrator user name and password.

User Administrator user name

Password Administrator password

Adding Application Nodes Actions

Management Tool 121

10.5 Adding Application Nodes

The action for adding an Application Node opens a dialog box in which the number and

type of the input fields depend on the selected server.

Actions Adding Application Nodes

122 Management Tool

Type Type of the Application Node.

Pool Pool to which the Application Node belongs.

Group Pool group to which the Application Node belongs.

Host Name Host name of the Application Node.

Switch Group Associated switch group.

OS Operating system (in Planning Mode)

OS Image Path to the operating system image (in Administration Mode)

Chassis Slot Slot number of the server blade

10 Gbit Data NICs true / false

Hypervisor Node

for VM

Name of the Hypervisor Node where the virtual machine will

be executed

Number of virtual

CPUs

Number of CPUs for the virtual machine. Must be a number

between 1 and 8. Moreover, the available resources of the

Hypervisor Node and the intended usage must be taken into

account.

Memory of VM [MB] Memory size in MB for the virtual machine. Must be a number

between 256 and 261120 (=255GB). Moreover, the available

resources of the Hypervisor Node and the intended usage

must be taken into account.

Overcommit of

Memory

true / false

If you change the type of the Application Node a dialog box opens saying that the

"AN parameters" are reinitialized.

Adding Application Nodes Actions

Management Tool 123

Just like add actions in general, adding an Application Node generates a new sub-tree in

the structured object tree. You have to navigate to the object representing the Application

Node and select it to activate the associated view, to be able to edit additional properties

of the newly created Application Node. This is particularly important for Application Nodes

of type ESXVM or KVMVM, which denotes a virtual machine on a hypervisor node.

The upper pane of this view contains virtual machine properties that are set to default

values, but should be adjusted to match the configuration requirements, as well as a link

to the hypervisor node on which the virtual machine will be created during the installation

process.

The meaning of these properties is described in the table on page 122.

Actions Adding New AN (Create an AN Image)

124 Management Tool

10.6 Adding New AN (Create an AN Image)

The action Add New AN (Create an AN Image)is only available in

Administration Mode.

The action for adding a New AN (Create an AN Image) opens a dialog box to select

whether to overwrite an existing image or not.

Overwrite

existing image

true / false

Adding Blade Server Chassis Actions

Management Tool 125

10.7 Adding Blade Server Chassis

The action for adding a blade server chassis opens the following dialog box.

Type Type of the blade chassis.

Host Name Host name of the blade chassis.


Switch Blade Type Type of the switch blade


Number of NICs Number of the network interface controllers

Login User name (only in Admin Mode available)

Password Password (only in Admin Mode available)

If you delete a blade server chassis the Application Nodes or hypervisor nodes that are

our FlexFrame representatives of this server blades still exist. These Application Nodes

or ESX just won’t be related anymore to a chassis via the Connector and Slot objects.

Depending on the Chassis Type – Switch Blade Type combination, due to the actual

availability, the input for "10 GBit Data NICs" and / or "Number of NICs" may by disabled

or not visible at all.

To assign a server blade to a new / different chassis do the following::

● Activate a connector in the sub-tree of the server blade.

● Select a new chassis slot corresponding to another blade server chassis.

Actions Adding Data NICs

126 Management Tool

10.8 Adding Data NICs

The action Add Data NICs is only available in Planning Mode.

The action for adding a data NIC is carried out directly, no dialog box is opened. The

following list shows the admissible range for the number of NICs that can be present for

the different types of Network Attached Storage:

2 1GbE NICs 16 or alternatively exactly 2 NICs of 10GbE type for the different

NetApp FASxxxx filer families (the exact maximum varies between the family types).

The interfaces added to already present interfaces have all to be of the same type,

either homogeneously 1GbE or homogeneously 10GbE.

10.9 Adding External Connectivities (Pool-specific)

The action Add external connectivity is only available in Planning Mode.

The action for adding a pool-specific external connectivity opens the following dialog box.

Procedure when adding an external device via context menu in the object tree:

With the first call of the action under Pools – <pool> the object External

Connectivity is created and the first device is added. Further devices can be

added then under Pools – <pool> – External Connectivity with

Add – External Device.

Default for external connectivities are 1 GBit ports. If you need external

connectivities with 10 GBit ports you have to navigate in the object tree to the

“DataNICs” of the external connectivity, “right click delete” the 1GBit DataNICs

and “right click add” 10 GBit DataNICs instead.

Adding LAN Interfaces Actions

Management Tool 127

Host Name Host name of the external device.

Client LAN

Storage LAN

Server LAN

Control LAN

Choice of the LANs which should be visible outside FlexFrame.

Pool Name of the associated pool.


10 GBit NICs true / false

Number of NICs Number of NICs.

10.10 Adding LAN Interfaces

In Administration Mode the action Add LAN Interface is only available for

storage LAN of NAS systems.

In Planning Mode the action Add LAN Interface is also available for the

storage LAN of the Control Nodes.

The action for adding a LAN interface opens the following dialog box. Depending on the

selected object in the object tree, this can be the interface for a Control LAN (max. 2 can

be present), a Client LAN, a Server LAN or a Storage LAN.

Actions Adding Mount Points for Volumes

128 Management Tool

LAN Selection of the appropriate LAN

Host Host part of the IP address of the LAN

10.11 Adding Mount Points for Volumes

The action for adding a mount point for a volume opens the following dialog box.

Mount Point Object tree path of the mount point.

Mount points exist for pool objects and for the database objects in the sub-tree of SID objects. For the database objects you can add sapdata and saplog mount points and

for pools in addition to these two mount points you can add a volFF mount point.

With Mount Point objects you can relate a mount point object to Volume. For FlexFrame

this just means that you mount e.g. sapdata for the given SID / Pool directory from the

specified volume of the filer that it resides on.

Adding NAS Systems Actions

Management Tool 129

10.12 Adding NAS Systems

Depending on the NAS type, the action for adding a NAS system opens one of the

following dialog boxes.

Actions Adding NAS Systems

130 Management Tool


Management Tool 131


132 Management Tool

Type

Type of the NAS system to be added.

This field is only available if the action is called via the Add

NAS button in the NAS Storage view.

Refer also to the section 3.3 NAS Storage on page 10.

Switch Group Available switch group

Name Name of the NAS system.

For NAS names only lower case letters should be used

because upper case letters will result in serious problems

when applying administration commands later.

Use Operating mode (ONTAP or cDOT)

For Details on how to use the cDOT operating mode see

section 10.12.1 Configuring a cDOT cluster in planning

mode on page 133.


Number of NICs Number of used Network Interface Cards (2-6).


Management Tool 133

10.12.1 Configuring a cDOT cluster in planning mode

To create a cDOT Cluster perform the following steps:

● Select New Configuration from the File menu.

● Set the Type parameter in the NAS System area to SVM and enter a Name for the

SVM e.g. svm-01 and a valid interface name, e.g. a0a.


134 Management Tool

● Select the FlexFrame object in the object tree and then the NAS Storage tab in

the view area.

● Click on the Add NAS button to open the dialog box for adding a NAS system.

In the dialog box select a filer in the Type field, e.g. FAS8060, select a switch group,

set the Use parameter to cDOT and enter a name for the filer, e.g. fas-11.

● Add more filers by repeating the previous step with different filer names, e.g. fas-

12, fas-21 and fas-22, so that an even number of filers are defined.


Management Tool 135

● Assign a partner to each existing filer so that pairs are built, e.g. fas-11 / fas-12

and fas-21 / fas-22.


136 Management Tool

● Then click on the Add NAS button again to add a cDOT cluster.

In the dialog box set the Type parameter to cDOTCluster and enter a name, e.g.

cluster-01.

● Assign the new cDOT cluster as parent to each of the filers added in the previous

steps.


Management Tool 137

● Assign any of the filers related to the cluster as parent to the SVM. This is owed to

performance reasons, logically the cluster is assigned as parent.

● Select the function IP Addresses – Initialize ‘0’ And ‘1’ Hostparts

in the Tools menu to initialize the IP addresses.

10.12.2 Configuring a cDOT cluster in administration mode

In administration mode every single NAS system has to be fully defined before the administration command can be executed. This can be only achieved, when you add the NAS systems in the following sequence:

1. cDOTCluster

2. FASxxxx with "parent" from step 1)

3. FASxxxx with "partner" from step 2) and "parent" from step 1)

4. SVM with "parent" from step 2) or 3)

Actions Adding Networks

138 Management Tool

10.13 Adding Networks

The action for adding a network opens the following dialog box.

Pool Name of the Pool

LAN Selection of the appropriate LAN. For the possible types of

LANs see the “Administration and Operation” manual.

Network /

Netmask /

VLAN ID

Network parameters of the individual LAN

Adding Pool Groups Actions

Management Tool 139

10.14 Adding Pool Groups

The action for adding a pool group opens the following dialog box.

Pool Host name of the pool.

Group Name Associated group.

Actions Adding Pools

140 Management Tool

10.15 Adding Pools

The action for adding a pool opens the following dialog box.

Pool Name Name of the new pool.

The name must start with a letter and may only contain numbers,

letters and "-". The pool name becomes part of an automatically

generated host name that may only be up to 13 characters long

in an SAP environment. Therefore, we recommend that the pool

name should be limited to three characters and written in lower

case letters.

Group Name Name of the first group within the pool.

The name must start with a letter and may only contain numbers,

letters, "_" or "-".

Adding Pools Actions

Management Tool 141

DNS Domain Name DNS domain name for the pool.

The name has to be conform to RFC1035. This means, the

domain parts have to be separated by a dot and must consist of

alphanumerical characters and dashes. The parts may not begin

with a number or a dash.

DNS Server DNS Domain Server for the pool (IPv4 format).

The name has to be conforming to RFC1035 (see above).

Network (LANs)

Relevant network in IPv4 format.

In binary, the network address must contain a zero at the same

position as the netmask of the individual LAN segments. The

individual networks must be different from each other.

Netmask (LANs)

Relevant netmask in IPv4 format.

In the network section the netmask must consist of binary ones,

and in the host section of binary zeros. You are recommended to

use the same netmask for all network segments.

VLAN ID (LANs)

Relevant VLAN ID.

The VLAN ID is an integer between 2 and 4094. The VLAN IDs

must be unique over all LAN segments.

Depending on the switching hardware (switch blades or

switchgroup switches) further restrictions may apply. For details

see the "HW Characteristics Quickguides" of these devices.

VolFF /

Sapdata /

Saplog

Path of the related volume

There is only one common Control LAN even though in the Pools table a

Control LAN is displayed for each pool.

Actions Adding SAP Services

142 Management Tool

10.16 Adding SAP Services

The action for adding a SAP service opens the following dialog box with 10 tabs for

different service types.

● Classic (SAP NetWeaver), page 143

● LiveCache Service (LC), page 147

● Business Objects Enterprise Service (BOBJ/SBOP), page 148

● Content Management Server Service (CMS), page 149

● Search and Classification Service (TRX), page 150

● Master Data Management Service Type (MDM), page 151

● Solution Manager Diagnostics Service Type (SMD), page 152

● Web Dispatcher Service Type (WD), page 155

● HANA and HANA-MN DB Service Type (HANA/HANA-MN), page 156

● R-HANA and R-HANA-MN DB Service Type (R-HANA/R-HANA-MN), page 158

Adding SAP Services Actions

Management Tool 143

10.16.1 Classic


144 Management Tool

SID SAP system ID (up to three characters or digits

in accordance with SAP rules).


Configuration Configuration type of SAP instances.

SAP Version SAP version.

For details on the available SAP versions see

the “FlexFrame® – Installation Guide for SAP

Solutions” manual.

DB Version Type and version of the database.

If the selected value stands for an external

DataBase (e.g. Hana DB Service Type, refer to

section 10.16.9 HANA and HANA-MN DB

Service Type (HANA/HANA-MN) on page 156

or R-HANA DB Service Type, refer to section

10.16.10 R-HANA and R-HANA-MN DB

Service Type (R-HANA/R-HANA-MN) on page

158) then you have to configure this relation in

a second step by editing the properties of this

SID.

Volume(s) Selectable path of the predefined volume or

volume group related do Sapdata or Saplog.

In Administration mode you may enter the NAS

volume manually if the Management Tool has

no knowledge about existing volumes.

Format: [NAS] <NAS system> <volume>.

Instance(s) Number of SAP instances.

Classic System Uid(s) SID specific user IDs and group IDs

(depending on the selected DB type).

10.16.1.1 Classic Service with external HANA or R-HANA-DB

The configuration has to be processed in two steps:

● First add a HANA DB Service Type, as described in section 10.16.9 HANA and

HANA-MN DB Service Type (HANA/HANA-MN) on page 156 or an R-HANA DB

Service Type, as described in section 10.16.10 R-HANA and R-HANA-MN DB

Service Type (R-HANA/R-HANA-MN) on page 158.

● Then add a classic service with the following parameters:

SAP Version SAP-7.3-HANA or SAP-7.4-HANA

DB Version HANADB-REF


Management Tool 145

To complete this configuration you must establish the connection to the DB:

● Set the Reference to a HANA DB field to the SID of the required HANA DB or R-

HANA DB as shown in the following screenshot:


146 Management Tool


Management Tool 147

10.16.2 LiveCache Service (LC)

The meaning of the fields in the dialog box for the LiveCache service type (LC) is

the same as that for the corresponding fields in the dialog box for the Classic

service type.


148 Management Tool

10.16.3 Business Objects Enterprise Service (BOBJ/SBOP)

SID SAP system ID (up to three characters, in

accordance with SAP rules).




BOBJ System Uid(s) SID specific user IDs and group IDs



Management Tool 149

10.16.4 Content Management Server Service (CMS)




Volume(s) Selectable path of the volume or volume group

related do Sapdata or Saplog.








CMS System Uid(s) SID specific user IDs and group IDs



150 Management Tool

The central feature of the CMS is that it is designed to be compatible with different types

of storage media. The CMS works as an interface between content servers and the

SAP System.

10.16.5 Search and Classification Service (TRX)






TRX System Uid(s) SID specific user IDs and group IDs


TRX finds information in unstructured and structured data. TRX provides SAP

applications with services for searching and classifying large collections of documents

and for searching and aggregating business objects.


Management Tool 151

10.16.6 Master Data Management Service Type (MDM)












Instance(s) Instance numbers.

MDM System Uid(s) SID specific user IDs and group IDs

(depending on the selected DB type, conform to

classic SAP system spec).


152 Management Tool

10.16.7 Solution Manager Diagnostics Service Type (SMD)




Configuration Configuration type of SAP instances.


For details on the available SAP versions see

the “FlexFrame® – Installation Guide for SAP

Solutions” manual.

A host based SMD type as SMD-7.4-HOST

requires a reference to a monitored host (see

below).

Number of Instances Number of SMD instances.


Management Tool 153

DB Type and Version Type and version of the database.

SMD System Uid(s) SID specific user IDs and group IDs



154 Management Tool

Assigning the reference to a monitored host

To assign the reference to a monitored host select the SMD object in the object tree.

Then you can select the required host in the view area as shown:

The Solution Manager Diagnostic (SMD) Agent is the remote component of the E2E Root

Cause Analysis. It performs a connection between SAP Solution Manager (as the

managing system) and the managed system(s). It gathers information from the managed

system(s) and reports them to the SAP Solution Manager.


Management Tool 155

10.16.8 Web Dispatcher Service Type (WD)






WD System Uid(s) SID specific user IDs and group IDs.

The SAP WebDispatcher is a layer between the Internet and customer's SAP system(s).

It is built with a number of Web application servers which are the entry point for HTTP(s)

requests into your SAP system(s). It is a 'software web switch' which accepts or rejects

connections. It balances the requests to ensure an even distribution across the available

SAP service(s).It is used with pure ABAP/JAVA or ABAP/JAVA doublestack installations.


156 Management Tool

10.16.9 HANA and HANA-MN DB Service Type (HANA/HANA-MN)







Management Tool 157



If neither Sapdata nor Saplog is assigned to a

node, this node is considered to be a standby

node. Otherwise it is considered to be a worker

node.

For a HANA SID Sapshare only a NAS volume

may be used.



no knowledge about existing volumes (if they

don’t appear in the combo box).


More detailed information of how defining

volumes you will find in the FFO V1.2

“Installation Guide for SAP Solutions”

Instance(s)/Node(s) Number of SAP instances (here only one “hdb”

instance) and with “hdpprop” the number of

nodes (with a single node system only one).

HANA System Uid(s) SID specific user IDs and group IDs


SAP-HANA is an in-memory database architecture. It is designed to support real-time

analytic and transactional processing.

It is only possible to define an initial configuration here. A running HANA-MN

configuration may dynamically reassign standby and worker mode to a node.

The definition of Sapdata and Saplog must provide individual volumes for each node. Any

volume cannot be used for the storage of the data of more the one node.

The necessary node-specific volumes for /usr/sap/SID and /home_sap/sidadm

have to be assigned manually via CLI (ff_sid_mnt_adm.pl) after the initialisation of

LDAP.


158 Management Tool

10.16.10 R-HANA and R-HANA-MN DB Service Type (R-HANA/R-HANA-MN)




System Replication Parameters for replication service: Replica ID: Replication ID.

At least Replication ID 0 must

be defined for each SID. Run in Group: Different Replication IDs of

the same SID must run in

different groups.




Management Tool 159



For a R-HANA SID Sapshare only a NAS

volume may be used.



no knowledge about existing volumes (if they

don’t appear in the combo box).


More detailed information of how defining

volumes you will find in the FFO V1.2

“Installation Guide for SAP Solutions”

Instance(s)/Node(s) Number of SAP instances (here only one “hdb”

instance) Number of SAP instances (here only

one “hdb” instance) and with “hdpprop” the

number of nodes.

R-HANA System Uid(s) SID specific user IDs and group IDs


SAP-R-HANA is an in-memory database architecture with replication service. It is

designed to support real-time analytic and transactional processing.

Actions Adding Switches

160 Management Tool

10.17 Adding Switches

The action for adding a switch opens the following dialog box.

Adding a switch is carried out via the Network object in the object tree.

Number of Switches Number of switches within the group. At least two switches

have to be configured in a switch group to provide network

redundancy. The upper limit is currently nine switches.

Switch Type The switch type of each switch within the group. Knowledge

of the precise name of each switch type is required to create

the cabling plan and the switch configurations.

WARNING: If you are building a stack of more than 4 Cisco 3750E switches:

In order to make sure, that this stack is dimensioned well for the planned

FlexFrame configuration, you should consult the FTS configuration and sizing

team in Walldorf before completion of configuration design.

Adding Switch Groups Actions

Management Tool 161

10.18 Adding Switch Groups

The action for adding a switch group opens the following dialog box.

Switch Group Name Name of the new switch group.

Number of Switches See description under Adding Switches above.

Typically 2 switches should be assigned.

Switch Type See description under Adding Switches above.

VPC Domain ID VPC Domain ID

Associated SWG

for Management

LAN

Reference to a connected 1G SWG

Actions Uplinks

162 Management Tool

10.19 Uplinks

The following actions are only available in Administration Mode.

10.19.1 Adding Uplinks

The action for adding an uplink opens the following dialog box.

Uplink port count Number of the ports to be added

Uplink media TX or TGBx

10.19.2 Deleting Uplinks

The action for deleting an uplink opens the following dialog box.

Uplink channel Uplink channel to be deleted

Adding Switch Ports Actions

Management Tool 163

10.19.3 Extend Uplinks

The action to extend an uplink opens the following dialog box.

Uplink channel Select an uplink channel

Uplink port count Number of the ports to be added

10.20 Adding Switch Ports

The action for adding a switch port is carried out via the Network object in the object tree

directly; no dialog box opens.

Actions Adding Volumes

164 Management Tool

10.21 Adding Volumes

The action Add volume is only available in Planning Mode.

The action for adding a volume opens the following dialog box.

NAS Device Name of the NAS system which contains the volume.

See also section 3.3.2 cDOT operating mode on page 10

Volume Name Name of the volume (max 32 signs, only letters and numbers,

have to start with a letter, volFF is not allowed).

If the volume has mount points, e.g. for SID specific sapdata, saplog, then you have to

proceed with Adding Mount Points for Volumes as described in section 10.11, like

you did it with the original volume earlier

Adding Volume Groups Actions

Management Tool 165

10.22 Adding Volume Groups

The action for adding a volume group opens the following dialog box.

Volume group name Name of the volume group

Pool name Name of the pool to which the volume group is assigned

Poolgroup name Name of the poolgroup to which the volume group is assigned

Actions Adding LUNs

166 Management Tool

10.23 Adding LUNs

The action for adding a LUN opens the following dialog box.

LUN Name Name of the LUN

Storage System Name or identification of the storage system

LUN GUID Globally unique LUN ID as assigned by the storage system

LUN ID (Storage) Storage system specific LUN ID

LUN ID (Host) LUN ID (number) as seen on the host where the LUN is

accessed

Pool name Name of the related pool

Volume group Name of the volume group

Management Tool 167

11 Abbreviations

ABAP Advanced Business Application Programming

ACC Adaptive Computing Controller

ACI Adaptive Computing Infrastructure

ACPI Advanced Configuration and Power Interface

APM Advanced Power Management

APOLC Advanced Planner & Optimizer Life Cache

CCU Console Connection Unit

cDOT Clustered Data ONTAP

CIFS Common Internet File System

DHCP Dynamic Host Configuration Protocol

DIT Domain Information Tree

ERP Enterprise Resource Planning

ESF Enhanced System Facility

EULA End User License Agreement

FA FlexFrame Autonomy

FC Fiber Channel

FF FlexFrame

FF4S FlexFrame for SAP

FFO FlexFrame Orchestrator

FSC FlexFrame Software Container, name part used for

Images and CDs/DVDs

FTP File Transfer Protocol

IP Internet Protocol

LAN Local Area Network

LDAP Lightweight Directory Access Protocol

KVM Kernel based virtual machine

LUN Logical Unit Number

MAC Media Access Control

Abbreviations

168 Management Tool

MINRA Minimal Read Ahead

NAS Network Attached Storage

NDMP Network Data Management Protocol

NFS Network File System

NIC Network Interface Card

NVRAM Non-Volatile Random Access Memory

OBP Open Boot Prom

OLAP Online Analytical Processing

OLTP On-Line Transaction Processing

ONTAP Open Network Technology for Appliance Products

OSS Open Source Software

POST Power-On Self Test

PXE Preboot Execution Environment

PY PRIMERGY

QA Quality Assurance

QS Quality of Service

RAID Redundant Array of Independent (or Inexpensive) Disks

RARP Reverse Address Resolution Protocol

RDBMS Relational Database Management System

SCS System Console Software

SAN Storage Area Network

SAP BW SAP Business Warehouse

SAPGUI SAP Graphical User Interface

SAPOSS SAP Online System Service

SID System Identifier

SLD System Landscape Directory

SLES SUSE Linux Enterprise Server

SMB Server Message Block

SMC System Management Console

Abbreviations

Management Tool 169

SNMP Simple Network Management Protocol

SWG Switch Group

SWP Switch Port

SPOC Single Point Of Control

SVM Storage virtual machine

TELNET Telecommunications Network

TFTP Trivial File Transfer Protocol

UDP User Datagram Protocol

UPS Uninterruptible Power Supply

vCC / vCN virtual Control Center / virtual Control Node

VLAN Virtual Local Area Network

VTOC Virtual Table Of Contents

WAN Wide Area Network

WAS Web Application Server

WAFL Write Anywhere File Layout

XSCF Extended System Control Facility

Management Tool 171

12 Glossary

Adaptive Computing Controller (ACC)

SAP system for monitoring and controlling SAP environments, mostly superceeded

by LVM nowadays.

Advanced Business Application Programming (ABAP)

Proprietary programming language of SAP.

Advanced Power Management

Advanced Power Management defines a layer between the hardware and the

operating system that effectively shields the programmer from hardware details.

Application Agent

A software program for monitoring and managing applications.

Application Node (AN)

A host for applications (e.g. SAP instances db, ci, agate, wgate, app etc.). This

definition includes Application Servers as well as Database Servers.

Automounter

The automounter is an NFS utility that automatically mounts directories on an NFS

client as they are needed, and unmounts them when they are no longer needed.

Autonomous Agent

Central system management and high availability software component of FlexFrame.

Blade

A special form factor for computer nodes.

BOOTPARAM

Boot time parameters of the kernel.

BRBACKUP

SAP backup and restore tools.

Client LAN

Virtual network segment within FlexFrame, used for client-server traffic.

Clustered Data ONTAP (cDOT)

One of two modes of NetApps NAS operating system ONTAP. In clustermode either

a single controller pair or multiple controller pairs are connected (clustered) via a

back-end 10GbE network; The other mode is called 7-mode; this mode will gradually

be replaced by the clustermode.

Common Internet File System (CIFS)

A protocol for the sharing of file systems (same as SMB).

Computing Node

From the SAP ACI perspective: A host that is used for applications.

Glossary

172 Management Tool

Control Agent

A software program for monitoring and managing nodes within FlexFrame.

Control LAN

Virtual network segment within FlexFrame, used for system management traffic.

Control Node (CN)

A physical computer system, controlling and monitoring the entire FlexFrame landscape and running shared services in the rack (dhcp, tftp, ldap etc.).

Control Station

A Control Node in an SAP ACI environment.

Dynamic Host Configuration Protocol (DHCP)

DHCP is a protocol for assigning dynamic IP addresses to devices on a network.

Dynamic Host Configuration Protocol server

A DHCP server provides configuration parameters specific to the DHCP client host,

required by the host to participate on the Internet.

Enterprise Resource Planning (ERP)

Enterprise Resource Planning systems are management information systems that

integrate and automate many of the business practices associated with the

operations or production aspects of a company.

Ethernet

A Local Area Network which supports data transfer rates of 10 megabits per second.

Fiber Channel (FC)

Fiber Channel is a serial computer bus intended for connecting high-speed storage

devices to computers.

Filer

Network attached storage for file systems of NetApp.

FlexFrame® (FF)

The name FlexFrame® is a generic term for both „FlexFrame

® for SAP

®“ and

„FlexFrame® Orchestrator“.

FlexFrame® Orchestrator (FFO)

This is the advancement of the Fujitsu solution FlexFrame for SAP and means a new

approach to offer enhanced functionality and features step by step and become more

and more independent from certain hardware and software components.

FlexFrame® for SAP

® (FF4S)

FlexFrame® for SAP

® is a Fujitsu solution and means a radically new architecture for

SAP environments. It exploits the latest business-critical computing technology to

deliver major cost savings for SAP customers. FlexFrame for SAP is a joint project in

which the main partners are SAP, Network Appliance, Intel and Fujitsu.

Glossary

Management Tool 173

FlexFrame internal LAN Switch

Network switches which are integral part of the FlexFrame hardware configuration

and which are automatically configured by the FlexFrame software.

Gigabit Ethernet

A Local Area Network which supports data transfer rates of 1 gigabit (1,000

megabits) per second.

HANA

SAP AG’s implementation of in-memory database technology.

Host name

The name of a node (assigned to an interface) that is resolved to a unique IP

address. One node can have multiple host names (cf. node name).

In SAP environments host names are currently limited to 13 alphanumeric characters

including the hyphen (" - "). The first character must be a letter. In the SAP

environment host names are case-sensitive.

Image

In the FlexFrame documentation, "Image" is used as a synonym for "Hard Disk

Image".

Internet Protocol Address

A unique number used by computers to refer to each other when sending information

through networks using the Internet Protocol.

Lightweight Directory Access Protocol (LDAP)

Protocol for accessing on-line directory services.

Local Area Network (LAN)

A computer network that spans a relatively small area. Most LANs are confined to a

single building or group of buildings. However, one LAN can be connected to other

LANs over any distance via telephone lines and radio waves. A system of LANs

connected in this way is called a Wide Area Network (WAN).

Local host name

The name of the node (physical computer); it can be displayed and set using the

command /bin/hostname.

Logical Unit Number (LUN)

An address for a single (SCSI) disk drive.

MAC address

Device identifier number of a Network Interface Card. In full: "media access control

address".

MaxDB

A relational database system from mySQL (formerly ADABAS and SAPDB).

Glossary

174 Management Tool

Media Access Control address

An identifier for network devices, usually unique. The MAC address is stored

physically on the device.

NAS system

Network Attached Storage of any vendor (in our context: NetApp Filer).

NDMPcopy

NDMPcopy transfers data between Filers using the Network Data Management

Protocol (NDMP).

Netboot

A boot procedure for computers where the operating system is provided via a

network instead of local disks.

Netweaver

SAP NetWeaver is the technical foundation of SAP solutions.

Network Appliance Filer

See "Filer".

Network Attached Storage (NAS)

A data storage device that is connected via a network to one or multiple computers.

Network File System (NFS)

A network protocol for network-based storage access.

Network Interface Card (NIC)

A hardware device that allows computer communication via networks.

Node

A physical computer system controlled by an OS.

Node name

The name of a physical node as returned by the command uname -n. Each node

name within a FlexFrame environment must be unique.

Non-Volatile Random Access Memory

A type of memory that retains its contents when the power is turned off.

On-Line Analytical Processing (OLAP)

The use of analytical informationssystems via computer networks

On-Line Transaction Processing (OLTP)

Transaction processing via computer networks.

OpenLDAP

An Open Source LDAP Service Implementation.

Open Network Technology for Appliance Products (ONTAP)

The operating system of Network Appliance Filers.

Glossary

Management Tool 175

Open Source Software

Software that is distributed free of charge under an open source license, such as the

GNU Public License.

Oracle RAC

A cluster database by Oracle Corporation.

Physical host

Name of a physical computer system (node).

Power-On Self Test

Part of a computer's boot process; automatic testing of diverse hardware

components.

Preboot Execution Environment (PXE)

An environment that allows a computer to boot from a network resource without

having a local operating system installed.

PRIMERGY

Fujitsu's i386-based server product line.

Red Hat Enterprise Linux (RHEL)

Linux distribution by Red Hat, Inc., targeting business customers.

Reverse Address Resolution Protocol (RARP)

A protocol allowing resolution of an IP address corresponding to a MAC address.

SAP Service

In FlexFrame: SAP Service and DB Services.

SAP service script

An administration script for starting and stopping an SAP application on a virtual host.

SAP Solution Manager

Service portal for the implementation, operation and optimization of an SAP solution.

SAPLogon

Front-end software for SAPGUI.

SAPRouter

Router for SAP services like SAPGUI or SAPTELNET.

Server

A physical host (hardware), same as node.

Service

A software program providing functions to clients.

Service type

The type of an application or service (db, ci, app, agate, wgate etc.).

Glossary

176 Management Tool

Single Point of Control

In FlexFrame: One user interface to control a whole FlexFrame environment.

Storage LAN

A virtual LAN segment within a FlexFrame environment, carrying the traffic to NAS

systems.

SUSE Linux Enterprise Server (SLES)

A Linux distribution by Novell, specializing in server installations.

Telecommunications Network

A terminal emulation program for TCP/IP networks such as the Internet.

Trivial File Transfer Protocol (TFTP)

A simple form of the File Transfer Protocol (FTP). TFTP uses the User Datagram

Protocol (UDP) and provides no security features. It is often used by servers to boot

diskless workstations, X-terminals, and routers.

TFTP server

A simple FTP implementation.

Virtual host

The name of the virtual host on which an application runs; it is assigned to a physical

node when an application is started.

Virtual Control Center

The Control Center of FlexFrame can either consist of physical Control Nodes or of

virtual Control Nodes. In case of a virtual Control Center both virtual machines are

hosted on different physical PRIMERGY servers that run SUSE KVM as hypervisor.

Virtual Local Area Network (VLAN)

A VLAN is a logically segmented network mapped over physical hardware according

to the IEEE 802.1q standard.

Virtualization

Virtualization means the separation of hardware and processes. In a virtualized

environment (FlexFrame), a process can be moved between hardware nodes while

staying transparent to the user and application.

Management Tool 177

13 Index

A

abbreviations 167

actions 113

add application node 121

add blade server chassis 125

add data NIC 126

add external connectivity 126

add group 139

add Hypervisor Nodes 119

add LAN 127

add LUN 165

add mount 128

add NAS 129

add Network 138

add pool 140

add SAP service 142

add switch 159

add switch group 160

add switch port 162

add uplink 161

add volume 163

add volume group 164

delete uplink 161

extend uplink 162

overview 114, 118

application node

add 121

application nodes table 86

assign blade server to chassis 125

B

blade server

assign to chassis 125

blade server chassis

add 125

BOBJ 148

C

chassis object 74

chassis table 101

Classic 143

CMS 149

configuration

create 27, 31

edit 42

modify 39

print 42

save 40

validate 47

control center

settings 57

control center object 57

Index

178 Management Tool

controlling table 83

create new configuration 27

D

data NIC

add 126

document history 3

E

error logging 25

ESX parameters 72

execution area 107

external connections 4

external connectivity

add 126

external connectivity table 98

F

failover concept for AN 81

FlexFrame object 56

functions

IP addresses

reset all 54

new configuration 32

open configuration file 38

open LDAP connection 36

open Local LDAP connection 38

perform wiring 49, 50

print 42

save 40

save for installation 41

validate configuration 47

G

general information 79

global connectivity object 75

global connectivity, generate 50

glossary 171

group

add 139

H

HANA 155

HANA-MN 155

host names 7

host parts

generate 53

generate automatically 54

generate manually 54

Hypervisor Nodes

add 119

Hypervisor nodes object 71

Hypervisor Nodes table 102

I

installation

save 41

IP addresses

reset 54

IPs 105

L

LAN

add 127

LC 147

Index

Management Tool 179

LUN

add 165

M

Management Tool

exit 21

screen layout 22

starting 20

MDM 151

menu functions 31

edit 42

file 31

mode 54

tools 47

mount

add 128

N

naming information 3

NAS

add 129

NAS storage table) 89

Network

add 138

network concept 3

network object 59

network settings 60

network wiring plan, generate 49

Networks table) 82

new configuration 32

notational conventions 2

NTP master server 58

O

object tree 55

open configuration file 38

open LDAP connection 36

open Local LDAP connection 38

P

pool

add 140

pool / SID mount 91

pool mount 50, 92

pools object 64

pools table 80

R

related documents 3

R-HANA 157

R-HANA-MN 157

S

SAP service

add 142

BOBJ 148

Classic 143

CMS 149

HANA 155

HANA-MN 155

LC 147

MDM 151

R-HANA 157

R-HANA-MN 157

Index

180 Management Tool

SMD 152

TRX 150

WD 154

SAP services 94

SID mount 50, 92

SMD 152

SNMP community 6

storage object 62

sub-object tree 68

switch

add 159

switch group

add 160

switch group tree view 61

switch port

add 162

switch ports 98

T

tagged VLAN 98

TRX 150

U

uplink

add 161

delete 161

extend 162

users groups services table 97

V

vCenter 73

view area 77

virtual host names) 95

virtual IP addresses 95

VLAN

host names 7

VLAN IDs 98

volume

add 163

volume group

add 164

volumes 91

volumes table 91

W

WD 154

wiring 103