Re: [j-nsp] MX80 upgrade path 18.4R

I agree with Tobias. If the unit is in production, expect some interruption in services as this type of install is the most disruptive, but should be doable within a maintenance window. - Brian > On Jun 14, 2020, at 4:59 AM, Tobias Heister wrote: > > Hi, > > On 14.06.2020 10:50, Robert Hass

Re: [j-nsp] Rate selectability on MPC7E-MRATE

s not disable the use of the additional 40G. > Been there done that, fully supported. > If you've got something specific from your team or JTAC otherwise, and don't > feel right sharing it on the forum, feel free to reach out directly. > > Joe > > > On 5/6/20, 1:4

Re: [j-nsp] Rate selectability on MPC7E-MRATE

). My advice would be to validate what you are doing with JTAC before implementing In production. - Brian > On May 6, 2020, at 12:47 PM, Tobias Heister wrote: > > On 06.05.2020 18:24, Brian Johnson wrote: >> A wise man once told me… “Just because you can do something, doesn

Re: [j-nsp] Rate selectability on MPC7E-MRATE

11:03 AM, Chris Wopat wrote: > > On Wed, May 6, 2020 at 9:41 AM Brian Johnson wrote: >> >> So you have a 4x10G breakout and a 100G QSFP28 in the same group of 3 >> interfaces and they are all working? Just because I can install and >> configure the optics

Re: [j-nsp] Rate selectability on MPC7E-MRATE

So you have a 4x10G breakout and a 100G QSFP28 in the same group of 3 interfaces and they are all working? Just because I can install and configure the optics, doesn’t mean they will function. This would conflict with what is coming from Juniper Product teams. To be clear, I realize that the

Re: [j-nsp] Rate selectability on MPC7E-MRATE

FYI this is a more complex question…. From my understanding, you need to look at the card as 4 groups of 3 ports (2 QSFP+ and 1 QSFP28). Here are your options: 1. All 3 ports can be used at 40G or 4x10G in any combination. So 120G per group or 480G per card. This is the maximum for the card.

Re: [j-nsp] Prioritize route advertisement

If you have inconsistent MTUs throughout your implementation, you can cause fragmentation and this will lead to re-transmittals. In other words… it will be slower, possibly extremely slow depending on the volume. - Brian Brian Johnson br...@sdjohnsons.us > On Apr 6, 2020, at 10:16 AM, Ja

Re: [j-nsp] EX2300 Code

Always use the JTAC recommends version unless you have a specific feature you need that is not supported in that version. https://kb.juniper.net/InfoCenter/index?page=content=KB21476 Thus... 15.1X53-D591 or 18.2R3-S2 should be good

Re: [j-nsp] Ramp up old MX480

Do you know if you have the enhanced mid-plane? If not, it’s a chassis upgrade to install MPC3 or better line cards. - Brian > On Aug 28, 2019, at 3:15 AM, john doe wrote: > > Hi! > > I need to bump one of my MX480 with better line cards so it can live in the > DFZ another year or so :)

Re: [j-nsp] QFX5100 NAT

NAT is not a supported feature on the QFX platform. - Brian > On Sep 6, 2018, at 2:15 PM, Brendan Mannella wrote: > > Trying to do NAT on a QFX5100 and cannot find where its configured. > Googling around i see its supported but none of the configuration examples > work for it. >

Re: [j-nsp] Which versions of Space support Spotlight

Check out this link: https://www.juniper.net/documentation/en_US/release-independent/spotlight-secure/information-products/pathway-pages/spotlight-secure/index.html

Re: [j-nsp] Juniper SRX 58K cluster IPv6 enable

>From my experience... Any change of the mode on a protocol requires a reboot >of JunOS. Correct? - Brian J. Sent from my iPhone Please excuse typos > On Feb 20, 2018, at 5:59 AM, Ola Thoresen wrote: > >> On 20. feb. 2018 11:10, Imran Kamal wrote: >> Hi all, >> >> Can anyone

Re: [j-nsp] Need Assistance

Completely agree. Unless you want all BGP routes to have a better preference than all OSPF routes. The route policy is a scalpel, the protocol preference is a hammer. - Brian > On Nov 7, 2017, at 7:26 AM, Julian Seifert wrote: > > Hi, > > wouldn't it be more preferable(less

Re: [j-nsp] srx event-options

Diogo, I believe he is shutting down his external interface when a neighbor on the internal interface is down. Alex: This script looks interesting and I'd like to see the final solution when you get it. Thanks. - Brian -Original Message- From: juniper-nsp-boun...@puck.nether.net

Re: [j-nsp] Problems with Link Aggregation

Filippo, Can you send the output of show lacp interface ae0? Thanks - Brian -Original Message- From: juniper-nsp-boun...@puck.nether.net [mailto:juniper-nsp- boun...@puck.nether.net] On Behalf Of Filippo Cugini Sent: Wednesday, March 06, 2013 8:16 AM To:

Re: [j-nsp] J-web on MX5 router

to believe that J-Web will not be developed for this platform? How long does it take for this type of release? - Brian -Original Message- From: Ben Dale [mailto:bd...@comlinx.com.au] Sent: Sunday, March 03, 2013 6:44 PM To: Brian Johnson Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp

Re: [j-nsp] J-web on MX5 router

On that note I'll start a new thread on SNMP for MX series... - Brian From: Tomasz Mikołajek [mailto:tmikola...@gmail.com] Sent: Monday, March 04, 2013 8:57 AM To: Brian Johnson Cc: juniper-nsp@puck.nether.net Subject: Re: [j-nsp] J-web on MX5 router Hello. Brian, maybe use Cacti to have

[j-nsp] MX Series MIBS

I am having a difficult time determining what MIBs to monitor on my new Juniper MX routers. I come from a Cisco shop and know how to monitor CPU, memory and (of course) interface stats. I'm having no issues with monitoring interfaces, but cannot determine what MIBs to monitor for CPU and memory

Re: [j-nsp] MX Series MIBS

They are versioned, I just linked to 11.4 as we are using that release but I would make sure to use the one applicable for your deployment. On Mon, Mar 4, 2013 at 9:09 AM, Brian Johnson bjohn...@drtel.com wrote: I am having a difficult time determining what MIBs to monitor on my new Juniper

[j-nsp] J-web on MX5 router

Simple question, but can the J-web software be installed on the MX5 platform? Thank you. - Brian ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp