FlexFrame for SAP 4 - Fujitsumanuals.ts.fujitsu.com/file/8348/ff42a_management_tool_v... · 2011-10-06 · SAP system installations should only be performed by consultants who are

User Guide

FlexFrame™ for SAP® 4.2AManagement Tool

English

FlexFrame™ for SAP® Version 4.2A

Management Tool

Edition December 2008 Document Version 1.0

Fujitsu Siemens Computers GmbH

© Copyright Fujitsu Siemens Computers GmbH 2008 FlexFrame™, PRIMECLUSTER™. PRIMEPOWER™ and PRIMERGY™ are trademarks of Fujitsu Siemens Computers SPARC64® is a registered trademark of Fujitsu Ltd. 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 coun-tries Java™ and Solaris™ are trademarks of Sun Microsystems, Inc. in the United States and other countries Intel® and PXE® are registered trademarks of Intel Corporation in the United States and other countries MaxDB® and MySQL® are registered trademarks of MySQL AB, Sweden NetApp®, Network Appliance®, Open Network Technology for Appliance Products™, Write Anywhere File Layout™ and WAFL™ are trademarks or registered trademarks of Network Appilance, Inc. in the United States and other countries Oracle® is a registered trademark of ORACLE Corporation EMC®, CLARiiON®, Symmetrix®, PowerPath®, Celerra™ and SnapSure™ are trademarks or registered trademarks of EMC Corporation in the United States and other countries SPARC™ is a trademark of SPARC International, Inc. in the United States and other coun-tries 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.............................................................................................. 2 1.3 Related Documents........................................................................................... 3

2 Network Concept............................................................................................. 5 2.1 LAN Failover...................................................................................................... 5 2.2 LAN Trunking .................................................................................................... 5 2.3 VLAN Segments................................................................................................ 6 2.4 Host Names....................................................................................................... 7 2.5 Switches............................................................................................................ 7

3 Working with the Management Tool .............................................................. 9 3.1 Starting the Management Tool .......................................................................... 9 3.2 Exit the Management Tool ................................................................................ 9 3.3 Screen Layout of the Management Tool ......................................................... 10

4 Brief Instruction for Creating a New FlexFrame Configuration................. 13

5 Menu Functions............................................................................................. 15 5.1 Creating a New Configuration ......................................................................... 15 5.1.1 “New Configuration” Function.......................................................................... 15 5.1.2 “Open LDAP Connection” Function ................................................................. 18 5.1.3 “Open Configuration File” Function ................................................................. 20 5.2 Modifying an Existing Configuration ................................................................ 20 5.3 Saving a Configuration .................................................................................... 21 5.4 Printing a Configuration................................................................................... 22 5.5 Editing a Configuration .................................................................................... 22 5.6 Validating a Configuration ............................................................................... 23 5.7 Generating a Network Wiring Plan .................................................................. 23 5.7.1 Automatic Generation...................................................................................... 24 5.7.2 Manual Generation.......................................................................................... 24 5.8 Generating Global External Connectivity......................................................... 25 5.8.1 Automatic Generation...................................................................................... 25 5.8.2 Manual Generation.......................................................................................... 26 5.9 Generating Host Parts of IP Addresses........................................................... 27 5.9.1 Generate Host Parts Automatically ................................................................. 27 5.9.2 Generate Host Parts Manually ........................................................................ 27

6 Object Tree..................................................................................................... 29 6.1 General Features ............................................................................................ 29 6.2 “FlexFrame” Object ......................................................................................... 30

Introduction

Management Tool

6.3 “Control Center” Object ................................................................................... 31 6.4 “Network” Object.............................................................................................. 33 6.5 “Storage” Object .............................................................................................. 35 6.6 “Pools” Object.................................................................................................. 36 6.7 “Chassis” Object .............................................................................................. 39 6.8 “External Connectivity” Object ......................................................................... 40

7 View Area ....................................................................................................... 41 7.1 General Features............................................................................................. 41 7.2 “General Information” View.............................................................................. 42 7.3 “Pools” View .................................................................................................... 43 7.4 “Controlling” View ............................................................................................ 44 7.5 “Application Nodes” View ................................................................................ 45 7.6 “NAS Storage” View ........................................................................................ 48 7.7 “Volumes” and “Pool / SID Mount” View .......................................................... 49 7.7.1 “Volumes” View ............................................................................................... 50 7.7.2 “Pool / SID Mount” View .................................................................................. 50 7.8 “SAP Services” View ....................................................................................... 51 7.9 “External Connectivity” View............................................................................ 54 7.10 “Wiring” View ................................................................................................... 55

8 Actions ........................................................................................................... 57 8.1 Overview.......................................................................................................... 57 8.2 Adding Application Nodes ............................................................................... 60 8.3 Adding Blade Server Chassis .......................................................................... 61 8.4 Adding Control Stations................................................................................... 61 8.5 Adding Data Movers ........................................................................................ 62 8.6 Adding Data NICs............................................................................................ 63 8.7 Adding External Connectivities (Pool-specific) ................................................ 63 8.8 Adding LAN Interfaces..................................................................................... 64 8.9 Adding Mount Points for Volumes ................................................................... 64 8.10 Adding NAS Systems ...................................................................................... 65 8.10.1 Celerra SRDF-NAS Active/Passive Configuration ........................................... 66 8.11 Adding Pool Groups ........................................................................................ 66 8.12 Adding Pools ................................................................................................... 67 8.13 Adding SAP Instances..................................................................................... 68 8.14 Adding SAP Services ...................................................................................... 69 8.15 Adding Switches .............................................................................................. 70 8.16 Adding Switch Groups ..................................................................................... 70 8.17 Adding Switch Ports ........................................................................................ 71 8.18 Adding Volumes .............................................................................................. 71

