Release Information for FlexFrame for SAP V5.1A00

Transcription

1 Copyright 2013 Fujitsu Technology Solutions Table of Contents General... 1 Ordering... 2 Delivery... 2 Documentation... 2 SW/HW Extensions / New Functionality... 3 Technical Information... 4 Resource Requirements... 4 Hardware Requirements / Support... 4 Installation, Configuration, Update... 4 Update an entire FlexFrame Landscape... 4 Upgrading from FlexFrame 4.2B or 5.0A... 4 Upgrading FlexFrame 4.1A or lower to 5.1A Product Use... 4 Obsolete Functions... 5 Incompatibilities... 5 Hints and Restrictions... 5 General... 5 Management Tool... 5 Administration Commands... 5 Control Nodes... 6 FlexFrame Autonomous Agents... 6 Application Nodes... 6 VMware... 7 Networking... 8 Network Attached Storage... 8 SAP... 8 Procedure in Case of Errors... 9 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 virtualization 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 This Release Information is a summary of the major extensions, requirements, restrictions and operating information concerning FlexFrame for SAP 5.1A00. Additionally the user is required to read the appropriate manuals, which describe the topics in detail. The use of names or product designations, etc., in this information does not constitute a general authorization 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. Copyright 2013 Fujitsu Technology Solutions 1

2 Ordering Delivery FlexFrame is subject to the general terms and conditions of the software product use and service agreement. The FlexFrame Software consists of several DVDs: Table 1. Media Documentation DVD Name Version Description Delivery Control Node 5.1A00 Control Node Software Image With FlexFrame Software Kit Application Node Linux 5.1A00 Application Node Software Image Linux SLES10 SP4 x86_64 for PRIMERGY Server Application Node Linux 5.1A00 Application Node Software Image Linux SLES11 SP2 x86_64 for PRIMERGY Server Service-DVD 5.1A00 FA-Suite, Management Tool, ESXi-Installer and Documentation With FlexFrame Software Kit With FlexFrame Software Kit With FlexFrame Software Kit The Service-DVD contains the following documentation titles for FlexFrame for SAP 5.1A: Manuals: Management Tool Installation of a FlexFrame Environment Administration and Operation Security Guide Network Design and Configuration Guide Installation Guide for SAP Solutions Upgrading FlexFrame 4.2B or 5.0A to 5.1A myamc.fa_agents - Installation and Administration myamc.fa_logagent - Concept and Usage myamc.fa_messenger - Installation and Administration Installation and Configuration of ACC 7.3 Other technical documents: Technical White Paper Hardware Characteristics Quick Guides Copyright 2013 Fujitsu Technology Solutions 2

3 SW/HW Extensions / New Functionality FlexFrame for SAP 5.1A00 patchlevel 22 supports the following new features: New hardware: NetApp FAS2220, FAS3220 and FAS3250 ONTAP FlexFrame for SAP 5.1A00 patchlevel 21 supports the following new features: New hardware: BX920 S3 and BX924 S3 as Application Nodes New Linux SLES11 SP2 and Linux SLES10 SP4 Images, including the latest patch cluster available at the time of building. Please see the SAP related SLES hints. [9] VMware ESXi 5.0 Update 1 ServerView Version FlexFrame for SAP 5.1A00 patchlevel 20 supports the following new features: New hardware: RX300 S7 as Control Node and Application Node, RX900 S2 as Application Node, BX900 S2 as new Blade Chassis, Cisco Nexus 5548/5596, Cisco Catalyst 3750-X as FlexFrame internal access layer switches and NetApp FAS2240. SAP BusinessObjects 4.0 (BOBJ 4.0) MaxDB 7.9 (Please notice: This release is not yet fully integrated, but can be added in a first step as version 7.8. Please see the SAP Installation Guide for further details.) Cloning of TRX and SMD instances SMD Agents for DB instances Linux SLES11 SP2 as new Application Node Image, including the latest patch cluster available at the time of building. Please see the SAP related SLES hints. [9] Linux SLES10 SP4 on the Application Nodes and Control Center include the latest patch cluster available at the time of building. Please see the SAP related SLES hints. [9] ONTAP and JVM 4.1 ServerView Version 5.51 FlexFrame for SAP 5.1A supports the following new features (compared to 5.0A): Linux SLES10 SP4 on the Control Center. Linux SLES10 SP4 and SLES11 SP1 on the Application Nodes include the latest patch clusters available at the time of building. Please see the SAP related SLES hints. [9] Support of VMware vsphere ESXi 5.0. This includes a new vsphere SDK and new VMware Tools. The predecessor FlexFrame 5.0A supported ESX 4.0, which has now been replaced by ESXi 5.0. Copyright 2013 Fujitsu Technology Solutions 3

4 Support of new hardware: RX600 S6 as Application Node. Graphical User Interface for administration. ServerView Version 5.30 Cloning of an entire SAP installation from one pool to another. Support of SAP NW 7.3. LACP as default Port-Channel configuration for switches. vfiler support for vfiler0. Technical Information Resource Requirements The resource requirements are determined within the sizing process for SAP infrastructures from Fujitsu Technology Solutions. Sizing requests can be sent to Application Node Images requires about 8GB of disk space on the NAS system for the Linux Images. Hardware Requirements / Support In the FlexFrame Support Matrix, available on the Fujitsu Technology Solutions Service Partner Portal, you can find the latest information on supported models and the required firmware versions. General information about the configuration is available in the Configuration Guide on the Dynamic Infrastructures Partner Portal. Installation, Configuration, Update The system is delivered preinstalled after having been assembled in a Staging Center taking the requirements of the Management Tool into consideration. The subsequent installation of SAP services is described in the Installation Guide for SAP Solutions (on the Service-DVD). Update an entire FlexFrame Landscape Upgrading from FlexFrame 4.2B or 5.0A For information on upgrading a FlexFrame 4.2B or 5.0A environment to 5.1A00, please see the document Upgrading FlexFrame 4.2B or 5.0A to 5.1A (on the Service-DVD). Any special release request, that was granted for an earlier version, will be voided with the update to FlexFrame for SAP 5.1A00 and must be reissued. Upgrading FlexFrame 4.1A or lower to 5.1A00 Product Use If you want to upgrade your FlexFrame environment with version 4.1A or lower to 5.1A00, please contact Expert.SAP@ts.fujitsu.com. There exists a process, which has to be adapted to project specific needs. The application of the product is described in the Document Administration & Operation (Service-DVD). Copyright 2013 Fujitsu Technology Solutions 4

5 Obsolete Functions / Incompatibilities / Hints and Restrictions General 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. Only certified FlexFrame for SAP specialist are allowed to install patch packages. The project and customer specific modifications of the system have to be checked and considered before a patch is installed. The upgrade of the software is subject to an additional charge and may only be installed by FlexFrame for SAP trained service engineers authorized by Fujitsu. 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, including the available online information. Management Tool The network segments of the various pools (Client LAN, Server LAN and Storage LAN) as well as the network segment of the Control LAN must have their own IP ranges. None of these network segments may be reused for a different purpose for instance a different pool. The host names of the virtual IP addresses of the SAP services are built by a predefined and fixed rule. They cannot be changed. However, it is possible to create aliases to each service after the installation has been completed. Note: The original predefined names still remain intact. With the new administration mode introduced in FlexFrame the Management Tool can be used for the administration of a FlexFrame for SAP system. Please check the documentation for which tasks it can be used. Please notice that pool names with a dash ("-") are not supported, but can be configured. Please avoid pool names with dashes, otherwise this may lead to serious problems during the installation/operation of the FlexFrame for SAP environment. Non ASCII characters must not be used in the following textboxes: Customer Project Name Person Comments Administration Commands Please notice that pool names with a dash ("-") are not supported, but can be configured. Please avoid pool names with dashes, otherwise this may lead to serious problems during the installation/operation of the FlexFrame for SAP environment. Copyright 2013 Fujitsu Technology Solutions 5

