Dear NSO experts,
Could you please help me understand why data-kicker doesn't kick for some of the events.
Requirement is , to check if out of band changes happened while service provisioning. This is LSA setup. I am using netsim devices at this stage.
In order to achieve this, i have setup some kickers , to watch the changes on devices :
kickers data-kicker nx-policymap
monitor /devices/device/config/nx:policy-map/type/qos
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker nx-vlan
monitor /devices/device/config/nx:vlan/vlan-list
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-bgp-vrf
monitor /devices/device/config/cisco-ios-xr:router/bgp/bgp-no-instance/vrf
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-bridge-domain-vlan
monitor /devices/device/config/cisco-ios-xr:l2vpn/bridge/group/bridge-domain
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-evpn-evi
monitor /devices/device/config/cisco-ios-xr:evpn/evi
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-interface-bundle-ether
monitor /devices/device/config/cisco-ios-xr:interface/Bundle-Ether
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-interface-bundle-ether-subinf-vlan
monitor /devices/device/config/cisco-ios-xr:interface/Bundle-Ether-subinterface/Bundle-Ether
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-interface-bvi
monitor /devices/device/config/cisco-ios-xr:interface/BVI
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-ipv4-access-list
monitor /devices/device/config/cisco-ios-xr:ipv4/access-list/named-acl
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-route-policy
monitor /devices/device/config/cisco-ios-xr:route-policy
kick-node /kicker-actions
action-name kicker-action
!
kickers data-kicker xr-vrf
monitor /devices/device/config/cisco-ios-xr:vrf
kick-node /kicker-actions
action-name kicker-action
!
Devices are in pairs, so any change is provisioned on both devices, and hence kicker kicks for both of the devices.
When a service-instance is provisioned, config is applied to devices, and kickers kick for all the configs which has now been provisioned , and all data is captured and propagated from RFS to CFS, so that CFS can check at service invocation. This works fine.
Problem is, when same service-instance is deleted, configs are deleted from devices. And hence kickers would kick for deletion of same config. But some kickers do not kick for some of the changes. For example,
at the time of service-instance is provisioned, /devices/device/config/cisco-ios-xr:evpn/evi is written to both devices in pair. And then related kicker kicks and this information is transferred from RFS to CFS and written to a dedicated auxiliary yang for both of the devices.
at the time of service-instance deleted, kicker doesn't kick for one of the devices, so we miss that it is deleted.
I have tried some combination of priority and serializer , but it didnot help. For some of the kickers above, kicker kicks for both devices in a pair, for some kickers it kicks only for one device in a pair. for some kickers it kicks for none of the devices. Interestingly, kickers kick for all events at time of service-instance is provisioned , but some kickers donot kick at service-instance deletion.
Is this expected behavior at event storm ( although cpu/mem are quite enough and this wouldn't be considered a storm in my opinion) , or is there a way to have these kick every time.
Thanks in advance.
