Patrick J. McEvoy
2009-Jun-16 00:18 UTC
[crossbow-discuss] objects disappear from dladm after reboot
On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I set some properties, and everything was working, then I rebooted my system and everything disappeared from show-vnic, show-flow, and show-prop. When I tried to re-create the objects, dladm said they already existed. While I could not see the objects, I could delete them. Example: # dladm show-vnic # dladm create-vnic -l bge0 vphys0 dladm: vnic creation over bge0 failed: object already exists # dladm show-vnic vphys0 dladm: failed to show vnic ''vphys0'': object not found # dladm delete-vnic vphys0 # dladm create-vnic -l bge0 vphys0 # How do I create persistent objects that continue to be visible after reboots? -- This message posted from opensolaris.org
Patrick J. McEvoy
2009-Jun-16 01:38 UTC
[crossbow-discuss] objects disappear from dladm after reboot
Seems to be a bug introduced between 2008.11 and 2009.06:
http://defect.opensolaris.org/bz/show_bug.cgi?id=6225
Trying to figure out a workaround...
--
This message posted from opensolaris.org
Patrick J. McEvoy
2009-Jun-16 02:00 UTC
[crossbow-discuss] objects disappear from dladm after reboot
Things show up in show-linkmap (see below), but these do not help:
svcadm restart network/datalink-management:default
svcadm disable network/datalink-management:default
svcadm enable network/datalink-management:default
# dladm show-linkmap
NAME LINKID CLASS MEDIA FLAGS
bge0 1 phys Ethernet 3
bge1 2 phys Ethernet 3
bge2 3 phys Ethernet 3
bge3 4 phys Ethernet 3
stub17 5 etherstub Ethernet 2
stub19 6 etherstub Ethernet 2
vnic170 7 vnic Ethernet 2
vnic171 8 vnic Ethernet 2
vnic172 9 vnic Ethernet 2
vnic190 10 vnic Ethernet 2
vnic191 11 vnic Ethernet 2
vnic192 12 vnic Ethernet 2
etherstub3 14 etherstub Ethernet 2
vnic1 15 vnic Ethernet 2
vnic2 16 vnic Ethernet 2
vnic3 17 vnic Ethernet 2
vnic6 18 vnic Ethernet 2
vnic9 19 vnic Ethernet 2
vphys1 21 vnic Ethernet 2
etherstub0 22 etherstub Ethernet 2
stub0 23 vnic Ethernet 2
stub1 24 vnic Ethernet 2
znic0 25 vnic Ethernet 2
znic1 26 vnic Ethernet 2
vphys0 28 vnic Ethernet 3
vphys01 29 vnic Ethernet 3
etherstub1 30 etherstub Ethernet 2
stub10 31 vnic Ethernet 2
stub11 32 vnic Ethernet 2
stub12 33 vnic Ethernet 2
foonic0 34 vnic Ethernet 2
foonic01 35 vnic Ethernet 2
#
--
This message posted from opensolaris.org
Nicolas Droux
2009-Jun-16 04:22 UTC
[crossbow-discuss] objects disappear from dladm after reboot
Patrick, This could be due to NWAM. Try disabling NWAM as described in nwamd(1M). See also 6776009 (nmaw doesn''t bring up pseudo data-links at boot time.) Nicolas. On Jun 15, 2009, at 6:18 PM, Patrick J. McEvoy wrote:> On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I > set some properties, and everything was working, then I rebooted my > system and everything disappeared from show-vnic, show-flow, and > show-prop. When I tried to re-create the objects, dladm said they > already existed. While I could not see the objects, I could delete > them. Example: > > # dladm show-vnic > # dladm create-vnic -l bge0 vphys0 > dladm: vnic creation over bge0 failed: object already exists > # dladm show-vnic vphys0 > dladm: failed to show vnic ''vphys0'': object not found > # dladm delete-vnic vphys0 > # dladm create-vnic -l bge0 vphys0 > # > > How do I create persistent objects that continue to be visible after > reboots? > -- > 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
Kais Belgaied
2009-Jun-16 17:33 UTC
[crossbow-discuss] objects disappear from dladm after reboot
there is also 6851483 - dladm: vnic creation over e1000g1 failed: object
already exists.
there is a work around:
. check if dladm show-linkmap shows the vnic.
. (blindly) delete the vnic before (re)creating it.
Kais.
On 06/15/09 21:22, Nicolas Droux wrote:> Patrick,
>
> This could be due to NWAM. Try disabling NWAM as described in
> nwamd(1M). See also 6776009 (nmaw doesn''t bring up pseudo
data-links
> at boot time.)
>
> Nicolas.
>
> On Jun 15, 2009, at 6:18 PM, Patrick J. McEvoy wrote:
>
>> On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I
>> set some properties, and everything was working, then I rebooted my
>> system and everything disappeared from show-vnic, show-flow, and
>> show-prop. When I tried to re-create the objects, dladm said they
>> already existed. While I could not see the objects, I could delete
>> them. Example:
>>
>> # dladm show-vnic
>> # dladm create-vnic -l bge0 vphys0
>> dladm: vnic creation over bge0 failed: object already exists
>> # dladm show-vnic vphys0
>> dladm: failed to show vnic ''vphys0'': object not found
>> # dladm delete-vnic vphys0
>> # dladm create-vnic -l bge0 vphys0
>> #
>>
>> How do I create persistent objects that continue to be visible after
>> reboots?
>> --
>> 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
2009-Jun-16 18:17 UTC
[crossbow-discuss] objects disappear from dladm after reboot
On Jun 16, 2009, at 11:33 AM, Kais Belgaied wrote:> there is also 6851483 - dladm: vnic creation over e1000g1 failed: > object already exists.It seems that 6851483 could be a dup of 6776009. They didn''t specify whether they were running in the default configuration with NWAM enabled though. I asked the submitter for more info via bugster. Nicolas.> there is a work around: > . check if dladm show-linkmap shows the vnic. > . (blindly) delete the vnic before (re)creating it. > > Kais. > > On 06/15/09 21:22, Nicolas Droux wrote: >> Patrick, >> >> This could be due to NWAM. Try disabling NWAM as described in >> nwamd(1M). See also 6776009 (nmaw doesn''t bring up pseudo data- >> links at boot time.) >> >> Nicolas. >> >> On Jun 15, 2009, at 6:18 PM, Patrick J. McEvoy wrote: >> >>> On OpenSolaris 2009.06 I created a flow, half a dozen VNICs, and I >>> set some properties, and everything was working, then I rebooted >>> my system and everything disappeared from show-vnic, show-flow, >>> and show-prop. When I tried to re-create the objects, dladm said >>> they already existed. While I could not see the objects, I could >>> delete them. Example: >>> >>> # dladm show-vnic >>> # dladm create-vnic -l bge0 vphys0 >>> dladm: vnic creation over bge0 failed: object already exists >>> # dladm show-vnic vphys0 >>> dladm: failed to show vnic ''vphys0'': object not found >>> # dladm delete-vnic vphys0 >>> # dladm create-vnic -l bge0 vphys0 >>> # >>> >>> How do I create persistent objects that continue to be visible >>> after reboots? >>> -- >>> 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
Patrick J. McEvoy
2009-Jun-16 20:29 UTC
[crossbow-discuss] objects disappear from dladm after reboot
> This could be due to NWAM. Try disabling NWAM as described in nwamd(1M).Thanks. I disabled NWAM and rebooted, and now I see VNICs, flows, and etherstubs. -- This message posted from opensolaris.org
Patrick J. McEvoy
2009-Jun-16 20:31 UTC
[crossbow-discuss] objects disappear from dladm after reboot
> there is a work around: > . check if dladm show-linkmap shows the vnic. > . (blindly) delete the vnic before (re)creating it.That''s only a workaround if one writes a service that deletes and recreates all the crossbow stuff before zones come up on reboot. So...I''m stuck running without NWAM for now. -- This message posted from opensolaris.org