[j-nsp] Ex4200 no native vlan, without fam. eth-switching. ?

[Peter Krupl]

Hi,

Yes we are running CCC's on the EX4200's. 

,Peter


> -----Original Message-----
> From: Michael Damkot > Sent: 23. September, 2010 13:56
> To: Peter Krupl
> Cc: juniper-nsp at puck.nether.net
> Subject: Re: [j-nsp] Ex4200 no native vlan, without fam. eth-switching. ?
> 
> You're running CCC on the ex switches, or the devices On the N. Side?
> 
> Michael Damkot
> 
> On Sep 23, 2010, at 7:46, Peter Krupl <Peter.Krupl at siminn.dk> wrote:
> 
> > Hi Micael,
> >
> > I sent a simplified version of my config. The reason we are using "vlan-tagging",
> > is that we are doing a lot of CCC's on the boxes. So ethernet switching is not an
> option for us.
> >
> > Kind Regards,
> > Peter
> >
> >> -----Original Message-----
> >> From: Michael Damkot > Sent: 23. September, 2010 13:33
> >> To: Peter Krupl
> >> Cc: juniper-nsp at puck.nether.net
> >> Subject: Re: [j-nsp] Ex4200 no native vlan, without fam. eth-switching. ?
> >>
> >> There's a switch to make it the native VLAN, but I believe you should not be
> using
> >> the "vlan-tagging' configuration method with ex series switches per Juniper 'best
> >> practices'
> >>
> >> I think for best practices, you do it something like this:
> >>
> >> Configure the VLANS:
> >>
> >> set vlans lab-team vlan-id 300
> >> set vlans lab-team l3-interface vlan.300
> >> set vlans qa-tester vlan-id 301
> >> set vlans qa-tester l3-interface vlan.301
> >> set vlans contractors vlan-id 302
> >> set vlans contractors l3-interface vlan.302
> >> set vlans ive-cluster vlan-id 330
> >> set vlans ive-cluster l3-interface vlan.330
> >>
> >> Configure the L3 Interfaces for the respective VLANS (you have to do this first if
> >> you commit between each block of config)
> >>
> >> set interfaces vlan unit 300 family inet address xx.xx.60.2/24 vrrp-group 0
> virtual-
> >> address xx.xx.60.1
> >> set interfaces vlan unit 300 family inet address xx.xx.60.2/24 vrrp-group 0
> priority
> >> 250
> >> set interfaces vlan unit 300 family inet address xx.xx.60.2/24 vrrp-group 0
> accept-
> >> data
> >> set interfaces vlan unit 300 family inet6 address DEAD:BEEF:300:1001::1/64
> >> set interfaces vlan unit 301 family inet address xx.xx.61.2/24 vrrp-group 1
> virtual-
> >> address xx.xx.61.1
> >> set interfaces vlan unit 301 family inet address xx.xx.61.2/24 vrrp-group 1
> priority
> >> 250
> >> set interfaces vlan unit 301 family inet address xx.xx.61.2/24 vrrp-group 1
> accept-
> >> data
> >> set interfaces vlan unit 301 family inet6 address DEAD:BEEF:300:1002::1/64
> >> set interfaces vlan unit 302 family inet address xx.xx.62.2/23 vrrp-group 2
> virtual-
> >> address xx.xx.62.1
> >> set interfaces vlan unit 302 family inet address xx.xx.62.2/23 vrrp-group 2
> priority
> >> 250
> >> set interfaces vlan unit 302 family inet address xx.xx.62.2/23 vrrp-group 2
> accept-
> >> data
> >> set interfaces vlan unit 302 family inet6 address DEAD:BEEF:300:1003::1/64
> >> set interfaces vlan unit 330 description "Default Inside Interface for IVE"
> >> set interfaces vlan unit 330 family inet address xx.xx.59.242/28 vrrp-group 30
> >> virtual-address xx.xx.59.241
> >> set interfaces vlan unit 330 family inet address xx.xx.59.242/28 vrrp-group 30
> >> priority 250
> >> set interfaces vlan unit 330 family inet address xx.xx.59.242/28 vrrp-group 30
> >> accept-data
> >>
> >> Then configure the physical ports:
> >>
> >> set interfaces ge-4/0/4 description "To hrn-core-ive-01 inside interface"
> >> set interfaces ge-4/0/4 unit 0 family ethernet-switching port-mode trunk
> >> set interfaces ge-4/0/4 unit 0 family ethernet-switching vlan members lab-team
> >> set interfaces ge-4/0/4 unit 0 family ethernet-switching vlan members qa-tester
> >> set interfaces ge-4/0/4 unit 0 family ethernet-switching vlan members
> contractors
> >> set interfaces ge-4/0/4 unit 0 family ethernet-switching native-vlan-id ive-cluster
> >>
> >> NOTE: the vlan L3 interface correlates to the Unit under 'interfaces vlan' but
> they
> >> don't have to match...
> >>
> >>
> >> On Sep 23, 2010, at 03:58 , Peter Krupl wrote:
> >>
> >>> Hi Group,
> >>>
> >>> Can I realy be true that it is not possible to have both vlan tagged and
> untagged
> >> subinterfaces son the same
> >>> physical interface on the EX4200 without using "fam. eth-switching" ?
> >>>
> >>> I have the following configuration:
> >>>
> >>> set interfaces ge-0/0/10 vlan-tagging
> >>> set interfaces ge-0/0/10 unit 10 vlan-id 10
> >>> set interfaces ge-0/0/10 unit 10 family inet address 192.168.100.1/24
> >>> set interfaces ge-0/0/10 unit 20 vlan-id 20
> >>> set interfaces ge-0/0/10 unit 20 family inet address 192.168.101.1/24
> >>>
> >>> But what if I also would like to route traffic that is untagged on the same
> interface
> >> ?
> >>>
> >>>
> >>>
> >>> Kind Regards,
> >>> Peter Krüpl
> >>>
> >>>
> >>> _______________________________________________
> >>> juniper-nsp mailing list juniper-nsp at puck.nether.net
> >>> https://puck.nether.net/mailman/listinfo/juniper-nsp
> >