Share via

Cluster Validation error - Update level warning

iutecg 1 Reputation point
2020-10-12T16:21:59.353+00:00

Hello
I have 2 server which will node for cluster (vrtx M640) . I performed cluster validation and all the time I received warnings that servers not running the same updates. It is strange because according to update history they have installed same software. Another thing is that one KB - 4462930 is missing on one of the server ( on other server was installed ). I tried download it and install manually but I reveiced message that this is not applicable on this computer. I checked and it seeams that on one server first was installed KB4462930 and than newest Adobe updates -KB4561600 and on this node all is ok, on second node first was installed KB4561600 (success) and then attempt to install KB4462930 (failure). I suspect that in this case newest KB contains 4561600 thats why I failed to install it (but I am not sure).
Anyway please help with this strange behavior during cluster validation, I need make cluster without any warning:)

Below I attached screnshot from server1, server2, cluster validation report:

31752-ser1-updates.jpg
31680-ser2-updates.jpg
31753-validate-rep.jpg

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,635 questions
Windows Server Clustering
Windows Server Clustering
Windows Server: A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.Clustering: The grouping of multiple servers in a way that allows them to appear to be a single unit to client computers on a network. Clustering is a means of increasing network capacity, providing live backup in case one of the servers fails, and improving data security.
979 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. TimCerling(ret) 1,156 Reputation points
    2020-10-13T13:26:42.95+00:00

    Update mismatch warnings can happen if the nodes of the cluster were updated on different cycles. This can happen when one node gets updated with a particular patch but the other node was updated later and it applied a patch that superseded a patch that was applied to the other system. The warning is simply that - a warning. You can generally investigate the patches to find this.

    The best way to avoid this is to perform a clean installation and full patch of each node before creating a cluster.