[j-nsp] MX204 and copper SFP?

[Chuck Anderson]

Back-in-the-day we had fe-x/x/x for 10/100 Mbps ports.  Now we have ge-x/x/x that can take a 100 Mbps SFP, but the name doesn't change to fe-x/x/x AFAIK.  So there is precedent for the names not changing when the speed changes.

But I do like having the ability to match ports based on speed, e.g. find all "uplink" ports by assuming ge-* are access ports and xe-* are uplinks.  Patterns can be used within configuration groups and interface-ranges.

On Thu, Apr 05, 2018 at 01:38:46PM +0000, Nelson, Brian wrote:
> Port-foo is so archaic. 
> It's an interface, inf-x/x/x would be more germane.
> 
> Brian
> 
> -----Original Message-----
> From: juniper-nsp [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Ola Thoresen
> Sent: Thursday, April 05, 2018 3:59 AM
> To: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] MX204 and copper SFP?
> 
> On 05. april 2018 10:44, Saku Ytti wrote:
> 
> > Since of the fathers.
> >
> > 'Cisco did it'.
> >
> > I also see no value in it.
> 
> Don't we all love that "linux" changed from eth0, eth1, eth2... to beautiful stuff like wwp0s20u4 and enp0s25...
> 
> Just call them port-x/x/x and be done with it.
> 
> 
> /Ola (T)