[j-nsp] mixed interface, switching + routed

Josh Reynolds josh at kyneticwifi.com
Tue Jul 5 14:51:26 EDT 2016


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 <hugo at slabnet.com> wrote:
>
> On Tue 2016-Jul-05 13:23:38 -0500, Josh Reynolds <josh at kyneticwifi.com>
> 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: hugo at slabnet.com
> pgp key: B178313E   | also on Signal
>
>>
>> On Tue, Jul 5, 2016 at 1:20 PM, Hugo Slabbert <hugo at slabnet.com> wrote:
>>>
>>>
>>> On Tue 2016-Jul-05 13:17:52 -0500, Josh Reynolds <josh at kyneticwifi.com>
>>> 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 :)


More information about the juniper-nsp mailing list