“vmservice-trend-pg could not be found” appears when deploying Deep Security Virtual Appliance (DSVA)

The issue is caused by any of the following:

• The vmservice-trend-pg switch or port group is not present. The vmservice-trend-pg switch is created during ESXi preparation. If the Deep Security Filter Driver was manually installed, this switch should have been created automatically.
• The vCenter account in use does not have sufficient permission to deploy a new DSVA.

To resolve the issue:

1. Verify if the vmservice-trend-pg switch / port group is present in the ESX networking properties:
   1. On the vCenter, select Hosts and Clusters view.
   2. Click the ESX, and then go to the Configuration tab.
   3. On the left pane, click Networking.

      The example below shows that the vmservice-trend-pg switch was not created.

      

      If the vmservice-trend-pg switch was created, proceed to Step 3.
      If the vmservice-trend-pg switch was not created, proceed to Step 2.

2. Create the vmservice-trend-pg port group under the vmservice-vswitch standard switch:
   1. On the vmservice-vswitch, click Properties.

      

       
   2. Click Add.

      

   3. Under Connection Types, select Virtual Machines and then click Next.
   4. Under Port Group Properties, click Network Label and then type “vmservice-trend-pg”.
   5. Click Next.
   6. Review the settings and click Finish.

   7. Check the networking properties of the ESXi to verify the newly-created switch. 

      

3. Ensure that the vCenter account set in the Deep Security Manager (DSM) properties has sufficient permission, preferably in the top-level hierarchy on the Vcenter. The default administrator role can be used. To do this:
   1. On the DSM console, right-click vCenter and then click Properties.

   2. Take note of the vCenter account used. 

      

   3. On the vCenter, highlight the top-level domain, data center, or cluster where the ESXi belongs.

   4. Go to the Permissions tab. The account specified in the DSM should be listed here, or is a member of a group that has an administrator role.

      

   5. If the account does not have full access or administrator role, specify an account that has an administrator role in the cluster, data center, or top-level domain where the ESXi belongs.