I am sure this is not helpful at all, but I remember in the old rhel 2.1 clustering, you could set a management IP that would bond to a single active cluster node... Not necessarily the service owver. Everyone would confuse the management IP with the service IP and set them to the same address. Then, when you would move the resource, the IP would stay with the original node rather than migrating with the service. I don't think rhel3 clustering has a management interface option, though. > -----Original Message----- > From: linux-cluster-bounces@xxxxxxxxxx > [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Lon Hohberger > Sent: Thursday, July 14, 2005 7:57 AM > To: linux clustering > Subject: Re: IP adress missing from interface > (sometimes) > > On Thu, 2005-07-14 at 11:38 +0200, Miroslav Zubcic wrote: > > > Yes. I have setup another script last night to check output of > > ifconfig every 1 second, it fails 7-8 times a day - 4 times > last night > > until this morning (central european time here). > > > There is no new version on RHN, just checked with up2date(8). > > Good, latest release is good stuff. ;) > > > > I think it's one of the first two, or a combination of both. > > > > I agree. That was my thinking also. We have escalated problem with > > e1000 driver to HP (e1000 is part of their official support > pack for > > RHEL 3 on DL 380). > > Ok, the e1000+bonding problem is almost definitely what you're seeing. > > > I'm afraid that I cannot put test kernels on that machines. > They are > > in production and my head can get on the chuck if I do this. :-) > > Understood. > > > Which version of initscripts? I have initscripts-7.31.22.EL-2 > > Given the report from above (failing 4 times overnight), this > is _not_ your problem. > > -- Lon > > -- > > Linux-cluster@xxxxxxxxxx > http://www.redhat.com/mailman/listinfo/linux-cluster > -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
