Re: [j-nsp] mixed interface, switching + routed

[Hugo Slabbert]

On Tue 2016-Jul-05 13:51:26 -0500, Josh Reynolds  wrote:


Thanks Hugo, I'll try and give that a shot.

So basically setup an ethernet-switching interface on unit 0, port
mode trunk, native vlan as the current access vlan, member list
includes the new vlan? 


Exactly.  One thing to watch: If you include the native vlan as a member as 
well, it will show up as both tagged and untagged on the port.  IOW, 
untagged frames as well as frames tagged with your native vlan ID will be 
accepted and plopped in the right VLAN, but frames from the VLAN egressing 
the port will be tagged, iirc.  Yea...


I think I'm confused about how I would assign an RVI to this in that 
state.


Do you have a quick example config I might be able to work off of?


In a non-ELS setup, it would be something like:

interfaces {
ge-x/y/z {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members VLAN600;
}
native-vlan-id $your-native-vlan;
}
}
}
vlan {
unit 600 {
description "RVI for L3 in VLAN600"
family inet {
address a.b.c.d/mask;
}
}
}
}
vlans {
VLAN600 {
vlan-id 600;
l3-interface vlan.600;
}
}

Check after committing that VLAN membership is as you expect it:

`show ethernet-switching interfaces ge-x/y/z`


Thank you!


np

--
Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal


signature.asc
Description: Digital signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mixed interface, switching + routed

[Matt Freitag]

Josh,

You should be able to define interfaces vlan unit 600 family inet address
192.168.1.1/24, and then vlans vlan600 l3-interface vlan.600.

Matt Freitag
Network Engineer I
Information Technology
Michigan Technological University
(906) 487-3696 <%28906%29%20487-3696>
https://www.mtu.edu/
https://www.it.mtu.edu/

On Tue, Jul 5, 2016 at 2:51 PM, Josh Reynolds  wrote:

> Thanks Hugo, I'll try and give that a shot.
>
> So basically setup an ethernet-switching interface on unit 0, port
> mode trunk, native vlan as the current access vlan, member list
> includes the new vlan? I think I'm confused about how I would assign
> an RVI to this in that state.
>
> Do you have a quick example config I might be able to work off of?
>
> Thank you!
>
> On Tue, Jul 5, 2016 at 1:32 PM, Hugo Slabbert  wrote:
> >
> > On Tue 2016-Jul-05 13:23:38 -0500, Josh Reynolds 
> > wrote:
> >
> >> EX4500
> >
> >
> > This would be done with flexible-ethernet-services on MX, but I don't
> > believe it's supported to mix L2 and L3 on the same port on the EX4500.
> > We've tried that on 4550, and you can't mix family ethernet-switching
> with
> > e.g. vlan-tagging, which is what you would use for your L3 unit.
> >
> > You could change the interface into a trunk, run your existing access
> vlan
> > as native, and create an RVI for your L3 interface, but that may or may
> not
> > cut it depending on what you need that L3 interface for.
> >
> >
> > --
> > Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
> > pgp key: B178313E   | also on Signal
> >
> >>
> >> On Tue, Jul 5, 2016 at 1:20 PM, Hugo Slabbert  wrote:
> >>>
> >>>
> >>> On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds  >
> >>> wrote:
> >>>
>  Hello,
> 
>  I'm sure this is a fairly basic question, but I'm having trouble
>  finding a solution.
> 
>  I have a port that is currently an ethernet switching port, set in
>  access mode that is tagging a vlan for upstream. This works fine. What
>  I'd like to do, is add a sub interface on the master port (say, unit
>  600 / vlan 600) that is a tagged/routed interface.
> 
>  I've tried to do this a couple of ways now, and every time I seem to
>  get thrown a different error.
> 
>  Anybody have any tips?
> >>>
> >>>
> >>>
> >>> Support for this varies depending on what platform you are using.  You
> >>> haven't told us what equipment you're talking about.
> >>>
>  Thanks :)
> ___
> 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] mixed interface, switching + routed

[Josh Reynolds]

Thanks Hugo, I'll try and give that a shot.

So basically setup an ethernet-switching interface on unit 0, port
mode trunk, native vlan as the current access vlan, member list
includes the new vlan? I think I'm confused about how I would assign
an RVI to this in that state.

Do you have a quick example config I might be able to work off of?

Thank you!

