Re: [j-nsp] Routed VLAN Interfaces on MX

> Almost forgot! Be sure to check the L2 and L3 MTUswhen you turn on vlan > tagging. Most of the time JunOS will not help you out by correctly bumping > the L2 MTU like Cisco. "Correctly"? Some of us believe that JunOS is doing exactly the right thing. I find the JunOS way much easier to

Re: [j-nsp] Routed VLAN Interfaces on MX

All very good suggestions. Since I only need L3 termination, I think this is the easiest thing to do. Thanks! On Fri, Nov 13, 2015 at 4:42 PM, Chuck Anderson wrote: > Right, you aren't required to do bridging and IRB if all you want is a > layer 3 termination: > > ae0 { >

Re: [j-nsp] Routed VLAN Interfaces on MX

And don't forget to allocate linecard memory for LAG interfaces: set chassis aggregated-devices ethernet device-count 8 8 is a safe number. Don't overallocate by inflating "the device-count" - once allocated, this memory is not accessible to other linecard processes if Your actual device

Re: [j-nsp] Routed VLAN Interfaces on MX

You also need to configure the physical interface(s) in the LAG: interfaces { xe-x/y/z { gigether-options { 802.3ad ae0; } } } interfaces { xe-x/y/w { gigether-options { 802.3ad ae0; } } } ... Otherwise, it looks fine. On

Re: [j-nsp] Routed VLAN Interfaces on MX

Right, you aren't required to do bridging and IRB if all you want is a layer 3 termination: ae0 { flexible-vlan-tagging; encapsulation flexible-ethernet-services; unit 41 { vlan-id 41; family inet { address 1.1.1.2/30; } } } You can do the same

Re: [j-nsp] Routed VLAN Interfaces on MX

in your bridge-domains stanza, add 'domain-type bridge' and I think you're golden. -b On Fri, Nov 13, 2015 at 1:12 PM, Josh Baird wrote: > Hi, > > I apologize for the basic question as I'm a new Junos user. I'm attempting > to convert the following basic config from a

[j-nsp] Routed VLAN Interfaces on MX

Hi, I apologize for the basic question as I'm a new Junos user. I'm attempting to convert the following basic config from a Cisco NPE-G1: interface GigabitEthernet0/3 desc 'Physical link to EX' interface GigabitEthernet0/3.41 encapsulation dot1q ip address 1.1.1.2/30 On the MX, I am

Re: [j-nsp] Routed VLAN Interfaces on MX

If you don't need to switch the subintf at all you can just do... set int ae0 flexible-vlan-tagging set int ae0 . set int ae0 unit 41 vlan-id family inet instead of doing encap vlan-bridge on the unit 41 and all the other related bridge-domain stuff On Fri, Nov 13, 2015 at 1:12 PM,

Re: [j-nsp] Routed VLAN Interfaces on MX

On Friday, November 13, 2015, Michael Loftis wrote: > If you don't need to switch the subintf at all you can just do... > set int ae0 flexible-vlan-tagging > set int ae0 . > set int ae0 unit 41 vlan-id family inet > > instead of doing encap vlan-bridge on the unit 41