From vlyamtsev@mzeal.com Fri Jan 4 07:13:00 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AF6321F8887 for ; Fri, 4 Jan 2013 07:13:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.001 X-Spam-Level: X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dPTzNHw5gEUi for ; Fri, 4 Jan 2013 07:12:59 -0800 (PST) Received: from mzeal.com (mzeal.com [199.237.228.71]) by ietfa.amsl.com (Postfix) with ESMTP id BC3C221F8756 for ; Fri, 4 Jan 2013 07:12:59 -0800 (PST) Received: (qmail 91283 invoked by uid 25671); 4 Jan 2013 15:12:59 -0000 Message-ID: <20130104151259.91282.qmail@mzeal.com> Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII"; format="flowed" MIME-Version: 1.0 X-Mailer: MIME::Lite 3.0104 (F2.72; T1.15; A1.47; B3.01; Q3.01) Date: Fri, 4 Jan 2013 15:12:59 +0000 From: "Victor Lyamtsev" To: netconf@ietf.org Subject: [Netconf] client/ server terminology -? X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 15:13:00 -0000 Hello, It's my understanding ( from standard) that "client" is an application that makes configuration request and "server" is an application (RPC server) that acts on it.... So, if I have 100 managed devices, does it mean I have to have "server" on each device? Is it possible to have one RPC server and 100 "actor" applications, like SNMP traps? What is the purpose of "manager"? Can someone clarify client/server/manager terminology? Thanks, From j.schoenwaelder@jacobs-university.de Fri Jan 4 08:31:04 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CEEFF21F8A79 for ; Fri, 4 Jan 2013 08:31:04 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id emI9ebTQ1xtN for ; Fri, 4 Jan 2013 08:31:04 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 0D98721F8A74 for ; Fri, 4 Jan 2013 08:31:04 -0800 (PST) Received: from localhost (demetrius4.jacobs-university.de [212.201.44.49]) by hermes.jacobs-university.de (Postfix) with ESMTP id 882C520BE6; Fri, 4 Jan 2013 17:31:02 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius4.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id G4t-sEJqfrY8; Fri, 4 Jan 2013 17:31:02 +0100 (CET) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 2265620BD8; Fri, 4 Jan 2013 17:31:02 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 6CCCB23C76BB; Fri, 4 Jan 2013 17:31:16 +0100 (CET) Date: Fri, 4 Jan 2013 17:31:16 +0100 From: Juergen Schoenwaelder To: Victor Lyamtsev Message-ID: <20130104163116.GA34483@elstar.local> Mail-Followup-To: Victor Lyamtsev , netconf@ietf.org References: <20130104151259.91282.qmail@mzeal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130104151259.91282.qmail@mzeal.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] client/ server terminology -? X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 16:31:04 -0000 On Fri, Jan 04, 2013 at 03:12:59PM +0000, Victor Lyamtsev wrote: > Hello, > It's my understanding ( from standard) that "client" is an application that makes configuration request and "server" is an application (RPC server) that acts on it.... So, if I have 100 managed devices, does it mean I have to have "server" on each device? Yes. > Is it possible to have one RPC server and 100 "actor" applications, like SNMP traps? Now you are talking about notifications. Notifications are emitted by the server and received by clients that subscribe to an event stream. > What is the purpose of "manager"? Can someone clarify > client/server/manager terminology? NETCONF does not use the term 'manager'. But basically, a NETCONF management applications includes a NETCONF client to talking to NETCONF servers. See RFC 6244 for a general overview or the slides of my NETCONF YANG tutorial that I presented a few IETFs ago. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From vlyamtsev@mzeal.com Fri Jan 4 08:48:47 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F041421F88A8 for ; Fri, 4 Jan 2013 08:48:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.299 X-Spam-Level: X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzbWNOegRqUJ for ; Fri, 4 Jan 2013 08:48:32 -0800 (PST) Received: from mzeal.com (mzeal.com [199.237.228.71]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB8C21F88A1 for ; Fri, 4 Jan 2013 08:48:32 -0800 (PST) Received: (qmail 48188 invoked by uid 25671); 4 Jan 2013 16:48:26 -0000 Message-ID: <20130104164826.48187.qmail@mzeal.com> Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII"; format="flowed" MIME-Version: 1.0 X-Mailer: MIME::Lite 3.0104 (F2.72; T1.15; A1.47; B3.01; Q3.01) Date: Fri, 4 Jan 2013 16:48:26 +0000 From: "Victor Lyamtsev" To: j.schoenwaelder@jacobs-university.de, vlyamtsev@mzeal.com Cc: netconf@ietf.org Subject: Re: [Netconf] client/ server terminology -? X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 16:48:47 -0000 So, is the "subscriber" also "client", e.g. would i have to install the same application on workstation that issues configuration request and on managed device? Does that mean "subscribers" have to be connected to RPC server to receive notifications, or is that mechanism multicast-based? Thank you, again. -V ------- Original Message ------- On 1/4/2013 4:31 PM Juergen Schoenwaelder wrote: On Fri, Jan 04, 2013 at 03:12:59PM +0000, Victor Lyamtsev wrote: > Hello, > It's my understanding ( from standard) that "client" is an application that makes configuration request and "server" is an application (RPC server) that acts on it.... So, if I have 100 managed devices, does it mean I have to have "server" on each device? Yes. > Is it possible to have one RPC server and 100 "actor" applications, like SNMP traps? Now you are talking about notifications. Notifications are emitted by the server and received by clients that subscribe to an event stream. > What is the purpose of "manager"? Can someone clarify > client/server/manager terminology? NETCONF does not use the term 'manager'. But basically, a NETCONF management applications includes a NETCONF client to talking to NETCONF servers. See RFC 6244 for a general overview or the slides of my NETCONF YANG tutorial that I presented a few IETFs ago. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From j.schoenwaelder@jacobs-university.de Fri Jan 4 09:50:07 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A5A21F889D for ; Fri, 4 Jan 2013 09:50:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -103.249 X-Spam-Level: X-Spam-Status: No, score=-103.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUBr0u80g2MR for ; Fri, 4 Jan 2013 09:50:07 -0800 (PST) Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) by ietfa.amsl.com (Postfix) with ESMTP id 4961921F8873 for ; Fri, 4 Jan 2013 09:50:06 -0800 (PST) Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 658A120BE1; Fri, 4 Jan 2013 18:50:05 +0100 (CET) X-Virus-Scanned: amavisd-new at jacobs-university.de Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id rsARrIWFkhDU; Fri, 4 Jan 2013 18:50:05 +0100 (CET) Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id C7E3520BD8; Fri, 4 Jan 2013 18:50:04 +0100 (CET) Received: by elstar.local (Postfix, from userid 501) id 7E46C23C796B; Fri, 4 Jan 2013 18:50:19 +0100 (CET) Date: Fri, 4 Jan 2013 18:50:19 +0100 From: Juergen Schoenwaelder To: Victor Lyamtsev Message-ID: <20130104175019.GA34693@elstar.local> Mail-Followup-To: Victor Lyamtsev , netconf@ietf.org References: <20130104164826.48187.qmail@mzeal.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130104164826.48187.qmail@mzeal.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: netconf@ietf.org Subject: Re: [Netconf] client/ server terminology -? X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Juergen Schoenwaelder List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 17:50:07 -0000 On Fri, Jan 04, 2013 at 04:48:26PM +0000, Victor Lyamtsev wrote: > So, is the "subscriber" also "client", e.g. would i have to install > the same application on workstation that issues configuration > request and on managed device? The notification receiver is a NETCONF client. In fact, you subscribe to events by invoking an RPC. But note that this does not imply that its the same _application_. You might very well have a special application that simply subscribes to event notifications. This is an implementation detail. > Does that mean "subscribers" have to be connected to RPC server to > receive notifications, or is that mechanism multicast-based? Yes to the first part. I do not know how you get to multicasting but since everything by default runs over SSH/TCP, it should be rather clear that things won't multicast. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1, 28759 Bremen, Germany Fax: +49 421 200 3103 From hungtath99@gmail.com Sun Jan 6 23:50:36 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93ECB21F8499 for ; Sun, 6 Jan 2013 23:50:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rVtZtzZfWn+9 for ; Sun, 6 Jan 2013 23:50:36 -0800 (PST) Received: from mail-la0-f51.google.com (mail-la0-f51.google.com [209.85.215.51]) by ietfa.amsl.com (Postfix) with ESMTP id 4868021F8444 for ; Sun, 6 Jan 2013 23:50:27 -0800 (PST) Received: by mail-la0-f51.google.com with SMTP id fj20so14779707lab.38 for ; Sun, 06 Jan 2013 23:50:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ZdUnHbWPdhtttiKAqbdXvw3pVg+cL6Rwzvf+dIcBRx8=; b=IuJXTmUERsyFopaNt2oil0JTAbzm94Zrna6eqlD5S5hL/ThNn2h8p4NJfiNqmdSPfN GUIuIaIFbggsb9ZgT8lCg4LZfncwqc4COWAQPwYW9VxdReXDA91LS7pxnBvVokJ1Exap O1n9c2syYeVB0Cuh1t+lwiwcKNPNT/Oz4/fX3LMHYHpJx0NhDYcQBvblodhLe3GK/dH0 I/AuSIhFTZCNnB786ivyW7VPE6nZk4QK1v4+vQrSsGlJuxU5tF0O5uFExQUfQXpHQa2y ztUflpAYig2LjuINXnU6rTUIUcgDxzVe7r4yOI59knjj4TxMSrgK/DpijfEdph2/0OXf FGCg== MIME-Version: 1.0 Received: by 10.112.102.5 with SMTP id fk5mr24680968lbb.31.1357545026767; Sun, 06 Jan 2013 23:50:26 -0800 (PST) Received: by 10.112.62.139 with HTTP; Sun, 6 Jan 2013 23:50:26 -0800 (PST) Date: Mon, 7 Jan 2013 14:50:26 +0700 Message-ID: From: Hung Ta To: netconf@ietf.org Content-Type: multipart/alternative; boundary=f46d0401fa8b164c9604d2ae1518 Subject: [Netconf] netconf daemon starts failed X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2013 08:01:36 -0000 --f46d0401fa8b164c9604d2ae1518 Content-Type: text/plain; charset=ISO-8859-1 Hello everyone, I'm new to netconf. My system is: Ubuntu 10.04 LTS; has built the yuma source. I started the netconf daemon: /home/hung/yuma/netconf/ target/bin/netconfd --superuser=hung --log=/tmp/netconf-example.log But it failed. This the log: *** log open at 2013-01-07T03:32:59Z *** Starting netconfd... Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved. Error: Open txid file for write failed (operation failed) Error: cfg-init transaction ID failed (operation failed) netconfd: init returned (operation failed) Shutting down the netconfd server *** log close at 2013-01-07T03:32:59Z *** Could you please help me to resolve this problem? Appreciate your support. Thanks, Hung --f46d0401fa8b164c9604d2ae1518 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello everyone,

I'm new to netconf.

My system is: Ubuntu = 10.04 LTS; has built the yuma source.

I started the netconf daemon:<= br>/home/hung/yuma/netconf/
target/bin/netconfd --superuser= =3Dhung --log=3D/tmp/netconf-example.log

But it failed. This the log:

*** log open at 2013-01-07T03:32:59Z ***
Starting netconfd...
Cop= yright (c) 2008-2012, Andy Bierman, All Rights Reserved.

Error: Open= txid file for write failed (operation failed)
Error: cfg-init transacti= on ID failed (operation failed)
netconfd: init returned (operation failed)
Shutting down the netconfd se= rver

*** log close at 2013-01-07T03:32:59Z ***

Could you plea= se help me to resolve this problem?

Appreciate your support.

Thanks,
Hung
--f46d0401fa8b164c9604d2ae1518-- From andy@yumaworks.com Mon Jan 7 08:16:38 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA14121F8976 for ; Mon, 7 Jan 2013 08:16:37 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jQiF9hvkrysC for ; Mon, 7 Jan 2013 08:16:37 -0800 (PST) Received: from mail-vb0-f41.google.com (mail-vb0-f41.google.com [209.85.212.41]) by ietfa.amsl.com (Postfix) with ESMTP id 136F621F8971 for ; Mon, 7 Jan 2013 08:16:36 -0800 (PST) Received: by mail-vb0-f41.google.com with SMTP id l22so19336223vbn.14 for ; Mon, 07 Jan 2013 08:16:36 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-gm-message-state; bh=A1hCJWalr2Os8flOkkuo5yNxFZx+TmNrUcGQ/duS2CY=; b=AVFXDEHO4OPwEB6+nvMKN8ylubyK1aNRoXqnrk/MoQ3U2hRM8k8RQf60u7JvnTbmHu 4GJyvePazoCAPsrxu66AKk0SbbHl7VXWspk2bugkBelSsFR0eNSVJUkNro7HnECcj5f1 GeSdhA36IvzOWbFP/Hp+J9VQ67pifvRHzLByPPbWuJLyooSfCQjOGIyApTRhoHI1IA5P 3Ez1fwkfXD4mcHJ+w4UPKsKZuFHlNl31genvpI+V+fMb1pXw8c1jOvrvqWqWUnQrto4h WTANPDFwx4UhYkE2S+szmULIhpoKkoHZedFOndXdqOPNxBRzUzVTPHomOkDPH81QXcND F7cg== MIME-Version: 1.0 Received: by 10.52.240.146 with SMTP id wa18mr72720476vdc.47.1357575396502; Mon, 07 Jan 2013 08:16:36 -0800 (PST) Received: by 10.58.218.71 with HTTP; Mon, 7 Jan 2013 08:16:36 -0800 (PST) In-Reply-To: References: Date: Mon, 7 Jan 2013 08:16:36 -0800 Message-ID: From: Andy Bierman To: Hung Ta Content-Type: multipart/alternative; boundary=20cf30780b4643acfa04d2b52722 X-Gm-Message-State: ALoCoQm+wB823JRPJm7ceSQi6P36S/kY7Cr3GGi8T+3tKf6ZuRsNaUX1NB9vxep/2Y1F2KqP3Y11 Cc: netconf@ietf.org Subject: Re: [Netconf] netconf daemon starts failed X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Jan 2013 16:16:38 -0000 --20cf30780b4643acfa04d2b52722 Content-Type: text/plain; charset=UTF-8 Hi, This list is for NETCONF standards questions. The sourceforge list yuma-users is for this sort of question. This looks like an issue that is fixed in the latest yuma 2.2-5. Make sure the YUMA_HOME env var is valid if it is defined. Andy On Sun, Jan 6, 2013 at 11:50 PM, Hung Ta wrote: > Hello everyone, > > I'm new to netconf. > > My system is: Ubuntu 10.04 LTS; has built the yuma source. > > I started the netconf daemon: > /home/hung/yuma/netconf/ > target/bin/netconfd --superuser=hung --log=/tmp/netconf-example.log > > But it failed. This the log: > > *** log open at 2013-01-07T03:32:59Z *** > Starting netconfd... > Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved. > > Error: Open txid file for write failed (operation failed) > Error: cfg-init transaction ID failed (operation failed) > netconfd: init returned (operation failed) > Shutting down the netconfd server > > *** log close at 2013-01-07T03:32:59Z *** > > Could you please help me to resolve this problem? > > Appreciate your support. > > Thanks, > Hung > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > > --20cf30780b4643acfa04d2b52722 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi,

