[nsp] AS53xx V.92 configuration not working
Daniel Fraser
dfraser@bellglobal.com
Mon, 19 Aug 2002 15:19:36 -0400
I had a similar problem with 12.2(2)XA5 and 2.9.2.0 portware. I found
that I could make it work by shuffling the order of the attributes in
the modemcap. Having the S53 and S54 commands immediately following
&F&D2 seemed to do the trick.
Regards,
=20
Dan Fraser
IP Engineering - Operations
Bell Nexxia
-----Original Message-----
From: Josh Duffek [mailto:jduffek@cisco.com]=20
Sent: Monday August 19, 2002 2:55 PM
To: cisco-nas@external.cisco.com; cisco-nsp@puck.nether.net; Cisco Geek
Rotation
Subject: Re: [nsp] AS53xx V.92 configuration not working
im decently sure that the modem autoconfig code is independent of
platform/modems.
hopefully someone smarter then me will comment.
joshd
=3D=3D=3D=3D
Hey Josh:
I can't find this above-referenced DDT.
What is the workaround? V.92 doesn't work at all, this condition occurs
for every modem on multiple chassis (I tried another one already).
>dup'd to:
>
>CSCdw78376 R UP324 - modem configuration failing for some ports
>Version:12.2(02)XB03 Integrated:12.2(11.05)GLD 12.2(11.05)T
12.2(10.07)T04
>12.2(02)XB06
This says it is a 5850, I'm using 53xx stuff:
---
=B7 CSCdw78376
Symptoms A modem configuration (using deb confmodem) may fail.
Conditions This symptom is observed on a Cisco AS5850 access server when
using modemcap to modify the nextport register configuration.
Workaround Apply the same modemcap from a reverse telnet to the
nextport.
---
Chris
>adding in cisco-nas just in case im wrong.
>
>joshd
>
>----- Original Message -----
>From: "Cisco Geek Rotation" <cisco@peakpeak.com>
>To: "Charles Sprickman" <spork@inch.com>; <cisco-nsp@puck.nether.net>
>Sent: Sunday, August 18, 2002 10:56 PM
>Subject: Re: [nsp] AS53xx V.92 configuration not working
>
>
> > At 06:32 PM 8/18/2002 -0400, Charles Sprickman wrote:
> > >I'm out of my league here, but it does seem to be barfing on the
init
> > >string. Does it do the same with something simple like "&F"?
> > >
> > >Charles
> >
> > Good idea.
> >
> > No it doesn't, here are some experiments I tried:
> >
> > Original string (FAILS):
> > modemcap edit cisco misc
> >
&F&D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S10=3D50de=
bugthismodemS71
=3D4
> >
> >
> > These work:
> >
> > modemcap edit cisco misc &F WORKS
> >
> > modemcap edit cisco misc &F&D2 WORKS
> >
> > These all fail:
> >
> > modemcap edit cisco misc &F&D2S62=3D8 FAILS
> >
> > modemcap edit cisco misc &F&D2S63=3D3 FAILS
> >
> > modemcap edit cisco misc &F&D2S21=3D15 FAILS
> >
> > So it seems to have something to do with any of the S-register
commands
> > that do something with V.92 as documented here:
> >
> > http://www.cisco.com/warp/public/471/v92_21360.html
> >
> > Here's what's in flash, according to all the documentation this is
the
>code
> > to run, so I'm puzzled as to what the problem could be.
> >
> > #show flash
> >
> > System flash directory:
> > File Length Name/status
> > 1 9807020 c5300-ds-mz.122-2.XA5.bin
> > 2 465726 mica-modem-pw.2.9.2.0.bin
> > [10272876 bytes used, 6504340 available, 16777216 total]
> > 16384K bytes of processor board System flash (Read/Write)
> >
> > And the code is loading into the modems (SPEs):
> >
> > #show modem ver
> >
> > Codes:
> > d - DSP software download is required for achieving K56flex
connections
> >
> > Modem module Firmware Boot DSP
> > Mdm Number Rev Rev Rev
> > 1/0 0 2.9.2.0
> > <snip>
> >
> >
> > Chris
> >
> >
> >
> > >--
> > >Charles Sprickman
> > >spork@inch.com
> > >
> > >
> > >On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:
> > >
> > > > At 02:03 PM 8/18/2002 -0400, you wrote:
> > > > >On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:
> > > > >
> > > > > >
> > >
>&F&D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S10=3D50d=
ebugthismodemS7
1=3D4
> > > > >
>^^^^^^^^^^^^^^
> > > > >
> > > > >I'm no cisco modem expert, but what happens if you remove the
above
> > > > >portion of the init string?
> > > >
> > > > Pretty much the same thing:
> > > >
> > > > Aug 18 18:43:57.846: TTY89: Modem
> > > > command:
> > >
> >
--AT&F&D2S62=3D8S63=3D3S21=3D15S29=3D12S40=3D10S54=3D456S10=3D50debugthis=
modemS71=3D4--
> > > > Aug 18 12:44:00: %TTY-3-AUTOCONFIG: TTY89: Modem
auto-configuration
>failed
> > > >
> > > >
> > > > >Also try to debug this with "debug confmodem".
> > > >
> > > >
> > > > Here is what I get:
> > > >
> > > > Aug 18 18:30:49.446: TTY160: detection speed (115200)
>response ---OK---
> > > > Aug 18 18:30:49.446: TTY160: Modem
> > > >
> > >
>ommand:
--AT&F&D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S10=3D=
50S71=3D4--
> > > > Aug 18 12:30:51: %TTY-3-AUTOCONFIG: TTY160: Modem
auto-configuration
>failed
> > > >
> > > > Not the treasure trove of info I was expecting! :)
> > > >
> > > > Chris
> > > >
> > > >
> > > > >Charles
> > > > >
> > > > > > line 1 192
> > > > > > exec-timeout 0 0
> > > > > > no flush-at-activation
> > > > > > modem Dialin
> > > > > > modem autoconfigure type cisco
> > > > > > transport input all
> > > > > > autoselect during-login
> > > > > > autoselect ppp
> > > > > > ----
> > > > > >
> > > > > > So why is it that the modems are failing to initialize with
this
> > > > > > modemcap? Thanks for any hints.
> > > > > >
> > > > > > Chris
> > > > > >
> > > > > >
> > > > > > _______________________________________________
> > > > > > cisco-nsp mailing list real_name)s@puck.nether.net
> > > > > > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > > > > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> > > > > >
> > > >
> > > >
> >
> >
> > _______________________________________________
> > cisco-nsp mailing list real_name)s@puck.nether.net
> > http://puck.nether.net/mailman/listinfo/cisco-nsp
> > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >