Joe Barbey writes:
> I would like to host a number of zones on a server, let's say an m4000,
> but I want those zones to be on a different subnet than the global. So
> far, no problem: use exclusive-IP. However, currently I don't have
> enough NICs to give one each to all zones.
Use VLANs. It'll work if you give each exclusive IP instance a
separate VLAN on an interface (or a small group of interfaces).
> One thought I had was a sort
> of mix of shared-IP and exclusive-IP. Give a couple of different zones
> the same NIC in exclusive-IP mode. I haven't tried it, but I'm fairly
> certain this won't work, as each zone will try to control the NIC itself.
No, that won't work. We discussed it during the development of the IP
Instances (exclusive stack) feature, but the project team considered
it to be too complex at least for the initial version. Exclusive is
just that: exclusive of all other zones on the system.
> My major concern is to get the global zone on one subnet, while the
> non-globals will be at least one other subnet, possibly others. Using
> shared-IP, I know we had routing issues. I can't remember if it was on
> the global side or the local, but I know there were issues. Perhaps
> this has been fixed in more recent releases?
As long as you have distinct destinations for the traffic, that can be
made to work with shared stack instances, but you're right that it's
always been a bit problematic. It wasn't the design center for the
original Kevlar/Zones project: all zones were expected to go on a
common set of subnets.
James Carlson, Solaris Networking <[EMAIL PROTECTED]>
Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
zones-discuss mailing list