Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

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

Configuring CA signed certificates for vCenter Site Recovery Manager 6.x and 8.x (66925)

Last Updated: 6/10/2021Categories: How toTotal Views: 16018Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article provides steps to configure Certificate Based Authentication using CA signed certificates within your SRM server pair.

Resolution

Site Recovery Manager certificate requirements

Site Recovery Manager places some requirements on the contents of those certificates, but the requirements in this release are less strict than in 5.x releases of Site Recovery Manager. Although the requirements are the same since SRM 6.0, the Site Recovery Manager certificate must meet these requirements outlined in the articles below:

SRM 8.4 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 8.4
SRM 8.3 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 8.3
SRM 8.2 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 8.2
SRM 8.1 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 8.1
SRM 6.5 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 6.5
SRM 6.1 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 6.1
SRM 6.0 - Requirements When Using Custom SSL/TLS Certificates with Site Recovery Manager 6.0

IMPORTANT Public CAs stopped issuing SSL/TLS certificates that contain internal server names or reserved IP addresses in November 2015. CAs will revoke SSL/TLS certificates that contain internal server names or reserved IP addresses on 1st October 2016. To minimize future disruption, if you use SSL/TLS certificates that contain internal server names or reserved IP addresses, obtain new, compliant certificates from a private CA before 1st October 2016.

For information about the deprecation of internal server names and reserved IP addresses, see https://cabforum.org/internal-names/.

For information about how the deprecation of internal server names and reserved IP addresses affects VMware products, see Frequently asked questions about Public Certificate Authority certificates with Internal Server Names and VMware Products (2134735).

Generating the certificate request

You can generate the certificate signing request using OpenSSL. If you have already installed the SRM Server using the default certificates, OpenSSL is available on the SRM server under C:\Program Files\VMware\VMware vCenter Site Recovery Manager\bin.

If you have installed OpenSSL on a Windows machine, you can use this while replacing the vCenter Server certificates:

Create an OpenSSL configuration file for each SRM site using a text editor (change the fields in red to match your environment):

Note: All entries in the OpenSSL configuration file must be lowercase.

[ req ]
default_bits = 2048
default_keyfile = rui.key
distinguished_name = req_distinguished_name
encrypt_key = no
prompt = no
string_mask = nombstr
req_extensions = v3_req

[ v3_req ]
basicConstraints = CA:FALSE
keyUsage = digitalSignature, keyEncipherment, dataEncipherment
extendedKeyUsage = serverAuth, clientAuth
subjectAltName = DNS: srm.fqdn.com

[ req_distinguished_name ]
0.organizationName = specify a organizationName or leave blank
organizationalUnitName =  specify a organizationalUnitName or leave blank
commonName = specify a commonName or leave blank

Note: In this example, the files are called protected.cfg and recovery.cfg.

Generate the certificate signing request:

openssl.exe req -new -nodes -out protected.csr -keyout protected-orig.key -config protected.cfg
openssl.exe req -new -nodes -out recovery.csr -keyout recovery-orig.key -config recovery.cfg

Convert the key to the proper RSA format:

openssl.exe rsa -in protected-orig.key -out protected.key
openssl.exe rsa -in recovery-orig.key -out recovery.key

Provide the .csr file to your certificate authority and receive the signed certificate back.

Converting the signed certificate to PKCS#12 format

After you receive the signed certificate (ending in .cer or .crt) from your certificate authority, it must be converted to the PKCS#12 format.

To convert to PKCS#12 format, it requires key files generated while generating the certificate request and the signed certificate:

Copy the signed certificate file to the server where you generated the certificate signing request.

Use OpenSSL to generate the PKCS#12 certificate:

openssl.exe pkcs12 -export -in protected.cer -inkey protected.key -name "srmprotected" -passout pass:srmserver -out protected.p12
openssl.exe pkcs12 -export -in recovery.cer -inkey recovery.key -name "srmrecovery" -passout pass:srmserver -out recovery.p12

Replacing the SRM Certificates

You can replace the SRM certificates during SRM installation or after installation.

Replacing the SRM certificate during installation

Copy the SRM certificate to your SRM server.

Launch the SRM installer and follow the SRM installation wizard.

In the VMware vCenter Server screen, specify the vCenter Server FQDN.

In the Certificate Type Selection screen, click Use a PKCS#12 certificate file and click Next.

Browse the location of the certificate, select the desired file, and enter the certificate password you chose when generating the p12 file.

Complete the SRM installation wizard.

Repeat these steps on the recovery site.

Replacing the SRM certificate after installation

In the protected site, click Add/Remove programs, click VMware vCenter Site Recovery Manager, and click Change.

Follow the wizard until you reach the Certificate Type Selection screen.

Click Use a PKCS#12 certificate file and click Next.

Browse the location of the certificate, select the desired file, and enter the certificate password you chose when generating the p12 file.

Complete the SRM Modify installation wizard.

Repeat the steps on the recovery site.

Configuring or reconfiguring the SRM site connection

After installing the SRM server on both sites, you must configure the connection between SRM sites. If SRM was previously configured you must repair the connection between sites after replacing the default certificates with CA signed certificates.

To repair the sites:

Log in to vCenter Server and access the SRM plugin.

For SRM 6.x - In the Sites navigation pane, right click an SRM site and select Reconfigure Site Pairing.

For SRM 8.x - Open Site Recovery H5 UI, select SRM Pair, select Actions and select Reconfigure Site Pair.

Enter the FQDN of the remote Platform Service Controller and adjust the port, if necessary (this field may be populated for you already).

Verify that the process completes successfully.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Adaptec maxView Storage Manager - ESXi 7.0、6.7.0、6.5.0、6.0 U3 向け CIM プロバイダ (66807)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Site Recovery Manager

Related Versions:

VMware Site Recovery Manager 8.3.x

VMware Site Recovery Manager 8.2.x

VMware Site Recovery Manager 8.1.x

VMware Site Recovery Manager 6.x

VMware Site Recovery Manager 6.5.x

VMware Site Recovery Manager 6.1.x

VMware Site Recovery Manager 6.0.x

Take Our Survey

Support Assistant