superfly · Senior Network Engineer · ✭✭✭✭✭

Yes you can https://www.itmanageworks.com/Network-Configuration-Manager.asp#:~:text=SolarWinds%20NCM%20can%20be%20used,health%20indicators%20alongside%20performance%20statistics.

Yes you can https://www.itmanageworks.com/Network-Configuration-Manager.asp#:~:text=SolarWinds%20NCM%20can%20be%20used,health%20indicators%20alongside%20performance%20statistics.

I don't know of one and I don't have CUCM to test. It seems these are normally managed by Solarwinds VNQM documentation.solarwinds.com/.../vnqm-adding-cisco-callmanager-devices-to-voip-and-network-quality-manager-sw17.htm But you should be able to write a custom device template if you have details on how to save the config…

I don't have a best practice for this. I use syslog alerting to give me the details I need.

Post up the conditions you are using in your alert.

That variable is for the email alert. https://solarwindscore.my.site.com/SuccessCenter/s/article/OLV-syslog-or-trap-messages-are-not-in-alert-messages?language=en_US Can you please share some screenshots on what you are trying to achieve?

I agree. NCM compliance report is your best bet.

You can't do it with the build in options. You could create a custom property and fill out the hardware details in it. You can then group on that custom property.

Have you tried to ping the device from the solarwinds poller that this node is on?

You could just add a description to the switch port that the AP is plugged into such as "Access Point". Then write an interface down alert that looks for the "Access Point" description. In your alert just show which node is alerting.

You could use the NCM compliance option to push out changes to only ports that don't have "switchport mode trunk" configured on them.

We too use SHA1 and AES128 to monitor PA's via SNMP 3. I use these setting in the GUI I'm monitoring PA-850's and PA-1410's

I remember those days well. Upgrading each individual product one at a time and step through the upgrades when to get to the latest one. Fun times

Check if the switch log is showing the link as going up/down. If it does, then the device will need closer investigation. Maybe a sleep mode or something like that.

You should invest in User Device Tracker. udt-datasheet.pdf

Sorry for the late reply. It is called Neighbor is Down

What are you using for your BGP Peer state change alert? The build in one? If so, by default that alert is applied to all nodes.

You should be able to do this with TACACS or Radius. Do you have either of these?

Do a snmpwalk on the device and find the right OID number.

Sweet! just mark this question as answered by marking the answer as the correct answer

Just be aware that changing the polling interval will put more load on the poller.

I agree with HerrDoktor, just write a script as to how you would do the process manually. That way it will work like a charm.

The article is explaining how to configure traps on the F5 which you can then send to the SNMP server. But if you are just wanting to do monitoring for now, just configure up the SNMP community on the F5 and get Solarwinds to poll it. Solarwinds has some F5 pollers built in such as device connections, device throughput,…

Nice one.

You could get around this my setting a view limitation to the page. There are a heap of view options even to the extend of just picking which nodes are to be represented on the page. Easiest to do though is to use some sort of wildcard so that when you add more nodes to a map, that they will automatically appear in the…

Unfortunately that information is not shown in the widget. But if you tick the highlighted option, you should get the info of who made the change in the email notification. (this works on cisco devices)

You can set how many config compares you can see by clicking the Edit button on the widget. But it will only go back as far as the number that are stored in the database which is set by the purge job (I have mine set to 6 months) The folder will store configs in there for 2 years as mentioned and that gets cleaned up by…

Have a look through the device configuration to see if there's double ups on it.

That's correct. I assume so it's only the alerts that have active alerts against it are shown.

Has the syslog receiver been configured under different IP addresses on the device?