IETF Logo Mail Archive

Re: [netmod] NMDA System controlled resource

Rohit R Ranade <rohitrranade@huawei.com> Thu, 17 May 2018 09:30 UTC

Return-Path: <rohitrranade@huawei.com>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B694F1267BB for <netmod@ietfa.amsl.com>; Thu, 17 May 2018 02:30:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level:
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8yI3Epodbq4a for <netmod@ietfa.amsl.com>; Thu, 17 May 2018 02:30:28 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B268E1250B8 for <netmod@ietf.org>; Thu, 17 May 2018 02:30:27 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 795FC821A7515 for <netmod@ietf.org>; Thu, 17 May 2018 10:30:21 +0100 (IST)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 17 May 2018 10:30:22 +0100
Received: from DGGEML510-MBS.china.huawei.com ([169.254.3.215]) by DGGEML404-HUB.china.huawei.com ([fe80::b177:a243:7a69:5ab8%31]) with mapi id 14.03.0382.000; Thu, 17 May 2018 17:30:10 +0800
From: Rohit R Ranade <rohitrranade@huawei.com>
To: Robert Wilton <rwilton@cisco.com>, "netmod@ietf.org" <netmod@ietf.org>
Thread-Topic: [netmod] NMDA System controlled resource
Thread-Index: AdPtkflME8Sn/pZvSPiqMr4/Yzk5pv//0HuA//9yM5A=
Date: Thu, 17 May 2018 09:30:10 +0000
Message-ID: <991B70D8B4112A4699D5C00DDBBF878A6BBAAE98@dggeml510-mbs.china.huawei.com>
References: <991B70D8B4112A4699D5C00DDBBF878A6BBAAC22@dggeml510-mbs.china.huawei.com> <4da2b372-d950-80c6-5a8e-9fa58951f6a8@cisco.com>
In-Reply-To: <4da2b372-d950-80c6-5a8e-9fa58951f6a8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.150.121]
Content-Type: multipart/alternative; boundary="_000_991B70D8B4112A4699D5C00DDBBF878A6BBAAE98dggeml510mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/fVE-gwwCDamG-kXfuB1dD38us5E>
Subject: Re: [netmod] NMDA System controlled resource
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 May 2018 09:30:30 -0000

Hi Robert,

So first , we try to get to know the system configuration.
Then for the configuration leaves (based on description), check whether system configuration trumps the intended configuration ? If yes, retain system configuration, Else apply intended configuration.
If for some leaf, there is no <intended> configuration , then apply system configuration .

Is my understanding correct ?

With Regards,
Rohit R Ranade

From: Robert Wilton [mailto:rwilton@cisco.com]
Sent: 17 May 2018 14:29
To: Rohit R Ranade <rohitrranade@huawei.com>; netmod@ietf.org
Subject: Re: [netmod] NMDA System controlled resource


Hi Rohit,

Section 5.3.2 states that you allowed to have configuration in <running>/<intended> for resources that could be present on the device but are not currently present.  The canonical example would be interface configuration for an interface on a linecard that isn't operational (either because it isn't present, or hasn't completely initialized).

Section 5.3.3 is saying that if the linecard becomes operational, then it may instantiate system controlled entries (in <operational>) for those interfaces.  It also states that if there also happens to be configuration in <running>/<intended> for those interfaces then that configuration will also get applied as those interfaces as instantiated in <operational>.  All of the configuration that has been successfully applied would also appear in <operational>.

Thanks,
Rob

On 17/05/2018 04:57, Rohit R Ranade wrote:
Hi All,

RFC 8342 has below statement in Section 5.3.3
"If a system-controlled resource has
   matching configuration in <intended> when it appears, the system will
   try to apply the configuration; this causes the configuration to
   appear in <operational> eventually (if application of the
   configuration was successful).
"
Why does application of configuration for system-controlled resources depend on whether <intended> has configurations for that resource ? The configuration will still get applied as part of "system" configuration as shown in examples in Section C.1 in the same RFC given below

"In addition to filling in the default value for the auto-negotiation
   enabled leaf, a loopback interface entry is also automatically
instantiated by the system.  All of this is reflected in
   <operational>."


With Regards,
Rohit R Ranade




_______________________________________________

netmod mailing list

netmod@ietf.org<mailto:netmod@ietf.org>

https://www.ietf.org/mailman/listinfo/netmod

v2.23.0 | Report a Bug | By Email