9 Abbreviations................................................................................................. 73

Contents

Management Tool 3

10 Glossary......................................................................................................... 77

11 Index............................................................................................................... 83

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 ver-sions ≥ 4.2A, whereas the previous FlexFrame for SAP Planning Tool works together with all FlexFrame for SAP versions prior to 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 cus-tomer-specific FlexFrame environment on a Windows® PC with Java SE 6 and newly also on other platforms, e.g. Linux.

With this tool you can

● create an initial FlexFrame configuration file ● modify an existing FlexFrame configuration file (new!) ● open an LDAP connection to a server to get a current FlexFrame configuration to be

used as initial configuration (new!) ● create/modify the network cabling plan

After the data has been entered correctly, it is stored in an XML file on an approved ex-ternal 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.

The two Control Nodes (CN) of FlexFrame for SAP are also named as 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.

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

This document is only to be used by Certified FlexFrame Consultants who have com-pleted FlexFrame, PRIMECLUSTER™ and Network Appliance® Filer training or EMC NAS Storage training. They also should have expert knowledge of Linux® OS and (if needed) Solaris™ 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).

1.2 Document History Document Version Changes Date

1.0 First Edition 2008-12-10

Related Documents Introduction

Management Tool 3

1.3 Related Documents FlexFrame™ for SAP® – Administration and Operation FlexFrame™ for SAP® – HW Characteristics Quickguides FlexFrame™ for SAP® – Installation ACC 7.1 SP06 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.0 or 4.1A to 4.2A PRIMECLUSTER Documentation ServerView Documentation Solaris Documentation SUSE Linux Enterprise Server Documentation

Management Tool 5

2 Network Concept The network concept of FlexFrame is very essential. We will therefore first provide a brief explanation of this concept. If you are already familiar with it, please continue with chap-ter “Working with the Management Tool” on page 9. 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. Only one network segment, the Client VLAN (see section VLAN Segments” on page 6), is routed outside the FlexFrame network to connect to the existing outside network.

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 Flex-Frame environment plus a set of preconfigured SAP services that belong to the same customer. A pool is usually related to a client. By assigning separate VLANs to every pool these clients are well separated. This multi client capability of FlexFrame is an essential feature.

2.1 LAN Failover LAN failover describes the ability of the FlexFrame environment to use a logical network interface that consists of several physical network interface cards (NICs), which in turn use redundant network paths (cables and switches). When a network component (NIC, cable, switch, etc.) fails, the network management logic will switch-over to another net-work interface card and path.

2.2 LAN Trunking High demands on network throughput the network path to the NAS system may require a bandwidth of more than a single NIC. LAN Trunking (IEEE 802.1q) allows multiple paths to the network backbone to be combined.

The method applied is able to work with the coexisting LAN failover solution described above. It is also required that the load balancing uses the round-robin method based on Ethernet packages.

Network Concept VLAN Segments

6 Management Tool

2.3 VLAN Segments FlexFrame relies on a virtual network concept, providing higher availability as well as increased flexibility for the FlexFrame environment.

This concept relies on VLAN technology that allows multiple virtual networks to be run across a single network wiring system. Additionally, in order to ensure high network availability, LAN bonding is used on every node. This includes a double switch and wiring infrastructure, to keep the whole environment working, even when a network switch, cable or NIC fails. Furthermore, the network segments are prioritized to ensure that im-portant connections are preferred.

Similar to former FlexFrame versions, typically four networks are used within one Flex-Frame system or within a single FlexFrame pool. FlexFrame uses virtual network seg-ments. These virtual networks run through redundant NICs, using bonding on Linux and IPMP on Solaris. The figure below outlines the basic network segments of a typical FlexFrame environ-ment with Linux-based Application Nodes.

Host Names Network Concept

Management Tool 7

The following virtual network segments are mandatory for FlexFrame: Client LAN (one for each pool)

This LAN provides dedicated user connectivity to the SAP instances. This segment also allows administrators to access the Control Center.

Control LAN (one for all pools together) This LAN carries all administrative communication for Remote View Service Board (RSB), IPMI-, XSCF- and/or RPS-interfaces, NAS devices and switches.

Server LAN (one for each pool) This LAN is used for SAP instances to communicate with each other and with the da-tabases.

Storage LAN (one for each pool) This LAN is dedicated to NFS communication for accessing the executables of SAP and the RDBMS, as well as the IO of the database content and SAP instances.

The network bandwidth has to be at least one Gbit/sec for all components (except for the Control Lan) to handle intense data traffic.

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 exeption 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 char-acters including the hyphen (“-”). The first character must be a letter. In the SAP environment host names are case-sensitive (see SAP Note No. 611361).

2.5 Switches Network switching components play a very important role within FlexFrame. Therefore, only the following switches are tested and supported:

● Cisco Catalyst 3750g ● Cisco Catalyst 3750e (including 10GbE NICs)

This switch family supports VLAN technology for a flexible configuration of the various network segments and QoS (Quality of Service) to prioritize traffic (e.g. higher priority for production systems over test systems etc.). The Cisco StackWise Technology is able to use cross-stack LAN trunking (this means the usage of ports of different switches within one stack).

Management Tool 9

3 Working with the Management Tool

3.1 Starting the Management Tool The Management Tool is shipped on the ServiceCD in the directory /config.

It consists of the Jar files MgmtTool.jar, MgmtToolLoader.jar, xercesImpl.jar, xml-apis.jar and an optional Patch.jar, which have to be copied 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 fol-lowing way:

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

o Type java –jar MgmtTool.jar

