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

From: Krishna <krishna.setwin_at_gmail.com>
Date: Fri, 6 Apr 2012 07:07:23 -0400
Message-ID: <CAF6DRCqNMj0Jt8VTLhs1rKXBj9D8SqJTgurjJzkxeq0bvxvuCg_at_mail.gmail.com>



our network admin mentioned to me that
169.254.1.x is a separate vlan created to me and nobody else will use other than myself..
is he correct?
The requirement I gave to him is: non-routable and separate vlan(if separate switch not available) and private

if 169.254.1.x is reserved for me only, can HAIP( and others like DHCp) use other available vlans?

Am i missing anything else here?

Thanks everybody for stepping in..

krishna..

On Fri, Apr 6, 2012 at 6:41 AM, Radoulov, Dimitre <cichomitiko_at_gmail.com>wrote:

>
> Hi Freek,
>
>
> On 06/04/2012 12:29, D'Hooge Freek wrote:
>
>> How can you assign a different vlan on network ports that are part of the
>> same bond?
>> I would think this would break your bonding, meaning you tested on a bond
>> that has only 1 working network port to begin with.
>>
>
> Correct. It was exactly that - a totally miss-configured bonding. It was
> due to a misunderstanding between
> the sysadmin group and the dba group that provided the installation
> requirements.
> We noticed that error during the HA tests ...
>
>
> The reason why you need to use separate subnets when using HAIP with
>> multiple nics is the os routing. When you have multiple ip addresses in the
>> same subnet on a server, it is the routing table which determines the
>> interface to be used for outgoing traffic.
>> If that interface fails, the routing table will not be changed and thus
>> all communications break.
>>
>> This is also the reason why one should not use ifdown to test network
>> failures.
>> It does things to cleanly, like removing the entry for that interface
>> from the routing table.
>>
>
> Thanks for the explanation!
>
>
> Best regards
> Dimitre
>

--
http://www.freelists.org/webpage/oracle-l
Received on Fri Apr 06 2012 - 06:07:23 CDT

Original text of this message