HP TMS zl Module Security Administrator's Guide

1-50
Managing TMS zl Modules
Configuring High Availability Clusters
■ It is highly recommended that other network devices not be placed
between the switch chassis that contain the cluster members to
reduce the risk of link failure.
Updating Cluster Software
When updating software on an HA cluster, keep the following in mind:
■ You cannot update the software on cluster Participants by synchro-
nizing them with an updated Master because both of the modules in
a cluster must be running the same software version when the cluster
is formed.
■ The Synchronize Now command copies the startup configuration from
the Master to the Participant; it does not copy the new software image
to the Participant. Instead, you must update each module separately.
■ You can download and install the new software image at one time and
then later reboot the module to complete the installation.
When updating the software, complete the following steps:
1. Back up the Master's startup configuration.
2. Remove the Participant from the cluster (using the no high-availability
command with the delete-cluster-data option).
3. Update the Master's software.
4. Update the Participant's software.
5. Rejoin the Participant to the cluster.
Note Please refer to HP Threat Management Services zl Module Management and
Configuration Guide for CLI and WebUI syntax and options.
Operating Notes on NIM Behavior with HA Configuration
Because of the HA-specific conditions in a cluster environment, such as the
absence of an assigned IP address on a Participant TMS zl module, there are
certain operations to make the management of TMS zl modules with NIM as
easy as possible. The resulting behaviors from management operations per-
formed with NIM when managing HA clusters are described below.
■ Since the Participant member within an HA cluster has no IP address
assigned to it and is managed via the Master TMS zl module, an
imported cluster Participant will show up as “unreachable” within the