Re: [j-nsp] MX Lab config for virtual-switch

2016-06-02 Thread Joshua Morgan
Why not set a vlan-id at the bridge domain level? That will take care of normalising the VLAN IDs. Josh On Friday, 3 June 2016, Matthew Crocker wrote: > > Hello, > > I’m trying to lab out the following scenario. Running into a couple > snags, hoping someone can point me to the right documenta

[j-nsp] MX Lab config for virtual-switch

2016-06-02 Thread Matthew Crocker
Hello, I’m trying to lab out the following scenario. Running into a couple snags, hoping someone can point me to the right documentation. I have 17 SRX300s connected to a WAN that I want to link together into the same virtual-switch/bridge/VPLS/??? in my MX240. The SRXs will enter the MX

Re: [j-nsp] force-64bit

2016-06-02 Thread Chris Adams
Once upon a time, Jesper Skriver said: > The flip side is that all pointers are twice the size, in an application like > rpd I'd expect most of the memory usage to be pointers, so we can expect ~2x > the memory usage. That coupled with memory access typically being the > bottleneck makes it les

Re: [j-nsp] force-64bit

2016-06-02 Thread Jesper Skriver
> On 01 Jun 2016, at 21:29, Vincent Bernat wrote: > > The other benefit would be the ability for rpd to make use of more CPU > registers and to be faster. On average, one could expect a 20% speedup > when recompiling for x86-64. I have absolutely no idea if such number > would apply to rpd. The

Re: [j-nsp] force-64bit

2016-06-02 Thread raf
Le 02/06/2016 à 00:02, Olivier Benghozi a écrit : This is not completely contradictory with the Juniper doc ; as usual with the Juniper doc written with feet, you have to read between the lines: -> Written in the doc: "Tip: You need not restart the routing protocol process (rpd) to use the 6