3 Reasons to Upgrade your SNMP Strategy
by December 3, 2012

Filed under: Network Performance Management, Performance Management Tech

For more than 20 years, SNMP monitoring was the default approach to network performance management. It was your only option, but this just isn’t the case anymore.

Application components are no longer delivered just from your datacenter, but are delivered from private clouds and from third-party services hosted outside of your control zone in the public cloud with multiple potential points of failure. To top it all, application requirements and end-user expectations are higher than ever before; regardless of where performance problems occurs within this new cloud-based application delivery chain, they will hold IT ultimately responsible for their experiences.

As your organization moves forward, so should your network performance management approach. Let’s review in more detail the three main reasons why traditional SNMP monitoring no longer fits today’s complex and distributed network architectures.

snmp

1. Traditional SNMP tools have always shown you the status of your network devices and the volume of data transmitted at the edge of your network.

The Problem: This level of monitoring only lets you see a fraction of the network used in the delivery of modern business services, and you only have partial visibility to the problems that might be occurring on it. This complicates troubleshooting activities.

2. Companies have transformed into interconnected, highly agile distributed organizations with multiple locations, offices and branches, with deployment architectures spanning across datacenters, private and public clouds.

The application delivery infrastructure is more diverse than ever and traditional SNMP monitoring wastes considerable network bandwidth constantly relaying unnecessary information, such as device version number, which is included in every SNMP message.

The Problem: Continuous SNMP data transmission across distributed networks can strain or flood your network, and negatively impact user experiences. In addition, processing SNMP queries on certain data sets may result in higher CPU utilization than necessary. Why should you overload your devices and network querying and transmitting data that you don’t really need?

3. Companies have moved away from an infrastructure-centric view, and are now interested in seeing in real time how services and business processes are being delivered, and what end-users are ultimately experiencing.

The Problem: Traditional SNMP monitoring offers a resource consumption view across your devices, but it doesn’t give you any visibility into what that device status means for network performance, and more importantly what this all means for application performance and user experience.