- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- HPE SimpliVity plugin not working on vCenter after...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday
yesterday
HPE SimpliVity plugin not working on vCenter after Vc certificate renewal
Good morning,
We have an HP server infrastructure with VMware and Simplivity. Our vCenter (v7.0.2.00200) certificate expired last week, and we ran the renewal procedure, which worked correctly. After this, we noticed that the Simplivity plugin couldn't connect to vCenter. We've investigated and found that there is a procedure to renew the vCenter certificate on our OmniCube machines, but it doesn't work on our version of them (the command doesn't exist). Has anyone encountered this problem and has another procedure or workaround to solve it?
Our Omnicube machines are version 4.1.0.266, and the procedure we found that doesn't work on them is to apply the following commands, logging in as svtcli:
$sudo su # Elevate to root
# source /var/tmp/build/bin/appsetup # Source the dsv commands
# dsv-reload-vc-cert --username administrator@vsphere.local --password <your_password> --server 'IP'
or
$sudo su # Elevate to root
# source /var/tmp/build/bin/appsetup # Source the dsv commands
# svt-reload-vc-cert --username administrator@vsphere.local --password <your_password> --server 'IP'
Thanks in advance