- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- OVC4.0.1 cannot safety shutdown.
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
07-20-2020 04:53 PM - edited 07-20-2020 04:54 PM
07-20-2020 04:53 PM - edited 07-20-2020 04:54 PM
OVC4.0.1 cannot safety shutdown.
Hi,
I installed 3nodes SimpliVity that OmniStack version is 4.0.1.
Then OVC cannot safety shutdown. Safety shutdown from CLI sometimes succeseed but almost failure.
Is it known issue? and Could I something to do ?
Regards,
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2020 07:19 AM
07-22-2020 07:19 AM
Re: OVC4.0.1 cannot safety shutdown.
Hi @kumadas
Thanks for using the forum.
I'm not aware of any specific issue. I would recommend opening a support case where this culd be demonstrated and subsequently investigated. This would require a live session and log analysis to understand exactly whats happening. Guessing here on the forum would not be the best use of your time I think.
I'm sure we can get to the bottom of what's happening via a support ticket. If there is a bug, then it will be important that we are aware of it, and can document it via a KB article for others that may hit similar.
Thanks,
DeclanOR