I have upgraded IOS one 3750 switch stack (two switch in that stack). I have upgraded from advipbase 12.2(25)SEE4 to advipbase 12.2(46)SE. From then SNMP has stopped working. i haven't done any changes on switch except for "boot" variable.Please help
Verify all of your SNMP configuration is still present. Check the output of "show snmp user" to make sure your v3 users are still there. What counters are incrementing is "show snmp" when you attempt to poll this stack? How do you have SNMP configured on this stack?
Without seeing your SNMP configuration or how you're querying the device, I cannot say for certain what the problem is. However, if you're getting SNMPv3 report packets back from the switch indicating that the credentials are wrong, it could be that the engine ID has changed.
Try removing, and re-adding your SNMPv3 user. See if that fixes it. If not, you will need to open a TAC service request with your "show tech password" so more detailed analysis can be done.
Changing your Engine ID back to what it was should resolve your problem, however, that requires a reboot.
If you don't want to change your Engine ID, then you'll have to recreate all of your users which were previously created under the OLD EngineID again.
Likewise, there's another "CISCO" Non conformance problem I noticed in the above EngineID:
The top bit set shows that the EngineID confirms to SNMPv3 specifications.
The first 4 octets (less the top bit) are the enterprise.id which is "9" and correct for Cisco Systems.
The 5th octet specifies how the remaining octets are to be interpreted.
0 - reserved, unused
1 - IPv4 Address (4 octets)
2 - IPv6 Address (16 octets)
3 - MAC Address (6 octets) <<- This is what Cisco has specified.
There are others, but I'll omit the rest of the list.
Notice the number of octets after the 03... there are actual 7 octest and not 6 per RFC3411 specifications.
00 00 17 E0 11 9C 81
MAC address 000017 Company TEKELEC
MAC address 0017E0 Company Cisco Systems
In other words, there's one too many leading octets which makes the Engine ID non-conformant per RFC3411 specifications and also causes for mistaken identity of a Cisco Systems product as a TEKELEC product!
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...