FlexFrame for SAP 4.1A

User Guide English FlexFrame for SAP 4.1A Planning Tool

FlexFrame for SAP Version 4.1A Planning Tool Edition April 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 countries 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 is a registered trademark of MySQL AB, Sweden MySQL is a registered trademark 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 countries Ethernet is a registered trademark of XEROX, Inc., Digital Equipment Corporation and Intel Corporation Windows, Excel 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.

Contents 1 Introduction...1 2 Network Concept...3 2.1 LAN Failover...3 2.2 LAN Trunking...3 2.3 VLAN Segments...4 2.4 Switches...5 3 Working with the Excel Spreadsheet...7 3.1 Requirements...7 4 General Information Form...9 4.1 Start new Button...10 4.2 Check data & generate config files Button...12 5 Pools Form...13 5.1 Add new pool Button...14 5.2 Delete selected pool Button...15 6 Pool Group Form...17 6.1 Add new group Button...18 6.2 Delete selected group Button...18 6.3 Change selected group Button...19 6.4 Sort groups Button...19 7 Pool Volumes Form...21 7.1 Add Pool to Volume Relationship Button...22 7.2 Delete Pool to Volume Relationship Button...22 8 Pool Specific UID and GID Form...23 8.1 Add UIDs GIDs Button...23 8.2 Delete selected entry Button...24 8.3 Modify selected entry Button...24 9 Controlling Form...25 9.1 Edit host part of selected IP Button...27 9.2 Add new Button...27 9.3 Delete selected Button...27 9.4 Change HW ID Button...28 9.5 Change switch group Button...28 10 NAS Configuration Details Form...29 10.1 Definition of an EMC NAS System...30 Planning Tool

Contents 10.1.1 EMC NAS Naming Conventions in the Wiring Plan... 30 10.2 Add new Button... 32 10.3 Delete selected Button... 32 10.4 Change switch group Button... 33 10.5 Change NICs & cluster partner Button... 33 11 NAS Volumes Form... 35 11.1 Add new Button... 36 11.2 Delete selected Button... 36 12 Switch Groups Form... 37 12.1 Change selected switch type Button... 39 13 External Connectivity Form... 41 13.1 Add new Button... 43 13.2 Delete selected Button... 43 13.3 Change switch group Button... 44 14 Application Nodes Form... 45 14.1 Add new Button... 47 14.2 Delete selected Button... 48 14.3 Change switch group Button... 48 14.4 Change OS Button... 49 14.5 Change pool/group of selected item Button... 49 14.6 Edit host part of selected IP Button... 50 14.7 BX630 Model Based Servers... 51 15 SAP Services Form... 53 15.1 Add SID Button... 56 15.2 Delete selected SID Button... 57 15.3 Add new instance Button... 58 15.4 Delete selected instance Button... 58 15.5 Edit host part of selected IP Button... 58 16 SAP Volumes Form... 59 16.1 Add SID-to-Volume Relationship Button... 60 16.2 Delete SID-to-Volume Relationship Button... 60 17 Miscellaneous Form... 61 18 Abbreviations... 63 19 Glossary... 67 20 Index... 73 Planning Tool

Notational conventions Additional information that should be observed. Warning that must be observed. italics fixed font Names of input fields in Excel spreadsheets and dialog boxes. Names of Excel forms, dialog boxes, paths, files, commands and system output and buttons in Excel spreadsheets and dialog boxes. <fixed font> Names of variables Document history Document Version Changes Date 1.0 First Edition 2008-04-01 Related Documents FlexFrame for SAP Administration and Operation FlexFrame for SAP FA Agents - Installation and Administration FlexFrame for SAP Installation ACC 1.0 SP13 FlexFrame for SAP Installation Guide for SAP Solutions FlexFrame for SAP Installation of a FlexFrame Environment FlexFrame for SAP myamc.fa_logagent - Concept and Usage FlexFrame for SAP myamc.messenger FlexFrame for SAP Network Design and Configuration Guide FlexFrame for SAP Planning Tool FlexFrame for SAP Security Guide FlexFrame for SAP Technical White Paper FlexFrame for SAP Upgrading FlexFrame 3.2B or 4.0 to 4.1A PRIMECLUSTER Documentation ServerView Documentation Solaris Documentation SUSE Linux Enterprise Server Documentation Planning Tool

1 Introduction This manual describes how to work with the Excel spreadsheet FFPLAN.xls which enables the SAP Technical Consultant to enter all the necessary configuration data for a customer-specific FlexFrame environment on a Windows PC during the preparation phase and to create the configuration files and the network cabling plan. Please try to avoid using the FlexFrame Tool with having other Excel sheets open at the same time. Closing and saving can cause damages in these files. After the data has been entered it is checked for plausibility using the Check data & generate config files button (see page 12). If all the data has been entered correctly, it is stored in the following configuration files: ff_cn.conf ff_an.conf ff_services.conf ff_misc.conf The configuration files are stored on an external data medium (e.g. a USB stick) and later read in by the installation scripts during the initial installation of the FlexFrame Control Nodes. All the required FlexFrame configurations are implemented automatically using this configuration data. Among other things, the configuration files contain information on the: network switch configuration hosts services network boot parameters LDAP parameters DHCP parameters automounter parameters for file systems user and group parameters FlexFrame pool and group definitions SAP services database systems After the configuration files have been created, the network cabling plan is generated with a Perl script (ff_wiring.pl) on a LINUX based system where a PERL runtime environment is available. Planning Tool 1

Introduction The figure below illustrates the installation procedure. Figure 1: Installation procedure 2, Planning Tool

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 chapter Working with the Excel Spreadsheet on page 7. 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 IO data blocks 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 4), 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 group of Application Nodes in a FlexFrame environment 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 network 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. Planning Tool 3

Network Concept 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 important 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 segments. 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 environment with Linux-based Application Nodes. VLANs V4: Client V3: Control V2: Server V1: Storage Physical Network Layout & Virtual LANs per Pool Control Nodes and Linux Application Nodes (RX300S3), both Storage Types Cluster Interconnect Logical View: VLANs Control Node A (RX300S3) CF IPMI V1 V2 V3 V4 cip0 Bond 0 eth 1 eth 2 eth 4 Onboard PCIe-NIC PCIe-NIC LAN Port B GBit GBit Control Node B (RX300S3) CF IPMI V1 V2 V3 V4 Bond 0 cip0 eth 1 eth 2 eth 4 Onboard PCIe-NIC PCIe-NIC LAN Port B GBit GBit Control Station V3 EMC Celerra Data V1 Mover trunk cge0 cge1 NetApp Filer V1 V3 Bond: vif exa exb Application Node n Application Node 1 (RX300S3) IPMI V1 V2 V4 Bond 0 eth 1 eth 2 eth 4 Onboard PCIe-NIC PCIe-NIC LAN Port B GBit GBit Physical View: Redundant Connections Cisco Switch A Switchgroup Cisco Switch B Figure 2: Basic network segments of a typical FlexFrame environment 4, Planning Tool

