Using UberJS Server


Home
UberJS Standard
UberJS Server
Links

Once an UberJS CD is created with all of the configuration files, using it is very simple.
UberJS Server follows the same initial network configuration steps as UberJS, so the documentation is very similar.
 

Booting the CD

1. Hit Stop + A on the keyboard
2. At the ok prompt, type "boot cdrom" and hit enter

 

Bringing up the network

UberJS will configure /dev and /devices and proceed through the initialization phase.
You should see an "UberJS Server v1.2.0 with NetInit v3.04.10 Booting" message.

If the machine is using DHCP, either because of a tag in the ipethers file or for lack of a specific configuration for your machine, UberJS will try and configure DHCP first. After UberJS receives an IP address from the DHCP server, it will prompt you to accept the IP with a y/n prompt. If the IP is acceptable, please type "y" and hit enter. If the results are not desirable and you wish to input an IP address manually, type "n" and hit enter.

If DHCP was successful, your network is now completely configured. The IP address, default router, and netmask should all be configured and the system will move to the NFS mounting phase.

If DHCP was not successful or you chose to input an IP address, you will be prompted for it. Enter the machines IP address and hit enter.

If no netmask file was found, you will be prompted to input the netmask. Usually 255.255.255.0 is safe, but 255.255.0.0 is sometimes used.

Next, a default router will be determined automatically. If one is not found, you will be prompted for that as well. If you do not know your default gateway, ask your system administrator

At this point, manual network configuration is complete and the system will move on to the client configuration stage of UberJS Server.

 

Adding Install Clients

Once UberJS Server is booted, we recommend that you use the Assisted add_install_client (AIC) setup option. Answering no to the prompt will result in a commandline and you will need to run /InstallTools/uber-aic with standard add_install_client options, but that is beyond the scope of this document. Type "y" and hit enter.

Your system administrator should provide you with the answers to these questions, the explanations of what some of these are is complicated and beyond the scope of this document.

You will first be asked if the machine will receive DHCP IP and bootparams info. If your network contains a DHCP server that will assign an IP address and provide you with NFS server paths, answer "y" and hit enter. Most likely you will want to answer "n" and hit enter.

If you answered no to the last question, you will be asked whether the machine will ultimately be booted as DHCP, if you want to boot with bootparams provided NFS paths but have the system come up ultimately as DHCP via the network_interface= line in sysidcfg, answer "y" and hit enter, most likely this is what you will want. Otherwise, answer "n" and hit enter.

If you answered no to the last question, you will be asked for an IP address for the machine, you may leave this blank in most cases, but your administrator may tell you to fill something in. If you are leaving it blank, simply hit enter. Otherwise, type the ip address and hit enter.

The next thing you will be prompted for is the machine MAC address, this usually looks something like 8:0:20:c0:ff:ee. To discover your mac address, on the machine you will be building, type Stop + A and at the ok prompt, type reset. When the screen comes back up, the MAC address will be displayed. You may desire to hit Stop+A when you see "Initializing Memory". Type the mac address in exactly as it appears on the machine you will be building and hit enter.

Next you will be prompted for the NFS Install path. This is NFS path to the directory containing the Solaris_9 directory, your administrator should provide you with this. Type the path and hit enter. It should look something like your.server.path:/export/solaris9/jumpstart

Next, you will be presented with a prompt for the NFS Install Config path, this is the NFS path where your profile/rules.ok is, and again your system administrator should provide this. Type the path and hit enter.

Next, another prompt for the NFS Sysid Config path will appear. This is the NFS path to the directory containing the sysidcfg file for your machine. Enter the path provided by your administrator and press enter.

Now you will be prompted for the client name, please enter the fully qualified DNS name of the machine you will be building and hit enter. This should look something like yourcomputer.yourdomain.com.

Lastly, you will be presented with the information you entered, the command that will be run, and given a chance to confirm that all of the information is correct. If everything looks correct, type "y" and hit enter. After a moment, your server should be configured and ready to boot the client machine. If you wish to boot more than one machine, answer "n" that you are not done adding machine and hit enter and follow the directions for this section again for the new machine. If you are done, answer "y" and hit enter.

If you answered "y", you will be returned to a command line. At this point you may start building the client machine. Do not touch the server until all clients have finished building and are rebooted.

 

Booting the client machine

Simply type Stop + A then at the ok prompt, type "boot net - install" and hit enter. The machine should proceed through the installation without further prompting, provided a correct sysidcfg file is on the server. If the Sun installer requires information, your system administrator should provide you with it.

Wait until the client build finishes and the client machine reboots before shutting down/rebooting the server.

 

Thank you for using UberJS!


Home UberJS Standard UberJS Server Links

 For problems or questions regarding this Web site contact uberjs@iastate.edu.
Last updated: 11/01/03.