Configure Member Standby: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
[[ | [[Category:Admin guide]] | ||
=== Standby Mode === | === Standby Mode === | ||
Unlike [[Enter Site Cluster Maintenance Mode|Maintenance Mode]], Standby Mode is configured per node, meaning other Active nodes in the cluster will continue to operate normally and can still fail over resources to each other. | Unlike [[Enter Site Cluster Maintenance Mode|Maintenance Mode]], Standby Mode is configured per node, meaning other Active nodes in the cluster will continue to operate normally and can still fail over resources to each other. | ||
Latest revision as of 05:12, 20 October 2025
Standby Mode
Unlike Maintenance Mode, Standby Mode is configured per node, meaning other Active nodes in the cluster will continue to operate normally and can still fail over resources to each other.
When a node with active resources (e.g., pools or VIFs) is placed into Standby Mode, those resources will automatically fail over to a healthy node in the cluster.
A node in Standby Mode will not receive any resources (e.g., pools or VIFs) during a failover event from an Active node.
Types of Standby Mode
- Active: The node is in a healthy, operational state.
- Standby Auto Activation: The node is set to Standby and will automatically switch back to 'Active' once it becomes healthy or after a reboot.
- Standby Manual Activation: The node is set to Standby and will remain in this state until it is manually changed back to Active, regardless of its health status or whether it has been rebooted.
Navigation: High-availability VIF Management --> Site Clusters --> Configure Member Standby... (right-click site cluster)