LinMin Bare Metal Provisioning 6.2 User's Guide

Quick Start Guide

Hide Navigation Pane

Quick Start Guide

Previous topic Next topic Expand/collapse all hidden text  

Quick Start Guide

Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

LinMin Bare Metal Provisioning

Quick Start Guide

 

This Quick Start Guide summarizes how install your LinMin Server (and optional provisioning modules) and how to provision and image your first Linux, Windows and ESX/ESXi systems.

 

Prepare your System

 

For dual NIC configurations, please read this entire "Prepare your System" section: at the very end of this section you will find instructions for configuring dual NIC systems.

 

LBMP is delivered as a software appliance, where the customer supplies a dedicated physical or virtual system, configured to LinMin specifications, onto which LBMP is then easily installed, used and maintained. No other applications may be running on the system dedicated to running LBMP. The LinMin Server can be accessed remotely via Firefox browser, via API and via SSH should external services need to interact with LBMP.

 

Your LinMin Server must be installed on the same VLAN/subnet (the "provisioning subnet") as the systems to be provisioned or imaged. Switching from production subnet to provisioning subnet and back can be accomplished automatically using orchestration software to control IT software, systems and switching equipment.

 

It is very important that you configure your environment as specified by LinMin otherwise your installation will fail or be unstable. If you follow the guidelines below, you will become productive immediately.

 

If running on a VMware Virtual Machine, your host hypervisor must be ESXi, not ESX or Workstation. With LBMP running on an ESX-hosted VM, provisioning ESXi will corrupt your ESX host.

 