Network Concept The following virtual network segments are mandatory for FlexFrame: Client VLAN (one for each pool) The purpose of the Client VLAN segment is to provide dedicated user connectivity to the SAP instances. This segment also allows administrators to access the Control Nodes. Control VLAN (one for all pools together) The Control VLAN segment carries all administrative communication for Remote View Service Board (RSB) and / or IPMI-Interfaces. Control LAN access to the Application Nodes is required for monitoring board (RSB) intervention. It may be redundant (doubled), depending on the server type (e.g. PRIMERGY BX300). Server VLAN (one for each pool) The Server VLAN segment is used for SAP instances to communicate with each other and with the databases. Storage VLAN (one for each pool) The Storage VLAN segment 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 to handle intense data traffic. 2.4 Switches Network switching components play a very important role within FlexFrame. Therefore, only the following switches are tested and supported: Cisco Catalyst 3750G 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). Planning Tool 5

3 Working with the Excel Spreadsheet The spreadsheet comprises a number of forms which are described in the order in which they are generally processed. These forms contain input fields (yellow background) output fields (green or white background) buttons (gray background) that open dialog boxes to enter parameters If you click on the OK button in a dialog box, a semantics check and plausibility check of the parameter values is performed. If errors are detected, a message is shown and the dialog box remains open so that the incorrect entries can be corrected. In this manual, fields which permit entries are written in italics. Before you begin working with the Excel spreadsheet, you should create a backup copy of the original Excel file. As the workbook initially contains an example, the existing table contents must be deleted for a concrete configuration. This is done using the Start new button in the General Information form (see page 10). The spreadsheet only works correctly if Excel macros are activated. Excel functions (such as manual execution of functions) and foreign macros should not be used, otherwise errors can occur in the functionality. The functionality of the spreadsheet can be seriously damaged, by using functions like cut and paste. Don t use this functionality, because errors caused by using cut and paste are not visible directly. The generated files can contain incorrect data under these circumstances. 3.1 Requirements This document is only to be used by SAP Technical Consultants who have successfully completed FlexFrame, PRIMECLUSTER and Network Appliance Filer training. They should also have expert knowledge of Linux OS and 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. Planning Tool 7

4 General Information Form General information is entered in this form. These entries are also contained in the generated configuration files as comment lines. Figure 3: General Information Form Input fields Name Customer Project name Contact person Content provided by Date Last data export Comments Description Name of the customer Name of the customer project Customer contact Contact at Fujitsu Siemens Computers (the responsible person for the content) Entry date (Format: DD.MM.YYYY) Date of the last export of configuration files (Format: DD.MM.YYYY / hh:mm:ss) Arbitrary comments (appears not in configuration files) Planning Tool 9

General Information Form 4.1 Start new Button This button initializes all forms, i.e. all preceding data is deleted, and opens the Enter First Pool dialog box in which the information for the first pool of a FlexFrame environment is specified. As the workbook is initially filled with an example, the existing table contents must be deleted for a concrete configuration using the Start new button after a backup copy of the original Excel file has been created. Figure 4: Enter First Pool Dialog Box 10, Planning Tool

General Information Form Input/output fields Name Enter first pool name Enter first group name Client LAN Network Server LAN Network Storage LAN Network Control LAN Network Client LAN Netmask Server LAN Netmask Storage LAN Netmask Control LAN Netmask Client LAN VLAN ID Server LAN VLAN ID Storage LAN VLAN ID Control LAN VLAN ID Select Control Node type Power Control Type Select Filer type Enter first switch group name Enter DNS domain name Description The first pool name has to be specified in this field. 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. The name for the first group of the first pool has to be specified in this field. The name must start with a letter and may only contain numbers, letters and _ or -. The relevant network has to be specified in IPv4 format (e.g. 10.3.100.0) in this field. 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. The relevant netmask has to be specified in IPv4 format (e.g. 255.255.255.0) in this field. 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. The relevant VLAN ID has to be specified in this field. The VLAN ID is an integer between 2 and 4094. The VLAN IDs must be unique over all LAN segments. The associated Control Node type has to be selected in this pick list. Display of the power control type which belongs to the Control Node. The associated Filer type has to be selected in this pick list. The name of the first switch group has to be specified in this field. The DNS domain name has to be specified in this field (alphanumeric,. and - are allowed - e.g. dns1.fsc.com) no more checks available. Planning Tool 11

General Information Form 4.2 Check data & generate config files Button After all the data has been entered in the forms described below, this button is used to open the Generate Configuration Files dialog box where you can specify the path names for the configuration files to be created. Figure 5: Generate Configuration Files Dialog Box Check routines are called using the OK button. If these check routines do not report an error, the configuration files are generated automatically. If there are errors, these are displayed in the Checking results display field and can be exported to a log file (text file) by clicking on the Generate result Log button. This information can then be used to correct the errors in the forms. Under Saving to you can use the... button to select the path where the configuration files and the log file are to be saved. The configuration files may not be modified by applications of third-party suppliers (e.g. MS Word ) as this might cause the installation procedure and subsequent functions to fail. All the generated files belong together and may only be processed further or forwarded as a unit. The overall configuration can be printed out for documentation purposes using the Print all sheets button. All prints contain a hint that no corresponding configuration files where generated with the print. The time stamp of the files can be found in the header of every print out. This button is only enabled, if generating of the files is successful. 12, Planning Tool

5 Pools Form In this form, the features for a pool are defined. A pool is a group of Application Nodes in a FlexFrame environment which belong to the same customer. This is, for example, the customer of a service provider who has a number of systems made available to him/her to use exclusively. A pool contains multiple systems and is separated and protected from other pools by different network addresses and access controls. Servers within a group can take over services. Pools are of central importance and have to be defined first. For example, the pool name is used as a selection criterion in the Controlling, Application Nodes, SAP Services and External Connectivity forms (e.g. for calculating the client IPs). Figure 6: Pools Form (left half) Figure 7: Pools Form (right half) The current parameters of the pools which already exist are displayed in the form s output fields. Planning Tool 13

Pools Form 5.1 Add new pool Button This button opens the Enter New Pool dialog box in which the parameters for a new pool in the FlexFrame configuration are specified. If the parameters of an existing pool are to be modified, this pool must first be deleted using the Delete selected pool button (see page 15) and then be recreated using Add new pool. Figure 8: Enter New Pool Dialog Box Input fields Name Enter new pool name Enter group name Description The name of the new pool has to be specified in this field.the name must start with a letter and may only contain numbers, letters and -. As the pool name becomes part of an automatically generated host name and host names may only be up to 13 characters long in the SAP environment, we recommend that the pool name should be limited to three characters and written in lower case letters. The name for the first group of the new pool has to be specified in this field. The name must start with a letter and may only contain numbers, letters and _ or -. 14, Planning Tool

Pools Form Name Client LAN Network ServerLAN Network Storage LAN Network Client LAN Netmask Server LAN Netmask Storage LAN Netmask Client LAN VLAN ID Server LAN VLAN ID Storage LAN VLAN ID Select Filer type Enter DNS domain name Description The relevant network has to be specified in IPv4 format (e.g. 10.3.100.0) in this field. In binary terms the network must contain a zero at the same position in the individual LAN segments as the associated netmask. The individual networks must be different. The relevant netmask has to be specified in IPv4 format (e.g. 255.255.255.0) in this field. 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. The relevant VLAN ID has to be specified in this field. The VLAN ID is an integer between 2 and 4094. The VLAN IDs have to be unambiguous over all LAN segments. The associated first Filer of the new pool has to be selected in this pick list (only existing Filer from Filer Details are shown). The DNS domain name has to be specified in this field (alphanumeric,. and - is allowed - e.g. dns1.fsc.com) - no more checks available. The information on the Control LAN is taken over from the first pool. If the pool shall be equipped with Application Nodes of type BX600 (blade server in a blade server cabinet with switch blades of type Quanta, see Application Node Form), then the following restriction concerning the VLAN-ID has to be considered: Quanta switch blades only allow the VLAN ID range from 1 to 3965! 5.2 Delete selected pool Button The pool selected in the form can be deleted using this button. After a security prompt the selected pool and all associated components in the other forms are deleted. Exceptions: If this pool was entered in the Application Nodes form, the pool is not deleted. To prevent inconsistencies, the corresponding entries Application Nodes must be edited first. The first pool cannot be deleted. If this is necessary, it can only be done using the Start new button (see page 10). Planning Tool 15

