Comments
-
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,…
-
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?
-
add this ;F=Bandwidth as part of the variable. So it looks like this ${N=SwisEntity;M=Inbps;F=Bandwidth}
-
It uses putty in the background. But upgrade to the latest version, then it just tabs the session across the top bar.
-
Look in the top right hand corner to see as whom you are logged into solarwinds as. Maybe you got added to a group that doesn't have IPAM rights.
-
Not all devices show this. With Cisco switches and routers, you can get this information in the change email notification.
-
https://documentation.solarwinds.com/en/success_center/orionplatform/content/install-centralized-upgrade-primary-server.htm
-
Do a SMPWALK on the device and then look for the OID that has the info you are looking for.
-
Just make sure they all have this turned on.
-
You could go into All Settings, Manage Nodes. Then select all the nodes you wish to change. Then click on Edit Properties. Scroll down to Connect Profile. Select it and fill out the details. Then click on Submit.
-
In the above reply you mentioned you have added in the new interface to be monitored at both ends. Can you confirm that you've selected the correct interface? As for a copy of CPD neighbour so you can confirm the correct interfaces. You will need to delete the old link out of Atlas and select the 2 nodes in question. Now…
-
Yes if you don't currently know the IP ranges used, then run a job to collect all the IP ranges. Using "sho ip int bri | i Vlan" might be an easier option to use.
-
Do you have all the options ticked in Node Invetory?
-
You should be able to achieve this by using the compliance part of NCM.
