IBM SevOne Network Performance Management (NPM) Reviews

Sometimes we get requests that a customer needs CPU or disk or memory performance or utilization graphs. We add those servers or devices into the tool and then we can generate the graphs and provide them to the customer.

Customers also ask us to create alerts. The tool generates alerts for CPU utilization when it is close to, for example, 90 percent utilized.

It is deployed directly on servers as well as on virtual machines.

One of the benefits is its ability to transform raw network performance data into actionable insights. That's one of the keys for us. When something goes above a threshold, we can see it in the alerts and take action. Likewise, we can see graphs and reports and we can judge what to do before something goes wrong.

Some of the teams that are using our graphs from SevOne, and the capacity team that uses the data it generates, are able to make decisions before something bad happens.

We use SevOne to monitor a multi-vendor network. We have a lot of different kinds of devices in our scenario. We have Cisco switches and network devices from various vendors. The alerting and reports that we can generate help us see if something is not the way it should be.

• Reports
  
• Alerting

These are the most valuable features for us because the customers in our company primarily want to see performance and usage graphs, and they are always concerned with the alerts.

Another useful feature is that SevOne gives you real-time insights into your network performance. It polls every five minutes. That is important for our customers because there are some network teams that are always monitoring their networks. There is an option for setting the polling frequency to less than five minutes. That means you can monitor your infrastructure faster and we do that for some of our devices.

And the data collection functionality, using SNMP protocol, is good. It's doing its job.

I'm not really sure if this was the software's fault or a server issue, but a couple of years back the disks were failing on our SevOne physical server every month and the server would go down. The secondary server took over from the primary until the disk issue was resolved. That was annoying.

I've been using IBM SevOne Network Performance Management since 2013.

It is resilient. If the server goes down, all the data and functionality is taken over by a secondary server. In our scenario, there has been no data loss.

You can add as many devices as you want, but I think you need to buy more licenses to add more devices. But scalability is not an issue. We have seven to eight clients and we monitor more than a thousand devices for each one.

There are no new clients in the pipeline, but if another comes along, we will definitely recommend SevOne to them.

The SevOne support team is very good. Whenever you have a strange issue or a big issue, something you have never seen before, when you reach out to them they are always available. They are very fast and always help us.

Positive

I deployed SevOne on a virtual machine a couple of years back. The deployment was easy and straightforward. The installation wizard helps, giving you all the details of what is happening. There was no confusion. And it was fast as well. It took roughly two hours.

Someone from our deployment team helped me. He told me to just "apply this, do this, do that," apart from what the wizard showed me. I believe he was in touch with the SevOne guys.

I can't say anything specific about the investment in the solution because I'm not given that data by my company. But our clients are still using this solution after many years with our company. That is a good indicator that they must be getting a good return.

There are other tools that we have used, like eHealth from CA. It also gives you graphs but we don't like that tool. We like SevOne. It is older than SevOne. We are using it for some clients that have had it from the beginning, so we cannot remove it. But eHealth has bugs. With SevOne, I don't have any complaints.

Definitely go for it. The interface is user-friendly, and it provides so many reports and alerts. It gives you a good, total package. And the support team is also very cooperative.

I can't think of very much that the solution lacks. Everything looks okay to me.

Our primary use cases are for network alerting and reporting.

The out-of-the-box reports helped speed up its time to value. It's very important to make the tool usable, so you can prove to management that money was spent wisely.

SevOne has improved my organization by taking us to a single pane of glass for alerting on the network reports. For NOC, they only have a single pane of glass they have to look at.

It can be very thorough and very complete if you buy all of the appropriate modules and you have enough licenses to cover all the gear on your network. Some of the niceness is the flexibility of the tool and what you can do, but some of the complexity is due to that flexibility. The tool can be very complex depending on what you want to do, but that complexity makes it flexible to see things in different ways.

It enables us to detect network performance issues faster and before they impact users. Looking at IP SLA metrics and seeing that something has exceeded the baseline before users actually call up and say that there's a problem.

I've found Data Insight to be the most valuable for mining the data that the tool collects.

Without data insights, it's really hard to mine the data out of the NMS tool. Data Insight makes it more flexible.

The network data collection has been very flexible for us. It's been thorough in areas that were lacking. They have a team that I've worked with to add other pieces to it. So if it's missing something out-of-the-box, they work with me to add it. I was able to collect that data. It's not perfect, but it's pretty thorough.

The ability to assess the comprehensiveness of the solution's collection network is important. I wish they had some things in there that they don't for us to sunset some of our homegrown tools, but it's not a showstopper.

Its collection abilities cover multiple vendors' equipment but that's lower on our priority list for our deployment. We mainly have one vendor for the majority of our environment but we do have some others, so it is nice having the ability to look at other vendors.

The out-of-the-box reports and workflows for automatically helping to understand what is normal and what is abnormal in our network are very poor if you only have NMS and that is the only portion of step one that you own. DI makes things a lot better. 

DI actually lets you get to the data in a way that is easy to view without DI getting the data out of NMS. NMS is great at harvesting the data and storing the data, but it's terrible at giving managerial style views to see the data, as well as reporting is hard to mine the data in the reports. It's a very old-school feeling. DI puts a modern view on top of the tool, allowing you to get to the data in a cleaner fashion and faster data mining.