Install Red Hat Enterprise Linux 5.6 (properly registered with # rhn_register) or CentOS 5.6 (64-bit or x86_64 only). Installing LBMP on RHEL 6.x or CentOS 6.x is not supported at this time. If you are not a Red Hat subscriber, download CentOS, burn it to a DVD and install this 64-bit operating system on a system (2 GHz with 512MB RAM or better, 100GB disk or better). We find that installing a simple Gnome desktop makes it easy to use the browser on the LinMin Server itself, while providing a Windows-like environment. When installing 64-bit RHEL or CentOS, accept all defaults including the language US/English (en_US.UTF-8) except for your time zone: this entire OS installation should be a Click "Next" - Click "Next" process. Do not add or remove packages/applications afterwards, do not change paths or make any other modifications to your installation unless indicated in this User's Guide. All necessary system software components (PostgreSQL, dhcp, NFS, Samba, PHP, Perl, etc.) will be downloaded and configured automatically during the LinMin Server installation.

 

Configure your system's clock with ntpd and set your time zone

 

Update your system with yum. If you have Internet access, upon issuing the command yum -y update, your system will become current and you establish the yum path required by the LinMin Server. If you require proxy access or have an in-house repository, configure the yum.conf file and establish the persistent connection required to install the LinMin Server, then execute the yum -y update command. After you update the system, reboot the system, regardless of whether you are prompted to do so or not. Remember: your yum connection must be persistent, such that you can execute yum -y update successfully from the command line without any parameters. If using RHEL 5.6, ensure that you use a RHN Channel that updates your RHEL 5.6 and does not upgrade your system to RHEL 6.x.

 

Make sure your existing DHCP server ("authoritative", meaning it hands out IP addresses/leases) does not service PXE boot requests: configure your existing DHCP server to forward these PXE boot requests to the LinMin Server's IP address). For complex networking environments please review the LinMin Server Configuration topic.

 

Firewall: either turn off your system firewall (if you are in a firewall-protected environment) or open the ports needed during the LinMin Server installation.

 

Identify 2 ranges of contiguous LBMP-dedicated PXE IP addresses used for provisioning and imaging, as you will be prompted for it when you install the LinMin Server. These IP addresses are automatically managed by the LinMin Server and are not to be used for any other purpose, e.g., they must not be assigned as static IP addresses for provisioned systems by LBMP users and they must be on the LinMin Server's subnet/VLAN. Starting with LBMP 6.2, the LBMP-dedicated PXE IP range is broken into 2 ranges: the "PXE Boot IP" range (defaulting to .151 to .160) and the "PXE Event IP" range (defaulting to .161 to .200). We recommend a mix of 20% PXE Boot IPs and 80% PXE Event IPs. For releases prior to LBMP 6.2, the default range of LBMP-dedicated PXE IPs is .151 to .200 as both ranges were combined. Read more about PXE IP Address Pre-Assignments. If necessary, ask your network administrator to provide the range of available IPs on your subnet/VLAN.

 

Assign your system a static IP address:

If you do not assign a static IP address to your system and specify your Network, Broadcast, DNS, Gateway and Netmask in the file ifcfg-eth(x) (where x is the Ethernet port number) before installing the LinMin Server, your client systems may not be able to be provisioned or imaged.

 

Remember: the LinMin Server must reside on the same subnet/VLAN where the systems to be provisioned or imaged reside.

 

Edit the file ifcfg-eth0 (if you are using Eth0):

/etc/sysconfig/network-scripts/ifcfg-eth0

 

Before: a typical system with a dynamic IP address:

 

DEVICE=eth0

HWADDR=00:11:09:2E:B4:05

ONBOOT=yes

BOOTPROTO=dhcp

 

After: the same system with a static IP address

 

DEVICE=eth0

HWADDR=00:11:09:2E:B4:05

ONBOOT=yes

# Please note to change BOOTPROTO=dhcp to BOOTPROTO=static

BOOTPROTO=static

# Enter your IP, Netmask, Network, Broadcast, Gateway and DNS information

IPADDR=192.168.0.222        

NETMASK=255.255.255.0

NETWORK=192.168.0.0

BROADCAST=192.168.0.255

GATEWAY=192.168.0.254

DNS=192.168.0.254

 

Caution: do not have duplicate entries in the ifcfg-ethx files. Duplicate entries will cause provisioning failures.

 

Restart your network services

 

service network restart

yum check-update (to ensure you have yum access)        

 

If you are using VMware (ESX or Workstation), shut your system down and clone it. Start your fresh clone and reboot it, take a snapshot (e.g., "Before LinMin Server Installation"), then proceed to install the LinMin Server. Note: these reboots are required to clear VMware caches and provide a stable system, and the snapshot you take before installing the LinMin Server may come in handy later.

 

Dual NIC Configurations

 

The following are the recommended steps for installing LBMP on systems with 2 Network Interface Cards.

 

In this example, provisioning and imaging functions will take place on the LinMin Server "Provisioning VLAN" (a full 10.49.49.0 class C subnet) on Eth0 and external access (to the Internet for RHEL and CentOS installations, or  to your Red Hat Network Satellite for RHEL) will be enabled through a "Public VLAN" (a full 192.168.0.0 class C subnet) on Eth1.

 

Your license key will be tied to the MAC address of the LBMP Provisioning VLAN (in this example, the 10.49.49.0/24 VLAN & Eth0 NIC).

 

Prior to installing the LinMin Server, configure both NICs to have static IP addresses (and static MAC addresses if your hardware allows dynamic MACs).

 

Configure your /etc/sysconfig/network-scripts/ifcfg-eth0 (this is your 10 dot private VLAN) file to have DNS and Gateway IP addresses that are part of your Eth1 Public VLAN. For example:

 

GATEWAY=192.168.0.254

DNS=192.168.0.254

And restart network services:

service network restart

yum check-update (to ensure you have yum access)

 

Now proceed with the LinMin Server installation.

 

After installing the LinMin Server, you must edit the /etc/dhcpd.conf file and change DNS and Gateway (called "routers") IP addresses from 192 dot to the IP of  the LinMin Server. These are valid IPs to satisfy the dhcp clients. Note that no gateway routing or DNS service is provided to the clients in this Release 6.2. A future release will support both DNS relay and HTTP relay.

From:

option domain-name-servers 192.168.0.254;

option routers 192.168.0.254;

To:

option domain-name-servers 10.49.49.1;

option routers 10.49.49.1;

 

Then:

cd /usr/local/linmin/

./linmin-services restart

 

 

 

Installation or Upgrade

 

Login to the LinMin Server as "root" user.

 

Create a directory then copy the installable .exp files you downloaded and your license key file to this directory:

mkdir /usr/local/linmin             (copy the downloaded “.exp” file(s) to this directory)

 

Go to the directory and install the base LBMP package. You will then be prompted to reboot:

cd /usr/local/linmin

sh linmin-bmp-{version#}.exp   (do not interrupt the 15-20 minute process)

 

If this is an upgrade from a prior version of LBMP, back up files you have modified (e.g., control files) just in case, then run the same script and select the "Upgrade" option when prompted.

 

After rebooting your system, your LinMin Server is now installed and operational.

 

If you have a release prior to LBMP 6.2, continue with the following steps to install your license key and the optional WPM and EPM packages.

 

If you were not prompted to install the license key during the LinMin Server installation, now install the license key file you received from LinMin after providing the MAC address of your LinMin Server:

sh yourcompany_{key_details}_lbmp.exp    

 

Install the Optional Modules, e.g., WPM, the Windows (Server 2008 and Windows 7) Provisioning Module, or EPM, the VMware ESX Provisioning Module:

sh linmin-wpm-{version#}.exp

sh linmin-epm-{version#}.exp

./linmin-services.sh restart

 

Login using the default User Name "admin" and Password “admin”, and check the Help/About page to see your installed license keyinformation. If you fail to see the login screen, troubleshoot "Unable to Connect".

 

 

Troubleshooting the Installation and Contacting Support

 

If you experience problems, consult the Troubleshooting the LinMin Server Installation topic. Read each scenario and try to recognize the problem you experienced, then resolve the situation.

 

Should you need to contact Support, first generate a .help file (this captures your system’s settings):

cd /usr/local/linmin

./linmin-bmp-support-help.sh

 

Then email LinMin-Support@LinMin.com the resulting “lbmp-supporthelp_{timestamp}*.help” file with a detailed description of what you experienced and the messages you saw. Screen shots are always very helpful.

 

Do not alter the .help file. Email it as it is: do not zip or otherwise compress the .help file, nor change its extension. Such help files received in other formats fail automated pre-processing and will delay providing you with a response.
 
Support .help files are already in "bz2" compressed format with a .help file extension. This format and file extension pass all known email security/spam filters. Other file formats and extensions, e.g. .zip, can be blocked or delayed.

 

Provision your first Linux system

 

The steps below summarize the information found in the "Provision Red Hat or CentOS" tutorial:

 

1) Prepare your Linux ISO media

 

Copy your Red Hat Enterprise Linux or CentOS 5 ISO to /home/tftpboot/ISOs/linux. Next, prepare your ISO file:

cd /home/tftpboot/bin

perl loadlinux.pl                   (then select your Linux distro)

 

2) Use the GUI to Create a Provisioning Role:

 

Open Firefox (the only supported browser) and go to <your LinMin Server's IP address>/tftpboot (e.g., 192.168.0.243/tftpboot)
Login using the default User Name "admin" and Password “admin”

 

Click “MAC-Independent Provisioning”, click “Add a System Role” (Red Hat type) and select from the drop-down Red Hat Enterprise Linux (or CentOS) 5.5 i386, then click “OK”
You now see the Red Hat (or CentOS) MAC-Independent Role that you created.
Click “Enable MAC-Independent Provisioning”

 

3) Power on the system you want to provision

 

Hit F12 to force a network boot and you will see the message “Welcome to the LinMin Server”
Press “1” (to select the role you created) and press the Enter key.  Your system will be provisioned automatically. The default password at installation time for client systems is “unsecure”.

 

If you ran into a problem, please review our Troubleshooting the Client topic.

 

Next steps: review this User’s Guide and start using MAC-Specific provisioning and disk imaging.

 

Provision your first Windows Server 2008 or Windows 7 system

 

The steps below summarize the information found in the "Provision Windows Server 2008 and Windows 7" tutorial:

 

You must have the optional Windows Provisioning Module (WPM) installed to provision Windows Server 2008 and Windows 7.

 

1) Prepare your Windows ISO media and create an “Installation Instance”

 

