Pre-requisites:
Enable subscriber management in the VPRN service.
Configure anti-spoof nh-mac in the group interface SAP or MSAP policy, with urpf-check optionally configured in the group interface to compensate for IP anti-spoofing not being enabled.
An ESM dynamic BGPv4 peer is established for a routed subscriber host if the 26.6527.55 Alc-BGP-Policy VSA returned in a RADIUS Access-Accept message contains the name of a local configured BGP peering policy and an ESM dynamic peer group is configured in the VPRN BGP context, as shown in the following classic CLI example.
config>subscr-mgmt
bgp-peering-policy "bgpv4-policy-1" create
local-address 10.3.2.254
local-as 65536
peer-as 65501
type external
exit
config>service>vprn
bgp
group "esm-dyn-peer-group-1" esm-dynamic-peer
exit
no shutdown
exit
The following example shows the MD-CLI equivalent.
[pr:/configure subscriber-mgmt]
bgp-peering-policy "bgpv4-policy-1" {
local-address 10.3.2.254
peer-as 65501
type external
local-as {
as-number 65536
}
}
[pr:/configure service vprn "submgmt-vprn-2000"]
bgp {
group "esm-dyn-peer-group-1" {
admin-state enable
static-group false
}
}
The subscriber host IPv4 address is used as the BGP peer IP address.
The local address can be the subscriber interface IPv4 address (single hop BGP peer) or a loopback interface IPv4 address (multi-hop BGP peer).
See BGP peering parameters for more information about how the other BGP peering parameters can be specified and Import and export policies for ESM dynamic BGP peers for more information about route policies.
To verify that an ESM dynamic BGPv4 peer is correctly installed, use the following show commands:
show service id service-id ipoe session detail
show service id service-id ppp session detail
Example output:
Bgp Peering Policy : bgpv4-policy-1
Bgp Peer Status : installed
To verify the state of an ESM dynamic BGPv4 peer, use the show router router-instance bgp summary command.