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
