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? > It's > then svc:/network/physical that (re)runs the dladm commands after the > next boot. > > >> Is there something different about the JumpStart net-boot environment? >> > > 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)
After reboot I find this in /var/svc/profile: r...@keymaster:/var/svc/profile# ls -l upgrade* -rw-r--r-- 1 root other 4949 Feb 9 14:56 upgrade.app.20090209151850 -rw-r--r-- 1 root root 184 Feb 9 15:06 upgrade_datalink.app.20090209151851 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) r...@keymaster:/var/svc/profile# I made all the other changes needed to /etc/hostname.*, and /etc/hosts for the renames to work. But 'svcs -xv' still gives: r...@keymaster:/var/svc/profile# svcs -xv svc:/network/physical:default (physical network interfaces) State: maintenance since Mon Feb 09 15:17:35 2009 Reason: Start method exited with $SMF_EXIT_ERR_CONFIG. See: http://sun.com/msg/SMF-8000-KS See: man -M /usr/share/man -s 1M ifconfig See: /etc/svc/volatile/network-physical:default.log Impact: 33 dependent services are not running: svc:/system/filesystem/local:default svc:/system/sysidtool:net . . . The Log file at /etc/svc/volatile/network-physical:default.log doesn't show the commands from 'upgrade_datalink' being run at all: r...@keymaster:/var/svc/profile# more /etc/svc/volatile/network-physical:default.log [ Feb 9 15:17:29 Enabled. ] [ Feb 9 15:17:30 Executing start method ("/lib/svc/method/net-physical"). ] [ Feb 9 15:17:30 Timeout override by svc.startd. Using infinite timeout. ] ifconfig: cannot open link "data0": DLPI link does not exist ifconfig: cannot open link "mgmt0": DLPI link does not exist add net default: gateway 172.30.171.254: Network is unreachable add net default: gateway 172.30.172.254: Network is unreachable [ Feb 9 15:17:35 Method "start" exited with status 96. ] r...@keymaster:/var/svc/profile# >> A related question, why don't 'show-link' and 'show-aggr' have a -R >> option? heck why isn't -R just an option to dladm itself and not the >> subcommand like this: >> > > Because you can't do that. :-/ > > The interfaces used by dladm (including the .conf file) are not stable > across patches. The alternate root might have an incompatible > database on it. We thus allow write-only commands to be put into the > post-reboot upgrade script, and we hope they'll work after reboot, but > there's no sane way we can read the configuration of the alternate > root environment. > > Ok. Makes sense. Just surprised me when the 'set/create' commands worked with out error, and the 'show' commands didn't show any thing as changed. Thanks! -Kyle _______________________________________________ networking-discuss mailing list [email protected]
