I'm a little confused. Are you saying "it's obviously supported because I can configure it, however I see high CPU when I do"?
The CLI was removed in 15.0.1S, when support for the SIP-200 ended. Generally on the 6k "not supported" means "can't be done in hardware", so I would say that punting the traffic and causing high CPU is expected behavior, unless you have a SIP-200. On Mon, Jan 21, 2013 at 5:12 PM, Alex K. <[email protected]> wrote: > Thank you Pete, > > Unfortunately, this link is inconclusive either. > > Earlier in this document it says that NBAR is indeed supported on SIP-200 > (here: > http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76ovwsip.html), > afterwards it claims it isn’t (here: > http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfgsip.html#wp1543942 > , > the same document, simply the next chapter) after these two, comes the > chapter you linked to, but unfortunately it claims that no NBAR should be > available on MSFC/PFC 3 (by the way of exclusion) but in my case it is > supported (i.e. on SVI). > > It just sends the CPU thru the roof. > > Thank you for your efforts, but that not seems to be document I'm looking > for, either. Will be glad to hear your future thoughts on this one. > Best Regards, > Alex. > > On Mon, Jan 21, 2013 at 9:37 PM, Pete Lumbis <[email protected]> wrote: > >> NBAR is only supported on SIP-200 (not SIP-400/ES/ES+) and MSFC2 (Sup32). >> >> NBAR without a SIP-200 on sup720 will be done entirely in software. >> >> >> http://www.cisco.com/en/US/docs/interfaces_modules/shared_port_adapters/configuration/7600series/76cfgsip.html#wp1526795 >> >> >> On Mon, Jan 21, 2013 at 2:16 PM, Alex K. <[email protected]> wrote: >> >>> Hi All ... >>> >>> > _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
