FlexFrame 4.0A10 Readme

Transcription

1 FlexFrame 4.0A10 Readme Issue This README file describes extensions and modifications for FlexFrame for SAP version 4.0A10 in reference to the following available user guides for the FlexFrame for SAP version 4.0 FlexFrame for SAP Installation of a FlexFrame Environment FlexFrame for SAP Installation Guide for SAP Solutions FlexFrame for SAP Administration and Operation FlexFrame for SAP Planning Tool FlexFrame for SAP FA Agents - Installation and Administration FlexFrame for SAP Upgrading FlexFrame 3.1 or 3.2 to 4.0 Chapter references refer to these original user guides listed below. Contents 1. Installation of a FlexFrame Environment... 3 New Chapter: 1.3 New Documents HW Characteristics Related Documents (replaces 1.5) Hardware Installation... 4 New Chapter after 2.6: Configuration of BX600 Management Blades Control Center OS (replace) Operating System Second Control Node (replace) DART Version (replace) BX300/600 (at the end of this chapter on side 155 the text) Installation Guide for SAP Solutions... 6 Chapter 17: Troubleshooting (replace) Administration and Operation... 7 Chapter 2.3 : Software (replace)... 7 New Chapter Changing RPS and Switch port configuration for RPS (used with PW650/850)... 8 Chapter and Chapter (add) Changing Pool DNS Domain (extend) Chapter 9.1 Create, Modify, Delete, or List User(s) for AppNodes (replace) Chapter Installing Veritas Software (replace) Chapter Password for Root of LDAP Server and Replica (add) Chapter 12.2 Adding / Removing SAP SIDs and Instances (add) Chapter Script: ff_change_id.pl (replace) Chapter 12.4 Multiple NAS Systems and Multiple Volumes (replace) New Chapter Support SAP upgrade Chapter Starting and Stopping SAP Services without Root Privileges (replace) New Chapter Mount Options using NDMP Backup Chapter : Restore of a Controle Node (add) New Chapter 17.5 LDAP and cache coherence New Chapter Linux New Chapter Solaris New Chapter Solaris Planning Tool FA Agents Installation and Administration Chapter External Switchover (add) of 23

2 Chapter Switchover Control Parameters (replace) Upgrading FlexFrame 3.1 or 3.2 to New Chapter 1.2 Important Upgrade Hint Chapter 2.2 Upgrade myamc.fa Agents (replace) Chapter 4 Install New Application Node Images of 23

3 1. Installation of a FlexFrame Environment New Chapter: 1.3 New Documents HW Characteristics This document used to contain informations strongly depending on the individual hardware server models as there are increasing lots of supported hardware server models, this guide grew in amount and complexity. In order to dissolve this incremental complexity a new approach has been started: collect all hardware server model dependent information for installation of new hardware server models and bring it together in an outsourced short document called HW Characteristics (nickname: HW- Steckbrief). An individual HW-Steckbrief is compiled for every new hardware server model and can be used independently from this referencebook. These HW Characteristics are delivered with the Service CD of a FlexFrame for SAP version. The hardware server models, which are described in this Installation Guide, and for which therefore no HW-Steckbrief has been created, are PY-Server Models RX300, RX300 S2, RX300 S3 RX600, RX600 S2, RX600 S3 RX800, RX800 S2, RX800 S3 BX300, BX620, BX620 S2, BX620 S3, BX630 PW-Server-Models PW250, PW450, PW650, PW850 The new server models and storage models as well have their own HW-Steckbrief. 1.6 Related Documents (replaces 1.5) FlexFrame for SAP - Technical White Paper FlexFrame for SAP - Planning Tool FlexFrame for SAP - Installation of a FlexFrame Environment FlexFrame for SAP - Network Design and Configuration Guide FlexFrame for SAP - Administration and Operation FlexFrame for SAP - Upgrading FlexFrame 3.1 or 3.2 to 4.0 FlexFrame for SAP - FA_Agents - Installation and Administration FlexFrame for SAP - myamc.fa_logagent Concept and Usage FlexFrame for SAP - Installation ACC 1.0 SP13 FlexFrame for SAP - Installation Guide for SAP Solutions PRIMECLUSTER Documentation ServerView Documentation SUSE Linux Enterprise Server Documentation Solaris Documentation 3 of 23

