SNMP Monitoring Issue after OS Update from 16.12.4 to 17.12.4

[michael-bentley]

Hello Everyone, 

after an OS-Update from 16.12.4 to 17.12.4 on Catalyst 9300L, we are not able to get the same PRTG-Monitorung results.
For Example smart licensing:
we have four Sensors setup, but with 17.x we only get response to one Sensor.

ciscoSlaEnabled
1.3.6.1.4.1.9.9.831.0.6.1.0

TruthValue (INTEGER) {true(1), false(2) }
Feedback: 1

ciscoSlaRegistrationStatus
.1.3.6.1.4.1.9.9.831.0.6.1
INTEGER {notRegistered(1), registrationInProgress(2), registrationFailed(3), registrationRetryinProgress(4), registrationCompleted(5) }
Feedback: No such instance

ciscoSlaAuthRenewSuccess
1.3.6.1.4.1.9.9.831.0.7.5.2

TruthValue (INTEGER) {true(1), false(2) }
Feedback: No such instance

ciscoSlaAuthEvalPeriodInUse
1.3.6.1.4.1.9.9.831.0.7.4.1.0

TruthValue (INTEGER) {true(1), false(2) }
Feedback: No such instance

Could someone please advice.

[marce1000]

 - I would advice to 'snmpwalk' the involved MIBS again from their root , because sometimes the 'physical' OIDs change slightly ; and also look at the renewed correspondence between the variables and the OID's (if applicable)

 M.

[shambhu.kumar]

if you are using SNMPv3 , change auth from MD5 to SHA and check,

for example

snmp-server user ***  *** v3 auth sha ***** priv aes 128 **** access **

[balaji.bandi · Accepted solution]

is that only not working, nothing working at all ?

check the restrictions apply on the new version release notes :

Restrictions

https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/snmp/configuration/xe-17-x/snmp-xe-17-book/nm-snmp-cfg-snmp-support.html

[sir_yrwins]

I have the same problem . 
currently using version 2c 

[michael-bentley]

Hello sir_yrwins, 

i figured it out. after the Update, the whole licensing changed. the Sensors are no longer working or needed, since the checks are now running with a policy in the Software-Center