Peter Memishian wrote: > > > Until that fix is available though, the alternatives seem limited -- the > > > only one that occurs to me is to have net-physical manually start dlmgmtd > > > (through svcadm if possible, though previous attempts to do this failed). > > > > Why did they fail? > > Unclear; Seb is looking into this now and will report back soon.
Yep, I'm currently re-creating a fresh snv_80 BE to test this on, which takes a little while. > (Conjecture: even though the service has been imported, maybe it's not > possible to enable the service until manifest-import has run?) We'll soon find out, I'll report back as soon as I implement this potential workaround. > > > If nothing else, we can instruct people to refresh network/physical > > manually and reboot, right? > > A reboot will suffice for most cases, but for aggregations the persistent > configuration will have been lost, since the create-aggr commands stored > in upgrade_datalink are only executed once. So the sysadmin would need > to manually recreate those (ugh!) Plus this is an issue for real customers who live-upgrade from s10. IMO, requiring a second reboot for internal snv users is okay (though embarrassing), requiring that of actual customers is not really acceptable. Was the suggestion made with the assumption that by the time customers upgrade, the SMF manifest-import fix will have been integrated? -Seb
