YumaPro Packages

There are several variants of YumaPro SDK in binary form. The installation is similar for all packages.

Packages are organized by release train (e.g., 19.10, 20.10, 21.10).


  • The release train identifier represents the year and month of the initial release, similar to Ubuntu.

  • This numbering will change in a future release to use the YumaPro SEMVER numbering instead. This is more compliant with Linux packaging conventions.

  • The <version#> in the package name is the monthly version number

  • The first monthly release is in October (e.g., 23.10-1)

  • A snapshot release will be identified by its snapshot sequence (e.g. 23.10-1.1)

In most cases the latest version of the SDK should be used.

Binary Packages

There are several binary distributions available, depending on the license.

Refer to this feature comparison chart for details on the Basic, Core, and Advanced Feature Sets.

Within the YumaPro download site, there are several folders with the same structure.

  • There is a directory for each release (e.g. 21.10-3).

  • There is a directory for each platform in this directory (e.g., u1804). Select the package based on the required CPU architecture (e.g. amd64).


  • Basic Feature Set

  • No Posix Threads


  • Core Feature Set

  • No Posix Threads


  • Advanced Feature Set

  • No Posix Threads


This is an evaluation version of the SDK:


  • Basic Feature Set

  • With Posix Threads


  • Core Feature Set

  • With Posix Threads

  • With yp-client Support


  • Advanced Feature Set

  • With Posix Threads

  • With yp-client Support


This is an evaluation version of the SDK:


This package contains the full SDK with the Simple Network Management Protocol (SNMP) supported.

  • Advanced Feature Set

  • No Posix Threads

  • SNMP Protocol


This package contains the full SDK with the gNMI and gRPC protocols supported.

  • Advanced Feature Set

  • No Posix Threads

  • Contains the yp-gnmi server distribution

Debian Packages

The Debian Packaging system is supported. Files with the ".deb" extension are Debian packages.

RPM Packages

The RPM Packaging system is supported. RPM packages are provided for selected platforms that do not support Debian Packages. Files with the ".rpm" extension are RPM packages.

Supported Linux Platforms

Each Linux-specific binary package is specific to a Linux distribution and CPU type.

The list of supported distributions and CPUs change over time. The current support is listed above, refer to Supported Distributions and Architectures

EVAL Version Restrictions

The evaluation version of YumaPro packages has some usage restrictions.

EVAL Version Expires in 100 Days

Most programs in the yumapro-sdk-eval and yumapro-pthreads-eval packages will stop working 100 days after the build date of the package. Binary packages are updated every month, so it should be possible to download a new package version before the 100 day limit is reached.

Error: EVAL version has expired

If the server is started with --log-level='debug4', then the version and build date will be printed at the start of the log file.

Example build-date:

version: 23.10-5-EVAL (23.5.0)
build-date: Feb  5 2024

EVAL Version of netconfd-pro Accepts 500 Requests

The evaluation server will stop accepting client requests after 500 NETCONF requests and 500 RESTCONF requests. The server will not shut down. Instead, an error will be returned for any client request.

  • The server must be manually restarted by Control-C or a signal.

Example: rpc- error returned when limit is reached

<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply message-id="500"
  <error-message xml:lang="en">request limit reached in evaluation version</error-message>

Installing YumaPro SDK Binary Packages

Download the Correct YumaPro Package

In your browser navigate to https://www.yumaworks.com/dld and login with the credentials YumaWorks provided to you.

Select a Package To Download

The root directory contains a number of directories, depending on your YumaPro license.


Documentation is available online:

Install the Package

On Debian systems:

mydir> sudo dpkg -i yumapro-sdk-21.10-3.u1804.amd64.deb

On RPM systems:

mydir> sudo dnf install yumapro-sdk-21.10-3.fc34.x86_64.rpm

To quickly test the install run the server to just display its version:

> /usr/sbin/netconfd-pro --version

 Starting netconfd-pro...
 Copyright (c) 2008-2012, Andy Bierman, All Rights Reserved.
 Copyright (c) 2012-2021, YumaWorks, Inc., All Rights Reserved.

 netconfd-pro version 21.10-3-3fcf


To see which files are installed in more detail refer to Appendix: Installed Files at the end of this document.

Installing YumaPro SDK from Source Code

To install YumaPro SDK from source files make sure you have installed the developer versions of the External Packages listed previously. Navigate to the YumaPro top level directory. You will find the file "README" that describes how to build YumaPro SDK and the build variables available. Below is an example. It is best to build, install, and if needed uninstall using the same build variables.


mydir> sudo make install EVERYTHING=1 USE_WERROR=1 DEBUG=1


If you have Server source code (e.g., yumapro-server2) you will not have access to the yangcli-pro/yp-shell source code and as such EVERYTHING=1 will not work.

You should: substitute EVERYTHING=1 for the features you want to include such as WITH_RESTCONF=1.

Refer to the YumaPro Source Code Guide for more details.

Uninstalling YumaPro SDK

If you need to uninstall YumaPro SDK see the article: How do I remove YumaPro SDK from my system?

Removing Files Not Needed By The Server

Installing yumapro-sdk and yumapro-pthreads SDK packages includes host platform developer tools that are not used by the server on a runtime platform. To remove these files see the article: Removing Files Not Needed by the Server