Return-Path: X-Original-To: oracle-l@orafaq.com Delivered-To: oracle-l@orafaq.com Received: from puck1183.startdedicated.com (localhost [127.0.0.1]) by puck1183.startdedicated.com (Postfix) with ESMTP id D7EAB196071C for ; Fri, 9 Sep 2016 23:52:41 +0200 (CEST) Received: from turing.freelists.org (turing.freelists.org [206.53.239.180]) by puck1183.startdedicated.com (Postfix) with ESMTPS for ; Fri, 9 Sep 2016 23:52:41 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 90CAF2CCEC; Fri, 9 Sep 2016 17:52:40 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at turing.freelists.org Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shinu_furyub; Fri, 9 Sep 2016 17:52:40 -0400 (EDT) Received: from turing.freelists.org (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id A14D42CCF5; Fri, 9 Sep 2016 17:52:27 -0400 (EDT) Received: with ECARTIS (v1.0.0; list oracle-l); Fri, 09 Sep 2016 17:51:06 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id DA82D2CCB2 for ; Fri, 9 Sep 2016 17:51:05 -0400 (EDT) Received: from turing.freelists.org ([127.0.0.1]) by localhost (turing.freelists.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eZGjzy_u-OSv for ; Fri, 9 Sep 2016 17:51:05 -0400 (EDT) Received: from mail-oi0-f51.google.com (mail-oi0-f51.google.com [209.85.218.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTPS id ACA462C9DA for ; Fri, 9 Sep 2016 17:51:05 -0400 (EDT) Received: by mail-oi0-f51.google.com with SMTP id q188so53220892oia.3 for ; Fri, 09 Sep 2016 14:51:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=3sQF/TwQUZIP+OmT+YktmHRhMCjqPDtSb2ClMxoaiUA=; b=VVTkyoab59lTtj9o/XQrnXTaxKXD08iQcDMyYuoAgwqzYP2sFNZrlbb1+H2qW+Vf45 0W6m+EV0aoRLYeXWx/0f6aQ2jnPNWzyc32oZuh9GbPlga9iK1zMIkigtJZle3MfG1Bxf YNX9tmUR8P4fX8YH8KfU3uNKMJwaRnwNtY1+W43IwrNUu6c3+ysUHZ5onKmQk3MhM4Zb e1eBrhOOgtbtwZysu+kkZPM4EdG58HormnjjepxNwVN7AtXOz6ygM1U45h/8SjfbiTJz jtCIBKQqpiDp8umVIne7yXyXyQgRKCnXB8MT8XZZEPyrnlWnjYvnj4LKZghzSJ05dKU9 oAHQ== X-Gm-Message-State: AE9vXwNLmLNDQ307i6GTxogPLi2ItreA0RbU/I1MIMUF4sZNIOhnskX/4au2wlZmJ+dxnQ== X-Received: by 10.157.10.50 with SMTP id 47mr8570440otg.8.1473457865039; Fri, 09 Sep 2016 14:51:05 -0700 (PDT) Received: from ?IPv6:::ffff:172.25.83.33? ([165.215.94.5]) by smtp.gmail.com with ESMTPSA id y132sm2593045itc.20.2016.09.09.14.51.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Sep 2016 14:51:04 -0700 (PDT) Message-ID: <57d32ec8.8a75240a.d8f5a.9e0d@mx.google.com> MIME-Version: 1.0 To: Seth Miller Cc: "'oracle-l@freelists.org' (oracle-l@freelists.org)" From: Subject: RE: Grid Networking Reliance on DHCP Date: Fri, 9 Sep 2016 17:51:04 -0400 In-Reply-To: References: <57d1cfea.47866b0a.db709.0e5b@mx.google.com> <57d1d508.d46f240a.19398.df46@mx.google.com> <57d2f379.0b16240a.560d5.6b7a@mx.google.com> Content-Type: multipart/alternative; boundary="_7878793D-31FD-44BD-B4B7-64928FC30FE0_" X-archive-position: 66196 X-ecartis-version: Ecartis v1.0.0 Sender: oracle-l-bounce@freelists.org Errors-to: oracle-l-bounce@freelists.org X-original-sender: fmhabash@gmail.com Precedence: normal Reply-To: fmhabash@gmail.com List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: oracle-l X-List-ID: oracle-l List-subscribe: List-owner: List-post: List-archive: X-list: oracle-l --_7878793D-31FD-44BD-B4B7-64928FC30FE0_ Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="utf-8" For the dhcp settings, are the GI/RAC cluster nodes configured any differen= tly in regards of =E2=80=98max-lease-time=E2=80=99?=20 I=E2=80=99m not sure ohw to=20 ---------------------------------------- Thank you From: Seth Miller Sent: Friday, September 9, 2016 4:05 PM To: fmhabash@gmail.com Cc: 'oracle-l@freelists.org' (oracle-l@freelists.org) Subject: Re: Grid Networking Reliance on DHCP I don't doubt this happened to you but I would say due to the lack of respo= nse from the rest of the list and zero mentions of this problem on MOS, it = probably has something more to do with your environment. The bug fix you mentioned is almost three years old. Has that fix not been = applied to your system? All of my clusters use the corporate DNS with DHCP for the public and priva= te IPs and GNS for everything else. Seth On Fri, Sep 9, 2016 at 12:38 PM, wrote: There are so many different implementations/infrastructure configs & bugs, = everything is possible. Googling =E2=80=98Unable to obtain IPv4 DHCP=E2=80= =99 will reveal multiple scenarios. There are also known RH bugs that cause= dhclient to fail to renew the IP e.g. RHBA-2013:1572. =C2=A0 This is the failure we see in the dmesg. The ifup-eth invoked dhclient. Thi= s script IF condition returned the error blow as a result of dhclient not g= etting its IP. As a result, OSW logs shows that the node had lost all its p= ublic/VIPs at the time. Event lasted for about 30 seconds. NTPD reacted by = deleting the interfaces from its configuration. =C2=A0 We see no evidence of device errors. Thus, letting these entries guide us t= hrough. =C2=A0 Aug 22 16:30:05 xxxxx dhclient[12319]: Please report for this software via = the Oracle Bugzilla site: Aug 22 16:30:05 xxxxx dhclient[12319]:=C2=A0=C2=A0=C2=A0=C2=A0 http://bugzi= lla.oracle.com Aug 22 16:30:05 xxxxx dhclient[12319]: Aug 22 16:30:05 xxxxx dhclient[12319]: exiting. Aug 22 16:30:05 xxxxx /etc/sysconfig/network-scripts/ifup-eth: Unable to ob= tain IPv4 DHCP address eth0. =E2=80=A6 Aug 22 16:30:08 xxxxx ntpd[22275]: Deleting interface #8 eth0:4, 172.26.208= .59#123, interface stats: received=3D0, sent=3D0, dropped=3D0, active_time= =3D1754 secs Aug 22 16:30:08 xxxxx ntpd[22275]: Deleting interface #7 eth0:3, 172.26.208= .127#123, interface stats: received=3D0, sent=3D0, dropped=3D0, active_time= =3D1756 secs Aug 22 16:30:08 xxxxx ntpd[22275]:=20 =C2=A0 What do you have the BOOTPROTO set up to in your ifcfg-ethx, for example? =C2=A0 Thanks ---------------------------------------- Thank you =C2=A0 From: Seth Miller Sent: Thursday, September 8, 2016 6:09 PM To: fmhabash@gmail.com Cc: 'oracle-l@freelists.org' (oracle-l@freelists.org) Subject: Re: Grid Networking Reliance on DHCP =C2=A0 Over the last decade, I have never had or heard of a DHCP lease renewal fai= lure causing a clusterware node failover.=C2=A0This seems like a pretty spe= cific problem with your DNS. =C2=A0 Regardless, is there a reason you are not using what I have found to be the= easiest to implement and manage, least error prone, and most scalable opti= on - GNS? =C2=A0 =C2=A0 Seth =C2=A0 On Thu, Sep 8, 2016 at 4:15 PM, wrote: True, but if they are left under the control of DHCP, I have seen issues wh= en dhclient attempts to renew the lease on these IPs and it fails for some = reason. As s result, the VIPs are gone and a failover is triggered. =C2=A0 This can be resolved either by configuring these IPs to never expire or rem= ove DHCP altogether. In such case, I=E2=80=99m thinking the virtual interfa= ces need to be configured with BOOTPROTO=3D"static" =C2=A0 =C2=A0 Feedback appreciated.=20 ---------------------------------------- Thank you =C2=A0 From: Seth Miller Sent: Thursday, September 8, 2016 5:02 PM To: fmhabash@gmail.com Cc: 'oracle-l@freelists.org' (oracle-l@freelists.org) Subject: Re: Grid Networking Reliance on DHCP =C2=A0 The VIPs are created and managed by clusterware. You shouldn't need a confi= guration file at all for them. =C2=A0 =C2=A0 Seth =C2=A0 On Thu, Sep 8, 2016 at 3:54 PM, wrote: I know there are 3 options to configure the public network for a GI cluster= . GNS, DHCP, or static. I have, typically, did a static IP=E2=80=99ing for = public & VIPs. =C2=A0 However, Oracle official documentation indicated that as of 11.2, DHCP can = by used for all VIPs, but not public IP. =C2=A0 SO, =C2=A0the physical interface eth0 and its virtual eth0:1 all have =E2= =80=98BOOTPROTO=3D"static"=E2=80=99.=20 =C2=A0 If you are not using GNS, how are having your IP=E2=80=99s setup for an 11.= 2 GI cluster. =C2=A0 ---------------------------------------- Thank you =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 --_7878793D-31FD-44BD-B4B7-64928FC30FE0_ Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="utf-8"

For the dhcp settings, are the GI/RA= C cluster nodes configured any differently in regards of =E2=80=98max-lease= -time=E2=80=99?

 

I=E2=80=99m not sure ohw to

 

 

=  


----------------------------------= ------
Thank you

 

From: Seth Miller=
Sent: Friday, September 9, 2016 4:05 PM
To: fmhabash@gmail.com
Cc: 'oracle-l@freelists.org' (oracle-l@free= lists.org)
Subject: Re: Grid Networking Reliance on DHCP

<= /div>

 

<= span style=3D'font-size:12.0pt;font-family:"Times New Roman",serif'>I don't= doubt this happened to you but I would say due to the lack of response fro= m the rest of the list and zero mentions of this problem on MOS, it probabl= y has something more to do with your environment.

 

The = bug fix you mentioned is almost three years old. Has that fix not been appl= ied to your system?

 

All of my clusters use the corporat= e DNS with DHCP for the public and private IPs and GNS for everything else.=

 

 

Seth

=  

On Fri, Sep 9, 2016 at 12:38 PM,= <fmhabash@gmail= .com> wrote:

There are so many different implementations/infrastructure con= figs & bugs, everything is possible. Googling =E2=80=98Unable to obtain= IPv4 DHCP=E2=80=99 will reveal multiple scenarios. There are also known RH= bugs that cause dhclient to fail to renew the IP e.g. RHBA-2013:1572.=

 

This is the f= ailure we see in the dmesg. The ifup-eth invoked dhclient. This script IF c= ondition returned the error blow as a result of dhclient not getting its IP= . As a result, OSW logs shows that the node had lost all its public/VIPs at= the time. Event lasted for about 30 seconds. NTPD reacted by deleting the = interfaces from its configuration.

 

We see no evidence of device errors. Thus, letting these ent= ries guide us through.

 

Aug 22 16:30:05 xxxxx dhclient[12319]: Please report for this software v= ia the Oracle Bugzilla site:

Aug 22 16:30:05 xxxxx = dhclient[12319]:     http://bugzilla.oracle.com

Aug 22 16:30:05 xxxxx dhclient[12319]:

Aug 22 16= :30:05 xxxxx dhclient[12319]: exiting.

Aug 22 16:30= :05 xxxxx /etc/sysconfig/network-scripts/ifup-eth: Unable to obtain IPv4 DH= CP address eth0.

=E2=80=A6

Aug 22 16:30:08 xxxxx ntpd[22275]: Deleting interface #8 eth0= :4, 172.26.208.59#123, interface stats: received=3D0, sent=3D0, dropped=3D0= , active_time=3D1754 secs

Au= g 22 16:30:08 xxxxx ntpd[22275]: Deleting interface #7 eth0:3, 172.26.208.127= #123, interface stats: received=3D0, sent=3D0, dropped=3D0, active_time=3D1= 756 secs

Aug 22 16:30:08 xxxxx ntpd[22275]:

 

What do you have the BOOTPROTO set up to in your ifcfg-ethx, for example?=

 

Thanks


----------------------------------------
Thank you

<= p class=3DMsoNormal> 

From: <= a href=3D"mailto:sethmiller.sm@gmail.com" target=3D"_blank">Seth Miller=
Sent: Thursday, September 8, 2016 6:09 PM
To: fmhabash@gmail.com
= Cc: 'ora= cle-l@freelists.org' (oracle-l@freelists.org)
Subject: Re: Gr= id Networking Reliance on DHCP

 

Over the last decade, I have never had or heard of a DHCP = lease renewal failure causing a clusterware node failover. This seems = like a pretty specific problem with your DNS.

 

Regardless, is there a reason y= ou are not using what I have found to be the easiest to implement and manag= e, least error prone, and most scalable option - GNS?

=

 

 

=

Seth

&n= bsp;

On Thu, Sep 8, 2016 at 4:15 PM, <fmhabash@gmail.com&= gt; wrote:

True, but= if they are left under the control of DHCP, I have seen issues when dhclie= nt attempts to renew the lease on these IPs and it fails for some reason. A= s s result, the VIPs are gone and a failover is triggered.

 

This can be resolved either by confi= guring these IPs to never expire or remove DHCP altogether. In such case, I= =E2=80=99m thinking the virtual interfaces need to be configured with BOOTP= ROTO=3D"static"

 

 

Feedback appreciated.


----------------------------------------
Thank you

 

From: Seth Miller
= Sent: Thursday, September 8, 2016 5:02 PM
To: fmhabash@gmail.com
Cc= : 'oracle-l= @freelists.org' (oracle-l@freelists.org)
Subject: Re: Grid Ne= tworking Reliance on DHCP

 

The VIPs are created and managed by clusterware. You shouldn't = need a configuration file at all for them.

&n= bsp;

 

 

=

On Thu, Sep 8, 2016 at 3:54 PM, <fmhabash@gmail.com> wrote:

I know there are 3 optio= ns to configure the public network for a GI cluster. GNS, DHCP, or static. = I have, typically, did a static IP=E2=80=99ing for public & VIPs.

 

However, Oracle official = documentation indicated that as of 11.2, DHCP can by used for all VIPs, but= not public IP.

 

SO, =  the physical interface eth0 and its virtual eth0:1 all have =E2=80=98= BOOTPROTO=3D"static"=E2=80=99.

 

If you are not using GNS, how are having your IP=E2= =80=99s setup for an 11.2 GI cluster.

 


----------------------------------------
Thank you=

 

 

 

 

 

 <= /o:p>

 

= --_7878793D-31FD-44BD-B4B7-64928FC30FE0_-- -- http://www.freelists.org/webpage/oracle-l