- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Network failover behavior... !?
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
07-03-2008 06:03 PM
07-03-2008 06:03 PM
I would like to clarify on the network failover behavior on the MC/SG.
I've got the following configure....
NODE_NAME NODE1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.1.1
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.2.1
NETWORK_INTERFACE lan2
NETWORK_INTERFACE lan3
linkloop lan0 --> lan3 OK
linkloop lan1 --> lan2 OK
I've got problem when both lan0 and lan1 is down.... the ip binded to incorrect interface.
lan0 --> lan2
lan1 --> lan3
any idea?
do i need to change the configure as follow?
NODE_NAME NODE1
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.1.1
NETWORK_INTERFACE lan3
NETWORK_INTERFACE lan1
HEARTBEAT_IP 192.168.2.1
NETWORK_INTERFACE lan2
Thanks,
Warren.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 06:15 PM
07-03-2008 06:15 PM
SolutionStandby LAN interface should have no IP address assigned and this way lan3 will become standby interface for lan0 only and lan2 for lan1 only.
In the previous configuration lan2 and lan3 were standby interfaces for both the lan cards so at the time of failover the first available interface will be assigned the IP. This is the reason lan0 binded to lan2 since that was the first available interface.
I think the last one is better anyways other two interface can not communicate to each other so there is point in keeping lan2 and lan3 as standy for both the interface. Keep them separated one for one.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 06:52 PM
07-03-2008 06:52 PM
Re: Network failover behavior... !?
I use the cmscancl to check on the configure and all the 4 interfaces are in the same "bridged net ID" ...... i think that is the root cause of the incorrect failover, right??
I've got another cluster which having the same network setting and cluster configure, but the 4 network interfaces are in 2 difference "bridged net ID".
thanks & regards,
Warren
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 07:59 PM
07-03-2008 07:59 PM
Re: Network failover behavior... !?
That is the reason it says that standby lan interfaces should be from same net ID.
Here cluster sees all 4 interfaces on same net ID hence in case of first setup it takes both standby interfaces for both the static IP addresses and assign them on availability at the time of failover.
If only one interface is available on that net ID then other standby interface would be ignored since that violates the criteria of standby interface.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 08:11 PM
07-03-2008 08:11 PM
Re: Network failover behavior... !?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 08:14 PM
07-03-2008 08:14 PM
Re: Network failover behavior... !?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-03-2008 10:36 PM
07-03-2008 10:36 PM
Re: Network failover behavior... !?
the cluster is build by HP and i think he did something wrong during the configuration.
When I using the cmscancl to check the cluster configure, the 4 interfaces are in 1 brigded net.
But if I use cmquerycl to check again, it show 2 brigded networks.