Available versions




Module Generic SNMPv3

Description

Template Module Generic version: 0.14 MIBs used: SNMPv2-MIB

Overview

This is a module based on the “Template Module Generic SNMPv2” module. For correct use, you need to define the macro “{$SNMP_SECNAME_CONTEXT}”, this macro is also used in the rest of my templates using SNMPv3. I do not use authentication and encryption in my templates, which corresponds to security level = noAuthNoPriv.

Author

Alexey Glotkin

Macros used

Name Description Default Type
{$SNMP_TIMEOUT} <p>-</p> 3m Text macro
Name
Template Module ICMP Ping

Discovery rules

There are no discovery rules in this template.

Items collected

Name Description Type Key and additional info
Device contact details <p>MIB: SNMPv2-MIB The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.</p> SNMP agent system.contact<p>Update: 3600</p>
SNMP traps (fallback) <p>Item is used to collect all SNMP traps unmatched by other snmptrap items</p> SNMP trap snmptrap.fallback<p>Update: 300</p>
Device name <p>MIB: SNMPv2-MIB An administratively-assigned name for this managed node.By convention, this is the node’s fully-qualified domain name. If the name is unknown, the value is the zero-length string.</p> SNMP agent system.name<p>Update: 3600</p>
SNMP availability <p>-</p> Zabbix internal zabbix[host,snmp,available]<p>Update: 60</p>
Device location <p>MIB: SNMPv2-MIB The physical location of this node (e.g., telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.</p>|SNMP agent` system.location<p>Update: 3600</p>  
System object ID <p>MIB: SNMPv2-MIB The vendor’s authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.’ was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its Fred Router'.</p>|SNMP agent` system.objectid<p>Update: 3600</p>  
Device description <p>MIB: SNMPv2-MIB A textual description of the entity. This value should include the full name and version identification of the system’s hardware type, software operating-system, and networking software.</p> SNMP agent system.descr<p>Update: 3600</p>
Device uptime <p>MIB: SNMPv2-MIB The time (in hundredths of a second) since the network management portion of the system was last re-initialized.</p> SNMP agent system.uptime<p>Update: 120s</p>

Triggers

There are no triggers in this template.

Module Generic SNMPv3

Description

Template Module Generic version: 0.14 MIBs used: SNMPv2-MIB

Overview

This is a module based on the “Template Module Generic SNMPv2” module. For correct use, you need to define the macro “{$SNMP_SECNAME_CONTEXT}”, this macro is also used in the rest of my templates using SNMPv3. I do not use authentication and encryption in my templates, which corresponds to security level = noAuthNoPriv.

Author

Alexey Glotkin

Macros used

Name Description Default Type
{$SNMP_TIMEOUT} <p>-</p> 3m Text macro
Name
Template Module ICMP Ping

Discovery rules

There are no discovery rules in this template.

Items collected

Name Description Type Key and additional info
SNMP availability <p>-</p> Zabbix internal zabbix[host,snmp,available]<p>Update: 60</p>
SNMP traps (fallback) <p>Item is used to collect all SNMP traps unmatched by other snmptrap items</p> SNMP trap snmptrap.fallback<p>Update: 300</p>
Device contact details <p>MIB: SNMPv2-MIB The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.</p> SNMP agent system.contact<p>Update: 3600</p>
Device uptime <p>MIB: SNMPv2-MIB The time (in hundredths of a second) since the network management portion of the system was last re-initialized.</p> SNMP agent system.uptime<p>Update: 120s</p>
Device description <p>MIB: SNMPv2-MIB A textual description of the entity. This value should include the full name and version identification of the system’s hardware type, software operating-system, and networking software.</p> SNMP agent system.descr<p>Update: 3600</p>
System object ID <p>MIB: SNMPv2-MIB The vendor’s authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.’ was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its Fred Router'.</p>|SNMP agent` system.objectid<p>Update: 3600</p>  
Device location <p>MIB: SNMPv2-MIB The physical location of this node (e.g., telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.</p>|SNMP agent` system.location<p>Update: 3600</p>  
Device name <p>MIB: SNMPv2-MIB An administratively-assigned name for this managed node.By convention, this is the node’s fully-qualified domain name. If the name is unknown, the value is the zero-length string.</p> SNMP agent system.name<p>Update: 3600</p>

Triggers

There are no triggers in this template.

Module Generic SNMPv3

Description

Template Module Generic version: 0.14 MIBs used: SNMPv2-MIB

Overview

This is a module based on the “Template Module Generic SNMPv2” module. For correct use, you need to define the macro “{$SNMP_SECNAME_CONTEXT}”, this macro is also used in the rest of my templates using SNMPv3. I do not use authentication and encryption in my templates, which corresponds to security level = noAuthNoPriv.

Author

Alexey Glotkin

Macros used

Name Description Default Type
{$SNMP_TIMEOUT} <p>-</p> 3m Text macro
Name
Template Module ICMP Ping

Discovery rules

There are no discovery rules in this template.

Items collected

Name Description Type Key and additional info
SNMP availability <p>-</p> Zabbix internal zabbix[host,snmp,available]<p>Update: 60</p>
SNMP traps (fallback) <p>Item is used to collect all SNMP traps unmatched by other snmptrap items</p> SNMP trap snmptrap.fallback<p>Update: 300</p>
Device contact details <p>MIB: SNMPv2-MIB The textual identification of the contact person for this managed node, together with information on how to contact this person. If no contact information is known, the value is the zero-length string.</p> SNMP agent system.contact<p>Update: 3600</p>
Device uptime <p>MIB: SNMPv2-MIB The time (in hundredths of a second) since the network management portion of the system was last re-initialized.</p> SNMP agent system.uptime<p>Update: 120s</p>
Device description <p>MIB: SNMPv2-MIB A textual description of the entity. This value should include the full name and version identification of the system’s hardware type, software operating-system, and networking software.</p> SNMP agent system.descr<p>Update: 3600</p>
System object ID <p>MIB: SNMPv2-MIB The vendor’s authoritative identification of the network management subsystem contained in the entity. This value is allocated within the SMI enterprises subtree (1.3.6.1.4.1) and provides an easy and unambiguous means for determiningwhat kind of box' is being managed. For example, if vendorFlintstones, Inc.’ was assigned the subtree1.3.6.1.4.1.4242, it could assign the identifier 1.3.6.1.4.1.4242.1.1 to its Fred Router'.</p>|SNMP agent` system.objectid<p>Update: 3600</p>  
Device location <p>MIB: SNMPv2-MIB The physical location of this node (e.g., telephone closet, 3rd floor'). If the location is unknown, the value is the zero-length string.</p>|SNMP agent` system.location<p>Update: 3600</p>  
Device name <p>MIB: SNMPv2-MIB An administratively-assigned name for this managed node.By convention, this is the node’s fully-qualified domain name. If the name is unknown, the value is the zero-length string.</p> SNMP agent system.name<p>Update: 3600</p>

Triggers

There are no triggers in this template.