Hi, I ran installadm create-client.
When the macro already exists, it was not changed. This left the macro full of information not pertinent to AI installation.
When the macro did not exist, one was not created.create-client used to create/change the macro to have AI information. Now it doesn't appear to do so. (Although when I did a delete-client it told me to run "dhtadm -D -m xxxxxxx".)
BTW: We're using these tools...
[ja123687] (67736)> pkg info installadm
Name: install/installadm
Summary: installadm utility
Description: Automatic Installation Server Setup Tools
Category: System/Administration and Configuration
State: Installed
Publisher: solaris
Version: 0.5.11
Build Release: 5.11
Branch: 0.164
Packaging Date: Fri Apr 22 17:45:21 2011
Size: 694.06 kB
FMRI:
pkg://solaris/install/[email protected],5.11-0.164:20110422T174521Z
Evan Layton said the following on 05/04/11 14:52:
On 5/4/11 2:40 PM, Jon K Aimone wrote:Hi, How does one go about getting AI and Solaris 10 network installation to coexist on the same multihomed server? Yes, this is a loaded question. We have been using the AI server as our DHCPserver for the lab. Which works fine as long as the S10 and S11 installers agreeto make certain the DHCP macros are configured correctly for themselves. With changes to AI to make multihomed servers work better, this doesn't appear to be the case. Lemme 'xplain... For Solaris 10 installation using DHCP certain installation tools create client macros named after the client ID. This is what's in the customer docs to do. Sorta the way AI used to do it. This was cool, because then when I set up the same target machine for AI it would change the macro to suite its needs. Now AI doesn't change that macro, and it doesn't warn the user that there is such a macro, so when I did a boot net:dhcp - install my system obediently installed Solaris 10, again. My witty response what "Huh? What the <censored>?"I've got a couple questions on this. If there is an existing macro for a specific client that is connected to a JumpStart I would expect that macro to install Solaris 10 from that JumpStart setup. What was done that the expectation was that the macro would be rewritten, was "installadm create-client" run to update the client and it just didn't update the macro? If that's the case then perhaps we have a bug (or I'm missing something) it appears that the man page states "Sets up DHCP macro, if it doesn't exist" but it doesn't state that it updates that macro if it finds a preexisting macro. If it's not updating the existing macro I think that's probably a bug in this case since we're trusting that the existing macro is correct and I don't think that's really the behavior we want here. -evanSo now it looks like I'm going to have to wrapper installadm to clean up the DHCP macro... just like I've had to do with Solaris 10 jumpstart. And here I thought things were going to get easier for customers. <usual CYA> Or did I miss something fundamental... again? </usual CYA> _______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
--
~~~~~~~\o/~~~~~~~
Cheers,
Jon.
{-%]
========
If you always do what you've always done, you'll always get what you've always
gotten.
- Anon.
--------
The difference between genius and stupidity is that genius has its limits.
- Albert Einstein
--------
When someone asks you, "Penny for your thoughts," and you put your two cents
in, what happens to the other penny?
- G. Carlin (May 12, 1937 - June 22, 2008)
========
<<attachment: jon_aimone.vcf>>
_______________________________________________ caiman-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/caiman-discuss