4 2.3 Hardware Installation Exchange the picture of RX600 S2/S3 on page 16 by the picture as follows: New Chapter after 2.6: Configuration of BX600 Management Blades The PRIMERGY BX600 Blade Server is equipped with two hot-swappable, redundant management blades with an integrated management solution for complete remote administration of the system. One management blade plays the role of a master, the second the role of a slave, which becomes master in case of breakdown of the first. In order to enable automatical exchange of roles also in case the LAN connection to the master is failing, the following action has to take place during installation (or later on): The management blades provide two user interfaces: A web interface is available as well as a console menu interface using the Telnet protocol. For a detailed description please see the manual RemoteView Management Blade - User Interface Description. The management blades provide two user interfaces: A web interface is available as well as a console menu interface using the Telnet protocol. For a detailed description please see the manual RemoteView Management Blade - User Interface Description. Choose the Telnet console menu interface by calling control1:~ # telnet <managementblade ip_address> 3172 login into management blade choose menu 1 (Management Agent) choose menu 3 (System Information) choose menu 9(NIC Status Detection) choose menu 1 and set NIC Status Detection to enable choose menu 2 and set NIC Detection Timeout to 30 choose menus 0 to quit telnet session 4 of 23

5 2.4 Control Center OS (replace) This chapter describes the installation and configuration of the FlexFrame Control Center, that is the installation and configuration of the two FlexFrame Control Nodes Operating System Second Control Node (replace) Now, proceed with the operating system installation of the second Control Node in the same way as described in section "Control Center OS" on page 22, using the same DVD DART Version (replace) The DART version (or greater) is mandatory for EMC NAS support within Flex-Frame for SAP. To use SAP/MaxDB applications within FlexFrame for SAP additionally a special installation parameter for manipulating the return code behaviour of the mkdir command has to be set for each Celerra data mover used within a FlexFrame environment. The new parameter checkforexistingfilefirst has to be set as follows param nfs checkforexistingfilefirst=1 This line has to be inserted into the file /nas/server/slot_2/param and the corresponding file for each data mover (slot_3..., depending on the Celerra model). The Data Mover have to be rebooted to activate the change. To avoid large banner messages when accessing the Celerra, you can delete the content of /etc/issue on the Control Station, or remove the file BX300/600 (at the end of this chapter on side 155 the text) Select 2 and set permissions to read write. Configuration is finished. Quit the menu and minicom session. shall be supplemented as follows: Select 2 and set permissions to read write. Configuration is finished. In order to have all changes activated in case of a initial management blade setup, the management blade has to be rebooted. This can be done from the console menu with option (6) Reboot Management Blade. Quit the menu and minicom session. 5 of 23

6 2. Installation Guide for SAP Solutions Chapter 17: Troubleshooting (replace) Account sdb is not locked (MaxDB 7.5, Solaris only) During the preparation phase of the Database Kernel package you can get the following messages: WRN: changing sdb administrators group. Account sdb is not locked, this is a security leak There are two workarounds to avoid the problem. Solution 1: Make the application image writetable and create the user sdb and the group sdba locally. The necessary UID and GUID you can get from LDAP by getent passwd grep sdb and getent group grep sdba. You can create it using Solaris admintool. After the installation you should withdraw your modifications. Solution 2: Set the password of user sdb in LDAP to *lk*. 6 of 23

