From the configuration check the vmbus-uuid used by MGMT port.
example: config authority router NODE node NODE1 device-interface MGMT vmbus-uuid 000d3a2e-61b8-000d-3a2e-61b8000d3a2e
Check the dmesg logs and see if you find similar error.
/usr/bin/dmesg [Thu Jul 11 14:39:24 2024 < 0.004406>] hv_vmbus: probe failed for device 000d3a2e-61b8-000d-3a2e-61b8000d3a2e (-12) [Thu Jul 11 14:39:24 2024 < 0.004787>] uio_hv_generic: probe of 000d3a2e-61b8-000d-3a2e-61b8000d3a2e failed with error -12
The (12) error code corresponds to ENOMEM, which means "Out of memory" in a a Microsoft Hyper-V hypervisor.
The error suggests that, there is a lack of memory resources.
To fix the problem, check if enough memory resources are allocated.
Ensure that enough memory is dedicated and its not shared..
If you still face the issue after allocating enough memory, you may need to restart the 128T serice or reboot the node during non production hours, this step may be required for proper memory allocation.