This list is for NETCONF standards questions.
<= div>The sourceforge list yuma-users is for this sort of question.This looks like an issue that is fixed in the latest yuma 2.2-5. Make sure the YUMA_HOME env var is valid if it is defined.


Andy


O= n Sun, Jan 6, 2013 at 11:50 PM, Hung Ta <hungtath99@gmail.com> wrote:
Hello everyone,

I'm new to netcon= f.

My system is: Ubuntu 10.04 LTS; has built the yuma source.
I started the netconf daemon:
/home/hung/yuma/netconf/
target/bin/ne= tconfd --superuser=3Dhung --log=3D/tmp/netconf-example.log

But it failed. This the log:

*** log open at 2013-01-07T03:32:59Z ***
Starting netconfd...
Cop= yright (c) 2008-2012, Andy Bierman, All Rights Reserved.

Error: Open= txid file for write failed (operation failed)
Error: cfg-init transacti= on ID failed (operation failed)
netconfd: init returned (operation failed)
Shutting down the netconfd se= rver

*** log close at 2013-01-07T03:32:59Z ***

Could you plea= se help me to resolve this problem?

Appreciate your support.

Thanks,
Hung

_______________________________________________
Netconf mailing list
Netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf


--20cf30780b4643acfa04d2b52722-- From rohit.pobbathi@huawei.com Tue Jan 29 05:06:00 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C3EF21F8734 for ; Tue, 29 Jan 2013 05:06:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.659 X-Spam-Level: X-Spam-Status: No, score=-3.659 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, HTML_MESSAGE=0.001, MISSING_MIMEOLE=0.001, MSGID_MULTIPLE_AT=1.449, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id anLbHJEPKQbi for ; Tue, 29 Jan 2013 05:05:58 -0800 (PST) Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 1698E21F87D2 for ; Tue, 29 Jan 2013 05:05:57 -0800 (PST) Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ANY96382; Tue, 29 Jan 2013 13:05:56 +0000 (GMT) Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 29 Jan 2013 13:05:24 +0000 Received: from SZXEML449-HUB.china.huawei.com (10.82.67.192) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.1.323.7; Tue, 29 Jan 2013 13:05:55 +0000 Received: from blrprnc10ns (10.18.96.99) by szxeml449-hub.china.huawei.com (10.82.67.192) with Microsoft SMTP Server id 14.1.323.7; Tue, 29 Jan 2013 21:05:49 +0800 From: Rohit Pobbathi To: Date: Tue, 29 Jan 2013 18:35:48 +0530 Organization: Htipl Message-ID: <000301cdfe21$5c34ea40$149ebec0$@pobbathi@huawei.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0004_01CDFE4F.75ED2640" X-Priority: 1 (Highest) X-MSMail-Priority: High X-Mailer: Microsoft Office Outlook 12.0 Importance: High Thread-Index: Ac3+IVuEWOnwbczmRJKhPrYlfbxQWQ== Content-Language: en-us X-Originating-IP: [10.18.96.99] X-CFilter-Loop: Reflected Subject: [Netconf] Query regarding lifetime of a NETCONF session with notification subscription X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: rohit.pobbathi@huawei.com List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 29 Jan 2013 13:06:00 -0000 ------=_NextPart_000_0004_01CDFE4F.75ED2640 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, I have a query regarding lifetime of a NETCONF session with notification (Server does not support interleave capability in this case). As per RFC 5277, below is the definition of a Notification Subscription: Subscription: An agreement and method to receive event notifications over a NETCONF session. A concept related to the delivery of notifications (if there are any to send) involving destination and selection of notifications. It is bound to the lifetime of a session. 3.5. Subscriptions Data Subscriptions are non-persistent state information, and their lifetime is defined by their session or by the parameter. Consider the case where the server may have a functionality to initiate session closure based on simple inactivity timeout. In such a scenario, the period of inactivity between two notifications can cause a session closure. To receive subsequent notifications, the NMS must create another session and enable subscription. RFC 5277 does not mention about the inactivity timeout in a session with notification subscription, please clarify. Regards, Rohit ------=_NextPart_000_0004_01CDFE4F.75ED2640 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi,

 

