callback stopped working after IOS upgrade

Discussion in 'Cisco' started by Victor Sudakov, Jun 26, 2007.

  1. 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/
    Victor Sudakov, Jun 26, 2007
    #1
    1. Advertising

  2. ~ 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
    Aaron Leonard, Jun 26, 2007
    #2
    1. Advertising

  3. 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/
    Victor Sudakov, Jun 27, 2007
    #3
  4. ~ > ~ 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
    Aaron Leonard, Jun 28, 2007
    #4
  5. 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/
    Victor Sudakov, Jun 29, 2007
    #5
  6. 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/sw/iosswrel/ps1828/products_white_paper09186a008018305e.shtml

    --
    Regards,
    Martin
    Martin Gallagher, Jun 30, 2007
    #6
    1. Advertising

Want to reply to this thread or ask your own question?

It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum.
Similar Threads
  1. cisconewbie

    Cisco 837 upgrade IOS upgrade gone wrong

    cisconewbie, Sep 22, 2006, in forum: Hardware
    Replies:
    5
    Views:
    3,356
    kuruvi
    Oct 5, 2008
  2. buttonbrn
    Replies:
    8
    Views:
    512
  3. Mike Rahl
    Replies:
    1
    Views:
    1,234
    Trendkill
    May 30, 2007
  4. Replies:
    11
    Views:
    928
    Leythos
    Jul 3, 2007
  5. Pablo
    Replies:
    1
    Views:
    501
    R. C. White
    Feb 4, 2009
Loading...

Share This Page