Opmantek NMIS Overview

What is Opmantek NMIS?
Opmantek’s multi award winning network management and IT audit software helps IT teams detect faults, review current and historical network performance, and predict where future failures are likely to occur. Opmantek software is used by more than 115,000 organizations in 130 countries, and manages some of the world’s most complex IT environments including some of the world’s largest telecommunications carriers, managed service providers and banks. Every six minutes somewhere in the world, a new organization implements an Opmantek product.
Buyer's Guide

Download the Network Monitoring Software Buyer's Guide including reviews and more. Updated: June 2021

Opmantek NMIS Customers
Telmex, John Deere, Three Network.

Filter Archived Reviews (More than two years old)

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
it_user855840
Systems Architect at a tech services company with 51-200 employees
Real User
Flexible device polling times and extensible modules are key features for me

What is our primary use case?

We use it as a network monitoring tool, essentially; getting the stats that we need on different interfaces, health reports that we need, depending on the device that we have. That's the main use, generating the SLA at the end of the month.

Pros and Cons

  • "The big thing is the event management engine, which is really, really nice to use, and it comes at a reasonable price, unlike some of the competitors like Netcool from IBM. Those kinds of tools are hugely expensive and they come as resource-heavy types of solutions. This obviously doesn't require as much hardware, but it does offer similar benefits where you can manage all the events."
  • "In my case, I prefer to only poll interfaces that have descriptions, and the ones that don't have descriptions, I don't really want to know about them. It does allow for all these bits and pieces and adjustments, and fine tuning to get it to a point where it works for my needs."
  • "The installer itself is basically something that can be used as a no-questions-asked type of installer. I can use it with automation tools like Chef and Puppet. I don't have to answer some random questions. I can worry about all that stuff later on in the configuration."
  • "It allows for variable polling times of devices on the network. Because it's all in text, in general, that obviously makes it easier from the automation perspective as well, to modify configuration on the fly, using Puppet and those kind of tools."
  • "These kinds of solutions are more node- or device-based solutions. It would be nice in the future if they could be more data-oriented, so it would be easier for me to pull different stats based on ad-hoc requirements; but in a big, centralized database where I can pull specific things, and mix and match the way I want to."

What other advice do I have?

I think it compares very well to all the solutions in what it offers. And also I think compared to some of them, it's much more reliable. On the other hand, there are some things that I do need and I am looking to develop, or get these new features, as I said in the "improvements" section above. When you look at the monitoring, I think the aspects of polling should be controlled by the person that pays for it, for software that has that ability. If I buy something, I need to be able to control some of it by myself without always having to involve someone. If I know what I am doing, I am fine…