NetCrunch Platform Module

SNMP & Core Monitoring

SNMP is ubiquitous due to its simplicity and lightweight protocol based on UDP. Core monitoring in NetCrunch is based on monitoring connectivity and checking Network Services (PING, HTTP, DNS, DHCP, FTP). NetCrunch supports over 70 network protocols and all SNMP versions (v1,v2c, and v3).

The module is part of all NetCrunch products

@Service Status

Download NetCrunch Trial

Reactive monitoring starts with checking the availability and the response time of vital services such as DNS, HTTP, DHCP, RADIUS, and others. NetCrunch does more than checking if the port is open or the connection is established - it verifies the service response to make sure the service is responding correctly.

SNMP protocol is the essential protocol used for monitoring state and performance data of various devices. Even though SNMP is now almost 30 years old, it is still an indispensable part of the monitoring landscape. It is lightweight and straightforward to implement, especially on the agent side, so you can find it in many devices such as switches, printers, UPS, firewall, and others.


    1. Over 70 network protocols supported out-of-the-box
    2. Ability to define your own protocol checks even with regexp patterns
    3. Full support for all versions of SNMP and SNMP Traps, SNMP Notifications (v3) and SNMP Info messages (v3)
    4. MIB Compiler
    5. 8700+ compiled MIBs from over 500 vendors with sources
    6. SNMP browser and diagnostic tools
    7. SNMP View technology with the editor allowing creating human-friendly views for any SNMP device
    8. 60+ Monitoring Packs - ready to use monitoring settings for various devices
    9. Built on feature-rich and complete monitoring platform with a built-in database, alerting, reporting and advanced threshold logic
    10. Easy management of authentication settings through SNMP profiles
  • Availability Monitoring

    This is the most basic monitoring type in NetCrunch. A node state is determined basically by the availability of network services. When a node is in the DOWN state, it's only monitored by a single network service we call leading service.

    @Leading Service

    Network Services

    NetCrunch automatically discovers services on each machine and starts monitoring them. Each check usually requires sending multiple packets, so that program can calculate packet loss rate and make sure the service is responding, even when it drops some responses.

    NetCrunch supports over 70 protocols, including a secure version of protocols such as HTTP/S, FTPS, POP3/S, etc.

    Custom Network Service Checks

    You can easily duplicate a service definition and make a new one with a different port name. For example, you can change the port and save the HTTP service as "HTTP 8080". You can also create a new protocol check from scratch by defining protocol type, port, data to be sent, and response pattern (you can use regexp).

    Remote Probe

    All network service checks are available in the Remote Probe - a lightweight probe installed on a tiny Windows device. You can use it similarly as you would Cisco IPSLA, but in this case, it checks only remote connections and service quality.

    Please refer to Distributed Monitoring for more information.

  • MIB Compiler & MIB Database

    NetCrunch delivers a pre-compiled MIB library containing over 8700 MIBs including Cisco, Nortel, 3Com, Alcatel, and hundreds of the others.

    @MIB Compiler

    We have grouped modules by vendors, and you can see that some MIB groups like Cisco group contain a massive number of compiled modules (over 1000).

    @MIB Groups

  • Device SNMP View

    @SNMP Views

    SNMP protocol describes only variables, tables, and basic operations. SNMP tables often refer to other tables to lookup for column values, making reading data not that easy.

    NetCrunch SNMP Views can present data in a clean human-readable form. Additionally, views allow changing SNMP values so that they can create a UI for the SNMP device.

    NetCrunch provides many ready-to-use view definitions for popular devices such as switches, routers, or servers. The program also allows creating custom views that can be automatically recognized by the device type and displayed correctly.

  • SNMP Monitoring

    Managing node settings is very easy. All you need is to add an element to be monitored to Custom or SNMP Trap or Interface tiles.

    The easiest way of managing SNMP settings is using Monitoring Packs.

    @Adding SNMP Monitoring Packs

    Monitoring SNMP Variables

    To monitor SNMP on a particular node, you need to enable the SNMP monitor, set its profile and port settings - otherwise, it will use the default port.

    You can quickly set alerts on numerical values using one of many threshold types available in NetCrunch.
    The process is very straightforward, click on Custom and add an <Alert on Performance Trigger>.

    See Event Triggers

    Then you will be able to select an SNMP variable as a performance counter. You can find an OID in the MIB library, or you can use the OID if you have one.

    Setting Alerts on Text Values

    You can also monitor text values returned by the SNMP agent. To this, you have to select a <New Event for SNMP Variable Value> alert type.

    Alerting Action & Forwarding

    NetCrunch allows executing Set SNMP Variable action as the alerting action. Additionally, NetCrunch can forward all received traps to another SNMP manager, making device configuration easier.

  • Receiving and logging SNMP Traps

    NetCrunch receives SNMP traps by default, even from nodes that are not in the Atlas. All you need is to configure the device to send it to NetCrunch.

    @Receive SNMNP Traps

    Turning traps into alerts

    Turning received traps from External Events windows into alerts is easy. The program will create a new node if it is not defined in the Atlas yet. This process creates the alert by trap OID. You can also define more complex alerts by filtering certain trap variables.

    SNMPv3 Notifications

    SNMP v3 protocol uses a different model for notifications than earlier SNMP versions. First, you have to define a proper authentication profile since they have to be decoded using a password and valid encryption settings.

    Read more in Receiving SNMPv3 Notifications

  • Switch Monitoring and Port Mapping

    As the switches are a vital part of your network, monitoring their performance is unquestionable. The monitoring of switch interfaces allows for bandwidth monitoring.

    @Switch SNMP Monitoring Settings

    In the picture above, you can see Monitoring Packs added automatically to a switch device.

    Monitoring Network Interfaces

    You can control interface monitoring by the policy. By default, NetCrunch monitors all active interfaces. You can create your own policy and monitor only selected interfaces.

    @Interface Monitoring Policy

    Traffic Information

    NetCrunch presents traffic from all switch interfaces.

    @Switch Interfaces

    You can also observe details of a single switch interface connection.

    @Live Interface Statys

    Port Mapping

    @Port Mapping

    Furthermore, NetCrunch provides Layer-2 topology mapping with additional module Layer 2 Topology Mapping

  • Monitoring Cisco IPSLA operations

    NetCrunch allows monitoring the state of Cisco IPSLA operations. You can select operations that were previously defined on a Cisco device. The protocol type groups operations. You can easily set alerts on status or metrics,

    Read more in the documentation Cisco IP SLA Operations

    @Cisco IPSLA Operation Status

  • Monitoring Printers

    NetCrunch offers two tools to monitors printers. Both of them use SNMP protocols and require Printer MIB v2 to be supported by your printer.

    Generic CMYK Printer Monitoring Pack

    It allows monitoring levels of toner or ink cartridge.

    Printer Sensor

    It allows monitoring much more than just checking the supplies level. The sensor supports printer status objects and can observe alarms triggered by the printer.

  • @NetCrunch Tools SNMP Scanner

    Diagnostic Tools

    Remote IP Tools

    The application allows you to run the most popular diagnostic operations remotely.

    The desktop version of IP tools can execute tools locally from the desktop, from the server on any installed remote probe. The web console version (provides identical UX) allows running tools from the NetCrunch Server or any NetCrunch remote probe.

    • PING - a graphical interface for ICMP PING
    • Traceroute - fast traceroute with IP - country mapping
    • Wake On LAN - send WakeOnLAN packet
    • DNS Info - get full DNS information
    • Who Is - traverse WhoIs databases
    • DNS Audit - Check if a reverse DNS is properly set
    • MAC Resolver - see list of MAC addresses in the local network
    • Subnet Calculator - calculate subnets, masks sizes, and broadcast addresses
    • Ping Scanner - an ultrafast sweep of IPv4 address range to find responding nodes
    • Network Service Scanner - fast checking a list o responding network services for a given node range
    • Open TCP Port Scanner - check opened ports for a range of nodes
    • SNMP Scanner - check which nodes are responding to SysObjId request

SNMP Device Types

Types of SNMP devices include switches, bridges, routers, access servers, computer hosts, servers, UPS-es, printers, IP cameras, and even automation devices that can be controlled thanks to SNMP gateways. These are devices that are part of your SNMP network and relay relevant information via SNMP about various services' status.

NetCrunch is Vendor Agnostic

Populating your infrastructure with devices from a single vendor is hard. NetCrunch supports multiple vendors out of the box, including Cisco, HP, Huawei, Juniper, Dell, Alcatel, Arista, and many others.

NetCrunch provides support for over 500 hardware manufactures - you do not have to look for MIBs as all are already in the NetCrunch database.

Read more in the documentation chapter Monitoring SNMP Devices