Chapter 10. IBM Tivoli Monitoring resiliency and high availability 347
Figure 10-6 Configuration after failover
The system can continue to operate with this configuration until there is a need to
shut down the acting hub, or if the machine on which it is running becomes
unavailable. Each time the acting hub becomes unavailable, the scenario
described in this section is repeated.
10.2.3 Tips and best practices for using Hot Standby
Some tips and best practices for using Hot Standby are presented in this section.
Configuration
1. Identify the primary and secondary hub monitoring servers to implement Hot
Standby. The Tivoli Monitoring software on both machines is required to be at
the same release and maintenance level. Application support for all the
required applications should be installed at both hub monitoring servers. Hot
Standby is not supported at present for hub monitoring server on the z/OS
platform.
2. Ensure that the primary and secondary hub monitoring servers refer to each
other as the standby hub in their configuration. On the Windows platform, for
348 IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments
example, the configuration would look like this for the primary hub monitoring
server (Figure 10-7, Figure 10-8 on page 348 and Figure 10-9 on page 349).
Figure 10-7 Primary hub monitoring server configuration - 1
Figure 10-8 Secondary hub monitoring server configuration - 2
Chapter 10. IBM Tivoli Monitoring resiliency and high availability 349
Figure 10-9 Primary hub monitoring server configuration - 3
The configuration for the secondary hub monitoring server should look like this
(Figure 10-10 on page 349, Figure 10-11 on page 350 and Figure 10-12 on
page 350).
Figure 10-10 Secondary hub monitoring server configuration - 1
350 IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments
Figure 10-11 Secondary hub monitoring server configuration - 2
Figure 10-12 Secondary hub monitoring server configuration - 3
Further, review the operations log for each hub monitoring server after it is
started to ensure that FTO messages are emitted.
3. Ensure that all remote monitoring servers are configured correctly and
consistently, with the primary hub monitoring server as the monitoring server
they connect to, and the secondary hub monitoring server as the standby hub
(Figure 10-13, Figure 10-14 on page 351 and Figure 10-15 on page 352).
Chapter 10. IBM Tivoli Monitoring resiliency and high availability 351
.
Figure 10-13 Remote monitoring server configuration – 1
Figure 10-14 Remote monitoring server configuration - 2

Get IBM Tivoli Monitoring: Implementation and Performance Optimization for Large Scale Environments now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.