Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Service Deployment fails in NSX-T Data Center 2.5.0 (76707)

Last Updated: 2/26/2024Categories: TroubleshootingTotal Views: 11733Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Service Deployment for Endpoint Protection and Network Introspection fails.

You see these errors similar to:

OVF parsing failed. Error: javax.net.ssl.SSLHandshakeException:

or

Unable to find certificate chain

or

Socket Exception

or

Connection Timeout

or

Error creating agency for deployment unit <UUID>. OVF certification validation failed. Error: Ovf, manifest and certificate files not found. Delete this deployment and create another one.

Cause

This issue occurs due to a connectivity issues when downloading the OVF for certificate validation. The connection might fail due to:

The endpoint is HTTPS.

The port being used is anything other than Port 80.

Resolution

This issue is resolved in VMware NSX-T Data Center 2.5.1, available at VMware Downloads.

Note:  In NSXT 3.x onwards these steps are not required.

For NSX-T 2.5.0/1 the follow steps should be followed:

In case the OVF is hosted on a port other than Port 80, open the respective port on each NSX Manager in the cluster.

For example, if the OVF is hosted on port 1000, then this port should be opened on each of the NSX-T Managers in the cluster using the root account. After upgrading to VMware NSX-T Data Center 2.5.1:

Log in to the NSX Manager CLI as administrator.

Run this command "st e" to switch to root user.

Run this command "iptables -A OUTPUT -p tcp --dport 1000 -j ACCEPT"

Note: The iptables rule that were manually added will not be available after the NSX Manager appliance is rebooted. Before doing any further fresh deployment, the respective custom port opening step needs to be done again.

Related Information

For additional information, see Known issues when deploying Deep Security Virtual Appliance in VMware NSX-T 2.5.

Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T

Take Our Survey

Support Assistant