 | |||||||||||
| |||||||||||
 |
|||||||||||
| |
| ||||||||||||||||
| ShaoLin Aptus 2.0 Installation and Operations Guide | ||
|---|---|---|
| Prev | Chapter 5. Quick setup with Aptus Configurator | Next |
After you created your group, the system will bring you to create the first Aptus client. A client record need to be created in order to allow the client to connect and boot from the server.
Your client and server should be located or connected within the same physical network. This is because the server needs to receive broadcast messages from the client. Make sure you check the connection before proceeding to the next step. A crossover cable will be the best choice to ensure no interruption for testing the first time setup.
You have to turn on the clients and using a special way of booting instead of using your local hard drive. There are generally 2 ways to boot an Aptus client, use PXE or Etherboot.
If you have disabled the PXE boot rom , you will have to re-enabled the PXE boot rom at the BIOS or the PXE firmware used to have their own setup interface. Usually they can be entered with a key-stroke (e.g.Ctrl-S) , please refer to your boot up console message or operation manual of your NIC.
If the PXE has been activated, you should see some message "DHCP ........." . At this point, the client cannot connect to the server yet until a proper client profile has created at the server.
If you don't have PXE bootrom on your ethernet adapter, you should have your client boot disk ready, if not please go to Chapter 6. Put in the Aptus client boot disk into the client machine, please enable boot from floppy or you will have to change this setting usually in the BIOS setup screen. To enter the BIOS screen, hit the 'Delete' key on startup, some system may use a different keystroke. When you client boots up with the boot floppy, you will see a menu. Hit "N" to boot from network (default), it should show a message "Searching for Aptus server...". if you don't see this message, you may have created a wrong boot disk with the wrong driver. Please check your network hardware. You can choose to boot to local disk by hitting "L" at boot disk startup.
If everything goes fine, you should see the message "Searching for Aptus server", by this time, your client will timeout and retry again and again. This is a correct behavior, because you have not setup the server to recognize this client yet.
If you have enabled detect unknown Aptus host for your network configuration, you click on to the "Detected unknown Aptus hosts" page. You should see a detected record with MAC address and time. You may click on to the record, then a page of group selection will come up. Select the group you wish to add this client into, then hit "OK".
When creating a host, the Aptus configurator actually create an entry in the configuration file /etc/var/opt/aptus/var/opt/aptusd.conf and create a copy of hostfs in "/var/opt/aptus/<groupname>/hosts/<hostname>/". This directory we called it hostfs is a file system (or a directory) contains all the files belong to this host (the host now you intend to create). The files under this hostfs will later be seen (by the client) in the root ( / ) of the client's context (at the client's point of view).
The host name of the Aptus Client must be unique, it does not accept spaces and special characters.
If you have autodetect enabled, you will just have to type in the IP address. Or please type in the MAC address you copied from the client screen, if you have not obtained the mac address, please go Section 5.7.3.2. If you have multiple subnets, you can select the desired subnets to add your host into, Aptus configurator will choose the correct subnet by default(If you are adding a detected host). Aptus configurator automatically suggest the next available IP address in the subnet, if you have other clients in the network please verify the IP address is not in used by another client. You will also need to specify the default gateway of the client if you want the client to reach the outside network or the Internet.
You will need to specify the number of CPUs so that the to keep the license valid. Using the wrong number of CPU will cause your Aptus client unable to startup properly.
lease select the correct boot image for you client, it depends on the processor type and network adapter type that you are using. The files default locations are in "/tftpboot/kernel" named with "<kernelversion>-<arch>-<netdevice>.nb". If you choose the wrong file, the client won't boot. Please use the latest boot image named "LATEST-<arch>.nb", the default is to use LATEST-i586.nb .
