Thanks for your help,
Let me summarize this:
- Shared IP has the advantage that the global zone fully administers the
network: zone don't have to (and even CAN'T) bother with it. There may be a
slight advantage performance wise.
- Exclusive IP with VNIC is needed for some features and enables ban
On 04/28/09 06:09, Vincent Boisard wrote:
Thanks for your help,
Let me summarize this:
- Shared IP has the advantage that the global zone fully administers the
network: zone don't have to (and even CAN'T) bother with it. There may
be a slight advantage performance wise.
Yes. I would expect
Hi.
I've got a routing issue with Solaris 10 Update 5 and I don't know if
I can solve it. Basically I've got a multihomed server:
enr...@server0:~$ ifconfig -a
lo0: flags=2001000849 mtu
8232 index 1
inet 127.0.0.1 netmask ff00
lo0:1: flags=2001000849
mtu 8232 index 1
zone zone
> The problem I have is when creating shared IP zones on another subnet,
> such as the 192.168.0.0/19: subnet 192.168.96.0/19 is unreachable and
> they cannot connet to the outside world through 192.168.96.1.
It can't work this way. Your zone on 192.168.0.0/19 will never see
192.168.96.1 because
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Christine.
Multi homing the router is an option we are considering and I'm waiting
for it to be assessed but unfortunately is not that obvious for us to
get it.
server0 is the global zone, indeed, and I thought I could use somehow
its packet-f
On Tue, Apr 28, 2009 at 6:09 AM, Vincent Boisard wrote:
> Thanks for your help,
>
> Let me summarize this:
>
> - Shared IP has the advantage that the global zone fully administers the
> network: zone don't have to (and even CAN'T) bother with it. There may be a
> slight advantage performance wise.
All,
We were trying to bring down a zone on a S10 U4 system and it ended up stuck
in the shutting_down state.
ID NAME STATUS PATH BRANDIP
74 zonetest-new shutting_down /zone/zonetest-new native
shared
The only process I see running i
+--
| On 2009-04-28 15:37:22, Derek McEachern wrote:
|
| We were trying to bring down a zone on a S10 U4 system and it ended up stuck
| in the shutting_down state.
|
| ID NAME STATUS PATH
Hi Jeff.
Thank you very much for sharing it with us. That's a very slick tool and
I was looking for something like this for quite some time now.
You just made our lives a lot easier.
We found 2 issues you should be aware of:
1. As this guy pointed out on your blog
(http://blogs.sun.com/JeffV
It's possible that it could be nfs mount related since the zone did have nfs
mounted fs's but they should have been umounted prior to shutting down the
zone. In any event I can no longer get into the zone to checkusing zlogin
and zlogin -C.
I tried Bryan's suggestion on looking for processes tha
Derek McEachern wrote:
> It's possible that it could be nfs mount related since the zone did
> have nfs mounted fs's but they should have been umounted prior to
> shutting down the zone. In any event I can no longer get into the
> zone to checkusing zlogin and zlogin -C.
>
> I tried Bryan's sugge
If its hung nfs mount you should be able to see it still mounted in
the /etc/mntab file in the global zone: grep nfs /etc/mntab. It will be
mounted under the zonepath. You should then be able to do a umount
-f / from the global zone and if you're really lucky the
zone will finish shutting down.
-
There were a bunch of nfs mounts listed in the /etc/mntab of the global
zone. I was able to umount them but zone is still hung up.
I tried killing the zoneadmd process and ran zoneadm halt again and it
started the zoneadmd back up but it didn't do anything.
Thanks to everyone for their suggestio
13 matches
Mail list logo