We use its ability to edit and customize out-of-the-box reports. It's been easy to edit, but I've run into some bugs. I'm focused solely on DI because NMS reporting is not very good. DI is a newer tool for them. I've run into several bugs that have slowed me down. It's easy to use other than I've run into the occasional bug that has caused problems.

I've given the firewall team reports that only look at their gear versus NOC is able to see all gear. I have done team-specific views. 

It provides continuous analytics of our network. I find it helpful, and I believe other people on my team find it helpful to be able to see all of the stats in a single tool. They can see an alert and then they can see the stats for the gear that was associated with that alert. I think that is very helpful.

NMS has several areas for improvement. It should be more user-friendly inside of NMS for some of the functionality in there. It's been getting better the last version or two, but there have been bugs in there whenever I've gone to new versions. 

There have been some features that were advertised that I would have that weren't actually there yet. They were kind of there, but even their tech support team didn't know how to use them because they were so new, and the documentation wasn't very thorough around those bleeding-edge features.

I have been using SevOne for two and a half to three years. 

It is very stable. 

Scalability has been good. It apparently has the ability to scale very broadly as long as you have the resources to deploy more instances of the tool, it is very nice on that front. The scalability is good.

We have around 30 users. Some of the users are in network operations and network engineering. Obviously, the network management team and some management use it to be able to get their visibility into how the network looks.

We have essentially two people managing the environment and they're both in the network management team. It eats up a fair amount of their time in order to really take advantage of what the tool can do.

It is used pretty extensively for the gear that we have deployed it on. We bought it for the monitoring. There are plans to expand, to include more of our network gear in the tool. I have no idea of the timeline, but I would say it's used pretty extensively. The gear that is modeled on there is only mounted on SevOne. We've taken off of all of our other monitoring to get down to a single pane of glass.

I would give their tech support very high marks. Tech support has been very helpful.

The initial setup was straightforward. 

I don't know that we've ever finished the deployment. The tool is flexible so we're always trying new things. But getting it off the ground and running and alerting, I would say took about a month and a half to two months.

We deployed it in parallel to our existing monitoring tools and then took devices out of our existing monitoring tools as we proved that they were inside of SevOne.

We did not use an integrator for the deployment. 

I have seen ROI. 

Be careful of how the licensing works. From the administration side of things, I am a propeller head. I do not know anything that has a dollar sign in it. Those are numbers I do not know.

We looked at large, standard NMS tools as well as open-source options. 

My advice would be to plan exactly what you're trying to get before you do the deployment and do as much research as you can before you go through the week-long training session that they give you with the initial purchase. There was a week-long training that we got as part of the initial purchase, but the training came before we even had the tool onsite. So I was not able to ask questions intelligently.

With flexibility comes complexity, and the other is going to be management. See everything that SevOne can do, they are going to ask for a lot. So you need to get management understanding what the tool can do with what you have deployed right now. Don't promise them the world. Filter down what management's expectations are.

I would rate SevOne a seven out of ten.

We use SevOne to manage about 10,000 network devices on our system. We monitor those devices with all the performance data, run reports, and see alerts. We have a manager of managers that sits above SevOne that actually displays all of our alerts, does some correlation and other things. We also provide some maps and reporting.

SevOne also enables us to detect network performance issues faster and before they impact end-users. We were monitoring the load balancers on our backstage passes for access to the network. And we can see, it went from around 3% to around 75% over a couple-of-week period where they had to send in all the remote access and change everything. SevOne really did a number for us, during the pandemic, of isolating which load balances were overloaded with users working from home. So that right there, was worth its weight in gold, because the management created all these reports for load balancers, for access for remote workers, and that's all they focused on, for a couple of months. So that was nice.

It has saved at least 50% because if we're just using ping and a couple of other tools, you can't really see that, all these devices went down at the same time, that segment, or that peer.

Data Insight reporting tool is the most valuable feature. They came up with it a couple of years ago. The most pleasing factor is the dark theme. You don't have a white background. It has templates that you can create for all kinds of reports that you can hit on the fly. It has a much better printing of the reports. If you want to send PDFs to people, the reports are actually decent. Whereas for years, the old architecture of the PDFs was rubbish and even our customers said, "We have to manipulate your PDFs because they all have bad margin breaks. SevOne fixed that a couple of years ago with the new Data Insight. It's fantastic. I would say the reporting of the new Data Insight is my favorite feature. 

We also have the Wifi Controller feature and we're starting to turn that up. That's going to be nice because we're going to be able to monitor wifi. Our group used to monitor wifi, about 10 years ago, maybe even longer, and then they took it away and gave it to Cisco Prime LAN. And they come to find out that Cisco Prime wasn't monitoring it as well as they thought. So we got some quotes from SevOne for a wifi solution, and now we're implementing that. We're excited about the wifi solution.

We also use NetFlow and Databus. It's not that new, maybe five years old. But everybody's starting to get on board where we just send our raw data to scientists. They correlate all the data into how they want to report on it. Those are a few of the new things that we like to use.

