Re: [YANG] mandatory & default

Hi,

Andy Bierman <ietf@andybierman.com> wrote:
>
>    container interfaces {
>      list interface {
>        key name;
> 
>        leaf name { type InterfaceName; }
> 
>        leaf mtu {
>          type uint32;
>          default 1500;
>        }
>      }
>    }
> 
> I start out with a get-config, and mtu is not there:
> 
>   <interfaces>
>     <interface>
>       <name>eth0</name>
>       <mtu>1600</mtu>
>     </interface>
>     <interface>
>       <name>eth1</name>
>     </interface>
>   </interfaces>
> 
> Does /interfaces/interface[name=eth1]/mtu exist or not?

Not in the config datastore, no.

> If not, then I can do an edit-config to create it:
> 
>    <config>
>      <interfaces>
>        <interface>
>          <name>eth1</eth1>
>          <mtu nc:operation='create'>1500</mtu>
>        </interface>
>      </interfaces>
>    </config>
> 
> Does this succeed? 

Yes.

> NETCONF says it should, because the
> leaf did not get returned in the previous <get-config>.
> 
> Now I do a get-config again and get back:
> 
>   <interfaces>
>     <interface>
>       <name>eth0</name>
>       <mtu>1600</mtu>
>     </interface>
>     <interface>
>       <name>eth1</name>
>       <mtu>1500</mtu>
>     </interface>
>   </interfaces>
> 
> The leaf never really changed value, but you would never know
> that from the NETCONF PDU responses.
> 
> After a system reboot, does the agent 'remember' that mtu
> was set to 1500 by the manager, so the initial <running/>
> config from NV-storage after the next reboot has an mtu leaf
> for eth1?

The value is stored in NV-storage, just like all other values set by
the manager.

/martin

_______________________________________________
YANG mailing list
YANG@ietf.org
https://www1.ietf.org/mailman/listinfo/yang