Symptom

messages and "show ip sla summary" commands displays it as "unknown". Example : ATH_C001#sh ip sla summary IPSLAs Latest Operation Summary Codes: * active, ^ inactive, ~ pending ID Type Destination Stats Return Last (ms) Code Run ----------------------------------------------------------------------- *10 mcast 222.255.22.1 - - - *1537222122 mcast-dest 22.64.22.32 - Unknown - We are also seeing the below error messages: ATH_C001# *Jun 26 13:24:52.528 UTC: %XOS-7-XOS_DM_DISPATCH: xos_dm_dispatch API cannot be called that does not own the XDM, xdm pid: 603, current pid: 602 -Process= "IP SLAs Control Process", ipl= 0, pid= 602 -Traceback= 1#9acb3916931d56895520b7fc69b1795f :55F819D69000+9FAA479 :55F819D69000+D084631 *Jun 26 13:24:52.528 UTC: %XOS-7-XOS_DM_WAIT: xos_dm_wait API cannot be called by a process that does not own the XDM, xdm pid: 603, current pid: 602 -Process= "IP SLAs Control Process", ipl= 0, pid= 602

Conditions

Workaround

Workaround for this is to enable IPSLA Responder after configuring the Sender and not to save the Responder configuration to start-up configuration. So that during the reload, Customer will not end up hitting this bug..

Further Problem Description