I would rate the comprehensiveness of SevOne's collection of network performance and flow data a ten out of ten. I've used Concord and eHealth before this. I used HP OpenView for 15 years. Right now, SevOne is top-notch for me because it's an all-in-one package, and it's easy for the operator to learn. If I can learn it, anybody can learn it. But it has a lot of features underneath that. I am one of the admins, but we have some really top-notch programmers that go in and get that in-depth data. I operate as an admin, I help people out, create policies, and everything. But when it comes to the in-depth stuff, I leave that to the scripters. I'd rather just click on the GUIs and let somebody else scrub through the comments.

It's extremely important that SevOne's collection abilities cover multiple vendors' equipment. We have F5 Firewalls, Palo Alto load-balancers, intrusion protection devices, ClearPass servers, Aruba, we got it all. SevOne has a good process. We also like the certification where we get the MIBs and the OIDs from the customer or the vendor. And they say, "We'd like to monitor this CPU key performance indicator." Or "These HC octets and the interfaces. If it's above 80% we want an alert."

With the vendors, we just take a new vendor like Aruba, they'll want to monitor the fan speed or whatever, we'll take that OID and send it to SevOne. Their certification team is top-notch. They have a 10-day turnaround, but for us, they always provide it quicker. We tell the customer 10 days but we sometimes tell the customer too, that they're always quicker. And they always are.

The process is easy. As long as the homework is done ahead of time, either by us or the vendor, we just provide SevOne with the OIDs, they provide us with a file, and we import it into SevOne. We apply it to the right vendor and all our key performance indicators are there. It's wonderful.

We're also just starting to monitor software-defined and streaming telemetry-based networks in our environment. We got a new manager and he's been pushing it. He loves SevOne. We use Data Bus, NetFlow, and we're doing the telemetry stuff. I don't really understand it, but we're working with some scientists on ride controls, to send them that data. When they started doing this, I told them "You better get some sharp people down here." And they did. 

The manager is a great manager. He's holding everybody's hands to the fire, and I got a bunch of burn marks on my hands. But we're getting progress. SevOne was great, but we weren't taking it to the next level. And other people were coming up with other tools, saying "This tool does this." And we said, "Well, SevOne does that, if you want us to do a proof of concept." So we've been doing all these proof of concepts.

In the old days, reports had nice baselines and stuff that we could use for deviations. With the new Data Insight reporting tool, now we have percentiles that we could have in the old ones, but when you had a reporting tool that wasn't that good, you're not real excited about baselines and stuff.

With Data Insight, we can see baselines and deviations. We can decide how many deviations we want to view. We can do percentiles. We can do time over time, and the graphing in which you can separate the graphs. Data Insight is a game-changer for reporting. 

You can look at the reports and it's just a picture, so your brain can say, "Whoa, that's out of normal. There's the baseline and there's somebody making a backup in the middle of the day or something." So, the out-of-the-box reporting is very nice. Every time they upgrade us, they upgrade Data Insight and they add more templates that their team has decided that the crews could use out there. They're great. I always see the new templates and I just copy it all over to my environment and change the names so people don't see.

The dashboards are fantastic. I don't use them as much as I should. I just started creating some. I'm doing it in the new Data Insights. You can customize it to your customers. We don't do much of that because we don't have a big enough crew to manage all the users out there, there are hundreds of users. And if we had to be their reporting gurus, we'd be hung up all day long, just clicking on reports for people. 

I love the dashboards because you can put it all in the front. You can have heat maps on the CPU. If you want it to have a dashboard for all of F5 you could just have the dashboard for F5 and say, "Hey, we're having CPU problems. I just want a heat map. Show me something red that I can click on and go troubleshoot." It's so nice.

There are a lot of pain points. My main problem is that we don't have a high availability system. There are 20 peers. We're going to lose the end-of-life appliances that are old. If we lose a peer and it doesn't come back, we lose all that data. The reason we don't have high availability is because it's double the charge.

I wish there was some way that we could just get a snapshot of our system so that if one of our peers failed, we could go through the process and get it back to where it was. If we built another peer, and it took us four days to build another peer and get all the firewall rules and everything it would be nice when it came back if we had a snapshot that said, "Hey, peer two, that died." Then can we just slap all that data onto the new peer two and have all that historical data, as opposed to just importing it new, and it wouldn't have any data from the past. That's kind of a pie in the sky thing. But I would like some kind of backup system.

I've been using it for about eight years now, which is actually a long time. Usually, our applications come and go. 

The stability is dynamite. We are having some issues in our VM world, where we don't have visibility to our peers that are out in the VM world. Sometimes our teams might get a peer locked up or whatever, but it's never SevOne's problem. When we had our appliances, it was rock solid. There were no issues with SevOne. You had a disk array and if you had a disk that went bad, you just ordered the disk and dispatched somebody out. I'd give them a positive as far as stability.

Scalability seems to be incredible. We're adding peers one after another. We got the wifi solution and then we just added four new peers, two on the east coast, two on the west coast of the United States. We just order more peers and get them built. SevOne sends us the OVA files. We install it, we open up a case of SevOne. They help us bring it into the cluster. And boom, we've got another whole peer ready for another 1000, 2000 devices. So its expandability is very nice, much better than OpenView and the other things I worked on.

We previously used HP OpenView. That was my thing. I liked it because of the maps, you could have all kinds of cartoons and stuff in the background. That was fun for the graphic artist people. SevOne just blew HP OpenView out of the water.

We had four servers and around 10,000 devices out there and we just couldn't handle it, it was just too much for HP OpenView. HP OpenView stagnated because I used it for about 15 years, and the last five years it looked like it was dying on the vine, with the support and stuff. They changed systems and our people in charge of budgeting and projects, decided not to go the route that HP suggested and went the SevOne route, which I'm glad they did.

I was the sidekick for the setup but it seemed to be pretty easy. I had installed, from setup, HP OpenView systems with four D80 servers around the world. The SevOne environment was pretty good. We were small at the beginning.

Without the planning and everything, just when we got the devices and turned them up, it took around a week or two. We were in our own little lab, testing.

We had a database and we were taking Cisco devices first. Once we had all key indicators identified that they wanted to monitor, we did it. Then we slowly brought in each vendor with the certified files and checked them as we imported them. It was a good plan.

We've used SevOne any chance we can get. We call them in all the time. They have a really tight relationship with my boss. They bring them in whenever there are questions on anything. And their support team is fantastic. We open up calls and get our tickets taken care of nicely.

SevOne is definitely earning its money because different departments are requesting SevOne monitoring for certain situations. And it's extra-billing, of course. I never see any of it, I just see the devices and we add them and we charge them. So they're bringing in money. 

They're getting their money back.

They were constantly looking at other products. I don't look at them. I don't even have time to think about other products. They looked at NerveCenter but NerveCenter is different. My customer is constantly looking for other replacements that are cheaper. Everybody's looking at their budget and asking "How can we get cheaper?" 

At one time they suggested ThousandEyes. It's much cheaper and easier. Well, they had ThousandEyes monitoring a little section of their network and they realized that there's no way ThousandEyes can do it. It's just too big of a network. ThousandEyes can do little stuff but overall, I work on changes all the time and I do my SevOne stuff, and the guy does his ThousandEyes stuff and his stuff is not quite right. 

My advice would be to read the PDFs they have and then look at the videos on YouTube. That's what I do. I'm not a voracious reader, but I go to YouTube a lot. 

I would rate SevOne a nine out of ten.

We are using this solution for monitoring the network for performance and availability. We have about 25 SevOne peers that are monitoring almost 8,000 devices. These devices include routers, switches, firewalls, etc.

On any outage, SevOne is pretty quick to send an alert. We've got an operations center that consumes the alert and sends it to the device owners so that they can minimize the time of impact of that alert. Such outages happen at least once a month, and whenever there is a real outage, SevOne is the one to detect it.

The comprehensiveness of SevOne's collection of network performance and flow data is very good. For NetFlow, I would rate it a 10 out of 10 because it collects everything that NetFlow delivers. You can also customize the reports to show only what you'd like to see or what your customers would like to see. For network monitoring, I would rate it a nine out of 10 because you can collect all the information and slice and dice that information in whatever manner you feel necessary to consume that data. We've got an operations team that subscribes only to the alerts. So, we've got tier two and tier three people who are looking at reports, and they slice and dice those reports however they like.

Its collection abilities across multiple vendors' equipment are really good. If we don't have an SNMP OID for a particular vendor, the only thing that the architects at my company need to do is to supply us the SNMP OIDs and/or MIBs. We send these to SevOne, and they certify it. We can then install it in the SevOne system, and it'll start monitoring that equipment. Its collection abilities are important because we've got multiple vendors in the network, and each specialty, such as a firewall or a router, has different collection needs. We're able to meet these specific collection needs based on the device types.

For our operations, the dashboard is very important because that's how our customers are making day-to-day and long-term strategic decisions, for six months to a year, about their network. We're not using any reports for capacity planning as such, but this is an idea that is going to be put in place shortly.

It provides continuous analytics of the network, which helps our customers in making smarter decisions and ensuring that things are up and running.

In terms of the integration of network performance management data with our ITSM tool, we don't have a direct integration with ServiceNow. We have integrated SevOne with Netcool, and Netcool is integrated with ServiceNow. It is pretty easy to integrate. We've got people on our team who are responsible for Netcool, and if we want to define a new policy or alert, we show them what alert we're sending over, and they integrate it in a matter of a couple of hours.

Its ability to monitor practically any type of network device via SNMP is most valuable. This is the main functionality that we're using. If a network device exposes a metric, such as interface utilization, SevOne will monitor it for us.

The reporting is very good in SevOne. We have static thresholds that are defined by our architects. They give these static thresholds to us, and we implement the alerting policies based on those static thresholds. We also have the capability of doing base-lining or deviation from normal or mean, but we haven't implemented that in our network. 

The out-of-the-box reports are of quality, and they would get you up to speed faster than having to build custom reports. I wasn't here when the reports were created, so I haven't, as such, used the out-of-the-box reports.

We are able to use SevOne's analytics, reports, and workflows in a single dashboard. Its dashboard is very easy to use and put together. It is also really easy to understand. If I had to give it a grade, I would give it an eight out of 10.

In terms of having a complete view of our network performance, I would rate it a nine out of 10. The reason for not giving it a 10 is that there is no packet capture associated with SevOne, but we do have other tools in place to do that.

In terms of stability, because of our move to VMs from physical appliances, some things have become a little unstable. It doesn't seem to be a SevOne issue, but we had to have a lot of calls with their technical support to figure out what's going on with it, but overall, it is pretty solid. 

I have been using this solution for one year and two or three months.

Overall, it is pretty solid. We've made some changes to the SevOne infrastructure, and we moved to VMs from physical appliances. Because of this transition, some things have become a little unstable, but we're working on these issues. It doesn't seem to be a SevOne issue, but because of the change of infrastructure of SevOne, we have had to have a lot of calls with their technical support to figure out what's going on with it. 

It is extremely scalable. We're managing almost 8,000 devices, and if we need to add 8,000 more devices, we just need to add a commensurate number of peers to handle that load. It is horizontally scalable, which is nice.

They're readily available, and they work with us in a very friendly way. They are very willing to help us. Some support desks, especially in performance monitoring, push you to solve your own problem, whereas SevOne's support is the exact opposite. Everyone I've worked with has been helpful. I would give them an A. 

I think they used HP OpenView. I have no idea about the reasons for switching.

I was not involved in its initial setup. For its maintenance, we've got two people in the US and two people in the Philippines who help us. They do network monitoring. The two people in the Philippines work part-time on it because they also support other tools. So, we have three people in total for 8,000 devices.

I would advise evaluating it thoroughly to make sure it is right for your network, and it meets your administrative needs. This should be a major or key element of your decision process.

SevOne supports software-defined and streaming telemetry-based networks, but we are not using any of that. I've also not customized out-of-the-box reports. I've only created custom reports for various customer groups that are consuming the data.

I would rate SevOne Network Data Platform a nine out of 10.

We use the solution for performance and capacity management reports. The product gives us flow data that helps us determine the top users. We also use the solution for LAN, WAN, and Wi-Fi.

I like the tool’s scalability and real-time reports. Earlier, we struggled to give real-time reports to clients. I also like the tool’s deployment model where we can deploy it either on-premises or in-house. We don’t have to carry the data all over the globe. Also, I am impressed with the tool's flow reporting and Wi-Fi.

The tool needs improvement in non-Cisco SD-WAN.

I have been using the product for four years.

My company has 500 users for the solution.

We talk to the tool’s support on a daily basis or whenever we need their help. The product’s support is good.

The tool’s setup was easy. We were able to onboard two major customers within two months of the product’s deployment. The overall deployment took around three months to complete.

The tool is not expensive. We were able to negotiate with SevOne on pricing.

I would rate the solution a nine out of ten.

• Flexible architecture: You can extend the system and its capacity by attaching another cluster pair.
• Very intuitive management interface: Adding and discovering new devices is a very simple process.
• Very useful and flexible end-user GUI interface: Reports or statistics can be prepared by a person who has no knowledge of performance monitoring.
• Automatic reporting: You can very quickly prepare a report to be periodically sent to recipients.
• Very fast reporting engine: Even very complex reports are generated in seconds.
• Many predefined Top-N reports are available out-of-the-box.
• Grouping capability: Each device can be assigned to many groups, which means you can report any interesting network factors according to the multiple group allocation.
• Baseline: The functionality that allow us to monitor a particular factor (like throughput or CPU load) based on some historical data (the value of the factor at similar period of day should be more or less the same)
• Virtualization of network elements: Many physical interfaces that exist on different physical devices can be aggregated as a single logical device with many logical interfaces. This is very useful functionality for network operators.
• Trend analysis: The system predicts the value of the traffic in the future based on existing behavior.

We provide customer internet access services and the 95th percentile is our target. Every month, we prepare a detailed report per customer that shows the current percentile value (does it exceed 95 or not), and we have to prepare detailed traffic reports that show the real traffic graph in the last month.

All of this was done manually. With SevOne, this process is fully automated and the reports can be sent directly to business customers (after a simple verification performed by another colleague).

Our version is quite old. In version 5.3.3.0, we see a lot of room for possible improvement. However, from SevOne support, we received confirmation that most of those expectations are met in version 5.4.x or higher.

Therefore, we have to think about upgrading to the later version as soon as possible.

SevOne should work with the graphs legend functionality. Now, you are able to put a part of the graph description as a customer description, but most of the original description stays unchanged. This means that sometimes the legend under the graph is unreadable (indicator names are sometimes not humanly readable). It would be nice to have a solution similar to the one in Cacti, where you can replace (or rather overwrite) an existing description with your own string.

It has now been almost one and a half years.

Currently, we are using version 5.3.3.0, but we are now just upgrading the system to version 5.3.10 due to several minor issues.

Not, over the last one and a half years.

Yes, but this was caused by special and very uncommon expectations from our side.

Together with SevOne, we implemented the solution which allows us to automatically add any new network device that is added to our external (independent from SevOne) database.

We use the SevOne API to add those devices and interfaces to SevOne. In case of devices with a huge number of interfaces, more than 100, SevOne was not able to load them into its own database.

SevOne recommended an upgrade to a later version to resolve this limitation.

This is the part I am happiest about. Their response is great.

Of course, I sometimes have to wait a week or two, but mostly that is because of the nature of the problem and its complexity.

Most problems are resolved within two to three days.

In our case, the SevOne platform was implemented by a third-party integrator. So, at the beginning, our contact with SevOne was very limited.

