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. 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.
> 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.
--
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]
