10-31-2013 07:44 AM - edited 07-04-2021 01:11 AM
Hello,
We had to manually reboot our backup WLC. The system was urresponsive and our syslog catched this:
Message: *NBAR2_Task: Oct 30 06:39:55.118: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 08 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.119: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 09 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.117: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 06 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.118: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 07 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.115: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 02 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.116: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 03 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.116: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 04 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.117: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 05 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.115: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 01 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:55.113: #BROFFU-0-DP_CORE_DID_NOT_CRASH: broffu_fp_dapi_cmd.c:5082 Fastpath DP0 core 00 did not crash. No Crashinfo.
Message: *NBAR2_Task: Oct 30 06:39:44.707: #BROFFU-0-DP_READING_CRASH_FILE: broffu_fp_dapi_cmd.c:4511 Heartbeat miss: Reading DP0 crash information.
We didn't find the on the web or within cisco's website.
As per the WLC itself, it usually don't have any AP's registered on it (acts as a backup WLC). It isn't member of a clustered WLC either (7.4 feature).
I'm attaching the crashinfo to this post.
Could be a HW malfunction?
Thanks in advance!
10-31-2013 08:58 AM
Lucas,
You would be better off opening up a TAC case and provide Cisco TAC with this info. They would be able to tell you hopefully the cause.
Sent from Cisco Technical Support iPad App
10-31-2013 02:53 PM
WLC's don't crash unless you have a potential hardware fault.
Open a TAC.
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