[cisco-nas] [Fwd: Re: Modems not responding on cisco AS5300.]

[Aaron Leonard]

Tassos,

Thanks for catching the typo - yes, this bug is CSCei63851:

CSCei63851 AS5300: mica modems randomly marked as bad in any version
afer 12.3(6)

The footprint is that the following event will appear in the modem log:

Jul 17 14:32:02.938 UTC-3: Out of Service event:
Cause: Onhook/Offhook failure

At which point the modem is marked Bad.

The regression seems to have gone into IOS right after 12.3(6), before
the next release of mainline IOS hit (which was 12.3(9).) I believe all
rebuilds in 12.3(6) (i.e. 12.3(6a) .. 12.3(6f)) are immune.

The bug doesn't affect *everybody*.

Btw, this is not the o.p.'s issue - in the CSCsi63851 case, when the
modem is marked Bad, subsequent incoming calls cannot land on it.

Aaron

------------------------------------------------------------------------

> Quite strangely, i have 2 AS5300s running 12.3(23) for over a year and i believe (are "Busied Out" calls due to bug?) i 
> haven't met this problem.
>
> AS5300-1#sh modem sum
> Avg Hold     Incoming calls       Outgoing calls     Busied   Failed   No   Succ
>    Time     Succ   Fail  Avail   Succ   Fail  Avail   Out      Dial     Ans  Pct.
> 00:32:34 515632  31270     89      0      0      0     186        0    12   94%
>
> AS5300-2#sh modem sum
> Avg Hold     Incoming calls       Outgoing calls     Busied   Failed   No   Succ
>    Time     Succ   Fail  Avail   Succ   Fail  Avail   Out      Dial     Ans  Pct.
> 00:32:14 224905  13652    116      0      0      0     192        0     7   94%
>
> btw, bug-id should be CSCei63851 ;) and it's quite annoying that something like this happened in the middle of an ios 
> release.
> Was it too difficult to find the differences between 12.3(6)d and 12.3(6)e?
>
> --
> Tassos
>
>
> Aaron Leonard wrote on 26/8/2008 6:25 ??:
>   
>> Oh yeah - CSCsi638651, which we never did figure out.  Actually,
>> anything in 12.3(6x) and before should be good.
>>
>> Aaron
>>
>> -------- Original Message --------
>> Subject: 	Re: [cisco-nas] Modems not responding on cisco AS5300.
>> Date: 	Tue, 26 Aug 2008 10:20:58 +0800
>> From: 	Mark Tinka <mtinka at globaltransit.net>
>> Reply-To: 	mtinka at globaltransit.net
>> Organization: 	Global Transit International
>> To: 	cisco-nas at puck.nether.net
>> CC: 	Aaron Leonard <Aaron at cisco.com>, Joseph Mays <mays at win.net>, Mike
>> Andrews <mandrews at bit0.com>
>> References: 	<081301c906e2$03cf90c0$0a2118d8 at engineering01>
>> <0b1301c9070d$87bc8ca0$0a2118d8 at engineering01> <48B34BE2.7080902 at Cisco.COM>
>>
>>
>>
>> On Tuesday 26 August 2008 08:18:42 Aaron Leonard wrote:
>>
>>     
>>> In any case, the guidance below is still generally
>>> applicable - i.e. run latest code (2.9.5.0); turn on
>>> modem recovery.
>>>       
>> You also want to run an IOS revision no later than 12.3(5)f.
>>
>> Anything more recent than this will continuously cause your 
>> modems to go into a BAD state.
>>
>> Cheers,
>>
>> Mark.
>>
>>
>> _______________________________________________
>> cisco-nas mailing list
>> cisco-nas at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-nas
>>
>>