[c-nsp] me3600 copp

[Nick Hilliard]

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