[cisco-nas] strange MICA behaviour : Disconnect Reason Info:
(0x6102)
Tassos Chatzithomaoglou
achatz at forthnet.gr
Wed May 19 08:59:59 EDT 2004
Aaron Leonard wrote:
>> 1st question
>> ------------
>> I have an AS5300 with 2 MICA modules which has ~60 success rate. The
>> quite common
>> disconnect reason is the following...DSP is the one that worries me...
>
>
> All this means is that it was the DSP that decided to hang up.
>
>> May 18 18:02:26: Modem State event:
>> State: Call Setup
>> May 18 18:02:26: Modem State event:
>> State: Connect
>> May 18 18:02:26: Modem State event:
>> State: V.8bis Exchange
>> May 18 18:02:26: Modem State event:
>> State: Link
>> May 18 18:02:26: Modem State event:
>> State: Train Up
>> May 18 18:02:38: Modem State event:
>> State: Terminate
>> May 18 18:02:38: End Connect event:
>> Call Timer: 22 secs
>> Disconnect Reason Info: (0x6102)
>> Type (=3 ): Condition occurred during call setup
>> Class (=1 ): DSP condition
>> Reason (=2 ): failure in modem training up
>
>
>> May 18 17:03:55: Modem State event:
>> State: Call Setup
>> May 18 17:03:55: Modem State event:
>> State: Connect
>> May 18 17:03:55: Modem State event:
>> State: V.8bis Exchange
>> May 18 17:03:55: Modem State event:
>> State: Link
>> May 18 17:04:07: Modem State event:
>> State: Train Up
>> May 18 17:04:19: Modem State event:
>> State: Terminate
>> May 18 17:04:19: End Connect event:
>> Call Timer: 22 secs
>> Disconnect Reason Info: (0x6102)
>> Type (=3 ): Condition occurred during call setup
>> Class (=1 ): DSP condition
>> Reason (=2 ): failure in modem training up
>
>
>> May 18 17:18:21: Modem State event:
>> State: Call Setup
>> May 18 17:18:21: Modem State event:
>> State: Connect
>> May 18 17:18:21: Modem State event:
>> State: V.8bis Exchange
>> May 18 17:18:21: Modem State event:
>> State: Link
>> May 18 17:18:21: Modem State event:
>> State: Train Up
>> May 18 17:18:33: Modem State event:
>> State: Terminate
>> May 18 17:18:33: End Connect event:
>> Call Timer: 16 secs
>> Disconnect Reason Info: (0x6102)
>> Type (=3 ): Condition occurred during call setup
>> Class (=1 ): DSP condition
>> Reason (=2 ): failure in modem training up
>
>
>
>> Should i replace the chassis or both the mica modules?
>
>
> I don't see any reason why - these just look like normal modem
> trainup failures.
> If "show modem" shows that certain specific modem lines have much lower
> CSR than others, then this could be a DSP problem however, since
> we made it thru the V.8bis exchange phase etc. OK, it doesn't
> look like it.
>
These are the detailed logs:
Avg Hold Inc calls Out calls Busied Failed No Succ
Mdm Time Succ Fail Succ Fail Out Dial Answer Pct.
1/0 00:18:57 13 2 0 0 0 0 0 87%
1/1 00:11:25 11 6 0 0 0 0 0 65%
1/2 00:12:06 7 10 0 0 0 0 0 41%
* 1/3 00:17:01 12 4 0 0 0 0 0 75%
1/4 00:23:46 8 6 0 0 0 0 0 57%
* 1/5 00:30:19 9 5 0 0 0 0 0 64%
1/6 00:12:26 12 6 0 0 0 0 0 67%
1/7 00:12:30 12 7 0 0 0 0 0 63%
1/8 00:08:43 8 11 0 0 0 0 0 42%
1/9 00:25:31 8 6 0 0 0 0 0 57%
1/10 00:09:56 8 9 0 0 0 0 0 47%
1/11 00:17:34 13 4 0 0 0 0 0 76%
* 1/12 01:17:18 7 1 0 0 0 0 0 88%
C 1/13 00:08:14 10 10 0 0 0 0 0 50%
* 1/14 00:14:47 13 4 0 0 0 0 0 76%
* 1/15 00:07:28 7 13 0 0 0 0 0 35%
* 1/16 00:16:51 13 4 0 0 0 0 0 76%
1/17 00:10:58 7 10 0 0 0 0 0 41%
* 1/18 00:14:13 11 7 0 0 0 0 0 61%
1/19 00:32:52 11 3 0 0 0 0 0 79%
1/20 00:19:24 12 3 0 0 0 0 0 80%
1/21 00:25:19 8 7 0 0 0 0 0 53%
* 1/22 00:36:47 10 2 0 0 0 0 0 83%
1/23 00:11:39 13 4 0 0 0 0 0 76%
* 1/24 00:08:45 11 8 0 0 0 0 0 58%
1/25 00:07:33 12 6 0 0 0 0 0 67%
1/26 00:18:55 8 6 0 0 0 0 0 57%
1/27 00:10:04 11 6 0 0 0 0 0 65%
1/28 00:17:33 11 5 0 0 0 0 0 69%
1/29 00:22:36 8 5 0 0 0 0 0 62%
1/30 00:25:44 8 6 0 0 0 0 0 57%
* 1/31 00:47:06 7 5 0 0 0 0 0 58%
1/32 00:09:14 13 7 0 0 0 0 0 65%
1/33 00:13:19 12 4 0 0 0 0 0 75%
* 1/34 00:22:44 12 3 0 0 0 0 0 80%
1/35 00:14:08 10 6 0 0 0 0 0 63%
* 1/36 00:32:02 8 4 0 0 0 0 0 67%
* 1/37 00:37:26 8 5 0 0 0 0 0 62%
1/38 00:33:27 9 4 0 0 0 0 0 69%
1/39 00:14:51 16 1 0 0 0 0 0 94%
1/40 00:53:46 8 1 0 0 0 0 0 89%
* 1/41 00:29:59 13 1 0 0 0 0 0 93%
* 1/42 00:14:45 15 2 0 0 0 0 0 88%
1/43 00:25:27 13 5 0 0 0 0 0 72%
1/44 00:15:12 11 5 0 0 0 0 0 69%
1/45 00:16:55 12 5 0 0 0 0 0 71%
* 1/46 00:10:47 12 7 0 0 0 0 0 63%
* 1/47 01:34:04 4 3 0 0 0 0 0 57%
1/48 00:11:52 13 4 0 0 0 0 0 76%
1/49 00:10:28 12 6 0 0 0 0 0 67%
1/50 00:27:53 8 5 0 0 0 0 0 62%
1/51 00:10:10 9 8 0 0 0 0 0 53%
1/52 00:49:23 6 8 0 0 0 0 0 43%
1/53 00:04:06 13 7 0 0 0 0 0 65%
1/54 00:07:36 10 8 0 0 0 0 0 56%
1/55 00:11:31 11 6 0 0 0 0 0 65%
1/56 00:14:37 11 6 0 0 0 0 0 65%
* 1/57 00:11:46 11 7 0 0 0 0 0 61%
* 1/58 00:11:02 10 9 0 0 0 0 0 53%
1/59 00:11:35 11 6 0 0 0 0 0 65%
2/0 00:34:36 12 0 0 0 0 0 0 100%
2/1 00:12:42 9 8 0 0 0 0 0 53%
2/2 00:31:35 9 6 0 0 0 0 0 60%
2/3 00:15:16 10 6 0 0 0 0 0 63%
2/4 00:18:38 10 5 0 0 0 0 0 67%
2/5 00:21:02 14 1 0 0 0 0 0 93%
2/6 00:09:20 13 5 0 0 0 0 0 72%
2/7 00:06:27 8 11 0 0 0 0 0 42%
2/8 00:09:48 12 6 0 0 0 0 0 67%
* 2/9 00:34:59 13 4 0 0 0 0 0 76%
2/10 00:11:30 9 8 0 0 0 0 0 53%
2/11 00:16:08 9 8 0 0 0 0 0 53%
2/12 00:27:43 9 4 0 0 0 0 0 69%
* 2/13 00:09:34 14 5 0 0 0 0 0 74%
2/14 00:18:54 11 5 0 0 0 0 0 69%
2/15 00:08:48 12 6 0 0 0 0 0 67%
2/16 00:12:58 14 3 0 0 0 0 0 82%
2/17 00:11:47 8 8 0 0 0 0 0 50%
* 2/18 00:06:08 11 9 0 0 0 0 0 55%
2/19 00:14:16 12 4 0 0 0 0 0 75%
* 2/20 00:08:57 14 5 0 0 0 0 0 74%
* 2/21 00:23:20 11 3 0 0 0 0 0 79%
2/22 00:11:31 12 7 0 0 0 0 0 63%
* 2/23 00:34:06 9 3 0 0 0 0 0 75%
* 2/24 00:14:56 11 5 0 0 0 0 0 69%
2/25 00:15:51 12 4 0 0 0 0 0 75%
2/26 00:32:08 8 4 0 0 0 0 0 67%
* 2/27 00:22:50 11 3 0 0 0 0 0 79%
2/28 00:17:24 11 4 0 0 0 0 0 73%
* 2/29 00:22:08 8 7 0 0 0 0 0 53%
2/30 00:27:52 12 2 0 0 0 0 0 86%
2/31 00:16:17 13 2 0 0 0 0 0 87%
* 2/32 01:11:37 4 4 0 0 0 0 0 50%
2/33 00:17:45 13 2 0 0 0 0 0 87%
2/34 00:11:24 12 5 0 0 0 0 0 71%
* 2/35 00:08:50 12 7 0 0 0 0 0 63%
2/36 00:05:42 11 8 0 0 0 0 0 58%
2/37 00:12:54 10 7 0 0 0 0 0 59%
2/38 00:11:43 10 6 0 0 0 0 0 63%
2/39 00:18:54 7 8 0 0 0 0 0 47%
2/40 00:17:31 11 4 0 0 0 0 0 73%
2/41 00:04:34 10 10 0 0 0 0 0 50%
* 2/42 00:14:33 8 9 0 0 0 0 0 47%
2/43 00:09:06 12 6 0 0 0 0 0 67%
* 2/44 00:09:20 11 8 0 0 0 0 0 58%
2/45 00:18:19 8 7 0 0 0 0 0 53%
* 2/46 00:12:20 13 6 0 0 0 0 0 68%
* 2/47 00:20:08 10 5 0 0 0 0 0 67%
2/48 00:17:14 10 7 0 0 0 0 0 59%
* 2/49 00:15:32 7 9 0 0 0 0 0 44%
2/50 00:14:05 12 4 0 0 0 0 0 75%
2/51 00:09:04 11 6 0 0 0 0 0 65%
2/52 00:08:20 14 5 0 0 0 0 0 74%
2/53 00:07:37 9 11 0 0 0 0 0 45%
2/54 00:43:45 7 3 0 0 0 0 0 70%
* 2/55 00:12:02 9 10 0 0 0 0 0 47%
2/56 00:07:41 8 9 0 0 0 0 0 47%
* 2/57 00:09:59 7 10 0 0 0 0 0 41%
2/58 00:26:49 7 6 0 0 0 0 0 54%
2/59 00:16:03 9 6 0 0 0 0 0 60%
Total: 00:17:03 1243 683 0 0 0 0 0 65%
As you can see there are no specific modems which have problem. Most of them have.
Also "sh contr e1" doesn't show any errors.
>> 2nd question
>> ------------
>> Quite strangely, while issuing "sh modem call-stats" the router
>> crashed (!) with the
>> following stack info.
>
>
>
>> Minimum process stacks:
>> Free/Size Name
>> 5672/6000 Reset ipc queue
>> 5676/6000 HPI Logger
>> 2512/3000 fstp init
>> 2464/3000 allegro libretto init
>> 5608/6000 Microcom DSP download Process
>> 11296/12000 Router Init
>> 8572/12000 Init
>> 5424/6000 RADIUS INITCONFIG
>> 10304/12000 Exec
>> 10432/12000 Mica board Download
>
>
>> Interrupt level stacks:
>> Level Called Unused/Size Name
>> 2 4679 7800/9000 Low IRQ Int Handler
>> 3 616 8272/9000 High IRQ Int Handler
>> 4 5555 8592/9000 Console Uart
>> 6 0 9000/9000 Parity interrupt
>> 7 25747 8600/9000 NMI Interrupt Handler
>
>
>> System was restarted by bus error at PC 0x6034EB0C, address 0x20686F73
>> 5300 Software (C5300-IS-M), Version 12.2(15)T9, RELEASE SOFTWARE (fc2)
>> TAC Support: http://www.cisco.com/tac
>> Compiled Sat 01-Nov-03 01:30 by ccai
>> Image text-base: 0x6000894C, data-base: 0x61574000
>
>
>
>> Stack trace from system failure:
>> FP: 0x648BD458, RA: 0x6034EB0C
>> FP: 0x648BD510, RA: 0x6034D518
>> FP: 0x648BD530, RA: 0x6017B120
>> FP: 0x648BD590, RA: 0x6017B50C
>> FP: 0x648BD648, RA: 0x601845D0
>> FP: 0x648BD680, RA: 0x60185A08
>> FP: 0x648BD698, RA: 0x6036AF68
>> FP: 0x648BD6F0, RA: 0x6037DC00
>
>
>> Bug-tool showed "CSCdy14558" as the possible bug, but this one doesn't
>> refer to 12.2(15)T9
>> which i'm using. Also the bug notes don't refer the ios versions where
>> the bug is solved.
>
>
> No, CSCdy14558. If you can replicate this and are willing
> to capture a core file, then open a TAC case and have the
> TAC engineer reopen and link to the DDTS.
Even if i could replicate it, i don't think i would like to do it, since this is a
production router. Maybe i'll give it a try on our test enviroment...
>
> Aaron
>
--
***************************************
Chatzithomaoglou Anastasios
Network Design & Development Department
FORTHnet S.A.
<achatz at forthnet.gr>
***************************************
More information about the cisco-nas
mailing list