● When using the Patch.jar file, you have to call MgmtToolLoader.jar instead of MgmtTool.jar. Only MgmtToolLoader.jar activates the patches in Patch.jar.

SUN Java SE 6 is required.

The screen of the Management Tool ist opened. For an explanation of the different areas see the following section.

At the moment the Management Tool does not possess a recovery func-tion!

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

– by adding it again or

– by reading 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 accom-plish a backup in the meantime).

3.2 Exit the Management Tool You exit the Management Tool by selecting Exit in the function area.

Working with the Management Tool Screen Layout of the Management Tool

10 Management Tool

3.3 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 is a photomontage illustrating all areas. Depending on the individual procedure step, all areas are not always visible.

1. Menu bar

Here you find administrative functions of the PlanningTool.

2. Object tree

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

When you select an object in this area with a left mouse click you get a differentiated view on this object or on the subtree of this object in the view area (3). This means, the selected object in the object tree determines the content of the view area and the

Screen Layout of the Management Tool Working with the Management Tool

Management Tool 11

deeper you are in the structure the differentiated is the display of the parameters. If you select a leaf object you will see in the view area only the properties of the se-lected object.

Depending on the selected object you can open a context menu by doing a right mouse click on the object. Via context menus you can carry out object dependent ac-tions. Each action carried out produces a new object-dependent subtree in this area.

3. View area

Depending on the selected object in the object tree, a view is opened in this area. This view consists of a table, a property list or of both of them in terms of split panes.

In this area the values of all fields highlighted in white in the table as well as the val-ues of the fields in the property lists can be changed via a pull-down menu or by di-rect input (the latter must be confirm with CR).

If applicable, there are buttons above a table for carrying out. Each action carried out produces a new object-dependent subtree in the object tree.

View area of the FlexFrame object (the root of the object tree)

When you select the FlexFrame object, you get information on the whole FlexFrame installation in the view area. To select this information, the view area of the Flex-Frame object contains an additional tab bar.

Depending on the selected tab in this bar, you get a global view on the configuration objects. For defining a basic Flexframe configuration most of the settings can be done under these tabs.

For users of the old Excel Management Tool the FlexFrame view with its tabbed panes will look familiar

For defining details of a configuration, which are not visible or change-able in the view area, you have to select the corresponding object in the object tree and to set the properties right at the objects itself.

Management Tool 13

4 Brief Instruction for Creating a New FlexFrame Configuration

The validation of the data input is done by using the Validate Configura-tion function (see section 5.6). This validation always is context sensitive which means that the input normally is not checked directly when edited. Therefore it is recommended to use the Validate Configuration function in between the data input to check the data and correct data mismatch not only at the end of the complete configuration.

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

1. After starting the Management Tool (see section 3.1) choose the function File->New Configuration in the File menu (see section 5.1.1).

A dialog box is opened 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 8.15).

Optional activities at this point:

You can add

2.1. other switch groups to the desired configuration (see section 8.16).

2.2. other pools to the desired configuration (see section 8.12).

2.3. other groups to the existing pool(s) (see section 8.11).

2.4. pool-specific external connectivities (see section 8.7).

2.5. other NAS storages (see section 8.10).

2.6. control stations (see section 8.4) and/or data movers (see section 8.5) in case of NAS storages of the type NS-Type.

2.7. volumes to the NAS storage(s) (see section 8.18) .

2.8. mount points for the added volumes (see section 8.9).

2.9. global connectivities either manually or automatically with optional additional Client LANs (see section 5.8).

2.10. one or more blade server chassis (see section 8.3).

Brief Instruction for Creating a New FlexFrame Configuration

14 Management Tool

3. Add Application Nodes (see section 8.2).

Optional activity at this point:

You can add SAP services (see section 8.14) and corresponding SAP instances (see section 8.13).

4. Fill in the form for the control center settings (see section 6.3).

5. Generate the hosts parts of the IP addresses (see section 5.9).

6. Generate the network wiring plan (see section 5.7).

7. Validate the configuration (see section 5.6). In case of errors you have to correct them and validate the configuration again.

8. Save the valid configuration (see section 5.3).

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

9. You can print the settings of the configuration (see section 5.4).

Management Tool 15

5 Menu Functions

5.1 Creating a New Configuration A new configuration can be created in the following three ways.

5.1.1 “New Configuration” Function With this function you can create a new initial configuration from scratch.

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.

Menu Functions Creating a New Configuration

16 Management Tool

First Pool Name The name of the first 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.

First Group Name The name of the first pool group. The name must start with a letter and may only contain numbers, letters, “_“ or “-“.

Creating a New Configuration Menu Functions

Management Tool 17

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 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 IPv4 address of the DNS Domain Server for the first pool. The name has to be conform to RFC1035 (see above). No entry is required for this field. If this field is empty, fully qualified domain names outside of Flex-Frame cannot be resolved by neither the Control Nodes nor the Application Nodes.

Network (LANs) The relevant network in IPv4 format. In binary, the net-work 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 be-tween 2 and 4094. The VLAN IDs must be unique over all LAN segments.

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, press the OK button. The structured object list for this configuration will be displayed.

Menu Functions Creating a New Configuration

18 Management Tool

5.1.2 “Open LDAP Connection” Function With this function you can create a new configuration by reading in an existing configura-tion from LDAP and saving it in an XML file.

A configuration file created with the Management Tool contains data that is not stored in the LDAP of a FlexFrame installation. These missing data must be added after reading in a configuration from LDAP.

Before adding the missing data, a validation of the current configuration will al-ways show errors (see Validating a Configuration on page 23).

Even when the missing data has been added and no validation errors are indi-cated anymore, you should be aware, that the data read from the LDAP might be erroneous due to unpropper 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 is dispayed in which you can choose a properties file.

