- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: OmniCube CN-3000 redeployment issue
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
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
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
11-10-2020 04:03 AM
11-10-2020 04:03 AM
Greerings!
Maybe someone has come across a similar issue..
I'm trying to redeploy a CN-3000 with OmniStack 3.7.10 (the latest supported version for legacy systems) because of the accelerator card replacement (refurbished one).
Here are the steps:
1. Factory reset to v3.7.10 (deploy-installer-10.35.0-psi18+sva-3.7.10.200-usb.img).
2. Boot into the Discovery screen and assign a temporary IP for deploment.
3. Mount the v3.7.0 image that has the required ESXI 6.5 version for legacy hosts.
4. Login into Shell with "svtsupport" account, switch to root (sudo su) and execute /opt/svtdi/legacyTools/fetch_legacy.
After the image has been copied over, I launch the Deployment Manager 3.7.10.
After all the IPs and settings are set, just before it's ready to deploy, it performs pre-requisites check and that's where I get this error:
Cluster OVC Compatibility Test: Host <IP> is not compatible with the <cluster-name> cluster. All virtual controllers in <cluster-name> cluster should be at version 3.7.10.200.
Of course all the existing OVCs are running 3.7.10.200.
It's somewhat unexpected. I performed such legacy deployments before (but without replaced accelerator cards) and never had any issues.
Could it be because the new card has some data on it that must be cleared first or smth like that?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2020 02:16 AM
11-11-2020 02:16 AM
SolutionHi Sergeisokolov
Hope you are doing well.
If the version is the same, this will require an override option as to allow to skip and the checks.
I would request you to get in touch with support to assists you to have the override option enabled.
Thanks
Imobi
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-18-2020 03:30 AM
11-18-2020 03:30 AM
Re: OmniCube CN-3000 redeployment issue
Thanks!
Changing "PredeployValidationOverride" parameter to "True" in the Simplivity.DM.View.exe.config file helped to redeploy the host successfully.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2023 03:54 AM
06-22-2023 03:54 AM
Re: OmniCube CN-3000 redeployment issue
What is the password of svtsupport?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-22-2023 04:02 AM
06-22-2023 04:02 AM
Re: OmniCube CN-3000 redeployment issue
Not sure if it can be publicly posted, but I've sent it to you via a private message.