Version 5 - Fujitsu Technology...
148
FlexFrame™ for SAP ® Version 5.1A Management Tool Edition February 2012 Document Version 1.1
Transcript of Version 5 - Fujitsu Technology...
FlexFrame™ for SAP®
Version 5.1A
Management Tool
Edition February 2012 Document Version 1.1
Fujitsu Limited
© Copyright Fujitsu Technology Solutions 2011
FlexFrame™ and PRIMERGY™ are trademarks or registered trademarks of Fujitsu Limited in
Japan and other countries.
SAP® and NetWeaver™ are trademarks or registered trademarks of SAP AG in Germany and
in several other countries
Linux® is a registered trademark of Linus Torvalds
SUSE® Linux is a registered trademark of Novell, Inc., 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.
EMC®, CLARiiON
®, Symmetrix
® and Celerra™ are trademarks or registered trademarks of
EMC Corporation in the United States 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
2 Network Concept ............................................................................................. 5 2.1 Brief Abstract of the Network Concept. ............................................................. 5 2.2 FlexFrame Network External Connections ........................................................ 5 2.2.1 External Connectivity ......................................................................................... 5 2.2.2 Global Connectivity - Client LAN Connection .................................................... 6 2.2.3 Core Switch Connectivity for Devices ................................................................ 6 2.2.4 Uplinks for Switch Groups ................................................................................. 7 2.3 Define SNMP Communities ............................................................................... 8 2.4 Host Names....................................................................................................... 8
3 Working with the Management Tool .............................................................. 9 3.1 Supported Administration Commands ............................................................... 9 3.2 Operating Mode Differences............................................................................ 12 3.2.1 Features Overview .......................................................................................... 12 3.2.2 Differences in Performing Actions ................................................................... 14 3.3 Starting the Management Tool ........................................................................ 16 3.4 Exit the Management Tool .............................................................................. 17 3.5 Screen Layout of the Management Tool ......................................................... 18 3.6 Error Logging ................................................................................................... 21
4 Brief Instruction for Creating a New FlexFrame Configuration ................. 23
5 Menu Functions ............................................................................................. 25 5.1 "File" Menu ...................................................................................................... 25 5.1.1 Creating a New Configuration ......................................................................... 25 5.1.2 Modifying an Existing Configuration ................................................................ 32 5.1.3 Saving a Configuration .................................................................................... 32 5.1.4 Saving for Installation ...................................................................................... 33 5.1.5 Printing a Configuration ................................................................................... 35 5.2 "Edit" Menu ...................................................................................................... 35 5.3 "Tools" Menu ................................................................................................... 36 5.3.1 Validating a Configuration ............................................................................... 36 5.3.2 Erasing the LDAP and XML Validation Errors ................................................. 37 5.3.3 Generating a Network Wiring Plan .................................................................. 37 5.3.4 Generating Global Connectivity ....................................................................... 39 5.3.5 Generating Host Parts of IP Addresses ........................................................... 41 5.4 "Mode" Menu ................................................................................................... 42
Contents
Management Tool
6 Object Tree ..................................................................................................... 43 6.1 General Features ............................................................................................. 43 6.2 "FlexFrame" Object.......................................................................................... 44 6.3 "Control Center" Object ................................................................................... 45 6.4 "Network" Object ............................................................................................. 47 6.5 "Storage" Object .............................................................................................. 50 6.6 "Pools" Object .................................................................................................. 51 6.8 "ESX Servers" Object ...................................................................................... 55 6.9 "Chassis" Object .............................................................................................. 58 6.10 "Global Connectivity" Object ............................................................................ 59
7 View Area ....................................................................................................... 61 7.1 General Features ............................................................................................. 61 7.2 "General Information" ...................................................................................... 63 7.3 "Pools" ............................................................................................................. 64 7.4 "Controlling" ..................................................................................................... 66 7.5 "Application Nodes" ......................................................................................... 68 7.6 "NAS Storage" ................................................................................................. 70 7.7 "Volumes" and "Pool / SID Mount"................................................................... 71 7.7.1 "Volumes" ........................................................................................................ 72 7.7.2 "Pool / SID Mount" ........................................................................................... 73 7.8 "SAP Services" ................................................................................................ 73 7.9 "Users Groups Services" ................................................................................. 77 7.10 "External Connectivity" .................................................................................... 78 7.11 Chassis ............................................................................................................ 80 7.12 Switch Blades .................................................................................................. 81 7.13 "ESX Servers" ................................................................................................. 81 7.14 "Wiring" ............................................................................................................ 83
8 Execution Area .............................................................................................. 85 8.1 General Overview ............................................................................................ 85 8.2 Administration Commands Overview ............................................................... 87 8.3 Validation ......................................................................................................... 88
9 Actions ........................................................................................................... 91 9.1 Actions Overview ............................................................................................. 92 9.1.1 Actions Overview Table ................................................................................... 92 9.1.2 Other administrative commands available in Administration Mode .................. 95 9.2 Context Menu of Selected Objects .................................................................. 96 9.3 Adding ESX Server .......................................................................................... 97 9.4 Adding Complete Configuration (ESX) ............................................................ 99 9.5 Adding Application Nodes................................................................................ 99 9.6 Adding New AN (Create an AN Image) ......................................................... 102 9.7 Adding Blade Server Chassis ........................................................................ 103 9.8 Adding Control Stations ................................................................................. 104
Contents
Management Tool 3
9.9 Adding Data Movers ...................................................................................... 105 9.10 Adding Data NICs .......................................................................................... 106 9.11 Adding External Connectivities (Pool-specific) .............................................. 106 9.12 Adding LAN Interfaces .................................................................................. 108 9.13 Adding Mount Points for Volumes ................................................................. 108 9.14 Adding NAS Systems .................................................................................... 109 9.14.1 Celerra SRDF-NAS Active/Passive Configuration ......................................... 111 9.15 Adding Pool Groups ...................................................................................... 111 9.16 Adding Pools ................................................................................................. 112 9.17 Adding SAP Services .................................................................................... 113 9.17.1 Classic ........................................................................................................... 114 9.17.2 LiveCache Service (LC) ................................................................................ 115 9.17.3 Business Objects Enterprise Servce (BOBJ)................................................. 116 9.17.4 Content Management Server Service Type (CMS) ....................................... 117 9.17.5 TRX ............................................................................................................... 118 9.17.6 Master Data Management Service Type (MDM) ........................................... 119 9.17.7 Solution Manager Diagnostics Service Type (SMD) ...................................... 120 9.18 Adding Switches ............................................................................................ 121 9.19 Adding Switch Groups ................................................................................... 122 9.20 Uplinks .......................................................................................................... 123 9.20.1 Adding Uplinks .............................................................................................. 123 9.20.2 Deleting Uplinks ............................................................................................ 123 9.20.3 Extend Uplinks .............................................................................................. 124 9.21 Adding Switch Ports ...................................................................................... 124 9.22 Adding Volumes ............................................................................................ 125
10 Abbreviations .............................................................................................. 127
11 Glossary ....................................................................................................... 131
12 Index ............................................................................................................. 137
Management Tool 1
1 Introduction
The FlexFrame™ for SAP 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 for SAP 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 (new as of FlexFrame v5.1!):
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 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 for SAP 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 or EMC NAS Storage
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 2011-10-19
1.1 Updates in chapter 4 2011-12-12
1.3 Related Documents
FlexFrame™ for SAP® – Administration and Operation
FlexFrame™ for SAP® – HW Characteristics Quickguides
FlexFrame™ for SAP® – Installation ACC 7.3
FlexFrame™ for SAP® – Installation Guide for SAP Solutions
FlexFrame™ for SAP® – Installation of a FlexFrame Environment
FlexFrame™ for SAP® – Management Tool
FlexFrame™ for SAP
® – myAMC.FA_Agents Installation and Administration
FlexFrame™ for SAP
® – myAMC.FA_Messenger Installation and Administration
FlexFrame™ for SAP
® – myAMC.FA_LogAgent Installation and Administration
FlexFrame™ for SAP® – Network Design and Configuration Guide
FlexFrame™ for SAP® – Security Guide
FlexFrame™ for SAP® – Technical White Paper
FlexFrame™ for SAP® – Upgrading FlexFrame 4.2B or 5.0A to 5.1A
ServerView Documentation
SUSE Linux Enterprise Server Documentation
Management Tool 5
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 "Working with the Management Tool" 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. 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.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 Ctrl LAN. External
Connectivity exists in a pool scope.
A more detailed description of this feature is given in section 7.10 "External Connectivity"
on page 78
Network Concept FlexFrame Network External Connections
6 Management Tool
2.2.2 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 6.10 "Global Connectivity"
Object on page 59.
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 6.4 "Network" Object on page 47). 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 you add portlist objects (right-click on the “Core or Direct”
object). As children of these portlist objects you can add different kind 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”
FlexFrame Network External Connections Network Concept
Management Tool 7
2.2.4 Uplinks for Switch Groups
Automatic creation of uplinks is done by calling the wiring menu function (see section
7.14 "Wiring" on page 83) after having set the networking properties (see Miscellaneous
Network Settings on page 48).
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 “switch interconnect” property of the SWP has to be set
to “true”. 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.
If you want to configure more than one uplink for a switch group, you have
to use a different portlist of “Core or Direct” for each uplink channel.
“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.
Network Concept Define SNMP Communities
8 Management Tool
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 6.3 "Control Center"
Object on page 45)
● 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.
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
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 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.
3.1 Supported Administration Commands
1. 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
2. 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
3. ff_sid_adm.pl --op add/del --pool <poolname> --sid <sidname> …
Accessible via:
Working with the Management Tool Supported Administration Commands
10 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
4. 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>
5. ff_sid_mnt_adm.pl --op add --sid <sidName> --sapdata <volume>
--saplog<volume> …
Is also generated when adding a new SID with sapdta and saplog volumes for this
SID.
Only as Administration Command available, there have to be sapdata and saplog
volumes for this SID, always executable.
Accessible via:
● Context menu of: /FlexFrame/Pools/<poolname>/SIDs/<sidName>
6. 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
7. ff_new_an.sh -n <name>…
Only as Administration Command available.
Accessible via:
● Context menu of: /FlexFrame/Pools/<poolname>/Groups/<groupName>/Servers/<se
rverName>
Supported Administration Commands Working with the Management Tool
Management Tool 11
8. 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
9. ff_esx_adm.pl --op add/rem --name <esxServerName> --type
<type> …
Accessible via:
● Add: Context menu of: /FlexFrame/ESX Servers/Server List
● Delete: Context menu of: /FlexFrame/ESX Servers/Server List/<esxServerName>
● Add / Delete ESX Server button in the ESX Servers table
10. ff_esx_adm.pl --op complete-config –name <esxServerName>
Only as Administration Command available
Accessible via:
● Context menu of:
/FlexFrame/ESX Servers/Server List /<esxServerName>
11. 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
12. 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>
● Celerra DM: Context menu of:
/…/NAS/<nasName>/<dmName>/Storage LANs
Working with the Management Tool Operating Mode Differences
12 Management Tool
● Celerra DM: Context menu of:
/…/NAS/<nasName>/<dmName>/Storage LANs/<stlanName>
13. 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
14. 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>
15. ff_swgroup_adm.pl --op add-uplink/rem-uplink/ext-uplink …
Only as Administration Command available.
Accessible via:
● Context menu of:
/FlexFrame/Network/Switch Groups/<swgName>
3.2 Operating Mode Differences
3.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 9.1 Actions
Overview on page 92.
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.
Operating Mode Differences Working with the Management Tool
Management Tool 13
Menu bar Submenu 1 Submenu 2 Planning
Mode
Administration
Mode
File New
Configuration
x o
Open LDAP Connection x o
Configuration File x 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
Esx Server x x
Chassis x x
NAS x x
Volume x o
Mount x o
SAP Services x x
External Connectivity x o
Tools Validate
Configuration
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
Working with the Management Tool Operating Mode Differences
14 Management Tool
Menu bar Submenu 1 Submenu 2 Planning
Mode
Administration
Mode
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
3.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.
Operating Mode Differences Working with the Management Tool
Management Tool 15
Example:
In this example the pool "beck-p2-mnt" should be deleted. The pool and all subjects 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 section 8 Execution Area on page 85.
Working with the Management Tool Starting the Management Tool
16 Management Tool
3.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_globals.xml
● ff_hardware.xml
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
SUN Java SE 6 is required.
The screen of the Management Tool opens. For an explanation of the different areas see
section 3.5 Screen Layout of the Management Tool on page 18.
At the moment the Management Tool does not possess a recovery
function (Redo/Undo)!
If you delete something by mistake, you can repair it 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.
Exit the Management Tool Working with the Management Tool
Management Tool 17
Attention when working in Administration Mode!
In Administration Mode you have direct access to the FlexFrame environment.
3.4 Exit the Management Tool
You exit the Management Tool by selecting Exit in the File menu.
Working with the Management Tool Screen Layout of the Management Tool
18 Management Tool
3.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.
Screen Layout of the Management Tool Working with the Management Tool
Management Tool 19
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 7.1 General Features on page 61.
In all views you will find editable fields or dropdown combo boxes, where you
can change the values of the related properties.
Working with the Management Tool Screen Layout of the Management Tool
20 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.
Error Logging Working with the Management Tool
Management Tool 21
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.
3.6 Error Logging
ManagementToolLog.txt
In case of unexpected behavior of the Management Tool, information of the available
ff_hardware.xml 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 23
4 Brief Instruction for Creating a New FlexFrame Configuration
This section 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 3.3 Starting the Management Tool
on page 16), select New Configuration in the File menu (see section 5.1.1
Creating a New Configuration on page 25).
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 9.18 Adding Switches on page 121).
3. Add one or more blade server chassis (see section 9.7 Adding Blade Server Chassis
on page 103).
4. Add one or more ESX servers (see section 9.3 Adding ESX Server on page 97).
5. Add one or more application nodes (rack servers, blade servers, VMs, see section
9.5 Adding Application Nodes on page 99)
6. Add SAP services (see section 9.17 Adding SAP Services on page 113).
7. Generate the IP addresses (see section 5.3.5 Generating Host Parts of IP Addresses
on page 41).
8. Generate the network wiring plan (see section 5.3.3 Generating a Network Wiring
Plan on page 37).
9. Validate the configuration (see section 5.3.1 Validating a Configuration on page 36).
In case of errors you have to correct them and validate the configuration again.
10. Save the valid configuration (see section 5.1.3 Saving a Configuration on page 32).
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 5.1.3 Saving a
Configuration on page 32).
Brief Instruction for Creating a New FlexFrame Configuration Error Logging
24 Management Tool
12. Optional activities:
● Add other switch groups to the desired configuration (see section 9.19 Adding
Switch Groups on page 122).
● Add other pools to the desired configuration (see section 9.16 Adding Pools on
page 112).
● Add other groups to the existing pool(s) (see section 9.15 Adding Pool Groups
on page 111).
● Add pool-specific external connectivities (see section 9.11 Adding External
Connectivities (Pool-specific) on page 106).
● Add other NAS storages (see section 9.14 Adding NAS Systems on page 109).
● Add volumes to the NAS storage(s) (see section 9.22 Adding Volumes on page
125).
● Add mount points for the added volumes (see section 9.13 Adding Mount
Points for Volumeson page 108).
● Add global connectivities either manually or automatically with optional
additional Client LANs (see section 5.3.4 Generating Global Connectivity on
page 39).
Optional activities make it necessary that you perform steps 7 to 10 again.
Optional activities may also be performed before step 7.
The validation of a complete FlexFrame configuration is done by using the
Validate Configuration function (see section 5.3.1 Validating a Configuration on
page 36).
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.
"File" Menu Menu Functions
Management Tool 25
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.
5 Menu Functions
5.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.
5.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 5.1.1.1 "New
Configuration" Function on page 26.
Menu Functions "File" Menu
26 Management Tool
● Open an existing configuration from LDAP via the File menu and save it as an XML
file, see section 5.1.1.2"Open LDAP Connection" Function on page 29.
● Open an existing configuration via the File menu, modify and save it under a
different name, see section 5.1.1.3 "Open Configuration File" Function on page 31.
5.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 27
First Pool Name The name of the first pool.
The name must start with a letter and may only contain
numbers, letters and "-".
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.
The name must start with a letter and may only contain
numbers, letters or "-".
Menu Functions "File" Menu
28 Management Tool
First Switch Group Name The name of the first switch group.
The name must start with a letter and may only contain
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.
NAS System Pull down menu with valid NAS types, name of the NAS
system and number of NICs (2-8).
After you have competed 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.
"File" Menu Menu Functions
Management Tool 29
5.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 5.3.1 Validating a Configuration on page 36).
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.
Menu Functions "File" Menu
30 Management Tool
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.
"File" Menu Menu Functions
Management Tool 31
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.
5.1.1.3 "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 5.1.2 Modifying an Existing Configuration on page 32.
The following dialog box is displayed in which you can select a configuration (XML file).
Menu Functions "File" Menu
32 Management Tool
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.
5.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.
5.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.
"File" Menu Menu Functions
Management Tool 33
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.
5.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.
Menu Functions "File" Menu
34 Management Tool
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.
"Edit" Menu Menu Functions
Management Tool 35
5.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.
5.2 "Edit" Menu
Not all functions are available in both operating modes. A detailed overview of the
differences is provided in section 3.2 Operating Mode Differences on page 12.
Planning Mode Administration Mode
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 section
7 View Area on page 61.
Menu Functions "Tools" Menu
36 Management Tool
5.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 current configuration file (Planning Mode) or reload the real FlexFrame
environment settings (Administration Mode) respectively.
5.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. You can
reduce the output by activating the Show only errors and warnings checkbox.
"Tools" Menu Menu Functions
Management Tool 37
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.
5.3.2 Erasing the LDAP and XML Validation Errors
With the Validate Configuration function yon can check whether the current
configuration is valid and may be used by the installation script.
The Validate Configuration function displays the check results, i.e. the errors
coming up while reading the LDAP or XML configuration.
This error list is saved as long as the function Erase LDAP / XML Read Validation
is selected.
To delete the error list, select Erase LDAP / XML Read Validation. The error list is
deleted; no dialog is displayed.
5.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 83).
Menu Functions "Tools" Menu
38 Management Tool
5.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.
5.3.3.2 Manual Generation
To modify a network wiring plan manually, navigate to a switch port 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.
Modification of a network wiring plan manually is only available in Planning
Mode.
"Tools" Menu Menu Functions
Management Tool 39
5.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 7.10 "External Connectivity" on page 78.
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 55)
and under the Wiring tab in the FlexFrame object view (see 7.14 "Wiring" on page 83).
5.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 6.4"Network" Object on page 47):
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.
Menu Functions "Tools" Menu
40 Management Tool
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.
5.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:
"Tools" Menu Menu Functions
Management Tool 41
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):
5.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
42 Management Tool
5.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.
5.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.
5.4 "Mode" Menu
Select the operating mode in the "Mode" menu. Details concerning the two operating
modes are described in section 3.2 Operating Mode Differences on page 12.
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 43
6 Object Tree
The object tree is an abstraction of the FlexFrame reality.
6.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 9.1 Actions Overview on page 91 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:
● 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 6.2 to 6.10.
Object Tree "FlexFrame" Object
44 Management Tool
6.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 45
6.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 (FA Control Agents).
The figure on the left side shows the Control Center
object as an example.
By selecting this object, the Control Node part of the
Controlling table is displayed (see 7.4 "Controlling" on
page 66).
The upper split pane shows a list of properties necessary for
the Control Center (see Miscellaneous Control Center
settings below).
The lower split pane shows a table where more properties of
the Control Center are shown in a similar way as properties
of NAS systems or Application Nodes.
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.
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.
Object Tree "Control Center" Object
46 Management Tool
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 8.
Allow Dynamic LUN Masking With this configuration dynamic LUN masking is
allowed (true) or not (false).
"Network" Object Object Tree
Management Tool 47
6.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, the icon
of the switch port is marked green. The relation then
also appears in the wiring view.
By selecting this object, the switch group part of the
Controlling view is displayed in the lower split
pane (see 7.4 "Controlling" on page 66).
The upper split pane shows miscellaneous settings
concerning the network (see Miscellaneous Network
settings below).
Right-click on Switches to add switches, see section
9.18, Adding Switches on page 121.
For every Switch Group a tree view is available
displaying the Path, Name and Value for the
corresponding switch group.
Object Tree "Network" Object
48 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 SWP1 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 SWGs2 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 LANs3 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).
1 corresponds to former „Separate VLANs to corporate LAN“
2 corresponds to former „Distribute corporate LAN ports to different switch groups”
3 corresponds to former “Use Fiber Optic port to corporate LAN“
"Network" Object Object Tree
Management Tool 49
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
Object Tree "Storage" Object
50 Management Tool
6.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 figure on the left side shows 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 7.6 "NAS Storage" page 70).
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.
"Pools" Object Object Tree
Management Tool 51
6.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 pools table is
displayed (see 7.3 "Pools" on page 64).
By selecting the External Connectivity object the
pool-specific External Connectivity table is
displayed (see 7.10 "External Connectivity" on page 78).
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.
For every Pool a tree view is available displaying the
Path, Name and Value for the corresponding Pool.
Object Tree "Pools" Object
52 Management Tool
By selecting the SIDs object the SIDs object view is
displayed (see page 7.8 "SAP Services" on page 73).
In the upper split pane of the view you can manage the
pool-specific UIDs and GIDs that might be necessary
when installing and running the SAP services in the
given pool. During installation the UIDs or GIDs given
here are only used, when a SAP version or DB version
that makes use of this user or group is actually installed.
If there is no UID or GID given here for a user or a group
actually needed for a SAP or DB installation, then a
default value will be used. When migrating an existing
SAP Installation to FlexFrame, the existing UIDs and
GIDs should be used here.
In the lower part of the split pane the SAP Services
table is displayed. Only the SAP services belonging to
this pool are displayed.
"Pools" Object Object Tree
Management Tool 53
By selecting the Users Groups Services object
the three corresponding sub-objects are displayed.
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 7.9, "Users Groups
Services" on page 77.
If you click on a specific user, group or service the
properties are displayed in the view area.
To delete a user, group or service click with the
right-mouse tab and select Delete.
Object Tree
54 Management Tool
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 7.5 "Application
Nodes" on page 68) 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 6.9 "Chassis"
Object on page 58 ). The Chassis object view is the
Chassis table.
"ESX Servers" Object Object Tree
Management Tool 55
6.8 "ESX Servers" Object
Instead of being used directly as Application Nodes, PRIMERGY servers may also be
used in FlexFrame as ESXi servers. An ESXi server can host a number of virtual ma-
chines 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 5.0, 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.
When starting a new FlexFrame configuration, the ESX Servers object is not yet present
in the object tree. It is created only after adding a first ESX server, for example by using
the Add ESX Server button of the ESX Server table that can be activated via the ESX
Servers tab of the FlexFrame root object view.
Object Tree "ESX Servers" Object
56 Management Tool
When selecting the Esx Servers object, ESX
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 ESX Server via the Server
List object with a right mouse-click. A dialog
box opens and you can add an ESX server in
exact the same way as you add an Application
node to a Server List object inside a Group
object.
If the ESX server 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
6.9 "Chassis" Object on page 58.
For every ESX Server a tree view is available
displaying the Path, Name and Value for the
corresponding ESX server.
ESX related global FlexFrame parameters
FlexFrame system code for
ESX and VM
A numeric value between 0 and 63 used to
generate MAC addresses for FlexFrame virtual
machines and to build names of some ESX
related resources such as port groups and
datastores.
Use a different system code for each
FlexFrame system in your environment.
"ESX Servers" Object Object Tree
Management Tool 57
vCenter Server usage
If FlexFrame ESX servers 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
58 Management Tool
6.9 "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 ESX Severs 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 59
6.10 "Global Connectivity" Object
In this object the global network connections are managed. For further information see
section Fehler! Verweisquelle konnte nicht gefunden werden. on page Fehler!
Textmarke nicht definiert..
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 61
7 View Area
7.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.
● 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).
● 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.
View Area General Features
62 Management Tool
● 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 6.1 General Features on
page 43.
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 63
7.2 "General Information"
Displays general information related to the Management Tool.
Customer Name of the customer.
Only ASCII characters are allowed.
Project Name Name of the customer project.
Only ASCII characters are allowed.
Contact Person Information to the contact person at the customer (e.g. name,
phone number, email address).
Only ASCII characters are allowed.
Origin of Data Original database of the configuration
Comments Any comments (not stored in the configuration file).
Only ASCII characters are allowed.
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"
64 Management Tool
7.3 "Pools"
The pools table is shown here. All existing pools with their current LAN parameters as
well as the DNS information are displayed.
● You can see a pools table also via the Pools object in the object tree (see 6.6"Pools"
Object on page 51).
● 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:
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.
"Pools" View Area
Management Tool 65
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
DNS Domain Name DNS domain name for the pool (alphanumeric, "." and "-" are
allowed)
DNS Server DNS server for the pool (IPv4 format)
● With the actions Add Pool and Delete Pool you can add or delete pools.
● 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.
View Area "Controlling"
66 Management Tool
Failover concept for Application Nodes related to FA Agents:
If a node in a pool group fails and no adequate spare node is found in the group of the
failed node, the FA 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.
7.4 "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 6.3 "Control Center" Object on page 45) and via the
Network object concerning the switch group entries (see 6.4 "Network" Object on
page 47) 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.
"Controlling" View Area
Management Tool 67
Host Name Name of the component
Type Type of the component
Swg Associated switch group
Pool Associated pool
Host Common host part of all VLAN sements for the component in the
relevant row
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 9.19, Adding Switch Groups on page 122.
● 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"
68 Management Tool
7.5 "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 6.6 "Pools" Object on page 51),
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_nam
e>:
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 69
Host Name Name of the Application Node
Type Type of the Application Node
Swg/Esx Server Associated switch group/ESX server
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
Host Name / IP Host name and IP address of the individual LAN
● 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 ESX you can change an Application Node to an Esx
server.
The action Change to ESX is only available in Planning Mode.
● In the Swg/Esx Server, Pool, Group and OS columns you can change the
association of a switch group or ESX server, 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.
● 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.
These changes are only available in Planning Mode.
View Area "NAS Storage"
70 Management Tool
7.6 "NAS Storage"
In the NAS Storage table all existing physical 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 6.5 "Storage" Object on page 50).
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 of the NAS system
(NS-Type = EMC NAS, FAS… = NetApp Filer)
Component Component of the NAS system (only for NS-Type NAS)
(Cs = Control station, DM = Data mover)
Standby local This data mover is standby for all data movers in the same NS-
"Volumes" and "Pool / SID Mount" View Area
Management Tool 71
Type NAS storage device (true) or not (false).
Standby remote This data mover is standby for a remote partner (true) or not
(false). The remote partner can be specified with NS-Type NAS
storage devices via the remote partner link. If the remote partner
fails, the standby data mover takes over all tasks.
Partner Name of the remote partner of this NAS system, if set in the
Storage object under Storage – NAS/<NAS_device>
Swg Associated switch group
Pool Associated pool
Host Name / IP Host name and IP address of the individual LAN
● With the actions Add NAS and Delete NAS you can add or delete NAS systems.
● 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.
These changes are only available in Planning Mode.
7.7 "Volumes" and "Pool / SID Mount"
For a description of the Volumes table, see section 7.7.1 "Volumes" on page 72.
For a description of the Pool /SID mount, see section 7.7.2 "Pool / SID Mount" on
page 73.
View Area "Volumes" and "Pool / SID Mount"
72 Management Tool
7.7.1 "Volumes"
In this view all existing volumes are displayed with their current parameters.
● You can open this view also object dependent via the
Storage/NAS/<NAS_name>/[<data_mover>]
object in the object tree (see 6.5 "Storage" Object on page 50).
Name Name of the volume
Host Name Name of the NAS system
Component Component of the NAS system on which the volume lies
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 9.22, Adding Volumes on page 125.
● 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.
"SAP Services" View Area
Management Tool 73
7.7.2 "Pool / SID 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 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.
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 Name of the associated pool
SID SID from SAP Services
VolFF /
Sapdata /
Saplog
Path of the related volume
● With the actions Add Mount and Delete Mount you can add or delete mount points of
volumes, see section 9.13, Adding Mount Points for Volumes on page 108.
The actions Add Mount and Delete Mount are only available in Planning
Mode.
7.8 "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 51).
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.
View Area "SAP Services"
74 Management Tool
SID ID of the SAP system
(up to three characters, in accordance with SAP rules)
Inst No Instance number of a SAP system
(unique across all SIDs per pool)
Service Type (see also "Virtual host names and virtual IP addresses" below)
DB Type / SAP Vers. Database type and SAP version of the service type
"SAP Services" View Area
Management Tool 75
UIDs / GIDs SID specific user and group ID
Pool Name of the associated pool
Host Common host part of all VLAN sements for the component in
the relevant row
Virtual Host Name Virtual host name of the individual LAN
Virtual IP Virtual IP address of the individual LAN
It is automatically ensured that precisely one database instance and one central
instance are contained for each SID.
The IP addresses on the Client and Server LANs are formed from the pool’s
network IP and the host number, taking the netmask into consideration.
● With the actions Add SAP Service and Delete SAP Service you can add or
delete SAP systems, see section 9.17, Adding SAP Services on page 113.
● 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.
Virtual host names are formed as follows:
<service_type>[<ID>]<SID>[<-LAN_type>]
service_type db
ci
app
ascs
scs
jc
j
lc
ers
database instance
central instance (ABAP)
application instance (ABAP)
ABAP SAP central services instance
JAVA SAP central services instance
JAVA central instance
JAVA application instance
LiveCache instance
Enqueue Replication Service instance
View Area "SAP Services"
76 Management Tool
mdis
mds
mdss
trx
cms
bobj
smd
MDM Import Server Instance
MDM Server instance
MDM Syndication Server instance
TREX Application Server instance
Content Management Service instance
Busines Objects Enterprise instance
Solution Manager Diagnostic agent
ID Instance number from 00 to 96 (except 2, 25, 43, 72 and 89) 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 in version ≥4.2A of the
FlexFrame solution. Some components rely on this rule.
"Users Groups Services" View Area
Management Tool 77
7.9 "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.
View Area "External Connectivity"
78 Management Tool
7.10 "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 5.3.4 Generating Global Connectivity on page 39.
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!
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 6.6
"Pools" Object on page 51).
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.
"External Connectivity" View Area
Management Tool 79
Host Name Host name of the external device
Swg Associated switch group
Pool Associated pool
NICs Number of NICs
Host Common host part of all VLAN segments for the component in
the relevant row
Host Name / IP Host name and IP address of the individual LAN
● With the actions Add External Connectivity and Delete External
Connectivity you can add or delete a connection (see section 9.11, Adding
External Connectivities (Pool-specific) on page 106).
● 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.
View Area Chassis
80 Management Tool
7.11 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.
Switch Blades View Area
Management Tool 81
7.12 Switch Blades
The view area of a switch blade shows the properties of the switch blade in the upper half
of a split pane and the same information as in the chassis table for this switch blade in
the lower half of the split pane.
Ensure to choose user and password of the switch blade according to the
restrictions in the “User Interface Description” of this switch blade.
7.13 "ESX Servers"
In this table, all ESX servers are displayed with their current parameters. You can also
add an ESX server, delete an ESX server or change an ESX server to an Application
Node.
The action Change to AN is only available in Planning Mode.
View Area "ESX Servers"
82 Management Tool
"Wiring" View Area
Management Tool 83
7.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>
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.
Management Tool 85
8 Execution Area
8.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™ for
SAP® – 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 General Overview
86 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.
Administration Commands Overview Execution Area
Management Tool 87
8.2 Administration Commands 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.
Command Overview
The following table gives an overview of all administration commands and how the
commands can be created.
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>
ESX Servers ff_esx_adm.pl ESX Servers
--
FlexFrame/ESX Servers/
Server List
FlexFrame/ESX Servers/
Server List/
<esxServerName>
Blade server chassis ff_bx_cabinet_adm.pl Chassis FlexFrame/Chassis
Control stations and
Data movers
ff_nas_adm.pl FlexFrame/Storage/NAS/
<emc_nas>
Execution Area Validation
88 Management Tool
You can add/delete Administration command Creation via button
in the table named:
Creation via context menu in
the named object
LANs
Storage LANs
ff_nas_adm.pl NAS Storage FlexFrame/Storage/NAS/
<filer>/Storage LANs
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 instances ff_sid_adm.pl SAP Service FlexFrame/Pools/<pool>/
SIDs
SAP services ff_sid_mnt_adm.pl
ff_sid_adm.pl
SAP Services FlexFrame/Pools/<pool>/
SIDs/<sid>
Switches ff_swgroup_adm.pl FlexFrame/Network/Switch
Groups/<swg>/Switches
FlexFrame/Network/Switch
Groups/<swg>
Switch groups ff_swgroup_adm.pl Controlling FlexFrame/Network/Switch
Groups
Setup SID Folder
Add New SID
ff_setup_sid_folder.sh FlexFrame/Pools/
<poolname>/SIDs
8.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.
Validation Execution Area
Management Tool 89
● Click on Show Errors.
The window Validation results opens. A table is listing the corresponding
errors.
The column Message 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.
Execution Area Validation
90 Management Tool
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.
Validation Actions
Management Tool 91
9 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 8 Execution Area on page 85.
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 3.2.1 Features Overview on page 12.
Actions Actions Overview
92 Management Tool
9.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.
9.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 9.1.2 Other administrative commands available in
Administration Mode on page 95
You can add/delete via button in the table
named: via context menu in the named object
PM AM 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
Actions Overview Actions
Management Tool 93
You can add/delete via button in the table
named: via context menu in the named object
PM AM PM AM
Application Nodes Application
Nodes
x x Pools/<pool>/Groups/
<group>/Servers
x x
ESX Servers ESX Servers x x ESX Servers/Server List x x
Adding Blade Server
Chassis Chassis
x x Chassis
x x
Control stations and
Adding Data Movers
o o Storage/NAS/<emc_nas>
x x
Data NICs
o o Control
Center/<control_node>
Chassis/<blade_server>/
<swb>
Global Connectivity/
Client LAN Connection
<n>/ClLanCons
Data NICs
o o Storage/NAS/<filer>
Storage/NAS/<emc_nas>/DM
<n>
External Connectivities
(pool-specific)
External
Connectivity
x x Pools/<pool> (first call)
Pools/<pool>/External
Connectivity
(further calls)
LANs
Control LANs
Client LANs
Server LANs
Storage LANs
Storage LANs
o o Control Center/
<control_node>
Control Center/
<control_node>/Client
LANs
Control Center/
<cn_name>/Server LANs
Control Center/
<cn_name>/Storage LANs
Storage/NAS/<emc_nas>/
<data_mover>/Storage LANs
x o
Actions Actions Overview
94 Management Tool
You can add/delete via button in the table
named: via context menu in the named object
PM AM PM AM
Storage LANs o o Storage/NAS/<filer>/
Storage LANs
x x
Mount points for volumes Pool / SID
Mount
x o
o o
NAS systems NAS Storage x x Storage/NAS x x
Pool groups Application
Nodes
x x Pools/<pool>/Groups
x x
Pools Pools x x Pools x x
SAP instances o o Pools/<pool>/SIDs/<sid>/
Instances
x x
SAP services SAP Services x x Pools/<pool>/SIDs x x
Switches o o 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/<emc_nas>/
<data_mover>/Volumes
Storage/NAS/<filer>/
Volumes
x o
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:
● add it again in the object immediately above or
● read it 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).
Actions Overview Actions
Management Tool 95
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.
9.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 (ESX) ESX Servers/Server List/<server>
Add SID setup folder
Mount Sid
Pools/<pool>/SIDs/<sid>
Add SWG Uplink
Delete SWG Uplink
Extend SWG Uplink
Network/Switch Groups/<switch group>
Actions Context Menu of Selected Objects
96 Management Tool
9.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 9.1 Actions Overview on page 92.
● 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 ist 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 ESX Server Actions
Management Tool 97
9.3 Adding ESX Server
The action for adding an ESX server opens a dialog box in which the type of the ESX
server and the corresponding parameter are selected.
Add ESX Server Dialog Box (example for Blade Server only available in
Administration Mode):
Actions Adding ESX Server
98 Management Tool
Add ESX Server Dialog Box (example for Rack Server):
Type Type of the ESX server.
Chassis Slot Slot number of the server blade.
Switch Group Available switch group
Host Name Host name of the ESX server.
10 GBit Data NICs true / false
macAddress1 (Only available in Administration Mode)
macAddress2 (Only available in Administration Mode)
Adding Complete Configuration (ESX) Actions
Management Tool 99
9.4 Adding Complete Configuration (ESX)
To add a Complete Configuration type in administrator user name and password.
User Administrator user name
Password Administrator password
9.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
100 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
Chassis Slot Slot number of the server blade
10 Gbit Data NICs 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 101
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, which denotes a virtual machine on an ESX server.
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 ESX server on which the virtual machine will be created during the installation
process.
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
ESX Server and the intended usage must be taken into
account.
Memory size of
virtual machine
[MB]
Memory size in MB for the virtual machine. Must be a number
between 256 and 261120 (=255GB). Moreover, the available
resources of the ESX Server and the intended usage must be
Actions Adding New AN (Create an AN Image)
102 Management Tool
taken into account.
ESX Server for VM Name of the ESX Server on which the virtual machine is
created
9.6 Adding New AN (Create an AN Image)
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 103
9.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 Group Associated switch group.
Switch Blade Type Type of the switch blade
10 GBit Data NICs wrong / false
Number of NICs Number of the network interface controllers
Use SWB
Credentials
true / false
false: set to default
true: read out from the properties of the switch blade and
handed over to the command
If you delete a blade server chassis the Application Nodes or ESX servers 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.
Actions Adding Control Stations
104 Management Tool
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.
9.8 Adding Control Stations
The action for adding a control station is only available with NS-Type NAS storage
devices. It is carried out directly, no dialog box is opened. Max. 2 control stations can be
present.
Adding Data Movers Actions
Management Tool 105
9.9 Adding Data Movers
The action Add Data Movers is only available in Planning Mode.
Add DM is carried out with a right mouse click on a
NAS storage device in the object tree
The action for adding a data mover is only
available with NS-Type NAS storage
devices.
The action opens the following dialog box. Max. 8 data mover can be present.
Name Name of the data mover.
volFF Device NAS system is VolFF device (true) or not (false).
In a FlexFrame environment must be exactly one VolFF device.
Remote Standby This data mover is standby for a remote partner (true) or not
Actions Adding Data NICs
106 Management Tool
Data Mover (false). The remote partner can be specified with NS-Type
NAS storage devices via the remote partner link. If the remote
partner fails, the standby data mover takes over all tasks.
Local Standby
Data Mover
This data mover is standby for all data movers in the same NS-
Type NAS storage device (true) or not (false).
Note:
Only one of both standby data movers attributes can be set to
true.
9.10 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 familiy types).
2 1GbE NICs 6 for all different types of EMC Celerra data movers.
All interfaces used in FlexFrame are of the same type, either homogeneously 1GbE
or homogeneously 10GbE.
9.11 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.
Adding External Connectivities (Pool-specific) Actions
Management Tool 107
Default for external connectivities are 1 GBit ports. If you need external
connectivites 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.
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.
Switch Group Associated switch group.
Number of NICs Number of NICs.
Actions Adding LAN Interfaces
108 Management Tool
9.12 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.
LAN Selection of the appropriate LAN
Host Host part of the IP address of the LAN
9.13 Adding Mount Points for Volumes
The action Add external connectivity is only available in Planning Mode.
The action for adding a mount point for a volume opens the following dialog box.
Adding NAS Systems Actions
Management Tool 109
Mount Point Object tree path of the mount point.
Volume Path Object tree path of the volume.
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.
9.14 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
110 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.
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.
10 GBit Data NICs wrong / false
Number of NICs Number of Network Interface Cards (2-6).
Number of CSs Number of control centers (1-2).
Number of active Number of active data movers (1-6).
Adding Pool Groups Actions
Management Tool 111
Datamovers
Number of passive
Datamovers
Number of standby data movers (0-6).
The sum of active and passive data movers cannot be higher than 6.
9.14.1 Celerra SRDF-NAS Active/Passive Configuration
In order to build a disaster tolerant FlexFrame configuration with SRDF mirrored EMC
NAS systems, a special type of Celerra SRDF-NAS active/passive configuration has to
be defined by applying the following procedure:
The active Celerra must be the one that has an active data mover which is the volFF
device of the FlexFrame landscape. This system must be defined in a first step (Add
NAS dialog) including storage LAN addresses and volumes for its active data movers.
This Celerra system will also have at least one local standby data mover, which must
be defined with no storage LAN addresses and no volumes, and has the property
Local standby datamover set to true.
Add the passive Celerra in a next step. The passive Celerra must have a number of
RDF standby data movers equal to the sum of the number of active data movers that
need to be protected by SRDF and their associated local standby data movers of the
active Celerra. This attribute cannot be set directly in the Add NAS dialog. Instead,
add the Celerra with the correct total number of data movers. Then set the Remote
partner property of this Celerra to point to the active Celerra. You can do this in the
Remote partner drop-down box in the view that is displayed when selecting the
passive Celerra in the object tree. Now you can set the Remote standby
datamover property to true for each data mover that will be used as an RDF
standby in the view that is displayed when selecting the concerned data mover in the
object tree. These data movers must also be defined with no storage LAN addresses
and no volumes.
9.15 Adding Pool Groups
The action for adding a pool group opens the following dialog box.
Actions Adding Pools
112 Management Tool
Pool Host name of the pool.
Group Name Associated group.
9.16 Adding Pools
The action for adding a pool opens the following dialog box.
Adding SAP Services Actions
Management Tool 113
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 "-".
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.
9.17 Adding SAP Services
The action for adding a SAP service opens the following dialog box with 7 tabs for
different service types.
Actions Adding SAP Services
114 Management Tool
● Classic, page 114
● LiveCache Service (LC, page 115
● Business Objects Enterprise Servce (BOBJ, page 116
● Content Management Server Service Type (CMS, page 117
● TRX, page 118
● Master Data Management Service Type (MDM, page 119
● Solution Manager Diagnostics Service Type (SMD, page 120
9.17.1 Classic
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Number of Instances Number of SAP instances.
Configuration Configuration type of SAP instances.
Pool Name of the associated pool.
Sapdata
Saplog
Path of the related volume
Adding SAP Services Actions
Management Tool 115
SAP Version SAP version.
DB Type and Version Type and version of the database.
Classic Service Uids SID specific user IDs and group IDs
(depending on the selected DB type).
9.17.2 LiveCache Service (LC)
The dialog box for the LiveCache service type (LC) is widely conform to the
dialog box for the Classic service type. The only differences are the missing
fields Configuration and Number of Instances.
Actions Adding SAP Services
116 Management Tool
9.17.3 Business Objects Enterprise Servce (BOBJ)
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Pool Name of the associated pool.
Sapdata
Saplog
Path of the related volume
SAP Version SAP version.
BOBJ Service Uids SID specific user IDs and group IDs
(depending on the selected DB type).
Adding SAP Services Actions
Management Tool 117
9.17.4 Content Management Server Service Type (CMS)
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Pool Name of the associated pool.
Sapdata
Saplog
Path of the related volume
SAP Version SAP version.
DB Type and Version Type and version of the database.
CMS Service Uids SID specific user IDs and group IDs
(depending on the selected DB type).
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.
Actions Adding SAP Services
118 Management Tool
9.17.5 TRX
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Number of Instances Number of SAP instances.
Pool Name of the associated pool.
Sapdata
Saplog
Path of the related volume
SAP Version SAP version.
TRX Service Uids SID specific user IDs and group IDs
(depending on the selected DB type).
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.
Adding SAP Services Actions
Management Tool 119
9.17.6 Master Data Management Service Type (MDM)
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Pool Name of the associated pool.
Sapdata
Saplog
Path of the related volume
SAP Version SAP version.
DB Version Type and version of the database.
Instance Number MDMS / MDS /
MDSS
Instance numbers.
MDM Service Uids SID specific user IDs and group IDs
(depending on the selected DB type, conform to
classic SAP system spec).
Actions Adding SAP Services
120 Management Tool
9.17.7 Solution Manager Diagnostics Service Type (SMD)
SID SAP system ID (up to three characters, in
accordance with SAP rules).
Number of Instances Number of SAP instances.
Pool Name of the associated pool.
OS Operating system
SAP Version SAP version. (optional)
DB Type and Version Type and version of the database.
SMD Service Uids SID specific user IDs and group IDs
(depending on the selected DB type).
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.
Modifying the instance the number of instances for a SAP Service:
Every service knows what instances may be modified in the instance list of a
SID. These kinds of instances / actions are offered in the right-click context
menu of the instance list object / instance.
Adding Switches Actions
Management Tool 121
9.18 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.
Actions Adding Switch Groups
122 Management Tool
9.19 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.
Switch Type See description under Adding Switches above.
Uplinks Actions
Management Tool 123
9.20 Uplinks
9.20.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
9.20.2 Deleting Uplinks
The action for deleting an uplink opens the following dialog box.
Uplink channel Uplink channel to be deleted
Actions Adding Switch Ports
124 Management Tool
9.20.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
9.21 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.
Adding Volumes Actions
Management Tool 125
9.22 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.
Volume Name Name of the volume (max 32 signs, only letters and numbers,
have to start with a letter, volFF is not allowed).
A local standby or remote standby data mover must not possess volumes. This will be
checked when validating the configuration by using the Validate Configuration
function.
If a local standby or remote standby data mover already possesses volumes, you have to
delete the corresponding volumes:
1. Right-click on the volume and select Delete
2. Add them to an active data mover.
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 9.13, like
you did it with the original volume earlier.
Management Tool 127
10 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
CIFS Common Internet File System
DART Data Access in Real Time
DHCP Dynamic Host Configuration Protocol
DIT Domain Information Tree
ERP Enterprise Resource Planning
ESF Enhanced System Facility
EULA End User License Agreement
FAA FlexFrame Autonomous Agent
FC Fiber Channel
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
LUN Logical Unit Number
MAC Media Access Control
MINRA Minimal Read Ahead
NAS Network Attached Storage
NDMP Network Data Management Protocol
NFS Network File System
Abbreviations
128 Management Tool
NIC Network Interface Card
NVRAM Non-Volatile Random Access Memory
OBP Open Boot Prom
OLTP On-Line Transaction Processing
ONTAP Open Network Technology for Appliance Products
OSS Open Source Software
POST Power-On Self Test
PFS Production File System (on Celerra)
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
RHEL Red Hat Enterprise Linux
SCS System Console Software
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
SNMP Simple Network Management Protocol
SWG Switch Group
SWP Switch Port
SPOC Single Point Of Control
Abbreviations
Management Tool 129
TELNET Telecommunications Network
TFTP Trivial File Transfer Protocol
UDP User Datagram Protocol
UPS Uninterruptible Power Supply
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 131
11 Glossary
Adaptive Computing Controller
SAP system for monitoring and controlling SAP environments.
Advanced Business Application Programming
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
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.
BladeRunner
The working title for the solution part of SAP for FlexFrame.
BOOTPARAM
Boot time parameters of the kernel.
BRBACKUP
SAP backup and restore tools.
Celerra
NAS system of EMC.
Checkpoint Restore
On EMC Celerra a SnapSure feature that restores a PFS to a point in time using
checkpoint information. As a precaution, SnapSure automatically creates a new
checkpoint of the PFS before it performs the restore operation.
Client LAN
Virtual network segment within FlexFrame, used for client-server traffic.
Glossary
132 Management Tool
Common Internet File System
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.
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
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.
DART
Operating system of Celerra data movers (Data Access in Real Time).
Dynamic Host Configuration Protocol
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.
EMC NAS
Network attached storage for file systems of EMC.
Enterprise Resource Planning
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
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
A joint project in which the main partners are SAP, Network Appliance, Intel and
Fujitsu.
Glossary
Management Tool 133
FlexFrameTM
for SAP®
FlexFrameTM
for SAP® is a radically new architecture for SAP environments. It
exploits the latest business-critical computing technology to deliver major cost
savings for SAP customers.
FlexFrame internal LAN Switch
Cisco network switches which are integral part of the FlexFrame for SAP hardware
configuration and which are automatically configured by the FlexFrame for SAP
software.
Gigabit Ethernet
A Local Area Network which supports data transfer rates of 1 gigabit (1,000
megabits) per second.
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
Protocol for accessing on-line directory services.
Local Area Network
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
An address for a single (SCSI) disk drive.
MAC address
Device identifier number of a Network Interface Card. In full: "media access control
address".
Glossary
134 Management Tool
MaxDB
A relational database system from mySQL (formerly ADABAS and SAPDB).
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: EMC NAS or 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
A data storage device that is connected via a network to one or multiple computers.
Network File System
A network protocol for network-based storage access.
Network Interface Card
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 Transaction Processing
Transaction processing via computer networks.
OpenLDAP
An Open Source LDAP Service Implementation.
Open Network Technology for Appliance Products
The operating system of Network Appliance Filers.
Glossary
Management Tool 135
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
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
Linux distribution by Red Hat, Inc., targeting business customers.
Reverse Address Resolution Protocol
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.
SavVol
A Celerra volume to which SnapSure copies original point-in-time data blocks from
the PFS before the blocks are altered by a PFS transaction.
Server
A physical host (hardware), same as node.
Service
A software program providing functions to clients.
Glossary
136 Management Tool
Service type
The type of an application or service (db, ci, app, agate, wgate etc.).
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
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
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 Local Area Network
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 137
12 Index
A
abbreviations 127
actions 91
add application node 99
add blade server chassis 103
add control station 104
add data mover 105
add data NIC 106
add ESX server 97
add external connectivity 106
add group 111
add LAN 108
add mount 108
add NAS 109
add pool 112
add SAP service 113
add switch 121
add switch group 122
add switch port 124
add volume 125
overview 92, 96
application node
add 99
application nodes table 68
assign blade server to chassis 104
B
blade server
assign to chassis 104
blade server chassis
add 103
BOBJ 116
C
chassis object 58
chassis table 80
Classic 114
CMS 117
configuration
create 23, 25
edit 35
modify 32
print 35
save 32
validate 36
control center
settings 45
control center object 45
control station
add 104
controlling table 66
create new configuration 23
Index
138 Management Tool
D
data mover
add 105
data NIC
add 106
document history 3
E
error logging 21
ESX parameters 56
ESX server
add 97
ESX servers object 55
ESX servers table 81
execution area 85
external connections 5
external connectivity
add 106
external connectivity table 78
F
failover concept for AN 66
FlexFrame object 44
functions
IP addresses
reset all 42
new configuration 26
open configuration file 31
open LDAP connection 29
perform wiring 37, 39
print 35
save 32
save for installation 33
validate configuration 36
G
general information 63
global connectivity object 59
global connectivity, generate 39
glossary 131
group
add 111
H
host names 8
host parts
generate 41
generate automatically 42
generate manually 42
I
installation
save 33
IP addresses
reset 42
L
LAN
add 108
LC 115
M
Management Tool
exit 17
screen layout 18
Index
Management Tool 139
starting 16
MDM 119
menu functions 25
edit 35
file 25
mode 42
tools 36
mount
add 108
N
NAS
add 109
NAS storage table) 70
network concept 5
network object 47
network settings 48
network wiring plan, generate 37
new configuration 26
notational conventions 2
NTP master server 46
O
object tree 43
open configuration file 31
open LDAP connection 29
P
pool
add 112
pool / SID mount 71
pool mount 73
pools object 51
pools table 64
R
related documents 3
S
SAP service
add 113
BOBJ 116
Classic 114
CMS 117
LC 115
MDM 119
SMD 120
TRX 118
SAP services 73
SID mount 73
SMD 120
SNMP community 8
storage object 50
sub-object tree 53
switch
add 121
switch group
add 122
switch group tree view 49
switch port
add 124
switch ports 78
Index
140 Management Tool
T
tagged VLAN 78
TRX 118
U
users groups services table 77
V
vCenter 57
view area 61
virtual host names) 75
virtual IP addresses 75
VLAN
host names 8
VLAN IDs 78
volume
add 125
volumes 71
volumes table 72
W
wiring 83
