NETSCOUT InfiniStreamNG Reviews

To isolate whether we are getting the data from customers.

It helps us to assist our customers to isolate problems. If it is us who is having the problem, then we can use it to streamline the process.

It helps us to get to root cause more quickly. It is easier than setting different traps or captures on firewalls.

To know that packets are reaching our platform. If they are not reaching our platform, then we push it back to the customer. My job is bringing people to our platform. So, if they can't connect to it, then I haven't done my job.

The single pane of glass view seems healthy, and I can work with it.

It does help us with uptime and end use experience.

It's not able to communicate with our probes.

Sometimes, we can't access it.

It appears to be very scalable.

We need a new solution because of the visibility. As a telecom company, we needed to know that there is quality and access.

I think it was direct with NETSCOUT for the connectivity.

As far as my function, this solution helps a lot. It's a definitive answer if we're seeing those packets at all. We send the packet capture that we're seeing to the customer, then they have to say, "Oh, it's our problem." Then, I don't have to mess with it.

This solution has saved us hours (three to four) per problem when troubleshooting.

I would recommend getting the product. It is super easy to use for what I need, and it provides me visibility.

The primary use case is for troubleshooting customers' connectivity.

This solution provide us with increased visibility when conducting an IT deployment. We are able to look back in our history of logs and see what is communicating to what resources. That is very helpful. It shows visuals of what is being connected and communicated.

The ability to troubleshoot customers' connectivity has been very beneficial.

The tool has the ability to look back within a month's data. It is very easy to navigate within the tool and troubleshoot the problem, compared to other solutions that we've used in the past.

This solution helps us get to root cause very quickly.

We don't use the single pane of glass view. It's something that we are looking into since we do own it. We just don't use it at this time.

The tool has been great. We have never had an issue with it. It has been running for many years.

It is a great, architecturally designed product and very scalable for our solutions.

The technical support is good. Every time that we reach out to NETSCOUT, they have responded quickly. The engineers are very well educated on what they need to do to help us.

An issue that used to take days is now fixed within minutes to an hour.

The solution has helped to increase your application/network uptime.

Reach out to NETSCOUT. They give great demos with good overviews on the product and how it works.

I am overall pretty satisfied with the product. It helps with our troubleshooting needs.

We haven't got to the dependency mapping yet, which is in the nGeniousONE client, but we are looking forward to getting there.

We do pre-analysis using the OptiView of the networks. We also do what is called packet analysis, quick reaction. We go through the site using OptiView, doing data analysis, bring it back and use that. 

We also do the pen screens on migrated sites through Joint Regional Security Stack (JRSS), so when we do the pen screen installs, the ball feeds back to the regional cyber center and into the nGeniusOne. Then, we look at the nGeniusONE to do KPIs, data analysis, and see where the problems are with the network and give reports on it. We try to be proactive regarding the networks using this tool.

Proactive analysis is what we do. Quick reaction is my team's title. We use the tools for proactive analysis of network sites to see where the problems are and what layer the problems at.

It gives us feature view analysis of the network and pre-deployment. It provides the local site better insight by showing them what is going on with their network.

Once we get it online, we have greater visibility on the network and can see where the problems are at.

There are common tools that a lot of our sites use, and when we see the data coming in, we try to pick one (Citrix or SCCM). We can see where they are having problems using the tool, then start building a list of what the dependencies are, and if there is any commonality between this site and that site in the network problems.

We had a site trying to get from point A to point B. They were going through multilayer jumps on the network. We found out it that they didn't have their proxy servers balanced, so everything was going through one proxy server. We used OptiView to find that out.

• Visibility
• Analysis
• Solving future problems that we see, as things come up using nGeniusONE.
• Ease of use
• The performance metrics that it provides. They gives us a proactive analysis of the different applications which are being used on the network. This gives us a better view into where the problems lie.

The nGeniusONE solution is very stable. I don't think we have had any problems with it. It gives us a good view into the networks, helping out the sites that we deal with.

Only problems that we have had are fiber issues going into the TAPs or vSTREAMs, which are usually local site issues. 

It can be scaled with the Multi-Mode TAP solution. We have it big and little sites, e.g., we have a site with 14,000 users and another site with about 3000.

The initial setup is pretty straightforward. We have a build guide that we went through and started in our lab. We modified it, so it's pretty easy to do once you get going.

I worked with NETSCOUT on the deployment.

It has cut our troubleshooting down by days. Once we have a product in place, we show people examples of how it can streamline their troubleshooting process. Getting sites and the government to understand this, that is the biggest obstacle.

Go with NETSCOUT. Versus other tools out there, this is the best tool.

We are getting ready to get the solution for unified communication application performance.

The primary use case is for packet collection and analysis.

From a troubleshooting perspective, it allows us to quickly search all data TAP points in the network.

It helps our network engineers get to root cause quickly.

The most valuable features are speed and cost.

It give us visibility in the network where we wouldn't have it. We can use TAP to see the data and areas that we need to.

I love the single pane of glass view. I love the ability to look at all of our devices in one area, not having to jump around.

There is a timeout feature that we have been asking for awhile.

The overall cost of the solution needs improvement.

Overall, the stability is really good. It continues to get better with each upgrade.

Scalability is good. It seems to be very scalable for what we use it for.

The technical support has been very good for all the cases that we have had.

We didn't have a previous solution.

This solution has cut our overall troubleshooting time.

The price is a little high.

Ask for demos. Come to a NETSCOUT Engage conference. Try the product out.

We minimally use it for unified communication application performance.

We use it for monitoring subscribers.

It provides you with your Internet traffic volume, like Facebook, and where your biggest source of volume is coming from.

The single pane of glass feed still needs work. I do feel for what we have that it's fine.

I would like them to simplify the interface when you go into nGeniousONE. When you look at your interfaces, they should combine them all, and instead of looking at an interface, have you look at events. Combine everything into one view.

It is very rock solid. We hardly have any hardware issues.

To capture more with the solution that we bought, you have to buy another InfiniStreamNG, and there are only four ports in the back.

I don't directly interface with the technical support. There is another group which does that in my company.

In my environment, any installation is complex. There was a lot of dotting the i's and crossing the t's. Also, getting the maintenance to do the work for the install required scheduling.

We deployed in-house.

The solution is not great, but it is not bad. It is just a monitoring device. It is an okay tool, but it's not the end all, be all of all tools.

The engineers in our core use it a lot more than we do. They have seen a measurable decrease in MTTK and MTTR, plus a reduction in their troubleshooting time.