ip-route-advertisement and allow-ip-int-bind commands are not allowed in this type of domain. An example of configuration for an L2-DOMAIN association is shown below:
*B:Dut>config>service# info
...
vsd
domain nuage_501 type l2-domain create
description "nuage_501_l2_domain"
no shutdown
exit
*B:Dut>config>service# vpls 501
*B:Dut>config>service>vpls# info
----------------------------------------------
bgp
route-distinguisher 192.0.2.2:52
vsi-import ‟policy-1”
vsi-export ‟policy-1”
exit
bgp-evpn
exit
sap 1/1/1:501 create
exit
spoke-sdp 10:501 create
no shutdown
exit
vsd-domain "nuage_501"
no shutdown
----------------------------------------------
If there is no vsi-import/export policy, the received dynamic route-target is added in the vpls>bgp context, and is used for all the BGP families in the service.
If there is a vsi-import/export policy, the dynamic route-target is added to the policy, in an auto-created community that is shown with the following format: ‟_VSD_svc-id”. That community is added to dynamically created entries 1000 and 2000 in the first policy configured in the service vsi-import and vsi-export commands. This allows the user to allocate entries before entries 1000 and 2000 in case other modifications have to be made (user entries would have an action next-entry). An example of the auto-generated entries is shown below:
*A:PE# show router policy "policy-1"
entry 900 # manual entry
from
as-path ‟null"
family evpn
exit
action next-entry
local-preference 500
exit
exit
entry 1000 # automatic VSD-generated entry
from
community "_VSD_1"
family evpn
exit
action accept
exit
exit
entry 2000 # automatic VSD-generated entry
from
family evpn
exit
action accept
community add "_VSD_1"
exit
exit