10-13-2010 11:48 AM - edited 03-16-2019 01:19 AM
Hey Guys,
My console's showing this error message. I have 4 PRIs on the gateway and all of them went dead when this happened. I had to reboot the router.
%HWECAN-5-TIMEOUT: HWECAN in slot 0 VWIC 3 Device 1 failed to return response for Command/Query 06
When I do sh echo-cancel hardware status 0, it shows following.
VWIC HWECAN 0/2 is UP.
Software version: 9.4.11 , Date: Jul 28 12:32:18 2009
Tail length: 128 Tone disabler type: G.165 Fax notify: Off
Device: VWIC_8MBPS_2TIEC_TL128_MS_2P Max Channels: 64
Both Port0 & Port1 have Local HWECAN Connectivity.
ECAN CH Assigned DSP ID VOICEPORT EC NLP COV LAW
===============================================================
3 yes 0/5:4 0/2/0:23.3 on on on u-Law
4 yes 0/7:4 0/2/0:23.4 on on on u-Law
6 yes 0/5:6 0/2/0:23.6 on on on u-Law
7 yes 0/6:6 0/2/0:23.7 on on on u-Law
10 yes 0/1:3 0/2/0:23.10 on on on u-Law
13 yes 0/6:2 0/2/0:23.13 on on on u-Law
14 yes 0/9:4 0/2/0:23.14 on on on u-Law
16 yes 0/1:4 0/2/0:23.16 on on on u-Law
17 yes 0/10:3 0/2/0:23.17 on on on u-Law
18 yes 0/2:2 0/2/0:23.18 on on on u-Law
19 yes 0/10:5 0/2/0:23.19 on on on u-Law
20 yes 0/2:3 0/2/0:23.20 on on on u-Law
21 yes 0/6:5 0/2/0:23.21 on on on u-Law
22 yes 0/9:1 0/2/0:23.22 on on on u-Law
23 yes 0/10:6 0/2/0:23.23 on on on u-Law
Total assigned channel(s): 15
VWIC HWECAN 0/3 is UP.
Software version: 9.4.11 , Date: Jul 28 12:32:18 2009
Tail length: 128 Tone disabler type: G.165 Fax notify: Off
Device: VWIC_8MBPS_2TIEC_TL128_MS_2P Max Channels: 64
Both Port0 & Port1 have Local HWECAN Connectivity.
ECAN CH Assigned DSP ID VOICEPORT EC NLP COV LAW
===============================================================
1 yes 0/1:1 0/3/0:23.1 on on on u-Law
2 yes 0/1:6 0/3/0:23.2 on on on u-Law
3 yes 0/9:5 0/3/0:23.3 on on on u-Law
5 yes 0/10:1 0/3/0:23.5 on on on u-Law
6 yes 0/9:2 0/3/0:23.6 on on on u-Law
7 yes 0/2:6 0/3/0:23.7 on on on u-Law
8 yes 0/7:6 0/3/0:23.8 on on on u-Law
9 yes 0/11:3 0/3/0:23.9 on on on u-Law
10 yes 0/10:4 0/3/0:23.10 on on on u-Law
11 yes 0/9:3 0/3/0:23.11 on on on u-Law
12 yes 0/2:1 0/3/0:23.12 on on on u-Law
13 yes 0/10:2 0/3/0:23.13 on on on u-Law
14 yes 0/11:6 0/3/0:23.14 on on on u-Law
15 yes 0/1:2 0/3/0:23.15 on on on u-Law
16 yes 0/7:5 0/3/0:23.16 on on on u-Law
17 yes 0/2:4 0/3/0:23.17 on on on u-Law
18 yes 0/7:2 0/3/0:23.18 on on on u-Law
19 yes 0/2:5 0/3/0:23.19 on on on u-Law
20 yes 0/11:2 0/3/0:23.20 on on on u-Law
21 yes 0/11:1 0/3/0:23.21 on on on u-Law
22 yes 0/7:3 0/3/0:23.22 on on on u-Law
23 yes 0/9:6 0/3/0:23.23 on on on u-Law
33 yes 0/6:1 0/3/1:23.1 on on on u-Law
34 yes 0/6:4 0/3/1:23.2 on on on u-Law
35 yes 0/11:4 0/3/1:23.3 on on on u-Law
36 yes 0/11:5 0/3/1:23.4 on on on u-Law
37 yes 0/7:1 0/3/1:23.5 on on on u-Law
38 yes 0/6:3 0/3/1:23.6 on on on u-Law
39 yes 0/5:3 0/3/1:23.7 on on on u-Law
40 yes 0/5:1 0/3/1:23.8 on on on u-Law
Total assigned channel(s): 30
Total device(s) in the slot 2
I did online reading and it suggested replacing the HWECAN module. Does anybody have any experience in this.
Regards
OJ
Solved! Go to Solution.
10-14-2010 06:28 AM
Does the problem resolve itself when the router is reloaded? If so, it's possible that you could be hitting a known bug, CSCtg92548. Unfortunately, it is still being investigated. The only workaround is to remove the hardware ecan and upgrade to 12.4(24)T to get the 128ms ecan coverage.
-Felipe
10-14-2010 05:29 AM
I've used an ECAN daughter card once. IOS 12.4(24)T and newer have baked the 128ms coverage into the standard DSP microcode. If it happens again I would upgrade IOS and yank the daughter card. There's no sense in paying for extra DSPs at this point it seems.
For my curiosity: What necessitated the longer echo cancellation coverage?
10-14-2010 06:14 AM
I think I am missing some here. What you are saying is that IOS 12.4(24)T and higher don't need HW echo cancellation modules.
We were experiencing echo on our gateway. it was suggested to increase the echo cancellation coverage.
Thanks and Regards
OJ
10-14-2010 06:28 AM
Does the problem resolve itself when the router is reloaded? If so, it's possible that you could be hitting a known bug, CSCtg92548. Unfortunately, it is still being investigated. The only workaround is to remove the hardware ecan and upgrade to 12.4(24)T to get the 128ms ecan coverage.
-Felipe
10-14-2010 06:54 AM
It only happened once and yes reloading the router fixed it.
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