NSO L3NM FP VPN endpoint port-id  attribute does not supports Tunnel-IP: I am trying to provide a Tunnel interface while configuring L3VPN. Looks like the port-id attribute is not allowing the type tunnel-IP. As per the yang, it seems string.ietf-l3vpn-nm --> ietf-l3vpn-ntw.yang(container vpn-network-accesses -> leaf port-id is referring -> l3vpn-svc:svc-id from ietf-l3vpn-svc@2018-01-19.yang) Inside the yang file : ietf-l3vpn-svc@2018-01-19.yang the leaf svc-id is declared as below.  typedef svc-id { type string; description "Defines a type of service component identifier."; }Also observed Tunnel-interface is not provided as an option in the dropdown of CNC UI (Services ; Traffic EngineeringProvisioning -> L3VPN/L3vpn-Service)Setup Details:==========CNC Versions: Crosswork Image Version: release-4.4.0 (Build 250) and Crosswork Infrastructure Version: 4.4.1 (Build rc.3)COE Version: v4.1.1-rc.5+build.10NED Version: cisco-iosxr-cli-7.40admin@ncs# show ncs-state | include versionncs-state version 5.7.6admin@ncs# show packages package package-versionNAME             PACKAGE VERSION-----------------------------------------------aws-common-actions      2.3.1aws-infoblox-provision    1.9.2aws-pedc-tunnel-actions    1.3aws-pedc-tunnel-service    2.1aws-tunnel-actions      2.2aws-tunnel-service      2.1cisco-aa-service-assurance  4.1.0cisco-cnfo          1.1.0cisco-flat-L2vpn-fp      4.1.0cisco-flat-L2vpn-fp-internal 4.1.0cisco-flat-L3vpn-fp      4.1.0cisco-flat-L3vpn-fp-internal 4.1.0cisco-ios-cli-6.77      6.77.9cisco-iosxr-cli-7.40     7.40.1cisco-iosxr-cli-7.46     7.46.4cisco-iosxr-nc-7.6      7.6cisco-iosxr-nc-7.7      7.7.1cisco-rsvp-te-fp       4.1.0cisco-sr-te-cfp        4.1.0cisco-sr-te-cfp-internal   4.1.0cisco-tsdn-core-fp-common   4.1.0cnfm-nc-1.1          1.1config-inventory       1.2core-fp-common        1.30.0core-fp-delete-tag-service  1.0.5core-fp-plan-notif-generator 1.0.6custom-template-utils     2.0.9cw-device-auth        4.4.0cw-dlm-fp           4.4.0-nso-5.7.6flat-l2vpn-multi-vendors   4.1.0flat-l3vpn-multi-vendors   4.1.0ietf-l2vpn-nm         4.1.0ietf-l3vpn-nm         4.1.0ietf-te-fp          4.1.0lsa-utils           1.0.1resource-manager       3.5.7sr-te-multi-vendors      4.1.0 ========================================================admin@ncs# show running-config devices device 20.0.1.14 | de-select configdevices device 20.0.1.14address  20.0.1.14device-type cli ned-id cisco-iosxr-cli-7.40state admin-state unlocked!
 Hi Srinivasa,Below are the port types we support in L3NM FP:Bundle-Ether,BVI,FiftyGigE,FortyGigE,FourHundredGigE,HundredGigE,Loopback,TenGigE,TwentyFiveGigE,TwoHundredGigE,,GigabitEthernet,EthernetWe have check to not add other port ids.Yeah i noticed that it allows only the type : Ether,BVI,FiftyGigE,FortyGigE,FourHundredGigE,HundredGigE,Loopback,TenGigE,TwentyFiveGigE,TwoHundredGigE,,GigabitEthernet,Ethernet but not Tunnel-ip. But it was declared as string. Logically it should allow. I guess you guys are validating inside package code.Could you please let us know whether the support for Tunnel-ip is going to be added or not? We have a dependency on this type: Tunnel-Ip. In case we want to customise, Is there any way to do that without impacting the visualization on the topology? Any leads on customisation would be a great help to us. Hi Srinivasa,We do not have any requirement to add tunnel-ip in CNC 6.0. If you believe it needs to added, please create an AHA ticket for CFP to be prioritized by PLM.I am not sure if the customization would be straightforward. First step is to remove the pattern check in the yang, re-compile the package and verify if the tunnel ip is being accepted and configured on the device.ThanksSahithi