Copy your Windows Server 2008 or Windows 7 ISO to /home/tftpboot/ISOs/windows/win7_2008/.

 

cd /home/tftpboot/bin

sh windows-create-install-instance.sh       (answer questions to prepare the media and create your Install Instance)

 

2) Use the GUI to Create a Provisioning Role:

 

Open Firefox (the only supported browser) and go to <your LinMin Server's IP address>/tftpboot (e.g., 192.168.0.243/tftpboot)
Login using the default User Name "admin" and Password “admin”

 

Click “MAC-Independent Provisioning”, click “Add a System Role” (Windows type) and select from the drop-down Windows Server 2008 R2 (if that is the Install Instance you created), then click “OK”
You now see the Windows MAC-Independent Role that you created
Click “Enable MAC-Independent Provisioning”

 

Power on the system you want to provision

 

Hit F12 to force a network boot and you will see the message “Welcome to the LinMin Server”
Press “1” (to select the role you created) and press the Enter key.  Your system will be provisioned automatically. The default password at installation time for client systems is “unsecure”.

 

If you ran into a problem, please review our Troubleshooting the Client topic.

 

Next steps: review this User’s Guide and start using MAC-Specific provisioning and disk imaging.

 

Image your first Linux or Windows system

 

The steps below summarize the information found in the "Imaging" tutorial:

 

Before you begin, make sure that the system you image has been backed up by other means.

 

1) Use the GUI to Create an Imaging Profile:

Open Firefox (the only supported browser) and go to <your LinMin Server's IP address>/tftpboot (e.g., 192.168.0.243/tftpboot)
Login using the default User Name "admin" and Password “admin”

 

2) Create an Imaging Profile

Click “MAC-Specific Imaging”, click “Add MAC-Specific Profile”
Enter a Unique Profile Name (e.g., server213)
Enter the MAC address for the client system you will image (format is 00:11:22:33:44:55)
Enter a directory name (e.g. server213_windows_test)
Enter the drive type (hint: most hardware uses SATA drives, so enter “sda”)
Click “OK”

 

3) Set the Imaging Profile to "Backup"

On the “MAC-Specific Imaging” page, select the system you created the profile for and click the button with the green check mark (and notice the text “Backup” appear)

 

4) Power on the system you want to image

 

Hit F12 to force a network boot and you will see the message “Automatic imaging in progress ”
When the imaging is complete, your system will reboot

 

5) Perform a "Restore":

Change the contents of the system you just backed up (add/remove icons on the desktop, or rename/copy directories) so you can easily notice when you roll your system back to the image you just created
On the “MAC-Specific Imaging” page, select the system you created the profile for and click the button with the yellow triangle (and notice the text “Restore” appear)
Power up your client system as directed above. When your system reboots, it will have restored the image you backed up a few minutes earlier
You have now successfully used imaging!

 

If you ran into a problem, please review our Troubleshooting the Client topic.

 

Release Notes