Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Chapter 16: One-To-Many Clusters
Understanding the One-To-Many tree structure
Understanding
the One-To-Many
tree structure
484
Figure 202: Example of
an individually configured
area
When the Sidewinder G2 is successfully removed from the One-To-Many
cluster, it will reboot automatically. When the Sidewinder G2 reboots, it will
be a standalone Sidewinder G2.
The Admin Console tree structure is slightly different in a One-To-Many cluster
environment. When you configure One-To-Many, all Sidewinder G2s are
managed within a single Admin Console connection to the primary. All
secondary icons are removed from the tree.
Areas within the primary connection that are synchronized (that is, areas in
which the information for all Sidewinder G2s must be the same) will appear as
a single tree option within the primary. When you modify information within
those areas, it will automatically be applied to all Sidewinder G2s that are part
of the One-To-Many cluster.
Information specific to individual Sidewinder G2s within the One-To-Many
cluster that cannot be synchronized between Sidewinder G2s (such as
Configuration Backup and Audit) will include a sub-folder within the primary
that provides an icon for each Sidewinder G2 in the One-To-Many cluster. To
modify these features, select the individual Sidewinder G2 icon and make the
changes. These changes will apply only to the Sidewinder G2 that you have
selected and will not be overwritten by the primary.
Important: DNS is the only exception to this structure. To configure DNS settings
on a secondary, you will need to add the secondary server icon and connect
directly to that Sidewinder G2. All other features should be configured using the
primary connection to avoid being overwritten. (For information on adding a
Sidewinder G2 server icon, see “Adding a Sidewinder G2 to the Admin Console” on
page 20.)
Figure 202 below demonstrates the difference between individually configured
areas of the One-To-Many cluster (Configuration Backup and Date and Time)
and a synchronized area of the One-To-Many cluster (Burb Configuration).
Burb Configuration is synchronized
(changes made are sent to all
Sidewinder G2s within the One-To-
Many cluster, and you cannot select
a Sidewinder G2.
Configuration Backup and Date and
Time are configured on an individual
Sidewinder G2 basis.
To modify individually configured information for a particular Sidewinder G2,
simply select that icon for the Sidewinder G2 and make the desired changes.
Changes to an individual Sidewinder G2 will be applied only to that Sidewinder
G2 and will not be overwritten by changes made to the other Sidewinder G2.