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. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

857 ADSL problems

I am having problems connecting over ADSL using an 857W router in the UK. My provider is Demon. Is anyone else having problems?

Config used is below,

interface ATM0

no ip address

no ip redirects

no ip unreachables

no ip proxy-arp

ip route-cache flow

no atm ilmi-keepalive

dsl operating-mode auto

!

interface ATM0.2 point-to-point

description $ES_WAN$$FW_OUTSIDE$

no ip redirects

no ip unreachables

no ip proxy-arp

pvc 0/38

encapsulation aal5mux ppp dialer

dialer pool-member 2

interface Dialer1

description $FW_OUTSIDE$

ip address xxxxxxxxxxxx

ip access-group 101 in

no ip redirects

no ip unreachables

no ip proxy-arp

ip inspect fwrule out

ip nat outside

ip virtual-reassembly

encapsulation ppp

ip route-cache flow

dialer pool 2

dialer-group 2

no cdp enable

ppp authentication chap callin

ppp chap hostname xxxxxxxxx

ppp chap password xxxxxxxxx

4 REPLIES

Re: 857 ADSL problems

What kind of problem do you have?

Do you have a link (CD led on)

If so, verify the vp/vc setting with the ISP and issue the "debug ppp neg" command to check for possible negotiation issues.

Regards,

Leo

New Member

Re: 857 ADSL problems

I changed the ATM interface from dsl operating-mode 'auto' with ansi-dmt as suggested.This seemed to improve connectivity as the CO led remained solid for 30s before dropping off.

debug logs below. Dialer debugs look most promising

Thanks for your help.

debug ppp neg

000124: *Jan 6 18:58:37.007 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to up

000125: *Jan 6 18:58:41.223 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to up

000126: *Jan 6 18:58:41.223 GMT: %DIALER-6-BIND: Interface Vi2 bound to profile Di1

000127: *Jan 6 18:58:41.223 GMT: Vi2 PPP: Using dialer call direction

000128: *Jan 6 18:58:41.223 GMT: Vi2 PPP: Treating connection as a callout

000129: *Jan 6 18:58:41.223 GMT: Vi2 PPP: Phase is ESTABLISHING, Active Open

000130: *Jan 6 18:58:41.223 GMT: Vi2 PPP: No remote authentication for call-out

000131: *Jan 6 18:58:41.223 GMT: Vi2 LCP: O CONFREQ [Closed] id 32 len 14

000132: *Jan 6 18:58:41.223 GMT: Vi2 LCP: MRU 1478 (0x010405C6)

000133: *Jan 6 18:58:41.223 GMT: Vi2 LCP: MagicNumber 0x14FD518E (0x050614FD518E)

000134: *Jan 6 18:58:42.279 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000135: *Jan 6 18:58:42.279 GMT: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1

000136: *Jan 6 18:58:42.279 GMT: Vi2 PPP: Sending Acct Event[Down] id[11]

000137: *Jan 6 18:58:42.279 GMT: Vi2 LCP: State is Closed

000138: *Jan 6 18:58:42.279 GMT: Vi2 PPP: Phase is DOWN

000139: *Jan 6 18:58:43.295 GMT: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000140: *Jan 6 18:58:44.295 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

Debug ATM Events

000245: *Jan 6 19:02:11.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000246: *Jan 6 19:02:12.115 GMT: atmsar_vc_tx_start(81C0A260).

000247: *Jan 6 19:02:12.115 GMT: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x81

B19518

000248: *Jan 6 19:02:12.115 GMT: atmsar_transmit_pak_wrapper: deq(81B19518). vc

d: 1.atmsar_transmit_pak_wrapper : encap = Data

000252: *Jan 6 19:02:15.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000253: *Jan 6 19:02:16.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000254: *Jan 6 19:02:17.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000256: *Jan 6 19:02:18.955 GMT: ATM0: atmsar_atm_get_stats,vcinfo = 0x0

000257: *Jan 6 19:02:19.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000258: *Jan 6 19:02:20.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000259: *Jan 6 19:02:21.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000260: *Jan 6 19:02:22.131 GMT: atmsar_vc_tx_start(81C0A260).

000261: *Jan 6 19:02:22.131 GMT: ATM0:atmsar_dequeue_pak, dequeued a pak = 0x82

0A57BC

000262: *Jan 6 19:02:22.131 GMT: atmsar_transmit_pak_wrapper: deq(820A57BC). vc

d: 1.atmsar_transmit_pak_wrapper : encap = Data

000263: *Jan 6 19:02:22.143 GMT: ATM0: vcd = 1, safe_start called from periodic

000264: *Jan 6 19:02:23.143 GMT: ATM0: vcd = 1, safe_start called from periodic

Debug atm state

000306: *Jan 6 19:03:13.123 GMT: Changing vc 0/38vc-state to ATM_VC_SHUTTING_DOWN

000307: *Jan 6 19:03:13.123 GMT: Changing vc 0/38vc-state to ATM_VC_NOT_IN_SERVICE

debug dialer events

000327: *Jan 6 19:05:12.747 GMT: %LINK-3-UPDOWN: Interface Virtual-Access2, changed state to down

000328: *Jan 6 19:05:12.747 GMT: %DIALER-6-UNBIND: Interface Vi2 unbound from profile Di1

000329: *Jan 6 19:05:13.823 GMT: %LINK-3-UPDOWN: Interface ATM0, changed state to down

000330: *Jan 6 19:05:14.823 GMT: %LINEPROTO-5-UPDOWN: Line protocol on Interface ATM0, changed state to down

000331: *Jan 6 19:05:15.239 GMT: Di1 DDR: Cannot place call, no dialer string set

000332: *Jan 6 19:05:15.239 GMT: Di1 DDR: Cannot place call, no dialer string set

000333: *Jan 6 19:05:27.747 GMT: Vi2 DDR: re-enable timeout

Bronze

Re: 857 ADSL problems

Hello,

try and configure ´ip mtu 1452´ on your Dialer1 interface.

Also, configure the following on your Dialer1 interface:

ppp authentication chap pap callin

ppp chap hostname USERNAME

ppp chap password 0 PASSWORD

ppp pap sent-username USERNAME password PASSWORD

If that doesn´t help, can you post the full configuration of your router ?

Regards,

Nethelper

New Member

Re: 857 ADSL problems

Attached is the whole config minus usernames and passwords. Any help much appreciated

266
Views
0
Helpful
4
Replies