03-31-2009 07:39 AM
Upgraded 2 3550-24 with 2 3560E-24 migrated config over to new switches
and I am unable to communicate with them via snmp v2 with the RO string. I have tried
several programs including LMS 3.1. I have removed the strings and re-added them from known
good configs still nothing. I did have an ACL on the strings and removed it with no luck.
I started out with 12.2(46)SE and upgraded to 12.2(50)SE with no improvement.
Solved! Go to Solution.
03-31-2009 09:23 AM
The SNMP portion looks good. I did notice your logging configuration might be problematic. How were you verifying the debug output? From what I could tell, you would have to have been running it on a VTY with "term mon" enabled.
03-31-2009 08:30 AM
Try running debug snmp packet to see if the SNMP requests are making it to the switch. It could be that udp/161 is blocked between your manager and this device.
03-31-2009 08:45 AM
Hello Jclarke,
I have enabled debug snmp packet and nothing is showing up in the log. I know UDP/161 is not being blocked on the LMS server I have no issues talking with the other network devices via SNMP v2. Should I try debug SNMP receive?
Thanks
03-31-2009 08:49 AM
If debug snmp packet is not showing anything, then you are not receiving SNMP packets. It may be that the filter is beyond the LMS server, and just in the path to this device.
You could try a sniffer trace at each hop in the path to see where the packets are stopping.
03-31-2009 08:55 AM
The LMS server is on the same vlan/subnet as all the switches it's just these 2 3560E-24's. any other ideas?
Thanks
03-31-2009 09:03 AM
Please post the show run from an effected switch. There was a bug in 12.2(46)SE where SNMP would not respond if you were using DHCP on the Fa0 port. However, that was fixed in 12.2(50)SE, and you would have still seen something under "debug snmp packet". Therefore, I suspect a possible configuration issue.
03-31-2009 09:09 AM
03-31-2009 09:23 AM
The SNMP portion looks good. I did notice your logging configuration might be problematic. How were you verifying the debug output? From what I could tell, you would have to have been running it on a VTY with "term mon" enabled.
03-31-2009 09:27 AM
Let me try it again using the term mon. any other suggestions? or captures wanted?
Thanks
03-31-2009 09:48 AM
Not at this point.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: