> This won't work. Each VLAN-tagged NIC is viewed as a separate
> link, or the physical entity you can assign to an exclusive zone,
> and thus only to one zone. You will either need to use two
> interfaces each with a tag of 32 or different VLAN tags, or
> shared zones.
>
> This will be do-able when VNICs are delivered into Nevada. But
> instead of using e1000g32000 you will use vnicXYZ where you
> determine XYZ when you create the VNIC with dladm.
>
> Steffen
>
Ah, okay. can multiple non-global zones share the same IP instance,
but have that instance be different to the global zone... eg:
Global, zone1, zone2 all on vlan 1 using e1000g1000
zone3 and zone4 on vlan 2 using e1000g20000
zonecfg -z zone3
zone3> set ip-type=exclusive
zone3> add net
zone3> set physical=e1000g2000
zone3> end
zonecfg -z zone4
zone4> add net
zone4> set address=172.20.1.65/27
zone4> set physical=e1000g2000
zone4> end
and so on?
Alternatively, is it possible to have the following configuration
----------------------- ----------------------
------ -------- ------ ------
Global zone1 zone2 zone3
------ -------- ------ -------
shared instance shared instance
------------------------ -----------------------
e1000g0 e1000g1
Assume for the sake of argument that the above does not make
use of vnics as vnics aren't available in production (eg s10uN)
yet.
--
Coy Hile
[EMAIL PROTECTED]
_______________________________________________
networking-discuss mailing list
[email protected]
