The information contained in this document is subject to change without notice.
Hewlett-Packard makes no warranty of any kind with regard to this material, including, but not limited to, the
implied warranties of merchantability and fitness for a particular purpose.
Hewlett-Packard shall not be liable for errors contained herein or for incidental or consequential damages in
connection with the furnishing, performance, or use of this material.
Hewlett-Packard assumes no responsibility for the use or reliability of its software on equipment that is not
furnished by Hewlett-Packard.
This document contains proprietary information that is protected by copyright. All rights are reserved. No part
of this document may be photocopied, reproduced, or translated to another language without the prior written
consent of Hewlett-Packard Company.
TRADEMARK NOTICE
Assured Availability, ComputeThru, Computing for the long run, Constant Computing, Endurance, Marathon
Assured, MIAL, SplitSite, and the Marathon logo are either registered trademarks or trademarks of Marathon Technologies Corporation in the United States and/or other countries.
Microsoft, MS-DOS, Windows, Windows NT, and Windows 2000 are either registered trademarks or trademarks of
Microsoft Corporation in the United States and/or other countries.
All other brands and product names are trademarks of their respective companies or organizations.
SOFTWARE REVISION
The revision of the Endurance software that this document supports is Revision 4.0.0-RL.EA.
Hewlett-Packard Company
Network Server Division
Technical Communications MS 45SLE
10955 Tantau Avenue
Cupertino, California 95014 USA
A-1 Hardware Configuration with a Video Switch . . . . . . . . . . . . . . . . . . . A-4
A-2 Hardware Configuration with a KVM Switch for Each Tuple . . . . . . . . . . . A-5
A-3 Hardware Configuration with a KVM Switch for Both Tuples in a Single Rack . . A-6
Figures vii
Preface
This guide describes how to install the HP Netserver AA Solution Enduranceâ server, the
Assured Availability
Audience
This guide is written for experienced network administrators and technical personnel
responsible for installing, configuring, administering, and managing network server hardware
and software, including Microsoft
This guide assumes that you are familiar with the Endurance terminology described in the HP
Netserver AA Solution Administrator’s Guide.
Documentation Set
The Endurance documentation set includes:
•HP Netserver AA Solution Installation Guide that describes how to install your Endurance
server.
ΤΜ
solution from the Hewlett-Packard Company.
â
Windowsâ.
•HP Netserver AA Solution Administrator’s Guide that describes the Endurance server and
its related Endurance applications. This guide also includes information about how to
monitor and manage your Endurance server.
•HP Netserver AA Solution Messagesthat lists and describes all Endurance messages. HP
Netserver AA Solution Messages is not shipped in printed form. It is only available online
using the HP Netserver AA Solution Endurance CD-ROM.
•Endurance Release Notes that describes release-specific information, including
installation requirements, operational information, and known product limitations that are
not documented in the HP Netserver AA Solution documentation set. You should read the
Release Notes before installing and using the Endurance server.
Preface ix
All the documentation is available online using the HP Netserver AA Solution Endurance CDROM that was shipped with your HP Netserver AA Solution kit.
Conventions
The following conventions are used in the Endurance server documentation set:
ConventionDescription
Italics,
Courier font
Bold, Courier
font
Courier fontRepresents examples of screen text. For example, scsiid = 0, 1.
BoldIs used to:
ItalicsIs used to:
Blue text(Available only in online documentation.) Indicates a hyperlink (cross-reference
CautionIs used to indicate procedures you should not perform or situations you should
WarningIs used to indicate procedures or actions that could cause file or data corruption,
Indicates a variable that you replace in a path name or command
Indicates actions or commands that you must type. For example, type A:\ETX
• Emphasize important information.
• Indicate menu, pathname, or button selections.
• Indicate actions you perform.
• Highlight the state of the Endurance server component.
• Refer to manual, chapter, or section titles.
to another section of the Endurance documentation set). Clicking on the link
takes you to the appropriate place in the documentation set.
avoid in order to avoid personal injury.
loss of data, or damage to server components.
Unless noted otherwise, all cross-references are to chapters and pages within this book.
x HP Netserver AA Solution Installation Guide
For Customer Support
Refer to the Warranty & Support for Your HP NetServer booklet supplied with your NetServer
for information relating to warranty or customer support.
Preface xi
xii HP Netserver AA Solution Installation Guide
Preparing for the
Installation 1
This chapter describes hardware and software requirements needed to install the Endurance
server. It also discusses what you need to do to prepare your site.
This chapter also introduces you to some Endurance terminology and concepts (described in
detail in the HP Netserver AA Solution Administrator’s Guide).
This chapter includes the following sections:
Overview of the Endurance Server . . . . . . . . . . . . . . . . . 1-2
The fault tolerant Endurance server provides continuous computing and fully-redundant I/O
devices for your Microsoft Windows operating system and its applications.
The main Endurance components include:
Table 1-1 Endurance Components
ComponentsDescription
2 Compute Elements (CEs)The systems that provide all compute processing. The CEs run the
2 I/O Processors (IOP)s The systems that provides I/O resources, including I/O processing,
4 Marathon Interface Cards
(MICs)
operating system where you install and execute all applications.
data storage, and network connectivity.
The PCI-based adapters that enable bidirectional communication
between system components.
The Endurance technology coordinates all I/O requests and responses between the CEs and
IOPs in a redundant processing environment. Using redundant CEs and memory, the Endurance
software performs CPU and memory functions in a tightly coupled manner. If there is a CPU or
memory failure, the Endurance operating system remains continuously available, providing
constant computing without any loss of context.
Figure 1-1 depicts a sample hardware configuration of the Endurance server.
Because all I/O devices in the server physically reside on the IOPs, Endurance software
redirects all I/O requests from the CEs to the IOPs. As a result, these I/O devices are logically
associated with the CE. For example, the Endurance software can redirect a CD-ROM drive
physically located in an IOP so that it is logically assigned to the CE (the CE has complete
control of that CD-ROM drive).
For mirrored disk devices and redundant Ethernet connections, the Endurance software
coordinates all I/O processing so that these redundant components appear as a single logical
device. For example, in a mirrored disk set, the two physical disks (one on each IOP) appear to
the CE operating system and applications as one logical disk. If a disk failure occurs, the disk
operations can transparently continue operating without affecting any server applications or
clients.
Preparing for the Installation 1-3
Redirected Video and the CE Desktop Application
In the Endurance server, CE video output is redirected to the IOPs. To accomplish video
redirection, the server uses kernel mode drivers and the CE Desktop application, an application
that runs on the IOPs and displays CE video output in a window on the IOPs. To display CE
video, you must run the CE Desktop application.
Virtual Network
The Endurance server includes a virtual network that provides LAN-style connectivity between
the CEs and each IOP. This connectivity is independent of any public (redirected) CE or private
(IOP) network adapters. It uses the Windows operating system resource sharing to provide
connectivity between the CEs and IOPs regardless of whether the IOPs have dedicated network
cards installed.
Endurance Manager
The Endurance Manager is a management application for the Endurance server. This
application provides both a Windows-based GUI and a command prompt interface through
which you can monitor and manage your server. You can install the Endurance Manager on a
remote client, enabling you to monitor the system from another location.
Endurance Configuration Utility
The Endurance Configuration Utility enables you to define the Endurance server’s hardware
configuration and to store that configuration information in the appropriate locations of the
Windows Registry. You use the Endurance Configuration Utility to configure the server
initially, and also after making any changes to the Endurance server hardware configuration.
Fault Detection and Event Reporting
Endurance software continuously monitors the server. If it detects a fault, the Endurance server
isolates the fault and deconfigures any affected components, ensuring that the server remains
operational by automatically using the redundant components.
The fault detection and reporting process occurs seamlessly, and in a fully operational
Endurance server, it maintains complete server availability. The Endurance software reports all
events, including general status, state changes, and faults, to the Windows event logs or displays
them in windows as they occur. Refer to HP Netserver AA Solution Messages for complete
1-4 HP Netserver AA Solution Installation Guide
documentation of Endurance messages, which use the standard Windows operating system
event format. Because the Endurance server uses standard message reporting, you can
integrate standard applications to notify you when a fault occurs.
Preparing for the Installation 1-5
Installation Requirements
To complete the Endurance installation, you need to meet the hardware, software, and other
requirements described in the following sections:
•Hardware Requirements
•Software Requirements
Hardware Requirements
To install the Endurance server, you need the following hardware:
Table 1-2 Endurance Server Hardware Requirements
ItemNotes
IOPs
The two IOPs must be Pentium® class PCI-bus PCs. Each IOP
must have:
• A minimum of 256 MB of system memory
• The capability of restarting automatically after a power failure.
On some systems, you may need to select options for automatic
restart in the system Setup utility.
• A SCSI system disk for the local copy of the version of the
Windows operating system you are using
• SCSI Host Based Adapter (HBA)
• One SCSI-based or IDE CD-ROM
• One SCSI IOP boot device (a physical drive or a logical drive
from a hardware RAID set)
• At least one SCSI hard disk that meets the requirements listed in
the Mirrored Disks Set(s) section of this table
•Two Ethernet Adapters that meet the requirements listed in the
Ethernet adapter section of this table
• Floppy disk drive
• Monitor, keyboard, mouse, and video adapter
Make sure your IOP systems conform with the requirements
specified in the Endurance Release Notes.
No IDE devices other than CD-ROMs may be present.
1-6 HP Netserver AA Solution Installation Guide
Table 1-2 Endurance Server Hardware Requirements (Continued)
ItemNotes
CEsThe two CEs must be identical Pentium class PCI-bus PCs. Each
CE must have:
• The capability of restarting automatically after a power failure.
On some systems, you may need to select options for automatic
restart in the system Setup utility.
• Both CEs must have the same amount of RAM (256 MB
minimum).
• Floppy disk drive
• Video adapter -- required for the CE to boot and for
maintenance purposes. A standard PCI or AGP
VGA-compatible video adapter provides the video BIOS
required to boot the CE and display the following items:
- POST messages
- BIOS setup, test, and diagnostics
- MS-DOS boot for flashing the MIC
- Windows operating system flex-boot
- Text phase of the Windows operating system boot
• Monitor – used for running setup and diagnostics, flashing the
MICs on the CEs, and maintenance purposes.
• Keyboard – if your computer’s BIOS requires a keyboard to
boot.
Make sure your CE systems conform with the requirements
specified in the Endurance Release Notes.
You can use one monitor, keyboard, and mouse for the IOPs and
CEs along with a keyboard, video, mouse (KVM) switch. For more
information about using a switch as part of your hardware
installation, see Appendix A.
Mirrored Disks Set(s)
Preparing for the Installation 1-7
Each Endurance server configuration must have at least one
mirrored disk set (two disks, one on each IOP).
Table 1-2 Endurance Server Hardware Requirements (Continued)
ItemNotes
Ethernet AdaptersAt least four Ethernet adapters, minimally:
• Two Ethernet PCI adapters for the IOP Link (IL) connection (one
per IOP). These adapters must be identical – the same
manufacturer and model number. Cross-over cables are
provided with the Endurance server kit. If your adapters require
an alternative media type, be sure you acquire the appropriate
cable.
• Two Ethernet adapters (one per IOP) that support soft-settable
Ethernet addresses to provide connectivity to your network.
These adapters must be identical – the same manufacturer and
model number.
Refer to the HP Customer Support Web site for information
about the cables and adapters you can use in your Endurance
server.
2 or 3 blank diskettesUse two diskettes to make the Emergency Repair diskettes (one for
each IOP). If you choose to do so, you can also make an
Endurance Configuration diskette.
Network cables to provide
network connectivity
Optional: 2 Uninterruptable
Power Supplies
The cables must be compatible with the Ethernet adapters that you
install.
Use one UPS per tuple. The Endurance server has two tuples.
Each tuple contains a CE, and IOP, and a network connection.
Software Requirements
Make sure that you have all of the following before starting to install the software:
Table 1-3 Endurance Server Software Requirements
ItemNotes
The Windows operating system Refer to the Endurance Release Notes for the Windows operating
One of the currently supported
Windows operating system
Service Packs
1 MS-DOS bootable diskette
systems on which the Endurance software can be installed.
New Service Packs, when available from Microsoft, may require
additional qualification from HP. For a complete list of supported
Service Packs, see the Endurance Release Notes
.
1-8 HP Netserver AA Solution Installation Guide
Table 1-3 Endurance Server Software Requirements (Continued)
ItemNotes
All device driver diskettes relating
to your computers and adapters
1 MIC utilities disketteCreate this diskette using the instructions in Chapter 7 of the HP
For SCSI and Ethernet adapters, be sure to install the most current
driver. For most adapters, the driver that is shipped with the
adapter or that is packaged in the Windows operating system
distribution kit is not the most current.
One way to ensure you to obtain the most current driver is to
download it from the manufacturer’s web site.
If you are not sure you have the latest driver, contact the
manufacturer or your service provider for assistance.
Make sure that you know the path to the
diskette. Depending on the manufacturer, the driver might be
located in a subdirectory on the manufacturer’s diskette. For
example,
Netserver AA Solution Administrator’s Guide.
Warning: Make sure that the version of MTCFLASH you use
a:\winnt\.
coincides with your hotfix level. If you have a hotfix that
supersedes what is contained on the MIC utilities
diskette you created, use the hotfix diskette to flash the
MICs. In that case, do not use the MIC utilities diskette
you created from the Endurance CD.
.INF file on each driver
After reviewing the software installation requirements, read the Endurance Release Notes for the
Endurance software that you are about to install.
Continue with Planning the SCSI Disk and CD-ROM Configurations.
Planning the SCSI Disk and CD-ROM Configurations
After ensuring that you have all needed components, you must determine the SCSI device
configuration. You use this information when you configure the Endurance server software.
Complete a SCSI Configuration Chart (Figure 1-3) for your Endurance server. Copy this chart
if you need to complete more than one, which is necessary if you are using either:
•Multiple buses on a SCSI adapter
•Multiple SCSI adapters
A sample of a completed chart is shown in Figure 1-2.
Preparing for the Installation 1-9
SCSI Configuration Charts
Sample SCSI Configuration Chart
PCI or other PC Bus Slot number: 1
1
SCSI Adapter Number (Port Number)
1
SCSI Bus Number
: 0
: 0
SCSI
1,2
ID
3
0
4
1
20Mirrored Disk
30Mirrored Disk
40CD-ROMN/AMust be unusedN/A
50Must be unusedN/ACD-ROMN/A
60TapeN/AMust be unusedN/A
70Initiator IDN/AInitiator IDN/A
8unusedunused
9unusedunused
10unusedunused
11unusedunused
12unusedunused
13unusedunused
Logical
Unit
1
No
0IOP1 Boot DiskIOP2 Boot Disk
0CE Boot Disk
IOP1 DeviceDisk SizeIOP2 DeviceDisk Size
(Mirrored Disk
Set 1)
Set 2
Set 3
CE Boot Disk
(Mirrored Disk
Set 1)
Mirrored Disk
Set 2
Mirrored Disk
Set 3
14unusedunused
15unusedunused
Note: Refer to the next page for notes and additional information.
Figure 1-2 Sample SCSI Configuration Chart
1-10 HP Netserver AA Solution Installation Guide
Notes for the Sample SCSI Configuration Chart
1
This information is available in the active Windows Registry after you install all SCSI
adapters and the Windows operating system drivers
(HKEY_LOCAL_MACHINE\HARDWARE\DEVICMAP\SCSI).
2
One SCSI ID (typically 7) is not available because the SCSI adapter uses it. To determine
which SCSI ID is not available, check the adapter setup and identify the value of the
Initiator Id. Note that you can reset or change the Initiator Id for an adapter,
but it is not recommended unless you are doing this so that it matches its peer adapter on the
other IOP. Check the adapter vendor’s recommendations for this ID, or use SCSI ID 7 if
possible. Note that SCSI ID and Target ID are equivalent in meaning.
3
The IOP boot disk must be the first hard disk detected in the system configuration: lowest
adapter number (determined by the BIOS), lowest SCSI ID. In a typical single SCSI adapter
configuration, this is SCSI ID 0. Some SCSI adapters support booting from IDs other than
the lowest.
4
For the CE boot disk to map to the c: drive when the Endurance server is operational, the
CE boot disk must be the first redirected hard disk detected in the configuration: lowest
adapter number, lowest SCSI ID among redirected disk devices. In a typical (single SCSI
adapter) configuration, this is SCSI ID 1.
Additional Notes:
•IOP boot disks are not redirected to CEs and should occupy the same SCSI address on
both IOPs.
•CD-ROMS can be SCSI devices or IDE devices. All other storage devices (mirrored and
non-mirrored) must be SCSI devices. No IDE devices other than CD-ROMs can be
present in the IOPs. Note, however, that the Windows operating system treats IDE CDROMs like SCSI devices for configuration purposes.
•If you configure a non-mirrored device, the same corresponding SCSI address may not be
in use on the other IOP (same adapter number).
Preparing for the Installation 1-11
SCSI Configuration Chart
PCI or other PC Bus Slot number:
SCSI Adapter Number (Port Number)
SCSI Configuration Chart
1
:
SCSI Bus Number
SCSI
ID
3
0
4
1
2
3
4
5
6
7
8
9
10
11
1,2
Logical
Unit No
1
:
IOP1 DeviceDisk SizeIOP2 DeviceDisk Size
1
12
13
14
15
Figure 1-3 SCSI Configuration Chart
1-12 HP Netserver AA Solution Installation Guide
Installing IDE CD-ROMS
You can install IDE CD-ROMs rather than SCSI CD-ROMs. If you install an IDE CD-ROM
drive in one IOP, then you must also install an IDE CD-ROM drive in the other IOP. No variation on this hardware configuration is allowed.
Configure the IDE CD-ROM drive as necessary to be accessible by the Windows operating
system. If your server requires it, make sure that the IOP can boot from the IDE CD-ROM. You
can assign the IDE CD-ROM drive to the IOP operating system and not configure it as
redirected. You can also use the Endurance Configuration Utility to configure the IDE
CD-ROM drive for redirection, on either IOP1 or IOP2, but not on both.
If an IDE device malfunctions upon boot, the Windows operating system does not assign any
SCSI resources to the IDE controller. Moreover, if no IDE devices are detected, the ATAPI
driver is not loaded. This is different than SCSI devices, for which the Windows operating
system loads the SCSI driver and assigns port numbers as long as a SCSI adapter is detected,
even if no devices are attached to it.
Unless promptly repaired, an IDE CD-ROM failure results in different SCSI port number
assignments for all physical Host Based Adapters (HBAs) upon rebooting the IOP. This
invalidates the Endurance configuration for the IOP with the failed CD-ROM device, thus
preventing it from joining with the other IOP. In that case, the failed component must be
repaired before the IOP with the failed CD-ROM can return to active status.
Continue with Unpacking Your Endurance Server Kit (page 1-14).
Preparing for the Installation 1-13
Loading...
+ 57 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.