[j-nsp] SSB SSRAM memory issue

[Jonas Frey]

Hi Reinier,

you cannot upgrade the SSB-E16 with even more memory, its maxed.

If you use aggregated links its usually a good idea to use different
FPCs for the ae's.
However in your case you are using up almost all FPCs with GE pics, so
that option aint valid.
I am not sure about the 2x4 ge trunk, but could be worth a try.

The problem you probably have is that your L2descriptors are
skyrocketing...i assume you use normal FPC?
A good idea might be to try FPC-E which have double/quad(?) the memory
of the normal FPC for this.

Regards,
Jonas Frey


On Wed, 2007-01-31 at 02:23, Eeden, Reinier wrote:
> Hello,
> 
>  
> 
> I have the same problem as described in this topic: 
> 
>  <http://puck.nether.net/pipermail/juniper-nsp/2005-March/003914.html>
> http://puck.nether.net/pipermail/juniper-nsp/2005-March/003914.html but i
> cannot find any solution anywhere, only how to find out what the issue is.
> 
>  
> 
> Our SSB-E-16-M20 is currently out of SSRAM memory. We work with aggregated
> interfaces in the Juniper m20, we have configured 10x 1g to one aggregated
> interface. This means for each mac-address the system will create 10
> entries. And for each vlan etc.. What can we do ???.
> 
>  
> 
> After doing some research on the net I found out I better could create 2x4x1
> gbit aggregated (2 aggregated links)  on different FPC's and because this
> would save memory? Please can someone give any advise. I also looked on the
> net if I could by that memory modules for the SSB :) but no luck.
> 
>  
> 
> Looking forward for your replies!
> 
>  
> 
> Best regards,
> 
> Reinier van Eeden
> 
> Ecatel LTD.
> 
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp