Sonic-MGMT MDB extensions : OTN

doc/multi_asic/SONiC_multi_asic_hld.md

@@ -525,7 +525,7 @@ Below are the list of MIBs suppored by snmp_ax_impl.
 |1.3.6.1.2.1.31.1 |  | InterfaceMIBObjects | All namespace DBs|
 #### 2.4.7.2. Telemetry
 
-There will be a single Telemetry service and telemetry docker for the multi asic platform which will pull needed data from the DB's of asic namespace.  More details will be provided in a separate document.
+There will be a single Telemetry service and sonic-gnmi docker for the multi asic platform which will pull needed data from the DB's of asic namespace.  More details provided in [Management Framework document](https://github.com/sonic-net/SONiC/blob/master/doc/mgmt/Management%20Framework.md).
 
 #### 2.4.7.3. LLDP
 

doc/system-telemetry/dialout.md

@@ -19,7 +19,7 @@ It is useful in some scenarios. A few typical examples:
 
 # SONiC system telemetry software architecture
 System telemetry in SONiC supports both dial-in mode and dial-out mode. The DB client takes care of retrieving data from SONiC redis databases, while non-DB client serves data outside of redis databases. gRPC dial-out client is described in this document,
-![SOFTWARE ARCHITECTURE](img/dial_in_out.png)
+![SOFTWARE ARCHITECTURE](img/GNMI_Server.png)
 
 # Services provided in dialout mode
 gNMIDialout service is defined for telemetry in dialout mode. It has one streaming RPC: Publish. The message from client to collector reuses [SubscribeResponse](https://github.com/openconfig/gnmi/blob/f6185680be3b63e2b17e155f06bfc892f74fc3e7/proto/gnmi/gnmi.proto#L216) from gNMI spec, while the PublishResponse message is optional and skipped by default.

doc/system-telemetry/grpc_telemetry.md

@@ -67,7 +67,7 @@ For data not available in DBs, Target name "OTHERS" is designated for that categ
 
 # SONiC system telemetry software architecture
 System telemetry in SONiC supports both dial-in mode and dial-out mode. The DB client takes care of retrieving data from SONiC redis database, while non-DB client serves data outside of redis databases. gRPC dial-in server (gNMI server) is described in this document,
-![SOFTWARE ARCHITECTURE](img/dial_in_out.png)
+![SOFTWARE ARCHITECTURE](img/GNMI_Server.png)
 # gRPC operations for system telemetry in SONiC
 As mentioned at the beginning, SONiC gRPC data telemetry is largely based on gNMI protocol,  the GetRquest/GetResponse and SubscribeRequest/SubscribeResponse RPC have been implemented. Since SONiC doesn't have complete YANG data model yet, the DB, TABLE, KEY and Field path hierarchy is used as path to uniquely identify the configuration/state and counter data.