On Tue, Jul 5, 2016 at 1:32 PM, Hugo Slabbert  wrote:
>
> On Tue 2016-Jul-05 13:23:38 -0500, Josh Reynolds 
> wrote:
>
>> EX4500
>
>
> This would be done with flexible-ethernet-services on MX, but I don't
> believe it's supported to mix L2 and L3 on the same port on the EX4500.
> We've tried that on 4550, and you can't mix family ethernet-switching with
> e.g. vlan-tagging, which is what you would use for your L3 unit.
>
> You could change the interface into a trunk, run your existing access vlan
> as native, and create an RVI for your L3 interface, but that may or may not
> cut it depending on what you need that L3 interface for.
>
>
> --
> Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
> pgp key: B178313E   | also on Signal
>
>>
>> On Tue, Jul 5, 2016 at 1:20 PM, Hugo Slabbert  wrote:
>>>
>>>
>>> On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds 
>>> wrote:
>>>
 Hello,

 I'm sure this is a fairly basic question, but I'm having trouble
 finding a solution.

 I have a port that is currently an ethernet switching port, set in
 access mode that is tagging a vlan for upstream. This works fine. What
 I'd like to do, is add a sub interface on the master port (say, unit
 600 / vlan 600) that is a tagged/routed interface.

 I've tried to do this a couple of ways now, and every time I seem to
 get thrown a different error.

 Anybody have any tips?
>>>
>>>
>>>
>>> Support for this varies depending on what platform you are using.  You
>>> haven't told us what equipment you're talking about.
>>>
 Thanks :)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mixed interface, switching + routed

[Hugo Slabbert]

On Tue 2016-Jul-05 13:23:38 -0500, Josh Reynolds  wrote:


EX4500


This would be done with flexible-ethernet-services on MX, but I don't 
believe it's supported to mix L2 and L3 on the same port on the EX4500.  
We've tried that on 4550, and you can't mix family ethernet-switching with 
e.g. vlan-tagging, which is what you would use for your L3 unit.


You could change the interface into a trunk, run your existing access vlan 
as native, and create an RVI for your L3 interface, but that may or may not 
cut it depending on what you need that L3 interface for.


--
Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal



On Tue, Jul 5, 2016 at 1:20 PM, Hugo Slabbert  wrote:


On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds 
wrote:


Hello,

I'm sure this is a fairly basic question, but I'm having trouble
finding a solution.

I have a port that is currently an ethernet switching port, set in
access mode that is tagging a vlan for upstream. This works fine. What
I'd like to do, is add a sub interface on the master port (say, unit
600 / vlan 600) that is a tagged/routed interface.

I've tried to do this a couple of ways now, and every time I seem to
get thrown a different error.

Anybody have any tips?



Support for this varies depending on what platform you are using.  You
haven't told us what equipment you're talking about.


Thanks :)


signature.asc
Description: Digital signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mixed interface, switching + routed

[Josh Reynolds]

EX4500

On Tue, Jul 5, 2016 at 1:20 PM, Hugo Slabbert  wrote:
>
> On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds 
> wrote:
>
>> Hello,
>>
>> I'm sure this is a fairly basic question, but I'm having trouble
>> finding a solution.
>>
>> I have a port that is currently an ethernet switching port, set in
>> access mode that is tagging a vlan for upstream. This works fine. What
>> I'd like to do, is add a sub interface on the master port (say, unit
>> 600 / vlan 600) that is a tagged/routed interface.
>>
>> I've tried to do this a couple of ways now, and every time I seem to
>> get thrown a different error.
>>
>> Anybody have any tips?
>
>
> Support for this varies depending on what platform you are using.  You
> haven't told us what equipment you're talking about.
>
>> Thanks :)
>
>
> --
> Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
> pgp key: B178313E   | also on Signal
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

Re: [j-nsp] mixed interface, switching + routed

[Hugo Slabbert]

On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds  wrote:


Hello,

I'm sure this is a fairly basic question, but I'm having trouble
finding a solution.

I have a port that is currently an ethernet switching port, set in
access mode that is tagging a vlan for upstream. This works fine. What
I'd like to do, is add a sub interface on the master port (say, unit
600 / vlan 600) that is a tagged/routed interface.

I've tried to do this a couple of ways now, and every time I seem to
get thrown a different error.

Anybody have any tips?


Support for this varies depending on what platform you are using.  You 
haven't told us what equipment you're talking about.



Thanks :)


--
Hugo Slabbert   | email, xmpp/jabber: h...@slabnet.com
pgp key: B178313E   | also on Signal


signature.asc
Description: Digital signature
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp

[j-nsp] mixed interface, switching + routed

[Josh Reynolds]

Hello,

I'm sure this is a fairly basic question, but I'm having trouble
finding a solution.

I have a port that is currently an ethernet switching port, set in
access mode that is tagging a vlan for upstream. This works fine. What
I'd like to do, is add a sub interface on the master port (say, unit
600 / vlan 600) that is a tagged/routed interface.

I've tried to do this a couple of ways now, and every time I seem to
get thrown a different error.

Anybody have any tips?

Thanks :)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp