config difference on NSO Native Config and ASR920: provision an L3VPN with no policy. one node it ASR9K and the other node is ASR920. No SR policy associated in the service.Compare the "Native config" and config on ASR920, observe the following. Can you confirm if this is expected?service payload attached.ASR920 IOS: 17.6.1ASR9K IOS: 6.7.2Config 1:On NSO Native Config:=================interface Loopback8 ip redirects vrf forwarding L3VPN_NM-IGP-IPV4-80 ip address 80.80.11.1 255.255.255.252 no shutdownOn ASR920:============interface Loopback8 vrf forwarding L3VPN_NM-IGP-IPV4-80 ip address 80.80.11.1 255.255.255.252 no shutdownDelta:=====ip redirects <--- do not see this line on ASR920Config 2: Under router bgpOn NSO Native Config:=================address-family vpnv4 unicast neighbor 80.80.11.2 activate    exit-address-familyON ASR920:=========address-family vpnv4 unicast neighbor 80.80.11.2 activate neighbor 80.80.11.2 send-community extended exit-address-familyDelta:====See extra line on ASR920, "neighbor 80.80.11.2 send-community extended"
 HI Crystal,We are working on getting the device access.--RaghaviThe original payload is not the correct one. Attached the right one here. Sorry for the confusion. Hi Crystal,This is the expected behavior. The NED translates activate into the two commands you have mentioned. Even on the device, if you set only activate, it automatically also configures the send-community extended. So we see only activate in NSO native config which internally configure send-community on the device.I would suggest if you see similar issues in future try to set directly on the device and see the behavior.--Raghavi.