6 Pool Group Form The pool groups are managed in this form. A pool group is an additional grouping level within a pool. All Application Nodes with the same characteristics are included in a pool group, e.g. servers with the same operating systems or performance classes. At least one spare Application Node is expected per pool group. The internal check routines verify the existence of at least two Application Nodes. The parameters of this form are required only for Application Nodes. As each pool must contain at least one pool group, a pool group is automatically created for each new pool. Figure 9: Pool Group Form The existing pools and their groups are displayed in the output fields of the form. Planning Tool 17

Pool Group Form 6.1 Add new group Button This button opens the Add Pool Group dialog box where a new pool group can be created. Figure 10: Add Pool Group Dialog Box Input fields Name Select pool Enter group Description The associated pool has to be selected in this pick list. The name of the new pool group has to be specified in this field. The name must start with a letter and may only contain numbers, letters and _ or -. 6.2 Delete selected group Button You can use this button to delete the pool group selected in the form. The selected group is deleted after a security prompt. Exceptions: If an entry exists for this group in the Application Nodes, the group is not deleted. The last group of a pool cannot be deleted. 18, Planning Tool

Pool Group Form 6.3 Change selected group Button This button opens the Change Pool Group dialog box where the membership of a pool group to a pool can be changed. Figure 11: Change Pool Group Dialog Box Exceptions: If an entry exists for this group in the Application Nodes, the group membership is not changed. The membership of the last group in a pool cannot be changed. Input fields Name Select pool Enter group Description The associated pool has to be selected in this pick list. The name of the pool group to be moved has to be specified in this field. The name must start with a letter and may only contain numbers, letters and _ or -. 6.4 Sort groups Button This button enables the list to be sorted alphabetically in the form by pools and, within these, by pool groups. Planning Tool 19

7 Pool Volumes Form This form is used to manage all Pool to Filer volume relationships. Figure 12: Pool Volumes Form Output fields Name Pool Pool volume Log volume Description Pool name of the pool that the following entries are for. Volume where the pool specific data for this pool is held or - if the data is still held under /volff/pool-<poolname> on the OS filer. Volume where the pool specific saplog data for this pool is held or - if the data is under its default position. Data volume Volume where the pool specific sapdata for this pool is held or - if the data is under its default position. Every volume that is related to a pool has to be created on a NAS System as it is documented in the Installation Guide or in the Administration Guide. Planning Tool 21

Pool Volumes Form 7.1 Add Pool to Volume Relationship Button This button opens the Add Pool to Volume Relationship dialog box where a new Pool-to-volume relationship can be added. Only Pools that have not been associated to a Volume, yet, can be added. Figure 13: Add Pool to Volume Relationship Dialog Box Input fields Name Pool Pool volume Sapdata volume Saplog volume Description The Pool to be added has to be selected in this pick list (shows only pools where no Pool to Volume Relationship is defined yet). The associated Filer volume for the pool specific data volume has to be selected in this pick list (shows only Filers entered in the NAS Configuration Details form and having entries in Storage LAN in the Controlling form for this pool). The associated Filer volume for the sapdata volumes of this pool have to be selected in this pick list (shows only Filers entered in the NAS Configuration Details form and having entries for a Storage LAN in the Controlling form for this pool). The associated Filer volume for the saplog volumes of this pool have to be selected in this pick list (shows only Filers entered in the NAS Configuration Details form and having entries for a Storage LAN in the Controlling form for this pool). 7.2 Delete Pool to Volume Relationship Button Use this button to delete the selected relationship. 22, Planning Tool

8 Pool Specific UID and GID Form This form is used to manage user ids and group ids for all users and groups that might be necessary when installing and running the SAP services in the given pool. During installation the UID 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 UID and GIDs should be used in this form. Figure 14: Pool specific UID and GID Form 8.1 Add UIDs GIDs Button This button opens the Add Pool UIDs GIDs dialog box where you can enter a pool specific user ID for the user sdb, as well as a pool specific group ID for each of the the groups sapsys, dba, oper, sdba, and sapinst. If you do not enter a value in one of these fields, a default value will be used during installation. The installation manual gives you further information about the default values used. Planning Tool 23

Pool Specific UID and GID Form Figure 15: Add Pool UID GIDs Dialog Box 8.2 Delete selected entry Button You can use this button to delete the entry selected in the form. 8.3 Modify selected entry Button This button opens a dialog box like Figure 15 where you can modify the values of the selected pool. After editing, accept the modifications with OK or reject it with Cancel. 24, Planning Tool

9 Controlling Form This form is used to manage central, jointly used infrastructure components of a Flex- Frame environment such as the network, switches and Control Nodes (as central monitoring instance), and also the memory subsystem which, if required, is addressed via different networks (see also the Pools form on page 12). Figure 16: Controlling Form (left half) Figure 17: Controlling Form (right half) Planning Tool 25

