Add to that, you can use a native vlan.
... unit 0 family ethernet-switching native-vlan-id # You can use the symbolic
name, too.
... and when you configure the vlan, if you want an RVI, use
set vlans VLAN-NAME l3-interface vlan.{vlan_id}, then configure the
vlan subinterface:
set interfaces vlan.{vlan_id} family inet ...
port-mode trunk is the default in family ethernet-switching (which can only be
on unit 0).
You can also use vlan-tagging and multiple units with distinct vlan-ids,
but you cannot also switch that vlan if you use that method - and all
vlans would need to be tagged.
I don't know whether this answers the original question?
Chris
>>> Jonathan Lassoff <j...@thejof.com> 12/23/09 2:30 PM >>>
Excerpts from Malte von dem Hagen's message of Wed Dec 23 10:23:45 -0800 2009:
> what exactly do you want to do? It's not yet clear to me.
>
> Anyway, you seem to mix up "vlan-tagging", which is a JunOS-Option for
> L3-ports,
> and "port-mode trunk", which does quite the same for L2-ports (below "family
> ethernet-switching"). On the EX, you can of course configure a trunk-port with
> just one VLAN, if that's what you want do do.
This is the right way to configure 802.1Q trunks on EX'es.
For example, from an EX4200:
------------------------------------------------------
j...@ex1.sfo2> show configuration interfaces xe-0/1/0
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members [ foo bar ];
}
}
}
------------------------------------------------------
--j
_______________________________________________
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