6 Control Nodes The installation of the Control Nodes must follow the process described in the Installation of a FlexFrame Environment. When using the new RX300 S7 as Control Node the new Control Node image, which was released with patchlevel 20, has to be used, otherwise FlexFrame for SAP can not be installed or upgraded. The new Control Node image identifies itself with the version FF_CN_5.1A and build date The only difference between the old and the new Control Node image is the RX300 S7 support. Customers who are already using FF5.1A and do not plan to use the new hardware do not need to use the new image. The disk layout (partitioning) is created during the installation of the Control Node. The layout is predefined and can't be changed by the user. The order of the partitions is likewise determined during the installation of the Control Node. The two unused partition created during this process can be used during a FlexFrame upgrade and may not be used for other purposes. No additional PCI cards or USB devices other than the ones installed on shipment may be used. Extensions are only allowed in accordance to the Configuration Guide available through the Fujitsu Technology Solutions Dynamic Infrastructures Partner Portal. 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 NAS. There is no backup of any additional software. No manual changes of the Control Nodes 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 Technology Solutions support. The use of telnet, ftp or rsh to the Control Nodes is not intended nor configured. FlexFrame requires the usage of the ssh (secure shell) tools. The pool created with the internal attribute CN Pool = true (visible in the Management Tool) may not be removed by an administration command, since this pool is used to mount file systems from the NAS device. This attribute is usually assigned to the pool created first. FlexFrame Autonomous Agents When running a MaxDB with an SMD instance the SMD instance is not moved to the new host by the FA Suite when using service-based failover. It is recommended to use nodebased failover, which is the default configuration. Application Nodes Only servers from Fujitsu or Fujitsu Siemens Computers can be used. The use of servers from other vendors is prohibited. For the latest information about the supported PRIMERGY servers models and their respectively supported infrastructure consult the FlexFrame Support Matrix for FlexFrame for SAP. Important: Before using SLES11 SP1 or SP2 for Application Nodes please check the network [8] and SAP [9] related restrictions. Please notice that the default behaviour of the automounter has changed in SLES11. Mountpoints, that are present in LDAP, but were not created yet (e.g. ff_sid_adm.pl --op Copyright 2013 Fujitsu Technology Solutions 6

7 add was run, but ff_setup_sid_folders.sh wasn't), will be displayed even if the corresponding directories do not exist. Because of changes in SAP-Software (SAP Solution Manager/SAP Hostagent) FlexFrame will use hostspecific /etc/oratab instead of poolspecific one with new images supplied with this patch. The previous link '/etc/oratab' points now to '/var/flexframe/etc/oratab' which contains only the SIDs currently running on specific application host. The older file '/oracle/ora-config/ oratab' which contains the complete list of SIDs in the pool is now reachable via the link '/ etc/oratab.shadow'. To get this configuration with older images you have to switch the links using maintenance cycle. If there are no changes the scripts behave as before. The use of the switchblade 10GbE-18/8-F (SBAX2) in fabric 1 within a BX900 chassis prohibits the operation of BX920 S1/S2 blades. The blades BX920 S3 and BX924 S3 can also be used in a blade chassis equipped with 1GbE-36/8+2-Q (SB11) switchblades. The network interfaces will then be throttled to 1Gbit. In a blade chassis equipped with 10GbE-18/8-F switchblades all 10GbE Blade Servers can be run. When adding these blades they should be added as 10GbE Servers. It will not be checked or prevented if they are added as 1GbE blades. To upgrade the Emulex CNA firmware of the onboard LAN controllers of the server models BX924 S3 and BX920 S3 via ASP-package it is necessary to use the following workaround: # mkdir /tmp/firmware # mount -o bind /tmp/firmware /lib/firmware Start of the Flash-Tool, e.g.: #./OCx_MC-CNA_V scexe -f -k -U $PWD/asp # umount /lib/firmware Reboot of the Application Node The server models RX800 S3 and BX630 are also no longer supported in FlexFrame for SAP 5.1A00, but are candidates for requests for special release; if a configuration including one of these server types shall be updated from a FlexFrame for SAP version 4.2B or 5.0A to 5.1A00, the upgrade will be terminated with a corresponding warning and the customer is asked to propose a request for special release. The update will be continued, when the special release file is available. No additional PCI or USB devices may be attached to any Application Nodes. Extensions are only allowed in accordance to the Configuration Guide available through the Fujitsu Technology Solutions Dynamic Infrastructures Partner Portal. More network interfaces in addition to the 2 redundantly configured Gigabit interfaces (1 or 10 GbE) are not supported. VMware To be configurable by FlexFrame scripts, PRIMERGY servers with vsphere ESXi must be licensed with vsphere Standard or higher, or be in evaluation mode. The ESXi Single Server license (free ESXi), that comes with the embedded ESXi variant on PRIMERGY servers is not sufficient and must be replaced or removed before the FlexFrame for SAP specific ESXi configuration can be completed. Due to a special behaviour of the memory management in SLES10, virtual machines must be configured with a memory size of at least 3.5GB. With less available memory, the vmxnet driver may not allocate enough memory to initialize the virtual NICs. Copyright 2013 Fujitsu Technology Solutions 7

