Hi Pieter, I think it's a limitation of management module - I had the same problem on NetIron: MLX module supports maximum 512 BGP sessions, XMR maximum 1024 sessions.
What management module do you have? Maxim Tuliuk On 22 Feb 2011, at 15:23, Pieter Taks wrote: > Hi all, > > While configuring a new peer on an BigIron RX4 we got the following error: > Error! BGP4 cannot allocate memory for peer 253 > > A PDF claims the following > (http://www.terabitsystems.com/foundry-docs/Foundry-BigIron-RX-Series-Datasheet.pdf): > BGPv4: Scalable to 4 million routes, 500 peers and 14,000 attributes with MR2 > management module > > Is there any reason why it wouldn’t want to configure more peering sessions? > - I do not see any system-max setting for this > - As well as I do not see any full memory yet > > Hope someone knows how to resolve this or what is causing this error. > > sh memory > ==================================================================== > BigIron RX active MP slot 33: > Total SDRAM: 2147483648 bytes > Available Memory: 1646874624 bytes > Free Physical Pages: 401374 pages > > Malloc statistics: total 500462813 > os_malloc count: 24059060, fail: 3; os_free count: 24046183, fail 0, diff: > 12877 > ==================================================================== > BigIron RX LP SL 1: > Total SDRAM: 536870912 bytes > Available Memory: 53039104 bytes > ==================================================================== > BigIron RX LP SL 3: > Total SDRAM: 536870912 bytes > Available Memory: 72671232 bytes > ==================================================================== > BigIron RX LP SL 4: > Total SDRAM: 536870912 bytes > Available Memory: 72654848 bytes > > > Any help is appreciated, thanks! > > Pieter Taks > _______________________________________________ > foundry-nsp mailing list > [email protected] > http://puck.nether.net/mailman/listinfo/foundry-nsp
_______________________________________________ foundry-nsp mailing list [email protected] http://puck.nether.net/mailman/listinfo/foundry-nsp
