01-15-2010 02:28 AM
Good day,
I would like to conform if the following would be correct to implement for WCCP redirection list on 6500. We have over 800 branches and we also need to manage the intra-server traffic in the Data Center which we do not want to be re-directed.
ip access-list extended WCCPLIST-61
permit tcp 10.112.0.0 0.0.31.255 any
ip access-list extended WCCPLIST-62
permit tcp any 10.112.0.0 0.0.31.255
So, as an example, would these masks work for us, as the number of entries otherwise would be exhaustive.
Just want to confirm that the mask in the ACL doesn't have to match exactly.
Thanks in advance.
Solved! Go to Solution.
01-15-2010 07:16 AM
Hi Paul,
The redirect configuration you are planning to use looks fine. This will cause any TCP traffic to/from 10.112.0.0/19 to be redirected.
Regards,
Zach
01-15-2010 07:16 AM
Hi Paul,
The redirect configuration you are planning to use looks fine. This will cause any TCP traffic to/from 10.112.0.0/19 to be redirected.
Regards,
Zach
01-18-2010 10:26 AM
Hi Zach,
Thanks for the response and confirmation.
I was wanting to make sure that it is not required to have the masks match the source masks, resulting in the exhaustive list (operational nightmare).
A quick question on the ACL for WCCP redirect-list. Should we not see hits on specific entry's (e.g.permit tcp 10.113.9.0 0.0.0.31 any for the 61 redirect list, and the same for the permit tcp any 10.113.9.0 0.0.0.31 for the 62 redirect list).
If we don't, no traffic? We see flows on the branch WAE, although very few (not many users), but no hits on the ACL on the DC 6500. Is this due them being handled in hardware maybe, TCAM's?
Any input would be apprecited.
Thanks again.
Paul.
01-24-2010 03:22 AM
OK, just had to dig around in the old filing cabinet of the mind a bit. Got the commands required and can confirm the ACL hits.
Thanks anyway.
Paul.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: