crossbow discuss - Mar 2010 - Making vnics and etherstubs persistent over reboots.

Hi all,

I''m working on a project where I''m creating many zones and
connecting them to the global-zone via an etherstub and vnics.

My problem is that when I reboot my machine (actually a VB VM at the moment) the
etherstubs and vnics aren''t there, dladm show-etherstub and dladm
show-vnic shows nothing in either the global zone nor the other zones...

Here''s an example of what I''m doing in the global zone: 
dladm create-etherstub global2applications_switch1
dladm create-vnic -l global2applications_switch1 global_vnic1
ifconfig global_vnic1plumb 10.0.0.1
dladm create-vnic -l global2applications_switch1 zone1


And then for the zones I''m using a script  similar to this:
create -b
set zonepath=/export/zones/testzone
set brand=ipkg
set autoboot=true
set ip-type=exclusive
add net
set physical=zone1
end
verify
commit
exit

I''m wondering whether I need to plumb the vnic into the zone to make it
persistent?  I''ve not tried that just yet, I''ve just thought
about it?

I have seen a number of bugs, but they have all been closed but no workaround
has been provided?

I''m using OpenSolaris 2009.06 and have no mechanism for upgrading to a
dev build.

Many, many thanks,
Ben
-- 
This message posted from opensolaris.org

Ben wrote:
> Hi all,
> 
> I''m working on a project where I''m creating many zones
and connecting them to
> the global-zone via an etherstub and vnics.
> 
> My problem is that when I reboot my machine (actually a VB VM at the
moment)
> the etherstubs and vnics aren''t there, dladm show-etherstub and
dladm
> show-vnic shows nothing in either the global zone nor the other zones...
Probably due to nwam use.

Here''s something from Erik:

The workaround I use it to manually run a script after reboot which does
     /sbin/dladm up-aggr
     /sbin/dladm up-vlan
     /sbin/dladm up-vnic
     /sbin/dladm init-linkprop -w

    Erik

Cheers,
Jim

On Sun, Mar 14, 2010 at 07:59:01PM -0600, Jim Walker
wrote:
> Ben wrote:
> >Hi all,
> >
> >I''m working on a project where I''m creating many
zones and connecting them to
> >the global-zone via an etherstub and vnics.
> >
> >My problem is that when I reboot my machine (actually a VB VM at the
moment)
> >the etherstubs and vnics aren''t there, dladm show-etherstub
and dladm
> >show-vnic shows nothing in either the global zone nor the other
zones...
> 
> Probably due to nwam use.
It is true that, when crossbow was first integrated, the initialization
of vlans, vnics, etc. was not included in the nwam start method, as it
was in the network/physical:default method.  However, that was corrected
in build 132, with the fix for 6776009.

One caveat is that aggrs are still *not* configured when nwam is enabled.
The problem there is that nwam attempts to manage all available links (with
the exception of vlans and vnics, which can clearly be excluded during link
discovery), but the logic is currently not there to ignore links that are
part of an aggregation.  So if you have aggrs in your config, you''ll
need
to stick to network/physical:default.

-renee
> Here''s something from Erik:
> 
> The workaround I use it to manually run a script after reboot which does
>     /sbin/dladm up-aggr
>     /sbin/dladm up-vlan
>     /sbin/dladm up-vnic
>     /sbin/dladm init-linkprop -w
> 
>    Erik
> 
> Cheers,
> Jim
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss

[b]It is true that, when crossbow was first integrated, the initialization
of vlans, vnics, etc. was not included in the nwam start method, as it
was in the network/physical:default method.  However, that was corrected
in build 132, with the fix for 6776009.

One caveat is that aggrs are still *not* configured when nwam is enabled.
The problem there is that nwam attempts to manage all available links (with
the exception of vlans and vnics, which can clearly be excluded during link
discovery), but the logic is currently not there to ignore links that are
part of an aggregation.  So if you have aggrs in your config, you''ll
need
to stick to network/physical:default.

-renee[/b]

Thanks Renee.  It''s good to hear that it''ll work in
OpenSolaris 2010.03.  I''ll stick with 2009.06 for the time being.  I
need to wait until I can download the new repository as I don''t have
internet access at home where my VMs are.
-- 
This message posted from opensolaris.org

On Mon, 15 Mar 2010 11:56:05 -0700 (PDT)
Ben <ben.lavery at gmail.com> wrote:
> One caveat is that aggrs are still *not* configured when nwam is enabled.
> The problem there is that nwam attempts to manage all available links (with
> the exception of vlans and vnics, which can clearly be excluded during link
> discovery), but the logic is currently not there to ignore links that are
> part of an aggregation.  So if you have aggrs in your config,
you''ll need
> to stick to network/physical:default.
This is no longer true in 135.  If you want to use aggrs use a User
profile and don''t include the links in the aggregation.

		Michael