I forgot the members [ ... ] part and that caused the vlan to be down. But after I added the members line the vlan was up but I was not able to ping bettween the two J2320, so same result.
On Thu, Apr 8, 2010 at 4:24 PM, Chris Kawchuk <juniperd...@gmail.com> wrote: > Seems to work fine with me, without any declared interface. Make sure your > actual trunk port is "up". This is a config snippet from one of my SRX240s: > > ge-0/0/0 { > unit 0 { > family ethernet-switching { > port-mode trunk; > vlan { > members [ vlan-10 vlan-99 ]; > } > } > } > > > vlan { > unit 10 { > family inet { > address 10.20.0.1/30; > } > } > unit 99 { > family inet { > address 10.20.0.5/30; > } > } > } > > > vlans { > vlan-10 { > vlan-id 10; > l3-interface vlan.10; > } > vlan-99 { > vlan-id 99; > l3-interface vlan.99; > } > } > > > chr...@clgr01-fw03> show vlans > Name Tag Interfaces > default 1 > None > vlan-10 10 > ge-0/0/0.0* > vlan-99 99 > ge-0/0/0.0* > > chr...@clgr01-fw03> > > > > > - Chris. > > > > > On 2010-04-08, at 7:32 AM, Morten Isaksen wrote: > >> If I delete the interface section in the vlan stanza then the vlan is down. >> >> /Morten >> >> On Thu, Apr 8, 2010 at 3:23 PM, Chris Kawchuk <juniperd...@gmail.com> wrote: >>> Do not include the "ge-0/0/3" in each of your VLAN statements; as that >>> designates that port to be an access port per se. >>> >>> You just need to have this: >>> >>> vlans { >>> bgp { >>> vlan-id 12; >>> l3-interface vlan.12; >>> } >>> lan { >>> vlan-id 10; >>> l3-interface vlan.10; >>> } >>> wan { >>> vlan-id 11; >>> l3-interface vlan.11; >>> } >>> } >>> >>> JunOS assumes that you have some trunk ports... somewhere... (as you have >>> declared under the [interfaces ge-0/0/3] stanza) for these VLANs if there's >>> no "untagged ports" associated with them. >>> >>> Regards, >>> >>> - Chris. > > -- Morten Isaksen _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp