SNMP Errors: Go Beyond The Basics for SolarWinds© Orion© Users

network monitoring

 

Finding errors lurking in your network with a SMNP based monitoring tool soooooo 1999.

If you are a SolarWinds Orion user, you have probably realized that while NPM is an amazing product for SNMP-based monitoring, today’s challenges require a more in-depth solution. Out of the box, SolarWinds Orion NPM will give you these:

  • Network availability
  • Bandwidth capacity utilization
  • Buffer usage and errors
  • CPU and memory utilization
  • Interface errors and discards
  • Network latency
  • Node, interface, and volume status
  • Volume usage

(the list above was taken from NPM’s Quick Start Guide)

All of the items listed above have a few common aspects to them:

  1. They are simple numbers – bits, bytes, percentages.
  2. They are numbers compared to thresholds for alerting (e.g. “if CPU is above 80%, then alert”)
  3. They are generic to all networking devices.

Back in 1999, when NPM was originally written, this approach was great. Network devices were simple (frankly, most of them were made by one of three or four manufacturers, such as Cisco) and the amount of know-how required to operate them was limited.

But it’s 2016. There are hundreds of network device manufacturers. Every enterprise we encounter is using at least a dozen of them. Each device has a plethora of features and getting certified on just a single product can take months. However, NPM’s approach to data collection and graphing isn’t sufficient for today’s needs. It makes sense if you think about it – it’s very difficult to write a product from scratch to match the new requirements of the market.

indeni was written from scratch with today’s requirements in mind. That’s why indeni treats every network device very differently. The code and knowledge utilized by indeni to analyze a Cisco switch is vastly different to what is used with a Palo Alto Networks firewall. Even between firewall vendors, such as Check Point, Cisco, Fortinet, Juniper and Palo Alto Networks, the logic used by indeni to look for issues is unique to each product analyzed.

So, if you have Check Point firewalls, Cisco firewalls, Cisco routers, Cisco switches, F5 LTMs, Fortinet firewalls, Juniper firewalls and Palo Alto Networks firewalls, take a look at the top of this page and click on the product you are responsible for. You’ll see that out-of-the-box, with no additional work or configuration, indeni will uncovers thousands more issues than NPM is capable of uncovering for the devices supported by indeni. What’s more, indeni keeps expanding in the set of issues it can identify.

It’s 2016. It’s time to use 2016’s software.

If you want to see the difference between outdated technology you’re currently running and a predictive analysis software for high availability networks,

Fill out the form below:

 

[ninja_form id=16]