[j-nsp] Suggestions for Edge/Peering Router..
Gert Doering
gert at greenie.muc.de
Mon Sep 23 03:23:17 EDT 2019
Hi,
On Mon, Sep 23, 2019 at 09:15:48AM +0200, Mark Tinka wrote:
> We hit an issue where policing did not work, despite being activated. We
> then realized we had to explicitly enable "l2 qos" for our TCAM profile.
> This is traffic-affecting. You then verify by bumping the hardware ACL
> counters.
>
> Now, where this gets hairy, is when you update the TCAM profile to
> enable policing, all TCAM resources are then exhausted because the
> default slicing of the TCAM in EOS shares it across various protocols
> and features, including ACL's, MPLS, IPv6, non-IP, PBR, pcap, e.t.c. So
> in order to support policing, you have to give up some of these features
Which box was this? Trident or Jericho?
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 gert at greenie.muc.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 630 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/juniper-nsp/attachments/20190923/a1af5ceb/attachment.sig>
More information about the juniper-nsp
mailing list