--- Begin Message ---
Sorry should have been clearer. When I said SRX/MX this for HE SRX only, not
branch (either 2xx or 3xx) and older mid-range; SRX4xxx shows as -xe only.
This is also ONLY for interfaces that support 1/10, not 1 GE only. Older MX
interfaces were either 1GE or 10GE only,
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]
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
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:
>
>
Eric
>
>
>
> -Original Message-
> From: juniper-nsp On Behalf Of Lukasz
> Trabinski
> Sent: Friday, October 09, 2020 9:49 AM
> To: Juniper List
> Subject: Re: [j-nsp] MX204 port 1G
>
>
> When I removed "speed 10g" from chassis section
>
>
--- 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
/112
Eric
-Original Message-
From: juniper-nsp On Behalf Of Lukasz
Trabinski
Sent: Friday, October 09, 2020 9:49 AM
To: Juniper List
Subject: Re: [j-nsp] MX204 port 1G
When I removed "speed 10g" from chassis section
admin@mx1> show configuration |compare rollback 1 [edi
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 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
puck.nether.net>
> Subject: Re: [j-nsp] MX204 port 1G
>
> 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 runn
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;
20 matches
Mail list logo
