Release Information for FlexFrame V4.0A10 for SAP

Transcription

1 Release Information for FlexFrame V4.0A10 for SAP Copyright 2008 Fujitsu Siemens Computers Table of Contents General... 1 Ordering... 1 Delivery... 1 Documentation... 2 Software Extensions / New Functionality... 2 Technical Information... 3 Resource Requirements... 3 Hardware Requirements / Support... 4 Software Requirements... 4 Installation, Configuration, Update... 4 Product Use... 4 Obsolete Functions... 4 Incompatibilities... 4 Hints and Restrictions... 4 Procedure in Case of Errors... 8 The FlexFrame for SAP solution is a revolutionary approach to run complex SAP solutions with higher reliability and efficiency. At the same time some major changes to the configuration paradigms for infrastructures have been implemented. These changes are: A shared operating system booted over IP networks for the SAP servers. Decoupling of application software and operating system, called virtualisation of SAP software. Shared Network Attached Storage from Network Appliance or EMC². FlexFrame Autonomous Agents (FA Agents) providing revolutionary mechanisms to implement highavailability functions without cluster software. General Ordering Delivery This Release Notice is a summary of the major extensions, requirements and operating Information concerning FlexFrame. The use of names or product designations, etc., in this information does not constitute a general authorisation to use such names or designations. In many cases they are legally or contractually protected names or designations even if they are not marked as such. FlexFrame is subject to the general terms and conditions of the software product use and service agreement. The FlexFrame 4.0A10 Software is ordered with the Control Nodes. It also contains the necessary PrimeCluster license. The Solaris Images have to be ordered separately. The license for the use on Application Nodes has also to be ordered separately. The FlexFrame Software consists of several DVDs and CDs: Copyright 2008 Fujitsu Siemens Computers 1

2 Table 1. Media Documentation DVD Name Version Description Delivery Control Node 4.0A10 Control Node Software Image Control Node 4.0A10 Control Node RPMs Application Node Linux 4.0A10 Application Node Software Image Linux SLES 9 i686 for PRIMERGY Server Application Node Linux 4.0A10 Application Node Software Image Linux SLES 9 x86_64 for PRIMERGY Server Application Node Linux 4.0A10 Application Node Software Image Linux SLES 10 x86_64 for PRIMERGY Server Application Node Solaris Tools/Sources 4.0A10 Images Production Set for Application Node PW250/450/650/850. (Solaris 9) Documentation 4.0A10 Complete Documentation (see next section [2]) Planning Tool 4.0A10 Configuration Tool The Documentation CD contains the following titles: Installation of a FlexFrame Environment Upgrading FlexFrame 3.1 or 3.2 to 4.0 Installation Guide for SAP Solutions FA Agents - Installation and Administration Administration and Operation Installation ACC 1.0 SP13 Technical White Paper Planning Tool FlexFrame Folder Structure Folder Structure List of Error Messages Software Extensions / New Functionality FlexFrame 4.0A10 supports the following new features: New Primergy models as application nodes: RX300S4, RX330S1, RX600S4 (only with administration commands), BX630S2 Dual NetApp Filer FAST20xx family Copyright 2008 Fujitsu Siemens Computers 2