7 3. Administration and Operation Chapter 2.3 : Software (replace) No. Hardware OS Software Services 1 Control Nodes: 2 x PRIMERGY RX300 S3 or 2 x PRIMERGY RX300 S2 SLES 9 32Bit SP3 PRIMECLUSTER 4.2A20, FA Agents (Control Agents) V3.0, FlexFrame 4.0 File System Image CN, ServerView, etc TFTP, DHCP, RARP, BOOTPARAM, LDAP, (SAPROUTER), etc 2 Network switches: SMI (as delivered) 2 x Cisco Catalyst 3750G- 24TS or 2 x Cisco Catalyst 3750G-24T or 2 x Cisco Catalyst 3750G- 48TS (proprietary) 3 Network Attached Storage one or more Network Appliance Filer heads (FASxxxx), disk shelves as required 1, hosting shared OS file systems and application data or ONTAP, recommended, minimum or 7.1 or (proprietary) ONTAP NetApp Tools NFS, SnapRestore optional Cluster components, FlexClone, SnapVault, SnapMirror one or more EMC Celerra NSxx, disk shelves as required 1, hosting shared OS file systems and application data. DART, minimum DART EMC Tools NFS, 4 SAN Storage Multipath SW SLES 9 / SLES 10: DM-MPIO integrated Multipath SW Solaris 9: MPxIO minimum Solaris 10: MPxIO integrated Multipath SW HA Services or optional for Solaris OS EMC Powerpath minimum SAN Storage Volume Manager SLES 9 / SLES 10: LINUX Volume Manager LVM2 Solaris 9 / 10: Solaris Volume Manager SVM or for all supported OS Veritas (VxVM, VxFS) Volume Management Services 1 The amount of disks required for customer-specific FlexFrame configurations can be determined together with Fujitsu Siemens Computers' Customer Support Filer Sizing Team 7 of 23

8 No. Hardware OS Software Services 6 Intel- or AMD-based PRIMERGY server (standard rack or blade server) SLES 10 SP1 (x86_64), SLES 9 SP3 (x86_64), and / or SLES 9 SP2 (i686), FlexFrame 4.0 File System Image, FA Agents (Application Agents), SAP Applications, Database SAP & DB Services 7 SPARC64 V-based PRIMEPOWER server Solaris 10 U3 and / or Solaris 9 FlexFrame 4.0 File System Image, FA Agents (Application Agents), SAP Applications, Database SAP & DB Services New Chapter Changing RPS and Switch port configuration for RPS (used with PW650/850) For the PRIMEPOWER models PW650/850 the following settings for the RPS (Remote Power Switch) and the 3750 SwitchGroup ports have to be observed: There are default settings called use auto negotiation for the RPS and the 3750 SwitchGroup ports as well, which when used may lead to a lot of notices logged at /var/log/messages. To prevent from this a manual configuration change to 10 Mbit and half duplex has to be done at RPS and switch ports connected to a RPS. See the screenshots and the snippet below for an example: 1. Change RPS configuration: cn1:~ # telnet host 3172 Enter user and password 8 of 23

9 Choose (5) Service Processor Choose (5) Configure IP Parameters 9 of 23

10 Select 4 as LAN Interface Link Speed 4 (10 Mbps half duplex) Select (0) to quit 2. Change switch port configuration: cn1:~ # telnet swg1 Trying Connected to Escape character is '^]'. User Access Verification Username: <login> Password: <password> swg1>enable Password: <password> swg1#configure terminal Enter configuration commands, one per line. End with CNTL/Z. swg1(config)#interface GigabitEthernet 1/0/20 swg1(config-if)#speed 10 swg1(config-if)#duplex half swg1(config-if)#exit swg1(config)#end swg1#copy running-config startup-config Destination filename [startup-config]? Building configuration... [OK] swg1#exit 10 of 23

11 Connection closed by foreign host. cn1:~ # 11 of 23

