- Community Home
- >
- Storage
- >
- HPE SimpliVity
- >
- What is HA failover?
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-2019 12:35 PM
07-20-2019 12:35 PM
What is HA failover?
Could someone put it in simple words on what actually happens when the storage address of one OVC is taken care by the other OVC when the former fails?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2019 02:40 AM
07-21-2019 02:40 AM
Re: What is HA failover?
ipfailover is triggered when the Virtual controller no longer responds to heartbeats or ARP.
This triggers a protocol by which any remaining nodes in the cluster agree that the node is no longer alive.
One of the nodes in the cluster begins the process of claiming the IP address.
It now has 4 IP addresses its own managment and federation and 2 storage (its own and the failed node)
The ESXi access the simplivty datastore via what appears to it to be an nfs mount,
Once another OVC in the cluster has claimed the faulty sotorage interface then the Datastores are available.
In a 2 node cluster the arbtier service is used to determine if a node is truely faulty or if its a network partition
Once the issue on the faulty node is corrected the ip is released and reclaimed by the origional node.
I am an HPE employee
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]