hda_dsprm_msg_proc: Unexpected event causing high router CPU and Lockup
On a 3660 router acting as an MGCP gateway this router is going into 99% CPU utilization anywhere from 5 minutes to 16 hours after a reload or initial power up. If I look at the log it shows unexpected events for a NM-HDA card that is not currenty connected to anything that correspond to the time when the router starts to have high cpu utilization. I have replaced the main board as well as all the voice cards and the problem persists. This problem has occured in 12.2T code as well as the latest 12.3(1)a that I am now running. I have those portions of the log file below. At this point the only 2 issue I could see is a bug, or a chassis problem. I have a TAC case open on this but they are almost as stumped as I am. Has anyone ran into a similar issue?
06:40:25: C5421_rx_int: rcv bogus packet len 63875
06:40:25: hda_dsprm_dsp_msg_proc: unexpected event 0, received on slot 4 dsp 2,
06:40:25: pak len 16 0 10 0 0 0 82 0 0 0 0 0 3 0 6 0 16
06:51:04: C5421_rx_int: rcv bogus packet len 63875
06:51:04: hda_dsprm_dsp_msg_proc: unexpected event 0, received on slot 4 dsp 2,
06:51:04: pak len 16 0 10 0 0 0 82 0 0 0 0 0 3 0 6 0 16
09:39:11: %LINK-3-UPDOWN: Interface Foreign Exchange Station 4/0/3, changed stat
e to up
14:24:44: %LINK-3-UPDOWN: Interface Foreign Exchange Station 4/0/3, changed stat
e to up
bad channel id 4483,dsp=2
16:29:25: C5421_rx_int: rcv bogus packet len 63875
Re: hda_dsprm_msg_proc: Unexpected event causing high router CPU
That bug actually was the one that my engineer finally referenced. It turned out by moving the HDA cards out of even numbered slots to only odd numbered slots the problem dissapeared. However,it has been recommended to me that I upgrade to 12.3(3) when it becomes available due to a bug, and also I am getting replacements for 3 NM-HDA cards because they are being recalled for a resistor problem, both issue which could be causing the problem.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...