5.02021-11-21T21:30:01ZTemplatesCisco TotalCisco Total## 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.
TemplatesBGPCiscoInterfacesOSPFTemperatureCisco OSPF DiscoverySNMP_AGENTdiscovery[{#SNMPVALUE},1.3.6.1.2.1.14.10.1.6]cisco.ospf.diuscovery3600ospfNbrState {#SNMPINDEX}SNMP_AGENT.1.3.6.1.2.1.14.10.1.6.{#SNMPINDEX}.1.3.6.1.2.1.14.10.1.6.[{#SNMPINDEX}]30FLOATOSPFCisco memory pool discoverySNMP_AGENTdiscovery[{#MEMNAME},1.3.6.1.4.1.9.9.48.1.1.1.2]ciscoMemoryPoolTable36001d{#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}]{Cisco Total: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}]AVERAGE{#SNMPINDEX} Memory Free1A7C11- Cisco TotalciscoMemoryPoolFree[{#SNMPINDEX}]
Cisco CPU DiscoverySNMP_AGENTdiscovery[{#CPUID},1.3.6.1.4.1.9.9.109.1.1.1.1.2]cpmCPUTotalTable36001d{#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}]{Cisco Total: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- Cisco TotalcpmCPUTotal5minRev[{#SNMPINDEX}]
Cisco BGP Peer EnumerationSNMP_AGENTdiscovery[{#SNMPVALUE},.1.3.6.1.2.1.15.3.1.7]discovery.bgpDescr36001dBGP Peer State {#SNMPINDEX}SNMP_AGENT.1.3.6.1.2.1.15.3.1.2.{#SNMPINDEX}.1.3.6.1.2.1.15.3.1.2.[{#SNMPINDEX}]30FLOATBGPBGP Admin Status {#SNMPINDEX}SNMP_AGENT.1.3.6.1.2.1.15.3.1.3.{#SNMPINDEX}.1.3.6.1.2.1.15.3.1.3.[{#SNMPINDEX}]30FLOATBGPCisco Interface DiscoverySNMP_AGENTdiscovery[{#SNMPVALUE},1.3.6.1.2.1.2.2.1.2]discovery.ifDescr36001d{#SNMPVALUE} - Inbound trafficSNMP_AGENT.1.3.6.1.2.1.2.2.1.10.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.10.[{#SNMPINDEX}]607dFLOATbpsInterfacesCHANGE_PER_SECONDMULTIPLIER8{#SNMPVALUE} - Inbound discarded packetsSNMP_AGENT.1.3.6.1.2.1.2.2.1.13.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.13.[{#SNMPINDEX}]607dInterfacesSIMPLE_CHANGE{#SNMPVALUE} - Inbound error packetsSNMP_AGENT.1.3.6.1.2.1.2.2.1.14.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.14.[{#SNMPINDEX}]607dInterfacesSIMPLE_CHANGE{#SNMPVALUE} - Outbound trafficSNMP_AGENT.1.3.6.1.2.1.2.2.1.16.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.16.[{#SNMPINDEX}]607dFLOATbpsInterfacesCHANGE_PER_SECONDMULTIPLIER8{#SNMPVALUE} - Outbound discarded packetsSNMP_AGENT.1.3.6.1.2.1.2.2.1.19.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.19.[{#SNMPINDEX}]607dInterfacesSIMPLE_CHANGE{#SNMPVALUE} - Outbound error packetsSNMP_AGENT.1.3.6.1.2.1.2.2.1.20.{#SNMPINDEX}.1.3.6.1.2.1.2.2.1.20.[{#SNMPINDEX}]607dInterfacesSIMPLE_CHANGEInterface {#SNMPVALUE} Discards and Errors1A7C11- Cisco Total.1.3.6.1.2.1.2.2.1.13.[{#SNMPINDEX}]
1F63100- Cisco Total.1.3.6.1.2.1.2.2.1.19.[{#SNMPINDEX}]
22774A4- Cisco Total.1.3.6.1.2.1.2.2.1.14.[{#SNMPINDEX}]
3A54F10- Cisco Total.1.3.6.1.2.1.2.2.1.20.[{#SNMPINDEX}]
Interface {#SNMPVALUE} Traffic1A7C11- Cisco Total.1.3.6.1.2.1.2.2.1.10.[{#SNMPINDEX}]
1F63100- Cisco Total.1.3.6.1.2.1.2.2.1.16.[{#SNMPINDEX}]
Cisco Temperature DiscoverySNMP_AGENTdiscovery[{#SNMPVALUE},1.3.6.1.4.1.9.9.13.1.3.1.3]discovery.TempDesc36001d{#SNMPINDEX} temperatureSNMP_AGENT1.3.6.1.4.1.9.9.13.1.3.1.3.{#SNMPINDEX}1.3.6.1.4.1.9.9.13.1.3.1.3.[{#SNMPINDEX}]30FLOATCTemperatureTemperature {#SNMPINDEX}1A7C11- Cisco Total1.3.6.1.4.1.9.9.13.1.3.1.3.[{#SNMPINDEX}]
{$CPU_PUSED_MAX_1}85{$CPU_PUSED_MAX_2}95{$CRD_SNMPV2_R}FillMeIn{$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{$SNMP_COMMUNITY}FillMeInPerformance screen2820Temperature {#SNMPINDEX}Cisco Total500100001100000220CPU usage on core '{#CPUID}'Cisco Total500100011100000220{#SNMPINDEX} Memory FreeCisco Total500100021100000220Interface {#SNMPVALUE} TrafficCisco Total500100031100000220Interface {#SNMPVALUE} Discards and ErrorsCisco Total5001000511000002