Controlling Form Input/output fields Name Controlling/Shared Equipment Host name Description General host name which is required to form the host names of the individual LAN segments. In SAP environments host names are currently limited to 13 alpha numeric characters including the hyphen ( - ). The first character must be a letter. In an SAP environment host names are case-sensitive. Type Display of the type of component inserted. HW ID Display of the HW ID of component inserted (will be created automatically and can only be changed for Filer). Switch Group LAN Section Host Display of the related switch group of component inserted (can be changed if defined by administrator). An IPv4 address consists of the two parts; network and host. With its 1 bits, the netmask defines the network part and its 0 bits at the end define the host part. The network numbers for the individual segments have been specified before when the pool was entered. The host part is entered for each individual component here, e.g. (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 LAN Section Pool Display of the associated pool. In the other output fields the host names, IP addresses and interfaces of the Client LANs, Storage LANs, Server LANs and Control LANs are displayed. In the current release of the spreadsheet, the Interface fields are used for documentation purposes only and are not written to the configuration files. Therefore, the settings can be different in the actual configuration. This is not an error. 26, Planning Tool

Controlling Form On the Control Nodes the interface name in the Control LAN is bond0 or RSB. The interface name in the other VLANs it is derived from vlan extended by the VLAN ID. In the case of all other components no interface names are formed, while the IP addresses are generated. All IP addresses are derived from the pool s network IP and the specified host number, taking the netmask into account. All new physical Filer systems have to be defined in the NAS Configuration Details form first! 9.1 Edit host part of selected IP Button For a description how to assign an individual host part to the the IP addresses see the corresponding description in the Application Nodes form (see page 49). 9.2 Add new Button This button opens the Add Controlling Component dialog box where a controlling component can be added. Only entries of the type Filer, Switch Group and Remote Console Adapter (RCA) can be added. Figure 18: Add Controlling Component Dialog Box Input fields Name Select pool Select type Description The associated pool has to be selected in this pick list. The controlling component to be added has to be selected in this pick list. 9.3 Delete selected Button You can use this button to delete the selected controlling component of the type Filer, Switch Group or Remote Console Adapter. The last Filer of a pool can not be deleted. Planning Tool 27

Controlling Form 9.4 Change HW ID Button This button opens the Change HW ID dialog box where the hardware ID of the selected Filer can be changed. Only entries of the type Filer can be changed. A single hardware ID can be used only once in a pool. To add new hardware IDs see NAS Configuration Details form. Figure 19: Change HW ID Dialog Box Input field Name HW ID Description The associated hardware ID has to be selected in this pick list. Only entries of the NAS Configuration Details form are shown. 9.5 Change switch group Button This button opens Change Switch Group dialog box where the associated switch group of the selected item can be changed. The switch group of only a few item types can be changed (defined by the administrator). Figure 20: Change Switch Group Dialog Box Input field Name Select SWG Description The associated switch group has to be selected in this pick list. 28, Planning Tool

10 NAS Configuration Details Form This form is used to manage all physical Filer systems. Figure 21: NAS Configuration Details Form Input/output fields Name HW ID Filer name Host Description Display of the hardware ID (automatically generated). General host name which is required to form the host names of the individual LAN segments. In SAP environments currently host names are limited to 13 alpha numeric characters including the hyphen ( - ). The first character must be a letter. In the SAP environment host names are casesensitive. For Filer names only lower case letters should be used because upper case letters will result in serious problems when applying administration commands later. An IPv4 address consists of the two parts; network and host. With its 1 bits, the netmask defines the network part and its 0 bits at the end define the host part. The network numbers for the individual segments have been specified before when the pool was entered. The host part is entered for each individual component here, e.g. (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 Filer type Display of the Filer type to be used. # NICs Display of the hardware ID of components inserted (will be created automatically and can only be changed for Filer). Switch Group Display of the switch group for the component inserted (can be changed if defined by the administrator). Planning Tool 29

NAS Configuration Details Form Name Cluster partner / NS-Type: Grp ID Description For EMC NAS systems (Filer type: NS-Type) this field shows a group ID which identifies with the same group ID all data movers of a EMC NAS system that belong together. The group ID is gene-rated by the the planning tool. For other NAS (Netapp filers) systems the field displays the hardware ID of the cluster partner ( 0 if no cluster partner exists). The remaining output fields display the host names, IP addresses and interfaces in the Control LAN. With the current state of the spreadsheet, the interface field is used for documentational purposes only and can be different in the actual application. This is not an error. 10.1 Definition of an EMC NAS System Every data mover (active and standby) of a EMC NAS system has an entry in the NAS Configuration Details form in form of a row. You add an EMC NAS system by choosing an NS-Type filer in the Add new dialog of this form and enter the number of data movers. The automatically generated NS-Type Grp Id in the related column groups data movers for one EMC NAS system together. For every data mover a control LAN IP has to be defined. If there are more data movers than control stations you will have control LAN IPs that are obsolete. In the Controlling form you have to define a storage LAN IP for every active data mover of a Celera. Data movers of a EMC NAS system without any storage LAN IP will be considered as standby data movers. In the External Connectivity form you are able to define any other control LAN address needed, e.g. Storage Processor or FC Switch. The control LAN addresses defined here will have a switch port reserved for access to this LAN. For further details see the Switch Groups and External Connectivity forms. 10.1.1 EMC NAS Naming Conventions in the Wiring Plan The name of the first data mover in the field Filer name of the NAS Configuration Details form (see Figure 22) is of special interest. The first data mover name is also the name that identifies the complete EMC NAS system. By this name, in our example cel1-dm1, the EMC NAS system will also be identified in the wiring plan as well as later, when administrating a FlexFrame, this will be the name to access this EMC NAS system. An EMC NAS system assigns to its data movers default names. The control station is called server_1, the first data mover is called server_2, the second data mover is called server_3 and so on. These default names of an EMC NAS system usually are not changed. In the wiring plan (see Figure 23) you will also find for your convenience the 30, Planning Tool

NAS Configuration Details Form data mover names from the NAS Configuration Details form next to the default names of the EMC NAS system. Furthermore for the convenience of the PlanningTool user the data mover names can be used in the PlanningTool as you would use the names of NetApp filers, which means you can assign in the Controlling form to every data mover a set of Storage Lan addresses. For every pool that accesses data on this data mover one address. As already earlier mentioned a data mover with no Storage Lan address will be considered a standby data mover. Figure 22: NAS Details Configuration Sheet defining an EMC NAS system with three datamovers Switch Group 1 Sw.ID / Port / Media Name (Sys.type): target port cat3750g-48ts 1 / 9 / TX-Cat5 cel1-dm1 (NS-Type DM server_2/cel1-dm1): port "data NIC-1" 1 / 10 / TX-Cat5 cel1-dm1 (NS-Type DM server_3/c1dm2): port "data NIC-2" 1 / 11 / TX-Cat5 cel1-dm1 (NS-Type DM server_4/c1dm3): port "data NIC-2" 1 / 43 / TX-Cat5 cel1-dm1-co (NS-Type): port "mgmt NIC-1" cat3750g-48ts 2 / 9 / TX-Cat5 cel1-dm1 (NS-Type DM server_2/cel1-dm1): port "data NIC-2" 2 / 10 / TX-Cat5 cel1-dm1 (NS-Type DM server_3/c1dm2): port "data NIC-1" 2 / 11 / TX-Cat5 cel1-dm1 (NS-Type DM server_4/c1dm3): port "data NIC-1" Figure 23: Wiring Plan Planning Tool 31

NAS Configuration Details Form 10.2 Add new Button This button opens the Add NAS Details dialog box where a new filer can be added. Figure 24: Add NAS Details Dialog Box Input fields Name Select type Select SWG Number of NICs Number of DMs Description The Filer type to be added has to be selected in this pick list. The associated switch group has to be selected in this pick list. The Filer to be added is associated to an existing switch group. The number of Network Interface Cards has to be specified in this field (between 2 and 8). This field is only activated when you select an NS-Type filer. An NS- Type filer is an EMC NAS system. In this field you have to enter the number of data movers of the selected EMC NAS system. For every EMC NAS system a group ID will be generated and this ID will be assigend to all the data movers of this system. You have to enter all available data movers of the EMC NAS system, the active data movers and even the standby data movers. 10.3 Delete selected Button You can use this button to delete the selected Filer. If the selected Filer is used in the Controlling form, the deletion will be aborted. 32, Planning Tool

NAS Configuration Details Form 10.4 Change switch group Button This button opens the Change Switch Group dialog box where the switch group associated with the selected item can be changed. Figure 25: Change Switch Group Dialog Box Input field Name Select SWG Description The associated switch group has to be selected in this pick list. 10.5 Change NICs & cluster partner Button This button opens the Change NAS Details dialog box where the associated cluster partner (HW ID) and the number of Network Interface Cards of the selected Filer can be changed. Figure 26: Change NAS Details Dialog Box Input fields Name Count of NICs Cluster HW ID Description The number of Network Interface Cards has to be specified in this field (between 2 and 8). The associated hardware ID of the cluster partner has to be selected in this pick list ( 0 if no cluster partner exists). If the selected partner is already associated with another Filer, an error is displayed). Planning Tool 33

11 NAS Volumes Form This form is used to manage all Filer volumes. Figure 27: NAS Volumes Form Output fields Name HW ID Filer Name Volume No Volume Name Description Display of the hardware ID. Display of the name of the selected Filer. Display of the number of the entered volume. Display of the name of the entered volume (max 32 signs, only letters and numbers, have to start with a letter, volff is not allowed). Planning Tool 35

NAS Volumes Form 11.1 Add new Button This button opens the Add Filer Volume dialog box where a Filer volume can be added. Figure 28: Add Filer Volume Dialog Box Input fields Name Select filer Description The Filer containing the volume to be added has to be selected in this pick list (shows only Filer entered in the NAS Configuration Details form and having entries in Storage LAN in the Controlling form). Enter volume no The volume number for the volume to be added has to be entered in this field. Enter volume name The volume name for the volume to be added has to be entered in this field (max 32 signs, only letters and numbers, have to start with a letter, volff is not allowed). 11.2 Delete selected Button You can use this button to delete the selected volume. If the selected volume is used in the SAP Volumes form, the deletion will be aborted. 36, Planning Tool

12 Switch Groups Form In this form the switch types actually used are assigned to the switch groups. The switch groups themselves can be defined in the Controlling form (see page 25). 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. Figure 29: Switch Groups Form During configuration only lines that contain entries in the Switch Type field are taken into account. Planning Tool 37

Switch Groups Form Input/output fields Name Distribute corporate LAN ports to different switch groups Use Fiber Optic port to corporate LAN Separate VLANs to corporate LAN Port count of switch group interconnects Group Type Switch Type Description When X is set, the corporate network cabeling is connected to the switches of the first two switch groups. When X is not set the corporate network is connected to the switches of the first switch group only. When X is set, the fibre optic ports of the switches are used for the connection to the corporate network if possible (among those connections is the client network for the SAP users). If multiple pools are used, multiple Client VLANs must be connected to the corporate network. This option allows you to select whether one (for all VLANs common) corporate network port is to be provided for all Client LANs (X not set) or if ports (X set) are provided for each Client VLAN. Number of ports that are provided for the switch group interconnect. Display of the switch group name as assigned in the Controlling form. Display of the type of switch group (for documentation purpose only). Display of the switch type of each switch within the group (required for the cabling and the switch configuration). Knowledge of the precise name of each switch type is required to create the cabling plan and the switch configurations. At least two switches have to be configured in each switch group to provide network redundancy. The upper limit is currently eight switches. To select a switch the cursor has to be positioned to the relevant line in the form and the switch type required has to be selected and modified using the Change selected switch type button. 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 my be connected directly. 38, Planning Tool

Switch Groups Form Node Node FlexFrame Switch Group 1 FlexFrame Switch Group 2 Node Node Uplink Channel Uplink Channel Node Node Customer own Core Switch Customer Corporate LAN Customer own Core Switch Node Figure 30: Structure and Connection of Switch Groups 12.1 Change selected switch type Button This button opens the Change Switch dialog box where the switch type of the entry selected in the form can be changed. Existing entries can be deleted using the last option (empty field). Figure 31: Change Switch Dialog Box Planning Tool 39

13 External Connectivity Form The network connections of the internal FlexFrame networks to the operator s corporate network are defined in this form. Entries in the various LAN segments may, for example, be necessary for backup servers or servers outside the FlexFrame environment. With the Planning Tool a so called External Connectivity can be planned. It leads to configuration of switch ports. The external connectivity switch ports are currently configured as untagged VLAN switch ports in case of a single VLAN. In case of multiple VLANs, all will be configured as tagged. Devices plugged into these ports require interfaces using tagged VLANs. To be able to communicate, these VLANs have to be configured with the same VLAN IDs like the switch port and as configured with the Planning Tool. For reasons of redundancy, two switch ports are configured for each externally connected device. 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. A link aggregation for load balancing will not work and may block the entire network! The saprouter that may run on the Control Node for the first pool as part of PRIMECLUSTER has its own IP address. Therefore an entry for the saprouter should be given here (type Other). The host name saprouterint is reserved for that purpose and has to be entered for the Client LAN. In this case no entries are required for the Storage or Server LAN. The host name (and at least one host name in the Client, Storage, Server LAN or Control LAN) has to be entered in each line. Figure 32: External Connectivity Form (left half) Figure 33: External Connectivity Form (right half) Planning Tool 41

External Connectivity Form Input/output fields Name External Connectivity Comment Description Description of the connection to the external component. Type Display of the type of component inserted. Switch Group LAN Section Host Display of the related switch group of component inserted (can be changed if defined by administrator). An IPv4 address consists of the two parts; network and host. With its 1 bits, the netmask defines the network part and its 0 bits at the end define the host part. The network numbers for the individual segments have been specified before when the pool was entered. The host part is entered for each individual component here, e.g. (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 LAN Section Pool Client LAN Host name Storage LAN Host name Server LAN Host name Control Lan Host name Client LAN IP Storage LAN IP Server LAN IP Control LAN IP Display of the associated pool. The host names of the relevant LAN. These host names are visible outside FlexFrame. A maximum of 13 alphanumeric characters, including the hyphen, in lower case may be used here. The first character must be a letter. The other FlexFrame formation rules for host names do not apply here. Display of the IP address of the relevant LAN. 42, Planning Tool

External Connectivity Form 13.1 Add new Button This button opens the Add External Connectivity dialog box where a controlling component can be added. Figure 34: Add External Connectivity Dialog Box Input fields Name Select pool Select type Select SWG Description The associated pool has to be selected in this pick list. The controlling component to be added has to be selected in this pick list. The associated switch group has to be selected in this pick list. The Filer to be added has to be associated to an existing switch group. 13.2 Delete selected Button You can use this button to delete the selected controlling component. Planning Tool 43

External Connectivity Form 13.3 Change switch group Button This button opens the Change Switch Group dialog box where the associated switch group of the selected item can be changed. The switch group of only a few item types can be changed (defined by the administrator). Figure 35: Change Switch Group Dialog Box Input field Name Select SWG Description The associated switch group has to be selected in this pick list. 44, Planning Tool

14 Application Nodes Form In this form you manage the Application Nodes of the FlexFrame environment on which the SAP services run. Depending on the type of Application Node, one or more lines are inserted. 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 on this spreadsheet are used by FlexFrame system software. These host names are physical host names and may not be used by SAP applications. Host names for Application Nodes are generated automatically by this spreadsheet. Host names are differentiated by a suffix to permit an Application Node to be addressed via a selected VLAN segment. For the Storage VLAN this suffix is st, for the Server VLAN it is se, for the Control VLAN it is co, and for the Client VLAN no suffix is used. These host names are not restricted by SAP conventions like virtual host names (For virtual host names see also chapter SAP Services form on page 53). To provide network redundancy for PRIMEPOWER nodes with Solaris IPMP, additional test addresses are required. When they are created, these entries are added automatically as the types Solaris HA1 and Solaris HA2. Figure 36: Application Nodes Form (left half) Planning Tool 45

Application Nodes Form Figure 37: Application Nodes Form (right half) Input/output fields Name Description Application Nodes Host name General host name which is required to generate the host names in the individual VLAN segments. In SAP environments currently host names are limited to 13 alpha numeric characters including the hyphen ( - ). The first character must be a letter. In the SAP environment host names are case-sensitive. Type Auto No Switch Group OS Display of the type of component added. If automatic numbering is defined for this component in the options, the number is displayed in this field. This number is used internally, for example, to differentiate the individual chassis of BX systems. Display of the switch group corresponding to the inserted component (can be changed if defined by administrator). Display of the operating system of the selected component. 46, Planning Tool

Application Nodes Form Name LAN Section Host Description An IPv4 address consists of the two parts; network and host. With its 1 bits, the netmask defines the network part and its 0 bits at the end define the host part. The network numbers for the individual segments have been specified before when the pool was entered. The host part is entered for each individual component here, e.g. (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 LAN Section Pool Display of the associated pool. LAN Section Group Display of the associated pool group. In the other output fields the host names, IP addresses and interfaces of the Client LANs and Control LANs are displayed. In the current state of the spreadsheet the interfaces fields are used for documentation purposes and may differ from those shown. This is not an error. 14.1 Add new Button This button opens the Add Application Node dialog box where an Application Node can be added. Figure 38: Add Application Node Dialog Box Planning Tool 47

Application Nodes Form Input fields Name Select pool Select group Select type Select SWG Select OS Description The associated pool has to be selected in this pick list. The associated group has to be selected in this pick list. The Application Node to be added has to be selected in this pick list. The associated switch group has to be selected in this pick list. A valid operating system of the selected component has to be selected in this pick list. Within a group you may only configure servers that can replace each other in terms of their functionality and performance. This means, for example, that PRIMERGY and PRIMEPOWER Servers may not be configured in the same group. The FF Planning Tool does not validate these considerations. Each group must consist of at least two Application Servers. 14.2 Delete selected Button The selected Application Node can be deleted using this button. 14.3 Change switch group Button This button opens the Change Switch Group dialog box in which the associated switch group of the selected item can be changed. The switch group can be changed only for a few item types (defined by the administrator). Figure 39: Change Switch Group Dialog Box Input field Name Select SWG Description The associated switch group has to be selected in this pick list. 48, Planning Tool

Application Nodes Form 14.4 Change OS Button This button opens the Change OS dialog box where the operating system of the selected Application Node (multiple selection allowed) can be changed. Figure 40: Change OS Dialog Box Input field Name Select OS Description The associated operating system has to be selected in this pick list. 14.5 Change pool/group of selected item Button This button opens the Change Group dialog box where the pool and group membership of the selected Application Node can be changed. Figure 41: Change Group Dialog Box Input fields Name Select pool Select group Description The associated pool has to be selected in this pick list. The associated group has to be selected in this pick list. Planning Tool 49

Application Nodes Form 14.6 Edit host part of selected IP Button This button opens the Edit IP Host Part dialog box. Usually the Planning Tool generates IP addresses for its components from the given network addresses for each of the available LANs and a common host part. Since there is only one Control LAN for all components and because of the mapping of Control LAN on one side and Client, Server and Storage LAN addresses on the other side, it is possible to run into problems defining all of the Control LAN addresses needed. More flexible definition of IP addresses you can achieve, when you select the generated IP addresses you want to assign an individual host part to and press the button Edit IP Host Part. A dialog box opens that allows you to enter the new host part of the first of the selected IP addresses in the column. The new value is auto incremented and assigned to all selected IP addresses in sequence. When the host part of an IP address spans across byte boundery this is not respected by the auto incrementation algorithm. Editing across byte boundery is not possible. In this case you have to edit the IP addresses column in two steps. Figure 42: Edit IP Host Part Dialog Box Input/output field/button Name Old Value New Value Reset to common host part Description Current host part of the first of the selected IP addresses. New host part of the first of the selected IP addresses. The host part is reset to the value as it is defined in the column Host of the form. This feature of individual IP addresses for components is also implementet in the SAP Services form and the Controlling form. The description of these forms will refer to the description given here. 50, Planning Tool

Application Nodes Form 14.7 BX630 Model Based Servers BX630 model based server blades currently are available in three different versions occupying a different number of slots; this is true for the current models BX630 S2 and the older models BX630 as well: BX630 S2 dual occupies 1 slot with 1 server blade similar to e.g. BX620 S4 BX630 S2 quad occupies 2 slots with 2 server blades BX630 dual occupies 1 slot with 1 server blade BX630 quad occupies 2 slots with 2 server blades BX630 octo occupies 4 slots with 4 server blades 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 Planning Tool you only have to assign host name and IP to the master slot. The other slots are left empy. Figure 43: Example arrangement of BX630 S2 and BX630 Server Blades Figure 44: Planning Tool configuration for the above example arrangement Planning Tool 51

15 SAP Services Form All the SAP systems and their instances for a FlexFrame environment are entered in this form. The virtual host name and its corresponding virtual IP address are used by applications to address the server on which an SAP instance is running. This virtual IP address is assigned to a physical host dynamically before an SAP instance is started. The virtual IP address thus identifies the actual host on which the SAP instance is running on. If an SAP instance is moved to another server, this SAP instance is always addressable using the same virtual IP address. Virtual host IP addresses are also used for communication from applications outside FlexFrame systems, i.e. SAP front ends such as SAPGUI. Virtual host names and virtual IP addresses are generated automatically by the planning tool. Formation Rules for Virtual Host Names The virtual host name is formed by the service type, the two-digit instance number for the service type app and the SID: <service type>[<id>]<sid>[<-lan type>] where <service type> can be one of: 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> is an instance number from 00 to 96 (except 2, 25, 43, 72 and 89) for the service types. The instance number is unique in the SAP system scope. It is left empty for db and lc service types. <SID> is the 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 3.2 of the Flex- Frame solution. Some components rely on this rule. Planning Tool 53

SAP Services Form In a FlexFrame environment, each node name must be unique. However, each node may have multiple host names that are derived from the node name using a defined naming rule. In the SAP environment, host names are currently limited to 13 alphanumeric characters including the hyphen ( - ). The first character must be a letter. In the SAP environment host names are case-sensitive (see SAP Note No. 611361). Figure 45: SAP Services Form (left half) Figure 46: SAP Services Form (right half) 54, Planning Tool

SAP Services Form Input/output fields Name SAP Services SID Description Display of the SAP system ID. SAP Services Inst. No. Unique instance number a SAP system. Information has to be entered in this field otherwise an error is generated when the configuration files are created. Make sure that the instance number is unique in every single pool. SAP Services Service Type Display of the service type (see also Formation rules for the host name on the next page). SAP Services DB Type Display of the database type in the row of the db instance. SAP Services SAP Version UID for DB User UID for SAP User LAN Section Host Display of the SAP version in the row of the ci instance. User ID for the DB related SID specific user (e.g.: sqd<sid> or ora<sid>). User ID for the SAP related SID specific user (e.g. <sid>adm). An IPv4 address consists of the two parts; network and host. With its 1 bits, the netmask defines the network part and its 0 bits at the end define the host part. The network numbers for the individual segments have been specified before when the pool was entered. The host part is entered for each individual component here, e.g. (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 A value has to be entered in this field, otherwise an error will occur when generating the configuration files. LAN Section Pool Display of the associated pool. In the other output fields the virtual IP addresses and virtual host names of the Client LAN and Server LAN are displayed. Planning Tool 55

SAP Services Form It is automatically ensured that precisely one database instance and one central instance are contained for each SID. The instance numbers must be unique across all SIDs per pool. 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. 15.1 Add SID Button This button opens the Add SAP Service dialog box where an SAP system can be added. Figure 47: Add SAP Service Dialog Box 56, Planning Tool

SAP Services Form Input fields Name Enter SID SID specific user IDs Select Configuration Select Pool Select DB Type Select SAP Vers Enter count of ABAP instances Enter count of JAVA instances Description The SAP SID has to be specified in this field (up to three characters, in accordance with SAP rules). Every database (e.g. ora<sid>, sqd<sid>) and every SAP system (e.g. <sid>adm) has per SID a user assigned for administration purposes. This user you can assign a user ID. The configuration type of SAP instances has to be selected by activating a radio button. With the checkbox next to the radio button you can decide whether a separate ascs/ers instance is generated. The associated pool has to be selected in this pick list. The database type has to be selected in this pick list. The SAP version has to be selected in this pick list. The number of SAP ABAP instances to be added has to be specified in this field (default value is 4). The number of SAP java instances to be added has to be specified in this field (default value is 4). 15.2 Delete selected SID Button With this button the selected SAP system can be deleted completely. The selected SID can not be deleted, if an entry exists in SAP Volumes. Planning Tool 57

SAP Services Form 15.3 Add new instance Button This button opens the Select Instance Type dialog box where the type and the number of the application instances which have to be added can be selected. Figure 48: Select Instances Type Dialog Box Input fields Name Select Adding Type Enter count of application instances Description The instance type has to be selected in this pick list. The number of instances which have to be inserted has to be specified in this field. 15.4 Delete selected instance Button With this button the selected SAP instances can be deleted. 15.5 Edit host part of selected IP Button For a description how to assign an individual host part to the the IP addresses see the corresponding description in the Application Nodes form (see page 49). 58, Planning Tool

16 SAP Volumes Form This form is used to manage all SID to Filer volume relationships. Figure 49: SAP Volumes Form Output fields Name SID Pool Log volume Data volume Description Display of the SID from SAP Services. Dispplay of the SID of the associated pool. Display of the Filer/volume information for the log volume associated with the SID. Display of the Filer/volume information for the data volume associated with the SID. Planning Tool 59

SAP Volumes Form 16.1 Add SID-to-Volume Relationship Button This button opens the Adding SID to Volume Relationship dialog box where a new SID-to-volume relationship can be added. Only SIDs that have not been associated to a Volume, yet, can be added. If there are no more (free) SIDs form SAP Services available, a new SID has to be added in SAP Services or an existing relationship has to be deleted for changing. Figure 50: Adding SID to Volume Relationship Dialog Box Input fields Name Select SID Select log volume Select data volume Description The SID to be added has to be selected in this pick list. The associated Filer volume for the log volume has to be selected in this pick list (shows only Filers entered in the NAS Configuration Details form and having entries in Storage LAN in the Controlling form only in the right pool). The associated Filer volume for the data volume has to be selected in this pick list (shows only Filers entered in the NAS Configuration Details form and having entries in Storage LAN in the Controlling form only in the right pool). 16.2 Delete SID-to-Volume Relationship Button Use this button to delete the selected relationship. 60, Planning Tool

17 Miscellaneous Form In this form you can enter parameters concerning the Control Node and the network. Figure 51: Miscellaneous Form Input fields Name Cluster name Cluster IP1 / Cluster IP2 Cluster Netmask Description Name of the PRIMECLUSTER on the Control Nodes (by default set to FlexFrame). First and second IP address of the cluster (both should be in the same network segment). The cluster IP addresses IP1 and IP2 must be in a separate private network segment. At least four addresses are required for this network segment (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 Netmask of the cluster (defines the cluster s network part). For a description and example see Cluster IP1. Planning Tool 61

Miscellaneous Form Name DNS domain name DNS server LDAP Base DN NTP time servers TIME_ZONE Default router LDAP root user LDAP root password SNMP read only community name Description 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. IPv4 addresses for DNS Domain Server (separated by blanks). No entry is required for this field. If this field is left empty, fully qualified domain names outside of FlexFrame cannot be resolved by neither the Control Nodes nor the Application Nodes. The LDAP Base Distinguished Name is the root for the LDAP name space for this FlexFrame environment (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. The entry is not checked for plausibility! One or more Network Time Protocol Servers (IPv4 addresses separated by blanks). No entry is required in this field. If this field is left empty, the first Control Node becomes the NTP master server and the second Control Node will be a backup NTP server. Time zone of the FlexFrame environment to be installed. 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. Root user (default: root). Root password (default: password). SNMP read only community name (default: public). For PRIMEPOWER system the field DNS domain name has to be set. 62, Planning Tool

18 Abbreviations ABAP ACC ACI ACPI APM APOLC CCU CIFS DART DHCP DIT ERP ESF EULA FAA FC FTP IP IPMP LAN LDAP LUN MAC MINRA NAS NDMP NFS NIC Advanced Business Application Programming Adaptive Computing Controller Adaptive Computing Infrastructure Advanced Configuration and Power Interface Advanced Power Management Advanced Planner & Optimizer Life Cache Console Connection Unit Common Internet File System Data Access in Real Time Dynamic Host Configuration Protocol Domain Information Tree Enterprise Resource Planning Enhanced System Facility End User License Agreement FlexFrame Autonomous Agent Fiber Channel File Transfer Protocol Internet Protocol IP Multipathing Local Area Network Lightweight Directory Access Protocol Logical Unit Number Media Access Control Minimal Read Ahead Network Attached Storage Network Data Management Protocol Network File System Network Interface Card Planning Tool 63

Abbreviations NVRAM OBP OLTP ONTAP OSS POST PCL PFS PW PXE PY QA QS RAID RARP RDBMS RHEL RSB SCS SAP BW SAPGUI SAPOSS SID SLD SLES SMB SMC SNMP SPOC TELNET Non-Volatile Random Access Memory Open Boot Prom On-Line Transaction Processing Open Network Technology for Appliance Products Open Source Software Power-On Self Test PRIMECLUSTER Production File System (on Celerra) PRIMEPOWER Preboot Execution Environment PRIMERGY Quality Assurance Quality of Service Redundant Array of Independent (or Inexpensive) Disks Reverse Address Resolution Protocol Relational Database Management System Red Hat Enterprise Linux Remote Service Board System Console Software SAP Business Warehouse SAP Graphical User Interface SAP Online System Service System Identifier System Landscape Directory SUSE Linux Enterprise Server Server Message Block System Management Console Simple Network Management Protocol Single Point Of Control Telecommunications Network 64, Planning Tool

Abbreviations TFTP UDP UPS VLAN VTOC WAN WAS WAFL XSCF Trivial File Transfer Protocol User Datagram Protocol Uninterruptible Power Supply Virtual Local Area Network Virtual Table Of Contents Wide Area Network Web Application Server Write Anywhere File Layout Extended System Control Facility Planning Tool 65

19 Glossary Adaptive Computing Controller SAP system for monitoring and controlling SAP environments. Advanced Business Application Programming Proprietary programming language of SAP. Advanced Power Management Advanced Power Management defines a layer between the hardware and the operating system that effectively shields the programmer from hardware details. Application Agent A software program for monitoring and managing applications. Application Node A host for applications (e.g. SAP instances db, ci, agate, wgate, app etc.). This definition includes Application Servers as well as Database Servers. Automounter The automounter is an NFS utility that automatically mounts directories on an NFS client as they are needed, and unmounts them when they are no longer needed. Autonomous Agent Central system management and high availability software component of Flex- Frame. 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. Planning Tool 67

Glossary Common Internet File System A protocol for the sharing of file systems (same as SMB). Computing Node From the SAP ACI perspective: A host that is used for applications. Control Agent A software program for monitoring and managing nodes within FlexFrame. Control LAN Virtual network segment within FlexFrame, used for system management traffic. Control Node A physical computer system, controlling and monitoring the entire FlexFrame landscape and running shared services in the rack (dhcp, tftp, ldap etc.). Control Station A Control Node in an SAP ACI environment. DART Operating system of Celerra data movers (Data Access in Real Time). Dynamic Host Configuration Protocol DHCP is a protocol for assigning dynamic IP addresses to devices on a network. Dynamic Host Configuration Protocol server A DHCP server provides configuration parameters specific to the DHCP client host, required by the host to participate on the Internet. EMC NAS Network attached storage for file systems of EMC. Enterprise Resource Planning Enterprise Resource Planning systems are management information systems that integrate and automate many of the business practices associated with the operations or production aspects of a company. Ethernet A Local Area Network which supports data transfer rates of 10 megabits per second. Fiber Channel Fiber Channel is a serial computer bus intended for connecting high-speed storage devices to computers. Filer Network attached storage for file systems of NetApp. FlexFrame A joint project in which the main partners are SAP, Network Appliance, Intel and Fujitsu Siemens Computers. 68, Planning Tool

Glossary FlexFrame TM for SAP FlexFrame TM for SAP is a radically new architecture for SAP environments. It exploits the latest business-critical computing technology to deliver major cost savings for SAP customers. FlexFrame internal LAN Switch Cisco network switches which are integral part of the FlexFrame for SAP hardware configuration and which are automatically configured by the FlexFrame for SAP software. Gigabit Ethernet A Local Area Network which supports data transfer rates of 1 gigabit (1,000 megabits) per second. Host name The name of a node (assigned to an interface) that is resolved to a unique IP address. One node can have multiple host names (cf. node name). In SAP environments host names are currently limited to 13 alphanumeric characters including the hyphen ( - ). The first character must be a letter. In the SAP environment host names are case-sensitive. Image In the FlexFrame documentation, Image is used as a synonym for Hard Disk Image. Internet Protocol Address A unique number used by computers to refer to each other when sending information through networks using the Internet Protocol. Lightweight Directory Access Protocol Protocol for accessing on-line directory services. Local Area Network A computer network that spans a relatively small area. Most LANs are confined to a single building or group of buildings. However, one LAN can be connected to other LANs over any distance via telephone lines and radio waves. A system of LANs connected in this way is called a Wide Area Network (WAN). Local host name The name of the node (physical computer); it can be displayed and set using the command /bin/hostname. Logical Unit Number An address for a single (SCSI) disk drive. MAC address Device identifier number of a Network Interface Card. In full: "media access control address". Planning Tool 69

Glossary MaxDB A relational database system from mysql (formerly ADABAS and SAPDB). Media Access Control address An identifier for network devices, usually unique. The MAC address is stored physically on the device. NAS system Network Attached Storage of any vendor (in our context: EMC NAS or NetApp Filer). NDMPcopy NDMPcopy transfers data between Filers using the Network Data Management Protocol (NDMP). Netboot A boot procedure for computers where the operating system is provided via a network instead of local disks. Netweaver SAP NetWeaver is the technical foundation of SAP solutions. Network Appliance Filer See Filer. Network Attached Storage A data storage device that is connected via a network to one or multiple computers. Network File System A network protocol for network-based storage access. Network Interface Card A hardware device that allows computer communication via networks. Node A physical computer system controlled by an OS. Node name The name of a physical node as returned by the command uname -n. Each node name within a FlexFrame environment must be unique. Non-Volatile Random Access Memory A type of memory that retains its contents when the power is turned off. On-Line Transaction Processing Transaction processing via computer networks. OpenLDAP An Open Source LDAP Service Implementation. Open Network Technology for Appliance Products The operating system of Network Appliance Filers. 70, Planning Tool

Glossary Open Source Software Software that is distributed free of charge under an open source license, such as the GNU Public License. Oracle RAC A cluster database by Oracle Corporation. Physical host Name of a physical computer system (node). Power-On Self Test Part of a computer's boot process; automatic testing of diverse hardware components. Preboot Execution Environment An environment that allows a computer to boot from a network resource without having a local operating system installed. PRIMECLUSTER Fujitsu Siemens Computer s 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. Planning Tool 71

Glossary 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 environment (FlexFrame), a process can be moved between hardware nodes while staying transparent to the user and application. 72, Planning Tool

20 Index A application nodes adding 47 BX630 model based servers 51 changing operating system 49 changing pool and group membership 49 changing switch group 48 deleting 48 editing IP host part 50 managing 45 B backup copy 7 C client 13 Client VLAN 6 configuration files generating 12 restrictions 12 Control VLAN 6 controlling components adding 27 changing HW ID 28 changing switch group 28 deleting 27 managing 25 E EMC NAS system defining 30 entering general information 9 Excel functions, executing manually 7 Excel spreadsheet, instructions for use 7 external connectivity adding 43 change switch group 44 defining 41 deleting 43 F foreign macros 7 forms Application Nodes 45 Controlling 25 External Connectivity 41 General Information 9 initializing 10 Miscellaneous 61 NAS Configuration Details 29 NAS Volumes 35 Pool Group 17 Pool specific UIDs and GIDs 23 Pool Volumes 21 Pools 13 SAP Services 53 SAP Volumes 59 Switch Groups 37 I installation procedure 2 L LAN failover 4 LAN trunking 4 Planning Tool 73

Index N NAS configuration details adding 32 changing cluster partner 33 changing NICs 33 changing switch group 33 deleting 32 NAS volume adding 36 deleting 36 network concept 3 NIC 4 NTP master server 62 P pool groups adding 18 changing 19 deleting 18 managing 17 sorting 19 pool specific UIDs and GIDs adding 23 deleting 24 managing 23 modifying 24 pool volumes adding pool-to-volume relationship 22 deleting pool-to-volume relationship 22 pools adding 14 defining characteristics 13 deleting 15 Q QoS (Quality of Service) 6 R requirements 7 S SAP instances 45, 53 SAP systems adding 56 adding an instance 58 deleting an instance 58 deleting completely 57 entering and maintaining 53 SAP volumes adding SID-to-volume relationship 60 deleting SID-to-volume relationship 60 Server VLAN 6 Storage VLAN 6 switch groups assigning types 37 changing types 39 switch ports 41 switches 6 T tagged VLAN 41 V virtual host IP 45, 53 virtual host name 45, 53 VLAN IDs 41 VLAN segments 3, 5 74, Planning Tool

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. 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 Solutions 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 seitdem 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