On May 21, 2009, at 11:38 PM, Narendra Kumar.S.S wrote:

Here below is the sysidcfg of NGZ:

cat /etc/sysidcfg:
system_locale=C
terminal=xterms
security_policy=NONE
timezone=US/Eastern
nfs4_domain=east.sun.com
root_password=rJSJNt0RfvMy6
network_interface=vnic0 {
primary

They shouldn't be using the "primary" option here, which should only be used with multiple network_interface entries, see sysidcfg(4).


hostname=mathesar-z1
ip_address=10.0.1.100
netmask=255.255.255.0
default_route=NONE
protocol_ipv6=yes
}

name_service=NONE

They haven't tried to use PRIMARY for network_interface.
I think, if PRIMARY is used, it will take the first probed physical interface which could be e1000g0. If they want vnic0 to be Primary interface, then they have to specify network_interface as vnic0.

In the case of a non-global zone it will be the interface which was assigned to the zone, so in this case vnic0. So instead of the above they could remove the "primary" option and specify "PRIMARY" interface instead of vnic0 as follows:

network_interface=PRIMARY {
        hostname=mathesar-z1
        ip_address=10.0.1.100
        netmask=255.255.255.0
        default_route=NONE
        protocol_ipv6=yes
}

See also Steffen's blog entry at http://blogs.sun.com/stw/entry/crossbow_is_delivered_traveling_vnics for an example showing how to use sysidcfg with VNICs and zones.

Nicolas.

--
Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc.
nicolas.dr...@sun.com - http://blogs.sun.com/droux

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

Reply via email to