SAI object interface to Redis database, as used in the SONiC project
Branch: master
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
SAI @ 8a29259 Fix compilation issues in stretch docker with gcc-6.3 (#426) Feb 22, 2019
debian install SAI extension header files into /usr/include/sai (#412) Jan 24, 2019
lib Update SAI pointer (#414) Jan 31, 2019
meta Add support for fdb_event MOVE and check fdb event oids (#420) Feb 15, 2019
saidiscovery Update SAI pointer to latest master (#408) Jan 18, 2019
saidump Update SAI pointer to latest master (#408) Jan 18, 2019
saiplayer Add support for fdb_event MOVE and check fdb event oids (#420) Feb 15, 2019
saisdkdump Update SAI pointer to latest master (#408) Jan 18, 2019
syncd Fix compilation issues in stretch docker with gcc-6.3 (#426) Feb 22, 2019
tests [vslib] add missing port attributes for virtual switch (#419) Feb 15, 2019
.gitignore [.gitignore]: Add more files in .gitignore file (#396) Dec 6, 2018
.gitmodules SAI 1.3 changes (#327) Jul 3, 2018
LICENSE Add LICENSE file Jul 5, 2016 Added SAI dump support to syncd (#199) Jul 31, 2017 Update Jan 10, 2018 Initial commit Mar 22, 2016 automake: Removing Darwin support & Setting foreign strictness May 10, 2016 [mellanox|ffb] use system level warm reboot for Mellanox fastfast boot ( Jan 7, 2019
package.cfg packaging: Adding debian packaging (debian/*) Mar 23, 2016

BroadcomBuild Status CaviumBuild Status MellanoxBuild Status P4Build Status

SONiC - SAI Redis - sairedis


The SAI Redis provides a SAI redis service that built on top of redis database. It contains two major components, 1) a SAI library that puts SAI objects into the redis database, 2) a syncd that takes the SAI objects and puts them into the ASIC.

Getting Started


Before installing, add key and package sources:

sudo apt-key adv --keyserver --recv-keys 417A0893
echo 'deb trusty main' | sudo tee -a /etc/apt/sources.list.d/sonic.list
sudo apt-get update

Install dependencies:

sudo apt-get install redis-server -t trusty
sudo apt-get install libhiredis0.13 -t trusty

Install building dependencies:

sudo apt-get install libtool
sudo apt-get install autoconf automake
sudo apt-get install dh-exec

There are a few different ways you can install sairedis.

Install from Debian Repo

For your convenience, you can install prepared packages on Debian Jessie:

sudo apt-get install libsairedis syncd

Install from Source

Checkout the source: git clone and install it yourself.

Get SAI header files into /usr/include/sai. Put the SAI header files that you use to compile libsairedis into /usr/include/sai

Get ASIC SDK and SAI packages from your ASIC vendor and install them.

Install prerequisite packages:

sudo apt-get install libswsscommon libswsscommon-dev

You can compile and install from source using:

make && sudo make install

You can also build a debian package using:

fakeroot debian/rules binary

Need Help?

For general questions, setup help, or troubleshooting:

For bug reports or feature requests, please open an Issue.

Contribution guide

See the contributors guide for information about how to contribute.

GitHub Workflow

We're following basic GitHub Flow. If you have no idea what we're talking about, check out GitHub's official guide. Note that merge is only performed by the repository maintainer.

Guide for performing commits:

  • Isolate each commit to one component/bugfix/issue/feature
  • Use a standard commit message format:
[component/folder touched]: Description intent of your changes

[List of changes]

Signed-off-by: Your Name

For example:

swss-common: Stabilize the ConsumerTable

* Fixing autoreconf
* Fixing unit-tests by adding checkers and initialize the DB before start
* Adding the ability to select from multiple channels
* Health-Monitor - The idea of the patch is that if something went wrong with the notification channel,
  we will have the option to know about it (Query the LLEN table length).

  Signed-off-by: user@dev.null
  • Each developer should fork this repository and add the team as a Contributor
  • Push your changes to your private fork and do "pull-request" to this repository
  • Use a pull request to do code review
  • Use issues to keep track of what is going on