Hello again
After long debugging I have just found a solution to the problem. I had enable
vlan tagging on remote side…
> Wiadomość napisana przez aar...@gvtc.com w dniu 09.10.2020, o godz. 19:35:
>
> I found a few things in my notes from when I deployed a few MX204's ...
>
> Early on I
i see ge interfaces in my SRX300 and older SRX240... also I'm pretty sure
legacy MX use ge for 1 gig inerfaces, and perhaps it's just those newer
MX204/10003 that don't.
user1@my-srx> show version
Hostname: my-srx
Model: srx300
Junos: 15.1X49-D170.4
JUNOS Software Release [15.1X49-D170.4]
Well this is coming from my experience with QFX5100, less of an
issue with MX platforms but still for the price tag it was kinda hellish.
Been stable after we worked some of the pitfalls... still got some
chipset related issue when someone makes an error and mix L2 VLANs with
VLAN-CCC
Once upon a time, Łukasz Trąbiński said:
> In Lab I'm trying to set up 1G port on MX204.
I've got several 1G ports on MX204 running okay with the same combo you
showed (chassis config to speed 10g and gigether-options speed 1g) on
18.4R2.7 on 18.1R2.5 - no other config required (so not tweaking
I found a few things in my notes from when I deployed a few MX204's ...
Early on I had Junos: 17.4R2.4 and 1 gig SFP's wouldn't work... said
UNSUPPORTED for 1 gig sfp's 4,5,7
root@lab-mx204> show chassis hardware
Hardware inventory:
Item Version Part number Serial number
--- Begin Message ---
Thanks. So only SRX/MX use xe only for 1/10 capable interfaces. 40/100 are et.
Richard McGovern
Sr Sales Engineer, Juniper Networks
978-618-3342
I’d rather be lucky than good, as I know I am not good
I don’t make the news, I just report it
On 10/9/20, 1:08 PM,
? " For MX/SRX (and I assume PTX and maybe ACX - don't much deal with those
products ) xe is ONLY name allowed" ?
I see otherwise...
MX... MPC7E-MRATE (however et is the name for 40 gig and 100 gig) xe is also
used, but with colon notation)
Physical interface: xe-0/1/5:3, Enabled, Physical
Like many things either it works or it doesn't. I'm not a fan of paying for
software with bugs personally.
We do have Evo in use.
Sent from my iCar
> On Oct 9, 2020, at 12:55 PM, Alain Hebert wrote:
>
> Nice another round of customers doing JNP QA :(
>
> -
> Alain Hebert
Nice another round of customers doing JNP QA :(
-
Alain Hebertaheb...@pubnix.net
PubNIX Inc.
50 boul. St-Charles
P.O. Box 26770 Beaconsfield, Quebec H9W 6G7
Tel: 514-990-5911 http://www.pubnix.netFax: 514-990-9443
On 2020-10-09 12:38, Saku
--- Begin Message ---
I think QFX5200-32C (and some PTX?) are only platforms that have support for
both a Junos version and an EVO version. I think once [very hard if not
impossible] to change.
FYI only
Richard McGovern
Sr Sales Engineer, Juniper Networks
978-618-3342
I’d rather be lucky
Hey Colton,
> I was unaware of Junos OS Evolved until recently. At what version did
> regular Junos evolve into Junos OS Evolved? Is there a certain version
> where after that version, everything ongoing is Junos OS Evolved?
I think EVO appeared in 19.1, but in most cases you don't have a
On Fri, Oct 9, 2020 at 11:49 AM Dave Bell wrote:
>
> On Fri, 9 Oct 2020 at 16:28, David Miller wrote:
>>
>> If you are using RFC 1918 private addresses, then you will want to
>> remove them from the Junos martian dropping.
>>
>> Like:
>> set routing-options martians 192.168.0.0/16 exact allow
>>
On Fri, 9 Oct 2020 at 16:28, David Miller wrote:
> If you are using RFC 1918 private addresses, then you will want to
> remove them from the Junos martian dropping.
>
> Like:
> set routing-options martians 192.168.0.0/16 exact allow
>
> Info:
>
>
If you are using RFC 1918 private addresses, then you will want to
remove them from the Junos martian dropping.
Like:
set routing-options martians 192.168.0.0/16 exact allow
Info:
https://www.juniper.net/documentation/en_US/junos/topics/topic-map/recognize-martian-addr-routing.html
--
--- Begin Message ---
If link is up, not L1 (speed negotiation) issue. What do you get for output of
show interface xe-0/1/4 extensive?
Richard McGovern
Sr Sales Engineer, Juniper Networks
978-618-3342
I’d rather be lucky than good, as I know I am not good
I don’t make the news, I just report
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
When I removed "speed 10g" from chassis section
admin@mx1> show configuration |compare rollback 1
[edit chassis fpc 0 pic 1]
- port 4 {
- speed 10g;
- }
and bounced FPC 0, interface not found.
admin@mx1> show interfaces xe-0/1/4
error: device xe-0/1/4 not found
In
I was unaware of Junos OS Evolved until recently. At what version did
regular Junos evolve into Junos OS Evolved? Is there a certain version
where after that version, everything ongoing is Junos OS Evolved?
___
juniper-nsp mailing list
I tried to play with almost all options in gigether-options section without any
results. Port is UP but it still not working properly.
admin@mx1> show configuration interfaces xe-0/1/4
description TEST;
gigether-options {
no-flow-control;
no-auto-negotiation;
speed 1g;
}
unit 0
--- Begin Message ---
Correct. Unlike EX/QFX where for 1/10 capable interfaces the name will match
the insert Optic. 1G Optic shows as ge, 10G Optic shows as xe. Both ge/xe
names allowed.
For MX/SRX (and I assume PTX and maybe ACX - don't much deal with those
products ) xe is ONLY name
--- Begin Message ---
Just chimed in to agree with Tobias. Speed 1g definitely needed. Recently
migrated from an mx104 to an mx204 with remote end being a different AS.
Mx204 end was link up but remote end was not. In our case the diff in 'show
int $x' output implied that the mx104's
Hi,
Am 09.10.2020 um 13:12 schrieb Łukasz Trąbiński:
In Lab I'm trying to set up 1G port on MX204.
You might need to play around with autoneg options. we have a working 1G LX SFP
running on 18.4R1-S7 on MX204
in our case thats the gigether section:
gigether-options {
no-flow-control;
Hi.
It does not work. according to the documentation it must be xe-
> Wiadomość napisana przez Jackson, William w
> dniu 09.10.2020, o godz. 13:42:
>
> Rename the interface ge-0/1/4
>
> admin@mx1> show interfaces xe-0/1/4
>Physical interface: xe-0/1/4, Enabled, Physical link is Up
>
Rename the interface ge-0/1/4
admin@mx1> show interfaces xe-0/1/4
Physical interface: xe-0/1/4, Enabled, Physical link is Up
Interface index: 154, SNMP ifIndex: 530
Description: TEST
Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode,
Speed:
Hello
In Lab I'm trying to set up 1G port on MX204.
admin@mx1> show configuration interfaces xe-0/1/4
description TEST;
gigether-options {
speed 1g;
}
unit 0 {
family inet {
address 192.168.1.138/30;
}
}
admin@mx1> show configuration chassis fpc 0 pic 1 port 4
speed 10g;
25 matches
Mail list logo