I am having a weird VLAN issue with NPM. Looking at NPM I noticed that my VLAN100 was the same as VLAN that was going to be handed off to me from another network. So I changed the VLAN100 on a few cisco switches to 105. NPM updated and showed that the devices where no longer on VLAN100 but did NOT create or show that VLAN105 exists.
I tried the normal trouble shooting steps
- Manually polled it
- Manually rediscovered it
- Waited for overnight maintenance to update it
Still nothing. I double checked that configure was right on the switches and saw that VLAN105 was indeed there. I looked back a few VLANs I had created fairly recently and noticed they did not update as well.
So I focus on the VLAN105 issue and did an SNMP walk and I can see the device is sending VLAN105 over OID .1.3.6.1.2.1.47.1.2.1.1.2.15. So I know Solarwinds is getting it. I then checked List Resources on the nodes and noticed that only VLANs with interfaces show up there, not sure why. I then checked the poller for VLANS and their only about 35 of our 75 switches showing up as being “assigned” to this poller. I was unable to manual assign them because it says “does not match”. These are normal 2960 etc.. Cisco switches nothing crazy. I do not know why Solarwinds will not use the poller on these devices.
Thinking it might be a MIB/OID issue I updated the MIB files as well, but it did not change anything
Still not sure what is happening with the VLAN but I am able to run a report called “cisco vlans” I can see VLAN105 and the other VLANs in questions.
I do not understand why Solarwinds is not showing this in NPM, I know the devices are sending it via SNMP and I can pull a report on Solarwinds and see the VLANs.
Can anyone help shed some light on this issue?
