TPAM running 2.5.917 and DPA running v3.3.12.
PSM Session is created and user can perform duties on the target system, but is unable to complete a File Transfer.
Test DPA completes but does not show complete output of all test functions:
vDPA not initialized correctly, not all services running as expected.
The following steps allow TPAM admin to reset the DPA and allow normal function again.
Login to /admin interface | Cluster Management
Select the problem DPA - Check "Appliance Active" - Change from "Active" to "Inactive"
Open your virtual server management tool, locate the vDPA - Using the management tools attempt a reboot, reset. Use the relevant option to force the virtual server to recycle and perform a reboot. This will take a few minutes to reboot and return to a login prompt.
Login to the vDPA console. You will notice that it has reverted to version 3.3.8. This is expected. DO NOT reboot the vDPA again. TPAM will update the DPA to 3.3.12 itself. This process can take between 20 - 30 minutes.
Move back to the Primary /admin | Cluster Management page, refresh the "Cluster Status" tab and wait for the version to show 3.3.12. It will take time be patient.
Once showing v3.3.12 perform a Test DPA to ensure the output is verbose and as expected, and DPA is now fully functional.