I have a = query regarding lifetime of a NETCONF session with notification (Server = does not support interleave capability in this case).

 

As per RFC = 5277, below is the definition of a Notification = Subscription:

Subscription:  = An agreement and method to receive event = notifications

      over a NETCONF session.  A = concept related to the delivery of

      notifications (if there are any to = send) involving destination and

      selection of notifications.  = It is bound to the lifetime of = a

      = session.

 

3.5.  = Subscriptions Data

 

   = Subscriptions are non-persistent state information, and = their

   lifetime is defined by their session or by = the <stopTime> parameter.

 

Consider the = case where the server may have a functionality to initiate session = closure based on simple inactivity timeout.

 

In such a = scenario, the period of inactivity between two notifications can cause a = session closure.

To receive = subsequent notifications, the NMS must create another session and enable = subscription.

 

RFC 5277 does not mention about the inactivity timeout = in a session with notification subscription, please = clarify.

 

Regards,

Rohit

 

------=_NextPart_000_0004_01CDFE4F.75ED2640-- From andy@yumaworks.com Wed Jan 30 00:27:43 2013 Return-Path: X-Original-To: netconf@ietfa.amsl.com Delivered-To: netconf@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57BF721F854E for ; Wed, 30 Jan 2013 00:27:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.976 X-Spam-Level: X-Spam-Status: No, score=-2.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kGaBCqJi+Fk5 for ; Wed, 30 Jan 2013 00:27:42 -0800 (PST) Received: from mail-vc0-f177.google.com (mail-vc0-f177.google.com [209.85.220.177]) by ietfa.amsl.com (Postfix) with ESMTP id 5BFA121F8526 for ; Wed, 30 Jan 2013 00:27:42 -0800 (PST) Received: by mail-vc0-f177.google.com with SMTP id m18so876010vcm.22 for ; Wed, 30 Jan 2013 00:27:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=wIuNUwzgRutUMi379bUzpXeIxiMea2+KOtOXo/m/Ah0=; b=Nptys7Fiumf4WR054JVXqRRTRaX9kQTHK1zsB2wavAIqVIz6Nx0HETklNdSV1od5Vo MZ+UhbRWJM9dbJlwRzHCRKwBPFw0W36VJhihU7kzx9Rno/MmWIrKXLB9SwN3Qgsg7uqW 5WbkvmoEWvlJ3ftq7O4t1ncnk5CZRzpetv24H8BTgfREcZdt4dwbQno6XR9RL5qAsxij ewyLELxhBddfOKqeQbLs31l73lopYeA4FHE5yLtlfIUJoSeFa1Dm2tuHaRXS7FVjWhni 4jdx2NCsoaUFTN1AC3rcEQ4tNkyUPmhswlBnqTyOgrO9DVj1hgpgrF4TJ24fRBcy2kJV k+VA== MIME-Version: 1.0 X-Received: by 10.52.21.107 with SMTP id u11mr3611480vde.101.1359534461658; Wed, 30 Jan 2013 00:27:41 -0800 (PST) Received: by 10.58.33.67 with HTTP; Wed, 30 Jan 2013 00:27:41 -0800 (PST) In-Reply-To: <5107c93c.e1f4440a.2d7e.50c7SMTPIN_ADDED_BROKEN@mx.google.com> References: <5107c93c.e1f4440a.2d7e.50c7SMTPIN_ADDED_BROKEN@mx.google.com> Date: Wed, 30 Jan 2013 00:27:41 -0800 Message-ID: From: Andy Bierman To: rohit.pobbathi@huawei.com Content-Type: multipart/alternative; boundary=20cf3079c0d2a5a7ee04d47d48f1 X-Gm-Message-State: ALoCoQkvxWz5fTuQRQw6HlleS0GS0LxdjnqN+fsADNUITz0pIjny3AKNKxX5EM13PjEGPMU815P9 Cc: netconf@ietf.org Subject: Re: [Netconf] Query regarding lifetime of a NETCONF session with notification subscription X-BeenThere: netconf@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Network Configuration WG mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 08:27:43 -0000 --20cf3079c0d2a5a7ee04d47d48f1 Content-Type: text/plain; charset=UTF-8 I don't think RFC 5277 says anything about idle timeouts. No NETCONF document does, so this is outside the scope of the standard. Do whatever you want I guess. There was no interest in the WG to re-open RFC 5277 when it was discussed last year. Andy On Tue, Jan 29, 2013 at 5:05 AM, Rohit Pobbathi wrote: > Hi,**** > > ** ** > > I have a query regarding lifetime of a NETCONF session with notification > (Server does not support interleave capability in this case).**** > > ** ** > > As per RFC 5277, below is the definition of a Notification Subscription:** > ** > > Subscription: An agreement and method to receive event notifications**** > > over a NETCONF session. A concept related to the delivery of**** > > notifications (if there are any to send) involving destination and** > ** > > selection of notifications. It is bound to the lifetime of a**** > > session.**** > > ** ** > > *3.5. Subscriptions Data***** > > ** ** > > Subscriptions are non-persistent state information, and their**** > > lifetime is defined by their session or by the parameter.*** > * > > ** ** > > *Consider the case where the server may have a functionality to initiate > session closure based on simple inactivity timeout.* > > ** ** > > In such a scenario, the period of inactivity between two notifications can > cause a session closure.**** > > To receive subsequent notifications, the NMS must create another session > and enable subscription.**** > > ** ** > > RFC 5277 does not mention about the inactivity timeout in a session with > notification subscription, please clarify.**** > > ** ** > > Regards,**** > > Rohit**** > > ** ** > > _______________________________________________ > Netconf mailing list > Netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf > > --20cf3079c0d2a5a7ee04d47d48f1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I don't think RFC 5277 says anything about idle timeouts.
No NETCON= F document does, so this is outside the scope
of the standard. = =C2=A0Do whatever you want I guess.
There was no interest in the = WG to re-open RFC 5277
when it was discussed last year.

