- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- heartbeat route entry
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
Forums
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
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
11-03-2011 01:18 AM
11-03-2011 01:18 AM
heartbeat route entry
hi ,
i have a heartbeat route entry given below ;
172.16.0.0/255.255.0.0 172.16.0.6 U 2 lan1 1500
My network guys want me to change this to
172.16.0.0 /255.255.255.0 172.16.0.6
My question is whether deletion of this roue and addition of new route panic my cluster ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-03-2011 08:48 AM
11-03-2011 08:48 AM
Re: heartbeat route entry
This looks like an entry for a directly-connected subnet. In effect, they want you to change the netmask configured for lan1.
If lan1 is your only heartbeat network, your cluster will definitely begin failover actions if you attempt to do this online. If this is a two-node cluster, then the node that can get the cluster lock should remain up, but the other node will panic.
If you have heartbeats routed through another network interface too, the cluster might remain up, but you will get messages about your network configuration not matching what is in the cluster configuration.
The easiest way would be to halt the cluster, modify the netmasks, then modify all the cluster and package configurations to use the new netmasks. You may have to run "cmapplyconf" again for the cluster configuration and all the packages too.