Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Computing > Cisco > callback stopped working after IOS upgrade

Reply
Thread Tools

callback stopped working after IOS upgrade

 
 
Victor Sudakov
Guest
Posts: n/a
 
      06-26-2007
Colleagues,

After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working
with the following message:

1951: TTY38 Callback PPP process creation
1952: TTY38 Callback process initiated, user: dialstring 9427624
1953: TTY38 Callback process before disconnect- modemcheck status=20090081

Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS.

Any ideas what this message means and how to fix the problem?

Downgrading to 12.2(27) does fix the problem with callback (this means
the callback configuration is correct), but a downgrade is not desirable
as 12.2(27) has other bugs.

--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
 
Reply With Quote
 
 
 
 
Aaron Leonard
Guest
Posts: n/a
 
      06-26-2007

~ After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working
~ with the following message:
~
~ 1951: TTY38 Callback PPP process creation
~ 1952: TTY38 Callback process initiated, user: dialstring 9427624
~ 1953: TTY38 Callback process before disconnect- modemcheck status=20090081
~
~ Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS.
~
~ Any ideas what this message means and how to fix the problem?
~
~ Downgrading to 12.2(27) does fix the problem with callback (this means
~ the callback configuration is correct), but a downgrade is not desirable
~ as 12.2(27) has other bugs.

This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T.
If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting
the DEs to patch in the fix.

Aaron
 
Reply With Quote
 
 
 
 
Victor Sudakov
Guest
Posts: n/a
 
      06-27-2007
Aaron Leonard wrote:

> ~ After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working
> ~ with the following message:
> ~
> ~ 1951: TTY38 Callback PPP process creation
> ~ 1952: TTY38 Callback process initiated, user: dialstring 9427624
> ~ 1953: TTY38 Callback process before disconnect- modemcheck status=20090081
> ~
> ~ Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS.
> ~
> ~ Any ideas what this message means and how to fix the problem?
> ~
> ~ Downgrading to 12.2(27) does fix the problem with callback (this means
> ~ the callback configuration is correct), but a downgrade is not desirable
> ~ as 12.2(27) has other bugs.


> This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T.
> If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting
> the DEs to patch in the fix.


CSCsc43163 is first found in 12.4T
How come that I was hit in 12.2(46) ?

Thank you for your input.

--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
 
Reply With Quote
 
Aaron Leonard
Guest
Posts: n/a
 
      06-27-2007

~ > ~ After IOS upgrade from 12.2(27) to 12.2(46) callback stopped working
~ > ~ with the following message:
~ > ~
~ > ~ 1951: TTY38 Callback PPP process creation
~ > ~ 1952: TTY38 Callback process initiated, user: dialstring 9427624
~ > ~ 1953: TTY38 Callback process before disconnect- modemcheck status=20090081
~ > ~
~ > ~ Platform: cisco 2621, NM-8A/DM, modem firmware source: IOS.
~ > ~
~ > ~ Any ideas what this message means and how to fix the problem?
~ > ~
~ > ~ Downgrading to 12.2(27) does fix the problem with callback (this means
~ > ~ the callback configuration is correct), but a downgrade is not desirable
~ > ~ as 12.2(27) has other bugs.
~
~ > This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T.
~ > If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting
~ > the DEs to patch in the fix.
~
~ CSCsc43163 is first found in 12.4T
~ How come that I was hit in 12.2(46) ?

My guess is that whatever bugfix it was that caused CSCsc43163 to appear
in 12.4T finally got committed to 12.2M some time between 12.2(27) and 12.2(46).

Regards,

Aaron
 
Reply With Quote
 
Victor Sudakov
Guest
Posts: n/a
 
      06-29-2007
Aaron Leonard wrote:
> ~ > This looks to be CSCsc43163, fixed in 12.4(09)T04 12.4(11)T02 12.4(13.12)T.
> ~ > If you need the fix in 12.2M, then I'd recommend opening a TAC case and getting
> ~ > the DEs to patch in the fix.
> ~
> ~ CSCsc43163 is first found in 12.4T
> ~ How come that I was hit in 12.2(46) ?


> My guess is that whatever bugfix it was that caused CSCsc43163 to
> appear in 12.4T finally got committed to 12.2M some time between
> 12.2(27) and 12.2(46).


Do you mean there is absolutely no luck for me trying anything between
12.2(46) and 12.4(09)T04 ?

--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49@fidonet http://vas.tomsk.ru/
 
Reply With Quote
 
Martin Gallagher
Guest
Posts: n/a
 
      06-30-2007
On Fri, 29 Jun 2007 11:28:16 +0000, Victor Sudakov wrote:

>> My guess is that whatever bugfix it was that caused to
>> appear in 12.4T finally got committed to 12.2M some time between
>> 12.2(27) and 12.2(46).

>
> Do you mean there is absolutely no luck for me trying anything between
> 12.2(46) and 12.4(09)T04 ?


No, it means that the same change was made to 12.2 between 12.2(27) and
12.2(49), and to 12.4T as well. It may have gone into 12.3, 12.3T etc. as
well.

Releases in any of the trains before that point will be ok. There isn't
an unbroken line of descent from 12.2(49) to 12.4(09)T04. it's more
complicated than that.

See White Paper: Cisco IOS Reference Guide
http://www.cisco.com/en/US/products/...8018305e.shtml

--
Regards,
Martin
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Cisco 837 upgrade IOS upgrade gone wrong cisconewbie Hardware 5 10-05-2008 06:29 PM
instructions on how to perform an IOS upgrade on a Catalyst 6500 switch (IOS to IOS) Mike Rahl Cisco 1 05-30-2007 05:22 PM
Application Stopped working....after upgrade stephen ASP .Net 2 06-17-2006 11:04 AM
Viewstate folder files stopped working after upgrade to 2.0 erik.lagusson@gmail.com ASP .Net 0 06-15-2006 10:34 AM
Re: debuger stopped working after upgrade to vs 2003 and .net framework 1.1 S. Justin Gengo ASP .Net 0 07-24-2003 01:58 AM



Advertisments