Now, for simple or medium issues, we contact SevOne directly through the SevOne support webpage because it speeds up the problem solution time. However, for more complex issues, we still contact the third-party integrator.

We were using Cacti and Zabbix (both open source solutions). We decided to switch mainly because there were some business expectations to have a platform that would prepare reports we can show to business customers.

On the other hand, we would like to have a tool ready to prepare reports on demand and by the non-technical staff.

In a standard solution, the instalation is very simple. In our case, we decided to integrate SevOne with an external database (an external application). All network devices devoted to that application should be automatically inserted into SevOne database.

The integration interface was the part of the solution that was performed by a third-party integrator in cooperation with SevOne.

From the operator’s point of view, it is quite painful to have to remember that every device costs us some cash if added to SevOne (CAPEX and, later, yearly OPEX).

Prices per license are not huge, but they exist.

It is very visible when we connect a big number of network devices (due to some new company acquisition). At once, we have to connect 100s of network elements, and it is hard to find extra money for that.

On the other hand, the existing model is very flexible from a financial point of view (pay-as-you-grow).

Yes, but there was a tender, and I am not authorized to provide such information.

I can only say that there were a few big players in the area of performance monitoring system vendors.

• The grouping capability is very simple and a very important issue in terms of system reporting capability. You should do your homework carefully so you will have a flexible reporting tool in the future.
• Enabling baseline functionality: We decided not to enable it at the beginning and very quickly decided to change our minds. It is a very useful mechanism for data comparison (today’s traffic to the week’s traffic, to weeks before at the same time, and so on).
• Report preparation: It depends on the agreement, but SevOne is ready to prepare some predefined report at initial integration. Let them do this to save you time, but it requires some time to think about your expectations.
• In SevOne, you pay mainly per object. Do not enable all object pooling by default. In a case with 10,000 devices, if you decide not to pool ICMP (not to ping devices to check availability), you can save 10,000 objects, and save real money. (We did so and we do not regret that decision, but it depends on the particular expectations of the company implementing the product.)
• The same as disabling ICMP pooling, you can decide to disable memory and CPU monitoring (if it is not necessary). Money that again stays in your pocket.

The platform is as flexible as an open source system can be. It has a very useful end user GUI interface, which means working with the system is very easy and intuitive.

My use case at the initial startup was very simple. I had a carrier, which was a backbone globally implemented, and I needed a monitoring solution. The type of solution I needed had to capture SNMP traps, poll my equipment, perform traffic analysis, deal with historical data, and things like that. This requirement has remained constant through the entire seven years of implementation with them.

At the end of the month, we're ending our relationship with this vendor for a variety of different reasons. Among the problems is the pricing model that they have, although a lot of it has to do with the fact that their virtualization solution isn't compatible with our Kubernetes environment.

SevOne has enabled us to integrate network performance management data across ITSM and our business decision-making tools, predominantly through the ServiceNow platform. We also did a Salesforce implementation where SevOne leveraged Salesforce to determine if a circuit was production versus non-production. Essentially, this distinction implies whether we should care about it, or not.

The integration with Salesforce was pretty easy, where most of the work was on the Salesforce side. It was probably one of the simpler integrations that we did for the platform.

The comprehensiveness of SevOne in terms of collecting network performance and flow data, when we started using this in 2013, was very limited. It was developed predominantly for a Cisco network and I'm a hundred percent Juniper. As such, it required a lot of work to get the platform to not only understand it but to speak in terms of Juniper MIB files, and even the nomenclature. For a Cisco network, it would have been a situation where you opened the box, plugged it in, and walked away. With Juniper, it was very much not that.

At this point, our collection capabilities are limited to just Juniper equipment. This is restricted by the tool that we have, which only covers Juniper networks.

With respect to streaming telemetry, we do not have it implemented. We were working with them to try and understand what they could do in this regard, but I do not believe that they supported streaming telemetry at the time.

The most valuable feature as of late has been the API integration with ServiceNow. Honestly, the biggest bang for the buck I've got out of SevOne has been this development. The bi-directional integration with ServiceNow has saved me a lot of money in man-hours, over the course of the last few years.

I don't have an exact figure for how much money I have saved, but I can say that it's hundreds of thousands of dollars. What it comes down to is when you're able to automate the console work with the ticketing system, you're saving people from copying and pasting, and other such menial tasks. For example, you are able to auto-populate tickets, update tickets, change the status of tickets, and also do verification to see if something is valid. You can make determinations such as whether there is a ticket currently open or whether there was a ticket previously open. Automating things like that, so a human no longer has to do them, can save hours a day per human per shift.

The out of the box reports and workflows are very sufficient for helping to understand what's normal and abnormal in the network. Out of the box, the reports were certainly there and even though it didn't necessarily understand Juniper, the minute we turned it on, we had a bunch of data. In fact, there was a lot of data that we had never previously seen before on the backbone, made available to us just by virtue of turning it on. It just needed to be cleaned up and polished.

We were aware of the reporting when we decided to implement SevOne, as we had done a lot of pre-sales work with them to make sure we knew what to expect out of the box. Even if we needed to do a lot of customization, it was certainly expected, and that's what we saw. It was important to us because we needed to immediately show some sort of value with all of the work that we'd invested over the course of the implementation. I needed to show almost a day-one value, and that certainly did help.

