Deployment Guide Series: IBM Tivoli Monitoring V6.2

216 Deployment Guide Series: IBM Tivoli Monitoring V6.2

The upper right corner shows the overall Upgrade level (in this case, 71%).

Scrolling down the page and expanding the Remote server entries, you can see

the OS Agents deployment status, as shown in Figure 4-13.

Figure 4-13 OS Agent deployment status

4.4.2 Determining a migration strategy for endpoints, profiles, and

profile managers

To migrate the endpoints, profiles, and profile managers in a Tivoli Management

Region, it is best to divide the work into manageable stages.

Migrate a portion of the Tivoli Management Region at a time: a set of endpoints,

the profiles distributed to those endpoints, and the profile managers that contain

the profiles. By migrating a Tivoli Management Region in increments of

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

reasonable size, you shorten the time it takes to reach the point where you can

view and test monitoring data in the new environment.

The migration workflow

Each of the phases in the migration of the endpoints, profiles, and profile

managers is an iterative process that follows this workflow:

1. Assess: For a set of V5.1.2 resources, request upgrade status and migration

settings.

2. Analyze: For a set of V5.1.2 resources that have not yet been migrated,

inspect the proposed migration settings.

3. Migrate: Migrate a set of non-migrated V5.1.2 resources to V6.x.

4. Review results and check status: Review the outcome of the object migration

and monitor the overall status of the upgrade.

Figure 4-14 shows the iterative nature of the process.

Figure 4-14 The migration workflow

The following sections describe the upgrade workflow in more detail.

218 Deployment Guide Series: IBM Tivoli Monitoring V6.2

Assess

The Assess tool assesses endpoints, profiles, and profile managers. The

assessment tools gather data about V5.1.2 resources and produce XML assess

files that contain the following information:

򐂰 A mapping of V5.1.2 resources to proposed equivalent V6.x resources. For

example, in an assessment of profiles, the output file maps each resource

model (the source) to proposed equivalent situations (the target).

򐂰 The upgrade status of the V5.1.2 resources that were included in the

assessment, indicating which resources have been upgraded and which have

not.

Analyze

In this step, you analyze the output data, and check that it provides the result you

want. The corresponding step for the infrastructure allowed you to reshape the

infrastructure from the proposed version. In this case, however, we do not

recommend modifying the results of the assessment, unless you are forced to

because the tool found a problem. If you want your monitoring results to be the

same in V6.x as in V5.1.2, you must leave the results as they are.

The migration toolkit provides various methods of viewing the XML files.

Migrate

The migration step implements the specifications from the assessment. The tool

deploys V6.x resources based on the specifications in the output file from the

Assess tool.

Check status

When the migration is complete, check the logs for errors and also, in the case of

endpoint migration, recalculate the infrastructure completion percentage.

Note: The assessment is made of the resource models on the server, not

those actually in use on the endpoint.