3 New and updated admin commands: ff_sap_upgrade.pl and ff_user_adm.pl. For more detailed information about the changes in this release please refer to the file FF40A10_README.pdf in the documentation directory of the Service CD. FlexFrame 4.0A00 supports the following features: Support of EMC² Network Attached Storage (NAS) devices (EMC² Celerra Family). Integration of SAN infrastructure for SAP data bases (EMC² + NetApp). See section SAN [7] for some important hints. Support of NW2004s SR2 / SAP Web AS Support of SLES 10 and SOLARIS 10 (U3) on Application Nodes (AN). Control Node now rebased on SLES 9 (SP3). Primergy RX800-S3 and BX600 with Cisco Switch Primergy RX300S3 as Control Node and Cisco 48 port switch. Enhanced integration capabilities of add-on SW. Partly integrated and/or done by Best Practise Documents for: Xprint Redwood Cronacle NetWorker (backup and restore) myamc functions (LogAgent) opensm2 SQUID proxy on Control Node. Support for Accounting & Billing (provided by myamc). Enhancement of the FA autonomous agent. Support of Replicated Enqueue and Live Cache. New dedicated switchover scenarios for SAP services (substitution, supplementation, displacement). Support of Non-SAP services (generic service configuration). Pool specific placement of volff. Pool specific placement of sapdata and saplog. Start/Stop of SAP services without normal root rights. Supplementary addition of further switch groups via admin-command. Technical Information Resource Requirements The resource requirements are determined within the sizing process for SAP infrastructures from Fujitsu Siemens Computers. Sizing requests can be sent to mailto:ccsap@fujitsusiemens.com Copyright 2008 Fujitsu Siemens Computers 3

4 The software is installed on the Control Nodes and Application Nodes of a server farm which do not run any other application software. So this issue does not apply. Application Node Images requires about 5GB of disk space on the NAS system for the Linux Images and about 3.5GB for one Solaris image or about 6GB for Solaris 10. Hardware Requirements / Support In the FlexFrame Support-Matrix available at you can find information on supported models. General information about the configuration is available in the Configuration Guide. Software Requirements / Installation, Configuration, Update The installation was accomplished after meeting requirements of the Planning Tool in a Staging Center. That way the system is delivered already installed. The basic installation is described in the FlexFrame Installation Guide (Documentation CD). Update an entire FlexFrame Landscape Upgrading FlexFrame 3.2 or lower to 4.0A10 If you want to upgrade your FlexFrame environment with version 3.0 or lower to 4.0A10, please contact CCSAP [mailto:ccsap@fujitsu-siemens.com]. There exists a process, which has to be adapted on project specific needs. Upgrading from FlexFrame 3.2B or 4.0A10 Product Use For information on upgrading a FlexFrame 3.2B or 4.0 environment to 4.0A10, please see the document Upgrading FlexFrame 3.1 or 3.2 to 4.0 (on the Documentation CD). The application of the product is described in the Document Administration & Operation (Documentation CD). Obsolete Functions / Incompatibilities / Hints and Restrictions General Planning Tool FlexFrame is a highly integrated product. It requires some knowledge about the dependencies of the components involved. Only people who have passed the FlexFrame training should plan, install, administer and/or maintain a FlexFrame landscape. We assume the people involved have read the full documentation which is shipped with the FlexFrame landscape. Most of the support issues are the result of not reading the manuals carefully enough. Cut & Paste functionality may not be used in the EXCEL workbook. Copyright 2008 Fujitsu Siemens Computers 4

5 Control Nodes Two or more planning tool files may not be opened within the same EXCEL session. Otherwise the files can't be saved. The host names of the virtual IP addresses of the SAP services are built upon a fixed rule. They cannot be changed. However, it is possible to create aliases to each service after the installation is completed. Note: The fixed names still remain intact. Not all input can be checked right on entering. After entering all data the user should use the check and create button. Otherwise inconsistent information may not be detected. The configuration files are protected by check sums. Alteration of the configuration files is not allowed and may lead to rejection or issues during or after the installation process. The installation of the Control Nodes must follow the process described in the Installation Manual. It is not intended to have additional software packages on the Control Nodes. The backup procedure assumes that the Control Node can be installed using the initial installation DVD plus a handful of configuration files saved onto the Filer. There is no backup of any additional software. No manual changes of the Control Node's configuration files or LDAP schemas are allowed, especially not in the configuration files which are generated by FlexFrame tools. They have an explicit warning in the beginning of each file. However, changes are allowed as they are based on the FlexFrame tools or procedures described in the Administration and Operations Manual or in the Installation Guide, or upon permission or instruction of Fujitsu Siemens Computers support. The use of telnet, ftp or rsh to the Control Nodes is not intended nor configured. We require usage of the ssh (secure shell) tools. No additional users or groups should be configured on the Control Nodes. All tools require one user (root). For compatibility reasons ff_sid_mnt_adm.pl --op=list doesn't display the existing LDAP entries of a SAN configuration. You have to use ff_sid_mnt_adm.pl --op=list --san=y to display the existing LDAP entries of a SAN configuration. But it is recommended to use the function ff_san_ldap_conf.pl --op=list to to display the existing LDAP entries of a SAN configuration. Application Nodes SLES10 Application Node images are not supported with RX300, RX600, BX620, RX300S2, BX620S2 and the BX300 blade server family. The new server RX800S3 is only supported with SLES10 (64Bit). Installing additional software, patches or drivers onto the image shipped by Fujitsu Siemens Computers is not allowed. The FlexFrame administrator has to create an own unsupported image using a name which does not start with FSC, as described in the Administration and Operations manual. Users like sidadm and orasid may start or stop their services only after the IP addresses have been setup by the appropriate tools (using root privileges). The creation of a Solaris 10 application node image with ff_new_an.sh requires 4 boots of the respective system until the image is ready. During these reboot a number of error message are displayed, which can be ignored. 1. Boot Copyright 2008 Fujitsu Siemens Computers 5

