Troubleshooting
Problem
Cannot add new Windows 2022 node to a SQL AlwaysOn cluster with existing nodes running Windows 2016
Symptom
Cluster log shows node does join the cluster but is evicted after a few minutes.
Cause
As addressed in Microsoft's "Cluster operating system rolling upgrade" does support adding nodes with a higher version of an operating system, it is in a concept of N1. This means the highest supported jump is 2016 to 2019.
Environment
Windows 2016 and 2022
Diagnosing The Problem
The sequence you will see if the new Node actually joins the cluster but is then evicted after a few minutes.
Example to look for in the cluster log:
A new node, XXXX-XXX, has been added to the failover cluster.
WARN Cluster node XXXX-XXX has been evicted from the failover cluster.
WARN Cluster node XXXX-XXX has been evicted from the failover cluster.
The reason why can be determined with these entries.
INFO [VER] Checking version compatibility for node XXXX-XXX id 1 with following versions: highest [Major 11 Minor 1 Upgrade 4 ClusterVersion 0x000B0004], lowest [Major 10 Minor 1 Upgrade 3 ClusterVersion 0x000A0003].
INFO [VER] Version check passed: accepting a node with a higher major or upgrade version 11.4 by default
WARN [VER] Closing connection due to reported version incompatibility, status 5075. My versions: highest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008], lowest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008]. Node XXXX-XXX (id 1) cluster versions: highest [Major 11 Minor 1 Upgrade 4 ClusterVersion 0x000B0004], lowest [Major 10 Minor 1 Upgrade 3 ClusterVersion 0x000A0003].
WARN mscs::ListenerWorker::operator (): (5075)' because of '[VER] Failed version compatibility check with node XXXX-XXX (id 1).
INFO [VER] Version check passed: accepting a node with a higher major or upgrade version 11.4 by default
WARN [VER] Closing connection due to reported version incompatibility, status 5075. My versions: highest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008], lowest [Major 9 Minor 1 Upgrade 8 ClusterVersion 0x00090008]. Node XXXX-XXX (id 1) cluster versions: highest [Major 11 Minor 1 Upgrade 4 ClusterVersion 0x000B0004], lowest [Major 10 Minor 1 Upgrade 3 ClusterVersion 0x000A0003].
WARN mscs::ListenerWorker::operator (): (5075)' because of '[VER] Failed version compatibility check with node XXXX-XXX (id 1).
Resolving The Problem
Bring the cluster nodes to server 2022 by adding with 2019 servers until the 2016 servers are then removed, then after the cluster functional level is raised, perform the same steps with Server 2022
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB66","label":"Technology Lifecycle Services"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SSTIPK","label":"Microsoft Windows"},"ARM Category":[{"code":"a8mKe000000004NIAQ","label":"Windows"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
More support for:
Microsoft Windows
Component:
Windows
Software version:
All Versions
Document number:
7169649
Modified date:
23 September 2024
UID
ibm17169649