The SNMP Device Driver provides communications via Simple Network Management Protocol (SNMP) allowing to exchange management information with SNMP-compliant network devices. All versions of SNMP protocol (v1, v2(c) and v3) are supported including secure communications introduced in SNMP version 3.
Like with all other types of devices, data collected from SNMP devices is converted into unified form to allow accessing them from different AggreGate facilities. See Devices article for more information about the "normalized" representation of devices in Tibbo AggreGate.
There are two basic SNMP monitoring methods described further in this section: polling and event (Trap/Inform) monitoring.
Refer to SNMP Global Settings subsection for details about global settings used by SNMP service.
Driver Information
Driver Plugin ID: |
com.tibbo.linkserver.plugin.device.snmp |
Global Settings
See SNMP Global Settings.
User Level Settings
None defined.
Device Properties
Device properties define SNMP communication parameters for the particular device. They comprises:
| • | Host Address (address) property that specifies IP Address or Host Name of the network host to be monitored |
| • | Polling Settings that are used to periodically obtain current status of the SNMP device (poll it). |
Device Assets
The driver creates one root asset for every MIB file supported by the device. Supported MIB files are detected automatically by polling the SNMP agent.
|
Assets for MIBs that are marked as Default in MIB Directory will be enabled automatically. |
SNMP device settings present results of the last polling operation.
No operations provided by the driver.
SNMP devices generate two different types of events: Service Outage (indicating SNMP downtime as described in Network Host device driver chapter) and SNMP notification (see below).
SNMP driver generates events on reception of SNMP notifications (both traps and informs). Refer to SNMP Notifications Monitoring section for details.
|
Since SNMP driver listens for the notifications from all network hosts (not only hosts that match to a certain Device account), the Trap events are generated in the Network Management context instead of Device context. |
Event Name |
trap |
Permissions |
Accessible at User permission level |
Records |
1 |
The trap event has the following format:
Field Name |
Field Type |
Notes |
agentAddress |
String |
SNMP Agent Address, i.e. IP address of the object generating the trap. |
version |
String |
Trap version. |
type |
String |
Trap type (Trap or Inform). |
enterprise |
String |
Enterprise. Corporation or organization that originated the trap. This is the object identifier (OID) assigned to the vendor implementing the agent. Equals to the value of the sysObjectID variable, and it is unique for each implementer of an SNMP agent. |
genericTrap |
Integer |
Generic Trap Type ID. Integer, see table below. |
specificTrap |
Integer |
Specific Trap Type ID. Defined when Generic Trap Type is set to Enterprise. |
oid |
String |
Trap OID. |
timestamp |
Date |
Elapsed time, in hundredths of a second, from the last reinitialization of the agent to the event generating the trap. |
variableBindings |
Data Table |
Variable Bindings. Extra information, dependent on generic-trap type. |
engineID |
String |
SNMP engine ID of the trap originator. |
The following Generic Trap Type ID values are defined for genericTrap field:
Value |
Name |
Description |
0 |
coldStart |
The agent is reinitializing. Configuration data or MIB variable values, or both, might have changed. Restart the measurement epochs. |
1 |
warmStart |
The agent is reinitializing but configuration data or MIB variable values have not changed. |
2 |
linkDown |
The agent has detected that a known communications interface has been disabled. |
3 |
linkUp |
The agent has detected that a known communications interface has been enabled. |
4 |
authenticationFailure |
A message was received that could not be authenticated. |
5 |
egpNeighborLoss |
An Exterior Gateway Protocol (EGP) neighbor was lost. |
6 |
enterpriseSpecific |
Vendor-specific trap. Specific Trap Type ID should be defined. |
Connection Handling
This driver makes the device Online if SNMP polling operation reports no errors.
Synchronization Details
The synchronization procedure executes SNMP polling operations, refer to SNMP polling section for details.