Using Egenera Virtualized Boot Services

Size: px

Start display at page:

Download "Using Egenera Virtualized Boot Services"

Cassandra Anastasia Ross
5 years ago
Views:

1 Using Egenera Virtualized Boot Services For BladeFrame BF400 S2 and BladeFrame BF200 Document Number 432-SB0045 September 2008 EVBS1.0_BF_1

2 Copyright Copyright 2008 Egenera, Inc. All rights reserved. This document, and the product described in it, is furnished under license and may only be used in accordance with the terms of such license. The content of this document is furnished for information purposes only and is subject to change without notice. Egenera, Egenera stylized logos, BladeFrame, BladeLatch, BladeMate, BladePlane, cblade, Control Blade, PAN Manager, pblade, Processing Blade, sblade, and Switch Blade are either registered trademarks or trademarks of Egenera, Inc. in the United States and/or other countries. PRIMERGY is a registered trademark of Fujitsu Siemens Computers. AMD, AMD Opteron, and AMD Athlon are trademarks of Advanced Micro Devices, Inc.. EMC, CLARiiON, and Symmetrix are registered trademarks of EMC Corporation. The IBM Developer Kit for Linux, Java 2 Technology Edition contains software which is copyright IBM Corporation, Sun Microsystems Inc., Hewlett-Packard Co., and X Consortium. Intel and Itanium are registered trademarks and Xeon is a trademark of the Intel Corporation in the United States and other countries. Sun, Sun Microsystems, the Sun Logo, Solaris, and the Java logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. Linux is a registered trademark of Linus Torvalds. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. The virtual VGA console uses Microsoft Terminal Services Advanced Client (TSAC), which is a copyright of Microsoft Corporation. MindTerm is copyright AppGate AB. Nero is a trademark of Nero AG. NetApp is a registered trademark and Network Appliance is a trademark of Network Appliance, Inc. Oracle9i is a trademark of Oracle Corporation. Red Hat is a registered trademark of Red Hat, Inc. in the United States and other countries. SUSE is a registered trademark of SUSE LINUX Products GmbH, a Novell business. VMware, Virtual SMP, and VMotion are registered trademarks or trademarks of VMware, Inc. Xen, XenSource, XenServer, and XenEnterprise are either registered trademarks or trademarks of Citrix Systems, Inc. in the United States and/or other countries. All other company and product names are trademarks or registered trademarks of their respective holders. Printed in the United States of America. Egenera, Inc., 165 Forest Street, Marlboro, Massachusetts

3 Preface Welcome to PAN Manager PM5.2_BF. Using Egenera Virtualized Boot Services is part of the PAN Manager documentation set. Its purpose is to describe the EVBS feature. Audience Using Egenera Virtualized Boot Services is for PAN Administrators. Topics Read this book to learn the following about boot services: Concepts, requirements, and restrictions Administration Commands Related installations Documentation Set To learn about the other documents available in the PAN Manager documentation set, see Chapter 2, Document List, of PAN Manager Feature Summary. Platform-Specific Product Features To learn about the PAN Manager features available in the current release, see Chapter 3, Feature List, of PAN Manager Feature Summary. PM5.2_BF v

4 Using Egenera Virtualized Boot Services Customer Support If you require customer support regarding this product, use the following contact information. Fujitsu Siemens Computers customer support Internet Telephone See the Help Desk information at manuals.fujitsu-siemens.com/ primergyservers.html under General Information, Warranty and Support. Document Conventions Convention Description > Directory-level delimiter used to navigate the left pane of the PAN Manager GUI. Example: Resources > Ethernet Connections Sans serif italics Variable text, such as a path, a filename, or an LPAN name. Example: lpan -c lpanname Sans serif Text that must be typed as shown. Example: Type root at the login prompt. vi PM5.2_BF

