get-modifications reverse on CFS does not include device config delta: Procedure and Issue:have NSO LSA setupdeployed the L2NM service on CFS.the 'get-modifications reverse' returned only '-flat-L2vpn internal' payload, without device config delta.Note:L2NM service payload is attached.device CL5-PE-A is configured on rfs-1, device CL5-PE-C is configured on rfs-2.the return of 'get-modifications reverse':admin@ncs% request l2vpn-ntw vpn-services vpn-service L2VPN_NM-P2P-PE-A-PE-C get-modifications reverse cli {  local-node {    data -flat-L2vpn L2NM-L2VPN_NM-P2P-PE-A-PE-C-internal {service-type p2p;flat-L2vpn-p2p {pw-id 301;local-site {pe CL5-PE-A;if-type GigabitEthernet;if-id 0/0/0/1;if-encap dot1q;vlan-id 301;sub-if-id 301;mtu 65;xconnect-group-name L2VPN_NM-P2P-PE-A-PE-C;p2p-name L2VPN_NM-P2P-PE-A-PE-C;sr-te {preferred-path {       -          policy SR-Policy-1;       -        }}control-word no;pw-class L2VPN_NM-P2P-PE-A-PE-C;xconnect-local-ip 200.200.200.5;xconnect-remote-ip 200.200.200.7;mpls-local-label 114;mpls-remote-label 115;}remote-site {pe CL5-PE-C;if-type GigabitEthernet;if-id 0/0/0/1;if-encap dot1q;vlan-id 301;sub-if-id 301;mtu 65;xconnect-group-name L2VPN_NM-P2P-PE-A-PE-C;p2p-name L2VPN_NM-P2P-PE-A-PE-C;sr-te {preferred-path {       -          policy SR-Policy-2;       -        }}control-word no;pw-class L2VPN_NM-P2P-PE-A-PE-C;}}       -}</ul>  }}admin@ncs% 
  Had verified, the config delta was pushed correctly on on the both devices.Hi JasonWe filed an RT for getting support to get-modifications from top level service.Workaround:Currently as work-around to get the device config, we need to do get-modifications reverse from second level service.For Example:When you create l2NM service, get-modifications reverse on flat-l2 service will work as intended.Tested this on your system and was able to verify:```admin@ncs% request flat-L2vpn L2NM-L2VPN_NM-P2P-PE-A-PE-C-internal get-modifications reversecli {  local-node {    data  }  lsa-service {    service-id /devices/device/config/cisco-flat-L2vpn-fp-internal-local-site:flat-L2vpn-internal-local-site-service    data devices {          device CL5-PE-A {            config {              interface {<ul class="alternate" type="square">GigabitEthernet 0/0/0/1 {description "to CL5-P-BOTTOMLEFT";ipv4 {address {       -              ip 20.20.15.5;       -              mask 255.255.255.252;       -            }}}                GigabitEthernet-subinterface {GigabitEthernet 0/0/0/1.301 {mode l2transport;description "T-SDN Interface";mtu 65;encapsulation {dot1q {```Please let me know if this workaround works until we make progress with RT.Please also let me know if this functionality was working/not-working for LSA on M1 Release too?I was able to capture the "device config" from the output of "get-modifications reverse" on one of CFP QA's testbed during M1 timeframe (earlier this year), so I believe it was working in M1.Hi Sahithi,Thanks for providing the workaround. Although it could retrieve the device config data in this way, but it is not practically applicable to SH implementation. I'd rather be waiting for the issue getting resolved. Here is the reason:<ul class="alternate" type="square">with this workaround, SH needs to query NSO twice to retrieve the data, because SH should not assume the flat-vpn-internal service yang path and name.the output of workaround is in different data structure (hierarchy).Both of above have to be reworked once the issue is resolved.Can you please re-check if it was LSA setup you captured the "device config" on M1?PLMK if you have the working get-modifications reverse config for LSA on M1, it would be helpful too.Just trying understand if this is a regression issue.ThanksSahithiHi Sahithi,Sorry, I do not have M1 setup. The one I accessed was CFP QA's.Hi Jason,Confirmed with CFP QA that this issue exists in LSA setup on M1 too. I understand this is not a regression issue and a new issue reported. As informed, we filed a RT on NSO platform and working with them on this.ThanksSahithiFixed with M3 release