6 Networking Configuring network interface addresses: fjgi0 fjgi1: network connection up autonegotiation: on speed: 1000 flowctrl: symmetric duplex: full role: slave fjgi1: network connection up autonegotiation: on speed: 1000 flowctrl: symmetric duplex: full role: slave ip_arp_done: init failed WARNING: IP: Hardware address '00:e0:00:c5:46:a0' trying to be our address !hme0 WARNING: hme0: fault detected in device; service degraded WARNING: hme0: No response from Ethernet network : Link down -- cable problem? 2. Boot May 24 17:12:10 pw251 /usr/lib/snmp/snmpdx: bind() failed on UDP port 8161 [errno: Address already in use(125)] 3. Boot Configuring devices. devfsadm: closedir failed Stale NFS file handle devfsadm: closedir failed Stale NFS file handle 4. Boot May 24 17:10:12 pw251 scsi: WARNING: /pci@83,2000/fibre-channel@2/ fp@0,0/ssd@w e0102e,3 (ssd0): May 24 17:10:12 pw251 offline or reservation conflict May 24 17:10:12 pw251 scsi: WARNING: /pci@83,2000/fibre-channel@2/ fp@0,0/ssd@w e0102e,1 (ssd2): May 24 17:10:12 pw251 offline or reservation conflict This last message can be ignored if issued for LUNs on the Storage Processor of a CLARiiON/FibreCAT CX that does not currently own the LUN, when multipathing is not yet configured on the Application Node. The use of the Cisco switches is required. Configuration tools are updating the switches automatically (e.g. if an Application Node moves from one pool to another). Separation of LAN segments (e.g. using just one switch per VLAN) is not possible. The VLANs are present in every stack of the FlexFrame landscape. However, ports have only permission to send or receive packages from VLANs of their own pool. There is no way to send data from one pool to the other without tempering with the configuration switch(es). The usage of Jumbo Frames is not possible with FlexFrame 4.0A10. Network Attached Storage The NAS system can be connected using multiple NICs to the Cisco switches configured as multi-vif (NetApp terminology) resp. virtual devices (EMC terminology). However, the switches may not be able to return packages to the NAS system over multiple NICs of the vif. It is possible to create a default router for each pool (in either Client LAN, Server LAN or Storage LAN). However, it is not possible to create a server-specific default router (which is not desirable). Copyright 2008 Fujitsu Siemens Computers 6

