I believe the issue is because of that second network on the prime client that I mentioned:
20230710-17:32:17 Info Info: FS Copy Staf.cfg File : Standby0 Returned: RC = 0, STAFResult = Trust level 4 required for the FS service's COPY request Requester has trust level 3 on machineStandby0.hmcdc.local Requesting machine: ssl://172.21.169.225 (ssl://172.21.169.225) Requesting user : none://anonymous
Your prime client has both 172.21.166.225 and 172.21.169.225 IP addresses but Standby's Staf.cfg doesn't have an appropriate trust machine line for 172.21.169.225. As you can see above, the requestor is listed as 172.21.169.225 so that would seem to be the issue. You either need to have the workload VMs trust 172.21.169.225 or you need to have the prime client communicate to the workload VMs via 172.21.166.225 since that IP is trusted.
-Joshua