12 Chapter and Chapter (add) To upload switch blade configuration do only plug one port, eg. port 11, to blade switches to prevent disabling of ports or portchannels at blade switches and switch group. After successfull upload and reboot of switch blade the other ports may be plugged Changing Pool DNS Domain (extend) Changing a pools DNS configuration can be done using maintenance tool ff_pool_adm.pl. The DNS configuration is written in /FlexFrame/volFF/pool-<pool name>/pooldata/config/etc/resolv.conf and identical in /etc/resolv.conf of all solaris AN images of the given pool. Attention: The DNS configuration is newly configured, therfore the domain name and all servers to be used for this pool have to be given in the options. Any modification in resolv.conf, done by the customer, is lost. Chapter 9.1 Create, Modify, Delete, or List User(s) for AppNodes (replace) Incompatible extension in handling of option "home": Create, Modifiy, Delete, or List User(s) for App Nodes The handling of the option home changed and the behaviour in case of operation add and mod is now equal. The option changed incompatible in comparison to previous versions. Option: --home <home_directory> If the <home_directory> is omitted the home directory is set to: /FlexFrame/pooldata/home/<username>. The directory is created if it does not exist. If the <home_directory> is set to home/<name> the home directory is set to: /FlexFrame/pooldata/home/<name>. The directory is created if it does not exist. If the <home_directory> is set to <dir>/<name> the home directory is set to: /FlexFrame/pooldata/<dir>/<name>. The directory is created if it does not exist. If the <home_directory> is set to <dirname> the home directory is set to: /FlexFrame/pooldata/<dirname>. The directory is created if it does not exist. 12 of 23

13 If the <home_directory> is set to /<dir1>/<dir2> the home directory is set to: /<dir1>/<dir2>. The directory has to be created manually (except <dir1> is /home_sap). Chapter Installing Veritas Software (replace) [last sentence of first paragraph is changed to:] Currently FlexFrame supports the version 5.0. Additionally, the currently needed combination of MP, RP and HF must be determined from the support matrix, and the corresponding patches must be installed too. [next 3 paragraphs unchanged; next paragraphs changed to:] Therefore, after copying the CD contents to your software, locate the file SunOS.pm in the subdirectory scripts/cpi/plat of the product you wish to install; for VxVM it is volume_manager/scripts/cpi/plat, for VxFS it is file_system/scripts/cpi/plat. Make the following change in each of these files: $CPI::PLAT{SunOS}{DFK}="/usr/bin/df -kl"; -> $CPI::PLAT{SunOS}{DFK}="/usr/bin/df -k"; To install VxVM, run the installation script installvm from the volume_manager directory, where you have changed the scripts/cpi/plat/sunos.pm file. To install VxFS, run the installation script installfs from the file_system directory, where you have changed the scripts/cpi/plat/sunos.pm file. [change last paragraph of the chapter to:] If using the DMP component of VxVM with a NetApp storage array, you must also install a so-called APM and ASL. This packages are contained in a tar archive that can be downloaded from the Symantec web page at A detailed description of how to install these packages can be found if you follow the given links. Chapter Password for Root of LDAP Server and Replica (add) To change the Password for root on the LDAP Server and Replica without using the ldapbrowser, type in statements according to the following example: ldapmodify -v -x -D"cn=root,ou=LDAPadmins,ou=FlexFrame,dc=tom,dc=fujitsu-siemens,dc=com" - w tom <<EOF dn: cn=root,ou=ldapadmins,ou=flexframe,dc=tom,dc=fujitsu-siemens,dc=com changetype: modify userpassword: <new password> dn: cn=replica,ou=ldapadmins,ou=flexframe,dc=tom,dc=fujitsu-siemens,dc=com changetype: modify userpassword: <new password> EOF 13 of 23

