Monday, April 26, 2010

Building Jumpstart Server with Root disk Mirroring

These steps are based upon the assumption that boot server, install server, config server all are on the same server.1. Put in the cd.

2. # cd /cdrom/so/Solaris_9/Tools

3. # ./setup_install_server /jumpstart_dir

/jumpstart_dir is the directory used for storing cd-images.

4. #cd /cdrom/s0/Solaris_9/Misc

5. #cp * /jumpstart_dir

6. Put in the second CD.

7. #cd /cdrom/s0/Solaris_9/Tools

8. #./add_to_install_server /jumpstart_dir

9. This would complete the boot server image as well as the install server image to the /jumpstart_dir directory.

10. get the ethernet address of the client, either from ifconfig -a command or from the
banner command from the ok prompt.

11. create the /etc/ethers file.

03:12:af:21:12:12 client-name

12. Make an entry in the /etc/hosts file corrosponding to the client-name

10.0.0.1 client-name

13. Create the sysidcfg file. This file would contain all the client identification mechanism for client. an example would be

system_locale=US
timezone=Asia/Calcutta
terminal=vt100
name_service=NONE
timeserver=localhost
security_policy=NONE
root_password=And123MpaN
network_interface=primary
{ hostname = client-name
ip_address=10.0.0.1
netmask=255.255.255.0
default_router=10.0.0.30
protocol_ipv6=no }

Here the root_password should be in encrypted format and can be a standard password for fresh installs.

14. NOTE: For the sysidcfg file, root password must be in the encrypted format, this is in the format from /etc/shadow. This can be copied from any of the existing servers.

15. create this sysidcfg file also in the /jumpstart_dir directory. However, inside the directory name of the client.

/jumpstart_dir/client-name/sysidcfg.

You need a unique sysidcfg file for each and every client.

16. a file called rules would exist in the scripts that we copied from Misc direcotry of the first CD. please edit the file, so that it contain only this line

any - - any_machine -

17. any_machine is the name of the profile file that would contain the partition information for the clients.

18. Profile file would be like the example below, this would also enable to root disk mirroring using the SVM.

File system partioning can be done based upon the following format

filesys slice start_cylinder:slice_size_by_cylinders file_system

install_type initial_install
system_type standalone
partitioning default
cluster SUNWCall
filesys mirror:d1 c1t0d0s0 c1t1d0s0 15000 /
filesys mirror:d10 c1t0d0s1 c1t1d0s1 32000 swap
filesys mirror:d20 c1t0d0s3 c1t1d0s3 32000 /var
metadb c1t0d0s7
metadb c1t1d0s7

Here we are creating a standard profile file to be used for all clients.

19. We need to verify the rules file along with the profile file for any syntax errors, to do this we would require something called the check script.

20. This check script would be available from the 1st CD, please copy the check script from the CD to the /jumpstart_dir directory.

21. after copy, please run the script.

22. If there are no errors, on profile and rules file, this would generate a rules.ok file on the /jumpstart_dir directory.

23. Share the /jumpstart_dir through NFS.

share -F nfs -o ro,anon=0 /jumpstart_dir

24. #cd /jumpstart_dir/Solaris_9/Tools/

25. Edit the inetd.conf, for tftp to work.

26. #./add_install_client -e 03:12:af:21:12:12 -s server-name:/jumpstart_dir -c server-name:/jumpstart_dir -p server-name:/jumpstart_dir/client-name sun4u

This would create the /etc/bootparams file, start the rpc.bootparamd, start in.rarpd, fill the /tftpboot directory.

27. Above steps complete the jumpstart server config.

28. Go to the client, give

{ok} boot net – install

29. See the magic happen

30. this would complete the unattended installation of client from a jumpstart-server.