IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Upgrade from a previous installation > Scenario: a rolling product upgrade
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Upgrade the Tivoli Monitoring environment
Install a given level of IBM Tivoli Monitoring on the primary and secondary hub monitoring server, on the remote monitoring servers, and on the portal server. Install agents (simple agents, subnode agents, SYSPLEX agents), including the Warehouse Proxy Agent and the Summarization and Pruning Agent, at the same level of IBM Tivoli Monitoring.
Configure the Warehouse Proxy and Summarization and Pruning Agents to report directly into both hubs, configured as primary and secondary. You can optionally configure a second Warehouse Proxy Agent, to serve as a backup.
If you are upgrading from V6.1 or V6.2.x to V6.3, you must update both infrastructure components and OS agents in that $ITM_HOME installation at the same time.
Other agents report to at least one of the remote monitoring servers.
- Begin historical collection of agent attributes. Assume the historical collection is being done at the agents and not at the Tivoli Enterprise Monitoring Server; otherwise data collection may be interrupted when agents switch from the acting monitoring server to the backup.
- Cause situations to fire, for example, by varying thresholds.
- Ensure the acting (primary), and backup (secondary) monitoring servers are connected by examining their log/trace records and process state for these messages:
- KQM0001 "FPO started at ..."
- KQM0003 "FTO connected to ..."
- KQM0009 "FTO promoted primary as the acting HUB"
- KQM0009 "FTO promoted SITMON*secondary (Mirror) as the acting HUB"
- If you have integrated the IBM Tivoli Monitoring events with either Tivoli Enterprise Console or Netcool/OMNIbus:
- First upgrade your event synchronization.
- Then restart Tivoli Enterprise Console or OMNIbus, as appropriate.
- Finally, restart the monitoring server to which Tivoli Enterprise Console or OMNIbus is connected. This must be the acting monitoring server.
- Confirm that both the acting and backup hub monitoring servers are operational, so that during this upgrade process, when the acting hub is shut down, the backup will be able to assume the role of acting Tivoli Enterprise Monitoring Server.
- Upgrade the primary hub Tivoli Enterprise Monitoring Server and all other Tivoli Management Services infrastructure components in that $ITM_HOME installation (in other words, select ALL when asked what to upgrade).
- If working on a Windows platform, apply support to upgraded agents as part of this upgrade step.
- If working on a UNIX or Linux platform, apply support for the upgraded infrastructure agents on the primary hub monitoring server:
./itmcmd support -t primary_TEMS_name lz nt ux hd sy
All Tivoli Management Services processes running within the same IBM Tivoli Monitoring environment are temporarily shut down when upgrading a monitoring server.
- Upgrade the secondary hub Tivoli Enterprise Monitoring Server and all other Tivoli Management Services infrastructure components in that $ITM_HOME installation (in other words, select ALL when asked what to upgrade).
The acting (primary) and backup (secondary) monitoring servers should be installed at the same version level. The best choice is to have the monitoring servers at the same fix pack level as well.
- If working on a Windows platform, apply support to upgraded agents as part of this upgrade step.
- If working on a UNIX or Linux platform, apply support for the upgraded infrastructure agents on the secondary hub monitoring server:
./itmcmd support -t secondary_TEMS_name lz nt ux hd sy
- Restart both the primary (backup), and secondary (acting) Tivoli Enterprise Monitoring Servers.
- Upgrade the Tivoli Enterprise Portal Server.
- Confirm that all remote Tivoli Enterprise Monitoring Servers are operational, so that during this upgrade process, when the acting hub monitoring server is shut down, the backup will be able to assume the role of acting Tivoli Enterprise Monitoring Server.
- Upgrade each remote monitoring server, one at a time.
- If working on a Windows platform, apply support to upgraded agents when upgrading the monitoring server.
- If working on a UNIX or Linux platform, immediately after a remote monitoring server is upgraded, apply support for the upgraded infrastructure agents on the same node. Then restart the remote monitoring server to make the upgraded support effective.
- Upgrade the remaining infrastructure agents.
- At a time when no history records will be uploaded to it, upgrade the Warehouse Proxy Agent.
Parent topic:
Scenario: a rolling product upgrade