< Day Day Up > |
Depending on how the server is ordered, it ships with options in separate boxes or preassembled with options. If the server arrives preassembled, installation involves only positioning it, connecting the cables, and powering it on. Servers without preassembled options require installation of those components. You might need a Torx screwdriver to perform the installation. In a suitable work area, remove the chassis cover and note which components are already installed. As you open each component package, read the instructions carefully to ensure proper installation. Follow all guidelines, including rules for electrostatic discharge protection. When installation is complete, replace the chassis cover, position the server, connect all cables, and power on the server. Observe the console of the server during the Power-On Self-Test (POST) for any errors. When you power on an unconfigured server, a variety of messages and errors might display on the screen. These errors typically relate to the following items:
After the server performs its autoconfiguration, you can launch the ROM-Based Setup Utility (RBSU) or Option-ROM Configuration for Arrays (ORCA) to make further changes or verify system settings. 15.1.1 Updating System and Option ROMsBefore configuring a ProLiant server, you must verify that the system and option ROMs are the latest version. If they are not, you must upgrade them. You can identify the system ROM family and version for your server in two ways. First, if the server is offline (operating system not running), you can use one of these techniques:
Second, if the server is online (operating system is running), you can use one of these techniques:
Flashing the ROM is the process of upgrading system, array controller, or options firmware on a target server with a new ROM image that supports new features or has been modified to fix problems in the previous version. You can flash the ROM in either offline or online mode. ! Important Do not reboot the target server while the ROM upgrade is in progress. You do not need to restart the target server before the system or option ROM flash upgrade begins. When the flash upgrade is complete, you must restart the target server for system and option ROM upgrades to take effect. 15.1.2 System Startup BehaviorAfter you have installed the server components and updated system and option ROMs, the next step is to configure the installed hardware. You may configure ProLiant servers when you start them for the first time or you may use startup defaults. You can reconfigure the default settings later if necessary. ProLiant servers have various indicators for monitoring system status. These indicators typically are integrated into the front panel of the server and are grouped together for easy reference. The most obvious indicator is the power LED. Other front-panel LEDs include the hard drive activity LED, the network activity LED, the internal health LED, and the unit ID LED. Some components have their own indicators, either on the front of the component or in the back or inside. Hot-plug drives, for example, have three LEDs on the front of the drive that indicate power, access, and fault. Internal (non-hot-plug) drives usually just have an activity LED on the front bezel of the server. Removable media drives (disk, CD-ROM, and other drives) have their own LEDs that activate when system power is started or when media in the drive is being accessed. When a system is powered on, all the LEDs briefly light up, and then return to the behavior normal for each indicator. Recognizing normal indicator behavior is crucial to recognizing when the LEDs are indicating an abnormal condition. As the server goes through the POST process, system video activates and system messages display on the console. Typically, these are the RAM count, BIOS date, HP name, processor description, array controller (if present), and any POST errors. The information displayed will vary depending on the options installed. The POST process must complete before any autoconfiguration can occur. In legacy ProLiant servers, the System Configuration Utility was used to configure the BIOS. Currently shipping ProLiant servers (except the 100 series), use RBSU. To configure the array controller, you can use either ORCA or the online Array Controller Utility (ACU). When you start up your server the first time, RBSU automatically configures the system without any intervention during the POST process. After the system configuration is complete and the server restarts, if an array controller is present, ORCA automatically configures your array to a default setting based on the number of drives connected to the controller. You can manually execute RBSU, which is contained in the system ROM, during POST by pressing F9 when prompted. After the server has been configured using RBSU, the system restarts. To configure, you can then change the primary array controller (if present) by pressing F8 when prompted to execute ORCA. Note You will not be prompted for ORCA if you do not have an array controller installed in your server. After the system restarts again, you can install the operating system and any necessary applications. In the rare case that the lithium battery that backs up the nonvolatile memory (NVRAM) fails, all system configuration data will be lost. Replacing the battery and powering on the server will cause it to go through the same automatic configuration process. 15.1.3 ProLiant Setup Configuration FlowFigure 15-1 shows the sequence of events that occurs when a ProLiant server is powered on. Figure 15-1. ProLiant Server power-on sequence.15.1.3.1 DEFAULTSThe RBSU has two default settings. The default operating system is Windows 2000/Windows .NET, and the default language is English. Note Press the F9 key when prompted during the boot process to change the server settings, such as the settings for language, operating system, and primary boot controller, using RBSU. The ORCA disk configuration is set to a default based upon number of drives in array. If there are fewer than two drives in the server, the disk configuration is set to RAID 0. If two drives are in the server, the configuration is RAID 1. If three to six drives are installed, the default is RAID 5. If more than six drivers are installed, there is no automatic default configuration. Note Long timeouts for both operating system and disk configuration defaults might occur. If any data has ever been written to the drive, ORCA will not configure the drive automatically. Tip For more advanced configurations, run ACU from the SmartStart CD or from within an operating system. 15.1.3.2 BOOT OPTIONSAfter the autoconfiguration process is complete or after the server restarts upon exit from the RBSU, the POST sequence runs and the boot option screen displays, as shown in Figure 15-2. Figure 15-2. Boot options screen.This screen is visible for several seconds before the system attempts to boot from either a bootable CD or disk or the hard drive. During this time, the menu on the screen enables you to (1) install an operating system by inserting the operating system CD or the SmartStart for Servers CD, or (2) make changes to the server configuration by pressing an industry-standard function key:
If you take no action, the system attempts to start using the default boot order before starting from the hard drive. The default boot order is (1) disk, (2) CD, (3) hard drive, and (4) PXE. 15.1.3.3 SERVER ROM FUNCTIONALITYThe server ROM is the system component that stores most of the basic server functionality. ProLiant server ROMs come in two sizes: 2MB or 4MB. The base functionality with 2MB ROM includes dynamic setup support (boot driver and ROM), an embedded Setup Utility, and an embedded Diagnostic Utility. The 4MB ROM includes all the functionality of the 2MB version plus an embedded Inspect Utility. ProLiant G2 servers and later have RBSU embedded in the system ROM. Note On some systems, ROM-based enhancements are available that automatically configure ORCA and RBSU. Refer to your server-specific user documentation, which will mention these features if they are available. For more information on using the ROM-based enhancements, refer to the ROM-Based Setup Utility User Guide located on the server documentation CD or at www.hp.com/smartstart. 15.1.3.4 DYNAMIC SETUP SUPPORTThe operating system-specific drivers in ROM include storage drivers and new boot drivers that feature support for these operating systems:
15.1.3.5 SYSTEM MAINTENANCE MENUThe System Maintenance menu, shown in Figure 15-3, displays the following options:
Figure 15-3. System Maintenance menu.This menu, embedded in the system ROM, replaces the legacy system-partition functionality supported on some ProLiant servers. To access the System Maintenance menu, press F10 when prompted from the boot option screen. Note The Inspect Utility is available only on a ProLiant server with 4MB ROM. 15.1.4 RBSUThe purpose of RBSU is to help you configure server hardware settings and prepare a server for an operating system installation. RBSU enables you to view and establish server configuration settings during the initial system startup, and to modify them after the server has been configured. The ROM on ProLiant servers currently shipping contains the functionality provided by the system partition utilities on legacy ProLiant servers. RBSU replaces the SCU that shipped on legacy ProLiant servers. RBSU provides the same functions, eliminating the need for a system partition on the primary drive and the use of a boot disk. Figure 15-4 shows the RBSU interface. Figure 15-4. RBSU interface.The following table describes some of the differences between RBSU and the SCU.
Warning RBSU is not available on some older HP servers. Do not flash an RBSU ROM image on a system initially configured with SCU. Reflashing a server configured with the SCU with an RBSU ROM image can result in potential loss of data, system lockup, and other unpredictable results. 15.1.4.1 STARTING AND EXITING RBSUPress F9 to access RBSU when prompted during the POST sequence to modify component configuration settings without a SmartStart CD or disk. RBSU configures the server automatically if the server is in an unconfigured or erased state. After configuring the server, you must exit RBSU to restart the server with the new settings. Pressing Esc at the main menu displays a confirmation to exit, as shown in Figure 15-5. The current boot controller also displays for reference purposes. Figure 15-5. Confirm RBSU exit.To exit, press F10. The server powers up with the new configuration settings. 15.1.4.2 RBSU MAIN MENUFrom the RBSU main menu, you can select which configuration setting to view or modify. Some selections bring you directly to configuration functions. Others lead to submenus that expand the available choices. The main menu, located on the left side of the screen, enables you to select which configuration setting to view or modify. The selection choices are as follows:
A window on the right side of the RBSU screen displays basic information about the server. This information includes the server model, serial number, BIOS version, backup BIOS version, and memory and processors installed. Pressing F1 when any menu option is highlighted enables you to view a description of that option. 15.1.4.3 RBSU ADVANCED OPTIONSThe Advanced Options menu of the main RBSU menu enables you to configure options normally set by default and not user modified, such as hot-plug resources and processor correction marking. The POST F1 Prompt option is a toggle setting that enables you to set the configuration options for errors on POST. By default, you must press F1 when an error is detected before the POST process will continue. From this menu, you can choose to delay or disable this feature. If you select Delayed and an error occurs, the system pauses for 20 seconds at the F1 prompt, and then continues to boot the operating system. If you select Enabled and an error occurs, the system stops booting at the prompt until you press the F1 key. Note The POST F1 Prompt setting is enabled by default in ProLiant ML and DL servers, and delayed by default in BL servers. 15.1.4.4 PROCESSOR HYPER-THREADING AND ADVANCED MEMORY PROTECTION OPTIONSThe Advanced Options menu also offers the Processor Hyper-Threading option, which is a toggle setting that enables you to enable or disable Intel Hyper-Threading technology. It is enabled by default. Hyper-Threading technology enables multithreaded applications to execute threads in parallel on each processor. This technology boosts system performance without going to a higher clock rate or adding more processors. When multiple instruction streams, called threads, are simultaneously available to a single processor, they allow the processor to better schedule the use of internal resources. Hyper-Threading technology is available in ProLiant servers that use Intel Xeon processors. Advanced memory protection is also available on most ProLiant servers. HP offers three levels of advanced memory protection to increase the fault tolerance of HP ProLiant servers:
15.1.4.5 EMBEDDED ERASE OPTIONThe Advanced Options menu also provides two embedded erase options to erase the NVRAM, as shown in Figure 15-6. Figure 15-6. Erase options.The Erase Non-volatile Memory option resets the nonvolatile memory of the server to an initial, factory state. When you select Yes, Select to Erase, the following pop-up message displays: Are you sure you want to erase NVRAM? You will lose all System Configuration Settings. {Y/N} The Erase NVRAM/Boot Disk option erases the system configuration by resetting the NVRAM, but it completely erases the boot disk. Use this option only when you are redeploying a server and are required to erase the NVRAM and boot disk to reinstall the operating system. User selectable options are as follows:
The Erase Non-volatile Memory option is a standard component of both the 2MB and 4MB system ROMs. If the Erase NVRAM/Boot Disk option is available for your server, it is listed under the Advanced Options menu of the main RBSU menu. 15.1.4.6 EMBEDDED DIAGNOSTIC UTILITYThe Diagnostic Utility provides a preboot method for quickly checking the validity of the three major server subsystems needed to start an operating system memory, CPU, and boot disk, as shown in Figure 15-7. Figure 15-7. Diagnostic Utility interface.This utility augments the version of server diagnostics available on the legacy system partition supported on some ProLiant servers. The purpose of the ROM-based Diagnostic Utility is to provide critical support diagnostics only. The Diagnostics Utility is available only in English. The Memory Test option tests all memory in the system. The CPU Test evaluates all processors in the system. The Boot Disk Test checks the boot drive for its readiness to boot. 15.1.4.7 EMBEDDED INSPECT UTILITYThe ROM-based Inspect Utility displays system configuration information and saves it to a file on a disk. This utility replaces the version of the Inspect Utility available on the legacy system partition supported on some ProLiant servers. To run the utility, select Inspect Utility from the System Maintenance menu. The Inspect Utility is a standard component on all ProLiant servers with 4MB ROM. 15.1.5 ORCAThe newest HP Smart Array controllers, including the RAID LC2, are configured using ORCA. Other HP Smart Array controllers are configured using the ACU. Figure 15-8 shows the ORCA interface. Figure 15-8. ORCA interface.Note The RAID LC2 controller can be configured with ORCA only. ORCA is similar to the ACU but does not require the use of disks or CDs. Instead, ORCA executes out of the Option ROM that is located on the array controllers. It is designed for users who have minimal configuration requirements. ORCA lets you create and delete logical drives, set interrupts, and set boot controller order. Note ORCA does not support drive expansion, RAID-level migration, or setting the stripe size. ORCA is executed by pressing F8 when prompted during the boot process. After using ORCA, the server restarts if any changes were made. During POST, any array controller that supports ORCA provides a prompt to the computer system console as part of the initialization process. If there are no configured logical drives on the array controller, this prompt waits 10 seconds before bypassing ORCA and continuing with the POST sequence. If any logical drives are configured, the prompt waits five seconds. When an HP RAID controller with ORCA support is installed in the system, the controller-based option ROM prompts during POST for 10 seconds. The main features of ORCA include the following:
15.1.5.1 CONFIGURATION METHODSORCA default disk configuration depends on the number of drives present at initial configuration, as follows:
If an array drive is not empty or there are more than six drives connected to the RAID controller, ORCA does not configure the array automatically. If this occurs, run ORCA to configure the array manually. For more information on running ORCA, refer to the server-specific setup and installation guide. 15.1.6 ACUThe ACU, shown in Figure 15-9, simplifies array configuration by providing a user-friendly interface to intelligent features of HP Smart Array controllers. You can start the ACU from within the operating system, from the SmartStart CD, or from a bootable disk. Figure 15-9. ACU interface.ACU features include the following:
15.1.7 ProLiant Essentials SoftwareProLiant essentials software, shown in Figure 15-10, is a critical part of the HP solution. These tools and utilities enable you to easily and quickly set up, configure, deploy, and manage ProLiant servers. This optional software extends the functionality of the HP adaptive infrastructure to address specific business problems and needs. Figure 15-10. ProLiant essentials.In sight Management tools, along with other key management products, are packaged as ProLiant essentials value packs. These software tools enhance solutions and services and are designed to meet specific customer needs. 15.1.8 ProLiant Essentials Foundation PackThe primary component of ProLiant essentials software is the foundation pack (previously distributed as the ProLiant Server Setup and Management Kit), shown in Figure 15-11. Figure 15-11. ProLiant essentials foundation pack.The foundation pack ships with every ProLiant server and includes the essentials needed to install, configure, and manage ProLiant servers, including the following:
Note SmartStart (32-bit) is not included with the ProLiant DL590/64 server. This server uses a default configuration and RBSU to prepare for a 64-bit operating system installation. 15.1.9 Value PacksProLiant essentials value packs are optional software offerings available for purchase that extend the functionality of the foundation pack software. The value packs available from HP include the following:
Note The Performance Management Pack with one license is included on the management CD in the foundation pack. It is also available as a value pack with flexible licensing options. ProLiant essentials value packs are offered in a variety of licensing packages suitable for single copy through large volume acquisitions. Two licensing choices are available for each value pack product: the Flexible Quantity License Kit and the Master License Agreement. 15.1.9.1 FLEXIBLE QUANTITY LICENSE KITThe Flexible Quantity License Kit allows customers to purchase a single software package, and provides one copy of the documentation and installation media (where applicable) and a single license key that is able to activate the exact number of licenses desired. 15.1.9.2 MASTER LICENSE AGREEMENTThe Master License Agreement is available for customers who want a single key for licenses of a value pack product that they plan to purchase incrementally over time. 15.1.10 Choosing a Deployment MethodIf you need to deploy a single ProLiant server, SmartStart is the preferred deployment tool. If you need to deploy multiple ProLiant servers, the two primary solutions are SmartStart Scripting Toolkit and Rapid Deployment Pack (RDP). Figure 15-12 shows these options. Figure 15-12. ProLiant server deployment options.Both SmartStart and the SmartStart Scripting Toolkit are powerful yet easy-to-use tools. Each solution is designed to meet specific customer requirements. Note The SmartStart Scripting Toolkit is available for download from http://h18013.www1.hp.com/products/servers/management/toolkit/index.html 15.1.11 SmartStartThe SmartStart and Support Software CD contains the SmartStart setup program, shown in Figure 15-13, which is the integration tool that optimizes platform configurations and simplifies the setup and installation of HP servers. Figure 15-13. SmartStart interface.SmartStart performs the following functions:
The SmartStart software is easy to use for single-server deployment. SmartStart requires user attention throughout the process and can be performed on only one server at a time. Not all operating systems that are supported by the server can use the SmartStart installation. The SmartStart CD is delivered in the ProLiant essentials foundation pack. It supports all HP ProLiant ML and DL servers except the DL590/64 and 100 series of servers. SmartStart is a very useful tool for both novice and advanced users. The SmartStart CD contains optimized drivers and utilities that provide maximum performance on all leading operating systems. 15.1.11.1 PROLIANT SUPPORT PACKSPSPs are operating system specific bundles of HP server support software. Each PSP includes multiple self-installable components known as smart components (optimized drivers, management agents, and utilities) for Microsoft Windows, Linux, and Novell NetWare. 15.1.11.2 SMARTSTART CD UTILITIESThe following utilities are also included with SmartStart:
SmartStart 6.00 and later offers an assisted installation path only. The assisted installation prepares the server hard drives by erasing the drives, creating a boot partition, preparing for the file system, and installing server support software, including the PSP. For manual installations, use vendor-supplied operating system media and the RBSU and ORCA ROM-based utilities. Server systems that support RBSU and ORCA feature maintenance utilities and automatic configuration operations that enable you to boot from the operating system CD to install the operating system, and then manually install server support software from the SmartStart CD or obtain the PSP. 15.1.12 System Erase with SmartStart 5.xUse the System Erase Utility to erase all previous hardware and software configurations, including the network operating system, before using SmartStart 5.x to initialize a server. The System Erase Utility can be run from SmartStart 5.x. The System Erase Utility erases system configuration information from NVRAM, from the hard drives, and from the Smart Array controllers present in the system. When reinitializing a system using SmartStart, be sure to use the System Erase Utility. Warning The System Erase Utility is destructive to all data. If you start a previously configured server with SmartStart and it prompts you to run the System Erase Utility, do not run the System Erase Utility unless you want to clear all existing server configuration and data. The System Erase Utility destroys all configuration information and data by completely erasing all hard drives. 15.1.13 System Erase with SmartStart 6.xSmartStart 6.x and later also includes the System Erase Utility, which provides options to clean various areas of the system, including attached drives, unattached drives, BIOS, and NVRAM. Unlike previous versions of SmartStart, the System Erase Utility for SmartStart 6.x and later does not erase the Smart Array controllers. For legacy systems, the Erase Utility is still available for download. To access the latest release of the Erase Utility, go to Software and Drivers Download at http://www.hp.com. |
< Day Day Up > |