In some cases, the Customer can report that OID polling is not working from external NMS servers.

In such cases, Please confirm whether the FlexVNF is responding to that SNMP get-request.

Upon confirming that, External servers may issue with polling that OID.

shaffi@server:~$ snmpwalk -v 2c -c public -Osq 10.16.0.8  1.3.6.1.4.1.42359.2.2.1.1.1.1.2
iso.3.6.1.4.1.42359.2.2.1.1.1.1.2.15 25
shaffi@server:~$ snmpwalk -v 2c -c public -Osq 10.16.0.8 1.3.6.1.4.1.42359.2.2.1.1.1.1.2
iso.3.6.1.4.1.42359.2.2.1.1.1.1.2.15 25
shaffi@server:~$ snmpwalk -v 2c -c public -Osq 10.16.0.8 1.3.6.1.4.1.42359.2.2.1.1.1.1.2
iso.3.6.1.4.1.42359.2.2.1.1.1.1.2.15 36
shaffi@server:~$ snmpwalk -v 2c -c public -Osq 10.16.0.8 1.3.6.1.4.1.42359.2.2.1.1.1.1.2
iso.3.6.1.4.1.42359.2.2.1.1.1.1.2.15 36

The mib definitions will always provide the parent oid, 1.3.6.1.4.1.42359.2.2.1.1.1.1.2 for example “deviceCPUload”, the .15 is the deviceClientId “index” which needs to be determined by performing an snmpwalk on the parent oid as seen below.

 “Indexes” always need to be determined through an snmpwalk, either the NMS should have the ability to parse values obtained via “snmpWALK”, or you have to determine the index (through an snmpwalk) and populate this index while executing “snmpGET” (which needs the “index” to be populated along with the parent oid.