In my setup I have tagged an "external" NIC on the server like so:
[root@node7 ~]# cat /usbkey/config | grep external
external_nic=0:1e:67:9f:dd:da
Then setup the interfaces in the vm setup, For example, LX/Ubuntu zone:
[root@node7 ~]# vmadm get 221c95b6-dd44-42bc-91c3-5e1c218d2880 | json nics
[
{
"interface": "net0",
"mac": "32:d9:2c:69:d6:fc",
"vlan_id": 216,
"nic_tag": "external",
"gateway": "192.168.10.1",
"ip": "192.168.10.105",
"netmask": "255.255.255.0",
"primary": true
}
]
and this KVM system on another node:
[root@node6 ~]# vmadm get aaa49efe-994b-4e8a-ab2c-8b67a03bc1d0 | json nics
[
{
"interface": "net0",
"mac": "d2:86:4f:40:43:a5",
"vlan_id": 229,
"nic_tag": "external",
"gateway": "X.X.X.X",
"ip": "X.X.X.X",
"netmask": "255.255.255.224",
"model": "virtio",
"primary": true
},
{
"interface": "net1",
"mac": "22:09:a4:37:7f:0c",
"vlan_id": 216,
"nic_tag": "external",
"ip": "192.168.10.15",
"netmask": "255.255.255.0",
"model": "virtio"
},
{
"interface": "net2",
"mac": "b2:96:ff:c5:0d:65",
"vlan_id": 251,
"nic_tag": "storage",
"ip": "172.29.220.102",
"netmask": "255.255.255.0",
"model": "virtio"
}
]
Note the different vlan tags for different subnets.
This also allows me to setup my linux/kvm VMs on the same basis.
May not be the most efficient, but I find it logically easy to manage.
Management access to the nodes is via a different NIC, but you could
probably use the same NIC if you had a different tag/same MAC in
/usbkey/config.
Nicholas
On 19 August 2015 at 14:59, Gavin Ang <[email protected]> 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)
>
> 2. Each physical host only has 2 physical NIC's
>
> 3. Existing FW/Router is a HA set operating in active/passive mode with
> auto failover (Sonicwall 3600)
>
> 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)
>
> 5. Cost effective, easy to maintain network
>
> 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?)
>
> 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?
>
> Thanks,
>
>
>
>
>
> *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