5 Preface Convention Bold Italics [text] {text} Description The name of a field or window element appearing in a GUI. It also highlights default values in PAN Manager man pages. Example: In the Users page... Text that is emphasized. Example: Do not connect the power. Text that is optional to a command. A set of choices, one of which is required. Separation of mutually exclusive choices in syntax lines. Example: lpan [-ad -rd]{switch SCSI_ID} lpanname Note Caution! Information of importance or that may not fit in main text. Failure to heed a caution could result in loss of data. Warning Failure to heed a warning could result in physical harm to the user or the hardware. PM5.2_BF vii

6 Using Egenera Virtualized Boot Services viii PM5.2_BF

7 Chapter 1 About Egenera Virtualized Boot Services This guide describes how to use Egenera Virtualized Boot Services (EVBS). This chapter provides a description of the features and the requirements for EVBS. The topics include: Introducing EVBS Compatibility PM5.2_BF 1-1

8 Using Egenera Virtualized Boot Services Introducing EVBS EVBS is a flexible pre-boot environment. EVBS lets you boot a pserver directly from a variety of devices. To enable network boots, EVBS implements the Preboot Execution Environment (PXE) standard. This standard calls for a PXE server to transfer a boot image over the network. EVBS also lets you control the boot device order. 1-2 PM5.2_BF

9 About Egenera Virtualized Boot Services Compatibility This section lists: Firmware level Media drives PXE tools that EVBS supports. Hardware Compatibility You need a minimum firmware level of MasterBlaster 42.2 on the pblades. Software Compatibility Virtual CD is only supported on PAN Manager release 5.1 or later. You can use the following PXE tools with EVBS: PXE Tool Windows SLES 10 Solaris Altiris Deployment Solution Yes Yes No Fujitsu Siemens Computers ServerView Installation Manager Yes No No Microsoft Windows Deployment Services Yes No No PXELinux No Yes No Some PXE deployment tools require the booting server s network interface to present a unique identifier. EVBS uses the pserver s MAC address as this identifier. A MAC address is automatically PM5.2_BF 1-3

10 Using Egenera Virtualized Boot Services generated when a Virtual Ethernet interface is created for a pserver. (A Virtual Ethernet, veth, is an interface with the equivalent functionality of a physical NIC.) 1-4 PM5.2_BF

11 2 Using EVBS to Boot a pserver EVBS is the mechanism by which PAN Manager boots pservers directly from a boot device. The boot devices among a pserver s configured resources may be CD-ROMs, Virtual CD-ROMs (VCDs), SAN disks, or veths through which a PXE server on the network is available. About EVBS Behavior To boot a pserver using EVBS, you use PAN Manager to do the following: Select the pserver. Specify EVBS as the boot image. (Optional) Indicate your preference among boot devices. Release

12 Using Egenera Virtualized Boot Services EVBS can scan the pserver s assigned resources, looking for a device that provides a bootable operating system image: If you specify a boot device or a scan order, EVBS boots the pserver from the specified device or from the first viable device that the scan uncovers. If you do not specify a boot device or a scan order, EVBS presents a timed menu of all the devices that provide a bootable operating system image. You then select a device, or (after 15 seconds) allow EVBS to boot from the first viable device in the default scan order. If EVBS does not find a suitable device, it generates a failure message and performs a warm reset of the pblade. This means that EVBS tries to find a suitable device again after the attempted boot. If enough resets occur, PAN Manager forces a failover to another pblade. Booting a pserver with EVBS This section explains how to use PAN Manager to initiate a pserver boot using EVBS. The sections that follow provide more information about EVBS behavior with and without the optional boot argument (scan order). To boot a pserver with EVBS: 1. On the pserver Dashboard page, click a pserver name. 2. On the pserver_name page, do one of the following: Click the Boot icon (the blue Up arrow) at the bottom of the page to bring up the Boot pserver dialog box. If you want to add boot arguments (or choose a non-default boot image), click Override in the Boot pserver dialog box. This adds the boot arguments for this boot only. 2-2 Release 1.0

