[cisco-nas] AS5350 Connection Problems
John McKinney
johnm at wnconline.net
Wed Jun 9 00:04:27 EDT 2004
On Tue, 8 Jun 2004, Melvin C. Etheridge wrote:
Mel,
This was a long time ago. I'm not sure I remember all the details.
>
> John,
>
> What did you do to resolve this issue?
>
> Thanks,
>
> Mel
> [cisco-nas] AS5350 Connection Problems
> John McKinney johnm at wnconline.net
> Tue Sep 9 02:34:20 EDT 2003
>
>
> I experienced the same problem again tonight, from my login.
> Everyone else is assigned an IP from the pool, but I use an assigned IP.
I have not resolved this issue. If I assign a static IP through radius,
the cisco will assign the IP, but the session dies. But I suspect this is
a config issue and not related to the problems mentioned on the list.
> > > > > Another user called in this morning with this problem. Luckily
> > > > > they had 2 lines, so I was able to do a little troubleshooting. The
> called
> > > > > looked normal. It showed V.34 and V.92. Connection speeds were
> > > > > 26000/24000. I had the user disconnect and enter 'AT+MS=v90,0. They
> > > > > reconnected and this time it was a V.34 call and everything worked
> fine.
> > > > > So, does this mean that the problem is a V.92 problem? Any
> suggestions on
> > > > > how to maintain the V.92 calls and resolve the problem?
> > > >
This was the main issue. Certain V.92 modems either would not connect or
would connect but not pass any data. I disabled V.92 on our end and the
problem went away. This was only a temp. fix. I believe we tried 3
different IOS versions around this time and it didn't seem to help. I
contacted CCO and they provided an SPE update. After updating it, the
problem went away. The customers quit complaining. I know dell and gateway
both have issued driver updates and this also seems to help. I have no
idea what (if anything) was different with the modem code, but after
updating the SPE code the customers quit complaining. We still get a few
complaints, but its very few (less than we had with our PM3 boxes). We
will still have to turn off V.92 on the customer end, but not very often.
Mostly on a V.92 connection, but the call slows to 28800. We can turn off
the V.92 and customer seems to get better performance. Maybe the customer
modem is a little to aggressive and can't maintain the call?
>From memory, we have experienced problems with:
bcm
gtw
motorola (can't recall the model)
>From memory, we have very good success with:
Zoom (3025 series)
HP LT win modems
I still think we have to many missed connections (customer redials), but
we get very few complaints. Here are some numbers.
## start numbers
as-1 uptime is 21 weeks, 2 days, 17 hours, 57 minutes
Avg Hold Inc calls Out calls Failed No Succ
SPE Time Succ Fail Succ Fail Dial Answer Pct
1/00 00:42:36 16256 1121 0 0 0 0 94%
1/01 00:42:40 16232 1102 0 0 0 0 94%
1/02 00:41:41 16507 1130 0 0 0 0 94%
1/03 00:41:39 16487 1130 0 0 0 0 94%
1/04 00:42:26 16253 1081 0 0 0 0 94%
1/05 00:42:14 16348 1066 0 0 0 0 94%
1/06 00:43:06 16001 1112 0 0 0 0 94%
1/07 00:42:39 16212 1120 0 0 0 0 94%
1/08 00:41:56 16374 1138 0 0 0 0 94%
1/09 00:41:09 16637 1155 0 0 0 0 94%
## end numbers
Here is some of my config if it helps. I don't recall all the features for
the modemcap, but maybe Aaron (or anyone else) can explain it.
## start config
boot system flash c5350-is-mz.122-2.XB15.bin
spe 1/00 1/09
firmware location flash:128.0.1.92.spe
modemcap entry cisco:MSC=&FS62=8S63=3S29=12S21=15
## end config
Heres a list of current calls. Pay attention to the Compression. When
the sessions would die, they were using V.44 compression. (Turn off in
your modemcap and I bet your problem goes away)
## Current Calls - w/o Retrain
SPE 1/00
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
2 V.34 LAP-M V.42bis 7546 26400/26400- 12/-24 38 In
4 V.34+ LAP-M V.44 1288 31200/21600- 13/-21 38 In
5 V.90 LAP-M V.42bis 6850 42667/24000- 12/-15 40 In
SPE 1/01
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
6 V.90 LAP-M V.42bis 4032 46667/24000- 12/-16 33 In
7 V.90 LAP-M V.42bis 3609 44000/26400- 12/-17 38 In
8 V.90/92 LAP-M V.44 3326 36000/26400- 12/-16 38 In
9 V.90 LAP-M V.42bis 63 45333/28800- 12/-12 38 In
10 V.34/92 LAP-M V.44 8451 26400/24000- 13/-13 33 In
11 V.34 LAP-M V.42bis 4650 26400/24000- 13/-20 38 In
SPE 1/02
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
14 V.34 LAP-M V.42bis 1449 26400/24000- 13/-20 33 In
15 V.90 LAP-M V.42bis 4448 45333/31200- 12/-14 40 In
17 V.34 LAP-M V.44 3520 28800/26400- 13/-19 38 In
SPE 1/03
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
19 V.90/92 LAP-M V.44 16236 46667/26400- 12/-19 40 In
20 V.90 LAP-M V.42bis 1352 50667/26400- 12/-12 42 In
23 V.34/92 LAP-M V.44 6761 21600/21600- 13/-21 33 In
SPE 1/04
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
25 V.34 LAP-M V.42bis 1650 28800/24000- 13/-19 38 In
29 V.90 LAP-M V.42bis 3304 52000/28800- 12/-10 40 In
SPE 1/05
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
30 V.90 LAP-M V.42bis 3248 38667/26400- 12/-16 38 In
31 V.90 LAP-M V.42bis 4976 41333/24000- 12/-18 37 In
32 V.90/92 LAP-M V.44 799 36000/26400- 12/-16 0 In
SPE 1/06
Port Type Prot Comp Duration Tx/Rx(bps) Tx/Rx(Lvl) SNR Cfg
37 V.90/92 LAP-M V.44 2086 46667/26400- 12/-15 0 In
38 V.34 LAP-M V.42bis 11552 26400/24000- 13/-19 33 In
40 V.90 LAP-M None 4757 46667/28800- 12/-11 40 In
41 V.34 LAP-M V.42bis 296 21600/26400- 13/-19 38 In
## end current calls
Did you notice port 29? Wish everyone could connection that fast!
Feel free to reply. All feedback is welcome.
--
Thank You,
John McKinney
WNC ONLINE
More information about the cisco-nas
mailing list