cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
687
Views
1
Helpful
5
Replies

VC datastore name does not match HX datastore name

apralong
Level 1
Level 1

Hello

Despite recommendations in the documentation, (not correctly read ). "Cisco HyperFlex Data Platform Administration Guide, Release 5.5"

We have unfortunately renamed the datastore from the vCenter, so we have Datastore-HX1 in vCenter and datastore1 in HX connect.
This works, but we recently got a message in vCenter and HX Healhcheck:
"VC datastore name does not match HX datastore name"
How to solve this problem to get back to the right situation
Should we rename it from the vCenter side or from the HX side?
Thanks

Alex

 

1 Accepted Solution

Accepted Solutions

We have renamed DSes in vSphere to match the name seen in HX Connect on 5.0 to get rid of this error message. No impact. 

View solution in original post

5 Replies 5

jhvillam
Cisco Employee
Cisco Employee

Hello, This is not a supported scenario per the documentation:

"Renaming the HX Datastore from the vCenter administration interface is not supported, and should not be done."
"Do not rename an HX datastore from vCenter. The datastore names shown in HX Connect or Intersight and in the ESXi host datastore (that appears in vCenter) must be identical including case sensitive. If they are not identical, some operations such as expansion, mount/unmount of a datastore will be impacted."
https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/AdminGuide/5-5/b-hxdp-admin-guide-5-5/m_hxdp_datastores_manage.html 

 

hello

Thank you for your reply. I know it's not supported but it doesn't help me to find a solution to the problem mentioned in my question.
Thanks in advance if you have a workaround.

Hello,

Renaming from vCenter to match the DS names in HX connect should help fixing it.I'd recommend to create a dummy DS to change the name in vCenter and change it back and see if it actually works fine since I have not tested it in the lab myself

 

 

We have renamed DSes in vSphere to match the name seen in HX Connect on 5.0 to get rid of this error message. No impact. 

apralong
Level 1
Level 1

Thanks you all for your help !

 

Review Cisco Networking for a $25 gift card

Review Cisco Networking for a $25 gift card