My apologies for the lateness of this summary - work has been interesting.
The solution on the routing side was to plumb and fully activate two nics in
the global zone for the two subnets the whole root zones would be active in.
For the zones themselves each nic assigned to a zone was plumbed
Matthew Taylor wrote:
Apologies if my search-fu failed me and the answer is out there.
I have a box with 1 hme and 8 qfe interfaces. I would normally used
exclusive IP zones, but that is not possible with these non-gldv3 driven
interfaces, so I am forced to use shared IP zones.
hme0
Apologies if my search-fu failed me and the answer is out there.
I have a box with 1 hme and 8 qfe interfaces. I would normally used exclusive
IP zones, but that is not possible with these non-gldv3 driven interfaces, so I
am forced to use shared IP zones.
hme0 is configured on the host
Matthew Taylor wrote:
Do you know if plumbing all the qfe's without assigning an IP address will
persist across reboots of the base system? Never tried that on Solaris
(works on LINUX iirc, but you have to enter the info in a script).
It will not persist. An empty /etc/hostname.qfe0 will
Do you know if plumbing all the qfe's without assigning an IP address will
persist across reboots of the base system? Never tried that on Solaris (works
on LINUX iirc, but you have to enter the info in a script).
This message posted from opensolaris.org
Matthew Taylor wrote:
Thank you, and to those who replied off line as well. I will try it out and
report back on my success (or not) in the morning.
It does strike me that this should be in the docs. I have gone through
817-1592-15, the Zones admin guide, and find little to nothing on
James Carlson wrote:
Matthew Taylor writes:
Do you know if plumbing all the qfe's without assigning an IP address will
persist across reboots of the base system? Never tried that on Solaris
(works on LINUX iirc, but you have to enter the info in a script).
This will make plumbing persist
