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 <e...@telic.us> 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 1                NON-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 <juniper-nsp-boun...@puck.nether.net> On Behalf Of Lukasz 
> Trabinski
> Sent: Friday, October 09, 2020 9:49 AM
> To: Juniper List <juniper-nsp@puck.nether.net>
> 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 <rmcgov...@juniper.net> 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" <luk...@trabinski.net> wrote:
> >
> >    Hi.
> >
> >    It does not work. according to the documentation it must be xe-
> >
> >> Wiadomość napisana przez Jackson, William <william.jack...@gibtele.com> 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" 
> >> <juniper-nsp-boun...@puck.nether.net on behalf of luk...@trabinski.net> 
> >> 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-NbGR
> >> h0FKlipj4DlsqFCEEmmURbUIQ$
> >>
> >>
> >
> >
> >
> >
> > Juniper Business Use Only
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp@puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
>
> --
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> _______________________________________________
> 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

Reply via email to