Views:

Trend Micro has identified the root cause of this issue and it was related to a new feature change that affected all existing Guest VM's local database and Certificate files. The correct filename for the Guest VMs should be ds_guest_agent.xxx but the file name was changed to ds_agent.xxx

Incorrect file name

Workaround

You will need to rollback the DSVA version by following the steps below:

  1. Remove DSVA from NSX-T Service deployment.
  2. (optional) Manually download previous RHEL7 DSA build from Download Center (e.g. DS 20.0.0.7719)
  3. (optional) Import the RHEL7 DSA package (e.g. DS 20.0.0.7719) to DSM > Administration > Updates > Software > Local.
  4. Configure the DSVA appliance upgrade to specific build (e.g. DS 20.0.0.7719). From DSM > Administration > System Settings > Updates tab > Virtual Appliance Deployment from default "Latest Available (Recommended)" to specific build.

    Deploy Specific DSVA Build

  5. Deploy DSVA appliance from NSX-T manager console.
  6. Check the DSVA appliance build info. Upon deploys successfully the appliance will upgrade to the specific build automatically.
 
It is strongly recommended that customers refrain from upgrading DSVA to version 20.0.0.7943 (20 LTS Update 2023-09-26) or DS 20 LTS Oct Release.
 

Long-term Solution

The developer team is working on the solution and the ETA will be DS 20 LTS Release in November 2023.

Keywords: DSVA 20.0.0.7943,Guest VM Protection,Offline Status Troubleshooting,Check Status Failed,Activation Required Issue