- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- Re: Shutdown virtual controller greyed out in vSph...
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
09-14-2020 12:44 PM
09-14-2020 12:44 PM
Shutdown virtual controller greyed out in vSphere
I'm trying to shutdown one of our hosts to see if we can resolve an issue with the omnistack accelerator card showing an error status. The HP maintenance guides state that a troubleshooting step when the accelerator card is not detected or the system cannot communicate with the card is to power off the host, wait 3 minutes for the system to fully shut down, then power the system back up.
I'm attempting to do this but in the vSphere web client when I right-click on the host and go to "All HPE Simplivity Actions.." the option "Shutdown virtual controller" is greyed out. Why is it greyed out? Should I ssh into the ovc and use the svt-shutdown-safe command?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2020 08:37 PM
09-14-2020 08:37 PM
Re: Shutdown virtual controller greyed out in vSphere
Hi,
The option can be greyed out due to multiple reasons. In this scenario, it might be due to the OVC not responding properly due to impending issues.
Kindly shh to the OVC and execute the "svt-shutdown-safe" command to shutdown the OVC.
Kindly reach out to our support team if further assistance is required.
Thank you.
I work for HPE
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2020 09:08 AM
09-16-2020 09:08 AM
Re: Shutdown virtual controller greyed out in vSphere
I haven't tried this yet but will today. A question just occurred to me though, I don't have to worry about the ovc not coming back up if the accelerator card still isn't working when I boot everything back up, right?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2020 11:14 AM
09-16-2020 11:14 AM
Re: Shutdown virtual controller greyed out in vSphere
The Accelerator card must be healthy for the OVC to come up properly.
I am an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2020 12:49 PM
09-16-2020 12:49 PM
Re: Shutdown virtual controller greyed out in vSphere
Ah, well I'm glad I haven't tried this then. I was only going to attempt this because the official simplivity Maintenance and Installation guide lists shutting down the host as a troubleshooting step when the accelerator card is not responding or not detected. This is what I'm seeing when I look at the Accelerator card in vCenter:
Is there some other troubleshooting step I can perform myself to try and resolve this or at least a way for me to determine if this is an irreperable hardware failure?