14 Chapter 12.2 Adding / Removing SAP SIDs and Instances (add) Command fails if option "db" is omitted: If you call the script for the first time to create a new SID and its instance(s) you have to use the option db mandatorily. Otherwise the scripts fail. Chapter Script: ff_change_id.pl (replace) Change cp -r to cp -rp Chapter 12.4 Multiple NAS Systems and Multiple Volumes (replace) It is possible to distribute 1. All NAS systems 2. The software for SAP and the database are located in the centralized volume volff of the first NAS system or alternatively (if wanted) in a pool-specific volff volume in an arbitrary NAS system (defined within the FlexFrame environment). 3. For each SID New Chapter Support SAP upgrade This command is used to support the migration from a previous SAP base version to a higher one. It could be also useful if you are migrating from an older release of FF to a newer one. You are able to change the SID specific settings in LDAP database like version of SAP or database installation. It also tries to introduce the LDAP data which are requested with newer SAP versions. At now it covers requirements until NetWeaver 2004s. Synopsis ff_sap_upgrade.pl \ --pool <pool_name> \ --sid { <sid> \* } \ --sapvo { } \ --sapvn 7.0 \ --dbvo { ORACLE9 ORACLE10 SAPDB73 SAPDB73 SAPDB74 MAXDB75 MAXDB76 } \ --dbvn { ORACLE9 MAXDB76 } \ [--help] [--version] [--debug] [--dryrun] 14 of 23

15 Options --pool <pool_name> Name of the pool the SID should belongs to. --sid <sid> SAP system identifier. Either you specify a specific SID or you use the asterisk. Asterisk means all SIDs of the specific pool which match to sapvo and dbvo are modified. --sapvo <old_version> Current value of the SAP-Version stored in LDAP (without leading SAP- ). --sapvn <new_version> SAP-Version the SID is migrated to. --dbvo <old_version> Version of previous used database version. --dbvn <new_version> Version of database the SID is migrated to. --help Display usage. --version Show version of command. --debug Sets the debug option to enlarge logging. --dryrun Just to see which changes would be made in LDAP. Hints It is not allowed to specifiy 7.0 with parameter sapvo. But in some installations it could be necessary to make system changes (e.g. automount entries). So you can do that with a little workaround: ff_sid_adm.pl op add pool pool1 sid ttt sapversion 4.6 \ --db ORACLE9:dbttt-se:\* \ --sap ci:90:cittt:\*:cittt-se:\* ff_sap_upgrade.pl pool pool1 sid ttt sapvo 4.6 sapvn 7.0 \ --dbvo ORACLE9 dbvn ORACLE10 ff_sid_adm.pl op del pool pool1 sid ttt Chapter Starting and Stopping SAP Services without Root Privileges (replace) In order to enable user to start and stop SAP services without having root privileges a sudo (see man sudo) configuration is shipped with the Application Nodes. This configuration allows the SAP and the DB administration users to start their respective services (including their virtual hostname s IP addresses). The user command line requires a prefix of sudo in addition to the standard command line (see example below): 15 of 23

16 > sudo /FlexFrame/scripts/sapdb <SID> start The sudo mechanisms will check against its configuration file if the user (or the responsible group) is allowed to run the command and run it with root privileges. The configuration file is stored on Application node and can be found in Linux: Solaris: /etc/sudoers /opt/smawplus/etc/sudoers If FlexFrame itself needs extensions those are made in our standard images. If there are any requirements to extent the configuration at customer site you can make those extensions in the corresponding configuration files. We strongly recommend to adjust the intended modifications with professional service support because in the worst case your system will not work correctly furthermore. To make those modifications persistent in Linux you can modify the root image directly without a maintenance cycle. But which each update of FlexFrame you need to modify your image again. To get persistence on Solaris you should use a nbrc script of your own which is linked to the normal create new process of an application node (please see description how to create nbrc scripts). A maintenance cycle is not mandatory needed. Content of FlexFrame configuration file on Linux: # sudoers for FlexFrame Application Nodes %sapsys ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sap*, /FlexFrame/scripts/view_* %oper ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* %sdba ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* %dba ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* Content of FlexFrame configuration file on Solaris: # sudoers for FlexFrame Application Nodes %sapsys ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sap*, /FlexFrame/scripts/view_* %oper ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* %sdba ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* %dba ALL=(ALL) NOPASSWD: /FlexFrame/scripts/sapdb, /FlexFrame/scripts/view_* This configuration means all members of the operating system group sapsys are allowed to execute the scripts named sap* and view_*. Members of oper, sdba or dba just have the permission to execute the scripts sapdb and view_*. Entering a password is not needed. New Chapter Mount Options using NDMP Backup Performance impacts using option minra on/off (minra = minimal read ahead): While using NDMP protocol for backup operations maybe you can get performance problems. We recommend to change the mount options (especially for sapdata/saplog) from minra on to minra off. 16 of 23

17 Minra on means that the filer does not use a cache read ahead option! So minra on only makes sense if the applications generally have a random access and in particular no sequential access profile. FlexFrame for SAP generally uses minra off (therefore dynamical and intelligent filer caching). Chapter : Restore of a Controle Node (add) The options are the same as in Chap You have to use the Service CD as well. New Chapter 17.5 LDAP and cache coherence While using command scripts to administer your FlexFrame environment it is possible that you do not see the changes on Application Nodes immediately. The reason is the usage of a cache daemon (nscd) which refreshes the cache content in defined time periods. On Solaris machines you do not see the nscd using ps. That process is overlayed with the ldap_cachemgr process. There are different caches for different types (e.g. passwd, group, etc.) The configuration of the cache properties is done in /etc/nscd.conf (default). Normally you do not need to change the FlexFrame default configuration. Please ask professional service colleagues before doing any change by yourself. You can display your current configuration by nscd g For further information look into the corresponding manpages (nscd, nscd.conf). New Chapter Linux To force the refresh of the cache content you use nscd i or nscd restart New Chapter Solaris 9 To force the refresh of the cache content you use nscd i { passwd group hosts user_attr } 17 of 23

18 You can enable a specific cache by nscd -e { passwd group hosts user_attr },yes You can disable a specific cache by nscd -e { passwd group hosts user_attr },no New Chapter Solaris 10 To force the refresh of the cache content you use nscd i cachename You can enable a specific cache by svcadm enable system/name_server_cache You can disable a specific cache by svcadm disable system/name_server_cache 18 of 23

19 4. Planning Tool No modifications in Planning Tool User Guide. 19 of 23

20 5. FA Agents Installation and Administration Chapter External Switchover (add) At the end of the chapter the follwing section is added: FA-Agents workaround for shutdown problems There are two new config values: Shut_PowerOff_Try SwitchOver_ext_Unavailability_check 'Shut_PowerOff_Try' specifies how often the power off will be tried. 'SwitchOver_ext_Unavailability_check' specifies which tests will be done for unavailability check ('ping' and/or 'ssh', 'ping', 'ssh'). The default values set for work as before: Shut_PowerOff_Try = 1 SwitchOver_ext_Unavailability_check = 'PING_and_SSH' For information of the administrator new traps are defined which inform about the result of the unavailability check and the situation if the node will not power off because the node is still available. Chapter Switchover Control Parameters (replace) The normal lapse on breakdown of a node requires the disconnecting of this node to avoid a disturbance caused by the existence of duplicate services. If it is not possible to disconnect the node, the move breaks up with a failure notice. The services concerned are not restarted. With the help of the parameter IgnoreShutdownFailure, this failure can be influenced in that, if a shutdown fault occurs, for example because a shutdown parameter was not configured for a node, the relevant node is separated from the network. If set to true, the result of the shutdown command is ignored in the sense that the CtrlAgent continues with the external switchover (after having removed the node from the switches). The default of this parameter is true. If a node is separated from the network, the network must be reactivated manually. For this, the following command must be executed on the Control Node before the defective node is restarted: ff_sw_ports.pl --op up --name <hostname> If the network interfaces of the node are not reactivated, it is not possible for the node to start. 20 of 23

