IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Installation Guides > Installation Guide > Pre-deployment phase > Sizing the Tivoli Monitoring hardware
IBM Tivoli Monitoring, Version 6.3 Fix Pack 2
Locating and sizing the hub Tivoli Enterprise Monitoring Server
Always locate the hub monitoring server in a data center with good network reliability and throughput. Network connection speeds of 100 Megabits per second or higher are typically sufficient.
Except where noted, the server sizings assume that the hub monitoring server is installed on a separate server with no additional Tivoli components. Below are some basic guidelines. For detailed guidelines, see Hardware and software requirements.
Sizing your hub monitoring server hardware
- Large and medium-sized environments (>1500 agents)
- Remote Tivoli Enterprise Monitoring Servers should be used in this environment. The Hub Tivoli Enterprise Monitoring Servers should have at least 2 processors and 3 GB of RAM.
Although the steady-state CPU utilization is usually low, the hub monitoring server uses a significant amount of system resources in processing transient workloads, such as startup, agent login, and situation distribution. It is reasonable to run other Tivoli Monitoring components on the same server such as the portal server, but allocate additional CPUs for the additional components. See Memory and disk requirements.
- Small environments (< 1000 agents)
- Remote Tivoli Enterprise Monitoring Servers are not typically required in this environment. The system should have at least 2 processors and 4 GB of RAM. It is reasonable to combine components such as the monitoring server and portal server on a dual-processor server. When combining monitoring components on a single server, the different components' process memory requirements should be added together. See Memory and disk requirements for more information.
For environments with 200 or fewer agents, most of the components can be combined onto a single server. If you are going to use a small monitoring environment, choose a multiprocessor (2 or 4-way) for the monitoring server with at least 4 GB of total system memory. Configure the software and begin monitoring CPU and memory usage during periods of both normal and high volumes of situation events. If CPU or memory usage is constrained, consider deploying a separate server for the Tivoli Data Warehouse, the Warehouse Proxy Agent, and the Summarization and Pruning Agent. For more information see Memory and disk requirements.
When to use multiple hub monitoring servers
As environments grow in size, you must run multiple hub monitoring servers. The recommended limit of managed systems per hub monitoring server is 20,000.
There are many factors that affect the scalability of a hub environment. The primary factors are network latency, number of situations running at the hub, the number of concurrent active users, and historical data collection.
When multiple hub monitoring servers are used, correlation of events can be performed by using either Tivoli Enterprise Console or Netcool/OMNIbus.
Parent topic:
Sizing the Tivoli Monitoring hardware