To open an LDAP connection, click on the corresponding file and then click the Open button. The structured object list for this configuration will be displayed.

Creating a New Configuration Menu Functions

Management Tool 19

By clicking the Edit LDAP Properties button the following dialog box is displayed and you can modify the properties of the selected file and save them (Save as).

By pressing the Set LDAP Properties button the same dialog box is displayed with blank input fields.

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 speci-fied. 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.

Menu Functions Modifying an Existing Configuration

20 Management Tool

5.1.3 “Open Configuration File” Function With this function you can create a new configuration by modifying an existing configura-tion file and saving it under a new name.

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

To open a configuration file, click on the corresponding XML file and then click the Open button. The structured object list for this configuration will be displayed.

5.2 Modifying an Existing Configuration To modify an existing configuration, use the Open Configuration File function, modi-fy the parameters and save it under the same name.

Saving a Configuration Menu Functions

Management Tool 21

5.3 Saving a Configuration You save a configuration by selecting the Save function.

The following dialog box is displayed in which you can save the new/modified configuration in an XML file.

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

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

The configuration file should be copied under the name ff_config.xml to the root directory of a blank floppy disk or 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.

Menu Functions Printing a Configuration

22 Management Tool

5.4 Printing a Configuration You can print the current settings of the choosen configuration by selecting the Print function. The views of all tabs or the wiring plan are printed.

5.5 Editing a Configuration With the functions Add and Delete you can execute the same actions, which are offered as buttons in different views. For more information see chapter “View Area” on page 41.

Validating a Configuration Menu Functions

Management Tool 23

5.6 Validating a Configuration With the Validate Configuration function yon can check whether the current con-figuration 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 checkbox.

The validation of the data input is done by using the Validate Configura-tion function. This validation always is context sensitive which means that the input normally is not checked directly when edited. Therefore it is recommended to use the Validate Configuration function in between the data input to check the data and correct data mismatch not only at the end of the complete configuration.

5.7 Generating a Network Wiring Plan Yon can generate a network wiring plan automatically or manually. The automatic gen-eration is recommended because it is the most comfortable and safest method to gene-rate 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 55).

Menu Functions Generating a Network Wiring Plan

24 Management Tool

5.7.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 func-tion. Only if the existing wiring is manually preconfigured and supposed to re-main, you may call Perform Wiring without first resetting it.

All NICs will be connected automatically to the related switch ports. The icons of the con-nected 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 core switch. The core switch is in the responsibility of the customer environ-ment (see “network Design and Configuration Guide).

5.7.2 Manual Generation To modify a network wiring plan manually, navigate to the appropriate entry in the object tree and select a value from the pull-down menu (see the example below). If the switch port is already connected, its icon is marked green in the object tree.

Before you generate a network wiring plan manually, it is recommended to de-lete an existing network wiring plan with the Clear Wiring function.

Generating Global Connectivity Menu Functions

Management Tool 25

5.8 Generating Global Connectivity With the Management Tool a pool-independent global connectivity can be planned. It leads to configuration of abstract external connectivity devices. For a pool-specific exter-nal connectivity see page 54.

The global connectivity is responsible for the global network connections which connect the internal FlexFrame network with the “outside world” (e.g. corporate network).

With the global connectivity switch ports are defined, to which external devices can be assigned.

After the global connectivity is generated, it is displayed in the object tree (see page 39) and under the Wiring tab in the FlexFrame object view (see page 55).

5.8.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 Clear Client LAN Connec-tivity function.

With the automatic generation a standard wiring will be generated analogous to the fol-lowing settings in the Network object (see also page 33):

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

If only one NIC is desired, you must delete it in the object tree. If the redundancy has to be used on the device side too, a similar active-backup failover configuration like on the Control and Application Nodes has to be used.

The 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.

Menu Functions Generating Global Connectivity

26 Management Tool

5.8.2 Manual Generation To generate the global connectivity manually, perform the following steps:

1. If the entry Global Con-nectivity is not available in the object tree, create it:

2. Add a Client LAN Connec-

tion entry:

3. Under ClLanCons add (at

least) one Client LAN entry:

A dialog box is opened, in which you must link the Cli-ent 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:

Generating Host Parts of IP Addresses Menu Functions

Management Tool 27

4. To connect the NICs to the related switch ports, execute the Perform Wiring func-tion (without executing Clear Client LAN Connectivity before), or set the con-nection manually (see below):

5.9 Generating Host Parts of IP Addresses Yon 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 Flex-Frame 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

5.9.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.9.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 prop-erty of a selected IP interface object.

Management Tool 29

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 subtree 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.

You can modify certain settings of any object. By selecting an object, the releated view with the responsible input fields is displayed.

Depending on an object you can open a context menu by doing a right mouse click on the object. Via context menus you can carry out object dependent actions. Each action car-ried out produces a new object-dependent subtree in this area.

On page 57 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 take place!


– by adding it again in the object immediately above or



The object tree consits of the major object FlexFrame and six basic objects described in the following.

Object Tree “FlexFrame” Object

30 Management Tool

6.2 “FlexFrame” Object If you select the FlexFrame object, the tab bar is displayed which is emulated from the old Excel based Management Tool.

Depending on the selected tab in this bar, you get a global view on the configuration objects in the view area (see page 41).

“Control Center” Object Object Tree

Management Tool 31

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 Con-trolling view is displayed (see page 44).

