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

Router 827 suddenly cannot negotiate for IP address

Hi,

Problem 1:-

I got problems with the adsl router when suddenly the default static route is lost. The "sh ip int brief" shows that the Dialer interface is still up but no ip address is shown.

I always have to reload the router in order to get it to work. Is there other ways to get it working without a reload? I tried a shut and "no shut" on the dialer interface but it did not work.

Problem 2:-

I got also statements in the same router that says below:-

pvc 0/100

encapsulation aal5mux ppp dialer

dialer pool-member 1

!

dsl operating-mode auto

hold-queue 224 in

Can anyone tell me what the above means???

I am a newbie to adsl routers.

adrian

  • Other Network Infrastructure Subjects
2 REPLIES
Cisco Employee

Re: Router 827 suddenly cannot negotiate for IP address

I assume that you are using the PPPoE configuration on 827.

1)The dialer interface will remain up/up spoofing always but the virtual-access interface which will be clonned from that dialer interface will receive the ip address.

So "sh users" or "sh ip interface brief" should show atm0 and vi-access up/up with the ip address allocated to vi-access. If vi-access dosen't have ip address then try to bounce the atm0 interface using shut/no shut.

2)The config shows the pvc information and encapsulation on the dsl line. That config is normal and required for PPPoE.

Pl. visit following url for config and troubleshooting of PPPoE on 827

http://www.cisco.com/warp/customer/794/827pppoe_client.html

New Member

Re: Router 827 suddenly cannot negotiate for IP address

The virtual access interface will not be shown with the ip address. The ip address which is negotiated will be assigned to the Dialer interface. The following is my lab setup where Dialer 2 is getting ip address via IPCP.

router#sh ip int brief

Interface IP-Address OK? Method Status Protocol

FastEthernet0/0 10.77.152.221 YES manual up up

ATM0/1 unassigned YES TFTP administratively down down

ATM0/1.1 2.2.2.2 YES TFTP administratively down down

FastEthernet0/1 unassigned YES TFTP up up

Virtual-Access1 unassigned YES unset up up

Virtual-Access2 unassigned YES unset up up

Dialer0 172.16.10.1 YES TFTP up up

Dialer1 1.1.1.2 YES TFTP up up

Dialer2 20.20.20.21 YES IPCP up up

Loopback0 40.40.40.40 YES TFTP up up

ATM0/0 unassigned YES TFTP up up

ATM0/0.1 unassigned YES unset up up

ATM0/0.2 unassigned YES unset up up

ATM0/0.3 3.3.3.3 YES TFTP up up

ATM0/0.4 4.4.4.4 YES TFTP up up

yourname#sh run int di2

Building configuration...

Current configuration : 252 bytes

!

interface Dialer2

ip address negotiated

ip mtu 1452

encapsulation ppp

dialer pool 3

dialer-group 3

no cdp enable

ppp authentication chap pap callin

ppp chap hostname sdm

ppp chap password 0 sdm

ppp pap sent-username sdm password 0 sdm

end

yourname#sh run int f0/1

Building configuration...

Current configuration : 158 bytes

!

interface FastEthernet0/1

no ip address

duplex auto

speed auto

pppoe enable

pppoe-client dial-pool-number 3

no cdp enable

end

Try giving Shut and no shut on both the ATM as well as the dialer interface. this should solve the problem.

-Deepu

121
Views
0
Helpful
2
Replies
This widget could not be displayed.