Here is what I do with multiple nodes and vlans. Including smartos + linux kvm hosts.
https://www.mail-archive.com/smartos-discuss@lists.smartos.org.email.enqueue.archive.listbox.com/msg01112.html The GZ interface will just act like a bridge and vmadm will plumb the VLAN tagged interface without much hassle. On 24 August 2016 at 09:10, Evan Rowley <[email protected]> wrote: > Help, please > > I have a L3 switch that has some VLANs on it. I would like for several of > my KVM VMs that are distributed across 3 SmartOS nodes to all have their > primary VNIC on VLAN 101. > > Each SmartOS node has a dual intel NIC. The admin interface is on igb0 and > I would like to trunk VLAN 101 on igb1. > > Based on the "Managing NICs" page of the SmartOS Wiki, the following seems > to get a global zone connected to VLAN 101. > > dladm create-vnic -l igb1 -v 101 v101n > ifconfig v101n plumb > ifconfig v101n inet 10.170.153.5 netmask 255.255.255.0 up > > While it is good to see that I can ping the 10.170.153.1 gateway from the > global zone, this doesn't solve the problem for my VMs. In fact. I don't > want my SmartOS nodes to be reachable from VLAN 101 - only the KVM VMs > should be reachable. > > My understanding of crossbow network virtualization is lacking, so right > now I am lost on how to implement this on vanilla SmartOS. What should > happen between the VMs VNICs and VLAN 101 is a mystery to me. > > > -- > - EJR > *smartos-discuss* | Archives > <https://www.listbox.com/member/archive/184463/=now> > <https://www.listbox.com/member/archive/rss/184463/25241303-ebebecbc> | > Modify > <https://www.listbox.com/member/?&;> > Your Subscription <http://www.listbox.com> > ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
