User manual NOVELL ZENWORKS LINUX MANAGEMENT 7.2 IR2 ADMINISTRATION GUIDE 09-25-2008

[. . . ] novdocx (en) 11 July 2008 AUTHORIZED DOCUMENTATION Administration Guide Novell® 7. 2 IR2 ZENworks® Linux Management September 25, 2008 www. novell. com Novell ZENworks 7. 2 Linux Management Administration Guide novdocx (en) 11 July 2008 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. [. . . ] The DHCP server responds with IP configuration information on port 68, including tag 60 for PXEClient, which indicates that novell-proxydhcp is running on the same server. Standard DHCP and Novell Proxy DHCP Configured on the Same Server: Part B Figure 28-3 DHCP Configuration on the Same Server, Part B Data Model Imaging Server novell-zmgprebootpolicy PXE Device novell-tftp nvlnbp. sys novell-pbserv novell-proxydhcp DHCP 2 port 68 PXE BIOS 1 port 4011 DHC P Request Network Processes: 1. When the device sees tag 60 in the DHCP response, the PXE BIOS reissues the DHCP request on port 4011. The Proxy DHCP server responds on port 68 with the name of the bootstrap program (nvlnbp. sys) and the IP address of the TFTP daemon where it can be found. Continue with "Phases 2 through 8: Continuing the Process" on page 334. Understanding Preboot Services in ZENworks Linux Management 333 novdocx (en) 11 July 2008 Phases 2 through 8: Continuing the Process The following sections explain how the Preboot Services process continues after Phase 1: "Phase 2" on page 334 "Phase 3" on page 334 "Phase 4" on page 335 "Phase 5" on page 335 "Phase 6" on page 336 "Phase 7" on page 336 "Phase 8" on page 337 Phase 2 Figure 28-4 Phase 2 of the Preboot Services Process Data Model Imaging Server novell-pbserv novell-zmgprebootpolicy 2 novell-tftp novell-proxydhcp nvlnbp. sys PXE Device 3 1 nvlnbp. sys PXE BIOS Processes: 1. Phase 3 Figure 28-5 Phase 3 of the Preboot Services Process Data Model novell-pbserv Imaging Server novell-zmgprebootpolicy 3 2 novell-tftp novell-proxydhcp Hot-key: pxemenu. text PXE Menu? PXE Device 1 nvlnbp. sys PXE BIOS Processes: 1. Hardware detection is performed by nvlnbp. sys and it reads the image-safe data. 334 Novell ZENworks 7. 2 Linux Management Administration Guide novdocx (en) 11 July 2008 2. Nvlnbp. sys requests the Preboot Services Menu configuration from the Data Model via the novell-zmgprebootpolicy daemon. The novell-zmgprebootpolicy daemon returns the Preboot Services Menu configuration. In this case, the menu described in pxemenu. txt is displayed when a user presses the hot key. Phase 4 Figure 28-6 Phase 4 of the Preboot Services Process Data Model novell-pbserv Imaging Server novell-zmgprebootpolicy 2 novell-tftp novell-proxydhcp PXE Device Preboot work to do? 1 Yes: z_auto. cfg nvlnbp. sys PXE BIOS Processes: 1. Assuming no Preboot Services Menu is displayed, the device asks the Data Model (via novellzmgprebootpolicy) if any work is assigned. Assuming work is assigned, the novell-zmgprebootpolicy daemon responds with the name of the configuration file to use in performing the preboot work (z_auto. cfg in this example). Phase 5 Figure 28-7 Phase 5 of the Preboot Services Process Data Model Imaging Server PXE Device novell-pbserv novell-zmgprebootpolicy novell-tftp 2 novell-proxydhcp pxelinux. 0 1 nvlnbp. sys PXE BIOS Processes: 1. The TFTP server sends pxelinux. 0 to the device. Understanding Preboot Services in ZENworks Linux Management 335 novdocx (en) 11 July 2008 Phase 6 Figure 28-8 Phase 6 of the Preboot Services Process Data Model Imaging Server novell-pbserv novell-zmgprebootpolicy novell-tftp 2 novell-proxydhcp z_auto. cfg z_auto. cfg PXE Device 1 pxelinux. 0 PXE BIOS Processes: 1. Pxelinux. 0 replaces nvlnbp. sys in memory and requests z_auto. cfg from the TFTP server. Phase 7 Figure 28-9 Phase 7 of the Preboot Services Process Data Model Imaging Server novell-pbserv novell-zmgprebootpolicy novell-tftp novell-proxydhcp 1 2 3 4 pxelinux. 0 PXE BIOS PXE Device Processes: 1. Pxelinux. 0 requests and receives /boot/updateDrivers. tgz from the TFTP server, but is denied because the file does not exist (it is used to provide post-release software updates). 336 Novell ZENworks 7. 2 Linux Management Administration Guide novdocx (en) 11 July 2008 Phase 8 Figure 28-10 Phase 8 of the Preboot Services Process Data Model Image Imaging Server 3 image. zmg novell-pbserv novell-zmgprebootpolicy novell-tftp novell-proxydhcp 2 3 Imaging Engine SUSE Linux Enterprise Server 9 SP1 1 PXE Device Processes: 1. SUSE Linux Enterprise Server (SLES) 9 SP1 is loaded and run on the device. The ZENworks Imaging Engine (img) requests the assigned Preboot Services work details and performs the work. The image is laid down on the device and it automatically reboots. 28. 5 Preboot Strategies The following sections present possible approaches to using Preboot Services. Section 28. 5. 1, "Automating Updates and Installations, " on page 337 Section 28. 5. 2, "Creating, Installing, and Restoring Standard Images, " on page 338 Section 28. 5. 3, "Reimaging Corrupted Devices, " on page 339 Section 28. 5. 4, "Restoring Lab Devices to a Clean State, " on page 339 Section 28. 5. 5, "Setting Up Devices for Future Reimaging, " on page 340 Section 28. 5. 6, "Multicasting Device Images, " on page 340 Section 28. 5. 7, "Configuring Dell Linux Devices, " on page 342 28. 5. 1 Automating Updates and Installations You can automate Linux installations and software updates using Preboot Services in the following ways: SUSE Linux installation: The AutoYaST bundle can automate installation of SUSE Linux on a Linux device. [. . . ] Added information for CreateMonothicBundle under Catalogs Bundles, and Packages. L. 3 June 26, 2008 Updates were made to the following sections. The changes are explained below. L. 3. 1 Appendix The following changes were made in this section: Location Change zlmmirror (1) (page 540) Updated this section. L. 4 May 19, 2008 (Interim Release 2) Updates were made to the following sections. Section L. 4. 1, "ZENworks System Management, " on page 667 Section L. 4. 2, "Package and Content Management, " on page 667 Section L. 4. 3, "Preboot Services, " on page 667 666 Novell ZENworks 7. 2 Linux Management Administration Guide novdocx (en) 11 July 2008 Section L. 4. 4, "Event Monitoring, " on page 668 Section L. 4. 5, "Appendix, " on page 668 L. 4. 1 ZENworks System Management The following changes were made in this section: Location Change Section 7. 12, "Configuring the ZENworks Server Preferences, " on page 76 Section 7. 13, "Understanding the StoreFileDeps Preference, " on page 77 Added this section. Added this section. Section 9. 1. 3, "Deleting the Added this section. Dangling Objects from ZENworks Object Store, " on page 84 Section 9. 5, "Cleaning Up the ZENworks Database, " on page 94 Added this section. L. 4. 2 Package and Content Management The following changes were made in this section: Location Change Chapter 19, "Understanding Added this chapter. [. . . ]