Not able to see the real stats from devices after deploying y1731 service: With NSO 5.5.2.7 + M6 installed, deployed the Y1731 service (please find the attachment for the payloads), after while all the stats still remaining as "0".The similar payloads were deployed on NSO 5.5.2.3 + M4 env, it was able to get the real stats.
  Hello Jason, do you by any chance have the original payloads from your M4 setup? If so, please upload them here!Jason, please also share the output from the following commands given on the device.```RP/0/RSP0/CPU0:PE1#show ethernet sla configuration-errors``````RP/0/RSP0/CPU0:PE1#show ethernet sla statistics``````RP/0/RSP0/CPU0:PE1#show ethernet cfm peer meps```Here are the payloads for NSO5.5.2.3 with M4, after service deploy, we did manual load merge of y1731_device_config_override.xml  Hi Jason, can we also get access to your setup?Hi Reginald, I did check "show ethernet cfm peer meps" on the same devices last night it was in Ok (>) state, even that, I did not see the real stats, means the output of "show ethernet sla statistics" looks were the same (no real stats). But I saw "show ethernet cfm peer meps" turn to error state today.  The NSO info: 172.20.200.112 admin/Cwork123! service name "new-l2nm-p2p-sr-1"Hello Jason, we checked your NSO CLI instance and we saw that your "new-l2nm-p2p-sr-1" plan is in failed state with out-of-sync device. Please correct this first and check Y1731 probe statistics.  Hi Isaac, I did the device sync, and checked the Y1731 probes, it looks the same. Would you please check? Thank.Hello Jason,After trying few things, we found that your frame size of 2000 exceeded your Interface MTU of 1500. Once we reduced frame size to 1000 connection issues were resolved. We also noticed that changing delay version to 1 fixed the 100% dropped packets. This seems to be specific for NCS5501 device.Apart from this, we confirmed that NSO configuration is correctly pushed to device in accordance to config governance defined schema. As such, NSOs role was successfully completed. Device level logic and configuration should be analyzed by subject experts (such as why delay version 0 is causing issues on NCS5501, is there an expectation to use delay version 0?)Also please note, your previous payload for M4 used frame-size of 1000 which likely indicates why you did not face connectivity issues.Thanks,Isaac KimHi Isaac, I made the changes as you suggested below, and re-deploy the service, but I still could not the probes coming...Hi Jason,I took a look at your setup. As Isaac mentioned were unable to get delay version 0 to work; however, we were able to get delay statistic working with version 1. If you need delay version 0 to work, then please provide the expected device configuration that you need.Thanks,Regi