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

Virtual Volumes datastore is inaccessible after moving to another vCenter Server or refreshing CA certificate (67744)

Last Updated: 4/8/2024Categories: TroubleshootingTotal Views: 35267Language:
Chinese (Simplified)JapaneseEnglish

11 like this article

Subscribe to get an email
newsletter with new updates

11 people found this helpful Please provide article feedback:

Symptoms

After moving a host to another vCenter Server or after refreshing CA Certificate, you experience these symptoms:

Virtual Volumes (vVOL) datastores are not accessible.

The command esxcli storage vvol vasaprovider list displays VP status as syncError.

In the vvold.log, you see similar to:

2019-04-03T11:34:59.243Z warning vvold[4AC6B70] [Originator@6876 sub=Default] VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:

--> PeerThumbprint: 4A:78:E1:82:CC:08:27:27:70:EB:BD:61:E2:1F:0D:BC:E4:85:48:F8

--> ExpectedThumbprint:

--> ExpectedPeerName: <IP>

--> The remote host certificate has these problems:

-->

--> * unable to get local issuer certificate, using default

2019-04-03T11:34:59.243Z info vvold[47B1B70] [Originator@6876 sub=Default] VasaSession::Initialize url is empty

2019-04-03T11:34:59.243Z warning vvold[47B1B70] [Originator@6876 sub=Default] VasaSession::DoSetContext: Empty VP URL for VP (xVP)!

2019-04-03T11:34:59.243Z info vvold[47B1B70] [Originator@6876 sub=Default] Initialize: Failed to establish connection https://<IP>:8443/vasa/version.xml

2019-04-03T11:34:59.243Z error vvold[47B1B70] [Originator@6876 sub=Default] Initialize: Unable to init session to VP xVP state: 0

2019-04-03T11:34:59.552Z info vvold[4770B70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols called

2019-04-03T11:34:59.553Z info vvold[4770B70] [Originator@6876 sub=Default] VVolUnbindManager::UnbindIdleVVols done for 0 VVols

2019-04-03T11:35:00.009Z info vvold[5ACBB70] [Originator@6876 sub=Default] Came to SI::GetVvolContainer: container 5fd41e3b-b676-4ad6-8a41-65f10bd73602

2019-04-03T11:35:00.009Z info vvold[5ACBB70] [Originator@6876 sub=Default] SI:GetVvolContainer successful for Datastore, id=, maxVVol=0 MB

Running the esxcli storage vvol storagecontainer list command returns similar to:

Datastore

StorageContainer Name: Datastore

UUID: vvol:5fd41e3bb6764ad6-8a4165f10bd73602

Array: com.vmware.vim:020009763e06-1000000

Size(MB): 0

Free(MB): 0

Accessible: true

Default Policy:

Running the esxcli storage vvol vasaprovider list command returns similar to:

xVP

VP Name: xVP

URL:https://<IP>:8443/vasa/version.xml

Status: syncError

Arrays:

Array Id: com.vmware.vim:020009763e06-1000000

Is Active: true

Priority: 0

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Purpose

This article provides information to resolve the certificate issue for vVols when vCenter Changes or CA certificate changes.

Cause

This issue occurs because the vVol ssl_reset is not occurring automatically when VMCA signed certificate is pushed to the host.

Resolution

To work around this issue reset the vVold SSL certificate:

Migrate the virtual machines from the host and place it in maintenance mode.

Log in to the ESXi host through SSH as root.

Run the command - /etc/init.d/vvold ssl_reset && /etc/init.d/vvold restart

Run the command - tail -f /var/log/vvold.log

Look for Empty VP URL for VP messages. If you still see Empty VP URL for VP messages the SSL certificate will need to re-generated on the ESXi host.

Refer to VMware Product Documentation for re-generating self-sign certs Replace the Default Certificate and Key from the ESXi Shell

Edit the re-generated self-signed certificate.

Log in to the ESXi Shell, either directly from the DCUI or from an SSH client, as a user with administrator privileges.

Navigate to/etc/vmware/ssl.

Rename the existing certificates:.

mv rui.crt orig.rui.crt
mv rui.key orig.rui.key

Run the command /sbin/generate-certificates to generate new certificates.

Confirm that the host successfully generated new certificates by using ls -l and comparing the time stamps of the new certificate files with orig.rui.crt and orig.rui.key.

Go to vSphere  Client, right click the ESXi host, click Certificates, Click Renew Certificate.

Run ls -l to ensure the date changed on the castore.pem file.

Reboot the ESXi host.

Once the host is up, run tail -f /var/log/vvold.log.

If you see errors, update the vCenter Server TRUSTED_ROOTS store.

Disconnect and reconnect the ESXi host to the vCenter Serverto resolve a mismatched SSL thumbprint in vCenter Server compared to the ESXi host.

Run tail -f /var/log/vvold.log. to verify the error is no longer seen.

The expected output should be as below:

2019-04-03T11:35:54.169Z info vvold[8355B70] [Originator@6876 sub=default] SI:GetVvolVontainer successful for DataStoreName, id= maxVVol=0 MB ...

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

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:

VMware vSphere ESXi

Related Versions:

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

Take Our Survey

Support Assistant