List of Examples

---

Chapter 3: High Availability Cluster Implementation

Example 3-1: lvsg -o output

Example 3-2: lsvg -l tiv_vg1 output

Example 3-3: lsvg -l tiv_vg1 output

Example 3-4: Command output of lsvg

Example 3-5: An entry in the /etc/filesystems file

Example 3-6: Output of an lspv command

Example 3-7: Output of lspv on node tivaix2

Example 3-8: lsvg -o output

Example 3-9: Verifying all shared volume groups are available on a cluster node

Example 3-10: Verifying no shared volume groups are online on a cluster node

Example 3-11: How to vary on all shared volume groups on a cluster node

Example 3-12: Logical volumes in each shared volume group varied on in a cluster node

Example 3-13: Mounts of logical volumes on shared volume groups on a cluster node

Example 3-14: Unmount logical volumes on shared volume groups on a cluster node

Example 3-15: How to vary off shared volume groups on a cluster node

Example 3-16: Verifying the currently installed maintenance level of AIX 5.2

Example 3-17: Confirming installation of fixes for APAR IY45695

Chapter 4: IBM Tivoli Workload Scheduler Implementation in a Cluster

Example 4-1: An example .profile for TWSusr

Example 4-2: twsinst script example for TIVAIX1

Example 4-3: twsinst script example for TIVAIX2

Example 4-4: Workstation definition for TIVIAIX1

Example 4-5: Workstation definition for TIVIAIX1

Example 4-6: Checking for IBM Tivoli Workload Scheduler process

Example 4-7: Installing JSS from the command line

Example 4-8: wlsinst -p command output

Example 4-9: wlsinst -p command output

Example 4-10: Example of a security file

Example 4-11: Output of makesec -v command

Example 4-12: Output of makesec command

Example 4-13: Output of wmaeutil command

Example 4-14: Output of wlookup command before adding additional instance

Example 4-15: Sample wtwsconn.sh command

Example 4-16: Output of wlookup command after adding additional instance

Example 4-17: Output of ps command

Example 4-18: Verifying the fix pack installation

Example 4-19: IBM Tivoli Workload Scheduler fix pack installation error

Example 4-20: The contents of /tmp/twspatchXXXXX.log

Example 4-21: How to determine a cluster node's HACMP node ID

Example 4-22: Show a system's SSA node number, taken from tivaix1

Example 4-23: Show a system's SSA node number, taken from tivaix2

Example 4-24: Ensure that target mode SSA is configured on a cluster node, taken from tivaix1

Example 4-25: Ensure that target mode SSA is configured on a cluster node, taken from tivaix2

Example 4-26: Display the target mode SSA files for tivaix1

Example 4-27: Display the target mode SSA files for tivaix2

Example 4-28: Sample start script for IBM Tivoli Workload Scheduler under HACMP

Example 4-29: Commands used by stop script to stop IBM Tivoli Workload Scheduler

Example 4-30: Sample stop script for IBM Tivoli Workload Scheduler under HACMP

Example 4-31: Commands to run to install custom HACMP start and stop scripts for IBM Tivoli Workload Scheduler

Example 4-32: How to determine in a script whether or not HACMP is running

Example 4-33: Using the clRGinfo command to determine the state of resource groups in a cluster

Example 4-34: Wait for currently executing jobs to exit

Example 4-35: Move a resource group using the clRGmove command

Example 4-36: All resources and attributes for resource group rg1

Example 4-37: All resources and attributes for resource group rg2

Example 4-38: Obtain the HACMP configuration using the cltopinfo command

Example 4-39: Gather detailed shared volume group information with the clharvest_vg command

Example 4-40: Configured IP addresses before starting HACMP Cluster services on tivaix1

Example 4-41: Configured IP addresses before starting HACMP Cluster services on tivaix2

Example 4-42: Configured IP addresses after starting HACMP Cluster services on tivaix1

Example 4-43: Configured IP addresses after starting HACMP Cluster services on tivaix2

Example 4-44: Using the command line to obtain the current status of all HACMP subsystems on a cluster node

Example 4-45: Using commands on tivaix1 to verify that tivaix2 falls over to tivaix1

Example 4-46: List resource groups in ONLINE state for a node

Example 4-47: Obtain a simple list of resource groups that are in the ONLINE state on a specific node

Example 4-48: Sample output of command to verify IBM Tivoli Workload Scheduler is moved by HACMP

Example 4-49: IBM Tivoli Workload Scheduler processes running on tivaix1 after falling back resource group rg2 to tivaix2

Example 4-50: IBM Tivoli Workload Scheduler processes running on tivaix2 after falling back resource group rg2 to tivaix2

Example 4-51: Organization of installation media

Example 4-52: Preparing for installation of IBM Tivoli Management Framework 4.1

Example 4-53: Initial installation of IBM Tivoli Management Framework Version 4.1

Example 4-54: Load Tivoli environment variables

Example 4-55: Script for installing IBM Tivoli Management Framework Version 4.1 with patches

Example 4-56: Add an IP alias to the Framework oserv server

Example 4-57: Identify the dispatcher number of a Framework installation

Example 4-58: Disable set_force_bind object dispatcher option

Example 4-59: Identify the dispatcher number of a Framework installation

Example 4-60: Back up the object database of IBM Tivoli Management Framework

Example 4-61: List all available object database backup files

Example 4-62: Verifying enough disk space in the current working directory for wbkupdb

Example 4-63: Install Job Scheduling Services component on cluster node tivaix1

