2650, SNMP Security access violation

[Anton Elita]

I have "snmp-server community" configured with a community name. No "IP authorized Managers".
Still I receive "snmp: SNMP Security access violation" when I try to snmpwalk.
Firmware revision : H.08.53

What could be the problem? Thanks.

[Georg Tresselt]

I guess the problem is your No "IP authorized Managers". You should enter the hostname/ip address of the box from where you snmpwalk.

[Anton Elita]

I've tried to introduce this host (and, even the whole network) in "IP authorized Managers". As well, I've tried to restart the switch. It does not help.

[Les Ligetfalvy]

With the scant details, we can only guess at what the problem may be.

Do ALL the community strings in your SNMPWalk utility match ALL the strings set in the switch? Are you sure they match? Check again.

Are you sure you set the authorized managers correctly?

What utility are you using to walk the MIBs?

Have you tried another utility to query?

[Anton Elita]

For sure, ALL community strings match.

the problem is that I have another 2650, configured absolutely the same way (IP address is the only different thing). The have the same firmware.

here are the snmp-relevant config lines:
snmp-server contact "me@my.com"
snmp-server location "my_location"
snmp-server community "my" Operator

and there are no ip authorized managers.

this config works on one switch, and does not on the other.

what could I do?

(warm and cold reboots already tried).

[Anton Elita]

Please help me! I need snmp acces to this switch and I have no more ideas what could I do!

If this is necessary, I will give ssh access to the switch!

[Kell van Daal]

Operator doesn't have access to all MIB's on the switch. Maybe you get the access violation on those MIB's?
Maybe you can try:

snmp-server community my manager restricted

for read access only. Or for read/write:

snmp-server community my manager unrestricted

Hope this helps.

[Anton Elita]

no. it did not help.

again, I have two switched with the same firmware and the same configuration. when I snmpwalk one switch -- it is ok, when the second - it is complainging about snmp security access violation. I've even tried snmpv3 -- the same result, though all the parameters are ok.

[Les Ligetfalvy]

You say that you have two switches with the same firmware and the same configuration so one would expect them to behave the same. I suspect that you only think they are the same and that something is being overlooked.

Do a showtech on both switches and compare them in detail.

[Anton Elita]

ok, i've found the diference. the order, in which vlans appear in running config.

on the first (snmp-good) switch:
vlan 1
vlan 3
vlan 2
vlan 5
vlan 4
vlan 10

on the second (snmp-bad) switch:
vlan 1
vlan 2
vlan 4
vlan 5
vlan 10
vlan 3

ALL the rest of configuration is COMPLETELY the same.

so, up to me, there is a bug in firmware.

the testing I've done: - I've taken the snmp-good switch and configured vlans on it in the order they are configured on the snmp-bad switch. ANd, it starts to complain about snmp security violation.

again, i've checked that ALL the configuration is the same, the difference is the order I configure vlans.

Hope, this information is helpful.

PS: by the way, why vlans appear in the order they are created, and not in the numbering order?