[j-nsp] M160/JunOS 7.6R1.10: ae0 fails to install L2 descriptor
Josef Buchsteiner
josefb at juniper.net
Fri Dec 29 11:30:40 EST 2006
pb> I have a couple of questions:
pb> a) Is it normal to have 32k L2 Descriptors for 8.2k Next-Hop Entries?
yes.. since this is ethernet and the layer2 header size is
big for ethernet and you most likely have all three links on
one FPC. i.e 3 times more resources.
pb> b) Is there a way to increase the number of available L2 Descriptors? (how
pb> many L2 Descriptors does a SFM-16 support?)
this has nothing to do with the SFM.. Enhanced FPC will have
about 160K space... its all about memory
pb> c) Is there a way to make the router fail with less impact to the network
pb> (for example simply shutting down the new interface automatically instead of
pb> refusing to update the next-hop table until the interface is taken down and
pb> all sfms are restarted manually)
there would have been never a need to restart any SFM. all
you would have need to do is to deactivate the aggregate
interface and enable it again without the third member link.
You could also maybe set the member links on different FPCs
so you better share the space of L2 Descriptor among the
FPCs. If you have three member-links you triple the L2
resources you need.
In fact you know only that you run out of resource once you
try to program it in hardware and the only way is to refuse
it. There is no real good way to know upfront. I believe the
RSMON feature is able to monitor such resources and will
send an alarm if configured once you reached a certain
threshold so you know that you are moving to the limits.
pb>
pb> Any help is appreciated.
pb> Thanks in advance, Peter
pb>
pb>
pb> _________________________________________________________________
pb> FREE pop-up blocking with the new MSN Toolbar - get it now!
pb> http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/
pb>
pb> _______________________________________________
pb> juniper-nsp mailing list juniper-nsp at puck.nether.net
pb> https://puck.nether.net/mailman/listinfo/juniper-nsp
pb>
pb>
pb>
More information about the juniper-nsp
mailing list