You need to consider each zone to be an individual host with is own IP. Share means it uses the same NIC card to connect to the internet. The following is the RAW network output (ifconfig -a ) from the global zone (dione)  and comparing it with the same output for the local zone (dione-dev) to show you what is going on. Note the "zone" parameter in the output of the global zone, but it is missing in the local zone ouput:
------------------------------------------------------------------------------------------------------

ifconfig:
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    zone dione-prod
    inet 127.0.0.1 netmask ff000000
lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    zone dione-dev
    inet 127.0.0.1 netmask ff000000
eri0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 172.166.11.202 netmask ffffff00 broadcast 172.166.11.255
    ether 0:3:ba:14:c0:df
eri0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    zone dione-prod
    inet 172.166.11.205 netmask ffffff00 broadcast 172.166.11.255
eri0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    zone dione-dev
    inet 172.166.11.206 netmask ffffff00 broadcast 172.166.11.255

eri0:3: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 172.166.11.208 netmask ffffff00 broadcast 255.255.255.255


This is the ouput from the local zone (dione-dev)

ifconfig:
lo0:2: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
    inet 127.0.0.1 netmask ff000000
eri0:2: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
    inet 172.166.11.206 netmask ffffff00 broadcast 172.166.11.255


Hopefully this will make things clearer to you.

Ava Zhang wrote:
Hi all,

I followed the instruction "Q: How do I create a zone?" in http://www.opensolaris.org/os/community/zones/faq/#sa_create, created a zone named zone1.
But zone1 can't boot, it is said some error about IP address. My system is s10u5_b02 X86.

I want to use shared-IP mode to configure zone1, because I have only one NIC.
Could you give me some hints to configure it?

Here is the detailed information about my system:
--------------------------------------------------
bash-3.00# cat /etc/release
                        Solaris 10 5/08 s10x_u5wos_02 X86
           Copyright 2007 Sun Microsystems, Inc.  All Rights Reserved.
                        Use is subject to license terms.
                           Assembled 12 November 2007
bash-3.00# id
uid=0(root) gid=0(root)
bash-3.00# zonecfg -z zone1
zonecfg:zone1> info
zonename: zone1
zonepath: /zone/zone1
brand: native
autoboot: true
bootargs:
pool:
limitpriv:
scheduling-class:
ip-type: shared
inherit-pkg-dir:
        dir: /lib
inherit-pkg-dir:
        dir: /platform
inherit-pkg-dir:
        dir: /sbin
inherit-pkg-dir:
        dir: /usr
net:
        address: 129.158.215.197    #<----Here IP address is my global zone's IP.
        physical: bge0
zonecfg:zone1>
bash-3.00# zoneadm -z zone1 boot
zoneadm: zone 'zone1': bge0:1: could not bring network interface up: address in
use by zone 'global': Cannot assign requested address
zoneadm: zone 'zone1': call to zoneadmd failed
bash-3.00#
--------------------------------------------------



Thanks
--Ava

_______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org

--



Michael Barto
Software Architect

LogiQwest Circle
LogiQwest Inc.
16458 Bolsa Chica Street, # 15
Huntington Beach, CA  92649
http://www.logiqwest.com/

    [EMAIL PROTECTED]
Tel:  714 377 3705
Fax: 714 840 3937
Cell: 714 883 1949

'tis a gift to be simple
This e-mail may contain LogiQwest proprietary information and should be treated as confidential.
_______________________________________________
zones-discuss mailing list
zones-discuss@opensolaris.org

Reply via email to