Re: [j-nsp] RE-S-X6-64G & ISSU?

Depending on your arrangement with Juniper the price for a backup RE is negligible compared to the rest of the chassis (we got them for free several times). There's really no reason to leave a blank RE slot considering you have redundant SCBs. Luis On Tue, Nov 22, 2016 at 2:19 PM, Michael Hare

Re: [j-nsp] RE-S-X6-64G & ISSU?

Agree with Mark, if you count loss of redundancy as a high priority issue find the funds to purchase dual RE even on dual chassis designs. We made this engineering mistake; initially saved money with a single RE design with dual PE MX104s. We've had some NAND corruption RE failures that are

Re: [j-nsp] EVPN -VXLAN in production

Yes I have two small pods setup using VXLAN/EVPN with IP Fabric. ( eBGP underlay/iBGP overlay ) D40 is the place to be on code and seems to have fixed most of the problems I had. Seems to work well now. Can get me off list for more details. On 22/11/2016, 15:02, "juniper-nsp on behalf of Amos

Re: [j-nsp] firewall filter terminating action

Hi, Yes, any non-terminating action - log, syslog, police, sample, count, etc - has an implicit accept at the end. On Tue, Nov 22, 2016 at 10:35 AM, Chen Jiang wrote: > Hi! Experts > > Sorry for disturbing, I have a question but couldn't find the answer, could > you pls

Re: [j-nsp] Questions about EX4550 switches

On 16/Nov/16 16:42, Valentini, Lucio wrote: > The 12.3R12 is recommended also for EX2200 and EX4200; always follow > Juniper´s recommendations! The table of recommended versions is available on > the website juniper.net > Ref.: >

Re: [j-nsp] RE-S-X6-64G & ISSU?

On 14/Nov/16 17:04, Aaron wrote: > Have y'all ever thought through the benefits of having dual RE in one > chassis compared to 2 chassis with 1 RE in each ? > > Like if I'm thinking about getting a MX480 with dual RE... what about > instead, getting dual MX240 with 1 RE in each ? ...and

[j-nsp] firewall filter terminating action

Hi! Experts Sorry for disturbing, I have a question but couldn't find the answer, could you pls shed some light on this? >From the documents we know that Juniper firewall filter has 3 termination actions: accept, discard, and reject. but when we configured mirror and sample action, if we

Re: [j-nsp] Questions about EX4550 switches

On 16/Nov/16 17:12, Doug McIntyre wrote: > > BUT, I know on this platform (EX4550), that certain interface cards require > newer code in the 13.2 series of code releases. So, make sure you check > out the requirements of all the modules installed in the switch. I know > the 40GB expansion

[j-nsp] how to disconnect/kill tcp session from juniper router

I have an unauthorized telnet session attached to my router but it does not show up under "show system users" and they have not successfully logged so it doesn't seem that I can do the "request system logout.." thing I do however so unsuccessful login attempts in syslog How do I

[j-nsp] EVPN -VXLAN in production

Hi Everybody, We are working on a new DC design for a relatively large deployment (start at 20 racks and grow to about 60). We are considering EVPN-VXLAN for extending L2 between rows (we failed convincing the server guys that they don’t need this). We are wondering if anyone has any

Re: [j-nsp] SNMP NMS support of Junos VLAN MIBs

Check out Observium. I don't know about this specific MIB, but it correctly detects vlan memberships for me. On Dec 9, 2015 14:32, "Chuck Anderson" wrote: > Has anyone tried to use or implement polling of the Q-BRIDGE-MIB on > any Juniper products, using either commercial or open

[j-nsp] EVPN -VXLAN in production

Hi Everybody, We are working on a new DC design for a relatively large deployment (start at 20 racks and grow to about 60). We are considering EVPN-VXLAN for extending L2 between rows (we failed convincing the server guys that they don’t need this). We are wondering if anyone has any

Re: [j-nsp] Questions about EX4550 switches

On Tue, Nov 22, 2016 at 08:22:04AM +0200, Mark Tinka wrote: > On 16/Nov/16 17:12, Doug McIntyre wrote: > > BUT, I know on this platform (EX4550), that certain interface cards require > > newer code in the 13.2 series of code releases. So, make sure you check > > out the requirements of all the