NCS- 6.0 M4 +: L2VPN P2p, RSVP, creation, we are seeing that MPLS label is compulsory: 1) CFP = nso-6.0-tsdn-5.0.0-M4+ENG-34.tar.gz2) Create l2vpn and RSVP. 3) While committing the payload in NSO, we see that it asking MPLS label mandatory.4) Please check the attached document5) Logs: 10.56.112.77:/tmp/data_121222_133343_dir/data_121222_133343.tgzlogin: auto1/Public1234!
 In TSDN 4.0 and 4.1 FP, mpls-label tagging was not mandatoryand device also doesnt need to have mpls-label as mandatory field.<mpls-label xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">111</mpls-label>can we know why this has been mandatory now ?Hello, we have created an internal ticket to fix this issue.Regards,Janaki DuggiralaHi janaki,Shouldnt we have CDETS for this as this is CFP bug?and also, why do we need to mention XMLNS for many tagging especially?for eg., <control-word xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">yes</control-word><metric xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l3vpn-ntw">123</metric><te-service-mapping xmlns="http://cisco.com/ns/nso/fp/examples/cisco-l2vpn-ntw">in ietf-te tunnel:., <head-end xmlns="http://cisco.com/ns/nso/fp/examples/cisco-te">without this xmlns, it says unknown element. Regarding xmlns:This is expected behavior with the new IETF model updates from TSDN 5.0 M3.Per design we have IETF augmentations in an external model, so it is required to define xmlns (namespace).Regarding CDETS, you may file one if you would like to.Thank you.This issue has been fixed and merged and is available in TSDN 5.0 M5 release.CSCwd93202 - is raised. Issue is not resolved in M5. Details are mentioned in cdetsHi Sampath, I did verified the issue are fixed before the M5 release. Does the M5 installed at 10.56.112.77? I will look at this server if you confirm.Thanks,Linhpls check : 10.56.116.138 as mentioned in the cdets10.56.112.77 is also M5, I tested on 10.56.116.138, which is also same version.It installed a wrong build. The file size of ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gz is different from 6.0 release installed in my setupYour setup:/opt/ncs/packages$ ls -ltr | grep l2vpn-nm<del>rw</del>------ 1 root root  148845 Dec 15 11:03 ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gzMine setup:$ ls -ltr | grep l2vpn-nm-rwxr-xr-x. 1 root root  149149 Dec 20 20:36 ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gzI also looked the codes in your ncs-6.0-ietf-l2vpn-nm-EXAMPLE-5.0.0.tar.gz. It does not have python codes with the fix.Please get a correct build and install it again-Linh