I have a 5110 18.1R3-S6.1 facing a trunk with a vlan coming with stacked.
Xe-0/0/46 comes in on 1079 with inner 776, 777.
I'm having a heck of a time figuring out the proper mapping to make this
work. Different docs don't seem to line up with available commands so I've
been getting nowhere
One of many working 204s with 1G.
Model: mx204
Junos: 18.2R3-S1.7
Chassis:
PIC 1 BUILTIN BUILTIN 8XSFPP PIC
Xcvr 0 @(+ NON-JNPR F179CO14506 SFP-LX10
Xcvr 1NON-JNPR F179CO14505 SFP-LX10
Xcvr 2 Et
That's what I was going to chime in on. Behaviour differences between
software versions have done different defaults.
ekrichbaum@atl-bdr1> show interfaces et-0/0/1 | grep FEC
Active defects : None
Ethernet FEC Mode : NONE
eric@cht-bdr2> show interfaces et-0/0/1 |
I tried 17.3 and 17.2 based on a PR, but let me try 17.4. Can't hurt. So
far none of the 4 versions have done anything for me.
-Original Message-
From: juniper-nsp On Behalf Of Tim
Jackson
Sent: Thursday, June 20, 2019 8:48 AM
To: Saku Ytti
Cc: Juniper List
Subject: Re: [j-nsp] 100G D
Has anyone gotten the Fiberstore 100G DAC to link up between a QFX and an MX?
I got link between 2 MX using it without any issue but haven't had any luck to
the QFX.
They detect ok:
Xcvr 48 REV 01 740-061001 C1905258091 QSFP28-100G-CU1M
Xcvr 49 REV 01 740-061001
I had a similar issue with 18.x and MX204. Did you try turning off
auto-negotiation?
set interfaces et-4/0/52 ether-options no-auto-negotiation
I had a similar issue with QFX5100/EX4300 and 40G and this fixed the issue
oddly enough.
Eric
-Original Message-
From: juniper-nsp On Behalf
I like them. 100G FS DAC between a pair works well in 17, not so much in 18
code (although I didn't try disabling auto negotiation, which is a quirk
with the 4300/5100 sometimes). I gave up early on about not hard setting
the interfaces. Never worked for me until I did that. BGP did as expected
You'll have to let us know how well they work. I heard no vc stacking until
v19 code or so. Also wondering about 18 level code. Just took a set of
5100s to 17.3 with good results.
-Original Message-
From: juniper-nsp On Behalf Of Aaron
Gould
Sent: Friday, December 21, 2018 10:34 AM
To: j
3x 40G + 8x 10G
-Original Message-
From: juniper-nsp On Behalf Of Mark Tinka
Sent: Monday, May 14, 2018 6:20 PM
To: Tim Jackson ; Bill Blackford
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] MX204
On 14/May/18 23:49, Tim Jackson wrote:
> Only kinda weird drawback is you can't
I tried the knobs in the kb as well with no luck. Never got the 40G port to
detect as 40. Just split 10s. trying to 40 on 2 ports to a QFX virt chassis.
Eric
-Original Message-
From: juniper-nsp On Behalf Of Nathan Ward
Sent: Monday, May 14, 2018 4:53 PM
To: Bill Blackford
Cc: juni
x/32
> extensive?
>
> Thanks.
>
> Tim
>
> On 26-04-13 15:36, Eric Krichbaum wrote:
>
>> This should be simple but I can't get the behavior I want.
>>
>> Blackhole scenario. Customer set community, I want to see that
>> community and set next-h
This should be simple but I can't get the behavior I want.
Blackhole scenario. Customer set community, I want to see that community
and set next-hop to an address I have with a discard. I've tried both a
discard interface and a basic static route. Those seem ok either way.
set routing-options
snort bsd [mailto:snort...@yahoo.com.au]
Sent: Thursday, March 14, 2013 9:12 AM
To: Eric Krichbaum; 'Jonathan Lassoff'
Cc: 'juniper-nsp'
Subject: Re: [j-nsp] 3750 and 4200
well, i deliberately not to activate lacp at this moment. just want to see
physical links up...
_
That's correct but in this case one is LACP (802.3ad) and one is not so it
won't bring up the links at all.
Eric
From: snort bsd [mailto:snort...@yahoo.com.au]
Sent: Thursday, March 14, 2013 9:17 AM
To: Jonathan Lassoff; Eric Krichbaum
Cc: juniper-nsp
Subject: Re: [j-nsp] 375
-Original Message-
From: Jonathan Lassoff [mailto:j...@thejof.com]
Sent: Wednesday, March 13, 2013 9:16 PM
To: Eric Krichbaum
Cc: snort bsd; juniper-nsp
Subject: Re: [j-nsp] 3750 and 4200
On Wed, Mar 13, 2013 at 6:36 PM, Eric Krichbaum wrote:
> More likely, it's the forced &
More likely, it's the forced "on" mode which disables LACP. Try it with
mode active.
-Original Message-
From: juniper-nsp-boun...@puck.nether.net
[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Jonathan Lassoff
Sent: Wednesday, March 13, 2013 8:34 PM
To: snort bsd
Cc: juniper-ns
16 matches
Mail list logo