Hi Chris, Solution:
Remove 'misc' from vlan members, but leave the native vlan id setting: http://kb.juniper.net/InfoCenter/index?page=content&id=KB17419&cat=EX_SERIES&actp=LIST Regards, Wojciech - Wojciech Owczarek On 20 Dec 2011, at 19:31, Chris Adams <[email protected]> wrote: > I've got a server connected to an EX4200 switch. Its port is in VLAN 9 > called "misc". All is well. The interface config looks like: > > unit 0 { > family ethernet-switching { > port-mode access; > vlan { > members misc; > } > } > } > > Now I want to enable IPMI on the server on a separate LAN segment. This > is done on the server hardware with a VLAN on the BMC; tagged traffic in > the specific VLAN (30, named "ipmi") is separated for IPMI (the server > OS never sees it), and the rest goes to the server. I want to keep VLAN > 9 untagged (so the OS sees it just the same as before). I tried: > > unit 0 { > family ethernet-switching { > port-mode trunk; > vlan { > members [ misc ipmi ]; > } > native-vlan-id 9; > } > } > > Now the IPMI LAN is active, but the packets to the server on VLAN 9 are > also tagged (so the server doesn't see them). It looks like > native-vlan-id only sets the VLAN for inbound untagged packets. How do > I get VLAN 9/misc packets sent untagged on this port? > -- > Chris Adams <[email protected]> > Systems and Network Administrator - HiWAAY Internet Services > I don't speak for anybody but myself - that's enough trouble. > _______________________________________________ > juniper-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/juniper-nsp _______________________________________________ juniper-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
