-
|`90` | ## Template links There are no template links in this template. ## Discovery rules |Name|Description|Type|Key and additional info| |----|-----------|----|----| |Memory Discovery |Discovery of ciscoMemoryPoolTable, a table of memory pool monitoring entries.
http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html
|SNMP |memory.discovery | ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |Memory |{#SNMPVALUE}: Used memory |MIB: CISCO-MEMORY-POOL-MIB
Indicates the number of bytes from the memory pool that are currently in use by applications on the managed device.
Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html
|SNMP |vm.memory.used[ciscoMemoryPoolUsed.{#SNMPINDEX}] | |Memory |{#SNMPVALUE}: Free memory |MIB: CISCO-MEMORY-POOL-MIB
Indicates the number of bytes from the memory pool that are currently unused on the managed device. Note that the sum of ciscoMemoryPoolUsed and ciscoMemoryPoolFree is the total amount of memory in the pool
Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15216-contiguous-memory.html
|SNMP |vm.memory.free[ciscoMemoryPoolFree.{#SNMPINDEX}] | |Memory |{#SNMPVALUE}: Memory utilization |Memory utilization in %
|CALCULATED |vm.memory.util[vm.memory.util.{#SNMPINDEX}]**Expression**:
`last(//vm.memory.used[ciscoMemoryPoolUsed.{#SNMPINDEX}])/(last(//vm.memory.free[ciscoMemoryPoolFree.{#SNMPINDEX}])+last(//vm.memory.used[ciscoMemoryPoolUsed.{#SNMPINDEX}]))*100` | ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |{#SNMPVALUE}: High memory utilization |The system is running out of free memory.
|`min(/Cisco CISCO-MEMORY-POOL-MIB SNMP/vm.memory.util[vm.memory.util.{#SNMPINDEX}],5m)>{$MEMORY.UTIL.MAX}` |AVERAGE | | ## Feedback Please report any issues with the template at https://support.zabbix.com # Cisco CISCO-PROCESS-MIB SNMP ## Overview For Zabbix version: 6.2 and higher ## Setup Refer to the vendor documentation. ## Zabbix configuration No specific Zabbix configuration is required. ### Macros used |Name|Description|Default| |----|-----------|-------| |{$CPU.UTIL.CRIT} |-
|`90` | ## Template links There are no template links in this template. ## Discovery rules |Name|Description|Type|Key and additional info| |----|-----------|----|----| |CPU Discovery |If your IOS device has several CPUs, you must use CISCO-PROCESS-MIB and its object cpmCPUTotal5minRev from the table called cpmCPUTotalTable,
indexed with cpmCPUTotalIndex.
This table allows CISCO-PROCESS-MIB to keep CPU statistics for different physical entities in the router,
like different CPU chips, group of CPUs, or CPUs in different modules/cards.
In case of a single CPU, cpmCPUTotalTable has only one entry.
|SNMP |cpu.discovery | ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |CPU |#{#SNMPINDEX}: CPU utilization |MIB: CISCO-PROCESS-MIB
The cpmCPUTotal5minRev MIB object provides a more accurate view of the performance of the router over time than the MIB objects cpmCPUTotal1minRev and cpmCPUTotal5secRev . These MIB objects are not accurate because they look at CPU at one minute and five second intervals, respectively. These MIBs enable you to monitor the trends and plan the capacity of your network. The recommended baseline rising threshold for cpmCPUTotal5minRev is 90 percent. Depending on the platform, some routers that run at 90 percent, for example, 2500s, can exhibit performance degradation versus a high-end router, for example, the 7500 series, which can operate fine.
Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15215-collect-cpu-util-snmp.html
|SNMP |system.cpu.util[cpmCPUTotal5minRev.{#SNMPINDEX}] | ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |#{#SNMPINDEX}: High CPU utilization |CPU utilization is too high. The system might be slow to respond.
|`min(/Cisco CISCO-PROCESS-MIB SNMP/system.cpu.util[cpmCPUTotal5minRev.{#SNMPINDEX}],5m)>{$CPU.UTIL.CRIT}` |WARNING | | ## Feedback Please report any issues with the template at https://support.zabbix.com # Cisco CISCO-PROCESS-MIB IOS versions 12.0_3_T-12.2_3.5 SNMP ## Overview For Zabbix version: 6.2 and higher ## Setup Refer to the vendor documentation. ## Zabbix configuration No specific Zabbix configuration is required. ### Macros used |Name|Description|Default| |----|-----------|-------| |{$CPU.UTIL.CRIT} |-
|`90` | ## Template links There are no template links in this template. ## Discovery rules |Name|Description|Type|Key and additional info| |----|-----------|----|----| |CPU Discovery |If your IOS device has several CPUs, you must use CISCO-PROCESS-MIB and its object cpmCPUTotal5minRev from the table called cpmCPUTotalTable,
indexed with cpmCPUTotalIndex.
This table allows CISCO-PROCESS-MIB to keep CPU statistics for different physical entities in the router,
like different CPU chips, group of CPUs, or CPUs in different modules/cards.
In case of a single CPU, cpmCPUTotalTable has only one entry.
|SNMP |cpu.discovery | ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |CPU |{#SNMPVALUE}: CPU utilization |MIB: CISCO-PROCESS-MIB
The overall CPU busy percentage in the last 5 minute
period. This object deprecates the avgBusy5 object from
the OLD-CISCO-SYSTEM-MIB. This object is deprecated
by cpmCPUTotal5minRev which has the changed range
of value (0..100).
Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15215-collect-cpu-util-snmp.html
|SNMP |system.cpu.util[cpmCPUTotal5min.{#SNMPINDEX}] | ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |{#SNMPVALUE}: High CPU utilization |CPU utilization is too high. The system might be slow to respond.
|`min(/Cisco CISCO-PROCESS-MIB IOS versions 12.0_3_T-12.2_3.5 SNMP/system.cpu.util[cpmCPUTotal5min.{#SNMPINDEX}],5m)>{$CPU.UTIL.CRIT}` |WARNING | | ## Feedback Please report any issues with the template at https://support.zabbix.com # Cisco OLD-CISCO-CPU-MIB SNMP ## Overview For Zabbix version: 6.2 and higher ## Setup Refer to the vendor documentation. ## Zabbix configuration No specific Zabbix configuration is required. ### Macros used |Name|Description|Default| |----|-----------|-------| |{$CPU.UTIL.CRIT} |-
|`90` | ## Template links There are no template links in this template. ## Discovery rules ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |CPU |CPU utilization |MIB: OLD-CISCO-CPU-MIB
5 minute exponentially-decayed moving average of the CPU busy percentage.
Reference: http://www.cisco.com/c/en/us/support/docs/ip/simple-network-management-protocol-snmp/15215-collect-cpu-util-snmp.html
|SNMP |system.cpu.util[avgBusy5] | ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |High CPU utilization |CPU utilization is too high. The system might be slow to respond.
|`min(/Cisco OLD-CISCO-CPU-MIB SNMP/system.cpu.util[avgBusy5],5m)>{$CPU.UTIL.CRIT}` |WARNING | | ## Feedback Please report any issues with the template at https://support.zabbix.com # Cisco Inventory SNMP ## Overview For Zabbix version: 6.2 and higher ## Setup Refer to the vendor documentation. ## Zabbix configuration No specific Zabbix configuration is required. ## Template links There are no template links in this template. ## Discovery rules |Name|Description|Type|Key and additional info| |----|-----------|----|----| |Entity Serial Numbers Discovery |-
|SNMP |entity_sn.discovery**Filter**:
AND- {#ENT_SN} MATCHES_REGEX `.+`
- {#ENT_CLASS} MATCHES_REGEX `^3$`
| ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |Inventory |Hardware model name |MIB: ENTITY-MIB
|SNMP |system.hw.model**Preprocessing**:
- DISCARD_UNCHANGED_HEARTBEAT: `1d`
| |Inventory |Hardware serial number |MIB: ENTITY-MIB
|SNMP |system.hw.serialnumber**Preprocessing**:
- DISCARD_UNCHANGED_HEARTBEAT: `1d`
| |Inventory |Operating system |MIB: SNMPv2-MIB
|SNMP |system.sw.os[sysDescr.0]**Preprocessing**:
- REGEX: `Version (.+), RELEASE \1`
- DISCARD_UNCHANGED_HEARTBEAT: `1d`
| |Inventory |{#ENT_NAME}: Hardware serial number |MIB: ENTITY-MIB
|SNMP |system.hw.serialnumber[entPhysicalSerialNum.{#SNMPINDEX}]**Preprocessing**:
- DISCARD_UNCHANGED_HEARTBEAT: `1d`
| ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |Device has been replaced |Device serial number has changed. Ack to close
|`last(/Cisco Inventory SNMP/system.hw.serialnumber,#1)<>last(/Cisco Inventory SNMP/system.hw.serialnumber,#2) and length(last(/Cisco Inventory SNMP/system.hw.serialnumber))>0` |INFO |Manual close: YES
| |Operating system description has changed |Operating system description has changed. Possible reasons that system has been updated or replaced. Ack to close.
|`last(/Cisco Inventory SNMP/system.sw.os[sysDescr.0],#1)<>last(/Cisco Inventory SNMP/system.sw.os[sysDescr.0],#2) and length(last(/Cisco Inventory SNMP/system.sw.os[sysDescr.0]))>0` |INFO |Manual close: YES
| |{#ENT_NAME}: Device has been replaced |Device serial number has changed. Ack to close
|`last(/Cisco Inventory SNMP/system.hw.serialnumber[entPhysicalSerialNum.{#SNMPINDEX}],#1)<>last(/Cisco Inventory SNMP/system.hw.serialnumber[entPhysicalSerialNum.{#SNMPINDEX}],#2) and length(last(/Cisco Inventory SNMP/system.hw.serialnumber[entPhysicalSerialNum.{#SNMPINDEX}]))>0` |INFO |Manual close: YES
| ## Feedback Please report any issues with the template at https://support.zabbix.com # Cisco CISCO-ENVMON-MIB SNMP ## Overview For Zabbix version: 6.2 and higher ## Setup Refer to the vendor documentation. ## Zabbix configuration No specific Zabbix configuration is required. ### Macros used |Name|Description|Default| |----|-----------|-------| |{$FAN_CRIT_STATUS:"critical"} |-
|`3` | |{$FAN_CRIT_STATUS:"shutdown"} |-
|`4` | |{$FAN_WARN_STATUS:"notFunctioning"} |-
|`6` | |{$FAN_WARN_STATUS:"warning"} |-
|`2` | |{$PSU_CRIT_STATUS:"critical"} |-
|`3` | |{$PSU_CRIT_STATUS:"shutdown"} |-
|`4` | |{$PSU_WARN_STATUS:"notFunctioning"} |-
|`6` | |{$PSU_WARN_STATUS:"warning"} |-
|`2` | |{$TEMP_CRIT:"CPU"} |-
|`75` | |{$TEMP_CRIT_LOW} |-
|`5` | |{$TEMP_CRIT_STATUS} |-
|`3` | |{$TEMP_CRIT} |-
|`60` | |{$TEMP_DISASTER_STATUS} |-
|`4` | |{$TEMP_WARN:"CPU"} |-
|`70` | |{$TEMP_WARN_STATUS} |-
|`2` | |{$TEMP_WARN} |-
|`50` | ## Template links There are no template links in this template. ## Discovery rules |Name|Description|Type|Key and additional info| |----|-----------|----|----| |FAN Discovery |The table of fan status maintained by the environmental monitor.
|SNMP |fan.discovery | |PSU Discovery |The table of power supply status maintained by the environmental monitor card.
|SNMP |psu.discovery | |Temperature Discovery |Discovery of ciscoEnvMonTemperatureTable (ciscoEnvMonTemperatureDescr), a table of ambient temperature status
maintained by the environmental monitor.
|SNMP |temperature.discovery | ## Items collected |Group|Name|Description|Type|Key and additional info| |-----|----|-----------|----|---------------------| |Fans |{#SENSOR_INFO}: Fan status |MIB: CISCO-ENVMON-MIB
|SNMP |sensor.fan.status[ciscoEnvMonFanState.{#SNMPINDEX}] | |Power supply |{#SENSOR_INFO}: Power supply status |MIB: CISCO-ENVMON-MIB
|SNMP |sensor.psu.status[ciscoEnvMonSupplyState.{#SNMPINDEX}] | |Temperature |{#SNMPVALUE}: Temperature |MIB: CISCO-ENVMON-MIB
The current measurement of the test point being instrumented.
|SNMP |sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}] | |Temperature |{#SNMPVALUE}: Temperature status |MIB: CISCO-ENVMON-MIB
The current state of the test point being instrumented.
|SNMP |sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}] | ## Triggers |Name|Description|Expression|Severity|Dependencies and additional info| |----|-----------|----|----|----| |{#SENSOR_INFO}: Fan is in critical state |Please check the fan unit
|`count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.fan.status[ciscoEnvMonFanState.{#SNMPINDEX}],#1,"eq","{$FAN_CRIT_STATUS:\"critical\"}")=1 or count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.fan.status[ciscoEnvMonFanState.{#SNMPINDEX}],#1,"eq","{$FAN_CRIT_STATUS:\"shutdown\"}")=1` |AVERAGE | | |{#SENSOR_INFO}: Fan is in warning state |Please check the fan unit
|`count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.fan.status[ciscoEnvMonFanState.{#SNMPINDEX}],#1,"eq","{$FAN_WARN_STATUS:\"warning\"}")=1 or count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.fan.status[ciscoEnvMonFanState.{#SNMPINDEX}],#1,"eq","{$FAN_WARN_STATUS:\"notFunctioning\"}")=1` |WARNING |**Depends on**:
- {#SENSOR_INFO}: Fan is in critical state
| |{#SENSOR_INFO}: Power supply is in critical state |Please check the power supply unit for errors
|`count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.psu.status[ciscoEnvMonSupplyState.{#SNMPINDEX}],#1,"eq","{$PSU_CRIT_STATUS:\"critical\"}")=1 or count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.psu.status[ciscoEnvMonSupplyState.{#SNMPINDEX}],#1,"eq","{$PSU_CRIT_STATUS:\"shutdown\"}")=1` |AVERAGE | | |{#SENSOR_INFO}: Power supply is in warning state |Please check the power supply unit for errors
|`count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.psu.status[ciscoEnvMonSupplyState.{#SNMPINDEX}],#1,"eq","{$PSU_WARN_STATUS:\"warning\"}")=1 or count(/Cisco CISCO-ENVMON-MIB SNMP/sensor.psu.status[ciscoEnvMonSupplyState.{#SNMPINDEX}],#1,"eq","{$PSU_WARN_STATUS:\"notFunctioning\"}")=1` |WARNING |**Depends on**:
- {#SENSOR_INFO}: Power supply is in critical state
| |{#SNMPVALUE}: Temperature is above warning threshold |This trigger uses temperature sensor values as well as temperature sensor status if available
|`avg(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_WARN:"{#SNMPVALUE}"} or last(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_WARN_STATUS} `Recovery expression:
`max(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)<{$TEMP_WARN:"{#SNMPVALUE}"}-3` |WARNING |**Depends on**:
- {#SNMPVALUE}: Temperature is above critical threshold
| |{#SNMPVALUE}: Temperature is above critical threshold |This trigger uses temperature sensor values as well as temperature sensor status if available
|`avg(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_CRIT:"{#SNMPVALUE}"} or last(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_CRIT_STATUS} or last(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.status[ciscoEnvMonTemperatureState.{#SNMPINDEX}])={$TEMP_DISASTER_STATUS} `Recovery expression:
`max(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)<{$TEMP_CRIT:"{#SNMPVALUE}"}-3` |HIGH | | |{#SNMPVALUE}: Temperature is too low |-
|`avg(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)<{$TEMP_CRIT_LOW:"{#SNMPVALUE}"}`Recovery expression:
`min(/Cisco CISCO-ENVMON-MIB SNMP/sensor.temp.value[ciscoEnvMonTemperatureValue.{#SNMPINDEX}],5m)>{$TEMP_CRIT_LOW:"{#SNMPVALUE}"}+3` |AVERAGE | | ## Feedback Please report any issues with the template at https://support.zabbix.com