Prior to use, the virtual hard disk should be expanded to a minimum of 50 GB to ensure sufficient storage for session log recordings. When the virtual hard disk is expanded, the DPA will automatically detect the change and will configure and encrypt this resource. This will cause the appliance to reboot, and could take several minutes to over an hour to complete, depending on the size.
Depending on your use case, the disk space may need to be enlarged again in the future. This can be done by shutting down the virtual appliance, modifying the disk space allotment and then starting the appliance back up. As above, this change will be detected and the drive will be re-encrypted.
If you should require assistance in expanding the Virtual DPA hard disk, please consult the documentation for your virtualization product, or contact your virtualization vendor for more assistance.
If the DPA is being updated to a new version, this could take several minutes. In most cases this should be just a few minutes and as much as 60 minutes. Do not try to access the DPA or reboot the DPA during this time. Run the Test DPA after 60 minutes to verify the this is not successful.
The following steps allow TPAM admin to reset the DPA and allow normal function again.
1. Login to /admin interface | Cluster Management
2. Select the problem DPA - Check "Appliance Active" - Change from "Active" to "Inactive"
3. 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.
4. Login to the vDPA console. You will notice that it has reverted to a prior version. This is expected. DO NOT reboot the vDPA again. TPAM will update the DPA to the latest version. This process can take between 30 minutes to an hour.
5. Move back to the Primary /admin | Cluster Management page, refresh the "Cluster Status" tab and wait for the new version.. It will take time be patient.
6. Once showing the new DPA version perform a Test DPA to ensure the output is verbose and as expected, and DPA is now fully functional
Virtual DPAs do revert back to a prior release upon reboot. This is because the vDPA uses a RAM disk. There are a few necessary scripts and files on the disk of the "imaged" vDPA that are required for enrolling and recovering after a reboot, but the majority of the code is pushed to the vDPA by the TPAM console during initialization, and this code is stored on the RAM disk. Of course, the code on the RAM disk is cleared during a reboot. Upon recovery, the vDPA will get updated to the latest DPA release that the TPAM console appliance contains.
It can take up 10 to 12 minutes for a vDPA to be recovered since the console appliance only checks the state of DPAs every 10 minutes.
Verified via Putty that version had downgraded to v3.3.x after a power down of the vDPA.
Run a Test DPA from /tpam - Management - DPAs - Select vDPA - Test DPA - After a long time waiting this seemed to trigger an upgrade of the vDPA, and the Putty session was closed while the upgrade went through. At this point there should be a relatively long list of DPA test results if everything is functioning correctly.
If the list is shorter on a particular DPA, it usually means that it wasn't able to successfully complete that part of the procedure. There could be different reasons, but most commonly, this is due to a communication problem, such as a blocked port.