L3VPN service with XE with NSO 5.0 M4: We are not able to create l3vpn service with XE endpoint, we used sample payload from release notesHi Sahiti,Under list of known issues I see followingI tried putting RD under node but running into another issue<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">  <error>    <error-type>application</error-type>    <error-tag>malformed-message</error-tag>    <error-path xmlns:l3nm="urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw">/l3nm:l3vpn-ntw/l3nm:vpn-services</error-path>    <error-message>unknown element: RD in /l3nm:l3vpn-ntw/l3nm:vpn-services/l3nm:vpn-service/l3nm:vpn-nodes/l3nm:vpn-node</error-message>  </error></errors>Has anyone else able to successfully create service for XE that we can leverage the payloadWe were using sample payload from Yevegeny and team, and that is based on NSO CFP documentation as wellThx,VaishaliFrom: Sahithi Patibandla (sahpatib) <sahpatib@cisco.com>Date: Tuesday, December 6, 2022 at 9:29 AMTo: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>, Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4Hi Vaishali,There have been quite many changes in M4 w.r.t service creation. We have moved to the newer IETF model for L3VPN in M4 release.Please look at the release details uploaded and the wiki we have provided with the release.This release includes:XR 7.7.2 CLI NED supportXR 7.8.1 CLI NED support with SIT buildXR 7.9.1 CLI NED support with DT buildRemoval of L2 Flat modelsRemoval of L3 Flat modelsUpgrade L3NM models to RFC version5G Slicing SRTE supportUpdate L2 and L3 Route Policy guided by IETF standardHighlighted changes are pertaining to the L3 VPN service.P.S: The wiki details and the above release notes are provided in the release email as well.ThanksSahithiFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Tuesday, December 6, 2022 at 8:54 AMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Cc: Sahithi Patibandla (sahpatib) <sahpatib@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4+Sahiti as wellTo see if any delta between M3 and M4 that might have caused issue w.r.t service creation with XE?Thx,VaishaliFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Monday, December 5, 2022 at 11:52 PMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>, Jason Zhang (jaszhang) <jaszhang@cisco.com>, Jen-Shue Shih (jeshih) <jeshih@cisco.com>Subject: Re: L3VPN service with XE with NSO 5.0 M4Keeping Jason and JenShue also in the loopHi Yevgeny, Manivel, Shlomi,Did any of you try XE service on M4 milestone build and did it work?Thx,VaishaliFrom: Vaishali Mithbaokar (vmithbao) <vmithbao@cisco.com>Date: Monday, December 5, 2022 at 10:53 PMTo: Yevgeny Chechelnitsky (ychechel) <ychechel@cisco.com>, Manivel Sengottuvel -X (msengott - HCL TECHNOLOGIES LIMITED at Cisco) <msengott@cisco.com>, Shlomi Eliyahu (seliyahu) <seliyahu@cisco.com>Subject: L3VPN service with XE with NSO 5.0 M4Hi All,I had used your collection for M3 and was able to create L3VPN on XE endpointBut now we switched to M4, and am running into following when using M4 postman collection<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">  <error>    <error-type>application</error-type>    <error-tag>malformed-message</error-tag>    <error-path xmlns:l3nm="urn:ietf:params:xml:ns:yang:ietf-l3vpn-ntw">/l3nm:l3vpn-ntw/l3nm:vpn-services</error-path>    <error-message>/l3vpn-ntw/vpn-services/vpn-service{L3VPN_NM-NATIVE-IPV4-500}: STATUS_CODE: TSDN-IETF-L3NM-416REASON: Route-distinguisher is mandatory when configuring L3VPN service on a XE deviceCATEGORY: validationSEVERITY: ERRORContext [name = Missing route-distinguisher. RD is mandatory for XEstate = {'Endpoint': 'AA-ASR903-2', 'Keypath': '/l3nm:l3vpn-ntw/vpn-services/vpn-service{L3VPN_NM-NATIVE-IPV4-500}'}]</error-message>  </error>
Hi Vaishali ,Please share your payload that you usedThanks,Linh<vpn-services><vpn-service><vpn-id>XE-L3VPN_NM-NATIVE-IPV4-500</vpn-id><vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id><rd>0:50:50</rd><address-family><address-familyxmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">ipv4</address-family><vpn-targets><vpn-target><id>51</id><route-targets><route-target>0:51:51</route-target></route-targets><route-target-type>both</route-target-type></vpn-target><vpn-target><id>52</id><route-targets><route-target>0:52:52</route-target></route-targets><route-target-type>import</route-target-type></vpn-target><vpn-target><id>53</id><route-targets><route-target>0:53:53</route-target></route-targets><route-target-type>export</route-target-type></vpn-target></vpn-targets></address-family></vpn-instance-profile></vpn-instance-profiles><vpn-nodes><vpn-node><vpn-node-id>AA-ASR903-3</vpn-node-id>        <RD>0:50:50</RD><local-as>1</local-as><vpn-network-accesses><vpn-network-access><id>1</id><interface-id>Loopback50</interface-id><ip-connection><ipv4><local-address>100.100.100.3</local-address><prefix-length>24</prefix-length></ipv4></ip-connection><routing-protocols><routing-protocol><id>EBGP</id><type xmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">bgp-routing</type><bgp><address-family>ipv4</address-family><redistribute-connected><address-family>ipv4</address-family></redistribute-connected><neighbor>100.100.100.2</neighbor><peer-as>50</peer-as><multihop>11</multihop></bgp></routing-protocol></routing-protocols></vpn-network-access></vpn-network-accesses><active-vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id></vpn-instance-profile></active-vpn-instance-profiles></vpn-node><vpn-node><vpn-node-id>AA-ASR903-2</vpn-node-id>        <RD>0:50:50</RD><local-as>1</local-as><vpn-network-accesses><vpn-network-access><id>1</id><interface-id>Loopback50</interface-id><ip-connection><ipv4><local-address>100.100.100.2</local-address><prefix-length>24</prefix-length></ipv4></ip-connection><routing-protocols><routing-protocol><id>EBGP</id><type xmlns:vpn-common="urn:ietf:params:xml:ns:yang:ietf-vpn-common">bgp-routing</type><bgp><address-family>ipv4</address-family><redistribute-connected><address-family>ipv4</address-family></redistribute-connected><neighbor>100.100.100.3</neighbor><peer-as>50</peer-as><multihop>11</multihop></bgp></routing-protocol></routing-protocols></vpn-network-access></vpn-network-accesses><active-vpn-instance-profiles><vpn-instance-profile><profile-id>L3VPN_NM-NATIVE-IPV4</profile-id></vpn-instance-profile></active-vpn-instance-profiles></vpn-node></vpn-nodes></vpn-service></vpn-services>Hi Vaishali,This is known issue and had a bug on this . It will be fix on coming release. Right now it has a work-arround by defining RD in active-vpn-instance-profiles under node level. Based on your payload, its format looks like this        <vpn-node-id>AA-ASR903-3</vpn-node-id>        <local-as>1</local-as>        <active-vpn-instance-profiles>         <vpn-instance-profile>           <profile-id>L3VPN_NM-NATIVE-IPV4</profile-id>          <rd>0:50:50</rd>         </vpn-instance-profile>        </active-vpn-instance-profiles>You should modify the same on the other end.Thanks,Linhthx much it worked!Thanks for let me know. I closed the ticket.The issue will fix in the coming release. Currently it works with workarround approach