
Configuring the Cluster Configuration and Control Feature
How the Protocol Works 13-3
How the Protocol Works
Cluster Configuration and Control uses Distributed Shared
Memory. The memory exchange is done via TCP/IP protocol
(fully routable via LAN/WAN routers and switches). The data
exchange is encrypted via the TLS protocol using 128-bit AES
encryption and SHA hashing. Because all cluster shared memory
exchange is administrator driven, and the protocol does not
perform background exchange unless prompted by the
administrator, the protocol works efficiently with low network
overhead. The protocol uses TCP port 8100.
Table 13.1 describes some of the common cluster operation
terms.
Table 13.1 Cluster Configuration and Control Terms
Term Definition
Master Any unit in the cluster from which changes are
being made. Any unit in the cluster can be the
master, but it is a good practice to always use the
same unit as the master to avoid confusion. Any
configuration changes are always pushed to the
cluster from the master.
Slave Any and all units in the cluster that are not the
master. This means that once you have chosen
your master unit, all other units in the cluster
should be considered slaves. All configuration
changes to the slaves will be pushed to them via
the master unit.
Cluster Save Config The command issued to the master unit to push
the configuration to the cluster.
Save Config Flash The command issued to any unit to save its own
configuration locally.
Comentarios a estos manuales