Contents |
The first important decsion that needs to be made is the hardware platform you wish to run the miru directory server upon. This will help decide which version you need to download.
| Media \ Hardware | Generic PC | Embedded |
|---|---|---|
| CD-ROM | OCEAN-classic.version.iso | OCEAN-embedded.version.iso |
| HDD/CF | OCEAN-classic.version.img | OCEAN-embedded.version.img |
| VMware | OCEAN-vm.zip | OCEAN-dev-vm.zip |
| NFS | developer1 | developer2 |
The developer options need to be manually built following the HOWTO: Create miru directory server PXE Developer Edition.
For testing a simple CD-ROM & Memory File System (MFS) system can be used, for a more permanent solution a floppy disk or USB storage device can be used, albeit a floppy disk will not be very useful for tftp images. Be aware that some computer BIOS do not support USB storage devices and will hang on boot. Here are the steps to follow.
If you are using a floppy disk or USB storage device you will have to make sure the BIOS boots from the CD-ROM first, please consult your motherboard vendors manual for further details.
↠ 
Follow the steps for a CD-ROM install and once running select option "7) Install on HDD, Compact Flash, or USB storage device". After completing reboot and remove the CD-ROM.
When you have a target machine with no CD-ROM device you can insert the HDD into another machine and transfer the image. This requires Linux or FreeBSD in order to use the dd command, a Linux LiveCD such as Knoppix or Ubuntu can be used for this process.
A compact flash card can be connected via a IDE HDD adapter to operate like a HDD, important to note that these devices are not hot swap, you need to powerdown before inserting or removing. Conveniently many new machines come with media card readers, or a USB external media card reader is available at a cheap price. Simply insert a new compact flash card into the reader and if you have Linux or FreeBSD install as the HDD Image Install or for Windows desktops the physdiskwrite utility from m0n0wall can be used.
Please refer to HOWTO: Create miru directory server PXE Developer Edition and HOWTO: Create miru directory server WRAP Developer Edition.
The factory defaults for the directory server are as follows:
Interface: lnc0 IP address: 10.0.0.78 Netmask: 255.255.25.0 Username: admin Password: miru Time zone: Etc/UTC NTP server: pool.ntp.org
Once the machine has been powered on and the directory server finished starting you should see a screen similar to this.
Failure to see such a screen could be due to one of the following.
The first two will require verification on your part, the third can be found by checking the FreeBSD website for further details, and for the latter please submit a ticket to Bugzilla.
Unless you are using VMware your network device is highly likely not going to be called "lnc0". You will need to reconfigure the LAN interface and reboot.
The default IP address is 10.0.0.78, for the VMware demo it is 10.82.6.2. For configuration on an existing network this will most likely require changing. Reconfigure the LAN IP address and you can then continue setup using the web management interface.
You will be prompted with a standard HTTP password dialog box, login with the default username "admin" and password "miru".
In order for DHCP clients to use DNS the directory server needs to be configured for your DNS servers. Select the "General Setup" page, add the IP address or addresses and save. For basic DSL / cable modem environments your router often acts as a DNS proxy and can be specified here, alternatively use the command ipconfig /all in Windows or view /etc/resolv.conf in Linux/BSD to view the settings your desktop is using.
For DHCP clients to connect to the internet or other networks they need the IP address of the local gateway or router. Select the "LAN" page underneath the "Interfaces" heading, enter your local gateway IP address and save.
For Ubuntu LTSP you will need to upload a Linux kernel, an initial disk image (initrd), a pxeboot program, and a pxeboot configuration file. Following the HOWTO: Convert Ubuntu to Diskless you should have the following files.
pxelinux.cfg/ pxelinux.cfg/default ubuntu.dapper/ ubuntu.dapper/initrd.img-2.6.15-23-386 ubuntu.dapper/vmlinuz-2.6.15-23-386 pxeboot.0
Create the two directories and upload the files with the "tftpboot/" page.
After uploading the files you can enable the TFTP service on the "TFTP" page under the "Services" heading.
Define the groups and users for your deployment. Normally Unix installations would create a unique group for each individual and then join each user to an organisational group, however it can be easier to simply create a "users" group and assign everyone to that. It is recommended to use IDs starting at 1,000 be sure not to conflict with any existing users on your systems. The web management interface requires creation of the group before the users can be added.
After you have added the users and groups you can configure the domain and enable the AD service using the "Active Directory" page underneath "Services" heading.
The directory server system has a DHCP service which provides PXE boot information to clients in order to operate without a disk. However many DSL routers also have a DHCP service and the two can conflict causing clients to get an IP address from whichever system responds faster. So disable the DHCP service in your DSL router, consult the vendor documentation for instructions on how to do this, and enable the DHCP service in the directory server.
If you have an administration desktop or other IP based appliances on your network you will want to make sure the DHCP service does not provide conflicting IP addresses. Enter the available range into the "DHCP" page underneath the "Services" heading.
You will probably want to specify "pxelinux.0" as the PXE boot filename as uploaded to tftpboot/.
If you are running a diskless Ubuntu LTSP server you will want to configure that machine to always receive the same IP address. In effect this is similar to a static IP address. You will need to find the MAC address of the server and choose an IP address outside of the DHCP range chosen. This IP address needs to be configured in Ubuntu in the /etc/hosts file and with the SSH keys in order for the secure login of LTSP clients to function.
© 2009 Novell, Inc. All Rights Reserved.
