PI 2.2 goes into config mode and issues snmp-server host x.x.x.x traps RWcommunityString command

[gabor.rozsa]

Hi,

I have a problem that based on the wireshark capture I did during the inventory collection I spotted the following:

Cisco3850#enable
Cisco3850#terminal length 0
Cisco3850#terminal width 0
Cisco3850#terminal length 0
Cisco3850#show snmp host
Notification host: 10.10.10.10.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Notification host: 10.10.10.11.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Notification host: 10.10.10.12.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Notification host: 10.10.10.13.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Notification host: 10.10.10.14.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Notification host: 10.10.10.14.udp-port: 162.type: trap
user: myROcommunityString.security model: v1

Cisco3850#config t
Enter configuration commands, one per line.  End with CNTL/Z.
Cisco3850(config)#snmp-server host 192.168.10.100 traps myRWcommunityString
Cisco3850(config)#exit
Cisco3850#

First and foremost: why PI enters configuration mode and configures a new SNMP server as a trap receiver without any asking? 

Secondly if it does this automatically why the configration is not saved? 

Thanks,

Gabor

[AFROJ AHMAD]

Hi Gabor,

this is some unexpected behavior , ideally this should not happen.

try to delete and re-add the device or at least re-enter the credentials in PI .

are there any special characters in your community string ?

you have defined both RW and RO  in  PI while adding device ?

is it happening for any particular device or all  ?

Thanks-

Afroz

[gabor.rozsa]

Hi Afroz,

I agree with you this is completely unexpected behaviour. There is nothing extra with the community string I use and I do provide both RO and RW community when adding devices to PI.

I could only spot this issue with the new Cisco 3850 series stackable switches.

Gabor

[AFROJ AHMAD]

Hi Gabor,

have you tried this ::

try to delete and re-add the device or at least re-enter the credentials in PI

Thanks-

try to delete and re-add the device or at least re-enter the credentials in PI - See more at: https://supportforums.cisco.com/discussion/12542946/pi-22-goes-config-mode-and-issues-snmp-server-host-xxxx-traps-rwcommunitystring#sthash.b1VKg9M3.dpuf

[gabor.rozsa]

Hi Afroz,

My real problem is that the device has the 'snmp-server host x.x.x.x traps' command in its configuration. To remove it I'd need a change (long love the change control). 

But I don't have any reason not to think Prime would do this with any other C3850 if it did with one during the syn phase of device addition.