Cluster updates reference | RS
This page describes the columns, status values, and notifications in the Cluster Updates section of the Updates page. For an overview of the section and how to use it, see Manage cluster updates.
Cluster table columns
The Cluster table appears only on the primary node. It has one row for each node.
| Column | Description |
|---|---|
| Node | The name of the node, and the address used to reach it if that address is different. |
| Role | Primary, Traffic, or Failover backup (the backup primary node). |
| Coordination | Whether the node takes part in cluster updates. For values, see Coordination values. |
| Product | The application and version that the node runs. A marker shows when the node is ahead of or behind the primary node. |
| Base Software | The Base Software version that the node runs, with the same markers as Product. |
| Patches | The number of patches installed on the node, with a link to the Installed Patches page. Patch counts often differ between nodes because each node installs patches on its own schedule. This is expected. |
| Last Contact | When the node last responded to the primary node, or Never. The primary node’s own row shows this node. |
Coordination values
| Value | Description |
|---|---|
| Coordinating | The node is the primary node and coordinates updates for the cluster. |
| Participating | The node installs updates together with the other nodes. |
| Not participating | The node manages its own updates. The primary node skips it. |
| Needs upgrade to participate | The node runs a version that is too old to take part in cluster updates. This value describes the software on the node, not the status of an update. |
Current panel status
The Status line of the Current panel shows the first of the following values that applies. The counts include only participating nodes.
| Status | Shown when |
|---|---|
| Installed on every node | Every participating node installed the update. |
| Failed on X of Y nodes | Every node finished, and X of them did not install the update. |
| Installing, finished on X of Y nodes | A node is installing the update or restarting to finish it. |
| Installed on X of Y nodes | X nodes have the update, and at least one other node is not ready. |
| Ready on X of Y nodes | Any other case. X nodes are waiting for the install time or are already up to date. |
The Previous panel uses the same values, plus Not confirmed on X of Y nodes when some nodes never confirmed the outcome.
Status values
A node that is not ready is listed under the Current panel with its status. A node's status is one of the following.
| Status | Description |
|---|---|
| Not yet contacted | The primary node has never successfully contacted this node. |
| Not reported | The primary node has contacted the node, but the node has not yet reported a status for this update. |
| Not acknowledged | The node has reported a status, but for an earlier plan. This is normal for a few minutes after a settings change replaces the coordinated update. |
| Ready to install | The node has determined what to install and is waiting for the scheduled time. |
| Installs at the maintenance window | Same as Ready to install, shown when the install is scheduled for a specific time. |
| Preparing, Installing, Restarting | The update is in progress on the node. |
| Up to date | The node runs everything the coordinated update requires. |
| Failed | The node could not install the update. The reason appears below the status. |
| None pending | There is no coordinated update for the node to act on. |
Status colors
Not reported and Not acknowledged appear in neutral text for the first 30 minutes after a coordinated update is published. After 30 minutes, they appear in the attention color.
Not yet contacted does not change color. To identify a node that the primary node has never reached, check whether Last Contact shows Never, or watch for the A Node Has Not Answered This Appliance notification.
Status messages on a participating node
When no update is pending, a participating node displays its status in a sentence that names the primary node in parentheses. When an update is pending, the node displays a Current panel with its status instead.
| Message | Meaning |
|---|---|
| This node has installed the last update from the primary node. | A coordinated update exists, and this node meets it. The node either installed the update or already had that build. Same as Up to date. |
| This node has no update pending from the primary node. | There is no coordinated update for this node. Same as None pending. |
| This node has not installed it. It installs on its own. | The scheduled install time has passed and this node has not installed the update yet. The node installs it without waiting for the primary node to schedule it again. |
Notifications
Only the primary node sends cluster update notifications. A cluster produces one notification for each event, not one for each node.
| Event | Email subject | Banner on the appliance |
|---|---|---|
| A coordinated update finished on every participating node. | Cluster Update: Installed | No |
| A node did not install the update. | Cluster Update: Failed | No |
| A node did not confirm whether it installed the update. | Cluster Update: Unconfirmed | No |
| A node cannot install the update that the other nodes are about to install. | Cluster Update: Cannot Install Everywhere | Yes |
| A node has fallen behind the other nodes for four hours. | A Node Is Behind The Other Nodes | Yes |
| A node has not responded to the primary node for four hours. | A Node Has Not Answered This Appliance | Yes |
| A scheduled update was withdrawn because the primary role moved to another appliance, or the cluster or failover pair was removed. | Cluster Update: Withdrawn | No |
The outcome of the first three notifications also appears in the Previous panel of the Cluster Updates section on the primary node.
The first three notifications are sent by email only. If you do not receive them, confirm the administrator email address configured on the primary node.
Updated outcome notifications
If a later check finds that the outcome of an update differs from what was reported, the primary node sends a second notification with Now in the subject line, such as Cluster Update: Now Installed.
Client connection warning
If a node is left on a different product build from the other nodes, the last three notifications include a warning that the node might stop accepting new client connections until it is updated. The same warning appears on the Updates page next to the outcome of the update.
This warning applies only to differences in the product build. It does not appear for differences in patches or Base Software, or in the Cluster Update: Installed, Failed, or Unconfirmed notifications.
Updated 1 day ago
