Kyle McDonald writes: > James Carlson wrote: > > Kyle McDonald writes: > > > >> The 'set-linkprop', 'rename-link', and 'create-aggr' sub commands all > >> seem to take a '-R /a' argument, and run with out error messages. > >> However when I reboot the machine boot sup with no changes what so ever. > >> It's like I never ran those commands at all? > >> > > > > All the command really does is do some light validation of the > > arguments, and then toss the command text into either: > > > > $ROOT/var/svc/profile/upgrade_datalink > > > > or: > > > > $ROOT/var/svc/profile/upgrade > > > > ... depending on whether $ROOT/etc/dladm/datalink.conf exists. > When I looked it did exist, but was empty (if memory serves.) Which of > those should it append the commands to in that case?
If the conf file exists, then the former, else the latter. > > Maybe. Look at the log file for network/physical first. > > > > > Which log would that be? I checked > /etc/svc/volatile/network-physical:default.log (see below) That sounds like the right one. > r...@keymaster:/var/svc/profile# more upgrade_datalink.app.20090209151851 > /sbin/dladm set-linkprop -p mtu=9000 e1000g0 # added by dladm(1M) > /sbin/dladm rename-link bge1 mgmt0 # added by dladm(1M) > /sbin/dladm rename-link e1000g0 data0 # added by dladm(1M) That looks like the right sort of stuff. I'm not sure exactly what causes this to get sucked in. (It seems to be tangled up with manifest-import ...) > The Log file at /etc/svc/volatile/network-physical:default.log doesn't > show the commands from 'upgrade_datalink' being run at all: File a bug. -- James Carlson, Solaris Networking <[email protected]> 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 _______________________________________________ networking-discuss mailing list [email protected]
