[c-nsp] Operational impact of switching from ingress to egress replication mode
Benjamin Lovell
belovell at cisco.com
Tue Sep 21 16:04:09 EDT 2010
Excellent point and suggestion. This should prevent punts from smashing your control plane and causing a cascading effect like the one I described.
-Ben
On Sep 21, 2010, at 3:47 PM, Phil Mayers wrote:
> On 09/21/2010 08:27 PM, Benjamin Lovell wrote:
>> The primary thing to worry about here is the mcast packet rate not
>> number of mroutes. Replication change will cause all mcast packets to
>> be punted to CPU for a short period(few 100 msec or so).
>
> Remember you can rate-limit this with the MLS limiters. Whilst they defaults are (very) high, lowering it for the duration of this change could ease the problems.
> _______________________________________________
> cisco-nsp mailing list cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
More information about the cisco-nsp
mailing list