Safe Mode

A node enters safe mode when there are unrecoverable errors. Any node in a cluster can enter this mode.

Examples of unrecoverable errors are when there are inconsistencies between the system and the running configuration or when the cluster configuration did not merge properly with the existing configuration. A node will automatically enter safe mode.

As part of merge error recovery, nodes joining a cluster are automatically restarted so the merge error can be fixed.

When a node is in safe mode:

■

The node displays a banner indicating it is in safe mode.

■

An SNMP trap is sent to notify the user when the mode changes

■

Traffic provisioning is not allowed on the affected node. Any other configuration remains as is.

■

Configured traffic continues to be forwarded.

■

If the standby node in the cluster is in safe mode, it can still become the leader if the current leader fails or switches over, but the database on the standby node may not be in sync, so it is not recommended to continue in that state. Instead, take immediate action to recover the node.

■

In safe mode, the node does not process any incoming traffic configuration from the cluster leader.

When a node is in safe mode and you try do any operations that are not allowed in safe mode, the UI displays the following message:

The system has restricted provisioning in safe mode. Contact Gigamon Support on how to troubleshoot and recover from safe mode.

Also, hovering over the status bubble of the nodes on the Physical Nodes page in GigaVUE‑FM displays a message that the node is in Safe Mode.

To exit safe mode, reload the node.