The upper split pane shows a list of properties necessary for the Control Center (see Miscellaneous Control Center set-tings 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 Cluster Name Name of the PRIMECLUSTER on the Control Nodes

(default FlexFrame). Cluster IP1 / IP2 First and second cluster IP address (both should be

in the same network section).

The cluster IP addresses IP1 and IP2 must be in separate host sections. At least four addresses are required: two IP addresses, a broadcast address and a network base address. Subnetworks are permitted.

Example:

Cluster Netmask: 255.255.255.252 # Subnetwork with 4 addresses Network Base Address: 192.168.1.0 Cluster IP1: 192.168.1.1 Cluster IP2: 192.168.1.2 Cluster Broadcast: 192.168.1.3

Object Tree “Control Center” Object

32 Management Tool

Cluster Netmask Netmask of the cluster (defines the cluster’s network part).

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.fujitsu-siemens.com). The DNS domain name is required and has to be 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 Con-trol Nodes nor the Application Nodes.

LDAP Base DN The LDAP Base Distinguished Name is the root for the LDAP name space for this FlexFrame environ-ment (e.g. DC=myFlexFrame,DC=fujitsu-siemens,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 sec-ond Control Node will be a backup NTP server.

Time Zone Time zone of the FlexFrame environment to be in-stalled.

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). Allow Dynamic LUN Masking With this configuration dynamic LUN masking is

allowed (true) or not (false).

“Network” Object Object Tree

Management Tool 33

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 inte-grated 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 page 44).

The upper split pane shows miscellaneous settings concerning the network (see Miscellaneous Network settings below).

Object Tree “Network” Object

34 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 config-ured 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 config-ured 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“

“Storage” Object Object Tree

Management Tool 35

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. Only two switch groups may be connected directly.

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.


By selecting this object, the NAS Storage view is dis-played (see page 48).

The NAS Details view is also displayed under the Stor-age – NAS object.

Object Tree “Pools” Object

36 Management Tool

6.6 “Pools” Object In this object the features of a pool within a FlexFrame environment are managed. De-pending on the choosen object an appopriate 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 belongs 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 contain one or more pool groups. A pool group is an additional grouping level within a pool. All Application Nodes with common characteristics maybe 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 in-stance 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 subobjects of the Pools object as examples.

By selecting the Pools object, the Pools view is dis-played (see page 43).

By selecting the External Connectivity object the pool-specific External Connectivity view is dis-played (see page 54).


“Pools” Object Object Tree

Management Tool 37

By selecting the Sids object the SAP Services view is displayed (see page 51).

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.

Object Tree “Pools” Object

38 Management Tool

By selecting a pool (e.g. pool1) or the Groups object (and subobject below), the Application Nodes view is displayed (see page 45). The rele-vant display is object dependent.

The left figure shows an example for a blade server (group2) and a PRIMERPOWER (group3).

With blade servers, only the server blades are managed in the Pools object. The mamagement blade and the switch blades are managed in the Chassis object (see page 39).

“Chassis” Object Object Tree

Management Tool 39

6.7 “Chassis” Object In this object the management blade and the switch blades of all blade servers within a FlexFrame environment are managed. The view of this object displays the same informa-tion as the Application Nodes view, but only for blade servers.

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

With the Add action you can add the management blade and the switch blades for a new blade server. The switch blade types include the type Pass-Thru, which enables dedicated connections to specific server blades and also enables to use part of the server blades within FlexFrame and part of it out-side of FlexFrame. The server blades for a blade server must be specified hereafter in the Pools ... Servers object or under the Application Nodes tab as Application Nodes. With the Delete action you can delete the management blade and the switch blades of a blade server.


If a server blade is already connected to a slot, the icon of the slot is marked green.

Object Tree “Global Connectivity” Object

40 Management Tool

6.8 “Global Connectivity” Object In this object the global network connections are managed. For further information see page 25.

The figure on the left side shows the Global Connec-tivity object as an example.

Under the ClLanCons object you can define global Client LANs.

Management Tool 41

7 View Area

7.1 General Features Depending on the selected object in the object tree or on the selected tab in the tab bar, a view is opened in this area. This view consists of a table, a property list or of both of them in terms of split panes.

A tab bar in the views is only displayed when you select the FlexFrame object in the object tree (see page 30).

The figures in this chapter show the information when opening the tabs of the FlexFrame object view.

The corresponding information will be also displayed when selecting another object (be-low the FlexFrame object) in the object tree. In this case, the view depends on the loca-tion of the object in the object tree. This means, the deeper you are in the structure the differentiated is the display of the information. If you select a leaf object you will see in the view area only the properties of the selected object (e.g.: Wiring View for Storage only, Wiring View for one switch group only or Application Nodes for one pool only).

While describing the individual views the corresponding objects are specified.

In the view area the values of all fields highlighted in white in the table as well as the values of the fields in the property lists can be changed via a pull-down menu or by direct input (the latter must be confirm with CR).

If applicable, there are buttons above a table for carrying out actions. Each action carried out produces a new object-dependent subtree in the structured object tree.

On page 57 you find an overview of all actions.

View Area “General Information” View

42 Management Tool

7.2 “General Information” View This view displays general information related to the Management Tool.

● No corresponding object in the object tree available.

Customer Name of the customer Project Name Name of the customer project Contact Person Information to the contact person at the customer (eg. name,

phone numer, email address) Origin of Data Original database of the configuration Comments Any comments (not stored in the configuration file)

“Pools” View View Area

Management Tool 43

7.3 “Pools” View This view shows all existing pools with their current LAN parameters as well as the DNS information.

● You can open this view also via the Pools object in the object tree (see page 36).

Due to the table size the presentation of the Pools view is divided into a left part (first figure) and a right part (second figure) of the screen.

Pool Name of the pool Network Network address of the individual LAN Netmask Netmask of the individual LAN VLAN ID 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.

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.

View Area “Controlling” View

44 Management Tool

7.4 “Controlling” View In this view the switch groups, the Control Nodes and associated pools are displayed with their current LAN parameters.

