
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2017 08:52 AM - edited 03-01-2019 06:13 PM
Hi everyone,
I have an applet configured to monitor CPU going above 50%, this was working previously but it suddenly stopped appending on the file. The file system has space on it. I also did a show "show clock - append sup-bootdisk:TEST-CLOCK.tx" and it worked. The event manager registers the event but it doesn't write. Here is my config:
event manager scheduler script thread class default number 1
event manager applet high_CPU
event snmp oid "1.3.6.1.4.1.9.9.109.1.1.1.1.10" get-type next entry-op ge entry-val "50" exit-op le exit-val "5" poll-interval 5
action 0.0 syslog msg "High CPU DETECTED. Please wait logging Information to sup-bootdisk:high_cpu_BOTMAN01.txt"
action 0.1 cli command "enable"
action 0.2 cli command "term exec prompt timestamp"
action 0.3 cli command "term len 0"
action 1.1 cli command "show clock | append sup-bootdisk:high_cpu_BOTMAN01.txt"
action 1.2 cli command "show processes cpu sorted | append sup-bootdisk:high_cpu_BOTMAN01.txt"
action 1.3 cli command "show processes cpu detailed | append sup-bootdisk:high_cpu_BOTMAN01.txt"
action 1.4 cli command "show ip route summary | append sup-bootdisk:high_cpu_BOTMAN01.txt"
action 1.5 cli command "show ip route | include 00:00: | append sup-bootdisk:high_cpu_BOTMAN01.txt"
action 2.0 cli command "end"
show event manager history events
No. Time of Event Event Type Name
1 Wed Oct25 01:08:51 2017 snmp applet: high_CPU
2 Thu Oct26 13:42:52 2017 snmp applet: high_CPU
3 Sat Oct28 01:06:09 2017 snmp applet: high_CPU
4 Mon Oct30 01:08:02 2017 snmp applet: high_CPU
5 Mon Oct30 09:18:26 2017 snmp applet: high_CPU
6 Mon Oct30 09:29:46 2017 snmp applet: high_CPU
7 Mon Oct30 09:31:26 2017 snmp applet: high_CPU
8 Mon Oct30 09:32:21 2017 snmp applet: high_CPU
9 Mon Oct30 09:32:31 2017 snmp applet: high_CPU
10 Mon Oct30 09:41:42 2017 snmp applet: high_CPU
The device is a 6504-E running 12.2(33)SXH6
Regards
Solved! Go to Solution.
- Labels:
-
Network Management
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2017 02:22 PM
If you have AAA command authorization configured, it could be blocking the commands. Enable "debug event manager action cli" and see what output you get.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2017 08:54 AM
Hi Hiram
Could you please paste the output of "show file system". Just want to make sure if you have sup-bootdisk: or sup-bootflash:.
Also, could you please perform the below test:
copy run sup-bootdisk:startup-config.txt
--Vinit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2017 08:59 AM
Hi Vinit,
File Systems:
Size(b) Free(b) Type Flags Prefixes
- - opaque rw system:
- - opaque rw tmpsys:
- - opaque ro flexwan-fpd:
* 511705088 511705088 disk rw disk0:#
- - disk rw disk1:
512024576 157442048 disk rw sup-bootdisk: sup-bootflash:#
73138346 0 opaque ro sup-microcode:
0 199835804 opaque wo sup-image:
129004 128208 nvram rw const_nvram:
1964024 1939175 nvram rw nvram:
- - opaque rw null:
- - opaque ro tar:
- - network rw tftp:
- - opaque wo syslog:
65536000 65196656 flash rw bootflash:
- - network rw rcp:
- - network rw ftp:
- - network rw http:
- - network rw scp:
- - network rw https:
- - opaque ro cns:
32055296 32055296 flash rw ssc4-disk0:
15990784 15990784 flash rw dfc#2-bootflash:
#copy running-config sup-bootdisk:startup-config.txt
Destination filename [startup-config.txt]?
19846 bytes copied in 2.888 secs (6872 bytes/sec)

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-30-2017 02:22 PM
If you have AAA command authorization configured, it could be blocking the commands. Enable "debug event manager action cli" and see what output you get.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-01-2017 11:22 AM
Hi Joe,
Thanks for your help
I activated the debug, I see Command Authorization Failed. I entered "event manager session cli username <username>", let's hope that fixes it.
