RE: RAC private network IP's - 169.254.x.x

As I understand the note only applies when using multiple single interfaces (or multiple bonds, if for some reason you want to do this) for the interconnect.

What this parameter would do is to allow that a response to a network package is given on a different interface then the interface which has recived the package.

For multiple nic's that are part of a single bond, this would not be necessary as all traffic would go over the bond.

Regards,  

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge_at_uptime.be
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer

-----Original Message-----
From: Radoulov, Dimitre [mailto:cichomitiko_at_gmail.com] Sent: vrijdag 6 april 2012 16:01
To: D'Hooge Freek
Cc: goran00_at_gmail.com; krishna.setwin_at_gmail.com; oracle-l Subject: Re: RAC private network IP's - 169.254.x.x

On 06/04/2012 15:05, D'Hooge Freek wrote:
> and to: http://docs.oracle.com/cd/E11882_01/relnotes.112/e23558/toc.htm#CJAFGABG

Hmm,
I remember reading this requirement and at that time I decided that it didn't apply (not at least in the last case I was talking about). Now, after re-reading the MOS note and the documentation I'm not sure about that...

If I understand the note correctly, after certain bugfix RAC systems that use kernel 2.6.31+ and utilize multiple NICs for the private interconnect, require specific settings for the rp_filter parameter (and Oracle recommends setting this parameter to 2).

The system I was talking about is using RHEL 5.7 with kernel 2.6.18. Multiple bonded NICs are used for the Interconnect If I remember correctly, on those systems rp_filter was set to 1 for all NICs (I don't know if this is a default setting for this OS and kernel or someone manually set it after the OS has been installed).

So should it be changed to 2 on a system that uses kernel 2.6.18 when multiple NICs in bonding are used
for the Interconnect?

Best regards
Dimitre

--
http://www.freelists.org/webpage/oracle-l