Unable to deploy Third Party Security Virtual Machine (SVM) on NSX-T Data Center

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• Third Party SVM fails to deploy.
• In the NSX-T Data Center log /var/log/syslog the following errors are seen: 

2021-09-06T06:41:48.109Z nsxsrv001 NSX 5725 FABRIC [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updating existing deployment Unit:DeploymentUnit
...
errors={26134=Error creating agency for deployment unit 39509698-b0fa-446e-8613-a34420179c44. Error occurred in compute manager plugin call. Error while creating agency: Invalid url specified http://example.company.com:8060/public/<path>/<version>.large.ovf. Delete this deployment and create another one.}]

• In NSX-T Data Center log /var/log/cm-inventory/cm-inventory.log similar errors can be seen:

... agentConfigs='[AgentConfigDto{ovfUrl='http://example.company.com:8060/public/<path>/<version>.large.ovf', hostVersion='7+'}, 
...

level="ERROR" subcomp="cm-inventory"] Error creating agency with deploymentConfig: AgencyConfigDto{agencyId='null', agencyName='_NSXT_efc68abd-fc60-43c3-bfc8-9631be80cb35_domain-c8',
...
com.vmware.nsx.management.cminv.exceptions.HostBasedVMException: Error while creating agency: Invalid url specified http://example.company.com:8060/public/<path>/<version>.large.ovf
...
2021-09-06T06:23:13.417Z ERROR http-nio-127.0.0.1-7443-exec-1 EamServiceImpl 4397 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP40428" level="ERROR" subcomp="cm-inventory"] Error connecting EAM on cm efc68abd-fc60-43c3-bfc8-9631be80cb35. Reconnecting.

2021-09-06T06:41:48.101Z ERROR http-nio-127.0.0.1-7443-exec-4 EamServiceImpl 4397 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP40427" level="ERROR" subcomp="cm-inventory"] Invalid url specified
2021-09-06T06:41:48.101Z ERROR http-nio-127.0.0.1-7443-exec-4 EamServiceImpl 4397 SYSTEM [nsx@6876 comp="nsx-manager" errorCode="MP40429" level="ERROR" subcomp="cm-inventory"] Error creating Agency in EAM for CM efc68abd-fc60-43c3-bfc8-9631be80cb35

• Note: in the above log entries, the path: http://example.company.com:8060/public/<path>/<version>.large.ovf <path> and <version> should reflect actual path and version used in production and relevant to the third party SVM.

Environment

VMware NSX-T Data Center 3.x
VMware NSX-T Data Center
VMware NSX-T Data Center 2.5.x

Cause

This issue occurs due to connectivity issues when downloading the OVF for the third party SVM, this is hosted in the environment based on third party SVM deployment requirements.
The connection may be failing due to blocked port, such as firewalled port.
You can use tools such as netcat to test connectivity from vCenter to location of OVF to be downloaded:

nc -zv <destination-ip-address> <destination-port>

For example:

nc -zv 10.10.10.1 8060

The following guide outlines ports required for NSX-T: https://ports.esp.vmware.com/home/NSX-T-Data-Center
Please review ports required for third party vendor also.

Resolution

Open any ports required to deploy the SVM.