[nsp] AS53xx V.92 configuration not working

Cisco Geek Rotation cisco@peakpeak.com
Mon, 19 Aug 2002 11:30:21 -0600


--=====================_48017916==_.ALT
Content-Type: text/plain; charset="iso-8859-1"; format=flowed
Content-Transfer-Encoding: quoted-printable

At 11:33 AM 8/19/2002 -0500, you wrote:
>There is nothing wrong with your string, or having the debugthismodemS71=3D=
4
>in there...
>
>I think you are running into this:
>
>CSCdw79744 Modem Autoconfiguration Sometimes Fails
>Version:12.2(02)XA04 Integrated:

Hey Josh:

I can't find this above-referenced DDT.

What is the workaround?  V.92 doesn't work at all, this condition occurs=20
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=20
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=3D50debu=
gthismodemS71=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=3D50debu=
gthismodemS71=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=3D50debugthi=
smodemS71=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=3D45=
6S10=3D50S71=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/
> >

--=====================_48017916==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
At 11:33 AM 8/19/2002 -0500, you wrote:<br>
<blockquote type=3Dcite class=3Dcite cite>There is nothing wrong with your
string, or having the debugthismodemS71=3D4<br>
in there...<br><br>
I think you are running into this:<br><br>
CSCdw79744 Modem Autoconfiguration Sometimes Fails<br>
Version:12.2(02)XA04 Integrated:</blockquote><br>
Hey Josh:<br><br>
I can't find this above-referenced DDT.<br><br>
What is the workaround?&nbsp; V.92 doesn't work at all, this condition
occurs for every modem on multiple chassis (I tried another one
already).<br><br>
<br><br>
<blockquote type=3Dcite class=3Dcite cite>dup'd to:<br><br>
CSCdw78376 R UP324 - modem configuration failing for some ports<br>
Version:12.2(02)XB03 Integrated:12.2(11.05)GLD 12.2(11.05)T
12.2(10.07)T04<br>
12.2(02)XB06</blockquote><br><br>
This says it is a 5850, I'm using 53xx stuff:<br><br>
---<br>
<font=
 face=3D"Symbol">=B7<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab=
></font>CSCdw78376<br><br>
<b>Symptoms</b> A modem configuration (using deb confmodem) may
fail.<br><br>
<b>Conditions</b> This symptom is observed on a Cisco AS5850 access
server when using modemcap to modify the nextport register
configuration.<br><br>
<b>Workaround</b> Apply the same modemcap from a reverse telnet to the
nextport.<br>
---<br><br>
Chris<br><br>
<br>
<blockquote type=3Dcite class=3Dcite cite>adding in cisco-nas just in case i=
m
wrong.<br><br>
joshd<br><br>
----- Original Message -----<br>
From: &quot;Cisco Geek Rotation&quot; &lt;cisco@peakpeak.com&gt;<br>
To: &quot;Charles Sprickman&quot; &lt;spork@inch.com&gt;;
&lt;cisco-nsp@puck.nether.net&gt;<br>
Sent: Sunday, August 18, 2002 10:56 PM<br>
Subject: Re: [nsp] AS53xx V.92 configuration not working<br><br>
<br>
&gt; At 06:32 PM 8/18/2002 -0400, Charles Sprickman wrote:<br>
&gt; &gt;I'm out of my league here, but it does seem to be barfing on the
init<br>
&gt; &gt;string.&nbsp; Does it do the same with something simple like
&quot;&amp;F&quot;?<br>
&gt; &gt;<br>
&gt; &gt;Charles<br>
&gt;<br>
&gt; Good idea.<br>
&gt;<br>
&gt; No it doesn't, here are some experiments I tried:<br>
&gt;<br>
&gt; Original string (FAILS):<br>
&gt; modemcap edit cisco misc<br>
&gt;
&amp;F&amp;D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S10=
=3D50debugthismodemS71=3D4<br>
&gt;<br>
&gt;<br>
&gt; These work:<br>
&gt;<br>
&gt; modemcap edit cisco misc &amp;F&nbsp; WORKS<br>
&gt;<br>
&gt; modemcap edit cisco misc &amp;F&amp;D2&nbsp; WORKS<br>
&gt;<br>
&gt; These all fail:<br>
&gt;<br>
&gt; modemcap edit cisco misc &amp;F&amp;D2S62=3D8&nbsp; FAILS<br>
&gt;<br>
&gt; modemcap edit cisco misc &amp;F&amp;D2S63=3D3&nbsp; FAILS<br>
&gt;<br>
&gt; modemcap edit cisco misc &amp;F&amp;D2S21=3D15 FAILS<br>
&gt;<br>
&gt; So it seems to have something to do with any of the S-register
commands<br>
&gt; that do something with V.92 as documented here:<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
<a href=3D"http://www.cisco.com/warp/public/471/v92_21360.html"=
 eudora=3D"autourl">http://www.cisco.com/warp/public/471/v92_21360.html</a><=
