Our IP SLA udp-jitter for a number of devices beyond an ASA suddenly stopped working when the target OS was updated from 12.x to 15.x. We have since discovered that the target is responding back on a different IP than it received the connection on and our ASA in the way is dropping "due to reverse path check". For numerous reasons i won't go into here I don't want to add the additional IP's in the ASA. The policy on the ASA hasn't changed in months, and we also see the same issue when trying to establish new IP SLA's across the ASA to responders with multiple IP's and IOS 12. I also see udp traffic from the responder port 1967 to the initiator using the IP the initiator connected on.
Is there a way to ensure the IP SLA responder responds using the same IP it was connected to on?
here is the code we are using for IP SLA initiator
ip sla 10
udp-jitter x.x.x.1 16384 codec g711alaw advantage factor 10
ip sla schedule 10 life forever start-time now
and on the responder
ip sla responder
-If I helped you somehow, please, rate it as useful.-
