what you're most likely seeing is that without WCCP, you have traffic being forwarded locally on each linecard.
in cisco parlance, that is called "distributed switching" -- typically "distributed cef".
on IOS 12.1E, when you enable WCCP, WCCP isn't in the "distributed" path, but only operates centrally, so all linecards have to forward all the traffic via the central processor (RSP).
that will mean that WCCP will work, but a bad side-effect is that the RSP is now really really busy. bad.
you should look at running IOS 12.0S (the "S Train") [http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/index.html]
12.0S is the train that is meant to be used by service-providers.
in 12.0S, WCCP can operate on each linecard on a 75xx -- so you'll end up with WCCP "distributed" across each linecard.
CPU on the RSP will be a lot happier.
details of the enhancements to WCCP that were added to 12.0S are detailed at http://www.cisco.com/en/US/products/sw/iosswrel/ps1829/prod_release_note09186a0080088244.html#xtocid280
cheers,
lincoln.
At 01:20 PM 30/10/2002 -0800, Rick Ernst wrote:
Has anybody seen issues with high CPU utilization on WCCP?
My test environment is a Cisco 7513 running 12.1(12C)-E1 handling about 80Mbs of
aggregate traffic. The cache server is an Intel Netstructure 1500.
With and without global WCCP enabled, CPU is about 5%. If I enable wccp
redirection on outbound interfaces (inbound isn't an option with this version of
IOS), CPU goes to almost 90% and stays there.
I'm using an ACL to allow only a single machine for testing.
Am I missing something obvious?
Thanks,
Rick
____________ The ISP-CACHING Discussion List ___________
To Join: mailto:join-isp-caching@;isp-caching.com
To Remove: mailto:remove-isp-caching@;isp-caching.com
Archives: http://isp-lists.isp-planet.com/isp-caching/archives/
____________ The ISP-CACHING Discussion List ___________ To Join: mailto:join-isp-caching@;isp-caching.com To Remove: mailto:remove-isp-caching@;isp-caching.com Archives: http://isp-lists.isp-planet.com/isp-caching/archives/
