Thank you all for your for your suggestions.
But unfortunately it looks like a locally connected subnet cannot be listing in an ACL:
My interupts jump to 4% with only one connection from 172.19.142.124 to 172.23.142.11
Rolf, I think the "local address" is a locally connected subnet, but thanks.
CPU utilization for five seconds: 10%/4%; one minute: 9%; five minutes: 9%
Then it jumps to 6% for a file transfer:
CPU utilization for five seconds: 13%/6%; one minute: 10%; five minutes: 9%
using:
route-map PBR permit 10
match ip address 198
!
route-map PBR permit 20
match ip address 199
set ip next-hop 192.168.250.2
ACL 198 matches the directly connected subnets.
permit ip 172.23.142.0 0.0.0.255 172.19.142.0 0.0.0.255 (1016 matches)
ACL 199
is everything above.
It was in the high 20% range yesterday and TAC believes that is what the issue is.
I did run thru a TAC ticket with the routing team last night and they had this same solution, but the issue remained.
They say it's the interupts: CPU utilization for five seconds: 10%/4%; that are causing the performance issue. Turns it into a software switch??
They did not have any other solutions or recommendations to try.
I was setting this up as a temporary solution while we changed our internet facing device (2811 router to a Fortinet device), and was thinking of leaving it as a failover/DR solution in case something happened with the Fortinet. But it looks like this may not work.
I really appreciate the suggestions and am hopful there may be another suggestion here.
Thanks again for everyone's time.
