HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- cluster re-config when removing network interface
Operating System - Linux
1827699
Members
3138
Online
109967
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
04-27-2007 02:42 AM
04-27-2007 02:42 AM
cluster re-config when removing network interface
I would assume that I do not need to halt the cluster when removing a broken interface card from the cluster configuration ?
Thanks,
Matthias
Thanks,
Matthias
mabios
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-27-2007 08:19 PM
04-27-2007 08:19 PM
Re: cluster re-config when removing network interface
If the interface is used for sending/receiving cluster heartbeats, you would have to at least remove this node from the cluster and re-add it as a "new" node.
The heartbeat configuration cannot be changed while the node is running... but a new node can have a different heartbeat configuration than the old ones.
Besides, why remove it?
If the fault is detected and does not cause any further problems, it can wait until you take the node down for fixing the failed interface. (If you have hardware that allows you to hot-swap the network interface, good for you.)
If the broken interface *does* cause problems, well... one of the reasons your cluster was built was certainly to make it possible to fix a broken node without affecting the applications, right? If this does not work in practice, find out why and fix that problem too. Usually this means the software bloat has eaten away your power reserve, and the remaining nodes cannot handle any extra load. The solution is to add more power, either by adding CPUs or RAM to the existing nodes, or increasing the number of nodes.
The alternative to fixing it now *at a time of your choosing* is to have a simple node failure at some unknown future time turn into a total catastrophe because the cluster cannot perform satisfactorily with one node down.
If you don't intend to replace the broken interface, you must realize you're weakening the redundancy built into your cluster configuration. The loss of the remaining interface card(s) on that node will now be more likely to drop the entire node out of the cluster.
MK
The heartbeat configuration cannot be changed while the node is running... but a new node can have a different heartbeat configuration than the old ones.
Besides, why remove it?
If the fault is detected and does not cause any further problems, it can wait until you take the node down for fixing the failed interface. (If you have hardware that allows you to hot-swap the network interface, good for you.)
If the broken interface *does* cause problems, well... one of the reasons your cluster was built was certainly to make it possible to fix a broken node without affecting the applications, right? If this does not work in practice, find out why and fix that problem too. Usually this means the software bloat has eaten away your power reserve, and the remaining nodes cannot handle any extra load. The solution is to add more power, either by adding CPUs or RAM to the existing nodes, or increasing the number of nodes.
The alternative to fixing it now *at a time of your choosing* is to have a simple node failure at some unknown future time turn into a total catastrophe because the cluster cannot perform satisfactorily with one node down.
If you don't intend to replace the broken interface, you must realize you're weakening the redundancy built into your cluster configuration. The loss of the remaining interface card(s) on that node will now be more likely to drop the entire node out of the cluster.
MK
MK
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP