Installation and Configuration Guide

hourglassjurorΜηχανική

5 Νοε 2013 (πριν από 3 χρόνια και 8 μήνες)

983 εμφανίσεις

T
ivo
l
i
®
SystemAutomation for Multiplatforms
Version 3.2.1
Installation and Configuration Guide
SC34-2584-01
￿￿￿
T
ivo
l
i
®
SystemAutomation for Multiplatforms
Version 3.2.1
Installation and Configuration Guide
SC34-2584-01
￿￿￿
Note!
Before using this information and the product it supports,read the information in “Notices” on page 289.
This edition of the Installation and Configuration Guide applies to Version 3,Release 2,Modification 0 of IBM Tivoli
System Automation for Multiplatforms,program number 5724–M00,and to all subsequent releases and
modifications of this product until otherwise indicated in new editions.The End-to-End Automation Management
Component was a component of System Automation for Multiplatforms until Version 2,Release 3.Since Version 3,
Release 1 of System Automation for Multiplatforms it is a separate product entitled IBM Tivoli System Automation
Application Manager (5724-S92).
This edition replaces SC34-2584-00.
IBM welcomes your comments.A form for readers'comments may be provided at the back of this publication,or
you may address your comments to the following address:
IBM Deutschland Research and Development GmbH
Department 3248
Schoenaicher Str.220
D-71032 Boeblingen
Federal Republic of Germany
FAX (Germany):07031 16-3456
FAX (Other Countries):49 7031 16-3456
Internet e-mail:eservdoc@de.ibm.com
If you would like a reply,be sure to include your name,address,telephone number,or FAX number.
Make sure to include the following in your comment or note:
Title and order number of this book
Page number or topic related to your comment
When you send information to IBM,you grant IBM a nonexclusive right to use or distribute the information in any
way it believes appropriate without incurring any obligation to you.
© Copyright IBMCorporation 2006,2010.
US Government Users Restricted Rights – Use,duplication or disclosure restricted by GSAADP Schedule Contract
with IBM Corp.
Contents
Figures..............vii
Tables...............ix
About this guide...........xi
Who should read this guide.........xi
How to use this guide...........xi
Where to find more information.......xi
Conventions used in this guide........xii
Typeface conventions..........xii
Related information...........xii
Summary of changes........xv
What's new in release 3.2.1.........xv
New SAP high availability solution feature..xvi
GDPS/PPRC Multiplatform Resiliency for
System z (xDR) feature.........xvi
Part 1.Installation.........1
Chapter 1.Installing on UNIX and Linux 3
Planning for the installation.........3
Contents of the CD...........3
CDs/archives for IBM Tivoli System Automation 3
Supported platforms...........4
Supported network interfaces........5
Live Partition Mobility support.......5
Preparing for installation..........6
Prerequisites.............7
Initial configurations...........8
Installing and upgrading IBM Tivoli System
Automation...............8
Installing IBM Tivoli System Automation on UNIX
and Linux..............9
Installing the product license.......12
Upgrading from a Try & Buy license to a full
product license............12
Languages and locales supported by IBM Tivoli
System Automation...........13
Migrating IBM Tivoli System Automation...14
Migrating AIX version 5 to 6.......17
Chapter 2.Installing on Windows...19
Planning for the installation.........19
IBM Tivoli System Automation installation CD 19
IBM Tivoli System Automation installation
archive...............19
Subsystem for Unix-based applications....19
Supported languages and locales......19
Preparing the system...........20
Prerequisites.............20
Considerations regarding clusters......21
Installing the Subsystem for UNIX-based
Applications (required).........21
Installing the Utilities and SDK Package
(required)..............21
Installing hotfixes...........22
Updating the DNS or hosts file (required)...22
Configuring the Subsystem for UNIX-based
Applications.............22
Setting up Windows user account access....24
Installing or upgrading..........24
Upgrading..............24
Installing using the graphical installation
program..............24
Installing on Windows in silent mode....35
Verifying the installation..........36
Changes made to your default profile.....36
Special considerations regarding Windows line
endings................37
Chapter 3.Post-installation tasks on
Windows..............39
Manual license installation.........39
Configuring a non-English environment for IBM
Tivoli System Automation on Windows.....39
Configuring the IBM Tivoli System Automation
Shell................39
Configuring a Telnet session from a Windows
command prompt...........40
Configuring a remote session using a terminal..40
Setting up the Windows firewall.......41
Windows Server 2008..........41
Chapter 4.Installing the operations
console..............45
Planning for the installation.........45
Packaging..............45
Product requirements..........46
Preparing for the installation of the IBM Tivoli
System Automation operations console.....49
Collecting the information you need to provide
during installation...........49
Installation prerequisites.........52
Installing the IBM Tivoli System Automation
operations console using the graphical installation
program...............53
Installing the IBM Tivoli System Automation
operations console in silent mode.......61
Post-installation tasks...........62
Installing WebSphere Application Server Service 62
Modify the Windows Firewall Security Rules..62
Verifying the installation..........64
Chapter 5.Upgrading the operations
console..............67
Upgrading the operations console from Release 2.2
or 2.3................67
© Copyright IBM Corp.2006,2010
iii
Upgrading the operations console from Release 3.1 67
Chapter 6.Configuring the operations
console..............69
Planning the configuration.........69
Performing the configuration on Windows Server
2008.................69
Using the configuration dialog........69
Chapter 7.Uninstalling on UNIX and
Linux...............71
Before you begin............71
Uninstallation procedure..........71
Chapter 8.Uninstalling on Windows..73
Uninstallation procedure..........73
Chapter 9.Uninstalling the operations
console..............77
Launching the graphical uninstallation program on
Windows...............77
Launching the graphical uninstallation program on
AIX and Linux.............77
Using the uninstallation program.......77
Chapter 10.Installing and uninstalling
service...............81
Installing service............81
Where to obtain fix packs.........81
Archive naming conventions.......81
Installing service for IBM Tivoli System
Automation.............82
Installing service for the operations console...84
Uninstalling service............85
Chapter 11.Installing the GDPS/PPRC
Multiplatform Resiliency for System z
feature...............87
Enabling GDPS/PPRC Multiplatform Resiliency for
zSeries................87
Supported GDPS version.........87
Supported Linux distributions.......88
Installing the xDR feature.........88
Packaging..............88
Installation prerequisites.........88
Installing the feature license........88
Upgrading the xDR feature from a version lower
than 3.2.1..............89
Activating the GDPS/PPRC Multiplatform
Resiliency for System z feature........89
Uninstalling the GDPS/PPRC Multiplatform
Resiliency for System z feature........89
Part 2.Integration with other Tivoli
products.............91
Chapter 12.Introduction.......93
Chapter 13.Event consoles......95
IBM Tivoli Netcool/OMNIbus........96
Prerequisites.............96
Event fields in OMNIbus database......96
Compound state to severity mapping.....99
Configuring OMNIbus to process System
Automation events..........100
Configuring launch-in-context feature....103
Tivoli Enterprise Console.........105
Prerequisites.............105
Configuring TEC to process System Automation
events...............106
Configuring launch-in-context support....106
Enabling event generation in System Automation
for Multiplatforms............108
Publisher configuration file........108
TEC EIF configuration file/etc/Tivoli/tec/
TECPublisher.conf...........110
Enabling the publisher.........112
Setting a new language locale for the TEC event
messages..............112
Chapter 14.Tivoli Business Service
Manager (TBSM)..........115
Integrating with System Automation for
Multiplatforms.............116
Prerequisites..............117
Configuring TBSM............117
System Automation Service Template for TBSM 117
Defining a System Automation service template
in TBSM..............118
Defining trigger in Netcool/OMNIbus....118
Integrating System Automation resources in TBSM 119
Assigning the service template to a service
instance..............119
Customizing TBSM views to add information from
System Automation...........121
Adding columns for additional System
Automation information to a TBSM service tree.122
Configuring launch-in-context support.....126
Additional attributes used to supply context
information.............126
Defining launch-in-context action......127
Exporting SA specific additional attributes for
use in LiC Action...........128
Chapter 15.Tivoli Enterprise Portal 131
Prerequisites..............131
Configuring launch-in-context support.....131
Part 3.Configuring the end-to-end
automation adapter........133
Chapter 16.Configuration......135
Automating the end-to-end automation adapter 137
Invoking the end-to-end automation adapter
configuration dialog...........138
Performing the configuration on Windows Server
2008................139
iv
IBM Tivoli System Automation:Installation and Configuration Guide
Configuring the end-to-end automation adapter 140
Adapter tab.............140
Host using adapter tab.........141
Automation tab...........143
Reporting tab............146
Security tab.............148
Logger tab.............150
Saving the configuration.........152
Replicating the end-to-end automation adapter
configuration files to other nodes in the domain..153
Defining the end-to-end adapter automation policy 154
Removing the adapter automation policy....155
Controlling the end-to-end automation adapter..155
Chapter 17.Silent configuration...157
Overview...............157
Working in silent mode.........157
Tasks to be performed manually......157
Invoking silent configuration........158
Silent mode input properties file.......158
Editing the input properties file......159
Output in silent mode..........160
Chapter 18.Securing the connection
to end-to-end automation adapters
using SSL.............163
Generate Keystore and Truststore with SSL public
and private keys............163
Enable SSL security in the operations console
configuration.............165
Enable SSL security in automation adapter
configurations.............166
Part 4.SAP High Availability
Policy..............169
Chapter 19.High availability concepts
for a SAP system..........171
Single Point of Failure (SPOF)........172
Example of a two-node setup........173
SAP HA setup options..........174
ASCS HA setup...........175
Java SCS HA setup..........177
Double-Stack HA setup.........179
ABAP Central Instance HA setup......181
Database HA installation setup options.....182
SAP Central Services HA setup with local
database..............183
(A)SCS HA setup with remote database...183
Dependencies between the SAP and database
server...............183
DB2 and other databases........183
NFS HA installation setup.........184
High availability impact..........185
Enqueue Server and Enqueue Replication Server 186
Database host............188
NFS server.............189
SAP Syslog Collector..........189
SAP Web Dispatcher..........189
SAProuter.............189
Chapter 20.Planning the SAP HA
solution..............191
Installing a new ASCS,SCS,or Double-Stack HA
SAP system..............191
Prerequisites.............191
Initial installation on primary node.....192
Initial installation on failover node.....192
Verifying the initial installation......194
Installing a new ABAP Central Instance HA SAP
system...............196
Prerequisites.............196
Initial installation on primary node.....197
Initial installation on failover node.....197
Verifying the initial installation......197
Chapter 21.Installing and setting up
SystemAutomation for Multiplatforms 199
Prerequisites..............199
Installing System Automation for Multiplatforms
on all cluster nodes...........199
Granting read and write access for the
<sapsid>adm.............200
Setting up the domain..........200
Setting up the tie breaker.........201
Disabling automatic mount.........201
Enabling syslog daemon..........201
Installing the SAP HA policy feature.....201
Packaging.............201
Restrictions.............202
Installation prerequisites.........202
Installing the feature license.......202
Chapter 22.Configuring and
activating the SAP HA solution....203
The SAP HA policy...........203
ASCS HA policy...........203
Java SCS HA policy..........208
Parts of the ABAP and Java policies with the
same behavior............210
ABAP and Java SCS HA policy (Double-Stack) 212
ABAP Central Instance (ABAP CI) HA policy 214
Policy parameters............216
SAP ABAP Central Services (ASCS) - Enqueue
Replication Server (ERS) HA policy (ABAP)..216
SAP ABAP Central Instance (ABAP CI) HA
policy (ABAPCI)...........225
SAP JAVA Central Services (SCS) - Enqueue
Replication Server (ERS) HA policy (Java)...229
SAP ABAP+JAVA Central Services (ASCS+SCS)
- Enqueue Replication Server (ERS) HA policy
(Double-Stack)............239
Using the wizard to configure and activate the
policy................251
Starting the Policy Setup Wizard......251
Overview dialog...........252
Parameter dialog...........254
Entering values............257
Option parameters..........261
Contents
v
Wizard dialog flow..........263
Parameter help information.......264
Terminating the wizard.........265
Activating the policy..........266
Activating the policy while SAP resources are
running..............266
Chapter 23.Verifying the SAP HA
solution..............269
Starting and stopping SAP HA.......269
Failover scenarios............270
Test setup.............270
Scenarios..............270
Chapter 24.Checklist for SAP HA
solution..............275
Part 5.Appendixes........277
Appendix A.Troubleshooting the
installation of the operations console.279
Cleaning up from a failed installation.....279
Procedures for troubleshooting an installation..279
Known problems............280
Attempt to connect to the IBM Tivoli System
Automation operations console fails.....280
Using the log file collector utility.......280
Gathering information for IBM Support....281
Appendix B.Troubleshooting the
installation on Windows.......283
Installing without requirements check.....283
Where to find installation log files......283
Uninstalling without check.........283
Uninstallation hang...........283
Appendix C.Troubleshooting SAP HA
solution..............285
Enqueue Replication Server fails to start....285
No valid license available when activating SAP HA
policy................286
Appendix D.Using IBM Support
Assistant.............287
Installing IBM Support Assistant and the System
Automation Application Manager plug-in....287
Notices..............289
Trademarks..............290
Index...............291
vi
IBM Tivoli System Automation:Installation and Configuration Guide
Figures
1.Verifying the active and installed version numbers....................16
2.Installation wizard:Select your language........................25
3.Installation wizard:Introduction..........................25
4.Installation wizard:Software License Agreement.....................26
5.Installation wizard:Requirements Check........................27
6.Installation wizard:Choose Install Folder.......................28
7.Installation wizard:Choose Shortcut Locations......................29
8.Installation wizard:Additional Features........................30
9.Installation wizard:Password...........................30
10.Installation wizard:Pre-Installation Summary......................31
11.Installation wizard:Installing SA for Multiplatforms....................32
12.Installation wizard:Installing SA for Multiplatforms,progress bar...............32
13.Installation wizard:Please Wait...........................33
14.Installation wizard:Installation Complete.......................34
15.Add or Remove Programs panel on Windows......................35
16.Installation wizard operations console:Select language...................54
17.Installation wizard operations console:Introduction....................54
18.Installation wizard operations console:Software License Agreement..............55
19.Installation wizard operations console:Installation directory.................55
20.Installation wizard operations console:Tivoli Common Directory...............56
21.Installation wizard operations console:Embedded WebSphere Application Server I.........57
22.Installation wizard operations console:Embedded WebSphere Application Server II.........57
23.Installation wizard operations console:System Automation Administration User ID.........58
24.Installation wizard operations console:Pre-Install Summary.................59
25.Installation wizard operations console:Installing IBM Tivoli System Automation for Multiplatforms Base
Operations Console...............................59
26.Installation wizard operations console:Please Wait....................60
27.Installation wizard operations console:Installation Complete.................61
28.Log in panel of Integrated Solutions Console......................64
29.Welcome panel of Integrated Solutions Console.....................65
30.Server tab of the configuration dialog.........................70
31.Security tab of the configuration dialog........................70
32.Uninstallation wizard:Uninstall SA for Multiplatforms...................73
33.Uninstallation wizard:Please Wait..........................74
34.Uninstallation wizard:Uninstalling...........................74
35.Uninstallation wizard:Uninstall Complete.......................75
36.Uninstallation wizard,base operations console:Introduction.................78
37.Uninstallation wizard,base operations console:WebSphere Application Server...........78
38.Uninstallation wizard,base operations console:Start Deinstallation...............79
39.Uninstallation wizard,base operations console:In progress...................79
40.Uninstallation wizard,base operations console:Uninstallation Complete.............80
41.Sample configuration of launch entry........................104
42.Modifying menu entries that are displayed in the Tools menu................105
43.Syntax format and sample of the publisher configuration file................109
44.Syntax format and sample of the TEC configuration file..................111
45.TBSM basic architecture.............................115
46.Identification Fields tab.............................120
47.Tree template editor..............................124
48.TBSM Tree Template Editor............................125
49.Overview of the environment of the end-to-end automation adapter in UNIX and Linux clusters....136
50.Overview of the environment of the end-to-end automation adapter in Windows clusters.......137
51.Main panel of the end-to-end automation adapter configuration dialog.............139
52.IBM Tivoli System Automation end-to-end adapter configuration...............140
53.Host using adapter tab.............................142
54."Automation"tab of the"Automation Adapter Configuration"dialog..............144
© Copyright IBM Corp.2006,2010
vii
55.Inconsistent IP addresses dialog..........................146
56.Configuring data reporting............................147
57.Configuring the adapter security..........................149
58.Adapter logging and trace information........................150
59.Configuration update status panel.........................153
60.IBM Tivoli System Automation replicate configuration files panel...............153
61.Silent mode output:input properties file generation...................161
62.Keystore and Truststore generation using SSL......................164
63.Configuring SSL on the Security tab of the Direct Access Operations Console Configuration dialog....166
64.Enabling SSL security on the Security tab of the Automation Adapter Configuration dialog......167
65.Components of a distributed SAP system.......................172
66.Example of a two-node setup...........................174
67.ASCS HA setup................................175
68.Java SCS HA setup..............................177
69.Double-Stack HA setup.............................179
70.ABAP Central Instance HA setup..........................181
71.Initial startup of (A)SCS.............................187
72.Failure of (A)SCS and recovery of the enqueue table...................188
73.Movement of the Enqueue Replication Server......................188
74.ASCS HA policy...............................204
75.SAP HA policy for Java.............................208
76.ABAP and JAVA SCS HA policy (Double-Stack).....................213
77.ABAP Central Instance (ABAP CI) HA policy......................215
78.Overview dialog...............................253
79.Parameter dialog#3 without value definition......................255
80.Parameter dialog#3 with value definition.......................255
81.Single value prompt..............................258
82.Multiple values prompt.............................259
83.Value selection mode..............................260
84.Decision prompt...............................261
85.Option parameter in overview dialog........................262
86.Option parameter dialog.............................262
87.Nested parameter dialog.............................263
88.Wizard dialog flow..............................264
89.Help information in parameter dialogs........................265
90.Policy activation in the wizard...........................266
viii
IBM Tivoli System Automation:Installation and Configuration Guide
Tables
1.Product CD versions...............................3
2.Archive for Linux platforms............................4
3.Archive for AIX platforms.............................4
4.Archive for Solaris platforms............................4
5.Supported UNIX and Linux platforms of IBM Tivoli System Automation.............4
6.Software packages available for installation,based on your operating system............6
7.Languages and locales supported by IBM Tivoli System Automation on Linux systems........13
8.Languages and locales supported by IBM Tivoli System Automation on AIX systems.........13
9.Languages and locales supported by IBM Tivoli System Automation on Solaris systems........14
10.Languages and locales supported by IBM Tivoli System Automation on Windows..........19
11.Supported Windows platforms of System Automation for Multiplatforms.............20
12.Installation directories for 32 bit and 64 bit Windows Server versions..............28
13.IBM Tivoli System Automation Shell properties.....................40
14.Windows command prompt properties........................40
15.Telnet session properties.............................40
16.Session properties...............................41
17.Session properties...............................41
18.Firewall rules (Windows Server 2008).........................42
19.Product CD versions..............................45
20.Archive for Windows platforms...........................46
21.Archive for AIX platforms............................46
22.Archive for Linux on System x...........................46
23.Archive for Linux on POWER...........................46
24.Archive for Linux on System z...........................46
25.Supported platforms of the operations console......................47
26.Disk space requirements for the installation on Windows systems...............48
27.Disk space requirements on AIX and Linux systems....................48
28.Installation directory and Tivoli Common Directory....................49
29.Installation parameters for Integrated Solutions Console..................51
30.Port assignment for the embedded version of IBM WebSphere Application Server..........52
31.Ports for inbound TCP traffic (Windows Server 2008)...................63
32.Archive for Linux platforms............................82
33.Archive for AIX platforms............................82
34.Archive for Solaris platforms............................82
35.Archive for Windows platforms...........................83
36.Windows platforms...............................84
37.AIX platforms.................................84
38.Linux on IBM System x.............................85
39.Linux on POWER...............................85
40.Linux on System z...............................85
41.System Automation Application Manager event class types.................95
42.alerts.status:Common System Automation status attributes used in resource status change events....96
43.alerts.status:Resource,domain,event identification....................97
44.alerts.status:Other attributes used in resource status change events...............98
45.alerts.status:Domain status change events.......................98
46.Existing rules file fields for System Automation events...................98
47.Compound State to OMNIbus severity mapping.....................99
48.EIF to OMNIbus severity mapping.........................100
49.Mapping of System Automation resource state change events to TBSM states...........118
50.Text-based incoming status rules for TBSM......................122
51.Launch-in-context action parameters.........................127
52.Context used to find a Tivoli Enterprise Portal workspace.................131
53.Resources in the end-to-end automation adapter policy..................154
54.Generated input properties files..........................159
55.ABAP resources and the corresponding components...................176
© Copyright IBM Corp.2006,2010
ix
56.Java resources and the corresponding components....................178
57.Double-Stack resources and the corresponding components.................180
58.ABAP Central Instance resources and the corresponding components..............182
59.Fully implemented high availability solution for SAP...................185
60.Resources and resource groups of the ASCS HA policy..................204
61.Description and examples of placeholders for ABAP resource names..............206
62.Resources and resource groups of the Java SCS HA policy.................208
63.Description and examples of placeholders for JAVA resource names..............209
64.Resources and resource groups of the ABAP Central Instance HA policy.............215
65.Description and examples of placeholders for ABAP Central Instance resource names........216
66.ABAP policy parameters.............................216
67.ABAP Central Instance policy parameters.......................225
68.Java policy parameters.............................229
69.ABAP policy parameters.............................239
70.Location for the SAP HA XML template files......................252
71.Help information text of the Setup Policy Wizard....................264
72.Planned Outages...............................271
73.Unplanned outages..............................273
74.SAP HA solution checklist............................275
x
IBM Tivoli System Automation:Installation and Configuration Guide
About this guide
This guide provides information needed to plan,install,configure,and upgrade
IBM Tivoli System Automation for Multiplatforms,hereafter also referred to simply
as IBM Tivoli System Automation.
Who should read this guide
This guide is for planners,installers,and administrators who plan to install and
configure IBM Tivoli System Automation.
How to use this guide
This guide is divided into the following parts:
v Part 1,“Installation,” on page 1 describes how to install,uninstall,service,and
configure IBM Tivoli System Automation and the IBM Tivoli System Automation
operations console.
v Part 2,“Integration with other Tivoli products,” on page 91 describes how you
install and configure the IBM TEC extension for IBM Tivoli System Automation,
which enables users to navigate from an event displayed in the Event Console of
Tivoli Enterprise Console to the corresponding resource or domain in the System
Automation operations console,and describes how to set up launch-in-context
support for Tivoli Enterprise Portal TEP),which enables users to launch TEP
workspaces from the System Automation operations console with a single mouse
click.
v Part 3,“Configuring the end-to-end automation adapter,” on page 133 explains
how to set up the end-to-end automation adapter and define the related
automation policy.
v The Appendixes provide troubleshooting procedures and reference information.
Where to find more information
In addition to this manual,the IBM Tivoli System Automation library contains the
following books:
More information about IBM Tivoli System Automation for Multiplatforms can be
found in the following books:
v IBM Tivoli System Automation for Multiplatforms Release Notes,SC34-2586-01
v IBM Tivoli System Automation for Multiplatforms Installation and Configuration
Guide,SC34-2584-01
v IBM Tivoli System Automation for Multiplatforms a_u_g,SC34-2583-01
v IBM Tivoli System Automation for Multiplatforms Reference,SC34-2585-01
You can download the complete documentation at
http://publib.boulder.ibm.com/tividd/td/IBMTivoliSystemAutomationforMultiplatforms3.2.1.html
The IBM Tivoli System Automation home page contains useful up-to-date
information,including support links and downloads for maintenance packages.
You will find the IBM Tivoli System Automation home page at:
www.ibm.com/software/tivoli/products/sys-auto-multi/
© Copyright IBM Corp.2006,2010
xi
Conventions used in this guide
This guide uses several conventions for special terms and actions and operating
system commands and paths.
Typeface conventions
This guide uses the following conventions:
v Typically,file names,directories,and commands appear in a different font.For
example:
– File name:setup.bin
– Directory:/etc
– Command:startrpdomain cluster
v Variables are either italicized,enclosed in brackets,or both.For example:
– http://<hostname.yourco.com>/index.html
v Frequently,variables are used to indicate a root installation directory:
– Root installation directory of IBM Tivoli System Automation:
<samp_root> or samp_root
v Directories are shown with forward slashes (/),unless operating-system specific
information is provided.On Windows systems,you should use backward
slashes (\) when typing at a command line,unless otherwise noted.
v Operating-system specific information is provided.For example:
– AIX,Solaris,Linux:/opt/IBM/tsamp/sam
– Windows:C:\Program Files\IBM\SA for Multiplatforms
Related information
This topic to provides information about publications and Web sites related to IBM
Tivoli System Automation:
WebSphere Application Server publications:
The latest versions of all WebSphere Application Server publications can be
found on the WebSphere Application Server library Web site at
www.ibm.com/software/webservers/appserv/was/library/
IBMReliable Scalable Cluster Technology (RSCT) documentation:
RSCT (Reliable Scalable Cluster Technology) is the infrastructure used by
IBM Tivoli System Automation to provide clusters with improved system
availability,scalability,and ease of use.
v The following RSCT publications are available on the IBM Tivoli System
Automation CD:
– RSCT Administration Guide,SA22-7889
– RSCT for AIX 5L:Technical Reference,SA22-7890
– RSCT for Multiplatforms:Technical Reference,SA22-7893
– RSCT Messages,GA22-7891
– RSCT Diagnosis Guide,SA23-2202
v RSCT publications can also be found at the following Web site:
www.ibm.com/servers/eserver/clusters/library/
IBMDB2 publications:
DB2 publications can be found on the IBM DB2 UDB Web site at
xii
IBM Tivoli System Automation:Installation and Configuration Guide
www.ibm.com/software/data/db2/udb/support/
The link to the PDF manuals is available in the Other resources section on
the Web page.
IBMRedbooks publications:
The following publication is available at:
www.redbooks.ibm.com/redbooks.nsf/
v Linux on IBM zSeries and S/390:High Availability for z/VM and Linux
About this guide
xiii
xiv
IBM Tivoli System Automation:Installation and Configuration Guide
Summary of changes
What's new in release 3.2.1
The following new features and enhancements are provided in Version 3 Release 2
Modification Level 1:
IBMTivoli Netcool/OMNIbus integration
The following functions are added for this integration:
v Send events and state information from System Automation to
OMNIbus.
v Correlate System Automation events in the OMNIbus event console.
For example,System Automation state change events from the same
application override each other to show always only the latest event.
v Provide a launch-in-context capability from a System Automation event
in the OMNIbus console to the System Automation Operations Console.
IBMTivoli TBSMintegration
The following functions are added for this integration:
v System Automation events are mapped to TBSM Services.
v Visualize additional System Automation information in the TBSM
Service Tree:
– Availability State
– Desired State
– Compound State of applications
v Provide a configuration exchange to harvest resources defined in System
Automation to use in TBSM Service Trees.
v Provide a launch-in-context capability from TBSM views to the System
Automation Operations Console and vice-versa.Control a TBSM Service
and its components using System Automation.For example start,stop,
move,and others.
Functional enhancements
v Request persistency:Store requests like online or offline in the cluster
registry to execute a full cluster restart.
v Concurrent resources:Concurrent resources can run on multiple eligible
nodes at the same time.
v Failback to home:Allow the definition of a preferred node.After a
resource was moved due to a failover,it is moved back to the preferred
node as soon as this node is available again.
v Cleanup processing:Moving an application away from a node as part of
a failover can leave persistent application data that makes a later restart
of the application on that node impossible.Means to define whether and
how application data cleanup is performed are provided to avoid that
problem.
Performance enhancements
v Application monitor commands can take a considerable amount of time
and have a negative performance impact.As an alternative,a fast system
process table lookup can be defined to monitor.
Problem determination enhancements
© Copyright IBM Corp.2006,2010
xv
v Provide the ability to create a stack dump for a live running resource
manager.
v Resource managers set soft ulimits to unlimited at startup to avoid that
core dumps can not be taken due to too restrictive hard ulimits.
v Extend the lssam command to work in an event-based mode as an
alternative to periodic polling.
v Provide new samlog command that allows to collect and merge multiple
traces from different nodes.
Platform support
v AIX 7.1 support is added,excluding the operations console.
v The Live Partition Mobility feature of the P6 hardware is supported.
New SAP high availability solution feature
With this release of System Automation for Multiplatforms a new separately priced
feature is introduced that you can order.This feature provides product-level
support for the SAP high availability policy,replacing the unsupported policy that
was available on an as-is basis.The feature includes:
v High availability policy templates for four different SAP configuration options.
v Start,stop,and monitor scripts for all involved resources.
v Ease of use wizard to configure the actual policy from the policy template.
v Support of different SAP releases.
GDPS/PPRC Multiplatform Resiliency for System z (xDR)
feature
LPAR/CEC awareness
Currently,GDPS knows which LPARs are running on which System z
CECs.The information which z/VM hosted systems that are managed by
System Automation for Multiplatforms xDR are running on which LPARs
is statically configured within GDPS.If,for any reason,such a z/VM
hosted system or the whole z/VM host is started within a different LPAR
than originally configured,GDPS does not know about this location change
and starts,stops,and resets the wrong LPAR,probably impacting a
production system.
System Automation for Multiplatforms introduces System z LPAR and
CEC awareness by informing GDPS about currently used LPAR and CEC
names.In this way,GDPS can compare the actual names with the
configured names and inform the user about mismatching configurations.
This avoids situations where GDPS resets wrong LPARs,in case of
unplanned HyperSwap or Site Takeover or that the LPAR is reset by a
GDPS script.
New platform support
v SLES11 SP1
xvi
IBM Tivoli System Automation:Installation and Configuration Guide
Part 1.Installation
Chapter 1.Installing on UNIX and Linux....3
Planning for the installation.........3
Contents of the CD...........3
CDs/archives for IBM Tivoli System Automation 3
IBM Tivoli System Automation CD.....3
Electronic distribution of IBM Tivoli System
Automation.............3
Supported platforms...........4
Supported network interfaces........5
Live Partition Mobility support.......5
Requirements............5
Preparing for installation..........6
Prerequisites.............7
Considerations regarding clusters.....8
Initial configurations...........8
Installing and upgrading IBM Tivoli System
Automation...............8
Installing IBM Tivoli System Automation on UNIX
and Linux..............9
Performing the prerequisites check.....9
Installing IBM Tivoli System Automation..10
Post-installation tasks.........11
Installing the product license.......12
Upgrading from a Try & Buy license to a full
product license............12
Languages and locales supported by IBM Tivoli
System Automation...........13
IBM Tivoli System Automation on Linux..13
IBM Tivoli System Automation on AIX...13
IBM Tivoli System Automation on Solaris..14
Migrating IBM Tivoli System Automation...14
Migrating an entire domain.......15
Performing a node-by-node migration...15
Verifying the active and installed version
number..............16
Completing the migration.......16
Migrating AIX version 5 to 6.......17
Chapter 2.Installing on Windows......19
Planning for the installation.........19
IBM Tivoli System Automation installation CD 19
IBM Tivoli System Automation installation
archive...............19
Subsystem for Unix-based applications....19
Supported languages and locales......19
Preparing the system...........20
Prerequisites.............20
Considerations regarding clusters......21
Loads on nodes...........21
Number of nodes in a cluster......21
Using cloned or copied virtual Windows
system images...........21
Installing the Subsystem for UNIX-based
Applications (required).........21
Installing the Utilities and SDK Package
(required)..............21
Installing hotfixes...........22
Updating the DNS or hosts file (required)...22
Configuring the Subsystem for UNIX-based
Applications.............22
Enabling the syslog daemon.......23
Enabling Telnet login to subsystem for
UNIX-based applications (optional)....23
Setting up Windows user account access....24
Windows Server 2008.........24
Installing or upgrading..........24
Upgrading..............24
Installing using the graphical installation
program..............24
Installing on Windows in silent mode....35
Response file generation........35
Using the response file to install silently...36
Verifying the installation..........36
Changes made to your default profile.....36
Special considerations regarding Windows line
endings................37
Chapter 3.Post-installation tasks on Windows 39
Manual license installation.........39
Configuring a non-English environment for IBM
Tivoli System Automation on Windows.....39
Configuring the IBM Tivoli System Automation
Shell................39
Configuring a Telnet session from a Windows
command prompt...........40
Configuring a remote session using a terminal..40
Setting up the Windows firewall.......41
Windows Server 2008..........41
Chapter 4.Installing the operations console..45
Planning for the installation.........45
Packaging..............45
Operations console CD........45
Electronic distribution.........45
Product requirements..........46
Supported platforms.........47
Supported Web browsers........47
Hardware requirements........48
Preparing for the installation of the IBM Tivoli
System Automation operations console.....49
Collecting the information you need to provide
during installation...........49
Installation directory and Tivoli Common
Directory.............49
Installation parameters for the IBM Tivoli
System Automation operations console...51
Port assignment for the embedded version of
IBM WebSphere Application Server....51
Installation prerequisites.........52
Installing the IBM Tivoli System Automation
operations console using the graphical installation
program...............53
© Copyright IBM Corp.2006,2010
1
Installing the IBM Tivoli System Automation
operations console in silent mode.......61
Post-installation tasks...........62
Installing WebSphere Application Server Service 62
Modify the Windows Firewall Security Rules..62
Verifying the installation..........64
Chapter 5.Upgrading the operations console..67
Upgrading the operations console from Release 2.2
or 2.3................67
Upgrading the operations console from Release 3.1 67
Chapter 6.Configuring the operations console 69
Planning the configuration.........69
Performing the configuration on Windows Server
2008.................69
Using the configuration dialog........69
Chapter 7.Uninstalling on UNIX and Linux...71
Before you begin............71
Uninstallation procedure..........71
Chapter 8.Uninstalling on Windows.....73
Uninstallation procedure..........73
Chapter 9.Uninstalling the operations console 77
Launching the graphical uninstallation program on
Windows...............77
Launching the graphical uninstallation program on
AIX and Linux.............77
Using the uninstallation program.......77
Chapter 10.Installing and uninstalling service..81
Installing service............81
Where to obtain fix packs.........81
Archive naming conventions.......81
Installing service for IBM Tivoli System
Automation.............82
Usage instructions for the platform-specific
archives.............82
Steps for installing service for IBM Tivoli
System Automation..........83
Installing service for the operations console...84
Usage instructions for the platform-specific
archives.............84
Installing product fix packs for the operations
console..............85
Uninstalling service............85
Chapter 11.Installing the GDPS/PPRC
Multiplatform Resiliency for System z feature..87
Enabling GDPS/PPRC Multiplatform Resiliency for
zSeries................87
Supported GDPS version.........87
Supported Linux distributions.......88
Installing the xDR feature.........88
Packaging..............88
Installation prerequisites.........88
Installing the feature license........88
Upgrading the xDR feature from a version lower
than 3.2.1..............89
Activating the GDPS/PPRC Multiplatform
Resiliency for System z feature........89
Uninstalling the GDPS/PPRC Multiplatform
Resiliency for System z feature........89
2
IBM Tivoli System Automation:Installation and Configuration Guide
Chapter 1.Installing on UNIX and Linux
The following sections describe planning,preparation,and installation of IBM
Tivoli System Automation on UNIX (AIX or Solaris) and Linux:
v “Planning for the installation.”
v “Preparing for installation” on page 6
v “Installing and upgrading IBM Tivoli System Automation” on page 8.
Note:If you want to install System Automation for Multiplatforms on Windows,
refer to Chapter 2,“Installing on Windows,” on page 19.If you want to
install the System Automation for Multiplatforms operation console,refer to
Chapter 4,“Installing the operations console,” on page 45.
Planning for the installation
Contents of the CD
Separate CDs labeled as follows contain scripts and software packages for each
platform and the corresponding architecture:
v IBM Tivoli System Automation for Multiplatforms 3.2.1 - Linux on System x,
Linux on POWER and Linux on System z
v IBM Tivoli System Automation for Multiplatforms 3.2.1 - AIX
v IBM Tivoli System Automation for Multiplatforms 3.2.1 - Solaris
CDs/archives for IBM Tivoli SystemAutomation
The following sections explain where to find the base component of IBM Tivoli
System Automation installation files and scripts on the CDs and electronic
distribution archives.
IBM Tivoli SystemAutomation CD
To install IBM Tivoli System Automation,you use the installation script listed in
the right column of the table below.
Table 1.Product CD versions
Operating
system Product CD label Installation script
Linux IBM Tivoli System Automation for
Multiplatforms 3.2.1 - Linux on
System x,Linux on POWER and
Linux on System z
SAM3210MPLinux/installSAM
AIX IBM Tivoli System Automation for
Multiplatforms 3.2.1 - AIX
SAM3210MPAIX/installSAM
Solaris IBM Tivoli System Automation for
Multiplatforms 3.2.1 for Solaris
SAM3210MPSunOS/installSAM
Electronic distribution of IBM Tivoli SystemAutomation
If you prefer electronic distribution to delivery on the CD,we offer you the
possibility to download the product from the Web.After you have purchased IBM
Tivoli System Automation you get a URL where you can download a tar or zip
file.
© Copyright IBM Corp.2006,2010
3
Archives:
Linux:
Table 2.Archive for Linux platforms
Archive name Description
CZP2QML.tar This is the archive you use to install the product.To extract
the archive,GNU tar 1.13 or later is required.
Use the tar xf command to extract the archive.When you
have extracted the files,you will find the installation script
installSAM in the following directory:SAM3210MPLinux
AIX:
Table 3.Archive for AIX platforms
Archive name Description
CZP2RML.tar This is the archive you use to install the product.
Use the tar xf command to extract the archive.When you
have extracted the files,you will find the installation script
installSAM in the following directory:SAM3210MPAIX
Solaris:
Table 4.Archive for Solaris platforms
Archive name Description
CZP2TML.zip This is the archive you use to install the product.
Use the unzip command to extract the archive.When you have
extracted the files,you will find the installation script
installSAM in the following directory:SAM3210MPSunOS
Supported platforms
IBM Tivoli System Automation Version 3.2,supports the following UNIX and
Linux environments:Linux on System z,Linux on System x,Linux on Power,AIX
5.3 and 6.1,and Solaris 10.
IBM Tivoli System Automation runs on all IBM Systems machines running Linux,
on IBM System p machines running AIX,and on Sun SPARC or compatible
systems running Solaris.Additionally,System Automation runs under VMware on
IBM System x (except Intel IA64 based servers) and any other 32-bit Intel based
server,AMD Opteron based server (64-bit),or Intel EM64T based server (64 bit).
The following table lists the supported operating system versions.For the latest
information,refer to the IBM Tivoli System Automation for Multiplatforms Release
Notes on the IBM Tivoli System Automation home page:
www.ibm.com/software/tivoli/products/sys-auto-multi/
The latest version of the release notes is available behind the Product manuals
link.
Table 5.Supported UNIX and Linux platforms of IBM Tivoli System Automation
IBMSystem
x
1
IBMSystem z Power
Systems
Sun
SPARC
SUSE SLES 10 (32-bit)
3
x
4
IBM Tivoli System Automation:Installation and Configuration Guide
Table 5.Supported UNIX and Linux platforms of IBM Tivoli System Automation (continued)
IBMSystem
x
1
IBMSystem z Power
Systems
Sun
SPARC
SUSE SLES 10 (64-bit)
3
x x x
SUSE SLES 11 (32-bit) x
SUSE SLES 11 (64-bit) x x x
Red Hat RHEL 5 (32-bit) x
Red Hat RHEL 5 (64-bit) x x x
AIX 5.3 x
2
AIX 6.1 x
5
AIX 7.1 x
Solaris 10 (64-bit) x
4,6
All SP levels of the listed supported SUSE versions and all SP levels higher than
the listed Red Hat version/SP levels are also supported,unless one of the
following notes indicates a more specific minimum requirement.
Notes:
1.System x (except Intel IA64 based servers) and any other 32-bit Intel based
server,or AMD Opteron based server (64-bit),or Intel EM64T based server (64
bit).
2.Requires C++ Runtime Library for AIX,version 7.0.0.1,which is included in
PTFs U800738 and U800739.
3.SP1 must be installed.
4.Solaris 10 on Sun SPARC 64-bit systems or fully compatible SPARC 64-bit
clones.The IBM Tivoli System Automation operations console is not available
within the Solaris environment,but an operations console on another platform
can be associated with a Solaris-based cluster.
5.AIX 6.1 supports Workload Partition (WPAR) mobility or relocation.IBM Tivoli
System Automation and RSCT do not support domains with nodes that are
System WPARs.
6.IBM Tivoli System Automation and RSCT do not support domains with nodes
that are Solaris zone containers.
Supported network interfaces
All platforms support 10 Megabit Ethernet,Fast Ethernet,and Gigabit Ethernet.In
addition,the System z platform also supports HiperSockets,CTC,and VM Guest
LAN.
Live Partition Mobility support
Requirements
With AIX Level 6100-00-01 (or higher) installed on the source and destination
POWER6 servers,the Live Partition Mobility feature can be used to migrate an
LPAR running as an System Automation for Multiplatforms node without affecting
the state or operation of the System Automation for Multiplatforms cluster,
provided the System Automation for Multiplatforms cluster is configured to use
standard (that is,default) heartbeat settings.In that case,the effect on the
application servers running under System Automation for Multiplatforms control is
a brief suspension of operations during the migration.Neither System Automation
for Multiplatforms nor the application servers will have to be restarted.
Chapter 1.Installing on UNIX and Linux
5
You may test to validate that the period of suspension during Live Partition
Mobility will not cause unwanted cluster events.Unwanted cluster events will
occur if a configured number of heartbeats is missing from the node experiencing a
suspend during Live Partition Mobility.If testing shows that the average period of
suspension may cause too many heartbeats to be missed,the heartbeat settings
should be relaxed for the time of Live Partition Mobility.
Another way to greatly minimize the chance of unwanted cluster events while an
LPAR is moved is to simply stop the peer domain forcefully before the move is
initiated with stoprpdomain -f,i.e.without stopping the applications managed by
the cluster services.Then upon successful completion of the move,simply restart
the peer domain.
For more information on how to properly configure POWER6 servers for Live
Partition Mobility and restrictions on its use,refer to http://
www14.software.ibm.com/webapp/set2/sas/f/pm/component.html.
Limitations:
v Disk tie breaker is not supported by virtual SCSI which is a prerequisite of Live
Partition Mobility.
Preparing for installation
IBM Tivoli System Automation is contained in several packages that must be
installed on every cluster node that you want to automate.Package type and
content depend on the operating system on which you are installing IBM Tivoli
System Automation.
Notes:
1.The software packages must be available on the nodes on which you want to
install IBM Tivoli System Automation.For example,you can mount the
CD-ROM on a PC and use FTP to transfer the files to the node,or you can
install the packages over a shared Network File System.
2.To be sure that the software packages are installed and uninstalled in the
correct order,use the IBM Tivoli System Automation scripts installSAMand
uninstallSAM.
Table 6.Software packages available for installation,based on your operating system
Operating system Type of package Content
Linux RPM packages IBM Tivoli System
Automation RPMs and
RSCT
1
RPMs.
AIX installp file sets IBM Tivoli System
Automation installp file sets
and RSCT
1
packages.
Solaris Solaris packages IBM Tivoli System
Automation packages and
RSCT
1
packages.
Notes:
1.RSCT (Reliable Scalable Cluster Technology) is the infrastructure used by IBM
Tivoli System Automation to provide clusters with improved system
availability,scalability,and ease of use.
6
IBM Tivoli System Automation:Installation and Configuration Guide
Prerequisites
Before starting the installation you must fulfill these requirements:
v You need to have root authority to install System Automation for Multiplatforms
on the system.
v A Korn shell must be installed.
v Perl is required to use the command line interface of IBM Tivoli System
Automation for Multiplatforms including native RSCT commands.It is,by
default,installed on your Linux,AIX,or Solaris systems as part of the operating
system,but if you are using IBM Tivoli System Automation in a language other
than English,a special version of Perl may be required.Due to known problems
with Perl 5.8.0 and how it handles UTF-8 encoded locales,some characters may
not be properly displayed.This can occur on systems with Perl 5.8.0 installed,
while using a UTF-8 encoded locale.When previous or subsequent versions of
Perl are used,or non-UTF-8 encoded locales are used,this problem does not
occur.
If you decide to upgrade your Perl 5.8.0 version on a Linux distribution,
perform the following steps:
1.Download the Perl 5.8.1 source:http://dev.perl.org/perl5/news/2003/perl-
5.8.1.html.
2.Unzip and tar -xvf on any directory.
3.Compile and install on the UTF-8 machine,referring to the instructions
provided with the downloaded files.
4.Change the symbolic link pointing to the directory of the Perl version that is
used by IBM Tivoli System Automation from:/usr/sbin/rsct/perl5/bin/
perl->/usr/bin/perl to the directory where the new version of Perl is per
default installed:
/usr/sbin/rsct/perl5/bin/perl->/usr/local/bin/perl.
v On AIX,the 32-bit version of Java 1.4.2 or Java 5 SR5 (or higher) is required.
v On Linux,make sure that the 32-bit version of the C++ library libstdc++.so.5 is
installed.
v Also make sure that the directories/usr/sbin and/opt have at least 100 MB free
space,and that the directory/var also provides at least 100 MB free space.
v On any node where the end-to-end automation adapter is configured to run,at
least 128 MB RAM must be available.
v During installation of IBM Tivoli System Automation on AIX,the levels of RSCT
packages required by IBM Tivoli System Automation are checked against the
levels of RSCT packages already installed with the operating system,and
missing packages or higher levels of RSCT packages are installed if required.
Under certain circumstances,you may need to manually install higher levels of
certain RSCT packages.For example,if the RSCT basic package is not installed,
and the level of the installed RSCT core package is higher than the level of the
RSCT packages supplied with IBM Tivoli System Automation,the installation of
the RSCT basic package may fail due to RSCT prerequisites not being met.You
need to download and install the appropriate RSCT filesets from the AIX service
center to ensure that all RSCT packages installed are at the same level.
v For other operating system-specific requirements,see the requirements Web page
at
http://www.ibm.com/software/tivoli/products/sys-auto-multi/requirements.html
v For languages using the double-byte character set (DBCS),the Telnet dialog
buffer must be sufficiently large to ensure that long messages are properly
displayed.If this is not the case,enlarge the Telnet dialog buffer.
Chapter 1.Installing on UNIX and Linux
7
v In the current Red Hat 5 distributions,the SELinux environment is switched on
by default.It must be switched off for IBM Tivoli System Automation to work
properly.
Considerations regarding clusters
Load on nodes:IBM Tivoli System Automation requires some of its subsystems to
be processed constantly on the node to ensure that the cluster services are working
properly (for example,heartbeating and communication between those
subsystems).If this is not guaranteed,System Automation may trigger critical
resource protection methods in case those subsystems cannot communicate in a
given period of time.This leads eventually to a reboot of the node on which this
issue occurs.To prevent this,it is recommended that the following prerequisites
are satisfied:
v Constant I/O and swap load < 10%
For information about critical resource protection methods,see IBM Tivoli System
Automation for Multiplatforms a_u_g.
Number of nodes in a cluster:Solaris,Linux,AIX 5.3:The maximum number of
nodes in a cluster is 32.
AIX 6.1:The maximum number of nodes in a cluster is 130.
Initial configurations
You must perform these initial configurations:
v On all nodes,set and export the environment variable
CT_MANAGEMENT_SCOPE to 2 (peer domain scope) for all users of IBM
Tivoli System Automation:
export CT_MANAGEMENT_SCOPE=2
To permanently set the variable,set and export it in the profile.
On SLES systems,you can create scripts in/etc/profile.d with the following
content:
sa_mp.sh:
export CT_MANAGEMENT_SCOPE=2
sap_mp.csh:
setenv CT_MANAGEMENT_SCOPE 2
v Make sure that the environment variable LANG is set to one of the supported
locales for the root user.To set the environment variable,use the command:
export LANG=xx_XX
where xx_XX denotes one of the supported languages.
Installing and upgrading IBM Tivoli SystemAutomation
This section covers the following topics:
v If you are performing an initial installation of IBM Tivoli System Automation,
see the topic “Installing IBM Tivoli System Automation on UNIX and Linux” on
page 9 below.
v If a previous version of IBM Tivoli System Automation is already installed,you
need to perform some steps before the new version of IBM Tivoli System
Automation can be installed.To perform a migration to a new version of the
product,see the topic “Migrating IBM Tivoli System Automation” on page 14.
8
IBM Tivoli System Automation:Installation and Configuration Guide
Installing IBM Tivoli SystemAutomation on UNIX and Linux
You use an installation script to install IBM Tivoli System Automation.The
installation script performs the following actions:
v A complete prerequisites check to verify that all prerequisites are available and
at the required level.If your system does not pass the check,the installation
does not start,and you need to provide the missing prerequisites and restart the
installation.
v Installs IBM Tivoli System Automation,including the end-to-end automation
adapter.
To avoid having to restart the installation,you can invoke the prerequisites check
separately,before starting the installation.
Performing the prerequisites check
Complete the following steps:
1.Get root authority.
2.If you downloaded the tar file from the Internet,extract the file,using the
following command:
tar -xvf <tar file>
If you got the product on a CD,mount the CD and change to the directory
where the CD is mounted.
3.Enter the following command:
v Linux:cd SAM3210MPLinux
v AIX:cd SAM3210MPAIX
v Solaris:cd SAM3210MPSunOS
For information about supported platforms,see “Supported platforms” on page
4
4.To start the prerequisites check,issue the following command:
./prereqSAM
Typically,you do not need to specify any of the options that are available for
the prereqSAMcommand.For a detailed description of the command,refer to
IBM Tivoli System Automation for Multiplatforms Reference.
5.When the check is complete,check the following log file for information about
missing prerequisites:
/tmp/prereqSAM.<#>.log
where <#> is a number;the highest number identifies the most recent log file.
6.If your system did not pass the prerequisites check,correct any problems before
starting the installation.
7.AIX only:Your AIX system is in an inconsistent state,if you have the following
error message:
lppchk:The following filesets need to be installed or corrected to bring the
system to a consistent state:
rsct.core.rmc 2.4.13.0 (not installed;requisite fileset)
Resolve the issues before you continue the installation.You can check the
consistency of the system manually using the following commands:
lppchk -v"rsct*"
lppchk -v"sam*"
Chapter 1.Installing on UNIX and Linux
9
Installing IBM Tivoli SystemAutomation
Before you begin:
If an RSCT peer domain already exists,ensure that the node on which you are
invoking the script is offline in the domain.Otherwise,the installation will be
canceled.
To install the product,including the automation adapter,perform the following
steps:
1.Get root authority.
2.If you downloaded the tar file from the Internet and have not yet extracted the
file,extract it using the following command:
tar -xvf <tar file>
If you got the product on a CD,mount the CD and change to the directory
where the CD is mounted.
3.Enter the following command:
v Linux:cd SAM3210MPLinux
v AIX:cd SAM3210MPAIX
v Solaris:cd SAM3210MPSunOS
4.Invoke the installation script:
./installSAM
Typically,you do not need to specify any of the options that are available for
the installSAMcommand.For a detailed description of the command,refer to
IBM Tivoli System Automation for Multiplatforms Reference.
5.Read the information in the License Agreement and the License Information
that is displayed.You can scroll forward line by line using the"Enter"key,and
page by page using the"spacebar",which is basically the"more"functionality
in UNIX.Once you have scrolled to the bottom of the License information file
and you want to accept the terms of the license agreement,type'y'.Any other
input will cancel the installation.
The installation is also canceled when no license file is found.
6.After you accept the license agreement,the installation program performs a
complete prerequisites check to verify that all prerequisites are available and at
the required level.
If your system does not pass the check,the installation does not start,and you
need to provide the missing prerequisites and restart the installation.
Information about the results of the prerequisites check is available in the log
file/tmp/installSAM.<#>.log (for details,see step 7).
If your system passed the check,the product,including the automation adapter,
is installed.
7.Check the following log file for information about the installation:
/tmp/installSAM.<#>.log
where <#> is a number;the highest number identifies the most recent log file.
The entries in the log file have the following prefixes:
prereqSAM
Entries that were written during the prerequisites check.
installSAM
Entries that were written during the installation of the product.
10
IBM Tivoli System Automation:Installation and Configuration Guide
8.To find out which packages were installed,inspect/tmp/installSAM.<#>.log,
where <#> is the highest number in the list of logs you find.
Post-installation tasks
When you have installed IBM Tivoli System Automation on AIX,perform the
following task:
Configure the system logger on AIX
The system logger is not configured by default.Messages are written to the
error log.
To be able to obtain the debug data,it is recommended that you configure
the system logger in the file/etc/syslog.conf.When you have made the
necessary changes,you must recycle the syslogd using the command
refresh –s syslogd.The location of the log file is defined in
/etc/syslog.conf.
No further action is required in the case of Linux.
If you have installed IBM Tivoli System Automation on Solaris,perform the
following task:The man pages are installed under the/usr/share/man directory.
Ensure that the MANPATH environment variable is not defined or the path
/usr/share/man is contained in the MANPATH environment variable.
Make shared volume groups enhanced concurrent capable on AIX:If your
shared volume groups are not enhanced concurrent capable,when a node crashes
the disks will be locked and the remote node will not be able to access the disk.To
avoid this situation,you should make the shared volume group enhanced
concurrent capable.
Before making the volume group enhanced concurrent capable,use the lsvg
command to view information about the shared volume group:
#lsvg vgERSTZ0
VOLUME GROUP:vgERSTZ0 VG IDENTIFIER:
00c31bfe00004c0000000118c2f1ead2
VG STATE:active PP SIZE:4 megabyte(s)
VG PERMISSION:read/write TOTAL PPs:255 (1020
megabytes)
MAX LVs:256 FREE PPs:14 (56 megabytes)
LVs:2 USED PPs:241 (964 megabytes)
OPEN LVs:2 QUORUM:2 (Enabled)
TOTAL PVs:1 VG DESCRIPTORS:2
STALE PVs:0 STALE PPs:0
ACTIVE PVs:1 AUTO ON:no
MAX PPs per VG:32512
MAX PPs per PV:1016 MAX PVs:32
LTG size (Dynamic):256 kilobyte(s) AUTO SYNC:no
HOT SPARE:no BB POLICY:relocatable
To make a volume group enhanced concurrent capable using SMIT:
1.Enter the following command:
#smitty vg
Text similar to the following is displayed:
Set Characteristics of a Volume Group
Change a Volume Group
* VOLUME GROUP name vgERSTZ0
* Activate volume group AUTOMATICALLY no +
at system restart?
Chapter 1.Installing on UNIX and Linux
11
* A QUORUM of disks required to keep the volume yes +
group on-line?
Convert this VG to Concurrent Capable?enhanced concurrent
2.Press ENTER.
To make the volume group enhanced concurrent capable from the command line,
enter the following command:
#/usr/sbin/chvg -a’n’ -Q’y’ ’-C’ <VOLUME_GROUP_NAME>
After making the volume group enhanced concurrent capable,the lsvg command
returns information similar to the following:
#lsvg vgERSTZ0
VOLUME GROUP:vgERSTZ0 VG IDENTIFIER:
00c31bfe00004c0000000118c2f1ead2
VG STATE:active PP SIZE:4 megabyte(s)
VG PERMISSION:read/write TOTAL PPs:255 (1020
megabytes)
MAX LVs:256 FREE PPs:14 (56 megabytes)
LVs:2 USED PPs:241 (964 megabytes)
OPEN LVs:2 QUORUM:2 (Enabled)
TOTAL PVs:1 VG DESCRIPTORS:2
STALE PVs:0 STALE PPs:0
ACTIVE PVs:1 AUTO ON:no
Concurrent:Enhanced-Capable Auto-Concurrent:Disabled
VG Mode:Non-Concurrent
MAX PPs per VG:32512
MAX PPs per PV:1016 MAX PVs:32
LTG size (Dynamic):256 kilobyte(s) AUTO SYNC:no
HOT SPARE:no BB POLICY:relocatable
Installing the product license
IBM Tivoli System Automation requires that a valid product license is installed on
each system it is running on.The license is contained on the installation medium
in the'license'sub directory.The installation of the license is usually performed
during the product installation process.In case this did not succeed,issue the
following command to install the license:
samlicm –i license_file
In order to display the license,issue:
samlicm -s
See IBM Tivoli System Automation for Multiplatforms Reference for a detailed
description of the samlicm command.
Upgrading from a Try & Buy license to a full product license
If you have installed the Try & Buy version of IBM Tivoli System Automation and
then purchase the full product version,you will receive another copy of the
installation media,which contains the license file for the full license.
The license file is located on the installation medium in the license subdirectory.It
is recommended to perform the license upgrade by issuing the following
command:
samlicm -i <license_file_name>
In order to display the license,issue:
samlicm -s
12
IBM Tivoli System Automation:Installation and Configuration Guide
After upgrading the license,you should check if any updates for IBM Tivoli
System Automation are already available and install the latest service level.
Languages and locales supported by IBM Tivoli System
Automation
If you want to use IBM Tivoli System Automation in a language other than
English,or if your default system locale is a non-English locale,use the following
sections to find out which languages and locales are supported.
IBM Tivoli SystemAutomation on Linux
Table 7 shows the combinations of languages and locales that are supported for
IBM Tivoli System Automation on Linux systems to display translated messages.
New versions of Linux operating systems may not support all of the listed
encoding.UTF-8 encoding is always supported.
Table 7.Languages and locales supported by IBM Tivoli System Automation on Linux systems
Language UTF-8 ISO-8859-1 EUC/GBK Euro GB18030/BIG5
German de_DE.UTF-8 de_DE,
de_DE.ISO-8859-1
de_DE@euro
Spanish es_ES.UTF-8 es_ES,
es_ES.ISO-8859-1
es_ES@euro
French fr_FR.UTF-8 fr_FR,
fr_FR.ISO-8859-1
fr_FR@euro
Italian it_IT.UTF-8 it_IT,
it_IT.ISO-8859-1
it_IT@euro
Japanese ja_JP.UTF-8 ja_JP.eucJP
Korean ko_KR.UTF-8 ko_KR.eucKR
Brazilian
Portuguese
pt_BR.UTF-8 pt_BR
Simplified
Chinese
zh_CN.UTF-8 zh_CN.GBK,
zh_CN.GB2312
zh_CN.GB18030
Traditional
Chinese
zh_TW.UTF-8 zh_TW.Big5,
zh_TW
IBM Tivoli SystemAutomation on AIX
The table below shows the combinations of languages and locales that are
supported for IBM Tivoli System Automation on AIX to display translated
messages.
Table 8.Languages and locales supported by IBM Tivoli System Automation on AIX systems
Language UTF-8 ISO-8859-1 EUC/GBK SJIS/GB18030/BIG5
German DE_DE de_DE
Spanish ES_ES es_ES
French FR_FR fr_FR
Italian IT_IT it_IT
Japanese JA_JP ja_JP Ja_JP
Korean KO_KR ko_KR
Brazilian Portuguese PT_BR pt_BR
Simplified Chinese ZH_CN zh_CN Zh_CN
Chapter 1.Installing on UNIX and Linux
13
Table 8.Languages and locales supported by IBM Tivoli System Automation on AIX systems (continued)
Language UTF-8 ISO-8859-1 EUC/GBK SJIS/GB18030/BIG5
Traditional Chinese ZH_TW zh_TW Zh_TW
IBM Tivoli SystemAutomation on Solaris
The following table shows the combinations of languages and locales that are
supported for IBM Tivoli System Automation on Solaris systems to display
translated messages.New versions of the Solaris operating system may not
support all of the listed encoding.UTF-8 encoding is always supported.
Table 9.Languages and locales supported by IBM Tivoli System Automation on Solaris systems
Language UTF-8 ISO-8859-1 EUC/GBK Euro GB18030/BIG5
German de_DE.UTF-8 de_DE.ISO-8859-1 de_DE.ISO-8859-15
Spanish es_ES.UTF-8 es_ES.ISO-8859-1 es_ES.ISO-8859-15
French fr_FR.UTF-8 fr_FR.ISO-8859-1 fr_FR.ISO-8859-15
Italian it_IT.UTF-8 it_IT.ISO-8859-1 it_IT.ISO-8859-15
Japanese ja_JP.UTF-8 ja_JP.eucJP
Korean ko_KR.UTF-8 ko_KR.EUC
Brazilian
Portuguese
pt_BR.UTF-8 pt_BR.ISO-8859-1
Simplified
Chinese
zh_CN.UTF-8 zh_CN.GBK,
zh_CN.EUC
zh_CN.GB18030
Traditional
Chinese
zh_TW.UTF-8 zh_TW.EUC zh_TW.BIG5
Migrating IBM Tivoli SystemAutomation
You can migrate to IBM Tivoli System Automation V3.2 if an older version of IBM
Tivoli System Automation is already installed.
Review the following considerations before migrating one or more nodes to a
newer level:
v The migration process starts when any node within the active cluster is
upgraded to the higher code level.
v You can always upgrade to a higher code level.Downward migration is not
possible.
v The migration process is only complete when the active version number is equal
to the highest installed code version number.Until then,different code levels
can coexist.See “Verifying the active and installed version number” on page 16
and “Completing the migration” on page 16 how to complete the migration
process.
You can use one of the following procedures to migrate IBM Tivoli System
Automation to a higher level:
v It is recommended to use the procedure described in “Migrating an entire
domain” on page 15
v “Performing a node-by-node migration” on page 15
14
IBM Tivoli System Automation:Installation and Configuration Guide
Migrating an entire domain
During the migration,the domain will not be available.To minimize downtime,
you can perform a prerequisites check before you start the actual migration (for
more information,see “Performing the prerequisites check” on page 9).
To migrate an entire domain,perform these steps:
1.Make sure that all resources are offline:
a.Check if the end-to-end automation adapter is running:
samadapter status
If it is running,stop the automation adapter:
samadapter stop
b.Stop all online resource groups by setting their NominalState to Offline:
chrg -o Offline <resource-group-name>
2.If the domain is online,stop the domain:
stoprpdomain <domain-name>
3.On AIX,execute the following command after the cluster has been stopped and
before the installation is started:
#/usr/sbin/slibclean
4.Run the./installSAMscript from the installation directory on the product CD
or from the extracted electronic deliverable on all nodes.For more information
on the installSAMscript,see “Installing IBM Tivoli System Automation on
UNIX and Linux” on page 9.
5.Start the domain:
startrpdomain <domain-name>
6.Check the code levels with the lssrc –ls IBM.RecoveryRMcommand (see the
sample in “Verifying the active and installed version number” on page 16).All
nodes should have the newly installed code level,but the active code level
should still be the previous one.
7.In order to activate the new version,continue with “Completing the migration”
on page 16.
Performing a node-by-node migration
Node-by-node migration is only supported when migrating from IBM Tivoli
System Automation V2.3 or higher.Migrating the nodes of a domain one by one
has the advantage that IBM Tivoli System Automation remains available during
the migration.To further minimize downtime,you can perform a prerequisites
check before you start the actual migration (for more information,see “Performing
the prerequisites check” on page 9).
To perform a node-by-node migration,do this:
1.Exclude the node from automation to ensure that resources that must be kept
available are moved to another node in the peer domain:
samctrl -u a <node>
Note that the move operations may take a moment.
2.Stop the node from another node in the domain,and verify that it is stopped:
stoprpnode <node>;lsrpnode
3.To upgrade the node,run the script./installSAMfrom the installation directory
on the product CD or from the extracted electronic deliverable.For more
information on the installSAMscript,see “Installing IBM Tivoli System
Automation on UNIX and Linux” on page 9.
Chapter 1.Installing on UNIX and Linux
15
4.Start the node:
startrpnode <node>
5.Include the upgraded node in automation again:
samctrl -u d <node>
6.The upgraded node can now join the existing domain.Use the lssrc –ls
IBM.RecoveryRMcommand (see the sample in “Verifying the active and
installed version number”) to display the installed version and the active
version of the product.The new code features will not be activated until the
active IBM Tivoli System Automation version number is equal to the highest
IBM Tivoli System Automation version number installed within the cluster,and
you cannot fully utilize these new code features until all the nodes are
upgraded.
7.Repeat the steps 1-6 for other nodes within the cluster.
8.In order to activate the new version continue with “Completing the migration.”
Verifying the active and installed version number
After the upgrade the new features of the new code are not yet activated.The
previous and new code levels can coexist until the migration is complete.The lssrc
–ls IBM.RecoveryRMcommand shows you the active version number AVN and
the installed version number IVN of the product.When IVN and AVN are the
same,migration is complete.
The output looks like:
In order to activate the new version,continue with “Completing the migration.”
Completing the migration
In order to check and complete the migration,perform the following steps:
1.Make sure that the domain is started and that all nodes in the domain are
online.
2.Issue the lsrpdomain command to display the version of RSCT that is active in
the peer domain,and the mixed version status:
Name OpState RSCTActiveVersion MixedVersions TSPort GSPort
SA_Domain Online 2.5.5.1 Yes 12347 12348
3.Issue the lsrpnode command to display which version of RSCT that is installed
on the nodes.Keep in mind that all nodes must be online:
Subsystem:IBM.RecoveryRM
PID:31163
Cluster Name:xdr43
Node Number:1
Daemon start time:02/19/10 15:12:00
Daemon State:
My Node Name:lnxxdr43
Master Node Name:lnxxdr43 (node number = 1)
Our IVN:3.2.1.0
Our AVN:3.2.1.0
Our CVN:d4b7e876c (4b7e876c)
Total Node Count:2
Joined Member Count:2
Config Quorum Count:2
Startup Quorum Count:1
Operational Quorum State:HAS_QUORUM
In Config Quorum:TRUE
In Config State:TRUE
Replace Config State:FALSE
Figure 1.Verifying the active and installed version numbers
16
IBM Tivoli System Automation:Installation and Configuration Guide
Name OpState RSCTVersion
node01 Online 2.5.5.1
node02 Online 2.5.5.1
node03 Online 2.5.5.1
4.If the RSCT peer domain is running in mixed version mode (MixedVersions =
Yes) and all nodes have been upgraded to the new release of IBM Tivoli System
Automation,you must update the active RSCT version by running the RSCT
CompleteMigration action on one of the nodes.Before running the action,
review the RSCT migration preparation procedures in IBM RSCT Administration
Guide.
To update the RSCTActiveVersion,make sure that all nodes are online,and
issue the following command on one of the nodes:
runact -c IBM.PeerDomain CompleteMigration Options=0
To verify that the active RSCT version has been updated,issue the lsrpdomain
command again:
Name OpState RSCTActiveVersion MixedVersions TSPort GSPort
SA_Domain Online 2.5.5.1 No 12347 12348
5.Run the samctrl -m command to activate the new features of the new code and
to finish the migration.For more information about the command,refer to IBM
Tivoli System Automation for Multiplatforms Reference.
The code version of the ActiveVersion and the InstalledVersion of IBM Tivoli
System Automation should now be the same for all nodes.Until this is true,the
new code features have not been activated and cannot be used.
Migrating AIX version 5 to 6
To migrate the AIX operating system from version 5 to 6 on the node where
System Automation for Multiplatforms runs,the following steps need to
performed.
v Stop System Automation for Multiplatforms before the migration starts.
v Migrate System Automation for Multiplatforms to the required version to run on
AIX 6.
v Start System Automation for Multiplatforms after the migration again.
Execute the following commands:
1.Exclude the node that you want to update:
samctrl -u a <node-name>
2.Stop the node that you want to update:
stoprpnode <node-name>
3.Execute a migration installation from AIX 5 to AIX 6 on the node that you
stopped.
Note:If you have the default configuration installed and syslog.out is located in
the/tmp directory,recreate/tmp/syslog.out again using the touch
command.The/tmp directory is deleted during the AIX migration.
Refresh syslogd with the command:
refresh -s syslogd
4.Install the same SA MP level that is already installed on top of the currently
installed version.This is necessary to get the correct AIX install package
installed,for example SA MP 3.1.0.0 upgrades to SA MP 3.1.5.0.
Enter the following command:
installSAM
Chapter 1.Installing on UNIX and Linux
17
5.Start the updated node from an online node within the domain:
startrpnode <node-name>
6.Include the updated node:
samctrl -u d <node-name>
18
IBM Tivoli System Automation:Installation and Configuration Guide
Chapter 2.Installing on Windows
The following sections describe planning,preparation,and installation of IBM
Tivoli System Automation on Windows:
v “Planning for the installation.”
v “Preparing the system” on page 20.
v “Installing or upgrading” on page 24.
Planning for the installation
You can install IBM Tivoli System Automation on Windows from CD or,if you
prefer electronic delivery,download the product archive from the Web after you
have purchased IBM Tivoli System Automation.
IBM Tivoli SystemAutomation installation CD
The CD labeled IBM Tivoli System Automation for Multiplatforms 3.2.1 - Windows
contains scripts and software packages for Windows.
To install IBM Tivoli System Automation on Windows,you use the installation
program setup.exe which is located in the following directory:
SAM3210MPWindows\Windows
IBM Tivoli SystemAutomation installation archive
The name of the self-extracting archive is CZP2SML.exe.After extraction,the
installation program setup.exe is available in the following directory:
SAM3210MPWindows\Windows
Subsystem for Unix-based applications
IBM Tivoli System Automation for Multiplatforms uses the Windows component
"Subsystem for Unix-based Applications"(SUA).This component is shipped with
Windows Server 2008.It provides a POSIX-compatible subsystem on top of the
Windows kernel and enables UNIX programs to be run on Windows.Several
UNIX utilities are also available for SUA,including ksh,gcc,perl,and vi.To get
these utilities,you have to download the"Utilities and SDK for UNIX-based
Applications"update package from Microsoft.This update package is a
requirement for IBM Tivoli System Automation as well.
Supported languages and locales
The table below shows the combinations of languages and locales that are
supported for IBM Tivoli System Automation on Windows to display translated
messages.
Table 10.Languages and locales supported by IBM Tivoli System Automation on Windows
Language ISO-8859-1 EUC/GBK SJIS
German de_DE.ISO-8859-1 - -
French fr_FR.ISO-8859-1 - -
Japanese ja_JP.EUC-JP win-ja_windows-932
All nodes in a cluster must have the same Windows system language.Clusters
with different Windows system languages on each node is not supported.For
© Copyright IBM Corp.2006,2010
19
example,a cluster with a Japanese Windows operating system on one node and a
French Windows operating system on a different node.
Setting a specific locale in the Korn shell is not affected by this restriction.For
example,a cluster with an English Windows operating system on all nodes can
work with Korn shells with locales set for Japanese,French,or German.
Note:Due to limitations in the system log daemon of the Subsystem for
UNIX-based Applications (SUA) used by IBM Tivoli System Automation on
Windows,messages to the system log are only available in English.
Preparing the system
Prerequisites
The following prerequisites must be met:
Table 11.Supported Windows platforms of System Automation for Multiplatforms
System x
1
32 bit 64 bit
Windows Server 2008 R1 Standard
Edition
X X
Windows Server 2008 R1 Enterprise
Edition
X X
Windows Server 2008 R2 Standard