Immediate recommendation to move to 5.2.3a or 5.2.4 - lots of catastrophic fun to be had on 5.2.1 / 5.2.2 ... Contact your account team for more details but I'm pretty sure one of the cases was shared on list a few months back.
Ryan On Mon, Mar 26, 2012 at 11:54 AM, Jeffrey G. Fitzwater <[email protected]>wrote: > > I am trying to understand if ALL ARP (requests ) packets that a nexus 7K > sees, need to be punted to the CPU and therefor managed by COPP policies / > rate-limits? > > Over the weekend we had a data loop that cooked the CPU and we are trying > to understand what packets that were control plane processed, caused the > CPU load. > > We currently have a Nexus 7k running 5.2.1, that only has L2 interfaces, > other than the management VRF port. I would think that the CPU would > never have to process any ARP requests for non-management traffic since it > does not have any L3 interfaces. > > > My understanding is that other sites have had similar issues and changing > the COPP profile stopped the CPU form being saturated during this kind of > event. > > The COPP profile can be ( lenient, moderate, strict ). > > > Thanks in advance for any info on this issue. > > > > Jeff Fitzwater > OIT Netwrok Systems > Princeton University > > > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
