Unable to use custom-template with NSO6.1: Hi Team,I am trying to add custom-template to L3VPN and getting error.Attaching the screenshot.ct-RPXR.xml<devices xmlns="http://tail-f.com/ns/ncs"><template><name>ct-RPXR</name><ned-id><id xmlns:cisco-iosxr-cli-7.44="http://tail-f.com/ns/ned-id/cisco-iosxr-cli-7.44">cisco-iosxr-cli-7.44:cisco-iosxr-cli-7.44</id><config><route-policy xmlns="http://tail-f.com/ned/cisco-ios-xr"><name>RP-FOR-COMMUNITY</name><value> if community matches-any ({$COMMUNITY_1}, {$COMMUNITY_2}) thenset extcommunity color COLOR_400endif</value></route-policy></config></ned-id></template></devices>Thanks,Kanchan
Hi Kanchan,Does this custom-templale work on previous NSO version? Or Is this the first time you try this format?i tried this route policy format on device side and it does not take itRP/0/RP0/CPU0:PE1(config)#route-policy TESTRP/0/RP0/CPU0:PE1(config-rpl)#if community matches-any ? (     Begin inline community set parameter Identifier specified in the format: '$' followed by alphanumeric characters WORD    Community set nameRP/0/RP0/CPU0:PE1(config-rpl)#if community matches-any (1.1.1.1, 2.2.2.2) then                             ^% Invalid input detected at '^' marker.Regards,LinhHi Linh,Yes it use to work, I just updated with NED version. earlier it was 7.38Thanks,KanchanHi Linh,I figured out that for community variable has to be in format int:int. so with value 66:1,66:2 it is workingThanks,KanchanHi Kanchan,Thanks for the update. It seems device issue and new NED ONLY accept certain format. If there is no other issue, i would like to close the ticketRegards,LinhThanks Linh for the help, you can close the ticket.Regards,KanchanDifferent format is used