PBB-CUSTOME over ODN policy : Trying tocreate PBB-Custom scenario with two end points with underlying ODN policy .Payload ; dry- run attached This is howI define my route policies <l2vpn-route-policy xmlns=><name>L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-A-430</name> <color> <id>430</id> <ipv4> <rd>430:430</rd> </ipv4> </color> </l2vpn-route-policy> <l2vpn-route-policy xmlns=><name>L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-B-430</name> <color> <id>430</id> <ipv4> <rd>430:431</rd> </ipv4> </color> </l2vpn-route-policy>Whenexecuting dry run, on one side default evpn-route type is applied if evpn-route-type is 1 then&#13; set extcommunity color COLOR_430&#13; endifAnd on the other is not applied. NSO: admin/Public1234!
 Hi Yevgeny,I checked your setup. This is your l2vpn-route-policy settingsl2vpn-route-policy L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-A-430 { color 430 {  ipv4 {   rd [ 430:430 ];  } }}l2vpn-route-policy L2VPN_NM-PBB-CUSTOM-SRTE-ODN-PE-B-430 { color 430 {  ipv4 {   rd [ 430:431 ];  }  evpn-route-type {   route-type [ 1 2 ];  }What you see is expected! It seems the l2vpn-route-policy name is already exist with evpn-route-type!Please clean up your l2vpn-route-policy and retest again.Thanks,LinhHi Yevgeny,I will close this ticket in a few days if there is no update from your side.Thanks,LinhGot it 