7 The network interface for the multi-vif resp. virtual devices must be named storage. The VLAN interfaces are built on top of this storage interface. The current FlexFrame is not designed to use multiple single vifs on the Filer. The storage interface is dedicated to FlexFrame. It may be used to access the FlexFrame related NFS shares, but not for other services such as Common Internet File System (CIFS) etc. Use different interfaces if CIFS or other services are required. FlexFrame tools configure the configuration files of the NAS system automatically. Settings for other applications using the NAS system may be conflicting with the settings of FlexFrame and may be overwritten by the FlexFrame tools. This may result in loss of FlexFrame functionalities or the loss of other services. Therefore it is not recommended to use other services on the NAS system. The NetApp VirtualFiler functionality is not supported by FlexFrame 4.0A10. SAN The setup of a SAN configuration is described in detail in chapter 10 of the Administration and Operation. The setup as such is considered an administration as opposed to an installation issue. The setup must be done in close cooperation with the SAN administration of the customer and requires appropriate SAN Know How. Solaris 9 Application Nodes are not supported with SAN attached disks. The Solaris native multipath software MPxIO is not supported within FlexFrame for SAP. Corresponding to this restriction also the Solaris native volume manager SVM is not supported within FlexFrame. The EMC² multipath product Powerpath will be available on Solaris-ANs only on request for special release; the cooperating volume manager then has to be the Veritas Volume Manager. SAP The names of the virtual hosts for SAP services are built by a fixed rule. SAP has listed some instance numbers as reserved (SAP reserved instances: 02, 25, 43, 72, 89, 97, 98, 99). The FlexFrame 4.0A10 Planning Tool automatically doesn't use these instance numbers. However, they can still be entered manually. The SAP SID (System ID) must be unique for each pool. The saprouter program is not be shipped on the FlexFrame installation media for legal reason. It must be installed manually (c.f. Installation Guide ). The SAP Versions 4.0B - 4.6B are not supported in FlexFrame 4.0A10, but we know of customer installations using 4.0B, 4.5B and 4.6B. Some manual tasks are necessary during the SAP installation. Detailed description is available on request from the Global Project Support Team. WebAS 6.20 ITS is not supported. The following DB versions have been tested: SAP DB 7.3.x, MaxDB 7.5, MaxDB 7.6, Oracle 9.2 and Oracle 10. WebAS 6.20 with pure Java Instances (for portals) is not integrated and does not work. Mixed ABAP and Java Instances work well. Copyright 2008 Fujitsu Siemens Computers 7

8 After updating from FlexFrame 3.1 or 3.2 to FlexFrame 4.0A10, OS images based on SLES8, SLES9, SLES10, Solaris8, Solaris9 and Solaris 10 are available. SAP systems installed on SLES8/Solaris8 or SLES9/Solaris9 must continue to run on these images in FF 4.0A10. If SAP applications are supposed to run on a higher OS version, the SAP systems have to be ported to the new OS manually. Only those SAP solutions which SAP states to be adaptive are supported and may be used in FlexFrame. Known examples of SAP solutions not being supported in FlexFrame are Webdispatcher, Content Server, TREX6/7, Request Bugseye, IPC with WebAS The SID of a SAP System has to be identical to the corresponding SID of the database. This especially leads to the fact, that SAP's MCOD-Feature (Multiple Components in One Database) is not supported within FlexFrame. EMC² Celerra Systems Some high end Celerra Models support two control stations for utmost high availability. Within FlexFrame 4.0 only one control station can be used, so that given a breakdown of the control station attached to the FlexFrame Control LAN no administration & configuration commands is possible as long as the control station isn't repaired. When using a CLARiiON storage subsystem within a FlexFrame environment (SAN- or NASattached) and the Control Node is used for administrating and/or configuring the CLARiiON via Navisphere Web GUI it may happen that caused by a switchover of an Application Node the Servlet-Container Tomcat is started and requires the port 8080 used by the Navisphere client. In that case the Java VM and the web browser, e.g. the Navisphere client are terminated. To avoid this situation use a non-flexframe server for the Navisphere client. Procedure in Case of Errors Descriptions of error reports are found in chapter 17 of the document Administration & Operation. For all FlexFrame components (hardware and software), a service contract is mandatory. For service reach-ability, at least a 5 x 9 hours service contract has to be defined. This service contract assures support for error fixing of hard- and software components as well as delivery of updates and patches. Copyright 2008 Fujitsu Siemens Computers 8

9 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 The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at 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 Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009