Hi, On Tue, Jan 22, 2013 at 07:29:27AM -0600, Andy Ellsworth wrote: > On Tue, Jan 22, 2013 at 6:56 AM, Alex K. <[email protected]> wrote: > > > Cat6500 is a distributed environment. Not only PFC (or any other one part > > for this matter) is responsible for capabilities. > > > You might want to read up on the role of the PFC. If NBAR were to be > implemented in hardware, it would indeed need to be on the PFC/DFC. > > https://supportforums.cisco.com/docs/DOC-21377#Role_of_PFC_Layer_3_Engine > > Since it isn't (as Oli's doc explicitly says), it's done in software, if > it's done at all.
You miss the mention of "SIP-200". That's a whole different beast again,
the SIPs have local CPUs that can do things like VPLS, and possibly NBAR
(note that I have no idea whether the SIP *can* do NBAR, but "interfaces on
SIP boards" generally have different restrictions than "interfaces on
c6k line cards").
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany [email protected]
fax: +49-89-35655025 [email protected]
pgpxxohp97Wv3.pgp
Description: PGP signature
_______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
