PBR(Policy-Based Routing) with IP SLA ICMP-jitter

[DaeHeon Kang]

Hi,

I'm testing currently PBR(Policy-Based Routing) with IP SLA ICMP-jitter(Packet Loss base) on simulation setup before applying it to the production network.

It seems the SLA is measured properly, but the PBR route is not down with threthold value of Packet loss.

Below is my configuration.

This is my first time using ICMP-jitter option, thus I am not sure whether I've configured properly or not.

I hope experties can help me for this.

ip sla 1
icmp-jitter 10.1.100.6 source-ip 10.1.100.2 num-packets 100 interval 40
ip sla schedule 1 life forever start-time now
ip sla reaction-configuration 1 react packetLoss threshold-value 4 2 threshold-type immediate action-type triggerOnly

track 1 ip sla 1 reachability

route-map PBR-RM permit 1
set ip next-hop verify-availability 10.1.100.6 1 track 1

interface Ethernet0/1
ip address 10.1.1.1 255.255.255.252
ip policy route-map PBR-RM
ip ospf network point-to-point

R1#show ip sla statistics
IPSLAs Latest Operation Statistics

IPSLA operation id: 1
Type of operation: icmp-jitter
Latest RTT: 1 milliseconds
Latest operation start time: *03:21:24.659 EET Mon Feb 22 2021
Latest operation return code: OK
RTT Values:
Number Of RTT: 92 RTT Min/Avg/Max: 1/1/4
Latency one-way time:
Number of Latency one-way Samples: 0
Source to Destination Latency one way Min/Avg/Max: 0/0/0
Destination to Source Latency one way Min/Avg/Max: 0/0/0
Jitter Time:
Number of SD Jitter Samples: 84
Number of DS Jitter Samples: 84
Source to Destination Jitter Min/Avg/Max: 0/3/8
Destination to Source Jitter Min/Avg/Max: 0/2/8
Packet Late Arrival: 0
Out Of Sequence: 0
Source to Destination: 0 Destination to Source 0
In both Directions: 0
Packet Skipped: 0 Packet Unprocessed: 0
Packet Loss: 8
Loss Period Length Min/Max: 1/1

[paul driver]

Hello
Your pbr ip next hop is the ipsla source?
Also the traffic you seem to want to policy route a /30 subnet is this correct?

[Georg Pauwen]

Hello,

post a diagram of your topology.

[MHM Cisco World]

I don't know a lot about this type of operation BUT 
IP sla monitor with trigger-only <- this IP sla check the link statistic and then if the pass threshold it will trigger another IP sla.

this type of IP sla not use for reachability it use for VoIP QoS and RSVP.

so I think it misconfig.