[c-nsp] ASR9k/IOS-XR BNG for IPoE (DHCP) help

[Bradley Williamson]

What version of code are you running. There is a bug in DHCP after 4.1. I
have been working with Cisco on this and they finally acknowledged it is a
bug. We have no date for a patch yet.

We are using ASR9010 with 4.2.1 software.

I cannot get any cpe routers to pull IP addresses, but if I just plug a
laptop in it works.

Not sure if you are seeing a similar issue.

Brad



On 6/6/13 5:13 PM, "Simon Lockhart" <simon at slimey.org> wrote:

>All,
>
>I'm currently evaluating the ASR9001 as a BNG for IPoE traffic (Double
>VLAN
>tagged traffic, doing DHCP) - but I'm having difficulties getting the DHCP
>proxy bit working. Has anyone done this before, or can anyone help point
>me
>in the direction of why my config isn't working?
>
>I've been working through the example at
>https://supportforums.cisco.com/docs/DOC-19702 and have come up with the
>following config:
>
>------ 8< -------- 8< ---------
>dhcp ipv4
> profile IP_DEFAULT proxy
>  helper-address vrf default 192.168.130.20 giaddr 100.64.248.129
>  relay information check
>  relay information option
>  relay information policy keep
>  relay information option allow-untrusted
> !        
> interface Bundle-Ether1.3121 proxy profile IP_DEFAULT
>!         
>interface Bundle-Ether1.3121
> ipv4 address 100.64.248.129 255.255.255.192
> service-policy type control subscriber IP_PM
> ipsubscriber ipv4 l2-connected
>  initiator dhcp
> !
> encapsulation ambiguous dot1q 3121 second-dot1q any
>!
>interface TenGigE0/0/2/1
> bundle id 1 mode on
>!
>dynamic-template
> type ipsubscriber IPSUB_TPL
> !
>!
>class-map type control subscriber match-any DHCP
> match protocol dhcpv4
> end-class-map
>!
>policy-map type control subscriber IP_PM
> event session-start match-first
>  class type control subscriber DHCP do-until-failure
>   5 activate dynamic-template IPSUB_TPL
>  !
> !
> end-policy-map
>!
>end
>
>------ 8< -------- 8< ---------
>
>Now, if I do "debug dhcp ipv4", I can see my DHCP requests coming in, and
>it
>starts to process them, but the requests are never forwarded to my DHCP
>server.
>
>If I do "show dhcp ipv4 proxy binding detail", it sees the client ok, but
>doesn't show the server address:
>
>------ 8< -------- 8< ---------
>RP/0/RSP0/CPU0:test-asr9k.lab.cc#show dhcp ipv4 proxy binding detail
>Thu Jun  6 22:08:00.070 UTC
>MAC Address:                 100d.7f4d.1cda
>VRF:                         default
>Server VRF:                  -
>IP Address:                  0.0.0.0
>Giaddr from client:          0.0.0.0
>Giaddr to server:            0.0.0.0
>Server IP Address:           0.0.0.0
>Server IP Address to client: 0.0.0.0
>ReceivedCircuit ID:          Xxx-21 eth 3/1/2/1/1:102
>InsertedCircuit ID:          Xxx-21 eth 3/1/2/1/1:102
>ReceivedRemote ID:           SimonsHouse
>InsertedRemote ID:           SimonsHouse
>ReceivedVSISO:               -
>InsertedVSISO:               -
>Auth. on received relay info:FALSE
>Profile:                     IP_DEFAULT
>State:                       INIT
>Proxy lease:                 60 secs (00:01:00)
>Proxy lease remaining:       22 secs (00:00:22)
>Client ID:                   0x01-0x10-0x0D-0x7F-0x4D-0x1C-0xDA
>Access Interface:            Bundle-Ether1.3121
>Access VRF:                  default
>VLAN Id:                     outer 3121, inner 102
>Subscriber Label:            0x0
>*
>
>* Next renew request from this client will be NAK'd in order to recreate
>subscriber session
>
>------ 8< -------- 8< ---------
>
>
>Any ideas why it might not be forwarding on the DHCP requests?
>
>Many thanks in advance,
>
>Simon
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/
>