The following shows the sequence of a non-interactive jumpstart installation. The jumpstart is an Initial install using a sysidcfg
file, profile and finish script. 

This can be used to identify the point where a Solaris 2.6 or Solaris 7 jumpstart is failing. 

1. Rebooting with command: net - install 

        Boot device: Note: output varies depending on machine architecture.
        File and args: - install             

2. PROM broadcasts RARP request. 

Note: several ARP/RARP timeouts displayed here are not unusual. 

3. 2dc00 - incrementing hex #s 

Note: represents the download of the tftpboot file. 

4. hostname: client_host_name 

5. domainname: the domainname 

Note: "no domainname" is seen when domainname is not configured. 

6. root server: root_server_name 

7. root directory: /some_path_to_solaris_2.6/Solaris_2.6/Tools/Boot 

8. The kernel gets loaded: 

        SunOS Release 5.6 Version Generic [UNIX(R) System V Release 4.0] 
        Copyright (c) 1983-1997, Sun Microsystems, Inc.            

9. Configuring devices... 

10. Using sysidcfg configuration file xxx.xxx.xx.xx:/path_to_file/sysidcfg 

Note: If the sysidcfg file is NOT found, there is no message saying, "can't find sysidcfg file" 

11. The system is coming up. Please wait. 

Note: Openwindows is started here if the jumpstart client's console is a graphics monitor. 

12. Starting remote procedure call (RPC) services: sysidnis done. 

13. Starting Solaris installation program... 

14. Searching for JumpStart directory... 

15. Using rules.ok from xxx.xxx.xx.xx:/path_to_rules file 

16. Checking rules.ok file... 

17. Using profile: name_of_profile 

18. Using finish script: name_of_finish_script 

19. Executing JumpStart preinstall phase... 

20. Searching for SolStart directory... 

21. Checking rules.ok file... 

22. Next: 

        Using begin script: install_begin
        Using finish script: patch_finish
        Executing SolStart preinstall phase...
        Executing begin script "install_begin"...
        Begin script install_begin execution completed.            

Note: The script names install_begin, patch_finish are standard 

23. Processing default locales 

        Specifying default locale (en_US)            

24. Processing profile 

Note: information contained in the jumpstart profile/class 

file is processed here: 

       Selecting cluster (SUNWCXall) 
       Deselecting cluster (SUNWCpm) 
       Deselecting cluster (SUNWCpmow) 
       Selecting locale (en_US) 

At this point, jumpstart will typically continue to completion. A complete capture of a Solaris 7 jumpstart of an Ultra 10 client: