OpenText Network Node Manager i Reviews

We use the product monitoring network infrastructure, interfaces, and devices.

The most valuable feature is the map topology. We can map CIs by node and present them along with devices.

It is a good network monitoring, enterprise solution. It is a meta-monitoring solution with good visualization.

The benefit is that we are able to use some features and we can provide external customers with the ability to monitor their devices.

It has improved our workflow, which is now easier with the solution. However, it's not an enterprise scalable solution. We are serving over 500 managed customers and 10 to 50 customers are being added every month. There are limitations to the number of tenants and groups we can add.

Our company uses the solution to manage all nodes, switches, routers, firewalls, cameras, and IoT, WAPs, IP phones, and many more. It completely manages all of our endpoints and network devices. 

The solution tells us when a link goes down or when a device goes offline. For example, we have thousands of cameras and can quickly see when one goes offline on the NNMi. It uses ICMP and SNMP to pull data from that device to report that it is offline. Fault and performance monitoring and reporting of all nodes in the Infra. 

We also use the solution for our topology. From there, we can see the map of how all devices are interconnected to one another.  

Throughout our company, we have ten to twenty network-supporting engineers and managers who use the solution.

The best feature is the solution's entire credibility with all vendors. When we bring in a Cisco device, the solution has a way of changing its own capabilities to adapt to the Cisco environment. A Moxa device sees the solution as Moxa. When we connect HP devices, the solution is immediately able to manage a 3rd-vendor device in far better ways than Cisco Prime or a Cisco monitoring device. We can easily manage any vendor including Fortinet, Aruba, and Cisco. So the solution is a very good device for network operations management, monitoring, and reporting.

The solution allows for much more modifications or human interventions than the Cisco brand. It gives more room for customization compared to other monitoring servers out there.

Our monitoring and network teams of less than 100 people use this solution. The availability and fault monitoring are good.

Micro Focus Network Node Manager is not the best when it comes to drilling down for more visibility, especially regarding traffic.

Performance and analysis need to be improved as well.

You need a special team to work on this product, and not everyone can use it.

We're working on fault, availability and performance. We have iSPI on the network for metrics and traffic.

The stability can be improved.

Our primary use case is for network monitoring, switches, routers, firewalls, all kinds of network equipment you can utilize for monitoring. It allows for multiple integrations for SNP purposes. There are many different use cases for the utilization of the product. 

I'm an IT architect and technical consultant and we partner with Micro Focus. I've dealt with over 1,000 customers who use the product and each organization has multiple customers and multiple users across multiple regions, in the Middle East, India, and other countries. The product is used mainly by IT managers and IT admins. 

It's quite a robust tool for network monitoring solutions. It has gradually evolved over time from a long initial stage to now where it's a very high scale product. It's good for the small tier enterprise role of infrastructure and handling, it's capable of handling multiple nodes and has global architecture - it's quite a good product.

The most valuable feature is that you can utilize the main file from various vendors for integration. In addition, you can carry out customized polling for certain parameters, so that is an add-on to enable a customer to utilize it efficiently.

We are a service provider and deploy in multiple locations such as banks and commercial organizations which have larger networks with 200 and sometimes 2,000 or 3,000 devices. Some of our customers have network teams of 25 to 30 but most have less than that, usually anywhere between five to 20 people. Most are IT admins, IT managers and workers in IT departments. 

The network phase in the product could be improved. Other tools such as SolarWinds have real-time bandwidth, and they can calculate bandwidth in MBs, which means something. But Micro Focus Network Node Manager always watches bandwidth. With Micro Focus, bandwidth utilization networks always show in bytes. It makes it difficult for the end-user to calculate. Micro Focus needs to offer customized dashboards. The reporting is very complex. It's not simple.

As a network person, I want to see the top end network devices, who is using maximum bandwidth or who is using maximum MB. It only requires a very simple graphic, a simple dashboard that I have customized myself. I would prefer to deploy SolarWinds or PRTG.
Unfortunately, our company only deploys Micro Focus. 

Additional features that could be included would be customizing some simple features like dashboard support. They also need to upgrade their level of support and focus on their customers. That's what's important.

The HPE suite is amazingly beautiful, has a fantastic user experience, and provides a high amount of simplification across transactions when adopting cloud technologies significantly.

NNMi is super robust and seamlessly connects everything across applications, infrastructure, server, storage, and networks. We wanted to connect the dots together.

We have implemented not just NNMi, but the entire HPE suite. The trigger to do this was the digital transformation that we are undertaking at my company, which was really fueled by the desire to give a completely different digital experience to our employees.

We started out with adopting the cloud. We started out with an Office 365 migration a couple of years back. We did it in record time. We migrated 125,000 plus mailboxes in 18 weeks. We looked at a case study on the Microsoft website, and once we liked that, and IT liked it too, our users loved it. And users love Yammer, because that's their way of going ahead and chattering about with everybody else.

Then we said, “Why not get everything else on the cloud too, rather than being on premises”? We also had a lot of end-of-life infrastructure and we said, “Okay, we've got to go significantly into the public cloud”.

We're very heavy in Microsoft Azure and in about nine months we've migrated our entire enterprise application landscape onto the public cloud. We're talking about close to 200 applications outside of SAP itself, which we upgraded to SAP HANA. Everything else is in the cloud. We have a true hybrid infrastructure out there. We're also on AWS, of course. We have our trouble-ticketing system on AWS, so if Azure goes down, we've got something else up and running. And of course, we use it for disaster recovery.

NNMi has proved to be certainly better in a) giving us slightly better capabilities to switch to alternatives when incidents do happen, and b) being able to optimize our costs on the infrastructure monitoring side. Now we have the ability to monitor all of these networks globally from a single tool.