isn't most of that a by-product of using trident/trident+? i know that trident ii fixes some of that -- but i think that comes down to the (some say unwise) decision of using ots components, no?
q. -- quinn snyder [email protected] On 12-Sep-13, at 20:15 , Pete Templin <[email protected]> wrote: > On 9/12/13 11:30 AM, Gert Doering wrote: > >> To be fair, one would need to compare software features - so what does >> the N3K do? L2 only? L3, with how many routes? IPv6, MPLS? > > Gert, you don't want to explore the N3K, you'll have 6500 heartburn all over > again. URPF halves the route table size, max 16k routes (but v6 routes count > double), a separate memory space for host routes, very limited ACL TCAM and > it has to be carved up for v4/v6 at boot time. NXOS for this platform seems > very buggy, so one might end up doing endless code upgrades to get past > showstopper bugs, only to encounter more bugs in the next build. > > pt > > _______________________________________________ > 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/
