no plan notification on ELAN service: we noticed a case when operation assurance on services of type ELAN - we recieve from NSO notifications only on the service, but not on the planwhen doing the same operation on EVPN - we do see both service and plan notifications arrive - can you have a look on it? here is the single notification we get on the ELAN:[{"handle":"1","message":{"db":"running","changes":[{"keypath":"/l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service{L2VPN_NM-ELAN-170}/l2vpn-ntw-augmentations:service-assurance/monitoring-state","op":"value_set","value":"enable"}],"user":"admin","ip":"https://172.20.200.130"}}]
Hello, Notifications are usually determined by the bootstrap files that are onboarded to the setup.Can you please share the setup on which this issue was seen so we can investigate this?Regards,Janaki DuggiralaHere is NSO service info: 172.20.100.133 admin/Cwork123!172.20.200.133Uploaded the service payload Hello Jason,We see that plan notifications are not being generated for L2NM EVPN MP -> service-assurance, but we do see that the AA notifications are still being generated correctly. As CNC UI is already receiving AA notifications from NSO for service-assurance updates, it would be possible to use AA notifications rather than plan notifications.Just a note, we cant reproduce this behavior in TSDN 5.0.Thanks,Isaac KimHi Isaac,Thanks for the RCA. From what I understand, CAT uses both notifications for different purposes. Hi Alan ; Idan, would you please chime in on this.Thanks,-jasonhi Isaac, what do you mean by AA notifications? not sure nso-c listen to this kind of notifications - can you send example? which component in CNC listen to this notifications? Alan - are you aware of it? Hello, we have a separate notification stream for service-assurance config changes as these changes are not pushed to device (as it is a service config only) and may not always result in a plan change. The service-assurance notifications include all the required information that would be provided in an equivalent service-state-change notification, with the exception of no plan component information (which again is not relevant to service-assurance config as it is not pushed to any particular device/component).service-state-changes notification<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% run show notification stream service-state-changesnotification { eventTime 2022-11-03T18:27:16.981329+00:00 plan-state-change {  service /l2vpn-ntw/vpn-services/vpn-service[vpn-id=]  component PIOSXR-1_a1  state ready  operation modified  status reached }}</pre></div></div>service-aa-changes notification<div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"><pre class="code-java">admin@ncs% run show notification stream service-aa-changesnotification { eventTime 2022-11-03T18:27:57.889234+00:00 service-assurance-config-change {  service /l2vpn-ntw:l2vpn-ntw/vpn-services/vpn-service[vpn-id=EVPN-MP-ELAN]  operation modified }}</pre></div></div>Here we can see that service-aa-changes notification has eventTime, full service path (including service name), and operation. This should have the relevant information to make necessary resulting operations/updates.Thanks,Isaac KimHi Isaac, I just checked on CFP5.0-M3, change of service-assurance on ELAN service does not send the plan change notification. The other VPN service does not have such problem. From what I understand, "plan change" notification is expected by CAT on service-assurance change. This feature has been working since CFP 3.0.Srini, Alan ; Idan, please confirm. Again, this is a severe issue which is blocking SH 5.0 feature development since it is not working on CFP 5.0-M3 either.Thanks,-jasonClosing this as the patch was provided for 5.0 M3 to generate plan notification on ELAN service. The issue is already fixed starting 5.0 M4.