Related Documentation
- M, MX Series
- Best Practice: IPv6 Addressing for Logical Interfaces in PPPoE Dynamic Profiles with NDRA
- Best Practice: Static PPPoE Interfaces with NDRA
- IPv4 and IPv6 Dual Stack in a PPPoE Access Network
- How NDRA Works in a Subscriber Access Network
- Methods for Obtaining IPv6 Prefixes for NDRA
- Duplicate Prefix Protection for NDRA
- Overview of Configuration Tasks for IPv4 and IPv6 Dual-Stack in Subscriber Access Networks
Configuration Tasks for PPPoE Access Networks in Which NDRA Is Used
Configuring a PPPoE Dynamic Profile for Use with NDRA in a Dual-Stack Network
Configure a dynamic profile for IPv4 and IPv6 PPPoE subscribers that access the network. The dynamic profile defines the attributes of the dynamic PPPoE logical subscriber interface.
This dynamic profile is for configurations that use NDRA to assign a global IP address to the CPE WAN link.
To configure a PPPoE dynamic profile for NDRA:
- Create and name the dynamic profile. [edit]user@host# edit dynamic profiles PPPOE-dyn-ipv4v6-ndra
- If you are using routing instances, add a routing instance
to the profile and add an interface to the routing instance.
- Specify the $junos-routing-instance variable for the routing instance. The routing instance variable is dynamically replaced with the routing instance the accessing subscriber uses when connecting to the BNG.
- Specify the $junos-interface-name variable for the interface. The interface variable is dynamically replaced with the interface that the accessing subscriber uses when connecting to the BNG.
[edit dynamic profiles PPPOE-dyn-ipv4v6-ndra]user@host# set routing-instances $junos-routing-instance interface $junos-interface-name - Add a PPPoE logical interface (pp0) to the profile, and
specify $junos-interface-unit as the predefined variable
to represent the logical unit number for the interface. The variable
is dynamically replaced with the actual unit number supplied by the
network when the subscriber logs in.[edit dynamic profiles PPPOE-dyn-ipv4v6-ndra]user@host# edit interfaces pp0 unit $junos-interface-unit
Configure the IPv4 family for the pp0 interface as follows:
- If you are not using routing instances, assign an unnumbered
address. The unnumbered address enables the local address to be derived
from the specified interface and allows IP processing on the interface
without assigning an explicit IP address to the interface.
For example:
[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set family inet unnumbered-address lo0.0 - If you are using routing instances,
assign the predefined variable $junos-loopback-interface.
For example:
[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set family inet unnumbered-address $junos-loopback-interface
- If you are not using routing instances, assign an unnumbered
address. The unnumbered address enables the local address to be derived
from the specified interface and allows IP processing on the interface
without assigning an explicit IP address to the interface.
- Configure the IPv6 family for the pp0 interface, and assign $junos-ipv6-address as the predefined variable. Use this variable
when you are using router advertisement with or without routing instances.
This variable is replaced with the IPv6 address of the interface used
for router advertisements. [edit dynamic profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set family inet6 address $junos-ipv6-address
- Specify $junos-underlying-interface as the predefined
variable to represent the name of the underlying Ethernet interface
on which the router creates the dynamic PPPoE logical interface. The
variable is dynamically replaced with the actual name of the underlying
interface.[edit dynamic profiles PPPOE-dyn-ipv4v6-ndra pp0 interfaces pp0 unit "$junos-interface-unit"]user@host# set pppoe-options underlying-interface $junos-underlying-interface
- Define the router to act as a PPPoE server when a PPPoE
logical interface is dynamically created.[edit dynamic profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set pppoe-options server
- (Optional) Configure the PPP authentication protocol that
is used to identify and authenticate the CPE. Specify either chap or pap (or both).[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set ppp-options chap user@host# set ppp-options pap
- (Optional) Enable keepalives and set
an interval for keepalives. We recommend an interval of 30 seconds.
For example:[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra interfaces pp0 unit "$junos-interface-unit"]user@host# set keepalives interval 30
Configure the router advertisement protocol.
- Access the router advertisement configuration.[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra]user@host# edit protocols router-advertisement
- Specify the interface on which the NDRA configuration
is applied. Assign $junos-interface-name as the predefined
variable. The variable is replaced with the actual name of the interface.[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra protocols router-advertisement]user@host# edit interface $junos-interface-name
- Specify a prefix value contained in router advertisement
messages sent to the CPE on interfaces created with this dynamic profile.
If you specify the $junos-ipv6-ndra-prefix predefined variable, the actual value is obtained from a local pool or through AAA.
[edit dynamic-profiles PPPOE-dyn-ipv4v6-ndra protocols router-advertisement]user@host# set prefix $junos-ipv6-ndra-prefix
- Access the router advertisement configuration.
Configuring a Static PPPoE Logical Interface for NDRA
To configure a static PPPoE logical interface for static NDRA configurations:
- Specify the name and logical unit number of the interface.[edit]user@host# edit interfaces pp0 unit 1000
- Configure a description for the interface. [edit interfaces pp0 unit 1000]user@host# set description "static IPv4v6 dual stack, NDRA”
- Specify the family
inet6 source address. [edit interfaces pp0 unit 1000]user@host# set family inet6 address 2040:2004::1.1.1.1/64
- Configure an unnumbered address for family inet. [edit interfaces pp0 unit 1000]user@host# set family inet unnumbered-address lo0.0
- Specify the underlying Ethernet interface. [edit interfaces pp0 unit 1000]user@host# set pppoe-options underlying-interface ge-1/0/0.1000
- Define the router to act as a PPPoE server when the PPPoE
logical interface is created. [edit interfaces pp0 unit 1000]user@host# set pppoe-options server
- Access the router advertisement configuration, and specify
the prefixes that the BNG sends in router advertisements for the static
interface. Make sure that the prefixes match the source address configured
for the static PPPoE logical interface configured in Step 3. [edit]user@host# edit protocols router-advertisementuser@host# set interface pp0.1000 prefix 2040:2004::/64
Configuring an Address-Assignment Pool Used for Router Advertisements
If you are using local address-assignment pools to be used for router advertisement, create a pool and add IPv6 prefixes to the pool.
You must configure separate pools for DHCPv6 prefix delegation, DHCPv6 IA_NA, and router advertisement.
To configure an NDRA address-assignment pool.
- Create a pool for IPv6 prefixes used by NDRA. [edit]user@host# edit access address-assignment pool ndra-2010 family inet6
- Add IPv6 network prefixes to the pool.[edit access address-assignment pool ndra-2010 family inet6]user@host# set prefix 2001::/64
- Configure the name of the IPv6 address range and define
the range. For NDRA pools, specify the range by setting a prefix length
of 64. [edit access address-assignment pool ndra-2010 family inet6]user@host# set range ndra-range prefix-length 64
- Specify that the address-assignment pool is used for NDRA. [edit access address-assignment]user@host# set neighbor-discovery-router-advertisement ndra-2010
Configuring Duplicate Prefix Protection for Router Advertisement
If you are using AAA to supply IPv6 prefixes for router advertisement, you can enable duplicate prefix protection to prevent prefixes from being used more than once. If enabled, the following attributes received from external servers are checked:
- Framed-IPv6-Prefix
- Framed-IPv6-Pool
If a prefix overlaps with a prefix in an address pool, the prefix is taken from the pool if it is available. If the prefix is already in use, it is rejected as unavailable. If the prefix length requested from the external server does not match the pool’s prefix length exactly, the authentication request is denied. If configured, the Acct-Stop message will include a termination cause.
To configure duplicate prefix protection:
- Enter the access configuration.[edit]user@host# edit access
- Enable duplicate prefix protection.[edit access]user@host# address-protection
Related Documentation
- M, MX Series
- Best Practice: IPv6 Addressing for Logical Interfaces in PPPoE Dynamic Profiles with NDRA
- Best Practice: Static PPPoE Interfaces with NDRA
- IPv4 and IPv6 Dual Stack in a PPPoE Access Network
- How NDRA Works in a Subscriber Access Network
- Methods for Obtaining IPv6 Prefixes for NDRA
- Duplicate Prefix Protection for NDRA
- Overview of Configuration Tasks for IPv4 and IPv6 Dual-Stack in Subscriber Access Networks
Published: 2013-07-09
Related Documentation
- M, MX Series
- Best Practice: IPv6 Addressing for Logical Interfaces in PPPoE Dynamic Profiles with NDRA
- Best Practice: Static PPPoE Interfaces with NDRA
- IPv4 and IPv6 Dual Stack in a PPPoE Access Network
- How NDRA Works in a Subscriber Access Network
- Methods for Obtaining IPv6 Prefixes for NDRA
- Duplicate Prefix Protection for NDRA
- Overview of Configuration Tasks for IPv4 and IPv6 Dual-Stack in Subscriber Access Networks