Hi, just played with the b105 (x86) in VirtualBox 2.1 to try the crossbow. The first thing that caused me some problems is that tutorials and documentations (even on http://opensolaris.org/os/project/crossbow) seems to be outdated (e.g.: there is no -d in dladm create-vnic, etc.). I tried to follow Sunay''s tutorial. I wanted to create a private network connecting several zones. But none of my zones have vnic plumbed when they get booted (have only lo interface). Also I cannot do it manually. This is how my system looks like: global# dladm show-etherstub LINK private_1 global# dladm show-vnic LINK OVER SPEED MACADDRESS MACADDRTYPE VID grid00 private_1 0 2:8:20:f:8c:9b random 0 grid01 private_1 0 2:8:20:18:c6:f9 random 0 grid02 private_1 0 2:8:20:ff:8f:99 random 0 ... grid10 private_1 0 2:8:20:e4:c1:cb random 0 test01 e1000g0 1000 2:8:20:ae:20:96 random 0 global# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 e1000g0: flags=201004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4,CoS> mtu 1500 index 2 inet 10.0.2.15 netmask ffffff00 broadcast 10.0.2.255 ether 8:0:27:95:df:f1 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 global# zonecfg -z grid02 export create -b set zonepath=/zones/grid02 set autoboot=false set ip-type=exclusive add inherit-pkg-dir set dir=/lib set dir=/platform set dir=/sbin set dir=/usr end add net set physical=grid02 end global# zoneadm -z grid02 boot global# zlogin grid02 grid02# ifconfig -a lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1 inet6 ::1/128 grid02# ifconfig grid02 plumb ifconfig: SIOCSLIFNAME for ip: grid02: Invalid argument Did I do something wrong? I''d expect that the vnics are plumbed once they are created via dladm create-vnic, but in my case ifconfig does not lists them at all. Is this expected? Thanks, Lubos.
> grid02# ifconfig grid02 plumb> ifconfig: SIOCSLIFNAME for ip: grid02: Invalid argument IP interfaces cannot have leading zeros. Try using the name "grid2" instead. Yes, it''s a bug that you were able to name a datalink with a leading zero. -- meem
Peter Memishian wrote:> > grid02# ifconfig grid02 plumb > > ifconfig: SIOCSLIFNAME for ip: grid02: Invalid argument > > IP interfaces cannot have leading zeros. Try using the name "grid2" > instead. Yes, it''s a bug that you were able to name a datalink with > a leading zero. > >Thanks Peter, but still after renaming the interfaces to vnic1 .. vnic10, they still do not automatically appear in the zones (I have only loopback interface). I can however zlogin to the zone and call ifconfig vnic1 plumb <IP/mask> up What seem strange to me is that even after I do so the vnics are not visible in the ifconfig -a output from the global zone. Is this expected? Do I have to plumb the interfaces in the zones myself and create necessary files (/etc/hostname.vnic1, ...) to keep my settings across reboots? I''d expect this to be done based on the net properties in the zone''s configuration. Regards, Lubos.
> Is this expected? Do I have to plumb the interfaces in the zones myself > and create necessary files (/etc/hostname.vnic1, ...) to keep my > settings across reboots? I''d expect this to be done based on the net > properties in the zone''s configuration. >Yes, thats expected. You have just assigned the interfaces to zones using ''zonecfg''. Once you login to zone you need to run ''ifconfig''. Further to persist the configuration across reboots you need to create those files as you would do in a global zone. HTH, ~Girish
Hi Lubos - I''m the technical writer who is working on the Crosbow system administration docs. The issue that you point out early in your post--that dladm create-vnic -d no longer works--is a known problem with the existing system administration docs posted on opensolaris/crossbow. As you know, that command has changed to dladm create-vnic -l. I''m in the process of updating the chapter "Configuring Virtual Networks" and hope to have an updated .pdf early next year. Thanks for reading our documentation and pointing this out. - Stephanie Brucker Senior Technical Writer -- This message posted from opensolaris.org
Lubos, Lubomir Petrik wrote:> Peter Memishian wrote: >> > grid02# ifconfig grid02 plumb >> > ifconfig: SIOCSLIFNAME for ip: grid02: Invalid argument >> >> IP interfaces cannot have leading zeros. Try using the name "grid2" >> instead. Yes, it''s a bug that you were able to name a datalink with >> a leading zero. >> >> > Thanks Peter, but still after renaming the interfaces to vnic1 .. > vnic10, they still do not automatically appear in the zones (I have only > loopback interface). I can however zlogin to the zone and call ifconfig > vnic1 plumb <IP/mask> upThat is expected behaviour.> What seem strange to me is that even after I do so the vnics are not > visible in the ifconfig -a output from the global zone. > > Is this expected? Do I have to plumb the interfaces in the zones myself > and create necessary files (/etc/hostname.vnic1, ...) to keep my > settings across reboots? I''d expect this to be done based on the net > properties in the zone''s configuration.No, you have to manually create the /etc/hostname.vnic1 etc for setting to be persistent. Its same behaviour as normal Solaris (without zone or global zone). And yes, I do need to fix my blog etc based on current man pages. Thanks for pointing that out. Cheers, Sunay -- Sunay Tripathi Distinguished Engineer Solaris Core Operating System Sun MicroSystems Inc. Solaris Networking: http://www.opensolaris.org/os/community/networking Project Crossbow: http://www.opensolaris.org/os/project/crossbow