stuartd · Senior Dogsbody · ✭✭✭✭✭

I don't know about the Op's reasons, but my organisation love to have everything documented and/or put into a process. So being able to export ones alerts into a readable flow charty type of document is a real boon. Secondly, when bidding for new business, having a clear "this is what we can offer when monitoring your kit"…

I am not a coder, and 99% of mine are acquired and edited. Try having a look through the 'content exchange' and see if anything is there that you can adapt. This one: Active alerts with acknowledge notes might be a place to start. 

I'd love to see a master list of where 'which' log file type is. I don't have your answer but I, like you start with c:\porgramdata\solarwinds\logs >> then sub-dive according to need. That, or I open a ticket with support and ask them. Maybe that's a thing... open a ticket and ask them to provide a master list of log file…

I also want to add, that we have 1000's of groups and maps and sadly the import tool (introduced, IIRC, in 2024.2.1 or .0) does not work. I expect it to be a WIP as it is the first release but for us but it simply doesn't work. The first issue I spotted is that the node names appear 'under the node' and appear to be…

If I understand you correctly you are saying that you display your Network Atlas maps based on the name of the group they are in. So if you have a group called ABC and you have a map called ABC then the widget displays it? This is because when you edit the widget it shows this: So then yes is the answer. You can also do…

I'd say a modern dashboard is perfect for this idea. Create a custom SWQL code block with whatever details your company requires and then use an MD to display nodes and interface alerts side by side, or one above the other. I think your biggest challenge will be in how to extract the data. A quick scroll through SWQL…

Ahh understood and yes I do follow. In which case you'll only ever get a "sense" of the latency, etc by monitoring specific links. If you have Netflow and the relevant nodes are configured to send that data to Solarwinds, then you could use that to extract the conversation(s). Other than that, then Adam's suggestion is a…

Above and beyond others that have already posted we also use (and I like): * Access - as in 'what protocol is used to access the node' * Accessibility - as in the where and what to access a node. This usually would say something like "CheckPoint GUI 80.10 from x.y.3.50" * Client / ClientSite / ClientPrefix - these 3 all…

Follow this: https://solarwindscore.my.site.com/SuccessCenter/s/article/Turn-on-and-use-Hubble?language=en_US and then you'll be able to see and extract the query yourself.

Unless I'm getting the wrong end of your question, then so long as you have the specific interface(s) that connect these two nodes together, then you can go to the specific interface summary pages for each and see traffic, etc... Alternatively you could set up a specific Perf Analysis project, add the distinct interfaces…

The newer GUI versions are, IMO, just plain horrible to work with. The fact that you can no longer select a Custom Property as a group (we heavily use CPs for client site names), just makes it even worse. Do what I do. Use the original. In the top right hand corner of the new Manage CPs page, click the three dots and then…

I don't have the answer you are after, but as a suggestion have you tried configuring a custom report using your SWQL, and have that sent on a daily [or whatever] schedule?

My first thoughts are: * why do you need to backup 5k nodes daily? On the presumption you are following some form of Core, Distribution, Access model, then a better approach would be to only backup the Core on a daily basis and the Access weekly or even less frequently. I'll wager the config on a lot of the nodes never…

So we do a similar thing for interfaces. We call it an interface flap alert and we want to know if an interface has triggered more than x times in the last y minutes. This is a custom SWQL alert and for your scenario all you need to do is adjust from interfaces to nodes. There are two parts. There's the hard coded part…

Thank you Marc - as per my response to Chad I will have a chat with our automation chap. The reason I mention alert is due to the trigger that alerts have for assigning/changing CP's and the fact that they have all the functionality in them for scheduling/triggering/etc.

Thank you Chad. I will need to get a hold of our automation chap to assist but this sounds like a way forward.

OK. In which case, the only way to do that with NPM is you need to monitor ALL the interfaces.

Understood that you don't have NCM, but you didn't clarify what you want to achieve? Is it a list of ALL interfaces, whether monitored or not? Or is it just a list of monitored interfaces? If the last one, then it would be useful to the community if you accept my first response as the answer.

The top screenshot is device pollers - I'm talking about UnDPs.

I know I can either add a node via the UnDP 'tool' (very painful process) or I can 'Assign pollers' from the manage nodes / entities but this is about looking down the line after the UnDP has been created and initially assigned, to a new node of same vendor/etc gets added, but also gets missed for adding the UnDP to. And…

If I understand, you want a report to show all the interfaces (ports) in your network. This should be straightforward enough BUT it will only show the interfaces you have discovered [aka that are monitored]. To put it another way, if you have 48 port switch and you only monitor 5 interfaces, then you will only get those 5.…

But fix what issue... You haven't provided any information for folks to advise on. Show us the query? Tell us what you've tried? (step by step)

Almost certainly due to weak / old ssh ciphers in your version of Solarwinds and your end devices are running newer versions. The answers are: * Update to 2024.2.1 to get latest ciphers built in. * Downgrade end node ciphers to weaker ones. Or you can read this: SSH - Connection Refused Cipher Updates - An F.Y.I. where I…

It looks to me as if you are running a SQL query? The advice from Solarwinds has always been (where feasible) to use a SWQL query instead using the API. Their reasoning being is that the DB Schema can and does change, but the API (ie using SWQL) will just reference the new or renamed tables. At least, that's my…

It sounds like you are talking about creating a device poller so that when you go to the node details page it shows OS versions, etc... I don't have an answer for you, but this sub-forum is dedicated to NCM and your query would sit better in the [mention:5ead648511384d829046fcc7d3f86b50:23b05a61c3e5445190d9bfa00453bce4]…

I'd suggest a feature request posted here: Network Configuration Manager (NCM) Feature Requests would be the best way forward with this. 

I've just posted about this here: SSH - Connection Refused Cipher Updates - An F.Y.I. This is absolutely one o a combination of three issues: * You aren't on the latest Solarwinds or have the buddy drop installed * Your FortiOS is v7 and higher * If 1 is not true (i.e. you are on 2024.2.1) then are you are using an edited…

What tweak(s)? It would be useful if you can tell us what you are looking to achieve, or what your template looks like now, or even if you are even successfully backing them up at all? We have various models newer and older than yours that we are backing up, so I might be able to help.

There have been some issues with the device pollers in recent versions of Solarwinds as they were broken in one of the recent upgrades. If you are on (IIRC) anything from late 2023 to 2024.2 then at least one or more of those versions was affected. It might be as simple as you need to update to 2024.2.1 which I can confirm…

TLDR: The answer is to either use the default template or add the two lines above to your device template.