HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Automatic and manual failover
Operating System - HP-UX
1834908
Members
2622
Online
110071
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
03-16-2002 08:07 AM
03-16-2002 08:07 AM
Automatic and manual failover
Hi all,
I want to know the difference between the mechanism behind halt the node to make the package automatically failover and manually halt the pacakge in one node, then restart the package on the other node. Because, in two case, the application connect to the node has received different error.
Thanks
Regards,
Wendy
I want to know the difference between the mechanism behind halt the node to make the package automatically failover and manually halt the pacakge in one node, then restart the package on the other node. Because, in two case, the application connect to the node has received different error.
Thanks
Regards,
Wendy
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2002 08:28 AM
03-16-2002 08:28 AM
Re: Automatic and manual failover
Hi Wendy:
If you stop to think about it a moment you will realize that your question is far from simple. If you do a cmhaltpkg that is a normal graceful package halt. Depending on what your package scripts do, a nice message might be sent to each client. Now for the automatic failover case, a meteor might have fallen on the node ,in which case, I doubt that the connected clients would get any kind of message.
MC/SG can't guarantee a nice, clean failover from the client's point of view. It does guarantee that the service will be restored to the same IP address in a reasonable period of time. How a client deals with the timeouts and other messages is up to it.
Food for thought, Clay
If you stop to think about it a moment you will realize that your question is far from simple. If you do a cmhaltpkg that is a normal graceful package halt. Depending on what your package scripts do, a nice message might be sent to each client. Now for the automatic failover case, a meteor might have fallen on the node ,in which case, I doubt that the connected clients would get any kind of message.
MC/SG can't guarantee a nice, clean failover from the client's point of view. It does guarantee that the service will be restored to the same IP address in a reasonable period of time. How a client deals with the timeouts and other messages is up to it.
Food for thought, Clay
If it ain't broke, I can fix that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP