l2vpn route policy ->evpn-route-type ser: EVPN set is not being translated to device configuration. They yellow highlighted part is expected but not generated .In 4.0 it used to be a free text and user responsibility. In 5.0 it is suppose to be generated out of configuration, but is not cheapening  
Hi Yevgeny,Please provide us the complete route-policy payload, since we need the policy-definition to investigate the policy being pushed to device.Thanks,NikhilHi Nikhil,PFA the payload including the service and the route policy. This was tested on a clean device configuration and failed to produce a working service.Thanks, Shlomi Had meeting with Customer. Requested updated payload for route-policy using RFC standard.Payload from customer contains 2 conditions with 1 action. This is not allowed as mentioned in wikiRequested customer to create 2 statements for each condition.Issue fixed for L2 route-policy, confirmed by customer as above.Following our meeting PFA the extra policy payloads we have been using and that have been failing Hello Shlomi, The payloads you have provided have missing vpn-nodes. Please check and fix. I have attached the sample payload we have tested with. We see the route-policy being pushed successfully to the device. As you can see in the screenshot, the APPEND_RPL was appended to the route-policy --> L3VPN_NM-SRTE-ODN-PE-A-44 Note: Please keep in mind that when you use the extra-policy field it will only push the string associated to the policy and not the policy definition. Let us know if all questions are answered.After investigating and undeploying / redploying L2VPN services with route policies I came across a weird finding: The provisioning is successful but only for the first service, if there is another L2 service that uses same evpn-route-type tag, the tunnel will fail to come up. I tried removing all previous services and provisioned one by one. The first one was successful, but after the second one, the tunnels belonging to the first service were gone. As the evpn-route-type tag can only have values 1, 3 this allows us to provision no more than two services successfully.Please advise.We would like to clarify thatevpn-route-type is not a "tag" but refers to types of traffic so it can be associated with multiple services.There is no validation stating that it should be only 1 and 3 either.Please also share your setup details in this ticket for further investigation.Adding the meeting minutes here:verified the commands being sent from NSO to the VXR are accurate and fit the info on postman commandsWhen using several EVPN_SET configurations in different services, they collide but we cannot tell if it is a VXR related limitationable to provision services 420 ; 290 simultaneously by dividing EVPN_SETs 1 ; 3 between themTE tunnels for service 250 are still not operational, possibly due to missing BGP connectivity between PE-A and PE-CL3 services might also be missing due to same issue A.I CFP team to continue looking into it and updateNikhil will share VXR credentials with CFP team for further investigationHad a meeting with the user and cleared the doubts they had. The services were working as expected.Had a meeting with the user and cleared the doubts they had. The services were working as expected.