Recent Changes - Search:


Code:


Social:


My journals will take the place of a blog. If you go to the Journal page there is an RSS feed to subscribe with.

« July 2017 
SunMonTueWedThuFriSat
      1
2345678
9101112131415
16171819202122
23242526272829
3031     

Sites I take responsibility for

West Volusia, Florida

Documents

Technical

General

Me

Living

Places I frequent

Hobbies

Humor

Items for sale:


Clipboard

edit SideBar

Remote operating system installation

Include our styles below Infobox - invoke as >>infobox<< ... >><<

Codebox: - invoke as >>codebox<< ... >><<

warnbox: - invoke as >>codebox<< ... >><<

editingbox: - invoke as >>codebox<< ... >><<

noticebox: - invoke as >>codebox<< ... >><<

Page bread crumbs: Welcome to ke3vin.org! - My Public Technical Notes - Software And Operating Systems - Operating System Concepts - Remote Installing

Pages by tags: (:listtags:)
Subscribe to this wiki: RSS Feed RSS or subscribe to this page for changes: RSS Feed RSS
496 articles have been published so far. Recent changes
Share

2016-03-22: This site is being moved to my main site at https://kevininscoe.com/wiki as part of a consolidation to one domain.


Netstarting - How Kickstart/Jumpstart works:

Kickstart (Linux) or JumpStart (Sun/Solaris) (which I will refer to generically from now on in this article as simply "netstarting") is a method of installing and configure systems remotely. In the process the configuration and customization of the client being installed is accomplished automatically via a series of rules you define in advance based on the clients unique system attributes. By using netstarting it is possible to install groups of identical systems easily. This provides system administrators with a tool for configuration and change management and helps provide continuity in a disaster recovery situation. In a best case scenario let's say you have racks of hosts connected to network or SAN attached storage. And let's say a host has failed or you need to scale an application up horizontally by adding a new host. You simply configure the rules or profile for the replacement or new host (usually just a file copy and changing the MAC, IP address and host name information) and away you go. In a lights out operation you don't even have to visit the physical host at all once it's physically installed and racked. In a worst case scenario at the very least you now have a ready recipe for system replacement without locating a bunch of install discs or remembering how to install an application.

While setting up a kick/jumpstart server requires some initial work up front (and lots of testing), the long term benefits of being able to install an operating system quickly (and more importantly in a repeatable prescribed configuration) makes the time investment worthwhile. How this is accomplished is completed slightly differently for Kickstart and Jumpstart and the details I will go into else where (see bottom).

Upon power-up, the client being installed can contact a bootp server on the local network and download a small boot kernel that subsequently brings the machine to a functional state. While this process is very similar to the way disk-less clients function, the netstart-ed client then requests a file or profile on the netstart profile server to determine what to install and configure on the client. A rules file or profile can be viewed as a table that contains one or more rules that define how clients are installed. These rules are based on the client system attributes usually the Media Access Control address (MAC address) of the target system.

There are three unique server functions: the DHCP or name server, the boot/install/bootp server and the net install profiles or rules file server. Normally one host performs all three functions however they can be separate as long as they are on the same physical or logical network. It is possible for these server functions to be on different networks through network router functions however I will leave that as an exercise for the reader. Suffice to say it is is difficult to get right and I highly recommend these three server functions remain local.

The following overall steps outline the procedure to install a client using netstarting (see Figure 1):

1. The install client is turned on and booted

(Intel/Alpha/RS-6000) using PXE boot

(Sun Sparc) with the following command at the boot prom:

   ok boot net - install

In the case of a PXE boot this causes the client to send out a DHCPDISCOVER packet which is picked up by a local DHCP server. The DHCP server then replies by broadcasting a DHCPOFFER packet extended with PXE-specific options (extended DHCPOFFER) to port 68/UDP (DHCP client port). This packet has to be broadcast, since most PXE clients will configure themselves by DHCP and cannot provide their IP address in the extended DHCPDISCOVER. Therefore the client is identified by its GUID/UUID pair. In the case of a Sun Sparc or RS/6000 the client issues a RARP broadcast to determine its IP address. The RARP packet contains the client's Ethernet hardware address. The bootp server responds by providing the client an IP address and other information necessary to function on the network. This is the older classic model. Most modern host hardware now work using the PXE boot method.

2. Once the client has determined its network information, it continues the boot process, loading the install kernel and operating system from the boot/install server using TFTP (old model) newer operating systems can now access the kernel image using NFS or even HTTP. Provisions the operating system and installs it.

Netstarting details:

Now that I have identified the concepts and components needed you are ready to proceed with an actual installation: Kickstart (Linux) or JumpStart (Sun/Solaris).


Kevin's Public Wiki maintained and created by Kevin P. Inscoe is licensed under a
Creative Commons Attribution 3.0 United States License.

Back to my web site - http://kevininscoe.com

Edit - History - Print - Recent Changes - Search
Page last modified on December 07, 2009, at 06:26 PM EST