UDP-Notif Collector

The yangcli-pro program supports the IETF UDP-Notif Protocol feature implemented in netconfid-pro. This is part of the new DRAFT level YANG Push 2 features.

UDP-Notif UDP Port Assignment:

• There is no 'well-known' port assigned for this protocol.

• This implementation uses a default UDP port determined by the --collector-port CLI parameter.

A Publisher (could be a NETCONF server) configured to send UDP-Notif messages will simply send UDP messages to the Collector. The yangcli-pro program will handle message state for multiple publishers using the IP address and publisher ID from the received messages.

Warning

This feature is under development and will be unstable until supported in a production release train.

Temporary Limitations

The initial release (24.10T-6) does not have the YANG Library information for the sender. This data is not saved or preconfigured offline in this release.

• The publisher can be pre-loaded by connecting the default or named session to the NETCONF server for the publisher.

• Multiple publishers can be supported at once if they are using the same YANG module sets

Collector Configuration

The following CLI parameters are available for UDP-Notif Collector configuration:

• --collector-address (default 0.0.0.0)

• --collector-enabled (default false)

• --collector-port (default 4334)

1. This feature has to be enabled by setting --collector-enabled=true in the configuration or command line.

   • This is not required if the collector command is used to start the Collector.

2. If the default listen address (all IPv4 addresses) is not desired, then the --collector-address parameter must be configured.

   • This parameter can be set at run-time if the collector command is used to start the Collector

3. If the default UDP port number (10832) is not desired then the --collector-port parameter must be set.

   • This parameter can be set at run-time if the collector command is used to start the Collector.

4. Connect to the NETCONF server for the publisher to have all the YANG modules available.

5. Incoming events will be delivered to the application the same as if they were received from a NETCONF dynamic subscription.