Skip to content

SONiC SNMP Design on Management Ports

Sumukha Tumkur Vani edited this page Apr 24, 2019 · 1 revision

SONiC SNMP Design on Management Ports

Rev 0.1

Revision

Rev Date Author Change Description
0.1 Qi Luo Initial version

About This Manual

This document is intended to provide general information about the SNMP Design on Management Ports

1. Functional Requirements

Originally snmpagent only expose front panel ports and neighbors. Now we are considering support management port in many SNMP oids:

  1. InterfacesMIB
  2. InterfaceMIBObjects
  3. LLDP* mibs

This effort will also make SONiC similar to other industrial NOS.

2. Redis schema design

There are two tables providing the information needed by snmp.

  1. MGMT_PORT_TABLE in configDB
  2. MGMT_PORT_TABLE in stateDB

There are several assumptions:

  1. At least one management port exists, but we should support multiple
  2. Management port could be oper down or admin down
  3. Backward compatiable: there may be no MGMT_PORT_TABLE at all in both DB
  4. Alias field is optional. eg. eth0 may have alias such as Management0

2. SNMP design

There are some concerns:

  1. We don't have counters for management ports. So use 0 as placeholders in SNMP
  2. We need to define a new port index range for management ports, as same as front panel ports, lags, or vlans.
  3. That file alias_map.j2 is there long ago before we have configDB. Nowadays, we could directly get everything from redis DB, so it could be removed. One thing you should be careful is that alias in confidgDB may be dynamic.
Clone this wiki locally