5.02021-11-21T21:21:59ZZZZ-TPL: Parts Networktpl_part_network_cisco_all_performancetpl_part_network_cisco_all_performance## Overview
Template for all Cisco devices which support the CISCO-MEMORY-POOL-MIB and CISCO-PROCESS-MIB.
Discovery all CPUs and memory pools with dynamic trigger thresholds (macro context) and flapping prevention (use of .max()/.min() functions).
You need to create a user macro on the template or global level with name {$CRD\_SNMPV2\_R} = "yourSNMPv2ReadCommunity".
## Author
Valentin Weber
ZZZ-TPL: Parts NetworkCiscoLLD of memory poolsSNMP_AGENTdiscovery[{#MEMNAME},1.3.6.1.4.1.9.9.48.1.1.1.2]ciscoMemoryPoolTable864007d{#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.Memory - free in pool '{#MEMNAME}'SNMP_AGENT1.3.6.1.4.1.9.9.48.1.1.1.6.{#SNMPINDEX}ciscoMemoryPoolFree[{#SNMPINDEX}]6007dBIndicates the number of bytes from the memory pool that are currently unused on the managed device.Cisco{max(#3)}<{$MEM_FREE_MIN_1:"{#MEMNAME}"}Cisco: 'Free memory' in pool '{#MEMNAME}' is low [{ITEM.LASTVALUE}]WARNINGCisco: 'Free memory' in pool '{#MEMNAME}' is too low [{ITEM.LASTVALUE}]{tpl_part_network_cisco_all_performance:ciscoMemoryPoolFree[{#SNMPINDEX}].max(#3)}<{$MEM_FREE_MIN_2:"{#MEMNAME}"}{max(#3)}<{$MEM_FREE_MIN_2:"{#MEMNAME}"}Cisco: 'Free memory' in pool '{#MEMNAME}' is too low [{ITEM.LASTVALUE}]AVERAGELLD of CPUSNMP_AGENTdiscovery[{#CPUID},1.3.6.1.4.1.9.9.109.1.1.1.1.2]cpmCPUTotalTable864007d{#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.CPU - usage on core '{#CPUID}'SNMP_AGENT1.3.6.1.4.1.9.9.109.1.1.1.1.8.{#SNMPINDEX}cpmCPUTotal5minRev[{#SNMPINDEX}]3007d%The overall CPU busy percentage in the last 5 minute period.Cisco{min(#3)}>{$CPU_PUSED_MAX_1:"{#CPUID}"}Cisco: 'CPU usage' on core '{#CPUID}' is high [{ITEM.LASTVALUE}]http://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/15095-highcpu.html#anc0WARNING- 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.Cisco: 'CPU usage' on core '{#CPUID}' is too high [{ITEM.LASTVALUE}]{tpl_part_network_cisco_all_performance:cpmCPUTotal5minRev[{#SNMPINDEX}].min(#3)}>{$CPU_PUSED_MAX_2:"{#CPUID}"}{min(#3)}>{$CPU_PUSED_MAX_2:"{#CPUID}"}Cisco: 'CPU usage' on core '{#CPUID}' is too high [{ITEM.LASTVALUE}]http://www.cisco.com/c/en/us/support/docs/routers/10000-series-routers/15095-highcpu.html#anc0AVERAGE- 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.CPU usage on core '{#CPUID}'NOFIXEDFIXED1A7C11- tpl_part_network_cisco_all_performancecpmCPUTotal5minRev[{#SNMPINDEX}]
{$CPU_PUSED_MAX_1}85{$CPU_PUSED_MAX_2}95{$MEM_FREE_MIN_1}5000000{$MEM_FREE_MIN_1:"I/O"}1400000{$MEM_FREE_MIN_1:"SRAM"}3000{$MEM_FREE_MIN_2}1000000{$MEM_FREE_MIN_2:"I/O"}500000{$MEM_FREE_MIN_2:"SRAM"}1000