Does NSO support to add device with netconf subsystem parameter

[sparrow109]

Hi,

Our device uses the same port 830 to ssh netconf-yang and open-config. By identifying the difference, the netconf subsystem parameter is used. 

To connect netconf-yang, we use ssh -p 830 localhost -s netconf-yang

To connect openconfig, we use ssh -p 830 localhost -s netconf-yang-open-config

Does NSO support to connect the netconf subsystem parameter?

Thanks!

[rogaglia]

First, the standard "SSH Subsystems" are govern by the IANA registry and neither "netconf-yang" nor "netconf-yang-open-config" are valid. From standard NETCONF RFC 6242 point of view, the subsystem should be "netconf".

Complete list of standard subsystems can be found here:

https://www.iana.org/assignments/ssh-parameters/ssh-parameters.xhtml

I do not believe NSO supports to change towards non-standard subsystems with our standard NETCONF/YANG NEDs. That said, you should talk to your sales rep if a non-standard NED could be possible or a feature request to make subsystems names configurable.

Native devices models or OpenConfigs are YANG schemas for device configuration where both could travel via the same standard NETCONF SSH connection/subsystem (or RESTCONF or  gNMI BTW). I found interesting (although it breaks the standard) that your device is basically providing a clean separation between the two worlds and forcing you to chose between one or the other. In general we do the same in NSO NEDs by selecting the YANG modules you will compile but the device is not aware of the choices every client makes.