HP TMS zl Module Security Administrator's Guide

1-49
Managing TMS zl Modules
Configuring High Availability Clusters
■ When another cluster member begins to come online, it detects the
cluster Master and reboots, using the cluster Master's startup-config
as its own. When it comes online again, it is the cluster Participant.
■ The TMS VLAN settings that were configured on the cluster Partici-
pant before becoming a cluster member are permanently erased.
■ When the cluster Master fails, the cluster Participant becomes the
cluster Master without significant interruption.
■ When the former cluster Master comes back online, it uploads the
startup-config of the current cluster Master and becomes the cluster
Participant.
Be careful to configure and reboot cluster members in the appropriate order.
You must configure HA on the intended Master first and reboot it, so that it is
the first member of the cluster. If the intended Master is not configured and
rebooted first, the intended Participant will become the actual Master, and
you will lose the Master's configuration settings.
To do this, select the delay that NIM will use to wait for the Master module to
complete booting before initiating the boot of the Participant module. Note
that since the Master/Participant roles are determined by boot order -- the first
to boot becomes the Master, in order to assure that the module you have
selected to be Master acquires that role, NIM delays booting the Participant
module until the Master has completed booting. Typically, the Master module
should take less than five minutes to boot, so the default value for this setting
is five minutes. If you find that the Master is taking longer than that to boot,
then increase the value for this parameter appropriately.
Linking Inter-Chassis Clusters
An inter-chassis cluster consists of cluster members that are physically
located in different switch chassis. When connecting the two chassis, follow
these guidelines:
■ There should be at least one Layer 2 link, and preferably redundant
links, between the two switch chassis.
■ If you use redundant links, enable the switches’ Multiple Spanning-
Tree Protocol (MSTP) or Rapid Spanning-Tree Protocol (RSTP) func-
tionality to prevent a loop.
■ The switch ports that connect the host switches should be tagged
members of the HA VLAN.
■ All TMS VLANs must be configured on both host switches.