Example 4-64: Install Connector component for cluster node tivaix1

Example 4-65: Verify installation of Framework components for IBM Tivoli Workload Scheduler

Example 4-66: Verify creation of initial Connector

Example 4-67: Identify which Connector objects already exist on a cluster node

Example 4-68: Create additional Connector object

Example 4-69: Verify creation of additional Connector object

Example 4-70: Create additional Connectors on tivaix2

Example 4-71: Remove a Connector

Example 4-72: Change Connector's directory value

Example 4-73: Identify which Framework Administrator object to modify to grant TWSuser account root-level Framework access

Example 4-74: Confirm TWSuser accounts are added to root Framework Administrator object

Example 4-75: Identify available Connectors to manage on cluster node

Example 4-76: Back up object database of IBM Tivoli Management Framework

Example 4-77: Contents of .rhosts file in home directory of root user

Example 4-78: Sampling Framework objects that exist before interconnection on tivaix1

Example 4-79: Sampling Framework objects that exist before interconnection on tivaix2

Example 4-80: Interconnect the Framework servers on tivaix1 and tivaix2

Example 4-81: Determine the encryption used in the Tivoli region of tivaix2

Example 4-82: Verify Framework interconnection

Example 4-83: Determine Tivoli region ID of cluster node

Example 4-84: Exchange useful and required resources for IBM Tivoli Workload Scheduler

Example 4-85: Verify on tivaix1 the exchange of Framework resources

Example 4-86: Verify on tivaix2 the exchange of Framework resources

Example 4-87: Check the user creation

Example 4-88: Header output for conman

Example 4-89: conman output

Example 4-90: conman output

Example 4-91: conman output

Chapter 5: Implement IBM Tivoli Management Framework in a Cluster

Example 5-1: Available SSA disks on tivaix1 before configuring shared volume groups

Example 5-2: Logical disks on tivaix1 before configuring shared volume groups

Example 5-3: How to show logical to physical SSA disk relationships on tivaix1.

Example 5-4: Available SSA disks on tivaix2 before configuring shared volume groups

Example 5-5: Logical disks on tivaix2 before configuring shared volume groups

Example 5-6: Show logical-to-physical SSA disk relationships on tivaix2

Example 5-7: How to list major numbers already in use on tivaix1

Example 5-8: Identify the major numbers used for shared volume groups on tivaix1

Example 5-9: Identify the major numbers used for shared volume groups on tivaix2

Example 5-10: Verify creation of shared volume group itmf_vg on tivaix1

Example 5-11: Verify successful creation of a JFS file system

Example 5-12: Identify logical volumes on new volume group

Example 5-13: Update relationship between renamed logical volumes and logical log volumes

Example 5-14: Verify the chfs command

Example 5-15: Verify the export of volume group itmf_vg from tivaix1

Example 5-16: Verify volume group itmf_vg is not already imported into tivaix1

Example 5-17: Verify import of volume group itmf_vg into tivaix1

Example 5-18: Verify the import of volume group itmf_vg into tivaix2

Example 5-19: Verify a volume group is not already active on a cluster node

Example 5-20: How to verify volume group itmf_vg is online on tivaix1

Example 5-21: Verify availability of a logical volume in a shared volume group

Example 5-22: Verify shared volume group itmf_vg on tivaix2

Example 5-23: Preparing for installation of IBM Tivoli Management Framework 4.1

Example 5-24: Initial installation of IBM Tivoli Management Framework Version 4.1

Example 5-25: Load Tivoli environment variables on tivaix1

Example 5-26: Script for installing IBM Tivoli Management Framework Version 4.1 with patches

Example 5-27: Add IP alias to Framework oserv server

Example 5-28: Identify dispatcher number of Framework installation

Example 5-29: Disable set_force_bind object dispatcher option

Example 5-30: Identify dispatcher number of Framework installation

Example 5-31: Create the new .tivoli directory

Example 5-32: Install a Managed Node

Example 5-33: Create a Gateway on tivaix1

Example 5-34: Verify no Endpoints exist within a Tivoli Enterprise installation

Example 5-35: Install a highly available Endpoint on cluster node tivaix1

Example 5-36: Verify installation of highly available Endpoint

Example 5-37: Identify directory location of LCF environment file

Example 5-38: Identify which instance of an Endpoint an LCF environment file is used for

Example 5-39: Stop an instance of an Endpoint

Example 5-40: Identify how an Endpoint starts during system restart

Example 5-41: Find all instances where IBM Tivoli Management Framework is started

Example 5-42: Script to start highly available IBM Tivoli Management Framework

Example 5-43: Script to stop highly available IBM Tivoli Management Framework

Example 5-44: Start script for highly available Endpoint

Example 5-45: Stop script for highly available Endpoint

Example 5-46: All resources and attributes for resource group rg1

Example 5-47: Output of cltopinfo command for hot standby Framework configuration

Example 5-48: Sample output of command to verify IBM Tivoli Management Framework is moved by HACMP

Example 5-49: Identify that an Endpoint is running on a cluster node

Example 5-50: f:\Tivoli\lcf\dat\2\last.cfg file

Appendix A: A Real-Life Implementation

Example A-1: /usr/es/sbin/cluster/utilities/cllscf > cl_top.txt

Example A-2: /usr/es/sbin/cluster/utilities/clshowres -g'twsmdmrg' > rg_top.txt

Example A-3: fconfig -a output

Example A-4: smit logs

---