Loading...
Loading...
Could provide fatal errors/issues for System 360 -- Monitoring and Log Analytics or inaccurate data in deployment if logstash service randomly stops/starts.
High load average alarms seen every 6 hours, "Process Down" alarm on dashboard, or ISE GUI is temporarily unresponsive. The following might show in the output of: show logging system ade/messages | include oom-killer ... kernel: [318329.129440] swapoff invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 ... kernel: swapoff invoked oom-killer: gfp_mask=0x6200ca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0
Seen with ISE 3.2 patch 6 and 7, 3.3 patch 3, and 3.4 no patch. High load could be seen on any system. Process Down alarms will only been seen when using System 360 Monitoring and Log Analytics
Fixed in: 3.1 patch 10 3.2 patch 8 (release date TBD) 3.3 patch 4 3.4 patch 1 If a workaround is absolutely necessary contact TAC to remove the cron entry manually via root access.
There was a cron.cleanup script introduced in 3.2 patch 6, 3.3 patch 3, and 3.4 that runs swapoff/swapon every 6 hours as a workaround to an OS bug that was causing high swap utilization. This can impact disk i/o for about 10 minutes after the swapoff/swapon script is run. 10:00:00 PM runq-sz plist-sz ldavg-1 ldavg-5 ldavg-15 blocked 04:00:00 AM 2 6376 2.70 1.61 1.44 0 04:10:00 AM 6 6390 44.78 97.64 52.32 0 04:20:00 AM 2 6447 1.25 14.25 28.04 0 10:00:00 PM kbswpfree kbswpused %swpused kbswpcad %swpcad 04:00:00 AM 5213952 2978044 36.35 232912 7.82 04:10:00 AM 8191996 0 0.00 0 0.00 04:20:00 AM 8111448 80548 0.98 1300 1.61
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.