- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Who Me Too'd this topic
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
Who Me Too'd this topic
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2020 08:10 AM
05-15-2020 08:10 AM
I've started a new thread on this rather than hijacking an old one :0)
I'm running SimpliVity 4.0.1
I'm finding the complete shutdown of a federation a very hit and miss affair. Everything is fine until I get to the last node that is running the VCSA. I shut all other vm's down with the exception of the VCSA and the OVC and then shutdown the VCSA.
I next SSH into the OVC as SVTCLI (as the VCSA is shutdown) and this is where I hit issues. I get the same error on all six of the two node environments I've tried so far - so I must be missing a step.
I run
~$ svt-shutdown-force --emergency
This asks me to confirm I want to shutdown even without achieving HA compliance to which I respond 'yes'. The it asks me for the svtcli password (which I enter). it then returns 'A shutdown task is not running on the virtual controller' and nothing more happens. This did work for one cluster but not any of the others I tested with.
I have also tried 'sudo su' followed by 'source /var/tmp/build/bin/appsetup' and 'stop svtfs' but this says "command 'stop' not found, but there are 18 similar ones"
Where do I go from here please?
Solved! Go to Solution.