ONF Stratum for Cassini - Read Me

2. Stop Taish server: systemctl stop taish-server.service
3. Pull and re-insert the big line-cards from both switches (on both sides)
4. Start taish server: systemctl start taish-server.service
5. Check taish logs until this message appears: docker logs -f taish-server :
DEBUG [int tai::nel::HW::controller_status()@1866] [module(1)] auto traffic state:
3
DEBUG [int tai::nel::HW::controller_status()@1868] [module(1)] auto traffic err
history: 0x0
DEBUG [int tai::nel::HW::controller_status()@1870] [module(1)] RX_LOS: false
DEBUG [int tai::nel::HW::controller_status()@1872] [module(1)] RXI-LOSI: false,
MLD-LOL: false
6. Start Stratum
7. Check port status: ps
Stratum TAI Interface and TAI Wrapper
TAI Interface
The TAI interface provides an abstract interface between Stratum data source and the actual
implementation.
This interface provides these function definitions for Stratum data source:
Get module, network interface, and host interface IDs
Get current input and output power
Get/Set TX laser frequency of a network interface
Get/Set target output power
Get/Set modulation format
TAI Wrapper
A TAI Wrapper is an implementation of the TAI Interfcace.
There are two ways to manage optical transponders via TAI.
Native C/C++ API (tai.h)
gRPC TAI Shell (taish.proto)
In Stratum, we are using the taish.proto to create a gRPC client to communicate to TAI Shell.
The Native C/C++ API is still work in progress. For more information, see taish_client.cc
PHAL integration
According to the current PHAL architecture, the following interfaces were implemented for
TAI.
TaiOpticsDataSource