davidmaltby · Principal Architect

Yes, definately there will be no EOL/EOS runtimes required. Instead, the major requirements are on the .NET 6 Runtime and the ASP.NET Core 6 Runtime.

I can't guarantee that our scripting action will support Powershell, but we have already done the research on using Powershell and it is a top candidate for the scripting languages supported. Please voice your interest, if this is a highly desired item. 

I assumed that it crashed at or around 5pm? Weren't you the customer who NTA would crash for at that time on two different occasions? It looks like something slams your SQL Server at that time. We have a second SP in QA right now. Maybe you can get some diagnostics to Tech Support? And also get us a list of the SQL…

I would set the values for compression and data retension down to their minimum values. To set them as such, go to the NetFlowGlobalSettings table and change the following rows to the following values: RetainUncompressedDataInMinutesDefault = 16 (minutes) CollapseTrigger2InHours =2 (hours) CollapseTrigger3InDays=2 (days)…

Tech support has assisted with rolling back to 2.2.1. I'd call in a ticket for that. As for reducing the size of the database, where is most of your data, based on row counts? Are you really just talking about orphaned data? If so, to get a list of monitored detail tables, you can run the following T-SQL: SELECT DISTINCT…

It looks like there was a deadlock on your system. Can you try again and see if you are still seeing the deadlock? If so, then maybe we need to look at the SQL Server processes and see which T-SQL statement that is blocking the Configuration Wizard.

Jeff, We have tested a fix for one customer and it allowed him to run 27 hours, instead of the few hours like you are seeing. Not sure if his new issue is related or not. It appears to be different and we're investigating that now. There is one thing that you can play around with to help mitigate the issue... In the…

The sniffer trace indicated that the sFlow packets are using sFlow v2. It there a switch or firmware upgrade to have it start sending sFlow v5? NTA only supports sFlow v5. Thanks,

Yes, although it wasn't easy for me to find either. It is in the customer portal under "Additional Components". There select the NPM link. On that page, it is called Orion-to-EOC Network Atlas Map Conversion Utility NEW Thanks,

Ghostcorps, The others on this thread seem to indicate that they got it working. Maybe on the box with Orion NetFlow module, can you use WireShark and get a sniffer trace capture? See if there is UDP traffic coming in on the port that nprobe should be sending to. If not, then you know that your problem isn't the Orion…

Ahh... no problem. Since you've attached the sniffer trace, I can have my team take a look at this and we'll get back to you. Things are a bit busy in development right now, so it may be a while. Thanks,

The language in the swdebug.log is for developer and tech support use only. To explain it all would require a lot of explaination into the inner workings of the NTA service. Thanks, David

Oh, I didn't release you were crashing. I though you were just hanging and/or killing/canceling the Configuration Wizard process before it completed. I'm not familiar with this error, I'll have to look it up and get back to you.

We hear you. SP2, which is so close to being released, has a NTA Setting to turn off/on NetBIOS resolution and it is turned off by default.

If you could call into support and use WireShark to capture a sniffer trace that contains the flows from these switches and send us the PCAP file, then we can see what is happening. Make sure to indicate the IP addresses of these two switches so we can identify them in the sniffer trace. Thanks,

In development, we just tested NTA with a Foundry device and were able to see the traffic from it. Can you open a ticket with Tech Support, so that we can get a sniffer trace from you? Make sure to take the sniffer trace on the machine with the NTA collector. If we have that, then we figure out what the problem is. Thanks,

If you're available tomorrow morning, I'll get on a GoTo meeting with the Tech Support rep and yourself to resolve this. Sorry about all this trouble that you're having. I have not seen any other cases where a customer's migration aborts like this. Thanks, David

Yes. It is a bug that we discovered last week. It was too late to make it into SP1, so we're including it in a quick SP2 release. For now, you'll have to have all the NTA sources for a node enable in order to not lose traffic, like you were seeing. Thanks, David

I am not sure yet, but I suspect that this issue may be occuring on a particular T-SQL statement. That statement involves both the FlowCorrelation and IPAddressGroup tables where one was a subquery of the other. For one customer's diagnostics (dmoore), I see that the FlowCorrelation table row count is 24,065,243. Can any…

Please note that I'm looking for row counts of databases if you've haven't made it through the Configuration Wizard for NTA 3.0 upgrade. If you have completed the Configuration Wizard, then the NTA service will start collasping the Summary2 data and hence will have a smaller row count.

Can one or both of you look for errors in the log files that are in the following directory: C:\Documents and Settings\All Users\Application Data\SolarWinds\InformationService The errors in there should explain what the reason for the timeout was, hopefully. Thanks, David

The size difference in your database is actually not a trade secret. In NTA 3.0, we would never perform shrinks on your database. In NTA 3.1, we do. In SQL Server, when disk space is freed up from deletions in the database, the space is not recovered by the filesystem. Doing so, would take time for SQL Server and so they…

I'm sorry. I took the wrong approach here. But the best thing to do here. (Even if you hadn't run the above T-SQL which updated the CacheExpiration dates on all those rows), is to run the following query... INSERT INTO NetFlowAddressToResolve (IPAddress, Reason, Timestamp) SELECT IPAddressSort, 0, GETDATE() FROM…

It is not that it can't be done, but allowing Orion to give up its account credentials to an EOC would pose a security risk. There would need to be extra measures to prevent rogue EOC installs or other software from consuming those account credentials. 

Over the weekend, I believe I've discovered what the issue was by performing some testing of a large lab database. It appears to be due to a bug in the previous version of NTA which caused the NetFlowSummary2 table to never collaspe its data. In NTA 3.0 upgrade, the Configuration Wizard creates some indexes on the Summary2…

There is one other thing that we could try, that I forgot about. In the NetFlowService.exe.config file, there is a line which looks like the following: <processingPool threadsPerProcessor="10" packetQueueSize="0" /> Now that I think about it, we didn't have the 10 thread limit on thread pool size in 2.2.1. This actually…

To this point, you're an isolated issue. We still need to figure out the cause of your crash. I've provided an image of the performance counter that I'm talking about. I am not convinced yet, that this isn't just an issue where SQL Server can't keep up with NTA. We probably have a slight performance problem with the NTA…

If you have deleted the data from the tables contained within those filegroups, then performing a shrink on those filegroups should reclaim the space. You can do this from Management Studio, by right clicking on the database then Tasks\Shrink\Files. This brings up the "Shrink File" dialog. Then in the Filegroup combobox,…

I'll get in touch with Tech Support now.

So the values must be messed in somewhere for these dates. Can you look in the FlowCorrelation table and look now at what the dates are for the CacheExpiration field? (All 7 million should be the same since we ran the query) Furthermore if you open the NetFlowCorrelationState table, what value is in there? What is the…