21 6. Upgrading FlexFrame 3.1 or 3.2 to 4.0 New Chapter 1.2 Important Upgrade Hint Please observe, that the original title of the Upgrade-Guide does no more make sense, as an upgrade from 3.1 to 4.0 actually is no more possible. The modified title Upgrading FlexFrame 3.2 or 4.0A00 to 4.0A10 describes the current situation more exact. An upgrade to V4.0A10 is only possible from FlexFrame Version V3.2B (Release 009) or FlexFrame Version V4.0A (Release 011) Chapter 2.2 Upgrade myamc.fa Agents (replace) Instead of old text Insert the DVD CD into the first Control Node, mount it and read the README: New text: Insert the CD into the first Control Node, mount it and read the README. Please note that the path name depends on the FlexFrame release: FlexFrame 3.2 uses /media/cdrom, FlexFrame 4.0 uses /media/dvd. This applies to the entire Guide. Between point 2 and point 3 insert: Necessary database updates of the messenger database won't be done automatically. The database updates must be performed before using fa_ezsetup.this must be done in PRIMECLUSTER maintenance mode of user application ff_manage. The myamc.messenger must be stopped. Syntax for mysql: mysql -u [user] -p[passwort] < UpdateAmcMsgmySQL_FF.6.0A12-KXXnach6.0A12-KYY.sql The Values for XX and YY must be detected in customer installation. Value YY is from the newest myamc.messenger mysql-database update script: cd /media/cdrom/fa_suite/myamc_fa/messenger_scripts/ Value XX is from the installed version of myamc.messenger. It can be detected from rpmdatabase like the following example: cn1: # rpm -qa grep -i messenger myamc.messenger-server-6.0a12-k02 All scripts between XX and YY must be executed. Full example: 21 of 23

22 cn1: # /opt/myamc/messenger/bin/myamc.messengersrv stop cn1: # mysql -u myamc -pflexframe < UpdateAmcMsgmySQL_FF.6.0A12-K02nach6.0A12-K03.sql cn1: # mysql -u myamc -pflexframe < UpdateAmcMsgmySQL_FF.6.0A12-K03nach6.0A12-K04.sql cn1: # /opt/myamc/messenger/bin/myamc.messengersrv start At the end of Point 5 insert: Attention: Sometimes the command may report messages starting with "failed to stop application...". This messages can be ignored. At the end of Point 6 insert: Please check all relevant configuration files for changes and new settings and make sure, that everything is ok and configured to the administrator's requirements. Note: Pool-specific changes of FA configuration settings are documented in the migration log files for each pool: /opt/myamc/vff/vff_<pool>/migration.<release>.<date>/migration-instructions.txt. The steps necessary to finalize the migration as mentioned in the migration instructions have already been performed! Change Point 7: (Re)start all AppAgents for all pools. cn1: #./fa_ezsetup.sh -L /tmp/myamc_fa.log -S /tmp/myamc_fa.state run -A /opt/myamc/fa_appagent/myamc.fa_appagent start OK? Leave the cdrom directory cn1: # cd / OK? Manually restart all myamc services. cn1: # /etc/init.d/myamc.fa_ctrlagent start cn1: # /etc/init.d/myamc.fa_logagent start cn1: # /etc/init.d/myamc.messengersrv start cn1: # /opt/flexframe/etc/init.d/ff_jakarta-tomcat start OK? OK? OK? OK? Only if myamc FA Accounting is used. cn1: # /etc/init.d/myamc.domainmanager start OK? 22 of 23

23 Chapter 4 Install New Application Node Images Instead of old text: Before upgrading your Application Node, please keep in mind the following: New text: Before upgrading your Application Node please keep in mind the following: The Application Nodes running on the new Application Node Images will not contain changes you made on the existing Application Node Images during Maintenance Cycles. For example a SAN configuration has to be done again: Details on this are available in Chapter of the Administration and Operations Guide (including example). 23 of 23

24 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