HP Integrity Servers for Microsoft Windows Server 2003 Smart Setup Guide HP Part Number: 5991-3718 Published: March 2007
Legal Notices © Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents 1 Preparing for the installation.......................................................................................11 Choosing an installation scenario.........................................................................................................11 Ensuring platform compatibility..........................................................................................................12 Check hardware compatibility...............................................................
Enabling Windows components...........................................................................................................41 Install TCP/IP...................................................................................................................................42 Install SNMP....................................................................................................................................42 Configure SNMP..................................................................
Hardware interface for all HP Integrity servers except Superdome...............................................68 Hardware interface for Superdome servers....................................................................................69 A Preparing the server for Microsoft SQL Server 2005..............................................71 SQL Server 2005 installation.................................................................................................................
List of Figures 1-1 1-2 1-3 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 2-10 2-11 2-12 2-13 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 B-1 Headless console configurations...................................................................................................18 GUI console configuration............................................................................................................19 PXE/RIS configuration.............................................................................
List of Tables 1-1 1-2 1-3 1-4 2-1 4-1 B-1 C-1 Installation matrix.........................................................................................................................13 Locating the Microsoft COA.........................................................................................................14 Graphics support on server models..............................................................................................20 EFI device mapping fields................................
1 Preparing for the installation Installing Microsoft® Windows® Server 2003 for Itanium®-based systems on an HP Integrity server involves preparing the hardware for operating system (OS) installation, loading the OS, and updating the system with the latest OS patches. This chapter helps you plan the installation based on the server model, the OS edition, the source of the OS media, and your network environment. Subsequent chapters guide you through the installation process.
OS was installed correctly, configure the system, and update it with the latest drivers and Microsoft patches and fixes (QFEs) on the HP Smart Update media included in the latest HP Integrity Essentials Foundation Pack or from the HP Integrity servers support website: http://www.hp.com/support/itaniumservers/ • Installed Windows Server 2003 incorrect or inoperable Prepare the server hardware for installation. Use the HP Reinstallation media to restore the OS files.
Table 1-1 Installation matrix Server Console Media rx1620 GUI console rx2620 HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2 rx2660 HP Reinstallation rx3600 Headless console rx4640 rx6600 BL860c HP Smart Setup, HP Smart Update, and Microsoft Windows Server 2003 with SP2 HP Reinstallation Integrated Remote Console (rx2660, rx3600, rx6600, and BL860c only) Virtual Media (vMedia) + HP Smart Setup, Smart Update, Windows Server 2003 with SP2, or HP Reinstallation PXE/RI
Using the HP Reinstallation media HP Integrity servers factory-installed with Windows Server 2003 provide the HP Reinstallation media, which you can use to restore the server to its factory condition if necessary. You must have the corresponding license key to reinstall Windows Server 2003. The license key is found on your server’s Certificate of Authenticity (COA). Locating the Microsoft Certificate of Authenticity The certificate contains the CD key for Microsoft Windows Server 2003.
Table 1-2 Locating the Microsoft COA (continued) Integrity Server Location rx2660 The COA is located on the left side panel, in the middle, as shown here: rx3600 The COA is located on the left side panel, as shown here: rx4640 The COA is located on the left side panel, as shown here: rx6600 The COA is located on the left side panel.
Table 1-2 Locating the Microsoft COA (continued) 16 Integrity Server Location BL860c The COA is located on the left side panel. If there is more than one label on the side panel, the COA is the one farthest left, as shown here: rx7620 and rx7640 The COA is located on the front of the system, above the light panel, next to the UUID label, as shown in the first illustration that follows. Additional COAs are shown in the second illustration.
Table 1-2 Locating the Microsoft COA (continued) Integrity Server Location rx8620 and rx8640 The COA is located in the front of the system, at the bottom, near the power supply as shown in the first illustration that follows. If additional COAs are required, they are located as shown in the second illustration.
Setting up a console Set up your server with a GUI console or a headless console. Set up a headless console A headless console is a PC running terminal emulation software, such as PuTTY (available on the Smart Setup media or from the web) or HyperTerminal, connected to the server through the management processor (MP) serial port or LAN port. Figure 1-1 shows headless consoles connected to an HP Integrity rx4640 server.
• • 3. 4. 5. 6. 7. Stop bits: 1 Flow control: Xon/Xoff Use the Keyboard Configuration Panel to map the backspace key to Control + H. Boot the server. Run PuTTY and press Enter. The MP login prompt appears. Enter your user name and password, and the MP command prompt appears. Enter the CO command to access the headless console. Set up the headless console using a LAN To set up the headless console over a LAN, complete the following steps: 1. 2. 3. 4.
A GUI console provides complete access to all the installation and administration tasks that you can perform on the server. You can use the GUI console to prepare the server for installation, install the OS, and check server status after installation. On servers configured with an internal graphics card, you can connect a monitor, keyboard, and mouse directly to the appropriate ports.
NOTE: You can use the Integrated Remote Console in place of the GUI Console method of installation anywhere the GUI method is described in this document. The IRC and vMedia features are enabled only after you have obtained and installed an iLO 2 MP Advanced Pack license (part number AB500A). If you are not licensed and try to use these features, you see the message: iLO 2 feature not licensed. Free limited-term trial licenses are also available.
5. 6. On the Virtual Devices tab, select Virtual Media in the left panel. Click the Launch button. If Launch is greyed out, the license might be invalid or expired. A new window appears, providing access to Virtual Media. Do on of the following actions: • Select Local Media Drive, specify the CD or DVD drive on your client machine, and insert the CD or DVD into that drive. • Select Local Image File, and specify the ISO image of the desired CD or DVD. 7. Click Connect.
NOTE: When you perform a PXE/RIS headless installation, note the following: • Headless installations using PXE/RIS are not supported with Windows Server 2003, Datacenter Edition. Use the HP Reinstallation media instead. • Do not connect the RIS server to the Integrity server using your intranet during initial Windows OS installation. Set up a small private network, populated with the RIS server, a hub, and the system LAN NIC of the HP Integrity server.
3. 4. to unknown client computers if you want the RIS server to respond only to prestaged client computers in Active Directory. c. Enter the location of the client images. This can be either the Windows Server 2003 Enterprise Edition with SP2 CD or a shared folder on the network that contains the installation files. d. Enter help text that describes the operating system installation choices to users or clients of RIS.
Authorize a RIS server in Active Directory A RIS server must be authorized in Active Directory to be able to respond to clients requesting service. If RIS is installed on a server that is not an authorized DHCP server, or added to a DHCP server that is not authorized in Active Directory, you must complete the following steps: 1. 2. 3. 4. Log in to the domain in which the RIS server resides. (The account you use must be a member of the Enterprise Admins group.
Set up the boot drive The operating system installs through the boot controller detected as adapter zero to the drive detected as drive zero. CAUTION: HP strongly recommends that only the target OS drive be connected during installation. This ensures that the OS is installed on the correct drive. Make sure that the Z: drive letter is free. Windows Server 2003 with SP1 or SP2 creates the EFI partition here. To set up the boot drive, complete the following steps: 1. 2. 3. 4. Power off the server.
fs0 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master)/CDROM(Entry1) blk0 : Acpi(PNP0A03,1)/Pci(1|0)/Scsi(Pun0,Lun0) blk1 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master) blk2 : Acpi(PNP0A03,0)/Pci(2|0)/Ata(Primary,Master)/CDROM(Entry1 3. Note the device name of the CD device: fs0 You use this to explore the contents of the CD or DVD. The map command displays or defines a mapping between a user-defined name and a device handle.
Windows Server 2003 implements the ACPI 1.0b specification with some extensions from version 2.0, whereas HP-UX and Linux implement ACPI 2.0. As a result, the firmware has to be prompted by this flag to recognize that the operating system to be booted is Windows Server 2003. NOTE: Updating the system firmware can reset this flag to default. Verify that the flag is set to windows after you flash the system firmware.
2 Installing the OS This chapter provides instructions for installing the operating system (OS) using a headless console, a GUI console, or a PXE-enabled NIC. This chapter also provides reinstallation instructions for Windows Server 2003. Each method comprises a series of tasks, concluding with two tasks that verify that the OS was installed correctly. You must install the HP Support Pack after installing the OS. You must also install any operating system and security updates using the Smart Update media.
Figure 2-1 Enter EBSU 5. 6. From the Main Menu, select Express Setup and press Enter. EBSU displays the Express Setup introduction. Press Enter to continue. Figure 2-2 Select Express Setup 7. 30 EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the devices whose firmware you want to update. To continue, select Next and press Enter.
Figure 2-3 Update firmware NOTE: You might be able to use EBSU to flash the firmware of some devices. You cannot flash the firmware if the installed version is the same or higher than the version on the Smart Setup media. Also, you cannot use EBSU to flash the MP firmware. You must download the latest MP firmware from the HP Integrity support site and flash it separately: http://www.hp.com/support/itaniumservers/ 8.
Figure 2-5 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter. 12. EBSU prompts you to insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive. Insert the CD and press Enter. Figure 2-6 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk.
3. 4. 5. If Windows Setup cannot find a system partition, it prompts you to create one. Press Enter to continue. Windows creates a partition and then prompts you to format it. Select the partition in which you want to install the OS and press Enter. Windows formats the partition if necessary, checks the partition for errors, and begins to copy the OS files. Monitor the copy process until it completes. You can monitor installation progress from the SAC command prompt by using these three channels: setuplog.
6. EBSU displays the Express Setup introduction. Press Enter to continue. Figure 2-8 Select Express Setup 7. EBSU displays the firmware update screen, listing each device, its installed firmware version, and the firmware version on the Smart Setup media. Select the devices whose firmware you want to update. To continue, select Next and press Enter. Figure 2-9 Update firmware NOTE: You might not be able to use EBSU to flash the firmware of some devices.
Figure 2-10 Partition disk 9. Specify the option to install offline diagnostic tools (from the HP Itanium Processor Family offline diagnostics and utilities CD). 10. Also, specify the option to launch the Windows OS installer. Select Setup and press Enter. Figure 2-11 Install diagnostic tools 11. EBSU displays the partition confirmation window. Select Continue and press Enter. 12. EBSU prompts you to insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive. Insert the CD and press Enter.
Figure 2-12 Insert the Microsoft Windows Server 2003 CD Run Windows Setup Windows Setup prompts you to create a system partition on the boot disk if needed, copies the OS files on to that partition, and attempts to reboot from the boot disk. To run Windows Setup, complete the following steps: 1. Insert the Microsoft Windows Server 2003 with SP2 CD in the DVD drive, and Windows Setup launches. Press Enter to start the installation.
c. d. e. f. In the Your Product Key window, enter the product key. The product key is located on the label attached to the server. In the Licensing Modes window, select the license you purchased. In the Administrator Password window, enter the server name and a password. In the Date and Time window, select the appropriate time zone, and click Next. The server reboots to the EFI Boot Manager. 3. 4. 5. From the EFI Boot Menu, select Windows Server 2003. The server boots to Windows.
1. 2. 3. From the headless console, log in to the MP using a terminal emulator such as HyperTerminal or PuTTY. Boot the server to EFI. Because Windows Server 2003 cannot create a boot entry if one already exists, you must delete the existing boot entry. To delete the boot entry: a. Do one of the following: • If you are using the Enhanced EFI Boot Manager Menu (grey background), select EFI Boot Manager Menu > Boot Configuration > Remove Boot Entry.
Specify server settings To set up Windows Server 2003 after initial boot from a headless console, complete the following steps: 1. At the SAC> prompt, switch to channel one by pressing Esc+Tab.
1. 2. Boot the server to EFI. Because Windows Server 2003 cannot create a boot entry if one already exists, you must delete the existing boot entry. To delete the boot entry: a. Do one of the following: • If you are using the Enhanced EFI Boot Manager Menu (grey background), select EFI Boot Manager Menu > Boot Configuration > Remove Boot Entry. • If you are using the Legacy EFI Boot Manager Menu (black background), select EFI Boot Manager Menu > Boot Option Maintenance Menu > Delete Boot Option(s). b.
c. d. e. f. In the Your Product Key window, enter the product key. The product key is located on the label attached to the server. In the Licensing Modes window, select the license you purchased. In the Administrator Password window, enter the server name and a password. In the Date and Time window, select the appropriate timezone, and click Next. The server reboots to the EFI Boot Manager and then boots up Windows Server 2003.
Install TCP/IP NOTE: Install TCP/IP before installing the HP management agents. To install the TCP/IP driver, complete the following steps: 1. 2. 3. 4. Select Start > Settings > Control Panel > Network Connections. Right-click the Local Area Connection icon and select Properties. Select Internet Protocol TCP/IP and click Install. Click OK. Install SNMP SNMP support is included in Windows Server 2003. To install the SNMP Protocol, complete the following steps: 1. 2. 3. 4. 5. 6. 7.
1. 2. 3. Use HyperTerminal or PuTTY to log in to the MP. Enter the CO command go to the SAC prompt. At the SAC> prompt, enter the I command to specify the network number, IP address, and subnet mask. For example: I. Set up and run a Remote Desktop Connection The remote administration mode is enabled by default on Windows Server 2003 if you use the HP Reinstall media. If you install or reinstall using Microsoft OS media, the Remote Desktop functionality is disabled.
Enable greater than 256 interrupts (cell-based servers only) NOTE: This section (Enabling greater than 256 interrupts) applies only if you are using Windows Server 2003 with SP1. If you are using Windows Server 2003 with SP2, you can skip this section. When you use Enterprise Edition on cell-based servers (rx7620, rx7640, rx8620, rx8640, and Superdome), the system allows a limit of 256 interrupts. To allow greater than 256 interrupts, apply QFE 900713, and then add /EXTINTVEC to the boot options.
3. 4. In the EFI Boot Manager select EFI Shell[Built-in], then press Enter. The device mapping table appears. Find the files in the EFI Shell. a. Enter fsX:, where X is a number from the device mapping table, for example, fs0:. b. At the EFI Shell prompt, change to the directory where the firmware file was copied. 5. Enter the firmware executable file name, and press Enter to begin installation.
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. Insert the HP Smart Setup CD in the CD drive of the target server. The Smart Setup CD starts and displays the license agreement screen. Click Accept to accept the license agreement. The HP Smart Setup Welcome screen appears. Click Software. Click Integrity Support Pack.
Using Integrated Remote Console to install Windows on rx2660, rx3600, rx6600, and BL860c servers If you are using the Integrated Remote Console (IRC) to remotely install Windows Server 2003 on rx2660, rx3600, rx6600, or BL860c servers with a graphics console attached to the local VGA port, you must do one of the following: • Install the OS remotely from a headless console instead (see “Installing from a headless console” (page 29)) • Disconnect the local graphics console before you install Windows using IRC
10. Enter q (to quit) then Exit to return to the Boot Manager. 11. In the new list of boot options, scroll down to the new entry and press Enter to reboot the system using the modified boot entry. Installing a Windows guest on an HP Integrity Virtual Machine host HP Virtual Machines (HPVM) is a soft partitioning and virtualization technology that provides operating system isolation with CPU allocation and shared I/O.
of tasks simultaneously. This feature makes use of resources that would otherwise sit idle, enabling your HP Integrity server to perform more work in less time. CAUTION: When installing the operating system using the Microsoft media with Service Pack 1 (SP1), you must disable hyperthreading before installing the OS; otherwise, the installation will fail. After installing the OS, you must install KB #919385 using the Smart Update media, as described in the next section.
To enable hyperthreading on partitionable HP Integrity servers where the OS and system management tools have already been installed and upgraded to their latest versions, complete the following steps: 1. 2. 3. On the management station or local nPartition desktop, double-click the HP System Management Homepage (SMH) icon. This icon is added to the desktop by the SMH installer. It is a link to the System Management Homepage on the local system.
3 Installing Management Tools This chapter describes the installation of tools and applications used to manage your Integrity server. Installing System Management Homepage This section describes the installation of System Management Homepage (SMH) on Integrity servers. Configure SMH after Support Pack installation When you install SMH using the Support Pack it, is configured using the default security settings. Use the SMH online help for information on the security settings. To access the help: 1.
11. To add HP SMH group names: a. In the Group Name field, enter a name for the operating system group. b. Select an operating level to include: Administrator, Operator, or User. 12. Click Add. The group name is added. You can add a maximum of five entries for each group level. 13. Click Next to continue. The User Access dialog box appears. Use it to configure HP SMH for the following access types: • Select Anonymous Access to enable anonymous access to unsecured pages.
17. Select IP Binding to enable the subnet IP address and netmask. The IP Binding dialog box enables you to bind to specific IP addresses that match a specific subnet IP address or netmask. It restricts the subnet you want to manage. a. Enter the subnet IP address in the designated field. b. Enter the netmask in the designated field. c. Click Add, and the subnet IP address or netmask appears in the dialog box. d. To delete a subnet IP address or netmask from the dialog box, select it and click Delete.
NOTE: Do not install any HP management agents until you have installed and configured the TCP/IP and SNMP protocols. Configure management agents after Support Pack installation Agents are automatically activated when they are installed (except for the Clustering Information agents). Inactive agents remain installed but are dormant until you activate them again. For instructions on configuring an agent or making it inactive, see “Activating and configuring agents” (page 54).
NOTE: You must have Administrator rights to access the management agents from the Windows Control Panel. 1. Open the Windows Control Panel and select HP Management Agents for Integrity Servers. The installed agents are listed in the window. All agents except clustering information are activated at time of installation. 2. Click the Services tab. Figure 3-3 Services tab screen 3. 4. 5. Select an agent from either column to change the active or inactive status.
Figure 3-4 Welcome message 2. Click Next to access the SMTP information window. Figure 3-5 Mail (SMTP) server information 3. 4. Enter a valid email address in the From address field or leave it blank. Enter the name of the SMTP mail server you are using in the Mail server field. You must enter a valid server address to continue with the setup process. The wizard checks the SMTP mail server address you entered to see if it can be accessed.
Figure 3-6 Event recipients information In this window, add users designated to receive event messages. 6. Click Add to add a new user or click Edit to edit the properties for an existing user. Figure 3-7 Adding a new user 7. 8. 9. Select the email recipient type from the Receiver type drop-down list. Click OK to return to the recipient information window. Select a user name and click Edit to edit user properties, or select a user name and click Delete to remove a user. 10.
Figure 3-8 Event selection window 11. Use the severity and source filter fields to view selected events only. The event severity levels, source, and message are not user-configurable. 12. Click the check box to enable an event or disable email notification for an event. 13. Click Use Default to load the current default event notification settings. 14. Click Set Default to set and save the current notification settings as the default values. 15.
3. 4. 5. 6. Select a time interval for SNMP data collection from the Data Collection Interval list box. Click the Send Test Trap button (available only if the HP host agent is active) to send a test trap. Click Clear All Thresholds to clear all current SNMP trap threshold values. Click OK.
7. Click OK to confirm. NOTE: You can only delete processes that a user has created. The Delete button is disabled for system default processes. 8. Click OK when you are done configuring process monitoring. Sending SNMP traps to management applications via IP Configure SNMP services with a specific IP addresses to send SNMP traps to an SNMP management application with an IP address. To configure management agents with a management console IP, complete the following steps: 1. 2.
Figure 3-12 SNMP traps tab 6. In the Community name field, if a community name already exists, select it. If one does not exist, enter a community name and click Add to List. NOTE: The default community string for HP Insight Manager is public. If you enter a different community string here, enter the same string on the management console that is responsible for the system. HP recommends not using the string public because it is the default value, commonly used, and can present a security risk. 7.
Install nPartition Commands Bundle from the Smart Setup media This section describes the tasks you need to complete before you install the nPartition Commands Bundle from the Smart Setup media. 1. 2. Install all the OS fixes and security fixes on the Smart Update media. The Smart Update DVD is part of the Integrity Essentials Foundation Pack kit, along with the Smart Setup CD. To verify that all fixes were installed, select Control Panel > Add/Remove Programs and scan the list of installed software.
14. The HP Partition Manager installation starts next. When it finishes, press any key in the command window to exit. 15. Verify that the installation succeeded. Verifying the installation To verify correct server configuration and software installation, perform the following simple tests: Verify nPartition commands 1.
3. In order to test remote WBEM connections, do the following: a. Copy the remote nPartition WBEM certificate into the local WBEM trusted certificate store. b. Enter the host name and IP address of the remote nPartition that you want to connect to, along with an account and password with administrative privileges on the remote nPartition in the top half of the Partition Manager login screen. c. Click OK. 4. In order to test remote IPMI connections, do the following: a.
4 Performing hot-plug operations This chapter describes adding and removing PCI cards on HP Integrity servers. Adding a card to your system is called a “hot-plug addition,” and removing a card is called a “hot-plug deletion.” IMPORTANT: HP Integrity rx1620, rx2620, rx2660, and BL860c servers do not support PCI card hot-plug addition or deletion. Before you begin Review the following terms before beginning hot-plug operations: • Attention button Use the attention button to initiate hot-plug operations.
NOTE: You cannot perform a hot-plug addition for some cards unless they replace the same type card in the slot. You cannot hot-add them in a new installation. Although no damage to the server occurs if you attempt a hot-plug addition with these cards, they will not function until the next reboot. The following table lists the PCI cards that do not support hot-plug addition.
NOTE: HP Integrity rx7620, rx7640, rx8620, and rx8640 servers have a white bell-shaped image button located at the top rear of the PCI slot. To access, remove the button cover. HP Integrity rx3600, rx4640, and rx6600 servers have a maroon-colored button on the top of the PCI slot separator, just below the manual retention latch (MRL). HP Integrity Superdome servers do not have attention buttons. 3. 4. Wait for the slot to power off (green power LED will turn off). Open the MRL.
Activate PCI card in Cabinet w, IO Bay x, IO Chassis y, PCI Slot z? (Y/[N]) y Request to Activate PCI card sent to system. Check slot power LED. MP:CM> 4. 5. Check that the slot power LED (found by looking down through top of chassis) is not blinking, indicating that the slot is powered. If the green LED is not on, the power to the slot is not on and the addition of the card failed. Check the Windows Device Manager for the device just installed. If the device is not present, the addition failed.
1. 2. Locate the slot of PCI card to delete. Press the attention button for the slot. The power LED will begin flashing. During the 5 seconds that the power LED is flashing, you can abort the request by pressing the attention button. When the green LED stops blinking and goes off, it is safe to remove the card. NOTE: Do not remove the card before the LED stops blinking or a fatal machine check alert (MCA) error occurs. 3. 4. 5. Open the manual retention latch (MRL). Remove the card. Close the MRL.
A Preparing the server for Microsoft SQL Server 2005 This appendix describes the server configuration tasks needed to install Microsoft SQL Server 2005. SQL Server 2005 installation This section is an overview of the steps needed to install SQL Server 2005. For further installation and configuration information, see the SQL Server 2005 documentation. 1. Configure the server • Set the system ACPI Config Flag to Windows.
INSTALLVS=SQL_Engine INSTANCENAME= ADDLOCAL=SQL_Engine,Client_Components ADDNODE= GROUP= IP= ADMINPASSWORD= SAPWD= INSTALLSQLDIR= INSTALLSQLDATADIR= SQLACCOUNT= SQLPASSWORD= AGTACCOUNT= AGTPASSWORD= Installing SQL Server from the GUI To install SQL Server from the GUI, complete the following steps: 1.
15. 16. 17. 18. 19. 20. 21. For more information about this page, click Help at the bottom of the page. When you are finished, click Next. If you selected SQL Server Authentication, you must provide a user name and password with administrative privileges for that instance. Confirm the Report Server Database Name. Click Next. If you selected Reporting Services as a feature, the Report Server Delivery Settings page displays.
B EFI Utilities This appendix provides an overview of the EFI Extensible Firmware Interface (EFI) and the EFI-Based Setup Utility (EBSU). The EFI provides access to the server at a pre-operating system , which enables you to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. Introduction to EFI The Extensible Firmware Interface (EFI) is an interface between the operating system, the firmware, and the hardware.
Common EFI Shell commands The following table lists some commonly used EFI commands. Table B-1 EFI Shell Commands and Descriptions Command Description Boot Commands autoboot Set and view autoboot timeout variable. bcfg Display and modify the driver and boot configuration. boottest Set and view BootTest bits. dbprofile Display and modify direct boot profiles for use by lanboot. lanboot Boot over the LAN.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description connect Bind a driver to a device. dblk Hex dump – BlkIo devices. devices Display devices managed by EFI drivers. devtree Display tree of devices. dh Dump handle information. disconnect Disconnect drivers from devices. drivers Display list of drivers. drvcfg Invoke the Driver Configuration Protocol. drvdiag Invoke the Driver Diagnostics Protocol. guid Dump known GUID IDs. lanaddress Display MAC address.
Table B-1 EFI Shell Commands and Descriptions (continued) Command Description Memory Commands Commands for listing and managing memory, EFI variables, and NVRAM details. default Set the default NVRAM values. dmem Dump memory or memory-mapped I/O. dmpstore Display all EFI variables. memmap Display the memory map. mm Display and modify MEM/IO/PCI. pdt View and clear nPartition or cell memory page deallocation table (PDT).
EFI-Based Setup Utility The EFI-Based Setup Utility (EBSU) provides an easy-to-use interface to flash the firmware, partition the hard disk, install diagnostic tools, configure storage controllers, and run other EFI utilities. The EBSU provides the following functions: • Express Setup — Guides you through Windows installation and setup. See “Run EBSU” (page 33) for detailed information on using Express Setup.
5. Enter the following: load vfloppy.efi 6. Enter the following: map -r You cannot unload or change the virtual floppy file system unless you reset the computer. CAUTION: When Windows installation begins, you are prompted to press F6 to install a third-party SCSI or RAID driver. Do not press F6. Pressing F6 forces Windows to look for the driver on a physical floppy drive, which does not exist. The driver is loaded in memory and installed automatically.
This creates the Windows boot file boot0001. Verify successful boot file creation To verify that the boot file was created successfully, use the following procedure: 1. Select EFI Shell[Built-in] from the EFI Boot Manager. 2. Enter fs0: at the EFI Shell prompt. 3. Enter cd MSUTIL at the fs0:> prompt. 4. Execute the NVRBOOT.EFI boot utility at the fs0:\MSUTIL> prompt. 5. Enter I to Import. 6. Enter the following path: EFI\Microsoft\Winnt50\boot0001 7. 8.
C Management processor and Special Administration Console This appendix describes the management processor (MP) and Special Administration Console (SAC), which you can use to monitor Windows installations and administer the system using a headless console. Management processor This section describes the management processor (MP).
• MODEM PROTOCOL: Bell or CCITT. CCITT is a European standard; RTS/CTS signaling is used as well as the Ring signal. Bell is a U.S. or simple mode. • BAUD RATES: Input and output data rates are the same — 300, 1200, 2400, 4800, 9600, 38400, 115200 bit/sec. • FLOW CONTROL: Hardware uses RTS/CTS; software uses Xon/Xoff. • TRANSMIT CONFIGURATION STRINGS: Disable this setting whenever the modem being used is not compatible with the supported modem (MT5634ZBA).
DI — Disconnects remote/modem or LAN/WEB console. This command disconnects (hangs up) the remote/modem or LAN/WEB users from the MP. It does not disable the ports. The remote console is no longer mirrored. FW — Activates MP firmware upgrade mode. This command is available from either the LAN or a local serial port. This command activates firmware upgrade mode, which loads new firmware through the MP LAN by FTP (which must be operational). An MP reset is generated after the upgrade is complete.
command displays the current state of the DCD, CTS, DSR, and RI status signals and the last state of the DTR and RTS control signals set by the firmware. PC — Power Control. Turns system power on and off. For proper system shut down, shutdown the OS before issuing this command or use the graceful shutdown option. Use this command to switch the system power on or off. You can have the action take place immediately or after a specified delay. PG — Paging parameter setup. Configures pagers.
• V — View mode configuration (text, keyword, hex) • ? — Display this help menu • Q — Quit SMCLP — Server Management Command Line Protocol (rx2660, rx3600, rx6600, and BL860c only). This command switches the console terminal from the MP Main Menu to the Server Management Command Line Protocol (SMASH) SM CLP interface.
XD — Diagnostics or Reset of MP. Use this command to perform some simple checks to confirm the health and connectivity status of the MP. The following tests are available: • MP Parameter Checksum • Verify I2C connection (get BMC Device ID) • LAN connectivity test using ping • Modem self-tests Also, you can reset the MP safely using this command, without affecting the operation of the server.
GUI console are also available using the headless console. This includes starting the system and performing system-recovery tasks. Emergency Management Services consists of components that are standard features of Windows Server 2003, and to which console redirection functionality has been added. Emergency Management Services also includes a management console that is unique to it: Special Administration Console (SAC).
Services, you can see which portions have completed and whether any errors have occurred. This is a useful way to check the progress of your setup and to diagnose setup failures. The setup log channels are as follows: • setuplog.txt: Monitors setup progress. • setupact.log: Displays any warnings during setup. • setuperr.log: Displays any errors that might occur during setup. SAC Channel Management Commands The following table lists the channel management commands.
