cancel
Showing results for 
Search instead for 
Did you mean: 

Standby Lan config question

C Lamb
Advisor

Standby Lan config question

I am building a 2 node MCSG cluster on Red Hat 5 and have a question on the lan config. It used to be you specified the primary interface and a standby, but the 11.18 instructions dont cover that option, rather they "recommend" you use channel bonding. We have had issues with linux and channel bonding so I would prefer setting up the primary/standby config. Below is the cut from the config file complaining there are no standby interfaces, even though they are clearly on the same subnet. The warining note clearly suggest a primary/stanby option is available.


NODE_NAME billdb01a
NETWORK_INTERFACE eth2
STATIONARY_IP 10.10.191.53
NETWORK_INTERFACE eth3
HEARTBEAT_IP 10.1.0.1
NETWORK_INTERFACE eth0
STATIONARY_IP 10.10.191.50
NETWORK_INTERFACE eth1
HEARTBEAT_IP 10.0.0.1
# CLUSTER_LOCK_LUN

# Warning: There are no standby network interfaces for eth2,eth0.
# Warning: There are no standby network interfaces for eth3.
# Warning: There are no standby network interfaces for eth1.

SO can anyone point me to documentation on configuring primary/standby lan for MCSG on Linux?

P.S. please no answers questioning not using channel bonding, we dont want to do that.
8 REPLIES
Steven E. Protter
Exalted Contributor

Re: Standby Lan config question

Shalom,

Check the release notes, but you should still be able to configure a stand by LAN. I do not think that feature was made obsoleted.

The configuration is not going to be different than other versions of SG.

If I'm wrong and the feature is obsolete (Its still there in HP-UX SG) then you may have to use a previous version of SG to avoid channel bonding(Which I use often with no ill effects).

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
C Lamb
Advisor

Re: Standby Lan config question

Started with the release notes A11.18 May 2008. I couldnt find anything except channel bonding.
C Lamb
Advisor

Re: Standby Lan config question

And yes I agree, I have been building MCSG clusters on HP-UX for over 10 years without issue. this is only my second Linux based MCSG cluster and that one didnt properly identify the standy either.
C Lamb
Advisor

Re: Standby Lan config question

In an interesting note, but not one that resolves the issue, I reread the section on redundant network components in the install guide ( B9903-90060 Mar 2008 ) and noticed a nore to use the -w full option on cmquerycl to force discovery across routers and got the following;

NODE_NAME billdb01a
NETWORK_INTERFACE eth2
HEARTBEAT_IP 10.10.191.53
NETWORK_INTERFACE eth3
HEARTBEAT_IP 10.1.0.1
NETWORK_INTERFACE eth0
HEARTBEAT_IP 10.10.191.50
NETWORK_INTERFACE eth1
STATIONARY_IP 10.0.0.1
# CLUSTER_LOCK_LUN

# Primary Network Interfaces on Bridged Net 1: eth2,eth0.
# Warning: There are no standby network interfaces on bridged net 1.
# Primary Network Interfaces on Bridged Net 2: eth3.
# Warning: There are no standby network interfaces on bridged net 2.
# Primary Network Interfaces on Bridged Net 3: eth1.
# Warning: There are no standby network interfaces on bridged net 3.

note it even recognizes eth0 and eth2 on the same network but wont Primary/Standby with them.
John Bigg
Esteemed Contributor

Re: Standby Lan config question

Serviceguard Linux has never had a concept of a standby lan and you MUST use channel bonding to get redundancy. On Serviceguard HP-UX there is a whole network sensor subsystem which monitors lans at a link level and allows failover to a standby. This simply does not exist on Linux and we monitor the lan status using kernel ioctls.

This does not include the functionality required for standby failover so bonding needs to be used to achieve this.

Any references to standby lans you see in older SG/LX manuals are incorrect and are a hangover from the original HP-UX manual the Linux manuals were derived from. No SG/LX release has supported or had standby lan functionality.

So, sorry, I know you did not want an answer directing you back to channel bonding, I am not questioning this decision but if you want redundancy on a single lan this is your only option.
John Bigg
Esteemed Contributor

Re: Standby Lan config question

P.S. The warning does not imply standby functionality is available. It's just shared code between the HP-UX version and the Linux version. You could say that this should not be printed out on Linux, but the fact is that it is and because we do not setup any standby lan structures which still exist within the code you get a message which indicates there is no standby.

The truth is that there are no standby network interfaces because the functionality does not exist.
C Lamb
Advisor

Re: Standby Lan config question

Thanks for the info. I had suspected as much, how does one submit to HP that a statement on this in the manual would be helpful! ;)
John Bigg
Esteemed Contributor

Re: Standby Lan config question

you just did ;-)