13 Using EVBS to Boot a pserver Scroll down to the Boot pserver section and click Modify to bring up the pserver Boot Image / Options dialog box. When you add arguments in this dialog box, they persist to the next boot. 3. In the pop-up dialog box (Boot pserver dialog box or pserver Boot Image / Options dialog box), select the EVBS image. Note: The drop-down menu also includes operating system boot images registered with PAN Manager. These menu options are primarily useful for installing pservers operating systems. If at boot time you choose a registered operating system image rather than EVBS, the pserver will boot from that image without EVBS involvement. 4. (Optional) In the same pop-up dialog box, supply User-Defined Boot Arguments to specify a device or the desired order in which to scan the pserver s assigned devices for a bootable operating system image. For argument syntax, see Using EVBS With Boot Argument on page Click Submit. If you supplied a boot argument, EVBS then boots the pserver from the device specified or from the first suitable device found. If you did not supply a boot argument (default), EVBS scans for suitable devices and presents a timed menu from which you can choose a boot device. For details on EVBS default scan behavior, see Using EVBS Without Boot Argument (Default) on page 2-4. Release

14 Using Egenera Virtualized Boot Services Using EVBS Without Boot Argument (Default) If you do not provide the boot argument when you boot the pserver, EVBS goes through the following process: 1. EVBS scans the pserver s disk0. 2. If disk0 is enabled, EVBS places it in the device selection menu. 3. EVBS scans for the physical media drives on each cblade as well as the pserver s VCD. If any of these are present, EVBS adds them to the selection menu. If multiple devices are found, EVBS presents them in the following order: 1-Virtual CD-ROM 2-CD-ROM inserted in cbladea 3-CD-ROM inserted in cbladeb 4. EVBS scans for the presence of veth0. 5. If veth0 is present, EVBS adds this device as the last one in the selection menu. 6. EVBS prints the device selection menu to the console. If you do not make a selection before a 15-second timeout, the pserver boots from the hard disk. If the disk is unavailable, EVBS does not continue. If the disk does not boot and EVBS hangs, make sure the pserver is configured with a viable boot disk. Note: If only one device is available after the disk, media drive, and veth scans, EVBS still prints the menu to the console. 2-4 Release 1.0

15 Using EVBS to Boot a pserver Using EVBS With Boot Argument Using the boot-order argument, you can instruct EVBS to do the following: Boot from a single device. Scan for specified devices and boot from the first device found. Scan for a class of devices and boot from the first device found. Scan for multiple classes in specified order and boot from the first device found. If you use the boot-order boot argument when you boot the pserver, EVBS does not provide a menu. EVBS uses classes with the boot-order argument. Classes are different device types that EVBS scans. These include disk, media drive, and veth. When you use the boot-order argument, EVBS restricts the scan to a finite number depending on the class. You can specify classes in any order in the boot-order argument: disk EVBS scans disk0 (you can use disk0 or disk in the argument). If disk0 is enabled, EVBS boots from the disk. If EVBS cannot boot disk0, EVBS does not continue. If the disk does not boot make sure the pserver is configured with a viable boot disk. cd EVBS can scan three drives: cd0 (VCD), cd1 (cbladea), and cd2 (cbladeb). When EVBS finds a bootable media drive, EVBS boots from the CD. If EVBS cannot boot from a media drive, it moves on to the next class. veth EVBS scans the veth and starts a PXE boot request on the pserver s veth0 device (the default veth used for PXE). Release

16 Using Egenera Virtualized Boot Services If a PXE server responds to the request, EVBS initiates a PXE boot. If EVBS cannot boot using a veth, it moves on to the next class. With the exception of management veths, you can use any of the pserver s assigned veths for a PXE boot. You can only use one veth, however, to support PXE activity for a specific boot. You cannot, for example, use a DHCP server on one veth s network and a PXE boot server on another veth s network. Configuration is required prior to using some PXE tools. For more details, see Chapter 3, Configuring PXE Tools to Use with EVBS. If EVBS cannot find a device to boot from, it writes a failure message to the remote console and performs a warm reset of the pblade. Argument Syntax Examples This section provides examples for using the boot-order argument. In the following example, EVBS boots from cd2: boot-order=cd2 In the following example, a PXE boot is attempted. If EVBS cannot locate a PXE server, it boots from cd2. If EVBS cannot boot from cd2, it boots from disk: boot-order=veth,cd2,disk Note: You can use semi-colons (;) to delimit devices as well. Ordering Rules The following rules apply to specifying boot-order arguments: When establishing an order, you cannot use a class with a specific member of the class. The following example is incorrect: boot-order=cd,cd2 Either use just the class: 2-6 Release 1.0

17 Using EVBS to Boot a pserver boot-order=cd or specify the order you want within the class: boot-order=cd2,cd0,cd1 You cannot specify more than one veth; however, you can change the default veth0. In the following example, a PXE boot occurs using veth9. boot-order=veth9 Release

18 Using Egenera Virtualized Boot Services 2-8 Release 1.0

19 Chapter 3 Configuring PXE Tools to Use with EVBS This chapter discusses using PXE tools with EVBS. For the latest PXE tool information, download this book from In order to boot pservers over a network, EVBS uses PXE and requires one of the following PXE tools: Altiris Deployment Solution Fujitsu Siemens Computers ServerView Installation Manager Microsoft Windows Deployment Services (WDS) PXELinux With the exception of Fujitsu Siemens Computers ServerView Installation Manager, the PXE tools require the addition of Fujitsu Siemens Computers virtualized extensions. Instructions are provided below. EVBS supports network booting for the following operating systems: Microsoft Windows Server 2003 SUSE Linux Enterprise Server 10 PM5.2_BF 3-1

20 Using Egenera Virtualized Boot Services To see which PXE tools boot which operating systems, see Software Compatibility. Configuring WinPE 2.1 You need to configure WinPE 2.1 before you can use deployment tools with EVBS. The configuration includes, mounting the WinPE 2.1 image, installing the virtualized extensions, and unmounting the image. Prior to integrating Fujitsu Siemens Computers virtualized extensions into WinPE 2.1, note the following: For the WinPE PXE preparation, do not use the virtualized extensions needed for the Microsoft Windows Server 2003 pserver installation. If you use the operating system extensions, then unexpected behavior could result. You must use the WinPE 2.1 specialized extensions. These extensions are included in the Fujitsu Siemens Computers WinPE 2.1 integration package. You can download this at support. Do not use the WinPE 2.1 extensions for Windows 2003 pserver operating system installations or updates. The extensions have been modified for WinPE 2.1 and may not be compatible with the Windows 2003 operating system. Requirements You need the following to do the integration: PAN Manager PM5.2_BF or higher Fujitsu Siemens Computers WinPE 2.1 integration package This includes: Egenbmc.inf Egenbmc.sys 3-2 PM5.2_BF

21 Configuring PXE Tools to Use with EVBS Egenbus.inf Egenbus.sys EgenDisp.dll EgenExp.sys EgenKbd.inf EgenKbd.sys EgenKbdInst.dll Egenkvm.inf EgenKVM.sys Egenlink.inf Egenlink.sys EgenMous.inf EgenMous.sys EgenMousInst.dll egennet.inf EgenNet.sys EgenNetInst.dll Egenscsi.inf EGENSCSI.sys EgenVga.sys EgenVVGAClsCoInst.dll EgenVVGAClsI.dll Egenxpt.inf, Egenxpt.sys WinPE 2.1 WIM image ImageX A tool that enables you to mount WIM images for modification. PEImg A tool that enables you to install drivers (virtualized extensions) into a WIM image. PM5.2_BF 3-3

22 Using Egenera Virtualized Boot Services The WIM image, ImageX, and PEImg are packaged in the Windows Automated Installation Kit (WAIK). This is a free download available from Microsoft. To configure WinPE 2.1: 1. Copy all of the Fujitsu Siemens Computers WinPE 2.1 integration package onto the local system. Make separate directories for 32-bit and 64-bit files. For example: c:\egenwinpefiles\x86 c:\egenwinpefiles\x64 2. Mount the source WinPE 2.1 image for read/write access using the imagex.exe tool provided in the WAIK: Imagex /mountrw c:\source\winpe.wim 1 c:\temp\winpemount where: /mountrw is the ImageX command used to mount the WinPE image providing read/write capabilities. c:\source\winpe.wim is the source image (and ultimately the destination image). 1 is the index of the internal image in the WIM file. c:\temp\winpemount represents the destination directory that will be used as the mount point. This directory must exist and must be empty. Once the mount command completes, the source image will appear as a set of subdirectories in this directory. 3. Install the Fujitsu Siemens Computers virtualized extensions provided in the WinPE 2.1 integration package using the peimg.exe tool: Peimg /inf=c:\egenwinpefiles\x86\egenbmc.inf c:\temp\winpemount\windows where: /inf=c:\egenwinpefiles\x86\egenbmc.inf is the location of an INF file from the WinPE 2.1 integration package. Make sure to use the appropriate platform (32-bit or 64-bit) when selecting the file path. 3-4 PM5.2_BF

23 Configuring PXE Tools to Use with EVBS c:\temp\winpemount\windows indicates the directory containing the mounted WinPE image. This directory should match the destination directory of Step 2 with the subdirectory Windows appended. You need to execute this command for each INF file in our WinPE 2.1 integration package. See Requirements above for the complete list. 4. Prepare the WinPE image using the peimg.exe tool: Peimg /prep c:\temp\winpemount\windows where: /prep indicates the prepare action to the Peimg tool. c:\temp\winpemount\windows is the directory containing the mounted WinPE image. This directory should match the destination directory of Step 2 with the subdirectory Windows appended. For more information on preparing a WinPE image using this tool, refer to the WAIK documentation. 5. Commit the changes to the source WinPE image and unmount it using the imagex.exe command: Imagex.exe /unmount c:\temp\winpemount /commit where: /unmount is the ImageX command used to unmount an already mounted WinPE image. c:\temp\winpemount is the directory where the WinPE image was mounted. This directory should match the destination directory of Step 2. /commit instructs the ImageX program to commit all changes to the source WinPE image. After you complete these steps, the original WinPE 2.1 image indicated in Step 2 contains all of the virtualized extensions. You can now integrate the WIM image with the 3rd party deployment solution. See the deployment solution documentation for integration instructions. PM5.2_BF 3-5

24 Using Egenera Virtualized Boot Services Note: When you use EVBS to PXE boot with Microsoft WDS, make sure you use pxeboot.n12 and not the default pxeboot.com. Microsoft WDS supplies pxeboot.n PM5.2_BF

Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions.

25 Information on this document On April 1, 2009, Fujitsu became the sole owner of Fujitsu Siemens Computers. This new subsidiary of Fujitsu has been renamed Fujitsu Technology Solutions. This document from the document archive refers to a product version which was released a considerable time ago or which is no longer marketed. Please note that all company references and copyrights in this document have been legally transferred to Fujitsu Technology Solutions. Contact and support addresses will now be offered by Fujitsu Technology Solutions and have the The Internet pages of Fujitsu Technology Solutions are available at and the user documentation at Copyright Fujitsu Technology Solutions, 2009 Hinweise zum vorliegenden Dokument Zum 1. April 2009 ist Fujitsu Siemens Computers in den alleinigen Besitz von Fujitsu übergegangen. Diese neue Tochtergesellschaft von Fujitsu trägt seitdem den Namen Fujitsu Technology Solutions. Das vorliegende Dokument aus dem Dokumentenarchiv bezieht sich auf eine bereits vor längerer Zeit freigegebene oder nicht mehr im Vertrieb befindliche Produktversion. Bitte beachten Sie, dass alle Firmenbezüge und Copyrights im vorliegenden Dokument rechtlich auf Fujitsu Technology Solutions übergegangen sind. Kontakt- und Supportadressen werden nun von Fujitsu Technology Solutions angeboten und haben die Die Internetseiten von Fujitsu Technology Solutions finden Sie unter und unter finden Sie die Benutzerdokumentation. Copyright Fujitsu Technology Solutions, 2009

PAN Manager Feature Summary

PAN Manager Feature Summary For BladeFrame BF400 S2 and BladeFrame BF200 Document Number 430-SB0073 August 2008 PM5.2_BF Copyright Copyright 2008 Egenera, Inc. All rights reserved. This document, and the