Hi, On Fri, Sep 18, 2020 at 10:54:53AM +0200, chiel wrote: > 3. New route entries will be software routed, but entries that are > already in TCAM will be hardware routed. You won't notice much impact in > the beginning.
"Route entries that have churn will end up in software" *and* "the
software path is heavily rate-limited".
So "for some targets you'll see massive packet loss".
Only a reload will get this fixed -> avoid this situation.
> What is true?
>
> The only reason that our 7606 needs to be replaces it because of the
> TCAM. It doesn't do much traffic, like 3Gbps upstream. Only BGP/OSPF.
> And not many ports, 8 x 10Gb fiber + 30 x 1Gb copper (local servers).
>
> We will probably go for the ASR9006. But I would like to use it like I'm
> using the 7600 now, as a router/switch. I have been reading that you
> need to make some uncommon config to create Ethernet VLAN/Trunk
> interfaces and ports, as this is not commonly not done with this router.
> But is this good practice? Will it be fine once I fingered it out?
If spanning tree is involved, the ASR9k gets clunky.
Besides that, it does routing/switching on VLANs and trunks nicely
(though the config is quite different to "more switchy" platforms
like the 6500/7600).
> Last question. Can I take a full BGP feed on both v4 and v6 with a
> A9K-RSP440-TR? Or do I need the -SE?
The RSP440 will cope nicely. It is end-of-life, though.
gert
--
"If was one thing all people took for granted, was conviction that if you
feed honest figures into a computer, honest figures come out. Never doubted
it myself till I met a computer with a sense of humor."
Robert A. Heinlein, The Moon is a Harsh Mistress
Gert Doering - Munich, Germany [email protected]
signature.asc
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/
