Sajid Zia wrote: > Bill Sommerfeld wrote: >> On Fri, 2007-08-03 at 14:41 -0700, Mark Carlson wrote: >> >> >>> The installation process changed a bit in the sense that we need to >>> provide iscsi boot target IP address and client's Initiator Node >>> Name during the installation to discover the boot device. This is >>> accomplished by using bootparams. The following name=val entry is >>> required in /etc/bootparams on the install server. >>> >>> <Client's Name> iscsi-boot=Target_IP:Initiator_Node_Name >>> >> whoa! you need *both* DHCP *and* bootparams configured for each client? >> Until now, you'd only ever need one or the other, and never both. Since >> early stages boot from DHCP, this should be in DHCP too, not >> bootparams... >> > A bootparams parameter is a better approach rather than inventing a new > dhcp macro > or overloading an exisiting one to provide this information. That is the > feedback I had > gotten from Solaris NewBoot folks. Please note that we are not using any > special dhcp > macro to provide client specific information. We use the standard > solaris net installation > process to do the boot as well. Only thing new is the bootparams parameter. >
I must respectfully, but vehemently, disagree with this advice (unfortunately, the Install team has not been consulted on this proposal prior to its presentation, so this is my first opportunity to comment). We have been moving network installation away from bootparams for a number of years due to its non-standard nature and lack of a reasonable ability to support any network topology beyond simple LANs. Requiring its use here is not defensible when ample methods for solving the boot-device location problem exist using DHCP or other standard protocols. Dave
