Dynamic Router Advertisement Configuration Overview

In a network deployment where router interfaces are configured statically, you might need to configure the Router Advertisement Protocol on only a small number of interfaces on which it might run. However, in a subscriber access network, static configuration of the Router Advertisement Protocol becomes impractical because the number of interfaces that potentially need the Router Advertisement Protocol increases substantially. In addition, deploying services in a dynamic environment requires dynamic modifications to interfaces as they are created.

Subscriber access supports the configuration of the Router Advertisement Protocol at the [edit dynamic-profiles profile-name protocols] hierarchy level. By specifying Router Advertisement Protocol statements within a dynamic profile, you can dynamically apply a Router Advertisement configuration when a subscriber connects to an interface using a particular access technology (for example, DHCP), enabling the subscriber to access a carrier (multicast) network.

To minimally configure the Router Advertisement Protocol requires that you include the router-advertisement statement at the [edit dynamic-profiles profile-name protocols] hierarchy level and the interface statement along with the $junos-interface-name dynamic variable. All other statements are optional.

Note: Statements used for Router Advertisement Protocol configuration at the [edit dynamic-profiles profile-name protocols] hierarchy level are identical in function to those same statements used for static Router Advertisement Protocol configuration, with the exception of the interface and prefix statements, which use dynamic variables.