With respect to customization, the reports themselves didn't take too much effort. We have had a resident SevOne engineer help manage the platform and tend to those apps throughout the entire implementation of SevOne. From my standpoint, it was simply a case of asking the resident engineer for what I needed or what I expected, and whether it was a function of hours or days. Shortly after, I would have exactly what I needed.

An example of how we have customized reporting is the top talking report. It is important because we have a lot of customers that are very bandwidth-intensive. This report is for aggregate bandwidth and it is from a trap-generation standpoint.

I also have a performance metric where we monitor a specific group of circuits that are notorious for having capacity issues with customers. Essentially, it is a top talker traffic graph where I get the top ten circuits for the past 24 hours, and it's a live graph. I get it as a report, but I can also watch it in real-time.

SevOne provides continuous analytics of our network and it's important because if you're in a network where you're polling every three minutes or every five minutes, then you could be missing important events. There's a lot of stuff happening and it can be very damaging in a matter of seconds. If you're not polling or collecting data to absorb that frequency or that duration, then you're not doing anything. You're completely overlooking the important stuff. Being able to see in some form or another, not always in the graph, but being able to see that real-time activity and have it called out to a human is exceptionally important. Again, it doesn't need to be a graph, but that's one of the things we leverage SevOne for.

With respect to giving us a complete view of our network performance, it's been very good. I don't know how many times a week I have a STEM vice president come to me and ask me what's going on with the backbone or how the backbone is performing with a certain world event or corporate event. Whatever it may be, I can get a very good visual summary, very quickly, just by virtue of logging in. It's just a matter of making sure that you have the right graph. You have to tell SevOne what you need and have it presented to you in the right way. Otherwise, it doesn't know. Once you accomplish that, it's immediate.

SevOne has enabled us to detect network performance issues faster, and before they impact end-users. It is very good at capturing those events, documenting them, opening a ticket, and letting a human know about them. There is a definite ability of proactiveness with the tool.

If I consider where we were in 2013, it could take several hours or days to detect events in some cases. I have examples of catastrophic events happening that we never even knew about, that SevOne is able to capture. I estimate that we are 60% faster on average at capturing and actioning events, hopefully proactively.

Their virtualization solution is not compatible with our Kubernetes environment, which is one of the reasons we are ending our relationship with them. I didn't spend a lot of time evaluating with them why it was the case. It was simply not a roadmap item for them, so it was a pretty quick conversation.

We have been using SevOne for approximately seven years.

This product is very scalable, especially if it's just a matter of growing the network. You add more devices, make sure your licensing is in check, and the system ingests it as that equipment is green-lighted.

If you're changing technology, adding layers upon which you want them to monitor, it is still scalable, although it takes a little bit more work.

We have approximately two dozen users in the organization.

Their technical support is very competent. We have had an immediate reaction to our issues, even without the resident engineer involved. Their technical support is 24/7. That said, I've actually had very minimal interaction with them, aside from some hand-holding during software upgrades. Other than that, the platform has been rock solid.

Prior to using SevOne, we were using an internal homegrown solution.

After we got done building it, it largely sat idle until we started onboarding customers. As customers grew, a need for a focused operations group, tooling, processes, and procedures arose. That's where SevOne came in. We needed a legit platform to monitor the backbone rather than use existing processes and procedures that just didn't work or didn't apply.

Essentially, with the growth of the backbone and the responsibility of it, we realized that we needed an enterprise-grade solution.

The initial setup was pretty straightforward. We knew that the biggest hurdle we had to overcome was the Juniper compatibility, so that's where we focused the resources in the planning.

The means of actually getting it installed, upgrading the software, and then actually discovering the network worked as expected. It crawled, it discovered, and it did everything we needed it to. It just needed to be tuned for a 100% Juniper network.

Of course, the Juniper tuning took many hours of post-sales engineering support as well as a resident engineer. It took a lot of work on the SevOne side to actually get it to that point.

In total, the deployment took approximately three months.

I and a colleague were responsible for deployment.

Maintenance requires one FTE.

In terms of ROI, I don't have a whole lot in terms of metrics. However, I would say that with DI, someone has definitely started to come around from a visualization standpoint. Not only do you get an alert with an indicative color like red, orange, or yellow, but it is well represented for different stakeholders. It is not only useful for the engineer sitting at the desk but also for the tier-three that supports that engineer, all the way up to the vice president, who just wants to know how things are going.

They've come a long way in developing that. Back in the day, all people wanted was something that told them the status; red is bad, green is good, yellow means that you should look into it. That was all the information that they had. These days, people want predictive analysis and they want to be able to trend failure. They want to be able to dig into the numbers a little bit more and graphically represent that. To this end, DI is actually something that they're doing to chase that down and fill that void.

Historically, that hadn't been the case. I think DI came out approximately four years ago, and I think that's something that they're really doing to try and add value to the platform.

The pricing has not evolved with the market, which is one of the reasons we are moving to a new product.

When we implemented SevOne, we had been evaluating other options for a couple of years for varying needs, although not necessarily the backbone. During that process, we had noted that SevOne would be the most accommodating and capable for our needs.

