Quote:
Originally Posted by
hicksd8
Apologies if I'm about to state the obvious stuff that you already know but let's cover a few facts here.............
Don't worry about stating the obvious, i'm not familiar with zones at all. Another guy set up the zone and we are learning as we go.
Quote:
The branded zone can share a network interface with the global zone or it can be configured to have exclusive use of an interface. It would seem that whatever interface the branded zone is requesting at boot time, it is requesting exclusivity and the global zone is already using it so an error results.
I would suggest that you use zonecfg to list what interfaces the global and branded zones think you've got and reconfigure to eliminate conflict.
zonecfg -z zone-s9 info shows:
net:
address: 192.168.82.197
pysical: nxge0
defrouter not specified
net:
address: 192.168.0.7
pysical: nxge1
defrouter not specified
net:
address: 127.0.0.1
pysical: lo0
defrouter not specified
Ifconfig -a (in global) shows:
lo0: blah blah blah inet 127.0.0.1 blah
nxge0: blah blah blah 192.168.82.180
nxge1: blah blah blah 192.168.0.5
nxge0: blahv6 blahv6 ::1/128
nxge:0:1: blahv6 blahv6 fe80::221:28ff:fe3c
There is no lo0:2 listed in either.
Quote:
Another thought is that Solaris decides what interfaces to configure by the existence of /etc/hostname.<interface> files (eg. /etc/hostname.nxge0).
You haven't said whether your branded zone is on its own filesystem or not but if you can get at it then look for these file(s). Renaming them temporarily should stop Solaris trying to configure the network interfaces and therefore get the system on its feet. (Easier to troubleshoot once the system is up???) You could also look at /etc/hostname.<interface> files on the global and see what that thinks its got.
No it is not a separate fs. I tried renaming the zone hostname files and the boot still failed. Were you meaning i should rename the global hostname files???
Quote:
Hope that helps.
---------- Post updated at 12:57 PM ---------- Previous update was at 12:21 PM ----------
Also, you didn't say how you got into this position. What command(s) did you use to try and configure the interfaces?
I had done an ifconfig while in the zone but the other admin said i should do the add trhough the zonecfg command. I backed out then tried the "add net" command. we didn't commit the first time so we did it again with the commit and attempted to restart the zone. It failed.
Quote:
If you think that you messed up your zone configuration you could try restoring everything under /etc/zones on global. This will put your zone config back to the way it was. (Rename the existing zones directory, don't delete anything)
---------- Post updated at 10:19 AM ---------- Previous update was at 08:46 AM ----------
*** FIX ***
In the global /etc/zones there is an xml file zone-s9.xml. This file list the zone information including the network interfaces. I tried moving the file but that caused the zone to be NOT CONFIGURED. I deleted the 3 interface lines instead and the zone came up fine. After adding the interfaces we knew were good we added an ip attached to lo. The new lo came up as lo0:1 and the loopback (127.0.0.1) interface was declared as lo0:2. Each time i added another lo connection the default loopback was incremented so it was always the last lo interface.
Thanks for the help.