Deployment Guide Series: IBM Tivoli Monitoring V6.2

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

4.4 IBM Tivoli Monitoring Migration Toolkit

The upgrade tools and procedures are designed to transfer control to the new

IBM Tivoli Monitoring V6.2 infrastructure while preserving the monitoring activity

and monitored resources that are already in place; this way, there will not be a

service disruption.

Let us briefly describe the main phases of the migration toolkit that will be then

explained in the sections that follow:

򐂰 To enable IBM Tivoli Monitoring V6.2 to take over from IBM Tivoli Monitoring

V5.1.2, the first requirement is to install a sufficient number of IBM Tivoli

Monitoring V6.2 servers (hub and remote Tivoli Enterprise Monitoring Servers

and Tivoli Enterprise Portal Servers) to handle the current monitoring

requirements.

򐂰 The existing Tivoli endpoint systems, which host the monitored resources,

can then be connected to the Tivoli Enterprise Monitoring Servers. Endpoints

are connected to monitoring servers by deploying OS monitoring agents to

the endpoints. The final result is that the endpoints become part of the IBM

Tivoli Monitoring V6.2 environment. At the same time, however, they remain

connected to the IBM Tivoli Monitoring V5.1.2 environment so that monitoring

can continue until the old resource models are no longer needed.

򐂰 The next step is to replace the resource models in IBM Tivoli Monitoring

V5.1.2 profiles with IBM Tivoli Monitoring V6.2 situations. Situations are

associated with the appropriate monitoring agents and with lists of managed

systems to be monitored. The managed system lists are created from the

subscriber lists of profile managers.

Figure 4-11 shows the diagram of the phases and steps for the migration.

Figure 4-11 Grid showing the migration phases and steps