> Quoting Robert J. Adams (radams@siscom.net):
>
> > I'm currently using a routing policy to force anything from
209.251.30.20
> > to next-hop "Sprint", and anything from 209.251.30.21 to next-hop
"UUnet".
> > Once we got up to about 60Meg/sec on a 300Mhz VXR I'm at around 80% CPU.
> > Is there a better way of doing this? See below for our current config.
>
> Your PBR is currently fast-switched. You could try switching to
> Netflow based PBR:
>
> ip cef [distributed]
> ip flow-cache feature-accelerate
> interface XXXXXX
> ip route-cache flow
> ip policy route-map YYYYYY
Hello,
I gave this a shot using c7200-is-mz.121-5.T9 (I need to run tagged vlans on
the same int as cef) and my policy routing stopped working. The access lists
were still getting hit, it just wasn't following the "next hop" I told it
it. Argh.. I have a Juniper eval coming next week.. getting tired of this
Cisco IOS hell.
Thanks,
Jason
SISCOM, Inc / Newshosting.com
This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:13:29 EDT