Nicolas Droux wrote:
>
> On May 21, 2009, at 11:34 AM, Narendra Kumar.S.S wrote:
>
>> Hi,
>>
>> I am discussing a problem with a customer who is trying to configure
>> vnic in a NGZ thru sysidcfg.
>>
>> He is giving a sysidcfg file in which network_interface is
>> configured as vnic0.
>> So, the NGZ should create this vnic and configure this.
>>
>> Here is the information that they have given regarding the NGZ and
>> the interfaces:
>>
>> From global zone:
>>
>> $ zoneadm -z mathesar-z1 list -v
>> ID NAME STATUS PATH
>> BRAND IP 10 mathesar-z1 running
>> /export/home/zones/mathesar-z1 native excl $ ifconfig
>> -a lo0:
>> flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
>> index 1
>> inet 127.0.0.1 netmask ff000000 e1000g0:
>> flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu 1500 index 2
>> inet 10.8.57.93 netmask ffffff00 broadcast 10.8.57.255
>> ether 0:14:4f:20:82:24 lo0:
>> flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
>> index 1
>> inet6 ::1/128 e1000g0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu
>> 1500 index 2
>> inet6 fe80::214:4fff:fe20:8224/10 ether 0:14:4f:20:82:24
>> e1000g0:1: flags=2080841<UP,RUNNING,MULTICAST,ADDRCONF,IPv6> mtu 1500
>> index 2
>> inet6 2002:a08:39f0:1:214:4fff:fe20:8224/64
>> $ dladm show-vnic LINK OVER SPEED
>> MACADDRESS MACADDRTYPE VID
>> vnic0 e1000g1 1000 2:8:20:4f:b3:a6
>> random 0
>>
>> $ zonecfg -z mathesar-z1 info
>> zonename: mathesar-z1
>> zonepath: /export/home/zones/mathesar-z1
>> brand: native
>> autoboot: true
>> bootargs: pool: limitpriv: scheduling-class: ip-type: exclusive
>> hostid: inherit-pkg-dir:
>> dir: /lib
>> inherit-pkg-dir:
>> dir: /platform
>> inherit-pkg-dir:
>> dir: /sbin
>> inherit-pkg-dir:
>> dir: /usr
>> net:
>> address not specified
>> physical: vnic0
>> defrouter not specified
>>
>> $ zlogin mathesar-z1 ifconfig -a lo0:
>> flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232
>> index 1
>> inet 127.0.0.1 netmask ff000000 vnic0:
>> flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
>> inet 10.0.1.100 netmask ffffff00 broadcast 10.0.1.255
>> ether 2:8:20:4f:b3:a6 lo0:
>> flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252
>> index 1
>> inet6 ::1/128 vnic0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6>
>> mtu 1500 index 2
>> inet6 fe80::8:20ff:fe4f:b3a6/10 ether 2:8:20:4f:b3:a6
>> $ zlogin mathesar-z1 cat /etc/hostname.vnic0
>> mathesar-z1
>>
>> Now the problem that is observed is, during zlogin an error
>> message is getting printed.
>> The error message is: "vnic0 is not a valid network interface line
>> 7 position 19".
>
> According to the output above vnic0 seems to be configured in the
> non-global zone, is the configuration of vnic0 correct? Did you
> already check the contents of the sysidcfg config file?
>
> Did they try to specify the "PRIMARY" interface instead of "vnic0" in
> the sysidcfg config file? Did they try to assign the physical NIC (for
> example e1000g1) to the zone instead to see if they still get this
> error message?
>
> Nicolas.
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
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.
When zlogin -C is done, it goes thru the sysid phase.
At this stage, the vnic0 is not yet plumbed, right? (Please correct me
if my assumption is wrong)
Now, before configuring the interface specified for network_interface
keyword, it creates a list of all the available interfaces.
So, at this stage the vnic0 is not yet plumbed and hence it will not
make it to the list.
Because of this validation of the name vnic0 fails and the error message
is printed.
Do you think, this is the possible reason for the error?
Now, do we have any solution here?
Is it possible to plumb vnic0 during zone boot?
Is the responsibility of the boot code or zones code?
Regards,
Narendra
>
>
>
>>
>>
>> If you have any suggestion on possible workarounds or solutions,
>> please let me know.
>>
>> Regards,
>> Narendra
>>
>> _______________________________________________
>> crossbow-discuss mailing list
>> crossbow-discuss at opensolaris.org
>> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
>
