cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
805
Views
0
Helpful
3
Replies

Cisco 877 ADSL connection issue

We are currently deploying a Cisco 877  using ADSL for our customer.

We have deployed many of these routers for our customer and always seem to have trouble with our west coast installs.  Mostly it is getting the right information from our vendor

Our last mile is ATT and the connection is ADSL over Ethernet.  From what we can see we are establishing a PPPoe tunnel but routing is not coming up.

The vendor states everything is good on the wire up to the gateway they can ping.  Generally we see that the gateway is not pingable with these types of WAN connections but if everything is working correctly the routers outside public IP is pingable.  We have several other ATT ADSL connections throughout the West Coast and nothing is consistent.

Here are my interface configs.  User information/IP has been purposefully changed.

This router is being deployed in CenturyCity CA.

flash:c870-advsecurityk9-mz.124-24.T4.bin
Cisco877

interface ATM0
mtu 1492
bandwidth 512
no ip address
no ip mroute-cache
atm vc-per-vp 64
no atm ilmi-keepalive
!
interface ATM0.1 point-to-point
pvc 0/35
  encapsulation aal5snap
  pppoe-client dial-pool-number 1
!


interface Dialer1
ip address 99.255.52.154 255.255.255.248
ip access-group 111 in
ip mtu 1492
ip virtual-reassembly
encapsulation ppp
dialer pool 1
dialer idle-timeout 0
dialer-group 1
no cdp enable
ppp authentication chap pap callin
ppp chap hostname mycustomersaccount@static.att.net
ppp chap password password
ppp pap sent-username mycustomersaccount@static.att.net password password
!
access-list 111 permit ip any any
dialer-list 1 protocol ip permit


results of debug


*Oct 27 13:14:32.897 PDT: Vi1 LCP:    AuthProto PAP (0x0304C023)
*Oct 27 13:14:32.897 PDT: Vi1 LCP:    MagicNumber 0x7A09F874 (0x05067A09F874)
*Oct 27 13:14:32.897 PDT: Vi1 LCP: O CONFREJ [ACKrcvd] id 190 len 8
*Oct 27 13:14:32.897 PDT: Vi1 LCP:    MRU 1492 (0x010405D4)
*Oct 27 13:14:32.909 PDT: Vi1 LCP: I CONFREQ [ACKrcvd] id 191 len 14
*Oct 27 13:14:32.909 PDT: Vi1 LCP:    AuthProto PAP (0x0304C023)
*Oct 27 13:14:32.909 PDT: Vi1 LCP:    MagicNumber 0x7A09F874 (0x05067A09F874)
*Oct 27 13:14:32.909 PDT: Vi1 LCP: O CONFACK [ACKrcvd] id 191 len 14
*Oct 27 13:14:32.909 PDT: Vi1 LCP:    AuthProto PAP (0x0304C023)
*Oct 27 13:14:32.909 PDT: Vi1 LCP:    MagicNumber 0x7A09F874 (0x05067A09F874)
*Oct 27 13:14:32.909 PDT: Vi1 LCP: State is Open
*Oct 27 13:14:32.913 PDT: Vi1 PPP: Phase is AUTHENTICATING, by the peer
*Oct 27 13:14:32.913 PDT: Vi1 PAP: Using hostname from interface PAP
*Oct 27 13:14:32.913 PDT: Vi1 PAP: Using password from interface PAP
*Oct 27 13:14:32.913 PDT: Vi1 PAP: O AUTH-REQ id 1 len 44 from "mycustommersaccount@static.att.net"
*Oct 27 13:14:33.285 PDT: Vi1 PAP: I AUTH-ACK id 1 len 5
*Oct 27 13:14:33.285 PDT: Vi1 PPP: Phase is FORWARDING, Attempting Forward
*Oct 27 13:14:33.285 PDT: Vi1 PPP: Phase is ESTABLISHING, Finish LCP
*Oct 27 13:14:33.285 PDT: Vi1 PPP: Phase is UP
*Oct 27 13:14:33.285 PDT: Vi1 IPCP: O CONFREQ [Closed] id 1 len 10
*Oct 27 13:14:33.289 PDT: Vi1 IPCP:    Address 99.255.52.154 (0x03066375349A)
*Oct 27 13:14:33.289 PDT: Vi1 PPP: Process pending ncp packets
*Oct 27 13:14:33.301 PDT: Vi1 IPCP: I CONFNAK [REQsent] id 1 len 10
*Oct 27 13:14:33.301 PDT: Vi1 IPCP:    Address 99.255.52.158 (0x03066375349E)
*Oct 27 13:14:33.301 PDT: Vi1 IPCP: O CONFREQ [REQsent] id 2 len 4
*Oct 27 13:14:33.313 PDT: Vi1 IPCP: I CONFACK [REQsent] id 2 len 4
*Oct 27 2010 13:14:33.317 PDT: %SYS-5-CONFIG_I: Configured from console by console
*Oct 27 13:14:33.337 PDT: Vi1 IPCP: I CONFREQ [ACKrcvd] id 114 len 10
*Oct 27 13:14:33.337 PDT: Vi1 IPCP:    Address 151.164.186.13 (0x030697A4BA0D)
*Oct 27 13:14:33.337 PDT: Vi1 IPCP: O CONFACK [ACKrcvd] id 114 len 10
*Oct 27 13:14:33.337 PDT: Vi1 IPCP:    Address 151.164.186.13 (0x030697A4BA0D)
*Oct 27 13:14:33.337 PDT: Vi1 IPCP: State is Open
*Oct 27 13:14:33.341 PDT: Di1 IPCP: Install route to 151.164.186.13
*Oct 27 13:14:33.341 PDT: Vi1 IPCP: Add link info for cef entry 151.164.186.13
*Oct 27 13:14:33.361 PDT: Vi1 IPCP: I TERMREQ [Open] id 115 len 4
*Oct 27 13:14:33.365 PDT: Vi1 IPCP: O TERMACK [Open] id 115 len 4
*Oct 27 13:14:33.365 PDT: Vi1 IPCP: State is Closed
*Oct 27 13:14:33.365 PDT: Vi1 IPCP: Remove link info for cef entry 151.164.186.13
*Oct 27 13:14:33.365 PDT: Di1 IPCP: Remove route to 151.164.186.13
*Oct 27 13:14:34.281 PDT: Vi1 IPCP: O CONFREQ [Closed] id 3 len 10
*Oct 27 13:14:34.281 PDT: Vi1 IPCP:    Address 99.117.52.154 (0x03066375349A)
*Oct 27 2010 13:14:34.285 PDT: %LINEPROTO-5-UPDOWN: Line protocol on Interface Virtual-Access1, changed state to up
*Oct 27 13:14:34.293 PDT: Vi1 IPCP: I CONFREQ [REQsent] id 116 len 10
*Oct 27 13:14:34.293 PDT: Vi1 IPCP:    Address 151.164.186.13 (0x030697A4BA0D)
*Oct 27 13:14:34.293 PDT: Vi1 IPCP: O CONFACK [REQsent] id 116 len 10
*Oct 27 13:14:34.293 PDT: Vi1 IPCP:    Address 151.164.186.13 (0x030697A4BA0D)
*Oct 27 13:14:34.293 PDT: Vi1 IPCP: I CONFNAK [ACKsent] id 3 len 10
*Oct 27 13:14:34.293 PDT: Vi1 IPCP:    Address 99.117.52.158 (0x03066375349E)
*Oct 27 13:14:34.293 PDT: Vi1 IPCP: O CONFREQ [ACKsent] id 4 len 4
*Oct 27 13:14:34.305 PDT: Vi1 IPCP: I CONFACK [ACKsent] id 4 len 4
*Oct 27 13:14:34.309 PDT: Vi1 IPCP: State is Open
*Oct 27 13:14:34.309 PDT: Di1 IPCP: Install route to 151.164.186.13
*Oct 27 13:14:34.309 PDT: Vi1 IPCP: I TERMREQ [Open] id 117 len 4
*Oct 27 13:14:34.309 PDT: Vi1 IPCP: O TERMACK [Open] id 117 len 4
*Oct 27 13:14:34.313 PDT: Vi1 IPCP: State is Closed
*Oct 27 13:14:34.313 PDT: Vi1 IPCP: Add link info for cef entry 151.164.186.13
*Oct 27 13:14:34.313 PDT: Vi1 IPCP: Remove link info for cef entry 151.164.186.13
*Oct 27 13:14:34.313 PDT: Di1 IPCP: Remove route to 151.164.186.13

Thanks In advance

Christopher Tomlinson

1 Accepted Solution

Accepted Solutions

paolo bevilacqua
Hall of Fame
Hall of Fame

*Oct 27 13:14:34.309 PDT: Vi1 IPCP: I TERMREQ [Open] id 117 len 4

ISP is closing PPP for unknow reasons, so nothing works, and nothign is pingable.

They must be able to state why they are torning down the connection.

View solution in original post

3 Replies 3

paolo bevilacqua
Hall of Fame
Hall of Fame

*Oct 27 13:14:34.309 PDT: Vi1 IPCP: I TERMREQ [Open] id 117 len 4

ISP is closing PPP for unknow reasons, so nothing works, and nothign is pingable.

They must be able to state why they are torning down the connection.

Paolo

The ISP was in fact sending a terminate notification since our router refused the DHCP request configured from ISP.

It took a bit of time to get ISP to reconfigure the circuit for the static IP the customer required.  All up and working.

Thank you for you help

Christopher Tomlinson

.

Right, I didn't noticed that.

*Oct 27 13:14:33.301 PDT: Vi1 IPCP: I CONFNAK [REQsent] id 1 len 10
*Oct 27 13:14:33.301 PDT: Vi1 IPCP:    Address 99.255.52.158 (0x03066375349E)
*Oct 27 13:14:33.301 PDT: Vi1 IPCP: O CONFREQ [REQsent] id 2 len 4

Thanks for the nice rating and good luck!

Review Cisco Networking for a $25 gift card