Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Dialup to AS5200 lockups. Need help on debug suggestions

We have an AS5200 OS version 12.0.(22).

Dialups (PPP) connections to this device will work OK for 30min-3 hours then they act like all data over the line just goes into a black hole. The connection on the computer will still show a connection, when you ping from the computer it shows info is being sent. Nothing appears to come back from the as5200 or beyond.

I'm trying to put a couple of debug statements in to get a better idea where this is going wrong. I've already added:

debug async events

debug isdn events

If you have better suggestions let me know. This is my first time debugging dialup connections.

Thanks

Wes

3 REPLIES
Silver

Re: Dialup to AS5200 lockups. Need help on debug suggestions

When this happens, can you console/ telnet into the as5200? If yes, pls execute the following commands:

sh user / sh line / show modem / sh ip route x.x.x.x (where x.x.x.x is the ip address of the dailup connection.

If the connection is still up, can try the following:

1) Ping the dialup client ip address, also can enable debug ip packet detailed with access list. (depending on amount of load on the as5200)

If you cannot even console/ telnet into the as5200, then we could have a different issue here, high cpu utilization or memory leak etc etc.

Do we see this with all the PC dialing in or is it specific to the PC you are using?

Thanks, Mak.

New Member

Re: Dialup to AS5200 lockups. Need help on debug suggestions

sh user:

Line User Host(s) Idle Location

11 tty 11 wes Async interface 00:09:58 PPP: 130.254.17.63

* 26 vty 0 wes idle 00:00:00 AASU-192116.Armstrong.EDU

sh line:

Tty Typ Tx/Rx A Modem Roty AccO AccI Uses Noise Overruns Int

0 CTY - - - - - 0 0 0/0 -

I 1 TTY - DialIn - - - 15 0 0/0 -

I 2 TTY - DialIn - - - 15 0 0/0 -

I 3 TTY - DialIn - - - 15 0 0/0 -

I 4 TTY - DialIn - - - 15 0 0/0 -

I 5 TTY - DialIn - - - 7 0 0/0 -

I 6 TTY - DialIn - - - 11 0 0/0 -

I 7 TTY - DialIn - - - 14 0 0/0 -

I 8 TTY - DialIn - - - 8 0 0/0 -

I 9 TTY - DialIn - - - 14 0 0/0 -

I 10 TTY - DialIn - - - 11 0 0/0 -

A 11 TTY - DialIn - - - 13 0 0/0 -

I 12 TTY - DialIn - - - 9 0 0/0 -

I 13 TTY - DialIn - - - 13 0 0/0 -

I 14 TTY - DialIn - - - 10 0 0/0 -

I 15 TTY - DialIn - - - 11 0 0/0 -

I 16 TTY - DialIn - - - 13 0 0/0 -

I 17 TTY - DialIn - - - 14 0 0/0 -

I 18 TTY - DialIn - - - 12 0 0/0 -

I 19 TTY - DialIn - - - 9 0 0/0 -

I 20 TTY - DialIn - - - 13 0 0/0 -

I 21 TTY - DialIn - - - 14 0 0/0 -

I 22 TTY - DialIn - - - 13 0 0/0 -

I 23 TTY - DialIn - - - 14 0 0/0 -

I 24 TTY - DialIn - - - 14 0 0/0 -

25 AUX 9600/9600 - - - - - 0 0 0/0 -

* 26 VTY - - - - - 14 0 0/0 -

I 27 VTY - - - - - 7 0 0/0 -

I 28 VTY - - - - - 0 0 0/0 -

I 29 VTY - - - - - 0 0 0/0 -

I 30 VTY - - - - - 0 0 0/0 -

SH modem:

Inc calls Out calls Busied Failed No Succ

Mdm Usage Succ Fail Succ Fail Out Dial Answer Pct.

1/0 0% 10 1 0 0 0 0 0 91%

1/1 0% 11 0 0 0 0 0 0 100%

1/2 0% 11 0 0 0 0 0 0 100%

1/3 0% 11 0 0 0 0 0 0 100%

1/4 0% 4 2 0 0 0 0 0 67%

1/5 0% 9 2 0 0 0 0 0 82%

1/6 0% 10 1 0 0 0 0 0 91%

1/7 0% 4 2 0 0 0 0 0 67%

1/8 0% 10 1 0 0 0 0 0 91%

1/9 0% 9 2 0 0 0 0 0 82%

* 1/10 0% 10 1 0 0 0 0 0 91%

1/11 0% 5 1 0 0 0 0 0 83%

1/12 0% 9 1 0 0 0 0 0 90%

1/13 0% 5 1 0 0 0 0 0 83%

1/14 0% 6 0 0 0 0 0 0 100%

1/15 0% 10 0 0 0 0 0 0 100%

1/16 0% 10 0 0 0 0 0 0 100%

1/17 0% 9 1 0 0 0 0 0 90%

1/18 0% 7 3 0 0 0 0 0 70%

1/19 0% 9 1 0 0 0 0 0 90%

1/20 0% 10 0 0 0 0 0 0 100%

1/21 0% 10 0 0 0 0 0 0 100%

1/22 0% 9 0 0 0 0 0 0 100%

1/23 0% 10 0 0 0 0 0 0 100%

Sh ip route:

Routing entry for 130.254.17.63/32

Known via "connected", distance 0, metric 0 (connected, via interface)

Redistributing via eigrp 100, rip

Advertised by eigrp 100

rip

Routing Descriptor Blocks:

* directly connected, via Async11

Route metric is 0, traffic share count is 1

Ping from as5200 to client :

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 130.254.17.63, timeout is 2 seconds:

.....

Success rate is 0 percent (0/5)

Can telnet to console fine and login with Tacas+ configuration.

This problem appears with all PC's that I know of.

Question on access-list:

Will give the info needed

access-list 101 permit ip host 130.254.17.63 any log -- (assuming 17.63 is the dialin's ip address)

Thanks for your help

wes

Silver

Re: Dialup to AS5200 lockups. Need help on debug suggestions

Use the following access-list for debugging:

access-list 150 permit icmp any host x.x.17.63

access-list 150 permit icmp host x.x.17.63 any

deb ip packet 150 & initiate a ping to the x.x.17.63 from the as5200.

On the PC, does the ipconfig /all look correct?

Thanks, Mak.

103
Views
0
Helpful
3
Replies
CreatePlease login to create content