If somebody comes up with a 'best-practices' COP example for the 6500 chassis, I'm sure it would be very useful for several people.
-Peter -----Original Message----- From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Saku Ytti Sent: Tuesday, March 23, 2010 6:58 AM To: cisco-nsp@puck.nether.net Subject: Re: [c-nsp] Sup720 CoPP, limits on CPU performance On (2010-03-23 09:20 -0400), Chris Griffin wrote: > Because on the PFC3B, mls HWRL glean traffic is subject to the > outbound ACL of the input interface. If it didn't have this "feature" > we would use the glean rate limiter. Its far easier for us to track > interface IPs than it is to re-write all of our outbound ACLs to > account for inbound glean traffic. That is nasty, 'luckily' for me egress ACL are no-no anyhow, as they'll create aggregate labels and cause egress IP lookup, which would break hub+spoke VRF config, which is fairly typical in my network. -- ++ytti _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/