netconf/yang capable device question

[khgrant]

Hi,

When a device is netconf capable and has a full yang model – how does that change the service template model?

Currently with our CLI based NED – we use a lot of XML/Yang based service templates.

  Thanks, JA

[khgrant · Accepted solution]

Hi JA,

Whether a device is NETCONF or not has no bearing on the templates. The template will always reflect the device model NETCONF or CLI. For a device which switches from CLI to NETCONF based NED will also require an updated template to support the newer device model which will most likely be quite a bit different than the CLI model.

-Dan

[khgrant]

Hi JA,

once vendors converge to natively support standardised YANG models, e.g. L3SM, open-config, etc. , template creation in multi-vendor projects may become easier, because we can use the same templates for e.g. cisco and juniper.

Still, new features only 1 or the other vendor has requires additional template creation.

Mike

[khgrant]

Mike,

And remember that IETF portions and vendor specific portions have different namespaces, which makes co-existence very simple.

These are all NSO differentiations against the competition.

Regards, 

Roque