Lucas Williams reports on Setting Up JumpStart With Solaris 10 OS for SPARC Platforms and ZFS in his recent BigAdmin piece. He used a single Sun Enterprise 3500 server running Solaris 10 Operating System (Solaris OS) and a single client machine, a Sun Netra X1 server. Although he used the Solaris 10 08/07 release, Williams writes that this procedure will work with versions going back as far as 03/05.
Williams covers the following topics in his article:
- Setting Up ZFS Storage Pools
- Copying Files
- Setting Up Configuration Files
- Setting Up the Server to Boot Correctly
- Setting Up the Client
- Booting the Client
Code samples are provided throughout the article, as well as several requirements, such as needing to be logged in as root or some other system administrator, and needing to have the boot server be the DHCP server.
Williams writes that he used a spare disk on his server to host the Solaris JumpStart server pool. He then reports on the install of Solaris 10 HW807 SPARC on his Sun Enterprise 3500 server, which was straightforward and went as expected.
When it came to writing the files necessary to get the Solaris JumpStart up and running, Williams writes that he wrote his own files since his system had an anticipated use but adds that one can just as easily copy the samples from the disc and then modify them as needed.
In setting up the client, Williams cautions that one needs to exercise care in choosing the installation image, not the CD as the source of commands. This is because installing from the CD will cause the client to look on the CD for the boot image which it will not find it, unless one is using NFS to share the CD-ROM drive on the server. Otherwise, the commands will fail.
In the final step of the process, booting the client, Williams reports that things could not have gone more smoothly. Starting with the OpenBoot prompt, he ran the ok. boot net - install command, which caused the client to connect to his server, download the OS and commence the install. That left Williams with only the need to tell the server to use the default IPv4 setting detected, after which rebooting and coming up in console mode followed automatically.
Read More ...