Enabling BGP over Dynamic PPPoE Subscriber Interfaces
BGP is supported over dynamic PPPoE interfaces for the IPv4 and IPV6 address families. You
must enable routing services with the routing-service statement in both the PPPoE subscriber dynamic profile and
the dynamic profile for the underlying VLAN interface.
You can create dedicated
VLAN dynamic profiles for subscriber interfaces that requires routing services.
For interfaces that do not require the BGP protocol support, you must create
a separate VLAN dynamic
profile without routing
services. For
example:
dynamic-profiles {
vlan profile 1 {
interfaces {
interface-name {
unit logical-unit-name {
routing-service {
enable;
}
}
}
}
}
}
dynamic-profiles {
vlan profile 2 {
interfaces {
interface-name {
unit logical-unit-name;
}
}
}
}In the above example, vlan profile 1 includes routing services
configuration, whereas vlan profile 2 remains without routing services.
Besides enabling or disabling routing services for all subscribers on the dynamic interface,
the routing-service statement enables you to use the RADIUS server to
selectively enable or disable routing services for a specific subscriber during authentication
if RADIUS server returns the Routing-Services VSA (26-212) in the Access-Accept message.
The system activates the routing services only during subscriber login and does not allow modification later through CoA (Change of Authorization).
If routing services are not enabled for the dynamic underlying interface, then the PPPoE subscriber is rejected during the first family profile activation.
In this configuration, the PPPoE subscriber clients correspond to BGP neighbors. This means
that when you configure the BGP neighbors with the [edit protocols bgp group name
neighbor] stanza, you must use the PPPoE client IP addresses as the BGP
neighbor addresses. The BGP peer addresses cannot be dynamically provisioned.
Support for BGP over dynamic PPPoE subscriber interfaces includes the following:
-
Route advertisement over the BGP-established PPPoE neighbor.
-
End-to-end bidirectional traffic from the core to the IP prefix advertised in the BGP route.
-
Dedicated next hops are created by the routing daemon for subscriber routes, rather than reusing shared next hops and pseudo logical interfaces.
The BGP over dynamic PPPoE interfaces feature does not support the following:
-
Multihop BGP
-
IBGP, because it might involve multihops
-
BFD for the PPPoE subscribers
-
Interface sets for the PPPoE subscribers
-
Aggregated Ethernet targeting
-
More than one routing protocol besides BGP over the same subscriber
-
MPLS termination on the PPPoE subscriber next hop
-
Subscribers over pseudowire interfaces over demux0 stacking
You can enable routing services for PPPoE subscribers over pseudowire interfaces only when the underlying VLAN is either a non-demux dynamic VLAN or a static VLAN.
The following interface stacking configurations are supported for routing-service-enabled PPPoE:
-
PPPoE over dynamic VLANs
-
PPPoE over static VLANs
-
PPPoE over stacked VLANs (with inner and outer VLAN IDs)
The underlying VLAN for which routing services is enabled supports:
-
Stacking of routing-service-enabled and routing-service-disabled PPPoE subscribers.
-
Stacking of other access models such as DHCP.
-
The parent physical interface can be a leg in an aggregated Ethernet bundle.