Deployment Guide Series: IBM Tivoli Monitoring V6.2

192 Deployment Guide Series: IBM Tivoli Monitoring V6.2

The phases

We can summarize the phases described in Figure 4-11 on page 191 as follows:

1. Phase A: Migrate the infrastructure.

2. Phase B: Migrate endpoints.

3. Phase C: Migrate profiles.

4. Phase D: Migrate profile managers.

The steps

Each of the phases in the upgrade is an iterative process that follows these

workflow steps:

1. Assess: This step consists of an assessment of the IBM Tivoli Monitoring

V5.1.2 resource and a mapping to the corresponding IBM Tivoli Monitoring

V6.2 resource together with the upgrade status and migration settings.

2. Analyze: During this step, you analyze the IBM Tivoli Monitoring V5.1.2

resources that have not yet been migrated, inspect the proposed migration

settings, and provide information when needed in the generated XML files.

3. Migrate: This steps represents the actual migration of a set of non-migrated

IBM Tivoli Monitoring V5.1.2 resources to IBM Tivoli Monitoring V6.2.

4. Review results and check status: This is the last step to review the outcome

of the object migration and monitor the overall status of the upgrade.

4.4.1 Phase A: Migrate from IBM Tivoli Monitoring V5.1.2 to IBM Tivoli

Monitoring V6.2 infrastructure

This phase is the first in the order to migrate the infrastructure. It is composed of

four steps that we will discuss in this section.

During this phase, the IBM Tivoli Monitoring V5.1.2 infrastructure is assessed

and a corresponding IBM Tivoli Monitoring V6.2 infrastructure is proposed for

review before its deployment.

Chapter 4. Upgrading from IBM Tivoli Monitoring V5.1.2 193

The infrastructure migration for the entire Tivoli Management Framework region

must complete before starting the migration of endpoints, profiles, and profile

managers.

The same apply in the case of multiple-region architecture, so called HUB and

SPOKE: in this case, you must complete the entire infrastructure migration for all

regions before migrating any endpoints, profiles, and profile managers.

The tool can be accessed both by the command line using the witmmtk command

and GUI. For the objective of this book, we will describe the command line

options and we will present some screen captures with the migration status.

Step 1: Migrate servers – assess

This step consist of the execution of the witmmtk tool with the scantmr parameter.

You can either use the GUI or CLI to perform this operation, and there is no

advantage in using one or the other method, as the GUI simply offers a

user-friendly interface for entering the command parameters and then runs the

command.

To use the command line, follow these steps:

1. Log on to the Tivoli server and source the Tivoli environment.

2. Enter the following command from any directory: witmmtk scantmr or witmmtk

scan.

The resulting baseline file is named <tmroid>.xml, where tmroid is the OID

(object ID) number that uniquely identifies the Tivoli Management Region.

Note: The Tivoli Management Region server is queried, looking for gateways

and endpoints based on the IBM Tivoli Monitoring V5.1.2 boot methods.

Some internal calls are executed to query the endpoint manager to look at the

endpoints’ boot methods, therefore only endpoints that do have a boot method

called DMAE_boot_engine are added to the baseline file for the infrastructure

and mapped to OS agents. For the gateways, the location attribute of the IBM

Tivoli Monitoring V5.1.2 installation object is queried to establish if it is

installed on the gateway: only those gateways are added into the baseline file

and mapped to a remote monitoring server.

194 Deployment Guide Series: IBM Tivoli Monitoring V6.2

Example 4-7 shows the output of the above command execution in our

environment.

Example 4-7 witmmtk scan command execution

The Framework environment we used was made of two gateways and eight

endpoints as shown in the below “wep ls” output:

C:\Tivoli\db\cairo.db\AMK\analyze\profilemanagers>wep ls

G 1713357986.1.590 cairo-gw

1713357986.14.522+#TMF_endpoint::endpoint# florence-ep

1713357986.4.522+#TMF_endpoint::endpoint# cairo-ep

1713357986.8.522+#TMF_endpoint::endpoint# rp3410-ep

G 1713357986.6.66 toronto-gw

1713357986.11.522+#TMF_endpoint::endpoint# paris-ep

1713357986.15.522+#TMF_endpoint::endpoint# rx2620-ep

1713357986.16.522+#TMF_endpoint::endpoint# server2-ep

1713357986.17.522+#TMF_endpoint::endpoint# edinburgh-ep

1713357986.7.522+#TMF_endpoint::endpoint# toronto-ep

Run the following command with any other parameter but “scan”.

C:\Tivoli\db\cairo.db\AMK\analyze\scans>witmmtk scan

AMKUT0016I Processing the request.

AMKUT2504I Creating a new infrastructure baseline file

"C:\Tivoli\db\cairo.db\AMK\analyze\scans\1713357986.xml".

AMKUT2515I IBM Tivoli Monitoring is installed on gateway "cairo-gw".

AMKUT2515I IBM Tivoli Monitoring is installed on gateway "toronto-gw".