Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: Cisco: NSP

DHCP_PD / IPv6

 

 

Cisco nsp RSS feed   Index | Next | Previous | View Threaded


vikas.hazrati at googlemail

Nov 6, 2009, 12:03 PM

Post #1 of 2 (542 views)
Permalink
DHCP_PD / IPv6

Hello all

I have been trying testing DHCP-PD functionality for ADSL / PPPoE users.
Using basic cisco-site examples I was
able to assign an IPv6 prefix to the CPE. The problem I am facing is the
following:

When the PPPoE session is torn down, the corresponding Virtual-Access
interface (and ipv6 routes) are deleted from
the NAS as expected, but in the CPE the DHCP-client remains up. So when the
PPPoE session is restablished no
new routes are installed in the NAS routing table for the DHCP delegated
prefixes, so no traffic can be forwarded to the
customer subnet.

The question is how can I make sure that in a DHCP-PD environment, the DHCP
client of the CPE is reinitialized
when the PPPoE session used for internet connectivity is re-established

The config used on the CPE side is really simple

interface Dialer 123
encapsulation ppp
dialer pool 123
ipv6 address autoconfig default
ipv6 enable
ipv6 dhcp client pd DHCP_PD
ppp pap sent-username **** password 0 ****


Any help is welcomed
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/


illcritikz at gmail

Nov 7, 2009, 12:13 AM

Post #2 of 2 (486 views)
Permalink
Re: DHCP_PD / IPv6 [In reply to]

The "fix" is to clear ipv6 dhcp client Dialer123

I use event manager to do this automagically for me like so:

event manager applet monitor_ipv6_dhcp
event syslog pattern "DIALER-6-BIND"
action 1.0 cli command "clear ipv6 dhcp client Dialer1"

This reacts to an event in the log of "DIALER-6-BIND" which for me is my
Dialer re-establishing its PPP session, do a clear int d123 and check your
logs to verify this for you.


You can view the results of event manager by:


router#sh event manager history events
No. Time of Event Event Type Name
1 Sat Nov 7 11:12:56 2009 syslog applet: monitor_ipv6_dhcp


and of course a sh ipv6 dhcp interface d123 will show you your new lease
aswell.


Cheers,


Ben

On Sat, Nov 7, 2009 at 7:03 AM, vikas hazrati
<vikas.hazrati [at] googlemail>wrote:

> Hello all
>
> I have been trying testing DHCP-PD functionality for ADSL / PPPoE users.
> Using basic cisco-site examples I was
> able to assign an IPv6 prefix to the CPE. The problem I am facing is the
> following:
>
> When the PPPoE session is torn down, the corresponding Virtual-Access
> interface (and ipv6 routes) are deleted from
> the NAS as expected, but in the CPE the DHCP-client remains up. So when the
> PPPoE session is restablished no
> new routes are installed in the NAS routing table for the DHCP delegated
> prefixes, so no traffic can be forwarded to the
> customer subnet.
>
> The question is how can I make sure that in a DHCP-PD environment, the DHCP
> client of the CPE is reinitialized
> when the PPPoE session used for internet connectivity is re-established
>
> The config used on the CPE side is really simple
>
> interface Dialer 123
> encapsulation ppp
> dialer pool 123
> ipv6 address autoconfig default
> ipv6 enable
> ipv6 dhcp client pd DHCP_PD
> ppp pap sent-username **** password 0 ****
>
>
> Any help is welcomed
> _______________________________________________
> cisco-nsp mailing list cisco-nsp [at] puck
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>
_______________________________________________
cisco-nsp mailing list cisco-nsp [at] puck
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/

Cisco nsp RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.