[cisco-nas] AS5300 modems busied out - 12.3.18

[Aaron Leonard]

Modem recovery can automatically busy out modems, if it should see 
excessive failures on certain modems and decide that it wants to 
"recover" the module.

There are probably some other reasons why the router will decide 
automatically to busy out modems, ... oh, I just though of one, that 
little featurette where where we proactively busy out modems to signal 
to the switch that the trunks are busy to force the switch to hunt to a 
different router.

Maybe if you look at the modem logs, they'll provide some explanation, 
unless they have rolled over past the busyout event.

Aaron

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


> Router1 is AS5300 with 12.3(18.8) - 2.9.5.0
>
> router1>sh mode sum
> Avg Hold     Incoming calls       Outgoing calls     Busied   Failed   No   Succ
>    Time     Succ   Fail  Avail   Succ   Fail  Avail   Out      Dial     Ans  Pct.
> 00:32:21  65667   4330     91      0      0      0      54        0     0   94%
>
> Router2 is AS5300 with 12.2(15)T16 - 2.9.5.0
>
> router2>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:31:52 435989  25314     76      0      0      0       0        0     4   95%
>
>
> Router1 is the only AS5300 running 12.3(18.8) and is the only one showing busied out calls during 
> the last 2 months. Previously, when it was running 12.2(15)T16 too, no busied calls were there for 
> over a year.
>
> So, is there a known bug with "busied out" calls in 12.3.18 IOS? I couldn't find anything in bugtool.
>
>
> --
> Tassos
> _______________________________________________
> cisco-nas mailing list
> cisco-nas at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>