forked from fernandobrunelli/Zabbix-Templates
-
Notifications
You must be signed in to change notification settings - Fork 88
/
Template Module EtherLike-MIB SNMPv2.xml
191 lines (191 loc) · 8.45 KB
/
Template Module EtherLike-MIB SNMPv2.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
<?xml version="1.0" encoding="UTF-8"?>
<zabbix_export>
<version>3.4</version>
<groups>
<group>
<name>Templates/Modules</name>
</group>
</groups>
<templates>
<template>
<template>Template Module EtherLike-MIB SNMPv2</template>
<name>Template Module EtherLike-MIB SNMPv2</name>
<description>Template EtherLike-MIB (duplex control only) version: 0.14
MIBs used:
EtherLike-MIB</description>
<groups>
<group>
<name>Templates/Modules</name>
</group>
</groups>
<applications>
<application>
<name>Network Interfaces</name>
</application>
</applications>
<items/>
<discovery_rules>
<discovery_rule>
<name>EtherLike-MIB Discovery</name>
<type>4</type>
<snmp_community>{$SNMP_COMMUNITY}</snmp_community>
<snmp_oid>discovery[{#SNMPVALUE},1.3.6.1.2.1.10.7.2.1.19,{#IFOPERSTATUS},1.3.6.1.2.1.2.2.1.8,{#IFALIAS},1.3.6.1.2.1.31.1.1.1.18,{#IFNAME},1.3.6.1.2.1.31.1.1.1.1,{#IFDESCR},1.3.6.1.2.1.2.2.1.2]</snmp_oid>
<key>net.if.duplex.discovery</key>
<delay>3600</delay>
<status>0</status>
<allowed_hosts/>
<snmpv3_contextname/>
<snmpv3_securityname/>
<snmpv3_securitylevel>0</snmpv3_securitylevel>
<snmpv3_authprotocol>0</snmpv3_authprotocol>
<snmpv3_authpassphrase/>
<snmpv3_privprotocol>0</snmpv3_privprotocol>
<snmpv3_privpassphrase/>
<params/>
<ipmi_sensor/>
<authtype>0</authtype>
<username/>
<password/>
<publickey/>
<privatekey/>
<port/>
<filter>
<evaltype>1</evaltype>
<formula/>
<conditions>
<condition>
<macro>{#IFOPERSTATUS}</macro>
<value>1</value>
<operator>8</operator>
<formulaid>A</formulaid>
</condition>
<condition>
<macro>{#SNMPVALUE}</macro>
<value>(2|3)</value>
<operator>8</operator>
<formulaid>B</formulaid>
</condition>
</conditions>
</filter>
<lifetime>30d</lifetime>
<description>Discovering interfaces from IF-MIB and EtherLike-MIB. Interfaces with up(1) Operational Status are discovered.</description>
<item_prototypes>
<item_prototype>
<name>Interface {#IFNAME}({#IFALIAS}): Duplex status</name>
<type>4</type>
<snmp_community>{$SNMP_COMMUNITY}</snmp_community>
<snmp_oid>1.3.6.1.2.1.10.7.2.1.19.{#SNMPINDEX}</snmp_oid>
<key>net.if.duplex[dot3StatsDuplexStatus.{#SNMPINDEX}]</key>
<delay>300</delay>
<history>1w</history>
<trends>0d</trends>
<status>0</status>
<value_type>3</value_type>
<allowed_hosts/>
<units/>
<snmpv3_contextname/>
<snmpv3_securityname/>
<snmpv3_securitylevel>0</snmpv3_securitylevel>
<snmpv3_authprotocol>0</snmpv3_authprotocol>
<snmpv3_authpassphrase/>
<snmpv3_privprotocol>0</snmpv3_privprotocol>
<snmpv3_privpassphrase/>
<params/>
<ipmi_sensor/>
<authtype>0</authtype>
<username/>
<password/>
<publickey/>
<privatekey/>
<port/>
<description>MIB: EtherLike-MIB
The current mode of operation of the MAC
entity. 'unknown' indicates that the current
duplex mode could not be determined.
Management control of the duplex mode is
accomplished through the MAU MIB. When
an interface does not support autonegotiation,
or when autonegotiation is not enabled, the
duplex mode is controlled using
ifMauDefaultType. When autonegotiation is
supported and enabled, duplex mode is controlled
using ifMauAutoNegAdvertisedBits. In either
case, the currently operating duplex mode is
reflected both in this object and in ifMauType.
Note that this object provides redundant
information with ifMauType. Normally, redundant
objects are discouraged. However, in this
instance, it allows a management application to
determine the duplex status of an interface
without having to know every possible value of
ifMauType. This was felt to be sufficiently
valuable to justify the redundancy.
Reference: [IEEE 802.3 Std.], 30.3.1.1.32,aDuplexStatus.</description>
<inventory_link>0</inventory_link>
<applications>
<application>
<name>Network Interfaces</name>
</application>
</applications>
<valuemap>
<name>EtherLike-MIB::dot3StatsDuplexStatus</name>
</valuemap>
<logtimefmt/>
<preprocessing/>
<jmx_endpoint/>
<application_prototypes/>
<master_item_prototype/>
</item_prototype>
</item_prototypes>
<trigger_prototypes>
<trigger_prototype>
<expression>{Template Module EtherLike-MIB SNMPv2:net.if.duplex[dot3StatsDuplexStatus.{#SNMPINDEX}].last()}=2</expression>
<recovery_mode>0</recovery_mode>
<recovery_expression/>
<name>Interface {#IFNAME}({#IFALIAS}): In half-duplex mode</name>
<correlation_mode>0</correlation_mode>
<correlation_tag/>
<url/>
<status>0</status>
<priority>2</priority>
<description>Last value: {ITEM.LASTVALUE1}.
Please check autonegotiation settings and cabling</description>
<type>0</type>
<manual_close>1</manual_close>
<dependencies/>
<tags/>
</trigger_prototype>
</trigger_prototypes>
<graph_prototypes/>
<host_prototypes/>
<jmx_endpoint/>
</discovery_rule>
</discovery_rules>
<httptests/>
<macros/>
<templates/>
<screens/>
</template>
</templates>
<value_maps>
<value_map>
<name>EtherLike-MIB::dot3StatsDuplexStatus</name>
<mappings>
<mapping>
<value>1</value>
<newvalue>unknown</newvalue>
</mapping>
<mapping>
<value>2</value>
<newvalue>halfDuplex</newvalue>
</mapping>
<mapping>
<value>3</value>
<newvalue>fullDuplex</newvalue>
</mapping>
</mappings>
</value_map>
</value_maps>
</zabbix_export>