Comments
-
Hey Gareth ... the current global IT issue prevents me logging in to details how we have done this, but the short answer is yes. The longer answer is that so long as you can craft a bit of SWQL to extract the data then you can definitely present it via a modern dashboard. One of my long-standing bugbears with SW is/was…
-
Hi Scott... you don't say whether this is using Network Atlas (under a deprecation notice] or Intelligent [not really] Maps. But yes, absolutely this can be done in either tool. For either tool it is a matter of manually linking nodes. With NA you just don't want to run the 'connect L2/L3' bits, and with IM it is a matter…
-
I guess that's a starter for 10 but "how" do I leverage powershell scripts? Is there a document somewhere that shows us a 'how to'?
-
Hi ... Yes, you have hit the bug. The pop out doesn't 'pop' anymore and the option to select your map name format is simply missing. After much hassle and a few choice words from me a SW employee confirmed this: "is due to a bug in the product that has been investigated by our Development Team under the ticket OO-34535."…
-
I access SWQL exclusively in our environments via RDP sessions and have never had an issue with Ctrl-A, C, and V'ing in to our out of the environment or even between tabs or windows in the same RDP session. Be that part code or whole code. This sounds very much like an issue with the way your RDP sessions are managed or…
-
Are you on version 2024.2 by any chance? If so, it is a known bug and 2024.2.1 [due any day] will fix that. If not that version, then go to one of your maps and click the edit button top right of that map widget. Then scroll to the bottom of the popout widget and select your 'Map Name Format' to be what you want/need it to…
-
This sounds like the same issue we were (and continue) to face. The solution for us was to delete the mapcache files - see this KB…
-
Never spotted that node selection was persistent in manage nodes and having just tested it in 2024.1.1 it doesn't work there either. I don't have 2024.2 yet to determine if NCM has stopped. However, what I'd like is for manage nodes to have the multi-filter option that NCM has.
-
No. They are shown to you via a on the fly SNMP get query. @"vinay.by" confirmed what I thought. I was 99% certain the non-connected details are not stored in the DB and therefore you can't create a report for them
-
I might be wrong, but surely if the interface isn't discovered, then it won't be in the DB for a report to be able to extract it. When you do a List Resources, it takes one of two options. Either it is doing an SNMP discovery at that point in time, or it is using a cached discovery from that node having recently been…
-
I spend a fair bit of my time re-writing alert names, trigger action names, etc because the tools admin guy doesn't bother. Unfortunately it is me that ends up 99% of the time trying to track stuff down or fix bits and it is a nightmare locating the associated action with generic/default names. Also, just how many times do…
-
Can you share the SWQL code you used - or a screenshot of it and the error would help?
-
Do the OIDs appear in syslog traffic? If so, I'd suggest a rule and alert built through OLA. Try this for starters if you haven't done that before: https://documentation.solarwinds.com/en/success_center/la/content/lm/lm-alerting.htm
-
You don't say what make/model the end nodes are? But, some off the cuff thoughts/questions: * Have you enabled monitoring on the newer interfaces at both ends? * Are these ticked on, on all nodes? * If yes to both the above, how long since they were added? * What's your topology polling period? * Have you done a…
-
There will be limits to what you can monitor, but yes you can, just configure up and use SNMP on the ESXi and then configure Solarwinds in the same manner as you would for monitoring a switch or router, etc... Also…
-
Then you need to raise a ticket for support to investigate. It could be the ciphers, etc you are using are still too high/new for the SW update.
-
I understood you were talking about Meraki API - we do the same. To get AP details you have to dive into the wireless tab. The approach you take, as you have found out, does nothing. There is also a Feature Request, here: [mention:81aa5c7d88a746b381a458424f93810d:fb5d84b10a5745448a7a45dafc1faa43] that you could go and vote…
-
You can enable 'Hubble' in the Log Adjuster. On pages where it works [NB it doesn't work on all] you will see an additional link appears. Click that and it takes you to a page of queries, where you can then work out which one you need. Full details in the KB…
-
You don't actually need to delete and re-add. What you do need to do is "tidy up" the unknown ports afterwards. With Cisco nodes, this could happen after a simple reboot if you don't have snmp ifindex persist configured on the node. Why? Well Ciscos love to change their ifindex, which is what SNMP [in simplistic terms]…
-
OK, so you've done the hard part (in my opinion) and found the OID and created the UnDP. What you now need to do is identify the differences between the node in service and the one that isn't. So if Node 1 (for eg) shows a result of 0 for your HA OID and the failover has a different result, and on failing over those…
-
Hi ... is there a question in there, or are you replying to a now locked 9yr old thread?
-
Have you tried viewing via the 'Wireless' link under 'Network' in your dropdown menu? From there you can narrow down via vendor or one of a dozen other filters, or search out specific AP names or IPs etc: Once you locate the AP you want, click on it to drill into the details - which, by default, opens into a new tab.…
-
@"NetDev_sol" We seem to have hit this in one of our deployments. Can you detail the steps please?
-
Even I can follow this one - nice job Antonis.
-
Sadly, when SW moved away from the old standalone application they removed a lot of the functionality that was available for free and in the "all new, all dancing" replacement they ask you to pay to get some, not even all of the same functionality. BTW - you don't have to mark my answer as helpful or right, but it is…
-
Do you have the default built in free Log Analyser or are you paying for the "enhanced" OLA? If the first, then this is probably expected behaviour as the free version does not have the power / capability / functionality to deal with live trap alerts on a guaranteed basis. If you are paying for OLA, then as Adam says, get…
-
If all other things are equal, i.e. same subnet, same rules, etc then you need to be looking at the server and the connections from it. Are the two VMs on the same host? If not, then check out the host. Do you have a.n.other host you can move the failing VM to?
-
You will need to build a SWQL [FYI: it is recommended that you use SWQL and not SQL for scripting in Solarwinds] query around a UnDP. The UnDP will need to be able to see the OID: 1.3.6.1.4.1.9.9.198888.0.1.12 which should return as 'cLHAPrimaryUnit'. If you do an snmp walk, the current primary unit will return the value…
-
You can certainly create a report to show all your audit stuff but be warned the list can get sizeable so best to try and restrict in some manner. As an e.g. I discovered only a week or so back that SW audits group access - as in anybody that clicks on a group name. But the way it phrases it makes it sound like someone is…
