Does CoPP actuaally work now? We've been bitten by the RPQ issue many times. ARP and routing protocols should now be split across two different CPU queues as of 15.5(3)S2.
In the mean time, you can use this to allocate more resources to that queue to prevent the routing protocols from going away during an ARP storm: test platform qos policer modify cpu 1 5000000 100000 On Feb 27, 2014, at 8:35 AM, Nick Hilliard <[email protected]> wrote: > Does anyone have suggestions on how to handle isis and arp separately on an > me3600 copp policy? There's no clear way of matching ISIS packets, and > according to the documentation, "MAC-based matching is done in software > only", which would seem to defeat the point of having hardware policers. > > My reading of this is that unless you want to handle CoPP in software, the > only way to match either ISIS or ARP is to create a bucket for all IPv4 and > IPv4 and catch ISIS/ARP in class-default. But that bundles them both in > under the same policer. Does anyone know if it's possible to separate them? > > Nick > _______________________________________________ > 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/
