- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- 2 Node Cluster with FOM, upon maintenance the clus...
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
тАО07-21-2014 08:57 AM
тАО07-21-2014 08:57 AM
2 Node Cluster with FOM, upon maintenance the cluster goes offline
We were updating the ESX host and put the host in Maint mode which migrated all the VM's to the other host. We powered off the VSA for that host and the storage cluster became inactive on both hosts. It seems that the FOM didnt failover the cluster but it looked online in the console. Has anyone experienced this, we have done this in the past wihout issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2014 10:56 AM
тАО07-21-2014 10:56 AM
Re: 2 Node Cluster with FOM, upon maintenance the cluster goes offline
what did it say in CMC? was there a quorum problem or did CMC think everything was ok? If CMC thought all was OK, then its likely a setup problem with your initiators and you need to check those settings.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-21-2014 11:17 AM
тАО07-21-2014 11:17 AM
Re: 2 Node Cluster with FOM, upon maintenance the cluster goes offline
CMC looks ok, no errors but as soon as I put the ESX host in Maint mode, migrate the VM's and shutdown the VSA for that host the storage cluster changes to inactive. I didnt check the CMC after it happened I just powered the Host backup and the VSA and everything came back. Where do you check the initiators?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-22-2014 05:50 AM
тАО07-22-2014 05:50 AM
Re: 2 Node Cluster with FOM, upon maintenance the cluster goes offline
initiators are the clients connecting to the SAN. In this case its the ESX hosts. If they lose their connection when you shut off a single node, then its likely that you don't have MPIO setup correctly. Follow the HP guide for setting up with ESX and it should work.
If you can repeat this in a controlled condition, it would be helpful to know if CMC has a problem or if its just ESX that is having the problem. If you can shut down all the VMs and then shut off one host and then try and connect to CMC, you should be able to connect and it will only give you a warning that one node is offline. If there is a problem with the SAN, you might not be able to connect to it with CMC or it will connect and throw alarms about LUNs being offline. If CMC isn't already complaining about quorum or connection problems with the FOM or either node then I would bet the problem is the ESX host iscsi config.
Side question... WHERE is your FOM located?