On 8/23/16 14:10 , Evan Rowley 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.
Hi Evan, So if you want your KVM VMs to basically have a VNIC whose packets are always tagged with the VLAN 101, all you need to do is specify the vlan_id 101 in the JSON definition for the network. There's nothing that you need to do in the GZ, just use the nic tag that corresponds to the physical device that the packets need to travel over. Basically creating a VNIC or VLAN in the GZ is only needed if the GZ needs to access it itself. Robert ------------------------------------------- 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
