This document provides a sample configuration for Embedded Event Manager (EEM) script on Cisco Nexus 7000 Series Switches to monitor the CPU utilization. EEM scripts have been used to automate common diagnostics and troubleshooting scenarios that occur on your device based on network events.
Make sure that you meet these requirements before you attempt this configuration.
Have a basic knowledge of configuration on Nexus 7000 Series Switches.
Have a basic understanding of Embedded Event Manager (EEM) scripts.
The information in this document is based on the Nexus 7000 Series NX-OS devices, started with a cleared (default) configuration. Before using this configuration make sure that you understand the potential impact of any command.
In this section, you are presented with EEM script configuration to monitor the Nexus 7000 CPU utilization, once it gets above a pre-defined threshold (in this example we use 50%) it will start to execute the commands. The output of the commands will get written to the bootflash which has the information gathered during the period of high CPU utilization.
From this output we can diagnose what causes the CPU to jump up periodically. This EEM script should be configured in the default VDC (virtual device context). It will capture “show proc cpu sort” output in each VDC and write the files to bootflash.
This document uses this EEM Script configuration.
Create and register the applet with EEM and enter applet configuration mode.
Enter the command to trigger an event based on SNMP object identifier (OID) cross the entry threshold.
Configure the action statements which trigger the action.
Sample configuration given below,
switch(config)#event manager applet highcpu
switch(config-applet)#event snmp oid 188.8.131.52.184.108.40.206.220.127.116.11.1.6.1 get-type exact entry-op ge entry-val 50 poll-interval 1
switch(config-applet)#action 0.1 syslog msg High CPU DETECTED "show process cpu sort" written to bootflash:highcpu.txt
switch(config-applet)#action 0.2 cli enable
switch(config-applet)#action 0.3 cli show process cpu sort >> bootflash:highcpu.txt
switch(config-applet)#action 0.4 cli show process cpu hist >> bootflash:highcpu.txt
I have not been successful in finding this OID. I have looked in the defualt MIB under CISCO-ENVMON-MIB, and tried using the external cisco-stackwise.mib to find this value. I have searched the forums and don't see this one there. I am l...
Hello everyoneI would really try my best not to be the one asking the stupid questions. Out of dire need I have salvaged a old 875 ADSL Cisco. I have used years before put it in storage and I know its working. I have done a factory reset and have been str...
I am planning for a VoIP install and I need to make sure we have enough power on the 3850 switch to support the phones. The phones consume 13 watts max, switch is 48 ports, there will be a phone plugged into each port, available watts per switch module in...
Hi All, I am currently running Cisco 2800 ME version 18.104.22.168 and have 4 AIR-AP2802I-E-K9 in the environment. Since the setup has been installed we have regular reports of clients disconnecting and when they reconnect everything is fine.&n...