Wrong Lan Failover.

[brian_31]

Hi Team:

We have two Packages on a Single node SG cluster. pkg.A(an appllication where lan1 would failover to lan4) pkg. B(routed thru lan 3 and when it fails would failover to lan5). Pkg.A works fine(when lan1 is taken off it fails over to lan4) but Pkg.B(when the lan3 is taken off it does not failover to lan5 but to lan4 too). Why would this happen. I have checked the config files and it seems to be OK. Can someone help please.

Thanks
Brian.

[John Poff]

Hi Brian,

The LAN failover is set in your cluster configuration file and is configured per node, not per package. The LAN failovers will happen according to that configuration no matter what packages are on the node and running.

If you really want to group your lan cards together like that, you might try loading the HP Auto Port Aggregation software and configuring it. It will let you group two or more LAN cards together. That way, you could group lan1 and lan4 together as lan100, and lan 3 and lan5 as lan101. Still, the packages are going to use whatever LAN is available per the cluster config.

JP

[brian_31]

Hi John:

The package control files and ascii files are set up for lan1 failing over to lan4 and lan3 to lan5. I am not sure what i am missing here?

Thanks
Brian.

[John Poff]

Brian,

Why don't you post your package and cluster config files and we'll see what you have setup?

JP

[Ashwani Kashyap]

If you are using mutli port LAN CARDS the ncheck you lan numbers with the hardware address and device files . Some thing might be missing there .

Also check whether lan5 is plugged in the segment as lan3 and not lan4 .

[harry d brown jr]

You have about 70 posts that you haven't responded to:
http://forums.itrc.hp.com/cm/TopSolutions/1,,CA695674!1!questions,00.html

live free or die
harry

[Carsten Krege · Accepted solution]

SG will perform a failover to the first lan that it finds that fulfills the following conditions:

- same lan topology (e.g. ethernet) as failed primary lan
- hardware status UP
- no IP address configured
- configured in the SG binary
- configured on the same bridged net as failed primary lan


If there is more than one standby lan that fulfills all these conditions, SG will choose the first that it finds. There is no mean to assign a specfic standby lan to specific primary lan. A standby lan can be standby for more than one primary lan.

Carsten

[brian_31]

Hi Carsten:

Thanks much. First to answer to harry's question: Thanks for reminding but as you can see it is not intentional. I try to assign points immediately, but in some cases the answers come days after the message is posted so you may not watch the thread. Anyway i will make it 100%.

So Carsten, my problem is when i fail lan3 it goes to lan4 (instead of lan5 as i thought i configured it) but when lan4 is is already pulled out it fails over to lan5. But can you explain the following case..
I had lan5 pulled out and i failed lan1 and it went to lan4 but when i plugged back lan1(with lan5 still taken away) it did not switch back to lan1 at all.I am little confused here.

Thanks
Brian.

[melvyn burnard]

would be good to post the output file created by doing cmscancl here.
Also confirm your SG version and patch level

[Carsten Krege]

Brian,

Your problem of a lan not failing back if the primary is reconnected, is most likely
a problem of the lan driver! There were several occurrences like this in the past
(e.g. EISA 100BT) and as far as I know, none is outstanding. You should identify the
driver of lan1 (ioscan -fkClan) and apply appropriate patches for this lan driver
(PHNE_.....).

One of the problems that I remember was that the failed lan was not marked DOWN
completely after the local failover. For your case this could mean that the fail
back would perhaps succeed if you did a "ifconfig lan1 down" before you reconnect
the cable. Again this was a problem of the lan driver which was fixed by a patch.
However, this is only one example of the few occurrences we had.

Carsten