Re: [j-nsp] MX204 port 1G
--- 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, not 1/10 (SFP+). Newer MX modules with 1/10 support shows as -xe only. Hopefully this is clearer. 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, 4:55 PM, "aar...@gvtc.com" wrote: [External Email. Be cautious of content] 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] user1@my-srx> show interfaces terse Interface Admin Link ProtoLocal Remote ge-0/0/0upup ge-0/0/0.0 upup eth-switch user1@my-srx240> show version Hostname: my-srx240 Model: srx240h JUNOS Software Release [12.1X46-D40.2] user1@my-srx240> show interfaces terse | grep ^ge ge-0/0/0upup ge-0/0/0.0 upup ge-0/0/1updown ge-0/0/1.0 updown eth-switch -Aaron Juniper Business Use Only --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 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 Description > Chassisremoved JNP204 [MX204] > Routing Engine 0 BUILTIN BUILTIN RE-S-1600x8 > CB 0 REV 27 750-069579 removed JNP204 [MX204] > FPC 0 BUILTIN BUILTIN MPC > PIC 0 BUILTIN BUILTIN 4XQSFP28 PIC >Xcvr 0 REV 01 740-043308 removed QSFP+-40G-LR4 > PIC 1 BUILTIN BUILTIN 8XSFPP PIC >Xcvr 4NON-JNPR removed UNSUPPORTED >Xcvr 5NON-JNPR removed UNSUPPORTED >Xcvr 7 `NON-JNPR removed UNSUPPORTED > > > I later upgraded to Junos: 18.4R1-S1.1 and then 1 gig sfp's worked, BUT one > of them was still not working, and I removed it, so I don't know of there was > a vendor sfp that didn't work at all or this one was broken > > Good link... > https://apps.juniper.net/home/port-checker/ > > - Here was my chassis port configs... interestingly, you need to set the > ports to 10g that you want to use as 1 gig > > I tried to simply configure pic 0 port 0 as 40g and the pic’s stayed > offline…even after restarting BOTH pics as is stated as required, they still > stay offline… it wasn’t until I configure explicitly all ports, that they > finally came online and then port to my upstream device came up also… > > set chassis fpc 0 pic 0 port 0 speed 100g > set chassis fpc 0 pic 0 port 1 speed 100g > set chassis fpc 0 pic 0 port 2 speed 40g > set chassis fpc 0 pic 0 port 3 speed 40g > > set chassis fpc 0 pic 1 port 0 speed 10g > set chassis fpc 0 pic 1 port 1 speed 10g > set chassis fpc 0 pic 1 port 2 speed 10g > set chassis fpc 0 pic 1 port 3 speed 10g > set chassis fpc 0 pic 1 port 4 speed 10g > set chassis fpc 0 pic 1 port 5 speed 10g > set chassis fpc 0 pic 1 port 6 speed 10g > set chassis fpc 0 pic 1 port 7 speed 10g > > > root> show interfaces terse | grep "^et|^xe|^ge" > et-0/0/0updown > et-0/0/1updown > et-0/0/2updown > et-0/0/3updown > xe-0/1/0updown > xe-0/1/1updown > xe-0/1/2updown > xe-0/1/3updown > xe-0/1/4updown > xe-0/1/5updown > xe-0/1/6updown > xe-0/1/7updown > > for ports you want to use are 1 gig, do this... > > config > > set interfaces xe-0/1/4 gigether-options speed 1g > set interfaces xe-0/1/5 gigether-options speed 1g > set interfaces xe-0/1/6 gigether-options speed 1g > set interfaces xe-0/1/7 gigether-options speed 1g > > > root> show interfaces xe-0/1/4 | grep speed > Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, > Speed Configuration: 1G > > root> show interfaces xe-0/1/5 | grep speed > Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, > Speed Configuration: 1G > > root> show interfaces xe-0/1/6 | grep speed > Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, > Speed Configuration: 1G > > root> show interfaces xe-0/1/7 | grep speed > Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, > Speed Configuration: 1G > > > -Aaron > ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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] user1@my-srx> show interfaces terse Interface Admin Link ProtoLocal Remote ge-0/0/0upup ge-0/0/0.0 upup eth-switch user1@my-srx240> show version Hostname: my-srx240 Model: srx240h JUNOS Software Release [12.1X46-D40.2] user1@my-srx240> show interfaces terse | grep ^ge ge-0/0/0upup ge-0/0/0.0 upup ge-0/0/1updown ge-0/0/1.0 updown eth-switch -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 autoneg or fec or the like). Have you tried alternate optics or such? -- Chris Adams ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 Description Chassisremoved JNP204 [MX204] Routing Engine 0 BUILTIN BUILTIN RE-S-1600x8 CB 0 REV 27 750-069579 removed JNP204 [MX204] FPC 0 BUILTIN BUILTIN MPC PIC 0 BUILTIN BUILTIN 4XQSFP28 PIC Xcvr 0 REV 01 740-043308 removed QSFP+-40G-LR4 PIC 1 BUILTIN BUILTIN 8XSFPP PIC Xcvr 4NON-JNPR removed UNSUPPORTED Xcvr 5NON-JNPR removed UNSUPPORTED Xcvr 7 `NON-JNPR removed UNSUPPORTED I later upgraded to Junos: 18.4R1-S1.1 and then 1 gig sfp's worked, BUT one of them was still not working, and I removed it, so I don't know of there was a vendor sfp that didn't work at all or this one was broken Good link... https://apps.juniper.net/home/port-checker/ - Here was my chassis port configs... interestingly, you need to set the ports to 10g that you want to use as 1 gig I tried to simply configure pic 0 port 0 as 40g and the pic’s stayed offline…even after restarting BOTH pics as is stated as required, they still stay offline… it wasn’t until I configure explicitly all ports, that they finally came online and then port to my upstream device came up also… set chassis fpc 0 pic 0 port 0 speed 100g set chassis fpc 0 pic 0 port 1 speed 100g set chassis fpc 0 pic 0 port 2 speed 40g set chassis fpc 0 pic 0 port 3 speed 40g set chassis fpc 0 pic 1 port 0 speed 10g set chassis fpc 0 pic 1 port 1 speed 10g set chassis fpc 0 pic 1 port 2 speed 10g set chassis fpc 0 pic 1 port 3 speed 10g set chassis fpc 0 pic 1 port 4 speed 10g set chassis fpc 0 pic 1 port 5 speed 10g set chassis fpc 0 pic 1 port 6 speed 10g set chassis fpc 0 pic 1 port 7 speed 10g root> show interfaces terse | grep "^et|^xe|^ge" et-0/0/0updown et-0/0/1updown et-0/0/2updown et-0/0/3updown xe-0/1/0updown xe-0/1/1updown xe-0/1/2updown xe-0/1/3updown xe-0/1/4updown xe-0/1/5updown xe-0/1/6updown xe-0/1/7updown for ports you want to use are 1 gig, do this... config set interfaces xe-0/1/4 gigether-options speed 1g set interfaces xe-0/1/5 gigether-options speed 1g set interfaces xe-0/1/6 gigether-options speed 1g set interfaces xe-0/1/7 gigether-options speed 1g root> show interfaces xe-0/1/4 | grep speed Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, Speed Configuration: 1G root> show interfaces xe-0/1/5 | grep speed Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, Speed Configuration: 1G root> show interfaces xe-0/1/6 | grep speed Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, Speed Configuration: 1G root> show interfaces xe-0/1/7 | grep speed Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, Speed Configuration: 1G -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
--- 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, "aar...@gvtc.com" wrote: [External Email. Be cautious of content] ? " 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 link is Down Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, BPDU Error: None, Loop Detect PDU Error: None, Physical interface: et-1/0/0, Enabled, Physical link is Up Link-level type: Flexible-Ethernet, MTU: 9216, MRU: 9224, Speed: 40Gbps, BPDU Error: None, Loop Detect PDU Error: None, Physical interface: et-1/0/2, Enabled, Physical link is Down Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps, BPDU Error: None, Loop Detect PDU Error: None, ACX has ge, ex, and et (got 1, 10 and 40 gig) user1@my5048> show system information Model: acx5048 Family: junos Junos: 17.4R2-S11 Hostname: my5048 ... ge-0/0/10 upup ge-0/0/10.0 upup inet 10.101.14.197/30 xe-0/0/25 upup xe-0/0/25.0 upup aenet--> ae5.0 et-0/0/48 upup et-0/0/48.0 upup aenet--> ae42.0 -Aaron Juniper Business Use Only --- End Message --- ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
? " 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 link is Down Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode, Speed: 10Gbps, BPDU Error: None, Loop Detect PDU Error: None, Physical interface: et-1/0/0, Enabled, Physical link is Up Link-level type: Flexible-Ethernet, MTU: 9216, MRU: 9224, Speed: 40Gbps, BPDU Error: None, Loop Detect PDU Error: None, Physical interface: et-1/0/2, Enabled, Physical link is Down Link-level type: Ethernet, MTU: 1514, MRU: 1522, Speed: 100Gbps, BPDU Error: None, Loop Detect PDU Error: None, ACX has ge, ex, and et (got 1, 10 and 40 gig) user1@my5048> show system information Model: acx5048 Family: junos Junos: 17.4R2-S11 Hostname: my5048 ... ge-0/0/10 upup ge-0/0/10.0 upup inet 10.101.14.197/30 xe-0/0/25 upup xe-0/0/25.0 upup aenet--> ae5.0 et-0/0/48 upup et-0/0/48.0 upup aenet--> ae42.0 -Aaron ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 >> >> Info: >> https://www.juniper.net/documentation/en_US/junos/topics/topic-map/recognize-martian-addr-routing.html > > > This is not required. RFC1918 are not martians. You are correct. Got my wires crossed there for a second. Apologies for the noise. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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: > > https://www.juniper.net/documentation/en_US/junos/topics/topic-map/recognize-martian-addr-routing.html This is not required. RFC1918 are not martians. ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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
--
__
David Miller
dmil...@tiggee.com
On Fri, Oct 9, 2020 at 11:08 AM Eric Krichbaum wrote:
>
> 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 NON-JNPR G1908908498 SFP-LX10
>
> Chassis ports are set 10G:
> set chassis fpc 0 pic 0 tunnel-services bandwidth 200g
> set chassis fpc 0 pic 0 port 0 speed 100g
> set chassis fpc 0 pic 0 port 1 speed 40g
> set chassis fpc 0 pic 0 port 2 speed 40g
> set chassis fpc 0 pic 1 port 0 speed 10g
> set chassis fpc 0 pic 1 port 1 speed 10g
> set chassis fpc 0 pic 1 port 2 speed 10g
> set chassis fpc 0 pic 1 port 3 speed 10g
> set chassis fpc 0 pic 1 port 4 speed 10g
> set chassis fpc 0 pic 1 port 5 speed 10g
> set chassis fpc 0 pic 1 port 6 speed 10g
> set chassis fpc 0 pic 1 port 7 speed 10g
>
> Interface:
> set interfaces xe-0/1/0 gigether-options no-auto-negotiation
> set interfaces xe-0/1/0 gigether-options speed 1g
> set interfaces xe-0/1/0 unit 0 family inet rpf-check mode loose
> set interfaces xe-0/1/0 unit 0 family inet address x.x.x.x/30
> set interfaces xe-0/1/0 unit 0 family inet6 address x:x:x:x::x/127
> set interfaces xe-0/1/1 gigether-options no-auto-negotiation
> set interfaces xe-0/1/1 gigether-options speed 1g
> set interfaces xe-0/1/1 unit 0 family inet rpf-check mode loose
> set interfaces xe-0/1/1 unit 0 family inet address x.x.x.x/29
> set interfaces xe-0/1/1 unit 0 family inet6 address x:x:x:x::x:x/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 [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 documentation we can read that 10g is default. It’s seems not.
> When I removed "speed 1G” from gigether-options section, interface is found,
> but is DOWN.
>
> Any Idea? :)
>
>
>
>
>
> > Wiadomość napisana przez Richard McGovern w dniu
> > 09.10.2020, o godz. 16:05:
> >
> > 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 allowed, and is used to indicate the interface
> > is 10G capable. For show interface info, the interface will show the
> > correct speed.
> >
> > NOTE: Please don't ask me the why. Tried to fight that battle, this will
> > NOT be changed.
> >
> > As for William original question why are you hard coding 1G in the config,
> > and setting 10G in the HW (chassis stanza)? From initial look, that is
> > first place to look. BTW, on MX204, neither should needed. FPC does not
> > need speed setting (default supports 1/10) and auto should work fine at
> > interface config. If you needed fixed speed for working with remote device,
> > then set speed at interface level only. If you are going to do both, make
> > them equal, although I am guess chassis fpc only has 10G as option.
> >
> > Did you have issue with auto for interface, which is default setting?
> >
> > HTH, Rich
> >
> > 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, 8:02 AM, "Łukasz Trąbiński" wrote:
> >
> >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
> >>
> >> ad
Re: [j-nsp] MX204 port 1G
--- 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 it
On 10/9/20, 10:25 AM, "Łukasz Trąbiński" wrote:
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 {
family inet {
address xx.xx.xx.xx/30;
}
}
When i removed "speed 10g" from chassis section and bounced FPC port was
DOWN.
> Wiadomość napisana przez Tobias Heister w dniu
09.10.2020, o godz. 14:44:
>
> 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;
>no-auto-negotiation;
>speed 1g;
> }
>
> Not sure if the Flow Control stuff was mandatory, but without the
no-auto-negotation the link was not useable. It might also help to check
autoneg settings on the other end (if you have access).
>
> --
> Kind Regards
> Tobias Heister
Juniper Business Use Only
--- End Message ---
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 NON-JNPR G1908908498 SFP-LX10
Chassis ports are set 10G:
set chassis fpc 0 pic 0 tunnel-services bandwidth 200g
set chassis fpc 0 pic 0 port 0 speed 100g
set chassis fpc 0 pic 0 port 1 speed 40g
set chassis fpc 0 pic 0 port 2 speed 40g
set chassis fpc 0 pic 1 port 0 speed 10g
set chassis fpc 0 pic 1 port 1 speed 10g
set chassis fpc 0 pic 1 port 2 speed 10g
set chassis fpc 0 pic 1 port 3 speed 10g
set chassis fpc 0 pic 1 port 4 speed 10g
set chassis fpc 0 pic 1 port 5 speed 10g
set chassis fpc 0 pic 1 port 6 speed 10g
set chassis fpc 0 pic 1 port 7 speed 10g
Interface:
set interfaces xe-0/1/0 gigether-options no-auto-negotiation
set interfaces xe-0/1/0 gigether-options speed 1g
set interfaces xe-0/1/0 unit 0 family inet rpf-check mode loose
set interfaces xe-0/1/0 unit 0 family inet address x.x.x.x/30
set interfaces xe-0/1/0 unit 0 family inet6 address x:x:x:x::x/127
set interfaces xe-0/1/1 gigether-options no-auto-negotiation
set interfaces xe-0/1/1 gigether-options speed 1g
set interfaces xe-0/1/1 unit 0 family inet rpf-check mode loose
set interfaces xe-0/1/1 unit 0 family inet address x.x.x.x/29
set interfaces xe-0/1/1 unit 0 family inet6 address x:x:x:x::x:x/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 [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 documentation we can read that 10g is default. It’s seems not.
When I removed "speed 1G” from gigether-options section, interface is found,
but is DOWN.
Any Idea? :)
> Wiadomość napisana przez Richard McGovern w dniu
> 09.10.2020, o godz. 16:05:
>
> 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 allowed, and is used to indicate the interface is
> 10G capable. For show interface info, the interface will show the correct
> speed.
>
> NOTE: Please don't ask me the why. Tried to fight that battle, this will NOT
> be changed.
>
> As for William original question why are you hard coding 1G in the config,
> and setting 10G in the HW (chassis stanza)? From initial look, that is first
> place to look. BTW, on MX204, neither should needed. FPC does not need
> speed setting (default supports 1/10) and auto should work fine at interface
> config. If you needed fixed speed for working with remote device, then set
> speed at interface level only. If you are going to do both, make them equal,
> although I am guess chassis fpc only has 10G as option.
>
> Did you have issue with auto for interface, which is default setting?
>
> HTH, Rich
>
> 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, 8:02 AM, "Łukasz Trąbiński" wrote:
>
>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
>> Interface index: 154, SNMP ifIndex: 530
>> Description: TEST
>> Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode,
>> Speed: 10Gbps,
>>
>> On 09/10/2020, 13:16, "juniper-nsp on behalf of Łukasz Trąbiński"
>>
>> wrote:
>>
>> 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;
>>
>> Port is UP, but
Re: [j-nsp] MX204 port 1G
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 documentation we can read that 10g is default. It’s seems not.
When I removed "speed 1G” from gigether-options section, interface is found,
but is DOWN.
Any Idea? :)
> Wiadomość napisana przez Richard McGovern w dniu
> 09.10.2020, o godz. 16:05:
>
> 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 allowed, and is used to indicate the interface is
> 10G capable. For show interface info, the interface will show the correct
> speed.
>
> NOTE: Please don't ask me the why. Tried to fight that battle, this will NOT
> be changed.
>
> As for William original question why are you hard coding 1G in the config,
> and setting 10G in the HW (chassis stanza)? From initial look, that is first
> place to look. BTW, on MX204, neither should needed. FPC does not need
> speed setting (default supports 1/10) and auto should work fine at interface
> config. If you needed fixed speed for working with remote device, then set
> speed at interface level only. If you are going to do both, make them equal,
> although I am guess chassis fpc only has 10G as option.
>
> Did you have issue with auto for interface, which is default setting?
>
> HTH, Rich
>
> 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, 8:02 AM, "Łukasz Trąbiński" wrote:
>
>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
>> Interface index: 154, SNMP ifIndex: 530
>> Description: TEST
>> Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode,
>> Speed: 10Gbps,
>>
>> On 09/10/2020, 13:16, "juniper-nsp on behalf of Łukasz Trąbiński"
>>
>> wrote:
>>
>> 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;
>>
>> Port is UP, but I can’t see any MAC address from remote side or I can’t
>> ping remote side.
>>
>>
>> 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:
>> 10Gbps,
>> BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None,
>> Loopback: None, Source filtering: Disabled, Flow control: Enabled,
>> Speed Configuration: 1G
>>
>>
>> Junos: 18.4R3-S5.4 but also tried on 18.4R3.3. I also setup
>> auto-negotiation and fec options but without success.
>>
>> SFP:
>> Xcvr 4 REV 01 740-011614 PJD2XXX SFP-LX10
>> ___
>> juniper-nsp mailing list juniper-nsp@puck.nether.net
>>
>> https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/juniper-nsp__;!!NEt6yMaO-gk!T3KOFxazJ51vM0Q41a56Y1mr9YYi0Ruejmyy-NbGRh0FKlipj4DlsqFCEEmmURbUIQ$
>>
>>
>
>
>
>
> Juniper Business Use Only
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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 {
family inet {
address xx.xx.xx.xx/30;
}
}
When i removed "speed 10g" from chassis section and bounced FPC port was DOWN.
> Wiadomość napisana przez Tobias Heister w dniu
> 09.10.2020, o godz. 14:44:
>
> 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;
>no-auto-negotiation;
>speed 1g;
> }
>
> Not sure if the Flow Control stuff was mandatory, but without the
> no-auto-negotation the link was not useable. It might also help to check
> autoneg settings on the other end (if you have access).
>
> --
> Kind Regards
> Tobias Heister
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
--- 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 allowed, and is used to indicate the interface is
10G capable. For show interface info, the interface will show the correct
speed.
NOTE: Please don't ask me the why. Tried to fight that battle, this will NOT
be changed.
As for William original question why are you hard coding 1G in the config, and
setting 10G in the HW (chassis stanza)? From initial look, that is first place
to look. BTW, on MX204, neither should needed. FPC does not need speed
setting (default supports 1/10) and auto should work fine at interface config.
If you needed fixed speed for working with remote device, then set speed at
interface level only. If you are going to do both, make them equal, although I
am guess chassis fpc only has 10G as option.
Did you have issue with auto for interface, which is default setting?
HTH, Rich
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, 8:02 AM, "Łukasz Trąbiński" wrote:
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
> Interface index: 154, SNMP ifIndex: 530
> Description: TEST
> Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode,
Speed: 10Gbps,
>
> On 09/10/2020, 13:16, "juniper-nsp on behalf of Łukasz Trąbiński"
wrote:
>
>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;
>
>Port is UP, but I can’t see any MAC address from remote side or I
can’t ping remote side.
>
>
>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: 10Gbps,
> BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error:
None,
> Loopback: None, Source filtering: Disabled, Flow control: Enabled,
> Speed Configuration: 1G
>
>
>Junos: 18.4R3-S5.4 but also tried on 18.4R3.3. I also setup
auto-negotiation and fec options but without success.
>
>SFP:
>Xcvr 4 REV 01 740-011614 PJD2XXX SFP-LX10
>___
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>
https://urldefense.com/v3/__https://puck.nether.net/mailman/listinfo/juniper-nsp__;!!NEt6yMaO-gk!T3KOFxazJ51vM0Q41a56Y1mr9YYi0Ruejmyy-NbGRh0FKlipj4DlsqFCEEmmURbUIQ$
>
>
Juniper Business Use Only
--- End Message ---
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
--- 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 default was auto-negotiation whereas
the mx204 was ambiguous. We added auto-negotiation to resolve our issue.
-Michael
> -Original Message-
> From: juniper-nsp On Behalf Of
> Tobias Heister
> Sent: Friday, October 9, 2020 7:45 AM
> To: Łukasz Trąbiński ; Juniper List n...@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 running on 18.4R1-S7 on MX204
>
> in our case thats the gigether section:
> gigether-options {
> no-flow-control;
> no-auto-negotiation;
> speed 1g;
> }
>
> Not sure if the Flow Control stuff was mandatory, but without the no-auto-
> negotation the link was not useable. It might also help to check autoneg
> settings on the other end (if you have access).
>
> --
> Kind Regards
> Tobias Heister
> ___
> juniper-nsp mailing list juniper-nsp@puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
--- End Message ---
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
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
running on 18.4R1-S7 on MX204
in our case thats the gigether section:
gigether-options {
no-flow-control;
no-auto-negotiation;
speed 1g;
}
Not sure if the Flow Control stuff was mandatory, but without the
no-auto-negotation the link was not useable. It might also help to check
autoneg settings on the other end (if you have access).
--
Kind Regards
Tobias Heister
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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
> Interface index: 154, SNMP ifIndex: 530
> Description: TEST
> Link-level type: Ethernet, MTU: 1514, MRU: 1522, LAN-PHY mode,
> Speed: 10Gbps,
>
> On 09/10/2020, 13:16, "juniper-nsp on behalf of Łukasz Trąbiński"
> wrote:
>
>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;
>
>Port is UP, but I can’t see any MAC address from remote side or I can’t
> ping remote side.
>
>
>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:
> 10Gbps,
> BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None,
> Loopback: None, Source filtering: Disabled, Flow control: Enabled,
> Speed Configuration: 1G
>
>
>Junos: 18.4R3-S5.4 but also tried on 18.4R3.3. I also setup
> auto-negotiation and fec options but without success.
>
>SFP:
>Xcvr 4 REV 01 740-011614 PJD2XXX SFP-LX10
>___
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] MX204 port 1G
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: 10Gbps,
On 09/10/2020, 13:16, "juniper-nsp on behalf of Łukasz Trąbiński"
wrote:
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;
Port is UP, but I can’t see any MAC address from remote side or I can’t
ping remote side.
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:
10Gbps,
BPDU Error: None, Loop Detect PDU Error: None, MAC-REWRITE Error: None,
Loopback: None, Source filtering: Disabled, Flow control: Enabled,
Speed Configuration: 1G
Junos: 18.4R3-S5.4 but also tried on 18.4R3.3. I also setup
auto-negotiation and fec options but without success.
SFP:
Xcvr 4 REV 01 740-011614 PJD2XXX SFP-LX10
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