● You can open this view also via the Control Center object concerning the Control Node entries (see page 31) and via the Network object concerning the switch group entries (see page 33) in the object tree.

If you open this view via the Control Center object, an additional area is dis-played above the table. Here you can enter miscellaneous settings concerning the Control Center.

Due to the table size the presentation of the Controlling view is divided into a left part (first figure) and a right part (second figure) of the screen.

“Application Nodes” View View Area

Management Tool 45

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.

● In the Swg column you can change the association of switch groups to Control No-des. 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 differ-ent LANs by direct input.

7.5 “Application Nodes” View In this view all existing Application Nodes of the FlexFrame environment on which the SAP services run are displayed with their current parameters.

● You can open this view object dependent also via different subentries of the Pools object in the object tree (see page 36), e.g. the information for a single pool is dis-played under Pools - <pool_name> and for a single group under Pools - <pool_name> - Groups - <group_name>.

Depending on the type of an Application Node, one or more lines exist. This is particularly important for blade servers with a chassis as they use common resources (management blade and switch blades) that need to be configured once only per blade chassis.

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.

To provide network redundancy for PRIMEPOWER™ nodes with Solaris IPMP, additional test addresses are required. When they are created, these entries are added automati-cally as the types Solaris HA1 and Solaris HA2.

Due to the table size the presentation of the Application Nodes view is di-vided into a left part (first figure) and a right part (second figure) of the screen.

View Area “Application Nodes” View

46 Management Tool

Host Name Name of the Application Node Type Type of the Application Node Swg Associated switch group Pool Associated pool Group Associated pool group OS Operating system of the component 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

“Application Nodes” View View Area

Management Tool 47

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

● With the actions Add Application Node and Delete Application Node you can add or delete Application Nodes.

● In the Swg, Pool, Group and OS columns you can change the association of a switch group, pool, pool group and operating system to an Application Node, respec-tively. 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 Applica-tion Nodes and the host part of the IP addresses of the different LANs by direct in-put.

BX630S2 Model Based Servers

BX630S2 model based server blades currently are available in two different versions that occupy a different number of slots:

BX630S2 (= BX630S2 dual) occupies 1 slot similar to BX620S4 or BX6302 (= BX630 dual)

BX630S22 (= BX630S2 quad) occupies 2 slots similar to BX6304 (= BX630 quad)

For models that occupy more than one slot the part of the server blade that occupies the slot with the highest slot number is called the master. The master is usually the rightmost slot. In the Management Tool you only have to assign an IP to the master slot. The other slots are left empy (see the example arrangement of BX630S2 Server Blades below).

View Area “NAS Storage” View

48 Management Tool

7.6 “NAS Storage” View In the NAS Storage view all existing physical Network Attached Storage systems are displayed with their current parameters.

● You can open this view also via the Storage and Storage - NAS objects in the object tree (see page 35)

Due to the table size the presentation of the NAS Storage view is divided into a left part (first figure) and a right part (second figure) of the screen.

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 (Cs = Control station, DM = Data mover)

Standby local This data mover is standby for all data movers in the same NS-Type NAS storage device (true) or not (false).

“Volumes” and “Pool / SID Mount” View View Area

Management Tool 49

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 sys-tems. 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.

7.7 “Volumes” and “Pool / SID Mount” View

View Area “Volumes” and “Pool / SID Mount” View

50 Management Tool

7.7.1 “Volumes” View 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 page 35).

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 Name Name of the volume 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.

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

7.7.2 “Pool / SID Mount” View In this view 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 subdirectories or for its sapdata subdirectories. This mounting of a volume is repre-sented 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 subdirectories. This mounting of a volume is also repre-sented 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 specifc mount and no sid specific mount the data will reside in the common volFF.

● You can open this view also object dependent via the Storage – NAS - <NAS_name> - [<data_mover>] object in the object tree (see page 35).

Mount Type Type of the mount point Pool Name of the associated pool SID SID from SAP Services VolFF / Sap-data / Saplog

Path of the related volume

“SAP Services” View View Area

Management Tool 51

● With the actions Add Mount and Delete Mount you can add or delete mount points of volumes.

7.8 “SAP Services” View In this view all existing SAP services are displayed with their current parameters.

● You can open this view object dependent via the Pools – <pool_name> - Sids object in the object tree (see page 36).

Due to the table size the presentation of the Sap Services view is divided into a left part (first figure) and a right part (second figure) of the screen.

View Area “SAP Services” View

52 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 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.

● 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 dif-ferent LANs by direct input.

“SAP Services” View View Area

Management Tool 53

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 - database instance ci - central instance (ABAP) app - application instance (ABAP) ascs - ABAP SAP central services instance scs - JAVA SAP central services instance jc - JAVA central instance j - JAVA application instance lc - LiveCache instance ers - Enqueue Replication Service instance

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.

View Area “External Connectivity” View

54 Management Tool

7.9 “External Connectivity” View 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 page 25.

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 inter-faces using tagged VLANs. To be able to communicate, these VLANs have to be config-ured with the same VLAN IDs like the switch port and as configured with the Manage-ment Tool. A link aggregation for load balancing will not work and may block the entire network!

In the External Connectivity view 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 open this view also object dependent via the Pools – <pool_name> - External Connectivity object in the object tree (see page 36).

Due to the table size the presentation of the Sap Services view is divided into a left part (first figure) and a right part (second figure) of the screen.

Host Name Host name of the external device Swg Associated switch group Pool Associated pool NICs Number of NICs 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

“Wiring” View View Area

Management Tool 55

● With the actions Add External Connectivity and Delete External Connec-tivity you can add or delete a connection (see page 63).

● 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.

7.10 “Wiring” View In this view the generated network wiring plan is displayed.

You can open this view also object dependent via the Add – Wiring action under the following objects in the object tree: – FlexFrame – Storage – Pools – <pool> – Pools – <pool> –- Groups – <group>

Management Tool 57

8 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.

Actions always generate a new subtree in the structured object tree like storage objects with their subcomponents, Application Nodes with their NICs and LAN addresses or switch groups.

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 context menu.

8.1 Overview The following table gives an overview where actions can be performed.

You can add/delete via button in the named view via context menu in the named object

Wiring View

This is a special view object which displays the wiring for the corresponding object in the view area.

FlexFrame

Storage

Pools – <pool>

Pools – <pool> –- Groups – <group>

Application Nodes Application Nodes Pools – <pool> – Groups – <group> – Servers

Blade server chassis Chassis Chassis

Control stations and Data movers

Storage – NAS – <emc_nas>

Data NICs

Control Center – <control_node>

Storage – NAS – <filer>

Storage – NAS – <emc_nas> – DM <n>

Chassis – <blade_server> – <swb>

Global Connectivity – Client LAN Connection <n> – ClLanCons

Actions Overview

58 Management Tool

You can add/delete via button in the named view via context menu in the named object

External connectivites (pool-specific)

External Connectivity

Pools – <pool> (first call)

Pools – <pool> – External Connectivity (further calls)

LANs

Control LANs

Client LANs

Server LANs

Storage LANs

Storage LANs

Storage LANs

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

Storage – NAS – <filer> – Storage Lans

Mount points for volumes Pool / SID Mount

NAS systems NAS Storage Storage – NAS

Pool groups Application Nodes Pools – <pool> – Groups

Pools Pools Pools

SAP instances Pools – <pool> – SIDs – <sid> – Instances

SAP services SAP Service Pools – <pool> – SIDs

Switches Network – Switch Groups – <swg> – Switches

Switch groups Controlling Network – Switch Groups

Switch ports Network – Core or Direct – Ports Core or Direct

Volumes Volumes

Storage – NAS – <emc_nas> – <data_mover> – Volumes

Storage – NAS – <filer> – Volumes

Overview Actions

Management Tool 59

Delete actions in the structured object tree are carried out directly, no safety inquiry take place!


– by adding it again or



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.

Actions Adding Application Nodes

60 Management Tool

8.2 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 choosen server.

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 Chassis Slot Slot number of the server blade

Adding Blade Server Chassis Actions

Management Tool 61

8.3 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

If you delete a blade server chassis the corresponding servers still exist.

You can delete a server by right clicking on it and choosing Delete or you can assign it to another existing blade server chassis by left clicking on Connector in the object tree entry of the server and choosing a new chassis slot corresponding to another blade server chassis.

8.4 Adding Control Stations The action for adding a control station is only available with NS-Type NAS storage de-vices. It is carried out directly, no dialog box is opened. Max. 2 control stations can be present.

Actions Adding Data Movers

62 Management Tool

8.5 Adding Data Movers 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 Data Mover

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.

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 can be set to true.

Adding Data NICs Actions

Management Tool 63

8.6 Adding Data NICs 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

8.7 Adding External Connectivities (Pool-specific) 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 table:

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.

Host Name Host name of the external device. Client LAN Storage LAN Server LAN Control LAN

Choice of the LANs witch 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

64 Management Tool

8.8 Adding LAN Interfaces The action for adding a LAN interface opens the following dialog box. Depending on the selected object, 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

8.9 Adding Mount Points for Volumes The action for adding a mount point for a volume opens the following dialog box.

Mount Point Mount path of the volume. Volume Path Path name of the volume.

Adding NAS Systems Actions

Management Tool 65

8.10 Adding NAS Systems Depending on the NAS system, the action for adding a NAS system opens one of the following dialog boxes.

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.

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.

Number of NICs Number of Network Interface Cards (2-6). Number of CSs Number of control centers (1-2). Number of Active DMs Number of active data movers (1-6). Number of Passive DMs Number of standby data movers (0-6).

The sum of active and passive data movers cannot be higher than 6.

Actions Adding Pool Groups

66 Management Tool

8.10.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 can not 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 data-mover 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.

8.11 Adding Pool Groups The action for adding a pool group opens the following dialog box.

Pool Host name of the pool. Group Name Associated group.

Adding Pools Actions

Management Tool 67

8.12 Adding Pools The action for adding a pool opens the following dialog box.

Pool Name Name of the new pool. The name must start with a letter and may only contain numbers, letters and “-“. The pool name becomes part of an automatically generated host name that may only be up to 13 characters long in an SAP environment. Therefore, we recommend that the pool name should be limited to three characters and written in lower case letters.

Group Name Name of the first group within the pool. The name must start with a letter and may only contain numbers, letters, “_“ or “-“.

DNS Domain Name DNS domain name for the pool. The name has to be conform to RFC1035. This means, the do-main 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 conform to RFC1035 (see above).

Actions Adding SAP Instances

68 Management Tool

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.

The information on the Control LAN is taken over from the first pool.

8.13 Adding SAP Instances The action for adding a SAP instance opens the following dialog box.

Service Type Instance type. Instance No. Instance number.

Adding SAP Services Actions

Management Tool 69

8.14 Adding SAP Services The action for adding a SAP service opens the following dialog box with two tabs for different service types.

The dialog box for the LiveCache service type (LC) is widely conform to the dialog box above. The only differences are the missing fields Configuration and Number of Instances.

SID SAP system ID (up to three characters, in ac-cordance with SAP rules).

Oracle SID Specific User IDs

SAP DB SID Specific User IDs

DB2 SID Specific UIDs and GIDs

SID specific user IDs and group IDs (depending on the choosen DB type).

Pool Name of the associated pool. Configuration Configuration type of SAP instances. DB Type and Version Type and version of the database. SAP Version SAP version. Number of Instances Number of SAP instances.

Actions Adding Switches

70 Management Tool

8.15 Adding Switches The action for adding a switch opens the following dialog box.

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.

8.16 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.

Adding Switch Ports Actions

Management Tool 71

8.17 Adding Switch Ports The action for adding a switch port is carried out directly, no dialog box is opened.

8.18 Adding Volumes The action for adding a volume opens the following dialog box.

NAS Device Name of the NAS system witch 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 already existing, you have to delete the corresponding volumes by right-clicking on the volume and choosing Delete and adding 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 8.9, like you did it with the original volume earlier.

Management Tool 73

9 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

FTP File Transfer Protocol

IP Internet Protocol

IPMP IP Multipathing

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

74 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

PCL PRIMECLUSTER

PFS Production File System (on Celerra)

PW PRIMEPOWER

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

SPOC Single Point Of Control

Abbreviations

Management Tool 75

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 77

10 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 operat-ing 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

78 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 land-scape 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 in-tegrate 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 Fu-jitsu Siemens Computers.

Glossary

Management Tool 79

FlexFrameTM for SAP® FlexFrameTM for SAP® is a radically new architecture for SAP environments. It ex-ploits 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 soft-ware.

Gigabit Ethernet A Local Area Network which supports data transfer rates of 1 gigabit (1,000 mega-bits) per second.

Host name The name of a node (assigned to an interface) that is resolved to a unique IP ad-dress. 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 environ-ment host names are case-sensitive.

Image In the FlexFrame documentation, “Image” is used as a synonym for “Hard Disk Im-age”.

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 con-nected 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

80 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 physi-cally 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 Pro-tocol (NDMP).

Netboot A boot procedure for computers where the operating system is provided via a net-work 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 81

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 compo-nents.

Preboot Execution Environment An environment that allows a computer to boot from a network resource without hav-ing a local operating system installed.

PRIMECLUSTER Fujitsu Siemens Computers high-availability and clustering software.

PRIMEPOWER

Fujitsu Siemens Computer's SPARC-based server product line.

PRIMERGY

Fujitsu Siemens Computer'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.

Glossary

82 Management Tool

Server A physical host (hardware), same as node.

Service A software program providing functions to clients.

Service type The type of an application or service (db, ci, app, agate, wgate etc.).

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 envi-ronment (FlexFrame), a process can be moved between hardware nodes while stay-ing transparent to the user and application.

Management Tool 83

11 Index A

abbreviations 73

actions

add application node 60

add control station 61

add data mover 62

add data NIC 63

add external connectivity 63

add group 66

add LAN 64

add mount 64

add NAS 65

add pool 67

add SAP instance 68

add SAP service 69

add switch 70

add switch group 70

add switch port 71

add volume 71

overview 57

application node

add 60

application nodes view 45

B

BX630 model based servers 47

C

chassis object 39

Client VLAN 7

configuration

create 15

edit 22

modify 20

print 22

save 21

validate 23

control center object 31

control station

add 61

Control VLAN 7

controlling view 44

D

data mover

add 62

data NIC

add 63

document history 2

E

external connectivity

add 63

external connectivity view 54

F

FlexFrame object 30

functions

edit 22

Index

84 Management Tool

IP addresses

reset all 27

new configuration 15

open configuration file 20

open LDAP connection 18

perform wiring 23, 25

print 22

save 21

validate configuration 23

G

general information view 42

global connectivity object 40

global connectivity, generate 25

glossary 77

group

add 66

H

host names 7

host parts of IP addresses, generate 27

I

IP addresses

reset 27

L

LAN

add 64

LAN failover 5

LAN trunking 5

M

menu functions 15

mount

add 64

N

NAS

add 65

NAS details view) 48

network concept 5

network object 33

network wiring plan, generate 23

new configuration 15

notational conventions 2

NTP master server 32

O

open configuration file 20

open LDAP connection 18

P

Planning Tool

exit 9

screen layout 10

starting 9

pool

add 67

pool / SID mount view 49

pools object 36

pools view 43

Q

QoS (Quality of Service) 7

R

related documents 3

Index

Management Tool 85

S

SAP instance

add 68

SAP service

add 69

SAP services view 51

Server VLAN 7

storage object 35

Storage VLAN 7

structured object tree 29

switch

add 70

switch group

add 70

switch port

add 71

switch ports 54

switches 7

T

tabs

volumes 49

tagged VLAN 54

V

view area 41

virtual host names) 53

virtual IP addresses 53

VLAN

host names 7

segments 6

VLAN IDs 54

volume

add 71

volumes (tab) 49

volumes view 49

W

wiring view 55

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Compu-ters. This new subsidiary of Fujitsu has been renamed Fujitsu Technology So-lutions.

This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed.

Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions.

Contact and support addresses will now be offered by Fujitsu Technology So-lutions and have the format …@ts.fujitsu.com.

The Internet pages of Fujitsu Technology Solutions are available at http://ts.fujitsu.com/... and the user documentation at http://manuals.ts.fujitsu.com.

Copyright Fujitsu Technology Solutions, 2009

Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seit-dem den Namen Fujitsu Technology Solutions.

Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion.

Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind.

Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Form …@ts.fujitsu.com.

Die Internetseiten von Fujitsu Technology Solutions finden Sie unter http://de.ts.fujitsu.com/..., und unter http://manuals.ts.fujitsu.com finden Sie die Benutzerdokumentation.

Copyright Fujitsu Technology Solutions, 2009