PfR:Troubleshooting:BestExitSelectionLinkNotExpected

From DocWiki

Jump to: navigation, search

Pfr-troubleshooting.png




Navigation


Traffic did not pick the link as expected
Is the correct policy applied to the traffic class?

Check with

show oer master prefix <prefix/prefix len> policy 
Yes
Is there an Out of Policy event?
show logging | inc <prefix> 
to look for OOP event.
Yes > Go to <resolver>
No
Is there a periodic timer configured?
show run | b oer master
No > Configure periodic timer:
oer master
 periodic <x>
Yes
<resolver> Are the appropriate resolver priorities configured?
show oer master policy 

and look for resolver priority for the traffic-class

No > Configure the appropriate resolver as higher priority.
Yes
Is the expected link “better”?
show oer master traffic

to look at the quality of the expected link.

Yes
Look for the reason why PfR selected the exit in syslog or
show oer master tr detail | b <prefix>

For passive monitoring, verify the netflow cache on BR.
(Note: Delay and loss are calculated only for TCP traffic)

Aug  4 19:06:02.629 PDT: %OER_MC-5-NOTICE: Route changed Appl Prefix 10.175.120.184/30 N    
6 [80, 80] [1, 65535], BR 10.185.111.17, i/f Et4/1, Reason Delay, OOP Reason Delay

Rating: 4.5/5 (2 votes cast)

Personal tools