01-03-2012 10:24 PM
Hi there
I'm having some issues on WAAS devices with Kernel_crash 's. How can this be resolved?
sabf-0051-kuruman-wae-1#sh alarm
Critical Alarms:
----------------
None
Major Alarms:
-------------
Alarm ID Module/Submodule Instance
--------------- -------------------- ---------------
1 kernel_crash sysmon kernel
Minor Alarms:
-------------
None
sabf-0051-kuruman-wae-1#
sabf-0051-kuruman-wae-1#sh version
Cisco Wide Area Application Services Software (WAAS)
Copyright (c) 1999-2011 by Cisco Systems, Inc.
Cisco Wide Area Application Services (accelerator-k9) Software Release 4.4.1 (build b12 May 27 2011)
Version: nme-wae-502-4.4.1.12
Compiled 08:42:00 May 27 2011 by damaster
Device Id: 00:1e:7a:12:b9:21
System was restarted on Tue Jan 3 10:33:54 2012.
The system has been up for 21 hours, 48 minutes, 18 seconds.
sabf-0051-kuruman-wae-1#sh disk detail
Physical disk information:
disk00: Present SB2D34EVHBJPAE (h01 c00 i00 l00 - Int DAS-SATA)
114470MB(111.8GB)
Mounted file systems:
MOUNT POINT TYPE DEVICE SIZE INUSE FREE USE%
/sw internal /dev/sdb1 991MB 698MB 293MB 70%
/swstore internal /dev/sdb2 991MB 497MB 494MB 50%
/state internal /dev/sdb3 3967MB 151MB 3816MB 3%
/local/local1 SYSFS /dev/sdb7 5951MB 2084MB 3867MB 35%
/disk00-04 CONTENT /dev/sdb6 96995MB 42674MB 54321MB 43%
.../local1/spool PRINTSPOOL /dev/sdb8 991MB 16MB 975MB 1%
No RAID devices present.
Disk encryption feature is disabled.
sabf-0051-kuruman-wae-1#sh alarm hist detail
Op Sev Alarm ID Module/Submodule Instance
-- --- -------------------- -------------------- --------------------
1 C Ma servicedead nodemgr actastor_watchdog
Jan 3 10:43:45.170 SAST, Processing Error Alarm, #000002, 2000:330003
nodemgr: The actastor_watchdog service died.
2 R Ma servicedead nodemgr actastor_watchdog
Jan 3 10:43:34.869 SAST, Processing Error Alarm, #000002, 2000:330003
nodemgr: The actastor_watchdog service died.
3 R Ma kernel_crash sysmon kernel
Jan 3 10:39:00.527 SAST, Processing Error Alarm, #000001, 1000:445020
Kernel Crash files were detected
Op - Operation: R-Raised, C-Cleared
Sev - Severity: Cr-Critical, Ma-Major, Mi-Minor
sabf-0051-kuruman-wae-1#sh acce
Accelerator Licensed Config State Operational State
----------- -------- ------------ -----------------
cifs Yes Enabled Running
epm Yes Enabled Running
http Yes Enabled Running
mapi Yes Disabled Shutdown
nfs Yes Enabled Running
ssl Yes Enabled Running
video No Enabled Shutdown
sabf-0051-kuruman-wae-1#
Solved! Go to Solution.
01-04-2012 01:00 PM
Hi Andre,
Core files / kernel crash files are generated when an AO goes to unstable state. It then restarts itself after creating a core dump / kernel crash.
If you want Cisco to analyze kernel crash / core dump, please open a TAC case and send sysreport along with all the files from core_dir OR crash directory.
The alarm will remain on if WAE finds any files in core_dir or crash directory. If you want to disable the alarm, you can delete the files from these folders. The alarm will go off automatically once you clean up crash and core_dir folders.
Hope this helps.
Regards.
PS: Please mark this as Answered, if this answers your question.
01-04-2012 01:00 PM
Hi Andre,
Core files / kernel crash files are generated when an AO goes to unstable state. It then restarts itself after creating a core dump / kernel crash.
If you want Cisco to analyze kernel crash / core dump, please open a TAC case and send sysreport along with all the files from core_dir OR crash directory.
The alarm will remain on if WAE finds any files in core_dir or crash directory. If you want to disable the alarm, you can delete the files from these folders. The alarm will go off automatically once you clean up crash and core_dir folders.
Hope this helps.
Regards.
PS: Please mark this as Answered, if this answers your question.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide