Uh... Let's clear up a few things first:
1. If you're polling using Solarwinds, there are only a few things you can hit:
- The sc0 interface on the switch.
- The defined interfaces on the rtr (incl loop).
So if you're getting a response from Solarwinds indicating that something is responding to SNMP (with a string of public) on the "VLAN" interface - you're talking something defined on the router.
2. Therefore, this whole "layer 2" and "layer 3" thing is kind of a red herring. Let's talk router.
3. Just configuring a "new" SNMP string with the appropriate command, like this:
snmp-server community IBMRAWKS ro
or whatever only ADDS to the strings already defined. It doesn't REPLACE what already exists. You must clear the previous SNMP string using the "no" command - standard IOS. Like this:
no snmp-server community public ro
And BTW: From one IBM'er to another, ITCS guidelines dictate that you're supposed to secure the equipment from screens using an ACL. Like this:
snmp-server community LOUANDSAM ro 10
with
access-list 10 permit 1.1.1.1
access-list 10 permit 2.2.2.2
etc.
4. You should also screen your switches using IP Permit lists (I do for both SNMP and telnet). [Easy to do on Cat 5000 and Cat 6000's using CatOS.]
5. Don't forget to save your config.
6. I've been working on a "hardened" IOS for both internal and external routers, switches, etc. Since you're doing Solarwinds sweeps, perhaps we can touch base and exchange information? If you have a Sametime id - can you drop a note with it? Be nice to share information.
