SNMP User-Defined Monitor is a sophisticated type of IPNetwork monitoring tools. SNMP, or Simple Network Management Protocol, is a protocol employed in numerous (primarily Unix-like) systems to query and/or adjust device parameters. This includes a wide variety of network devices.
SNMP utilizes a hierarchical structure of OIDs (object identifiers) which are allocated and documented (refer to the IANA OID registry). OIDs are depicted as sequences of integers separated by dots (or in ASN.1, Abstract Syntax Notation One – a more human-readable text format). Note: In the latter scenario, the same ASN.1 representation can potentially correspond to different OIDs depending on the MIB (Management Information Base) in use. Three versions of the SNMP protocol exist; they differ mainly in their security implementations. All other things being equal, either v3 (with user authentication) or v2c (employing read-only communities) should be preferred; v1 should be avoided if the target device supports newer versions. SNMP can be configured to retain data for each required system parameter, making it a versatile tool suitable for almost all monitoring needs. However, manual monitoring can be quite intricate. IPNetwork Monitor provides an effective method for managing such tasks.
Despite their advanced nature, SNMP Monitors are straightforward to configure. Create a new monitor, choose the target host, and on the third page of the New Monitor wizard, click the *Select* button next to the OID field. The
SNMP browser will appear; upload the necessary MIBs as needed and choose the OID you wish to monitor. Configure the remaining settings. The Counter type can be either ‘Current value’ (verify the present value) or ‘Value Change’ (contrast the current value with the previous poll’s value). Specify the port and select the credentials from the dropdown menu in the Credentials section (credentials in this context include the protocol version and either the community string or the username/password/encryption key for authentication). Fine-tune alerting and performance settings on the Alerting and State Conditions tabs, respectively. This simple process completes the setup.
A SNMP User-Defined Monitor can retrieve diverse information. If the standard OIDs don’t furnish the required data, SNMP can be set up to provide the output of a script or program as the requested value. This enables the monitoring of anything verifiable via a program. Frequent examples include monitoring traffic usage, device uptime, system resources, confirming specific processes are active, or checking if a particular user is logged in, and so on.
An SNMP User-Defined Monitor can be resource-intensive, depending on the OID and target device. When feasible, less demanding monitors should be employed, either alongside the SNMP User-Defined Monitor or as dependencies (for example, a
TCP monitor).
Description of other features:
| Monitoring Features |
Here you can find the list of monitor types supported in IPNetwork Monitor and brief description of their parameters. |
|
| Application Templates |
Here you can find the list of application templates supported in IPNetwork Monitor and their short description. |
|
| Network Discovery |
Helps you to create a basis of your monitoring configuration and automates the task of detection network hosts and network services. |
|
| Alerting Features |
Here you can find the list of alert types (ways of reaction to the problems happened during monitoring) available in IPNetwork Monitor, and their brief description. |
|
| Reporting Features |
Here you can find the list of report types available in IPNetwork Monitor with brief descriptions. |
|
| IPNetwork Monitor interfaces
and structure |
Here you can find an overview of IPNetwork Monitor components, Windows and web interfaces. |
