- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Re: VSA boot up and shut down order with ESX
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
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
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
тАО04-20-2009 09:57 AM
тАО04-20-2009 09:57 AM
VSA boot up and shut down order with ESX
One issue with using a VSA as iSCSI storage on the same ESX server hosting the VSA is that rebooting the ESX server can take a long time, and may not complete, since the VSA has to shutdown first taking some storage offline before ESX is done shutting down.
Also on bootup the VSA is not online when ESX is first looking for iSCSI.
All this is avoided usually since VSA are meant to me clustered together to provide redundancy. But if using just one VSA, or a power event takes the whole cluster offline you would run into this issue.
There are scripts available now that were built by a collaborative effort in the old forum. These scripts make ESX servers capable of shutting down and booting up cleaner even if hosting the same VSA as they use for iSCSI storage.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2009 10:00 AM
тАО04-20-2009 10:00 AM
Re: VSA boot up and shut down order with ESX
ESX server shutdown, and boot up script is attached.
The shutdown script automates shutting down VMs, shutting down VSA, and disabling iSCSI in a manner that allows the ESX server to shutdown cleanly.
The boot up script automates enabling iSCSI, starting the VSA, rescanning storage, and then starting VMs that are configured to auto start in ESX as per usual.
The disabling and enabling of the iSCSI adapter eliminates the long wait for iSCSI volumes at boot up.
To install simply remove the .txt file extension, copy it to your ESX server, make it executable, and run it. The single script sets up everything.
This does not work with ESXi, that will probably require something more involved inside of a remote CLI appliance.
The script is attached as a text file to this post (look for the paper clip icon)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2009 10:04 AM
тАО04-20-2009 10:04 AM
Re: VSA boot up and shut down order with ESX
The script is attached as a text file to this post (look for the paper clip icon)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 09:48 PM
тАО06-01-2009 09:48 PM
Re: VSA boot up and shut down order with ESX
We called VMWare and opened a ticket, they tweaked the script and we are still having the same issue.
Anyone test this script recently?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-01-2009 10:43 PM
тАО06-01-2009 10:43 PM
Re: VSA boot up and shut down order with ESX
The original script works, just do not allow the use of spaces in your VSA path to your vmx file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2009 05:07 AM
тАО07-28-2009 05:07 AM
Re: VSA boot up and shut down order with ESX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2009 11:57 AM
тАО07-28-2009 11:57 AM
Re: VSA boot up and shut down order with ESX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-28-2009 02:44 PM
тАО07-28-2009 02:44 PM
Re: VSA boot up and shut down order with ESX
1) Enable ssh on the ESXi server
2) generate ssh public/private keys on the vMA for the "root" user (/root/.ssh/) and don't user a passphrase (yes this isn't very secure, so don't use it in production)
3) on the ESXi server you need to create a /.ssh/authorized_keys file. If using a USB version of ESXi you'll need to create a new oem.tgz. (this site helps http://lars.karlslund.dk/?p=3)
4) Once you've got it setup so that from the vMA you can auto ssh into the ESXi it's just a matter of a few commands and timing of startup.
5) vi /etc/rc.local on the vMA
You'll need to add these 3 commands (replace vmhbaXYZ with your correct HBA and use your real password):
ssh root@SERVER_IP 'esxcfg-swiscsi -e'
vicfg-rescan --username root --password yourpassword --server SERVER_IP vmhbaXYZ
ssh root@SERVER_IP 'esxcfg-swiscsi -d'
6) in your automatic startup on ESXi, make sure VSA starts first, then after it has completely started, startup the vMA, and make sure any other VM on the direct attached storage (not on the virtual iSCSI) is setup to go after the vMA and has a long enough delay to have the vMA completely start, run it's commands, and let ESXi rescan the HBA.
I think that's all there was to it. :)