br>
&gt;<br>
&gt; Here's what's in flash, according to all the documentation this is
the<br>
code<br>
&gt; to run, so I'm puzzled as to what the problem could be.<br>
&gt;<br>
&gt; #show flash<br>
&gt;<br>
&gt; System flash directory:<br>
&gt; File&nbsp; Length&nbsp;&nbsp; Name/status<br>
&gt;&nbsp;&nbsp;&nbsp; 1&nbsp;&nbsp; 9807020&nbsp;
c5300-ds-mz.122-2.XA5.bin<br>
&gt;&nbsp;&nbsp;&nbsp; 2&nbsp;&nbsp; 465726&nbsp;&nbsp;
mica-modem-pw.2.9.2.0.bin<br>
&gt; [10272876 bytes used, 6504340 available, 16777216 total]<br>
&gt; 16384K bytes of processor board System flash (Read/Write)<br>
&gt;<br>
&gt; And the code is loading into the modems (SPEs):<br>
&gt;<br>
&gt; #show modem ver<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp; Codes:<br>
&gt;&nbsp;&nbsp;&nbsp; d - DSP software download is required for
achieving K56flex connections<br>
&gt;<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Modem module&nbsp;&nbsp;&nbsp;&nbsp; Firmware&nbsp;&nbsp;
Boot&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; DSP<br>
&gt;&nbsp;&nbsp;&nbsp; Mdm&nbsp;&nbsp;&nbsp;&nbsp;
Number&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Rev&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
Rev&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Rev<br>
&gt;&nbsp;&nbsp;&nbsp;
1/0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;
0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2.9.2.0<br>
&gt; &lt;snip&gt;<br>
&gt;<br>
&gt;<br>
&gt; Chris<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; &gt;--<br>
&gt; &gt;Charles Sprickman<br>
&gt; &gt;spork@inch.com<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; &gt;On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; At 02:03 PM 8/18/2002 -0400, you wrote:<br>
&gt; &gt; &gt; &gt;On Sun, 18 Aug 2002, Cisco Geek Rotation wrote:<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt;<br>
&amp;F&amp;D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S10=
=3D50debugthismodemS71=3D4<br>
&gt; &gt; &gt; &gt;<br>
^^^^^^^^^^^^^^<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;I'm no cisco modem expert, but what happens if you
remove the above<br>
&gt; &gt; &gt; &gt;portion of the init string?<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Pretty much the same thing:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Aug 18 18:43:57.846: TTY89: Modem<br>
&gt; &gt; &gt; command:<br>
&gt; &gt;<br>
&gt;
--AT&amp;F&amp;D2S62=3D8S63=3D3S21=3D15S29=3D12S40=3D10S54=3D456S10=3D50debu=
gthismodemS71=3D4--<br>
&gt; &gt; &gt; Aug 18 12:44:00: %TTY-3-AUTOCONFIG: TTY89: Modem
auto-configuration<br>
failed<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;Also try to debug this with &quot;debug
confmodem&quot;.<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Here is what I get:<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Aug 18 18:30:49.446: TTY160: detection speed=20
(115200)<br>
response ---OK---<br>
&gt; &gt; &gt; Aug 18 18:30:49.446: TTY160: Modem<br>
&gt; &gt; &gt;<br>
&gt; &gt;<br>
ommand:&nbsp;
--AT&amp;F&amp;D2S62=3D8S63=3D3S21=3D15S29=3D12S34=3D18000S40=3D10S54=3D456S=
10=3D50S71=3D4--<br>
&gt; &gt; &gt; Aug 18 12:30:51: %TTY-3-AUTOCONFIG: TTY160: Modem
auto-configuration<br>
failed<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Not the treasure trove of info I was expecting! :)<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; Chris<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt;Charles<br>
&gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; line 1 192<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; exec-timeout 0 0<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; no flush-at-activation<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; modem Dialin<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; modem autoconfigure type cisco<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; transport input all<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; autoselect during-login<br>
&gt; &gt; &gt; &gt; &gt;&nbsp;&nbsp; autoselect ppp<br>
&gt; &gt; &gt; &gt; &gt; ----<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; So why is it that the modems are failing to
initialize with this<br>
&gt; &gt; &gt; &gt; &gt; modemcap?&nbsp; Thanks for any hints.<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt; Chris<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt; &gt; &gt;
_______________________________________________<br>
&gt; &gt; &gt; &gt; &gt; cisco-nsp mailing list&nbsp;
real_name)s@puck.nether.net<br>
&gt; &gt; &gt; &gt; &gt;
<a href=3D"http://puck.nether.net/mailman/listinfo/cisco-nsp"=
 eudora=3D"autourl">http://puck.nether.net/mailman/listinfo/cisco-nsp</a><br=
>
&gt; &gt; &gt; &gt; &gt; archive at
<a href=3D"http://puck.nether.net/pipermail/cisco-nsp/"=
 eudora=3D"autourl">http://puck.nether.net/pipermail/cisco-nsp/</a><br>
&gt; &gt; &gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt;<br>
&gt;<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; cisco-nsp mailing list&nbsp; real_name)s@puck.nether.net<br>
&gt;
<a href=3D"http://puck.nether.net/mailman/listinfo/cisco-nsp"=
 eudora=3D"autourl">http://puck.nether.net/mailman/listinfo/cisco-nsp</a><br=
>
&gt; archive at
<a href=3D"http://puck.nether.net/pipermail/cisco-nsp/"=
 eudora=3D"autourl">http://puck.nether.net/pipermail/cisco-nsp/</a><br>
&gt;</blockquote></html>

--=====================_48017916==_.ALT--