|
|
< Day Day Up > |
|
We followed these steps to create the cluster resources.
In order for the oserv service to fail over, we created a resource in the cluster manager for both oserv services. We opened up the cluster manager first on the primary node, and then on the secondary node. We right-clicked the cluster
The trip service is required for the oserv to process correctly, so we also had to create a resource for it in the cluster manager. We opened up the cluster manager on either the primary or secondary node, right-clicked the cluster group, and selected new resource . We defined trip as a generic service and added the required information.
To set up the resource dependencies, right-click the oserv resource and set it so that the virtual hostname, virtual IP, quorum disk, shared disk and trip are set as dependencies. Without setting up these dependencies, the oserv could possibly get in to an infinite failover loop.
|
|
< Day Day Up > |
|
|
|
< Day Day Up > |
|
Follow these steps to validate and back up your configuration.
Open the cluster manager and initiate a failover. Verify that the oserv service starts on each node. If failover works, bring down the oserv on each node and verify that the cluster will fail over successfully. If the backup of the Tivoli databases works, it means that you have successfully installed Framework 3.7b on a Windows cluster.
This is the most important part of the installation-if all the validation tests are positive, back up your Tivoli databases by running the wbkupdb command.
|
|
< Day Day Up > |
|
|
|
< Day Day Up > |
|
|
AFS |
Andrew File System |
|
AIX |
Advanced Interactive Executive |
|
APAR |
authorized program analysis report |
|
API |
Application Program Interface |
|
BDM |
Backup Domain Manager |
|
BMDM |
Backup Master Domain Manager |
|
CLI |
command line interface |
|
CMP |
cluster multi-processing |
|
CORBA |
Common Object Request Broker Architecture |
|
CPU |
ITWS workstation |
|
CWOF |
cascading without fallback |
|
DHCP |
Dynamic Host Configuration Protocol |
|
DM |
Domain Manager |
|
DNS |
Domain
|
|
ESS |
IBM TotalStorage Enterprise Storage Server |
|
FTA |
Fault Tolerant Agent |
|
FTP |
File Transfer Protocol |
|
HA |
high availability |
|
HACMP |
High Availability Cluster Multi-Processing |
|
HAGEO |
High Availability Geographic Cluster system |
|
HCL |
Hardware Compatibility List |
|
IBM |
International Business Machines Corporation |
|
IP |
Internet Protocol |
|
IPAT |
IP Address Takeover |
|
ITSO |
International Technical Support Organization |
|
ITWS |
IBM Tivoli Workload Scheduler |
|
JFS |
Journaled File System |
|
JSC |
Job Scheduling Console |
|
JSS |
Job Scheduling Services |
|
JVM |
Java Virtual Machine |
|
LCF |
Lightweight Client Framework |
|
LVM |
Logical Volume Manager |
|
MDM |
Master Domain Manager |
|
MIB |
Management Information Base |
|
MSCS |
Microsoft Cluster Service |
|
NFS |
Network File System |
|
NIC |
Network Interface Card |
|
ODM |
Object Data Manager |
|
PERL |
Practical Extraction and Report Language |
|
PID |
process ID |
|
PTF |
program temporary fix |
|
PV |
physical volume |
|
PVID |
physical volume id |
|
RAM |
random access memory |
|
RC |
return code |
|
SA |
Standard Agent |
|
SAF |
System Authorization Facility |
|
SAN |
Storage Area Network |
|
SMIT |
System Management Interface Tool |
|
SNMP |
Simple Network Management Protocol |
|
SSA |
Serial Storage Architecture |
|
SCSI |
Small Computer System Interface |
|
STLIST |
standard list |
|
TCP |
Transmission Control Protocol |
|
TMA |
Tivoli Management Agent |
|
TMF |
Tivoli Management Framework |
|
TMR |
Tivoli Management Region |
|
TRIP |
Tivoli Remote Execution Service |
|
X-agent |
Extended Agent |
|
|
< Day Day Up > |
|