Hi Md Rashid,
Adding a node with a third-generation Intel Xeon processor to a cluster of fourth-generation processors is a fully supported architecture. The primary configuration requirement is that your cluster must be operating at Cluster Functional Level 11, which is the native operational mode for Windows Server 2022. Additionally, your BIOS and firmware microcode must be identically patched across all nodes to ensure uniform CPU vulnerability mitigations.
The newer processors possess advanced instruction sets absent in the older processor, so you are required to enable Processor Compatibility Mode to facilitate Live Migration. Without this, Hyper-V will block migrations from the newer nodes to the older node to prevent guest operating system crashes. To apply this, you must shut down the virtual machines and execute the PowerShell cmdlet Set-VMProcessor followed by your virtual machine name and the parameter -CompatibilityForMigrationEnabled set to true. This dynamically masks the advanced processor features, presenting a uniform baseline to the guest operating systems.
Before joining the node, execute the Test-Cluster PowerShell cmdlet, specifying only your current and target nodes, and intentionally exclude the storage parameter to prevent your active Cluster Shared Volumes from dropping offline. After using Add-ClusterNode to introduce the host to the environment, you should verify its health by reviewing the Microsoft-Windows-FailoverClustering/Operational log in the Event Viewer. You should look specifically for Live Migration success events after manually testing virtual machine movement to and from the newly introduced legacy hardware.
Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.
VPHAN