Network monitoring engineer at a tech vendor with 10,001+ employees
Real User
Top 20
Mar 21, 2025
The primary use case of IBM SevOne Network Performance Management (NPM) ( /products/ibm-sevone-network-performance-management-npm-reviews ) is network monitoring. It helps to maintain the infrastructure's availability and ensure that alerts are generated when needed.
Tranformation Programmes and Global Config Hub Lead at BT - British Telecom
MSP
Apr 6, 2023
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.
Principal Network Engineer at a comms service provider with 10,001+ employees
Real User
Aug 2, 2022
We are a large enterprise and provider. We use the solution to monitor and capacity plan our network. We also use it for our cable modem estate. We have about 6 to 7 million customers who aggregate onto devices. We monitor those devices with SevOne NPM on a separate cluster. We also have a customer-facing cluster that we are about to install. It is our strategic performance monitoring tool. So, it is the only thing that we use to monitor our internal network, which is huge. We plan to extend it and replace our network performance monitoring tool, which is another IBM tool and currently a big customer-facing system. We planned for another fairly large cluster of about 20 virtual machines. We have both physical and virtual appliances onsite. We don't currently use the cloud.
We are a VoIP company and we use Cisco BroadWorks as our voice platform. SevOne monitors all the servers, the uptime, the bandwidth being used, and everything else. It also monitors the trap that it gets from these servers. It's running on VMware.
Professional II Service Delivery Coordinator at a computer software company with 10,001+ employees
Real User
Mar 9, 2022
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.
Learn what your peers think about IBM SevOne Network Performance Management (NPM). Get advice and tips from experienced pros sharing their opinions. Updated: April 2026.
Tranformation Programmes and Global Config Hub Lead at BT - British Telecom
MSP
Jan 5, 2022
Our company provides managed services to our global customers for our networks. We also sell our WAN networks and provide managed services on the LAN network. We use SevOne to look at the performance management of the networks that we sell to our customers including routers, switches, and network links as they go up and down. We have installed more than 100,000 devices on the non-SD WAN side of SevOne. We can determine the performance utilization with metrics of the devices including fan speed, temperature, and other generic health checkups. If the utilization is high we raise an alarm in our ticket managing system and then our service desk can start looking into them. We use SevOne quite extensively. We use all the modules extensively both internally and externally with our customers. They log in and use SevOne to access the tools.
Solution Architect at a media company with 10,001+ employees
Real User
Jun 16, 2021
SevOne is used mainly for network monitoring. In my company, there are different services that include mobile data, voice, and broadband. SevOne is being used across all of these three services, and it also covers our corporate network. SevOne is also being used for business reporting and capacity planning.
We use it pretty extensively for all of our network performance management needs. It's monitoring Spark core and network performance. It's managing our managed-data customers' equipment on site, and it's also used to look after monitoring our internet links as well. We use it for any performance-related stats or information of that type. It has the capability for that. It's all on-premise at the moment. We don't have the Data Insight component of the SevOne offering at this stage. We're still looking at that, but we predominantly use the platform to give us collection capability, and we'll use the data and visualize it on other platforms as well. So we have engineers that can use the data directly or natively in the tool, or we'll take the data or the collections and use those for other purposes, including billing.
Network Engineer at a financial services firm with 1,001-5,000 employees
Real User
Jun 9, 2021
We use it to look into performances in our system and different dedicated environments. We try to draw graphs that represent what we have in terms of time response, bandwidth, and input and output across all our data centers to see if the load balance is correct. We have some traffic flows that say if the traffic is dropping and being taken by another data center. There are a lot of reports all around about different points of our architecture. It is deployed as a physical appliance on-premises. So, we have the SevOne appliance in our data center.
SevOne Admin at a financial services firm with 10,001+ employees
Vendor
Apr 27, 2021
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.
Network Tool Manager at a financial services firm with 10,001+ employees
Real User
Apr 13, 2021
We are primarily using SevOne to monitor bandwidth utilization. We also use it for proactive monitoring of the CPU, memory, and other resources. Our main goal is to monitor the network health and proactively upgrade before any issues occur.
Sr. Network Engineer at a comms service provider with 10,001+ employees
Real User
Mar 30, 2021
We have quite a few use cases for the SevOne NMS. It's mainly for performance management by our different network teams and we also do performance management of our external customers. That means we offer businesses and schools and others access to a Comcast device for their site to give them internet, or site-to-site connectivity. We also monitor our Comcast Digital Voice in SevOne NMS. For the external customers and the Comcast Digital Voice, we're inputting flat file data into SevOne so that we can get the metrics for that flat file data and provide it to those customers. We're doing SMP and what they call xStats. With SevOne DI we allow our external customers to log in and get a report for their data. We give them a subset of the data that we collect so that they can see that we're staying within our SLAs. I mainly focus on the thresholding capability of SevOne. We configure thresholds on the performance metrics and they send us alerts so that the NOC is alerted about the systems that are having issues. I maintain SevOne and I give the customers what they want. They're the ones who let me know if there's an issue. They're the ones monitoring the health of our network. We have various NOCs, depending on the device type, and they're the ones that will let me know if something needs to be modified or tweaked to enhance that performance management. We have a SevOne NMS cluster that is also attached to a SevOne Data Insight cluster, and the SevOne NMS system is also sending out the SDB to a set of servers that we maintain for customers for rural data. We're using the 300K which we've licensed to 200K and we're on version 5.7.22 of the NMS and 3.0 on the SDI.
We're using SevOne to monitor our network infrastructure. We provide monitoring services and performance capacity management for network gear, including routers, switches, wireless controllers, firewalls, and load balancers, to name a few. We have various manufacturers and different device models that we leverage the solution to monitor in our organization. Our deployment of SevOne is mostly virtualized. We have gone completely virtual in our environment. We have SevOne deployed in different regions of the world: the U.S., Hong Kong for Asia, as well as in London for Europe.
Network monitoring engineer at a tech vendor with 10,001+ employees
Real User
Top 20
Mar 30, 2021
This is mainly used for network performance monitoring and availability alerting. Also, we are using SevOne to help with the troubleshooting of any issue. For example, whenever there is a service outage, we have a look into the graphing data. Mainly, we are using the SNMP data and NetFlow. Other than that, we are using the ICMP availability, which is just an availability check. These are the major areas that we have been pulling. It is a physical box installed in our data centers.
Our client who is using SevOne is a large client, it's big. We have to create multiple instances to support their infrastructure on the platform because they are very huge and are on-prem as well as on the cloud. Because Turbonomics is unlimited, they can do certain VM levels. I think you can do 11,000. You can collect 11,000 metrics from the VMs and you cannot go above that number. So let's say if you have 9,000 VMs, you can handle it, but sometimes you become busy and you're doing a lot of collections, or if you start collecting the processes' metrics, that is going to be a problem for you down the line. So we have about eight instances to support the platform on-prem and I think 11 or 12 on the cloud.
IBM SevOne Network Performance Management offers real-time insights, customization, and integration capabilities to efficiently monitor network performance across diverse infrastructures, enhancing operational efficiency.IBM SevOne NPM is recognized for its ability to provide scalable network monitoring across multi-vendor environments. It delivers real-time data insights essential for maintaining network health and performance. With features like SNMP monitoring, NetFlow data collection, and...
The primary use case of IBM SevOne Network Performance Management (NPM) ( /products/ibm-sevone-network-performance-management-npm-reviews ) is network monitoring. It helps to maintain the infrastructure's availability and ensure that alerts are generated when needed.
We use SevOne to collect and report on network flows.
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.
We are a large enterprise and provider. We use the solution to monitor and capacity plan our network. We also use it for our cable modem estate. We have about 6 to 7 million customers who aggregate onto devices. We monitor those devices with SevOne NPM on a separate cluster. We also have a customer-facing cluster that we are about to install. It is our strategic performance monitoring tool. So, it is the only thing that we use to monitor our internal network, which is huge. We plan to extend it and replace our network performance monitoring tool, which is another IBM tool and currently a big customer-facing system. We planned for another fairly large cluster of about 20 virtual machines. We have both physical and virtual appliances onsite. We don't currently use the cloud.
We are a VoIP company and we use Cisco BroadWorks as our voice platform. SevOne monitors all the servers, the uptime, the bandwidth being used, and everything else. It also monitors the trap that it gets from these servers. It's running on VMware.
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.
Our company provides managed services to our global customers for our networks. We also sell our WAN networks and provide managed services on the LAN network. We use SevOne to look at the performance management of the networks that we sell to our customers including routers, switches, and network links as they go up and down. We have installed more than 100,000 devices on the non-SD WAN side of SevOne. We can determine the performance utilization with metrics of the devices including fan speed, temperature, and other generic health checkups. If the utilization is high we raise an alarm in our ticket managing system and then our service desk can start looking into them. We use SevOne quite extensively. We use all the modules extensively both internally and externally with our customers. They log in and use SevOne to access the tools.
SevOne is used mainly for network monitoring. In my company, there are different services that include mobile data, voice, and broadband. SevOne is being used across all of these three services, and it also covers our corporate network. SevOne is also being used for business reporting and capacity planning.
Our primary use cases are for network alerting and reporting.
We use it pretty extensively for all of our network performance management needs. It's monitoring Spark core and network performance. It's managing our managed-data customers' equipment on site, and it's also used to look after monitoring our internet links as well. We use it for any performance-related stats or information of that type. It has the capability for that. It's all on-premise at the moment. We don't have the Data Insight component of the SevOne offering at this stage. We're still looking at that, but we predominantly use the platform to give us collection capability, and we'll use the data and visualize it on other platforms as well. So we have engineers that can use the data directly or natively in the tool, or we'll take the data or the collections and use those for other purposes, including billing.
We use it to look into performances in our system and different dedicated environments. We try to draw graphs that represent what we have in terms of time response, bandwidth, and input and output across all our data centers to see if the load balance is correct. We have some traffic flows that say if the traffic is dropping and being taken by another data center. There are a lot of reports all around about different points of our architecture. It is deployed as a physical appliance on-premises. So, we have the SevOne appliance in our data center.
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.
We are primarily using SevOne to monitor bandwidth utilization. We also use it for proactive monitoring of the CPU, memory, and other resources. Our main goal is to monitor the network health and proactively upgrade before any issues occur.
We have quite a few use cases for the SevOne NMS. It's mainly for performance management by our different network teams and we also do performance management of our external customers. That means we offer businesses and schools and others access to a Comcast device for their site to give them internet, or site-to-site connectivity. We also monitor our Comcast Digital Voice in SevOne NMS. For the external customers and the Comcast Digital Voice, we're inputting flat file data into SevOne so that we can get the metrics for that flat file data and provide it to those customers. We're doing SMP and what they call xStats. With SevOne DI we allow our external customers to log in and get a report for their data. We give them a subset of the data that we collect so that they can see that we're staying within our SLAs. I mainly focus on the thresholding capability of SevOne. We configure thresholds on the performance metrics and they send us alerts so that the NOC is alerted about the systems that are having issues. I maintain SevOne and I give the customers what they want. They're the ones who let me know if there's an issue. They're the ones monitoring the health of our network. We have various NOCs, depending on the device type, and they're the ones that will let me know if something needs to be modified or tweaked to enhance that performance management. We have a SevOne NMS cluster that is also attached to a SevOne Data Insight cluster, and the SevOne NMS system is also sending out the SDB to a set of servers that we maintain for customers for rural data. We're using the 300K which we've licensed to 200K and we're on version 5.7.22 of the NMS and 3.0 on the SDI.
We're using SevOne to monitor our network infrastructure. We provide monitoring services and performance capacity management for network gear, including routers, switches, wireless controllers, firewalls, and load balancers, to name a few. We have various manufacturers and different device models that we leverage the solution to monitor in our organization. Our deployment of SevOne is mostly virtualized. We have gone completely virtual in our environment. We have SevOne deployed in different regions of the world: the U.S., Hong Kong for Asia, as well as in London for Europe.
This is mainly used for network performance monitoring and availability alerting. Also, we are using SevOne to help with the troubleshooting of any issue. For example, whenever there is a service outage, we have a look into the graphing data. Mainly, we are using the SNMP data and NetFlow. Other than that, we are using the ICMP availability, which is just an availability check. These are the major areas that we have been pulling. It is a physical box installed in our data centers.
Our client who is using SevOne is a large client, it's big. We have to create multiple instances to support their infrastructure on the platform because they are very huge and are on-prem as well as on the cloud. Because Turbonomics is unlimited, they can do certain VM levels. I think you can do 11,000. You can collect 11,000 metrics from the VMs and you cannot go above that number. So let's say if you have 9,000 VMs, you can handle it, but sometimes you become busy and you're doing a lot of collections, or if you start collecting the processes' metrics, that is going to be a problem for you down the line. So we have about eight instances to support the platform on-prem and I think 11 or 12 on the cloud.
We use SevOne to display all the information from Cisco IP SLA regarding the delay, voice quality, etc.