8 Networking Important: Because of a bug in SLES11 SP1 and SLES11 SP2 bonding can only be used in mode active-passive. Please check SB-FF4S-11P15 before running SAP systems on this operating system. It can be found in the Service Partner Portal. The VLANs with the IDs 1, , and 4094 are switch internally reserved and can therefore not be used for FlexFrame purposes. This is a restriction, which is imposed by the switches and is valid for all FlexFrame versions. The Cisco Catalyst 3750-E switches can also be configured with so-called TwinGig converters. Then the switch provides 4 SFP ports instead of the 2 10GbE ports and therefore basically offers the same connectivity as an Cisco Catalyst 3750G-24TS or -48TS model. This configuration is not generally supported in FlexFrame. Customer projects upon special release request are however possible. Please note that only modules that are present in the SupportMatrix are supported for the switchtypes Cisco Catalyst 3750-X and Cisco Nexus 5010/5020 and 5548/5596. With more than 4 configured Cisco Catalyst 3750-E/-X switches a warning about the usage of the 10GbE ports is issued. Please contact Expert.SAP@ts.fujitsu.com about any throughput implications. The failure of the switch operating system or the reloading of a switch will make the whole switch stack unavailable. Network Attached Storage SAP The NetApp VirtualFiler functionality within ONTAP is supported by FlexFrame 5.1A00. Please notice: Only vfiler0 can be used for FlexFrame for SAP. The V-Series devices are supported however. The NetApp storage families FAS22xx, FAS30xx, FAS31xx, FAS32xx, FAS60xx and FAS62xx can be equipped with 10GbE NICs. In FlexFrame for SAP either exactly two 10GbE NICs or none at all are supported. These interfaces can be single-ported (the older PCI-X variant) or dual-ported (the newer PCIe variant). Only one port per NIC is supported by FlexFrame for SAP. The usage of more than two 10GbE ports of a NetApp storage device in a FlexFrame installation can be supported on a single project basis upon special release request. Enable CDP (optional): NetApp supports the Cisco Discovery Protokoll. When enabled you can see the filer as cdp neighbor on the switch. cn1:~ # ssh <filer> options cdpd.enable on Depending on the software stack used, the SAP-command startsap (called by ff_service.sh) shows a warning message Could not find virtual host in ifconfig list. That message can be ignored. FlexFrame for SAP does only support SAP Business Objects with the integrated IBM DB2 database which is created with the full installation automatically. Concerning an issue with SAP installation procedure for SAP systems using DB2 (Unable to determine whether account user="db2sid" uid="3600" has password, SAP case /2011) you have to do some actions to get rid of the issue until SAP supplies a new Installation Master: /FlexFrame/volFF/FlexFrame/ldap/common/slapd_acl.conf: exchange the string by peername.ip. auth to by peername.ip. read Copyright 2013 Fujitsu Technology Solutions 8

9 restart ldap master using ff_ha_cmd.sh restart ldap_master (on the control node) restart nscd using rcnscd restart (application node) restart SAP installation procedure after finishing your database installation reset read to auth in /FlexFrame/volFF/ FlexFrame/ldap/common/slapd_acl.conf restart ldap_master restart nscd There are two noteworthy notes from SAP in relation to SLES10 SP4 and SLES11 SP2: Note Introducing missing iiop functionality for IBM 142 SR13 JDK SLES10 SP4 and SLES11 SP2 integrate IBM Java JDK SR13. SR13 is not 100% compatible to the SR12 integrated in the previous SPs of SLES10. Therefore the customer needs to make sure, that the components described in the first SAP note are updated to the relevant versions, before any Application Node is moved to SLES10 SP4 or SLES11 SP2. Note Linux-3.x-Kernel When trying to run SAP programs on a Linux Kernel 3.x an error message can be displayed ("can not determine current Linux kernel version --> exiting" / OS release Linux 3.x is not supported with this kernel). In the past only Linux 2.6 or 2.4 kernels where allowed. To run SAP on the new Linux kernel (which is integrated in SLES11 SP2), a SAP kernel update is required. Please check the SAP Note to determine which update fit your needs. The SAP Versions 4.0B - 4.6B are not supported in FlexFrame 5.1A00. WebAS 6.20 ITS is not supported. The following DB versions have been tested: MaxDB 7.6, 7.7, 7.8, 7.9, Oracle 9i, 10g and 11g, IBM DB2 9.1, 9.5 and 9.7. WebAS 6.20 with pure Java Instances (for portals) is not integrated and does not work. Mixed ABAP and Java Instances work well. 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 Web Dispatcher Request Bugseye IPC with WebAS 6.40 If needed, the above solutions can be implemented on a single project basis upon special release request. 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. Procedure in Case of Errors Information about troubleshooting are found in chapter 12 of the document Administration & Operation. Copyright 2013 Fujitsu Technology Solutions 9

10 For all FlexFrame components (hardware and software), a service contract is mandatory. For service reachability, 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 2013 Fujitsu Technology Solutions 10