Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Maximum Number of IPv6 Prefixes Assigned to Clients by Using Both DHCPv6 Local Server and Neighbor Discovery Router Advertisements

    When you use both IPv6 Neighbor Discovery router advertisements and DHCPv6 Prefix Delegation methods to assign IPv6 prefixes to clients, only two host routes for IPv6 are consumed from the routing table irrespective of the way in which the router advertisement prefix is determined. The following sections describe sample configuration scenarios to illustrate how you can delegate IPv6 prefixes to a maximum of 64,000 subscribers, based on whether a unique IPv6 prefix is allocated to a client or the same IPv6 prefix is allocated to multiple clients:

    Unique IPv6 Prefix Delegated Per Subscriber

    Consider a scenario in which the RADIUS server is configured to assign a unique router advertisement prefix route to each IPv6 subscriber. In such a case, one route is used for neighbor discovery and one IPv6 route is consumed for prefix delegation. Therefore, it is possible to support 64,000 IPv6 bindings with 128,000 IPv6 static routes.

    The following output of the show ipv6 route command displays how two routes are used by the same subscriber, as can be seen from the Interface field in the output. The routes are assigned using Prefix Delegation and the access-internal route, such as the DHCP and AAA/PPP host route, which is a host route to directly connected clients. Access routes, also known as AAA framed routes, are sourced by AAA.

    host1#show ipv6 route
    Prefix/Length                      Type      Dst/Met     Interface 
    -------------------------------- 	---------  --------   ---------------- 
    1111:1111:1111:1111::/64          	Access     3/0 	      GigabitEthernet0/2.600.6
    1111:1111:2222:2222:21b:c0ff:fe4 	 AccIntern  2/0 	      GigabitEthernet0/2.600.6 b:9d00/128

    Same IPv6 Prefix Delegated to Multiple Subscribers

    Consider a scenario in which the same prefix with a length of /64 for ICMPv6 neighbor discovery router advertisements is assigned to all subscribers by configuring the prefix in the profile or by configuring the RADIUS server to send the same prefix in the Framed-IPv6-Prefix attribute (RADIUS IETF attribute 97) of the RADIUS-Access-Accept message.

    If you use this method for allocating IPv6 prefixes of /64 length to subscribers, neighbor discovery consumes one IPv6 route and prefix delegation consumes one IPv6 route, which results in a total of two IPv6 routes per subscriber being used. Therefore, it is possible to scale up to a maximum of 64,000 subscribers for delegation of IPv6 prefixes.

    The increased scaling limit of support for delegation of IPv6 prefixes using the DHCPv6 local server Prefix Delegation mechanism for 64,000 subscribers applies only to E120 and E320 routers and not to ERX14xx models, ERX7xx models, and the ERX310 router because the binding information is stored in the SRP modules of E120 and E320 routers. Also, a limitation exists on the number of IPv6 interfaces and the IPv6 routing table size supported by ERX routers that prevents the support for 64,000 subscribers for Prefix Delegation on DHCPv6 local servers running on those routers.

    To enable support for 64,000 subscribers for IPv6 Prefix Delegation, about 7.42 MB of memory on the SRP module is consumed additionally.

    Published: 2014-08-20