IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase > Estimate deployment tasks
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Scheduling for fix packs
In a typical user environment, allocate one day to upgrade the Tivoli Monitoring infrastructure components (hub monitoring server, portal server, Warehouse Proxy Agent, Summarization and Pruning Agent). In a multi-hub environment, allow one day for each hub. Then, time must be allocated to upgrade the agents.
Typically, the schedule is driven largely by Change Control windows and not by the time it takes to deploy the fix pack to the agents. However, for planning purposes use the following time estimates.
These times assume that there is adequate network bandwidth between the remote monitoring server deployment depot and the agents. In environments with slow network links between the remote monitoring server and the agents, evaluate the size of the fix pack files to calculate the rate of transfer. Because each fix pack is a different size and each network has unique characteristics, calculate this for your environment before starting the upgrade.
Performing agent upgrades in parallel can be done with the itmpatchagents tool. For environments with adequate network bandwidth and two people performing upgrades in parallel, plan to upgrade approximately 500 agents per day.
Finally, following the installation of a fix pack, plan time to test your environment. For Tivoli Monitoring infrastructure fix packs, spend two person days thoroughly testing your environment. For application agents, there is little risk that the Tivoli Monitoring infrastructure components were affected by the fix pack. Therefore, no more than one person day need be allocated to test the environment following the installation of an application fix pack.
Parent topic:
Estimate deployment tasks