Cluster-Wide and Local Commands

When working with a cluster, most configuration settings made on one node are synchronized to all other nodes in the cluster, resulting in a seamless, unified Visibility Platform. On the other hand, some settings are kept locally and only apply to the local node. The following table summarizes the commands that only apply to a local node and those that are pushed to all nodes in the cluster.

Note: A good rule of thumb is that if a command takes a box ID as part of its arguments, it can be configured for an individual node from the cluster’s leader/VIP address. If a command does not take a box ID as part of its arguments, the corresponding setting must be configured from the individual clustered nodes.

Global Cluster Commands
The following commands are synchronized with all nodes in the cluster, regardless of whether they are made from the VIP or an individual node in the cluster.
map
map-passall
port-pair
tool-mirror
gigastream
hosts
time (clock)
snmp hosts and notifications You configure SNMP hosts and notification events from the leader. The settings are pushed to each node. However, when a clustered node sends an SNMP notification, it is sent from its own Mgmt port, not from the leader/VIP address. In addition, you browse each individual clustered node’s MIB separately, not over the VIP/leader.
cli session auto-logout
ssh server enable/disable
web
ssh host-key Note: The leader node automatically pushes its SSH hostkeys to all other nodes in the cluster, ensuring that they are the same on all nodes. If you connected through SSH to perform the initial configuration of a normal node, it will have different keys after this synchronization, likely resulting in a warning from your SSH client when you log back into that individual node later on. This is normal behavior.
syslog settings Similar to SNMP notifications, syslog messages are sent from each individual reporting node’s Mgmt port and not from the leader/VIP address.
aaa settings (RADIUS, TACACS+, and LDAP, including AAA)
ntp settings Note: The configuration is updated from the leader.

Local Commands
The following commands must be made on a local node – they are not synchronized from the leader.
hostname
ip settings for Mgmt port Note: Although you configure a clustered node’s IP settings for the Mgmt port over its local console port, the settings once made are stored in the global configuration database along with node’s box ID.
ptp settings