Prime Infrastructure 2.0 - SNMP location lost when collecting

[Bart Mars]

Hi,

We've detected strange behaviour from our Cisco Prime Infrastructure. We did a upgrade from 1.3 to 2.0 last friday and all looked good and well. However, we noticed that our SNMP locations were missing from our network devices. With some research, we saw that the SNMP locations were in the startup-config, but not in the running-config. We also noticed that our LMSuser (which we use for identifying that Prime is logging into the switch) changed something in the config:

Oct  2 22:00:50 192.168.57.220 7566: Oct  2 22:00:49: %SYS-5-CONFIG_I: Configured from console by lmsuser on vty1 (172.20.250.1)

So we set the SNMP location on a couple of switches to test our theory. And the next evening when Prime does its collection routine, it removes the SNMP location again.

Is this a bug or is this a new setting in Prime?

Thanks in advance!

[AFROJ AHMAD · Accepted solution]

Hi Bart,

This is the BUG :

PI 2.0 corrupts device config by doing snmp set for location after sync

CSCuj09556

Symptom:

Prime Infrastructure 2.0 corrupts a managed devices config by doing an SNMP Set for location after a device sync.

Conditions:

Workaround:

Add/sync  the device with RO community (to read the system location) and after  that, change the community in PI to RW with following snmp view:

snmp-server view SYS_exclude system.6.0 excluded

snmp-server view SYS_exclude iso included

snmp-server community

Thanks-

Afroz

[Do rate the useful post]