SYSLOG
| Feature | Description |
|---|---|
| Logging output integrated with SYSLOG | Structured logging output can be sent to the SYSLOG deamon independently of the normal logging options. |
| Vendor-configurable messages | Logging messages can be customized with vendor-specific callback functions. |
| Facility, Class, Severity support | SYSLOG formatted and filtered message output is supported. |
| External SYSLOG API support | The default SYSLOG service can be replaced with vendor-specific callback functions. |
CLI
| Feature | Description |
|---|---|
| YANG-driven interface | The commands available are automatically populated based on the YANG modules loaded into yp-shell. The command line syntax is derived from the YANG syntax. |
| Config Mode | The config command is used to enter configuration mode. The YANG data nodes become the keywords and familiar CLI syntax is used to create, modify and delete configuration data. |
| Command Recall | Several familiar command line recall mechanisms are supported: history and recall commands to show recent command lines and recall a command line. control-P (previous line) and Control-N (next line) to scroll through the history buffer. The ! (bang character) to recall commands by line number or by matching the specified command string. |
| Context Sensitive Editing | The command completion text and available help text is context-sensitive, based on the YANG definitions, the current command mode or sub-mode, and the cursor position in the command line. |
| Command Aliases | Aliases are user-created commands that can be used to customize the command set and reduce typing. |
| The '?' Help Key | The ‘?’ (question mark) key can be used to get context-sensitive help for the keyword(s) or value that is expected next within the current command line. The ‘tab’ key is used for short help text and the ‘?’ key is used for long help. |
Role Based Access Control
| Feature | Description |
|---|---|
| Bypass Protection | The access control enforcement is integrated into the engine so no operations can bypass it and allow unauthorized access to configuration data. |
| IETF NACM Support | The (standard) IETF NETCONF Access Control Model is supported. |
| Yuma NACM Support | The (pre-standard) Yuma NETCONF Access Control Model is supported. |
| External ACM Support | An external (vendor-specific) access control model can be selected instead of Yuma NACM or IETF NACM, and easily integrated into the netconfd-pro server through a structured API. |
Automation
| Feature | Description |
|---|---|
| All CRUDX database operations | The built-in transaction engine automatically handles all Create, Retrieval, Update, Delete, and eXecution operations for all NETCONF standards and all YANG modules. |
| Smart XPath Caching | The built-in XPath handler automatically detects which database nodes are referenced in any YANG must or when XPath expressions, allowing XPath results to be cached safely with no development effort or doctored YANG files. |
| YANG Defaults Handling | The built-in transaction engine automatically handles all CRUDX operations correctly, even if default leafs and/or default non-presence containers are involved. |
| YANG features | Standard YANG feature statements can be used to easily manage optional data model sections across multiple product platforms and product versions. Separate feature sets can be specified for each platform and release. |
| YANG extensions | Standard YANG extension statements and structured APIs can be used automatically process vendor-specific custom language statements. |
| Full Database locking | Automatic support for standard all NETCONF database locking features. |
| Backup and Restore Management | Integrated backup and restore operations to simplify configuration management changes. Delete named backups with the delete-backup operation and view backup information in the YumaWorks monitoring extension to the standard ietf-netconf-monitoring module. |
| Transaction auditing | Configurable server transaction auditing with separate audit log. |
| Optimized Transaction Validation Handling | The built-in transaction engine automatically detects which commit validation tests can safely be skipped because the database nodes involved in the test have not changed value. This includes all YANG XPath expressions (must, when), all instance tests (min-elements, max-elements, mandatory, unique, key), and all edit operations. |
| XPath Expression Pruning | The built-in XPath handler automatically prunes false AND expressions and true OR expressions, which can greatly improve XPath validation speed. |
| YANG deviations | Standard YANG deviation statements can be used to easily manage data model diversity across multiple product platforms and product versions. Separate deviation files are automatically patched into the main module. |
| YANG user-defined types | Standard YANG typedef statements can be used to add any user-defined data types for reuse across multiple YANG modules. |
| YANG insert operations | Automatic order-list insertion management through full support for the YANG insert operation extensions to NETCONF. |
| Partial Database locking | Automatic support for standard all NETCONF partial-lock data sub-tree locking features. |
| Transaction management | Automatic support for fully recoverable database edits, using a 3 phase transaction model, providing separate Validate, Apply, Commit and Rollback callback interfaces. |
| Confirmed-Commit Handling | Full automated support for the latest standard NETCONF confirmed-commit operations. |
Data Retrieval Automation
| Type | Description |
|---|---|
| Streamed or Bulk Output | The netconfd-pro server is configurable so protocol messages can be streamed from data structures directly or buffered and sent in bulk transfer mode. |
| Subtree Filtering | Optimized NETCONF sub-tree filtering with streamed output. |
| Time-stamp Filtering | The if-modified-since parameter is provided all NETCONF retrieval operations to minimize polling overhead. The |
| XPath Filtering | Full XML Path Language (version 1.0) filtering with streamed output. |
| Event-type Filtering | Configurable event type filtering for notification delivery; only send notifications for desired event-types. |
NETCONF Standards
| Fully Supported IETF Standard | Description |
|---|---|
| RFC 4253 | Secure Shell (SSH) Transport Layer Protocol |
| RFC 4741 | NETCONF base 1.0 |
| RFC 4742 | NETCONF over SSH v1 |
| RFC 5277 | NETCONF Notifications |
| RFC 5717 | NETCONF Partial Locking |
| RFC 5789 | PATCH Method for HTTP |
| RFC 6020 | YANG 1.0 |
| RFC 6021 | YANG Data Types v1 |
| RFC 6022 | NETCONF Monitoring |
| RFC 6241 | NETCONF base 1.1 |
| RFC 6242 | NETCONF over SSH v1.1 |
| RFC 6243 | NETCONF With-Defaults Capability |
| RFC 6470 | NETCONF Base Notifications |
| RFC 6643 | Translation of SMIv2 to YANG |
| RFC 6991 | YANG Data Types v2 |
| RFC 7230* | HTTP/1.1 Message Syntax and Routing |
| RFC 7231* | HTTP/1.1 Semantics and Content |
| RFC 7232* | HTTP/1.1 Conditional Requests |
| RFC 7589 | NETCONF over TLS with Mutual X.509 Authentication |
| RFC 7950 | YANG v1.1 |
| RFC 7951 | JSON Encoding of YANG Data |
| RFC 8040 | RESTCONF |
| RFC 8071* | Call Home |
| RFC 8072 | YANG Patch |
| RFC 8341, RFC 6536 | NETCONF Access Control Model |
| RFC 8342 | Network Management Datastore Architecture (NMDA) |
| RFC 8525, RFC 7895 | YANG Module Library |
| RFC 8526* | NETCONF Extensions to Support NMDA |
| RFC 8528* | YANG Schema Mount |
| RFC 8639* | Subscription to YANG Notifications |
| RFC 8640* | Dynamic Subscription to YANG Events and Datastores over NETCONF |
| RFC 8641* | Subscription to YANG Notifications for Datastore Updates |
| RFC 8791 | Support for Structure and Augment-Structure YANG Extension Statements |
| RFC 8949* | Concise Binary Object Representation (CBOR) |
| RFC 9254 | Encoding of Data Modeled with YANG in the Concise Binary Object Representation (CBOR) |
* = partially supported
YANG Modules Included
| YANG Module Name | Description |
|---|---|
| iana-crypt-hash | Standard type for storing passwords using a hash function and features to indicate which hash functions are supported by an implementation, from RFC 7317. |
| iana-if-type | Standard YANG identities for IANA-registered interface types from RFC 7224. |
| ietf-datastores | Standard set of identities for identifying datastores for use with NMDA, from RFC 8342. |
| ietf-interfaces | Standard YANG definitions for managing network interfaces from RFC 7223. |
| ietf-inet-types | Standard YANG networking data types from RFC 6021. |
| ietf-netconf | Standard YANG data model for NETCONF protocol operations from RFC 6241. |
| ietf-netconf-acm | Standard NETCONF Access Control Model (NACM) from RFC 6536. |
| ietf-netconf-monitoring | Standard NETCONF monitoring data model and |
| ietf-netconf-nmda | Standard set of NETCONF operations to support the Network Management Datastore Architecture (NMDA) from RFC 8526. |
| ietf-netconf-notifications | Standard NETCONF Notification delivery with replay buffer and command interleave mode from RFC 5277. |
| ietf-origin | Defines an 'origin' metadata annotation and a set of identities for the origin value for use with NMDA, from RFC 8342. |
| ietf-netconf-partial-lock | Standard NETCONF |
| ietf-netconf-with-defaults | Standard NETCONF :with-defaults capability extensions to the |
| ietf-restconf | Standard RESTCONF protocol message artifacts from RFC 8040. |
| ietf-restconf-monitoring | Standard RESTCONF monitoring from RFC 8040. |
| ietf-yang-library | Standard YANG Module Library for RESTCONF and YANG 1.1 from RFC 7895 |
| ietf-yang-patch | Standard YANG Patch Media Type used by RESTCONF and DB-API from RFC 8072 |
| ietf-yang-types | Standard YANG data types from RFC 6021. |
| nc-notifications | Netconf Central YANG module for notification monitoring data model from RFC 5277. |
| notifications | Netconf Central YANG module for |
| toaster | Example SIL module. |
| yuma-arp | Netconf Central YANG module for Linux ARP management. |
| yuma-interfaces | Netconf Central YANG module for Linux interface monitoring. |
| yuma-mysession | Netconf Central YANG module for setting and retrieving session-specific session parameters. |
| yuma-nacm | Netconf Central YANG module for NETCONF Access Control, used as the starting point for NACM in RFC 6536. |
| yuma-ncx | Netconf Central YANG language extensions. |
| yuma-proc | Netconf Central YANG module for Linux /proc system information. |
| yuma-system | Netconf Central YANG module for NETCONF system management and notifications, which was used as the starting point for RFC 6470. |
| yuma-time-filter | Netconf Central YANG module for time-stamp based filtered of configuration data. |
| yuma-types | Netconf Central YANG module for extended data types. |
| yumaworks-attrs | This module contains abstract object definitions for the last-modified and etag XML attributes. |
| yumaworks-config-change | YumaPro common identities. |
| yumaworks-event-filter | YumaWorks YANG module adds configurable event type filtering for notification delivery. |
| yumaworks-extensions | YumaWorks YANG language extensions. |
| yumaworks-getbulk | YumaWorks |
| yumaworks-ids | YumaWorks YANG identities. |
| yumaworks-restconf | YumaWorks RESTCONF monitoring extensions. |
| yumaworks-restconf-commit | YumaWorks RESTCONF confirmed commit extensions. |
| yumaworks-server | Runtime access to netconfd-pro server parameters. |
| yumaworks-support-save | This module contains the get-support-save operation and the support-save-data yang-data structure. |
| yumaworks-system | YumaWorks extensions for CM maintenance such as the backup, restore, and delete-backup operations. |
| yumaworks-templates | YumaWorks configuration templates extension to edit-config. |
| yumaworks-term-msg | Notification event for terminal message feature. |
| yumaworks-test | This module contains data structures representing replayable test suites for specific use cases and YANG modules for use with yangcli-pro. |
| yumaworks-types | YumaWorks YANG data type extensions. |
| yumaworks-yangmap | YANG model mapping control block parameters for yangcli-pro. |