T-SDN L3NM CLI problem with route-policies spaces: In L3VPN CFP (L3NM), when programming a route-policy there is a blank space discrepancy between the CFP template and the outcome in XR when using CLI NED.This is well known when dealing with string leafs.The outcome is that the target devices (Node-4 in this example) are in-sync but compare-config is not empty. This can be fixed by adapting the template with blank spaces to match XR string encoding.Regards,Roqueadmin@ncs> request devices device Node-4 compare-configdiffdevices { device Node-4 { config {route-policy PASS_ALL {- valuepass;+ value" pass"; } } }}
Hi Roque, Can I please get a sample payload for this? Would like to reproduce this on our system. Thank you!Hello Roque, please let us know if we can get a payload for investigating this issue. Thank you!Hi,This ticket has been pending for some time.Please provide a reply by end of week. Otherwise this ticket will be closed.Thanks,Isaac KimHere you have but you can use the dcloud demos for CNC and follow their instructions that it will happen always.admin@ncs> show configuration l3vpn-route-policy VPN-101-ROUTE-POLICYcolor 4001 {  ipv4 {    prefix [ 30.2.1.0/24 30.2.2.0/24 30.2.3.0/24 ];  }}color 4003 {  ipv4 {    prefix [ 10.9.0.0/16 10.9.54.0/24 10.9.55.0/24 10.9.56.0/24 30.1.1.0/24 30.1.2.0/24 30.1.3.0/24 ];  }}admin@ncs>admin@ncs> show configuration l3vpn-ntw vpn-profiles valid-provider-identifiers routing-profile-identifier VPN-101-ROUTE-POLICYNo entries found.admin@ncs>admin@ncs> show configuration l3vpn-ntw vpn-services vpn-service vpn-101ie-profiles {  ie-profile vpn-101-profile {    rd 0:65000:101;    vpn-targets {      vpn-target 1 {        route-targets 0:65000:101;        route-target-type both;      }    }  }}vpn-nodes {  vpn-node Node-4 {    custom-template ct-tpa;    local-autonomous-system 65000;    vpn-network-accesses {      vpn-network-access Node-4-vpn1 {        port-id GigabitEthernet0/0/0/1;        connection {          encapsulation-type tagged-int;          tagged-interface {            type dot1q;            dot1q-vlan-tagged {              cvlan-id 101;            }          }        }        ip-connection {          ipv4 {            address-allocation-type static-address;            static-addresses {              primary-address Node-4-vpn1-ipv4-address;              address Node-4-vpn1-ipv4-address {                provider-address 30.1.2.1;                prefix-length  24;              }            }          }        }        routing-protocols {          routing-protocol Node-4-routing {            type bgp;            bgp {              peer-autonomous-system 65003;              address-family     [ ipv4 ];              redistribute-connected-ipv4-af;              neighbor        [ 30.1.2.2 ];            }          }        }      }    }    node-ie-profile     vpn-101-profile;  }  vpn-node Node-5 {    custom-template ct-tpa;    local-autonomous-system 65000;    vpn-network-accesses {      vpn-network-access Node-5-vpn1 {        port-id GigabitEthernet0/0/0/1;        connection {          encapsulation-type tagged-int;          tagged-interface {            type dot1q;            dot1q-vlan-tagged {              cvlan-id 101;            }          }        }        ip-connection {          ipv4 {            address-allocation-type static-address;            static-addresses {              primary-address Node-5-vpn1-ipv4-address;              address Node-5-vpn1-ipv4-address {                provider-address 30.1.1.1;                prefix-length  24;              }            }          }        }        routing-protocols {          routing-protocol Node-5-vpn1-routing {            type bgp;            bgp {              peer-autonomous-system 65003;              address-family     [ ipv4 ];              redistribute-connected-ipv4-af;              neighbor        [ 30.1.1.2 ];            }          }        }      }    }    node-ie-profile     vpn-101-profile;  }}service-assurance {  monitoring-state enable;  profile-name   "Gold_L3VPN_ConfigProfile system";  rule-name    "Rule-L3VPN-NM system";}admin@ncs>admin@ncs> request devices device Node-5 compare-configdiff devices {   device Node-5 {     config {       route-policy PASS_ALL {-        value pass;+        value " passrn";       }     }   } }admin@ncs> request devices device Node-4 compare-configdiff devices {   device Node-4 {     config {       route-policy PASS_ALL {-        value pass;+        value " passrn";       }     }   } }admin@ncs>Thank you for the information Roque. An internal ticket has been created for this issue, Closing this ticket as all further tracking will be under CDETSIssue will be fixed as part of CDETS