crossbow discuss - Nov 2008 - help - crossbow etherstub missing after reboot

I am trying to use crossbow to simulate a low latency multicast messaging test
environment on a single box.

I''ve BFU''ed crossbow from
nightly-nd-bins-20081031.i386.tar.bz2 onto a clean Opensolaris 2008.5 build
running in VirtualBox.

All seems to work well except any etherstubs created and associated vnics
disappear after a reboot. After reboot, they do not appear in the list with
"dladm show-link", but if I try and recreate the etherstubs I get the
error "dladm: etherstub creation failed: object already exists".

Is this because I''ve installed crossbow on opensolaris 2008.5 and it
has dependencies in Nevada that are not in the 2008.5 distribution?

If so, is there anything I can do to get crossbow to work on opensolaris 2008.5?

Will crossbow work with 2008.11?

When will crossbow be released into the opensolaris tree as a pkg?

Thanks
-- 
This message posted from opensolaris.org

David,

On Nov 23, 2008, at 8:44 AM, David Sewell wrote:
> I am trying to use crossbow to simulate a low latency multicast  
> messaging test environment on a single box.
>
> I''ve BFU''ed crossbow from
nightly-nd-bins-20081031.i386.tar.bz2 onto
> a clean Opensolaris 2008.5 build running in VirtualBox.
>
> All seems to work well except any etherstubs created and associated  
> vnics disappear after a reboot. After reboot, they do not appear in  
> the list with "dladm show-link", but if I try and recreate the  
> etherstubs I get the error "dladm: etherstub creation failed: object  
> already exists".
NWAM is probably enabled. NWAM doesn''t bring up pseudo data-links like
aggr, VNICs, and etherstubs at boot. You can try disabling NWAM, see  
nwamd(1M), to confirm that this is the problem.
>
>
> Is this because I''ve installed crossbow on opensolaris 2008.5 and
it
> has dependencies in Nevada that are not in the 2008.5 distribution?
>
> If so, is there anything I can do to get crossbow to work on  
> opensolaris 2008.5?
>
> Will crossbow work with 2008.11?
Yes that should work.
> When will crossbow be released into the opensolaris tree as a pkg?
Crossbow is not a separate package since it changes the kernel stack,  
drivers, and other core OS components. However we''re in final approach
for integration of Crossbow in ONNV. When that''s done the bits will  
part of OpenSolaris.

Nicolas.
>
>
> Thanks
> -- 
> This message posted from opensolaris.org
> _______________________________________________
> crossbow-discuss mailing list
> crossbow-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/crossbow-discuss
-- 
Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc.
nicolas.droux at sun.com - http://blogs.sun.com/droux

Thanks - that fixed it.
-- 
This message posted from opensolaris.org

Nicolas Droux writes:
> David,
> 
> On Nov 23, 2008, at 8:44 AM, David Sewell wrote:
> 
> > I am trying to use crossbow to simulate a low latency multicast  
> > messaging test environment on a single box.
> >
> > I''ve BFU''ed crossbow from
nightly-nd-bins-20081031.i386.tar.bz2 onto
> > a clean Opensolaris 2008.5 build running in VirtualBox.
> >
> > All seems to work well except any etherstubs created and associated  
> > vnics disappear after a reboot. After reboot, they do not appear in  
> > the list with "dladm show-link", but if I try and recreate
the
> > etherstubs I get the error "dladm: etherstub creation failed:
object
> > already exists".
> 
> NWAM is probably enabled. NWAM doesn''t bring up pseudo data-links
like
> aggr, VNICs, and etherstubs at boot. You can try disabling NWAM, see  
> nwamd(1M), to confirm that this is the problem.
Is there a CR for this?  I wouldn''t expect NWAM to run on those
interfaces -- it wouldn''t plumb IP on them or acquire addresses -- but
I''m surprised that the user''s configured L2 devices would just
disappear on reboot and be put into an unusable state.

-- 
James Carlson, Solaris Networking              <james.d.carlson at
sun.com>
Sun Microsystems / 35 Network Drive        71.232W   Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677

On Nov 24, 2008, at 5:14 AM, James Carlson wrote:
> Nicolas Droux writes:
>> David,
>>
>> On Nov 23, 2008, at 8:44 AM, David Sewell wrote:
>>
>>> I am trying to use crossbow to simulate a low latency multicast
>>> messaging test environment on a single box.
>>>
>>> I''ve BFU''ed crossbow from
nightly-nd-bins-20081031.i386.tar.bz2 onto
>>> a clean Opensolaris 2008.5 build running in VirtualBox.
>>>
>>> All seems to work well except any etherstubs created and associated
>>> vnics disappear after a reboot. After reboot, they do not appear in
>>> the list with "dladm show-link", but if I try and
recreate the
>>> etherstubs I get the error "dladm: etherstub creation failed:
object
>>> already exists".
>>
>> NWAM is probably enabled. NWAM doesn''t bring up pseudo
data-links
>> like
>> aggr, VNICs, and etherstubs at boot. You can try disabling NWAM, see
>> nwamd(1M), to confirm that this is the problem.
>
> Is there a CR for this?  I wouldn''t expect NWAM to run on those
> interfaces -- it wouldn''t plumb IP on them or acquire addresses --
but
> I''m surprised that the user''s configured L2 devices would
just
> disappear on reboot and be put into an unusable state.
I couldn''t find an existing CR for this issue so I filed 6776009 (nmaw
doesn''t bring up pseudo data-links at boot time.)

Nicolas.

-- 
Nicolas Droux - Solaris Kernel Networking - Sun Microsystems, Inc.
nicolas.droux at sun.com - http://blogs.sun.com/droux