Re: oracle 10.2.0.4.3 RAC RHEL 5.4 x86_64 nic bonding + trunking (etherchannel)

HI Jakub,

sorry for the late reply too,
I found there is network design problem (blade)

We want to aggregate the bandwidth with 2 switches, but it likelily doesn't
support.
so they are trying to mix the network diagram and configuration
but when conduct failover test, RAC problem just comes.


On Sat, Jun 12, 2010 at 6:42 PM, Jakub Wartak <vnulllists@xxxxxxxxxxxx>wrote:

> Dnia czwartek, 3 czerwca 2010 14:09, Ujang Jaenudin napisał:
> > hi jakub,
> >
> > I have set MIITOL variable to non-existent-file, like this:
> > #MIITOOL=/sbin/mii-tool
> > MIITOOL=/sbin/mii-tool-non
> >
> > but got this when one switch turn off (we do HA test)
> >
> > rac 10.2.0.4.4
> > bond0 is bonding for virtual ip, switch is trunked
> > bond1 for heartbeat.
> >
> >
> > 2010-05-29 06:33:32.803: [ RACG][51317200]
> > [5674][51317200][ora.radpadb2.vip]: clsrcep:evm post return 1
> > 2010-06-03 18:19:23.210: [ RACG][51317200]
> > [27658][51317200][ora.radpadb2.vip]: ping to 10.33.200.1 via bond0
> failed,
> > rc = 1 (host=radpadb1)
> > ping to 10.33.200.1 via bond0 failed, rc = 1 (host=radpadb1)
> > Interface bond0 checked failed (host=radpadb1)
> > Invalid parameters, or failed to bring up VIP (host=radpadb1)
> >
> > so, even node1 still alive, but from client/app server cannot connect to
> > it. node2 was restarted, due to share switch for public and heartbeat :)
> > this is blade world...we had no flexible networking on it :(
>
> Sorry for late reply, but please send me
> 1) version of your script (and attach it to the email), i don't have access
> to
> 10.2.0.4 currently
> 2) network diagram of your RAC cluster with ip addresses for public&private
> interfaces, switches, connections, etc.
>
> It's hard to say anything without seeing the enviorniment.
>
> --
> Jakub Wartak
> http://jakub.wartak.pl/blog
>



-- 
thanks and regards
ujang jaenudin
jakarta - indonesia

Other related posts: