zabbix_export: version: '6.0' date: '2021-11-21T21:30:04Z' groups: - uuid: 7df96b18c230490a9a0a9e2307226338 name: Templates templates: - uuid: c6da3eaddc6e45748d083ef401d397f7 template: 'Cisco Total' name: 'Cisco Total' description: | ## Overview This template is a smattering of a few templates combined with some custom discovery rules. It has been tested to work with a bunch of Cisco switches and routers. It uses the standard SNMP root for all discovery (using OID's), so it works with most switch/router devices. If you have any issues with it let me know. I exported this from a live system, so the read the dependencies below. **What it does:** * BGP Discovery + Admin Status + Peer State * CPU Discovery + Usage on core * Interface Discovery + Traffic in/out + Errors in/out + Drops in/out * Memory Pool Discovery + Mem free in pool * OSPF Discovery + Neighbor State * Temperature Discovery + temperature of monitor The template creates quite a few graph prototypes and adds them to a screen as well. **Dependencies:** The template had value maps, interface filters and groups associated with it when I cloned it, but I removed them so there shouldn't be any issues with it. If you find an issue importing let me know. I was successful importing default template to a new system. **Other Instructions:** Be sure to set the $SNMP\_COMMUNITY and $CRD\_SNMPV2\_R values. They should both be your SNMP community string. groups: - name: Templates discovery_rules: - uuid: 6686600d55694dd38588511cfd4be267 name: 'Cisco OSPF Discovery' type: SNMP_AGENT snmp_oid: 'discovery[{#SNMPVALUE},1.3.6.1.2.1.14.10.1.6]' key: cisco.ospf.diuscovery delay: '3600' item_prototypes: - uuid: dbcf5a117f7848bc82a51c56df848e2f name: 'ospfNbrState {#SNMPINDEX}' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.14.10.1.6.{#SNMPINDEX}' key: '.1.3.6.1.2.1.14.10.1.6.[{#SNMPINDEX}]' delay: '30' value_type: FLOAT tags: - tag: Application value: OSPF - uuid: 6d90b9c0b64a41bf89020044f7c302e5 name: 'Cisco memory pool discovery' type: SNMP_AGENT snmp_oid: 'discovery[{#MEMNAME},1.3.6.1.4.1.9.9.48.1.1.1.2]' key: ciscoMemoryPoolTable delay: '3600' lifetime: 1d description: '{#MEMNAME} --> A textual name assigned to the memory pool. This object is suitable for output to a human operator, and may also be used to distinguish among the various pool types, especially among dynamic pools.' item_prototypes: - uuid: 5ba45edd63194618a5433866d3f90e59 name: 'Memory - free in pool ''{#MEMNAME}''' type: SNMP_AGENT snmp_oid: '1.3.6.1.4.1.9.9.48.1.1.1.6.{#SNMPINDEX}' key: 'ciscoMemoryPoolFree[{#SNMPINDEX}]' delay: '600' history: 7d units: B description: 'Indicates the number of bytes from the memory pool that are currently unused on the managed device.' tags: - tag: Application value: Cisco trigger_prototypes: - uuid: 97af793d1a4b4010ba7c15ed113b8b85 expression: 'max(/Cisco Total/ciscoMemoryPoolFree[{#SNMPINDEX}],#3)<{$MEM_FREE_MIN_1:"{#MEMNAME}"}' name: 'Cisco: ''Free memory'' in pool ''{#MEMNAME}'' is low [{ITEM.LASTVALUE}]' priority: WARNING dependencies: - name: 'Cisco: ''Free memory'' in pool ''{#MEMNAME}'' is too low [{ITEM.LASTVALUE}]' expression: 'max(/Cisco Total/ciscoMemoryPoolFree[{#SNMPINDEX}],#3)<{$MEM_FREE_MIN_2:"{#MEMNAME}"}' - uuid: f70a2289c9814f6a874d9d951a0714ae expression: 'max(/Cisco Total/ciscoMemoryPoolFree[{#SNMPINDEX}],#3)<{$MEM_FREE_MIN_2:"{#MEMNAME}"}' name: 'Cisco: ''Free memory'' in pool ''{#MEMNAME}'' is too low [{ITEM.LASTVALUE}]' priority: AVERAGE graph_prototypes: - uuid: 3f59b11008e647978cb17c42efa84aad name: '{#SNMPINDEX} Memory Free' graph_items: - color: 1A7C11 item: host: 'Cisco Total' key: 'ciscoMemoryPoolFree[{#SNMPINDEX}]' - uuid: 894726d6164748d18af2191fd0e70936 name: 'Cisco CPU Discovery' type: SNMP_AGENT snmp_oid: 'discovery[{#CPUID},1.3.6.1.4.1.9.9.109.1.1.1.1.2]' key: cpmCPUTotalTable delay: '3600' lifetime: 1d description: '{#CPUID} --> The physical entity can be a CPU chip, a group of CPUs, a CPU card etc. The exact type of this entity is described by its entPhysicalVendorType value.' item_prototypes: - uuid: 11575b6192e84eb9a7baa6920679f73c name: 'CPU - usage on core ''{#CPUID}''' type: SNMP_AGENT snmp_oid: '1.3.6.1.4.1.9.9.109.1.1.1.1.8.{#SNMPINDEX}' key: 'cpmCPUTotal5minRev[{#SNMPINDEX}]' delay: '300' history: 7d units: '%' description: 'The overall CPU busy percentage in the last 5 minute period.' tags: - tag: Application value: Cisco trigger_prototypes: - uuid: 3107380531d243968c3515a3299d6015 expression: 'min(/Cisco Total/cpmCPUTotal5minRev[{#SNMPINDEX}],#3)>{$CPU_PUSED_MAX_1:"{#CPUID}"}' name: 'Cisco: ''CPU usage'' on core ''{#CPUID}'' is high [{ITEM.LASTVALUE}]' url: 'http://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/15095-highcpu.html#anc0' priority: WARNING description: | - Check for a possible security issue. Commonly, high CPU utilization is caused by a security issue, such as a worm or virus operating in your network. This is especially likely to be the cause if there have not been recent changes to the network. Usually, a configuration change, such as adding additional lines to your access lists can mitigate the effects of this problem. Cisco Product Security Advisories and Notices contains information on detection of the most likely causes and specific workarounds. - Make sure all debugging commands in your router are turned off by issuing the undebug all or no debug all commands. For more information on the use of debugging commands, refer to Using Debug Commands. - Are you able to issue show commands on the router? If yes, start collecting more information immediately, using these show commands. - Is the router inaccessible? Can you reproduce this problem? If yes, power-cycle the router and, before reproducing the problem, configure the scheduler interval 500 command. This schedules low priority processes to run every 500 milliseconds, which provides time for you to run some commands, even if CPU usage is at 100 percent. On Cisco 7200 and Cisco 7500 Series Routers, use the scheduler allocate 3000 1000 command. - Does the router show symptoms of high CPU utilization at brief and unpredictable intervals? If yes, periodically collect the output of the show processes cpu command, which shows if the high CPU utilization is caused by interrupts or by a certain process. Use this UNIX script and, based on the first findings, modify the script to collect data needed for further investigation of the issue. The overall CPU busy percentage. dependencies: - name: 'Cisco: ''CPU usage'' on core ''{#CPUID}'' is too high [{ITEM.LASTVALUE}]' expression: 'min(/Cisco Total/cpmCPUTotal5minRev[{#SNMPINDEX}],#3)>{$CPU_PUSED_MAX_2:"{#CPUID}"}' - uuid: fd452a56b62f4d0488d38849c32ddae9 expression: 'min(/Cisco Total/cpmCPUTotal5minRev[{#SNMPINDEX}],#3)>{$CPU_PUSED_MAX_2:"{#CPUID}"}' name: 'Cisco: ''CPU usage'' on core ''{#CPUID}'' is too high [{ITEM.LASTVALUE}]' url: 'http://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/15095-highcpu.html#anc0' priority: AVERAGE description: | - Check for a possible security issue. Commonly, high CPU utilization is caused by a security issue, such as a worm or virus operating in your network. This is especially likely to be the cause if there have not been recent changes to the network. Usually, a configuration change, such as adding additional lines to your access lists can mitigate the effects of this problem. Cisco Product Security Advisories and Notices contains information on detection of the most likely causes and specific workarounds. - Make sure all debugging commands in your router are turned off by issuing the undebug all or no debug all commands. For more information on the use of debugging commands, refer to Using Debug Commands. - Are you able to issue show commands on the router? If yes, start collecting more information immediately, using these show commands. - Is the router inaccessible? Can you reproduce this problem? If yes, power-cycle the router and, before reproducing the problem, configure the scheduler interval 500 command. This schedules low priority processes to run every 500 milliseconds, which provides time for you to run some commands, even if CPU usage is at 100 percent. On Cisco 7200 and Cisco 7500 Series Routers, use the scheduler allocate 3000 1000 command. - Does the router show symptoms of high CPU utilization at brief and unpredictable intervals? If yes, periodically collect the output of the show processes cpu command, which shows if the high CPU utilization is caused by interrupts or by a certain process. Use this UNIX script and, based on the first findings, modify the script to collect data needed for further investigation of the issue. The overall CPU busy percentage. graph_prototypes: - uuid: f23c25f733f045609a99887efd490425 name: 'CPU usage on core ''{#CPUID}''' show_triggers: 'NO' ymin_type_1: FIXED ymax_type_1: FIXED graph_items: - color: 1A7C11 item: host: 'Cisco Total' key: 'cpmCPUTotal5minRev[{#SNMPINDEX}]' - uuid: f9f8c5b38f7a492e88287e558877ed8b name: 'Cisco BGP Peer Enumeration' type: SNMP_AGENT snmp_oid: 'discovery[{#SNMPVALUE},.1.3.6.1.2.1.15.3.1.7]' key: discovery.bgpDescr delay: '3600' lifetime: 1d item_prototypes: - uuid: 74b7e343e2814470a3b32d5c60b53fec name: 'BGP Peer State {#SNMPINDEX}' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.15.3.1.2.{#SNMPINDEX}' key: '.1.3.6.1.2.1.15.3.1.2.[{#SNMPINDEX}]' delay: '30' value_type: FLOAT tags: - tag: Application value: BGP - uuid: 3d02ecb286ea4d7abba63ba69ce8a3a5 name: 'BGP Admin Status {#SNMPINDEX}' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.15.3.1.3.{#SNMPINDEX}' key: '.1.3.6.1.2.1.15.3.1.3.[{#SNMPINDEX}]' delay: '30' value_type: FLOAT tags: - tag: Application value: BGP - uuid: dabcb6fe4e6c41f1a68335915cd6eea8 name: 'Cisco Interface Discovery' type: SNMP_AGENT snmp_oid: 'discovery[{#SNMPVALUE},1.3.6.1.2.1.2.2.1.2]' key: discovery.ifDescr delay: '3600' lifetime: 1d item_prototypes: - uuid: 79e9ed2671c0469eb682da4f7d1707d3 name: '{#SNMPVALUE} - Inbound traffic' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.10.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.10.[{#SNMPINDEX}]' delay: '60' history: 7d value_type: FLOAT units: bps preprocessing: - type: CHANGE_PER_SECOND parameters: - '' - type: MULTIPLIER parameters: - '8' tags: - tag: Application value: Interfaces - uuid: a2f83aec09e44c068175b1c1983ae2c8 name: '{#SNMPVALUE} - Inbound discarded packets' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.13.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.13.[{#SNMPINDEX}]' delay: '60' history: 7d preprocessing: - type: SIMPLE_CHANGE parameters: - '' tags: - tag: Application value: Interfaces - uuid: f8529300d989457b805725b09371f340 name: '{#SNMPVALUE} - Inbound error packets' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.14.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.14.[{#SNMPINDEX}]' delay: '60' history: 7d preprocessing: - type: SIMPLE_CHANGE parameters: - '' tags: - tag: Application value: Interfaces - uuid: 6df35deba4854659897eda892189b459 name: '{#SNMPVALUE} - Outbound traffic' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.16.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.16.[{#SNMPINDEX}]' delay: '60' history: 7d value_type: FLOAT units: bps preprocessing: - type: CHANGE_PER_SECOND parameters: - '' - type: MULTIPLIER parameters: - '8' tags: - tag: Application value: Interfaces - uuid: 2e95784bed984b5faea9a208a4980e33 name: '{#SNMPVALUE} - Outbound discarded packets' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.19.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.19.[{#SNMPINDEX}]' delay: '60' history: 7d preprocessing: - type: SIMPLE_CHANGE parameters: - '' tags: - tag: Application value: Interfaces - uuid: 9a4ee78499b143989c36962dda86bdc7 name: '{#SNMPVALUE} - Outbound error packets' type: SNMP_AGENT snmp_oid: '.1.3.6.1.2.1.2.2.1.20.{#SNMPINDEX}' key: '.1.3.6.1.2.1.2.2.1.20.[{#SNMPINDEX}]' delay: '60' history: 7d preprocessing: - type: SIMPLE_CHANGE parameters: - '' tags: - tag: Application value: Interfaces graph_prototypes: - uuid: f47b4158803e4ff8b7271b21c8f7cad2 name: 'Interface {#SNMPVALUE} Discards and Errors' graph_items: - color: 1A7C11 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.13.[{#SNMPINDEX}]' - sortorder: '1' color: F63100 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.19.[{#SNMPINDEX}]' - sortorder: '2' color: 2774A4 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.14.[{#SNMPINDEX}]' - sortorder: '3' color: A54F10 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.20.[{#SNMPINDEX}]' - uuid: 5ad321f190db4a8db12798e009ce5d59 name: 'Interface {#SNMPVALUE} Traffic' graph_items: - color: 1A7C11 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.10.[{#SNMPINDEX}]' - sortorder: '1' color: F63100 item: host: 'Cisco Total' key: '.1.3.6.1.2.1.2.2.1.16.[{#SNMPINDEX}]' - uuid: f547d466420b4fb385d1399fb632a289 name: 'Cisco Temperature Discovery' type: SNMP_AGENT snmp_oid: 'discovery[{#SNMPVALUE},1.3.6.1.4.1.9.9.13.1.3.1.3]' key: discovery.TempDesc delay: '3600' lifetime: 1d item_prototypes: - uuid: 215efd583f9a45408621dda423bc5302 name: '{#SNMPINDEX} temperature' type: SNMP_AGENT snmp_oid: '1.3.6.1.4.1.9.9.13.1.3.1.3.{#SNMPINDEX}' key: '1.3.6.1.4.1.9.9.13.1.3.1.3.[{#SNMPINDEX}]' delay: '30' value_type: FLOAT units: C tags: - tag: Application value: Temperature graph_prototypes: - uuid: 41bb16bbef9a4001b429458b2f22ee5f name: 'Temperature {#SNMPINDEX}' graph_items: - color: 1A7C11 item: host: 'Cisco Total' key: '1.3.6.1.4.1.9.9.13.1.3.1.3.[{#SNMPINDEX}]' macros: - macro: '{$CPU_PUSED_MAX_1}' value: '85' - macro: '{$CPU_PUSED_MAX_2}' value: '95' - macro: '{$CRD_SNMPV2_R}' value: FillMeIn - macro: '{$MEM_FREE_MIN_1}' value: '5000000' - macro: '{$MEM_FREE_MIN_1:"I/O"}' value: '1400000' - macro: '{$MEM_FREE_MIN_1:"SRAM"}' value: '3000' - macro: '{$MEM_FREE_MIN_2}' value: '1000000' - macro: '{$MEM_FREE_MIN_2:"I/O"}' value: '500000' - macro: '{$MEM_FREE_MIN_2:"SRAM"}' value: '1000' - macro: '{$SNMP_COMMUNITY}' value: FillMeIn dashboards: - uuid: 2be3a51a7a774854bdfbfd587d57d278 name: 'Performance screen' pages: - widgets: - type: GRAPH_PROTOTYPE width: '24' height: '5' fields: - type: INTEGER name: source_type value: '2' - type: INTEGER name: columns value: '1' - type: INTEGER name: rows value: '1' - type: GRAPH_PROTOTYPE name: graphid value: name: 'Temperature {#SNMPINDEX}' host: 'Cisco Total' - type: GRAPH_PROTOTYPE 'y': '5' width: '24' height: '5' fields: - type: INTEGER name: source_type value: '2' - type: INTEGER name: columns value: '1' - type: INTEGER name: rows value: '1' - type: GRAPH_PROTOTYPE name: graphid value: name: 'CPU usage on core ''{#CPUID}''' host: 'Cisco Total' - type: GRAPH_PROTOTYPE 'y': '10' width: '24' height: '5' fields: - type: INTEGER name: source_type value: '2' - type: INTEGER name: columns value: '1' - type: INTEGER name: rows value: '1' - type: GRAPH_PROTOTYPE name: graphid value: name: '{#SNMPINDEX} Memory Free' host: 'Cisco Total' - type: GRAPH_PROTOTYPE 'y': '15' width: '24' height: '5' fields: - type: INTEGER name: source_type value: '2' - type: INTEGER name: columns value: '1' - type: INTEGER name: rows value: '1' - type: GRAPH_PROTOTYPE name: graphid value: name: 'Interface {#SNMPVALUE} Traffic' host: 'Cisco Total' - type: GRAPH_PROTOTYPE 'y': '20' width: '24' height: '5' fields: - type: INTEGER name: source_type value: '2' - type: INTEGER name: columns value: '1' - type: INTEGER name: rows value: '1' - type: GRAPH_PROTOTYPE name: graphid value: name: 'Interface {#SNMPVALUE} Discards and Errors' host: 'Cisco Total'