At the time, it just wasn't possible for us to implement it.

SevOne is capable of bringing together its analytics reports and workflows in a single dashboard, although I don't actively use that specific dashboard. The stuff that I use with SevOne is very specific to a need at the moment and as such, I don't require the use of a collapsed view. In my world, it's hard to summarize everything in one place. Everything is going to be compartmentalized, so I have multiple dashboards with different data. It isn't that I don't want to use a single pane of glass but it just doesn't serve any purpose for what I need on a daily basis.

Overall, this is a good product and we had a really good relationship with the vendor. When it all started, I had a pretty basic need that I was unable to get any support internally for. We had spoken with them before, and at that initial time, I had some internal obstructions to bringing them onboard. The problems were not financially related and over time, as usual, things changed and the obstructions were gone. Once that happened, I was given the opportunity and the power to develop my own tooling suite for my team, and SevOne was a pretty easy discussion at that point in time.

The relationship continued to be a really good one up until a couple of years ago, when we were growing and of course, they wanted in on that, but their pricing was not adapting to what we were seeing in the market. They were still doing pricing from 2013 when we bought in. Naturally, anytime I expand tool usage, it works in my best interest to make sure that what I'm using is still the best implementation for not only the cost but also, the scalability at the time.

The biggest lesson that I have learned from using SevOne is that leveraging your platforms to do more work in place of a human, isn't always a bad thing. A lot of people think that you're just trying to replace humans with automation and software. What it really boils down to is that you're enabling those humans to do something else that is more important. It's not a function of eliminating jobs. It's letting the humans work on more important, complex items, and let the software and the automation do what they can to contribute to that equation.

It's not that it's necessarily been a challenge or an obstacle for me, but it is important to consider it when explaining the process. When you explain to someone that we're changing this process because SevOne can now do a certain aspect of it, with human involvement starting somewhere further down the line, you have to be able to sell that as an improvement to the process. Ultimately, it's allowing that human to focus on other things that have previously been neglected.

This problem of automating a task that is historically done by a human has been a lesson that I've learned with SevOne. The reality is that you have to let automation do what it can, and let humans do the more important engineering work. Getting away from that stigma and letting the software do its job and really focusing on releasing that, allowing the humans to do the more technical and engineering-level work, is really an act in cost-savings and from a Human Resourcing standpoint, you're getting more bang for your buck out of it. You don't want to pay people a lot of money an hour to sit there and say that red is bad and green is good. If you can get away from that, you're going to be more efficient.

I would rate this solution a seven out of ten.

The fact that it's agentless. With agents, you only see what you instrument and what you tell it to look at. With SevOne, I have complete infrastructure visibility and can see anything on the network.

In 2002, my company was using Tivoli and I was totally frustrated in our inability to see anything. The first thing we fixed was storage and only got around to monitoring in 2008, which was a mess. We had trouble keeping our agents running and had 5 actions for every 125.

Now, we have about 125 actions as opposed to 125 phone calls of issues, increasing our proactive measures hundred-fold. We also began providing rich detailed data to our customer on system performance to the point that they had to change their processes and level of transparency.

We're blowing away our competition.

I think that the downstream suppression could be improved. Suppression must all be done manually, but this improvement is on SevOne's roadmap, I believe.

I've used SevOne since 2010.

For our POC in 2010, we did a little bit of work ahead of time, laying down a small system and receiving an actionable date within four hours. A sister company was having a problem with a payroll system and had no monitoring on the system, so we installed a full suite of SevOne for them on a shared, virtual environment. We deployed those in 24 hours and we provided real-time data into how well the infrastructure was performing.

The only stability issue we had was with a recent upgrade, which took us a long time to backup and restore. We had significant issues with the stability of the PLA platform early on but they fixed and relaunched – very few companies have done that. The PAS and DNC have been rock solid.

No issues with scalability – that’s what's sweet about this product, unlike Tivoli with which he did have scalability issues. SevOne is peer-to-peer so you just add another PAS to the cluster. It's like lots of hands making light work – no problems scaling.

9/10 – they are working on improving that, but have a way to go yet.

We looked at a bunch – we did and RFI – Opnet, NetQS, SevOne and a fourth one. We ended up testing NetQOS (CA owned) and SevOne.

Tivoli – we're still using it as a backup, but all of our RCA and SLA reporting are coming from SevOne.

Easiest deploying product I have ever worked with. It's intuitive. I used to be a Unix admin, and I haven’t done this deployment before, yet I'm able to find data as I need.

We implemented SevOne through our in-house team.

The ROI for my kind of business is difficult to assess, but if I could get rid of Tivoli, I'd reduce my load by two FTE’s which would give me a six month ROI as a back-of-the-envelope kind of guess.

We have increased our capability a hundred-fold over, so it was more of a customer performance thing than ROI. I could see stuff I never saw before. In our root-cause analysis, I would typically have eight level-six people and it could take 24 hours. That’s a lot of horsepower. Now it takes us a quarter of the time. That’s huge.

We looked at a bunch during the RFI process – Opnet, NetQS, SevOne, and a fourth one. We ended up testing NetQOS (CA owned) and SevOne.

I would advise someone to test drive the product and see if it's what you need. I've recommended many people to use this product because it deploys so easily.