On 8/18/15 19:59 , Gavin Ang wrote: > My company wants to move to virtualized environment from its current > physical environment - total about 50 vms on 12 hosts. Need to have HA > capability to ensure that the system keeps chugging along even if the HW > fails. We are going to repurpose some of the compute HW with SmartOS Hosts > and add some new networking hardware for this. It seems like VLAN > architecture on the network with tagged frames and trunking might do the > trick, but the literature on this is quite confusing on actually how to > implement this: > > Network requirements: > > 1. Need to have multiple network zones (DMZ, App, Db, Storage, Management > etc)
I presume these are different physical subnets on different VLANs? > 3. Existing FW/Router is a HA set operating in active/passive mode with auto > failover (Sonicwall 3600) Presumably you're expecting hosts to do this using LACP? > 4. VM's from any host should be able to be assigned into any network zone, > and have connectivity to another VM in another zone (eg Internet -> Web VM > (DMZ) -> DB VM (DB zone) This should be rather simple to do. > We will purchase 2 new switches for this, but question is which one, and > what features do I need to achieve all the above. Seems like a layer 2 > switch is sufficient, and I would like to avoid complications like adding > Open vSwitch (do I have to have this?) No, all the functionality that you need is built into the operating system. You don't need additional software to do anything that you'd like to do. > We intend to bond the 2 physical NICs at the host level and connect the > NIC's separately to each switch, then configure the VLAN to span the 2 > switches for HA. Is the SmartOS link aggregation feature used for this? > Could not find any other documentation. How would the vswitching (vmware > equivalent) need to be configured? So, assuming the answers to the questions above are basically, yes each of the different network domains is its own L3 IP subnet on its own VLAN and you're using LACP to do the bonding, then here are the steps you would do: 1) Set up link aggregations, following https://wiki.smartos.org/display/DOC/Managing+NICs#ManagingNICs-LinkAggregationsintheGlobalZone 2) Use a single networking tag for everything, the default 'admin' tag should be fine. 3) Create your VMs, using different IP subnets and VLAN tags. That's it. There's no need for you to create logical bridges or switches, the operating system takes care of all of that for you. See Nicholas Lee's e-mail on the subject for more information. 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