Andy




On Tue, Jan 29, 2013 at 5:05 AM, Rohit Pobbathi <<= a href=3D"mailto:rohit.pobbathi@huawei.com" target=3D"_blank">rohit.pobbath= i@huawei.com> wrote:

Hi,

=C2=A0

I have a query regarding lifetime of a NETCONF sessi= on with notification (Server does not support interleave capability in this= case).

=C2=A0

As per RFC 5277, below is the definition of a Notification Subscription:=

Subscription:=C2=A0 An agreement and method to receive event notificat= ions

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 over a NETCONF session.=C2=A0 A concept related to th= e delivery of

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 notifications (if there are any to send) involving de= stination and

=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 selection of notifications.=C2=A0 It is bound to the lifetime of a

= =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 session.

=C2=A0

3.5.=C2=A0 Subscriptions Data=

=C2= =A0

=C2=A0= =C2=A0 Subscriptions are non-persistent state information, and their=

=C2=A0= =C2=A0 lifetime is defined by their session or by the <stopTime> parameter.

=C2=A0

Consider the case where = the server may have a functionality to initiate session closure based on si= mple inactivity timeout.

=C2=A0

In su= ch a scenario, the period of inactivity between two notifications can cause= a session closure.

To receive subs= equent notifications, the NMS must create another session and enable subscr= iption.

=C2=A0

RFC 5= 277 does not mention about the inactivity timeout in a session with notific= ation subscription, please clarify.

=C2=A0

Regards,

Roh= it

=C2=A0


_______________________________________________
Netconf mailing list
Netconf@ietf.org
https://www.ietf.org/mailman/listinfo/netconf


--20cf3079c0d2a5a7ee04d47d48f1--