On 05/25/09 02:33, Narendra Kumar S.S wrote:
Steffen Weiberle wrote:
On 05/22/09 14:28, Nicolas Droux wrote:
On May 21, 2009, at 11:38 PM, Narendra Kumar.S.S wrote:
Here below is the sysidcfg of NGZ:
They shouldn't be using the "primary" option here, which should only
be used with multiple network_interface entries, see sysidcfg(4).
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:
See also Steffen's blog entry at
for an example showing how to use sysidcfg with VNICs and zones.
I have seen errors like this as well, and working on an example with
*two* interfaces, both VNICs, I come across this also. Have been
wondering where to look regarding sysidcfg and its long term use, and
whether to file a bug. And if so, under which category.
The category/subcategory will be: sysadmin/sysidtool under Solaris product.
Also, the second interface must have a default_route entry, even if it
is the same as that in the first (there is no router on the second
subnet, it is on an etherstub). Without that, the interface is plumbed
From your sysidcfg below: Is your interface name and hostname same?
As advised by Nicolas, please remove the word primary from within the
braces and see how it goes.
Yes, interface and hostname are the same, as I like the option to make
my interface names be ease to see where they are being used, now that we
can set the name.
Nicolas' advice applies if you you only configuring one interface. The
'primary' keyword is appropriate when configuring multiple, see
"Multiple Network Interfaces" in sysidcfg(4).
I must admit that I fail to see the value of the 'primary' keyword when
not using DHCP--this is a habit of mine. Either the process or the
documentation may need updating.
opensolaris2009.06# cat web1.sysidcfg
SunOS Release 5.11 Version snv_111a 64-bit
Copyright 1983-2009 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Reading ZFS config: done.
Mounting ZFS filesystems: (6/6)
web1 is not a valid network interface line 3 position 19
Creating new rsa public/private host key pair
Creating new dsa public/private host key pair
Configuring network interface addresses: web1 webp1.
web1 console login:
zones-discuss mailing list