48-volt DC power shelves, 2 power supplies per shelf, plus optional lN+1
(Model 24 includes 3 shelves, Model 32 includes 4 shelves)
4.
Connections for PCI drawers
DA - 11424 North America — Version 7 — August 19, 2003
Rear View
Rear View
Rear ViewRear View
5.
6.
7.
8.
System boxes each with 2 QBB's (Model 24 includes 3 system boxes, 6
QBB's, Model 32 includes 4 system boxes, 8 QBB's)
Global switch
Cooling blowers
Two AC input controllers
Page 1
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Overview
At A Glance
At A Glance
At A GlanceAt A Glance
AlphaServer GS320 systems include:
One 1224-MHz CPU module; up to 32 1224-MHz Alpha 21264 processors are supported
Optional HP Capacity on Demand (CoD) SMP processors for non-disruptive performance growth
16-MB on-board cache per processor
Advanced crossbar switch with 7-GB memory bandwidth per building block; up to 57-GB memory bandwidth per system
Choice of memory: up to 256-GB memory supported
PCI I/O master drawer with 12 configurable PCI slots; up to 224 64-bit PCI slots supported
Up to 64 64-bit PCI buses with 12.8-GB aggregate I/O bandwidth
PCI 10/100 Mbit Ethernet adapter
18.2-GB SCSI disk drive
600-MB CD-ROM drive
Enhanced reliability with ECC-protected memory, processor cache, and system data paths
Security of RAID storage and online add and removal of CPUs
Optional redundant power supplies with N+1 power option
Tru64 UNIX or OpenVMS factory installed software (FIS); optional high availability support with Tru64 UNIX and OpenVMS cluster solutions
Product warranty, one-year hardware, on-site next business day
DA - 11424 North America — Version 7 — August 19, 2003
Page 2
QuickSpecs
Standard Features
Processor
Processor
ProcessorProcessor
Cache Memory
Cache Memory
Cache MemoryCache Memory
Architecture
Architecture
ArchitectureArchitecture
CPUs, Memory, and I/O
CPUs, Memory, and I/O
CPUs, Memory, and I/OCPUs, Memory, and I/O
Slots
Slots
SlotsSlots
Up to 32 Alpha 21264 6/1224-MHz CPUs (one CPU per module)
64K I and D caches on-chip; 16-MB ECC on-board cache per CPU
AlphaServer GS320 utilizes two-level crossbar switch structure
Quad building blocks (QBBs) support up to four CPUs, four memory modules, and eight PCI buses on a 7-GB non-blocking
crossbar switch backplane
Up to eight QBBs are connected by a second level non-blocking switch with 14-GB of bandwidth
Base systems contain one CPU and one master PCI I/O drawer
Maximum CPUs supported
Maximum memory supported
Maximum PCI slots supported
NOTE:
NOTE:
NOTE: NOTE:
System capacities shown are available with both Tru64 UNIX and OpenVMS operating systems.
Model 24 and Model 32 base systems include 12 configurable PCI slots.
Model 32
Model 32Model 32
Network and I/O
Network and I/O
Network and I/ONetwork and I/O
Controllers
Controllers
ControllersControllers
Boot/Diagnostic Devices
Boot/Diagnostic Devices
Boot/Diagnostic DevicesBoot/Diagnostic Devices
Internal Disk Expansion
Internal Disk Expansion
Internal Disk ExpansionInternal Disk Expansion
Power Supplies
Power Supplies
Power SuppliesPower Supplies
Ethernet
Console ports
Boot/diagnostic devices included in master PCI shelf box
CD-ROM or DVD-ROM
Hard Drives
Total Drive Bays
3-phase power subsystem with power cords; optional redundant 48 VDC hot swap power supplies
PCI Dual 10/100 Mbit Fast Ethernet Adapter (DE602) included in master PCI shelf box;
additional Ethernet adapters available as options
One bi-directional parallel port with 25-pin D-subminiature connector
Two EIA-232 full duplex asynchronous modem control serial ports, 9-pin D-subminiature
connectors
One PS/2 compatible keyboard port; one PS/2 compatible mouse port
One 5.25-inch half height 600-MB CD-ROM drive or 16X DVD-ROM
One 18.2-GB 10,000 rpm SCSI disk drive
Up to 14 146-GB drives (2,044 GB) may be mounted in optional storage shelves in the
system power cabinet
DA - 11424 North America — Version 7 — August 19, 2003
Page 3
QuickSpecs
Standard Features
OS Support
OS Support
OS SupportOS Support
Service and Support
Service and Support
Service and SupportService and Support
Tru64 UNIX systems include pre-installed software, Base license, Unlimited User license, Server Extension license, Internet
Express, and Secure Web Server
Support for up to eight total instances of Tru64 UNIX or OpenVMS, or a combination of both, in hardware partitions on a
single GS320 hardware platform (up to six instances supported on Model 24 systems, up to eight instances supported on
Model 32 systems)
Protected by HP Services including a one-year on-site hardware warranty training, consulting, network integration, software
support, comprehensive system maintenance and guaranteed uptime services are also available for customers requiring
higher levels of service and support.
HP AlphaServer GS320 (1224 MHz)
Tru64 UNIX refers to versions 4.0G, 5.1, 5.1A, or later. Refer to the "Supported Options List"–
– for any unique limitations based on OS version.
This Web site is available in English only.
OpenVMS refers to versions 7.2-1H1, 7.2-2, 7.3, or later. Refer to the "Supported Options List" –
– for any unique limitations based on OS version.
This Web site is available in English only.
DA - 11424 North America — Version 7 — August 19, 2003
Page 4
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Systems
Important note before you begin
Important note before you begin
Important note before you beginImportant note before you begin
Systems may be configured with more than 16 CPUs per partition, only when used with Tru64 UNIX V5.1 or OpenVMS V7.2-1H1 with Update #5. System
components, such as master PCI drawers and numbers of PCI options supported must be consistent with this requirement.
Selection of system components must be made in the context of total application requirements. Although the configuration of system components
must be done in steps (for example, base packages, CPUs, memories, etc.), these steps cannot be done in isolation.
The order in which requirements are assessed is also important, since one requirement may impact others. Before proceeding, it would be useful to
assess the total application requirements in the following order:
What level of availability is required?
If no single points of failure are allowed, then the solution should be configured as a multi-system cluster.
If access to specific devices must be assured, consider redundant adapters - RAID, N+1 power, redundant PCI drawers, and redundant consoles.
If software redundancy is required, consider clusters and/or hardware partitioning. The choice of hardware partitioning will generate a need for
multiple master PCI drawers, multiple consoles, and I/O adapters.
If the "CPU On-Line Add and Remove" feature is required, refer to document EK-GSHPG-RM for configuration and operational requirements.
What level of hardware partitioning is required for optimal system management?
What overall capacities are required in terms of processor performance, memory capacity, and disk storage?
How should the system be configured to optimize performance?
In most cases, optimum performance is achieved if the system resources (CPUs, memory, and I/O adapters) are balanced across the quad building
blocks in the system.
Memory should be configured according to application guidelines listed in Step 4.
What are the near-term system expansion needs?
How will system cabinets be physically arranged? This will determine if expansion cabinets are required and what cable lengths are required.
NOTE:
NOTE:
NOTE: NOTE:
application requirements.
System Ordering Requirements:
System Ordering Requirements:
System Ordering Requirements:System Ordering Requirements:
Certain system components or services are either required for normal operation or are recommended for best system performance and/or operation. This
document uses the following definitions to specify these options:
Most configuration steps require that these data be considered in whole or in part. Be sure to execute each step in the context of the total
Mandatory purchase
Mandatory purchase
Mandatory purchaseMandatory purchase
Required to function
Required to function
Required to functionRequired to function
available onsite.
Recommended
Recommended
RecommendedRecommended
: The system cannot function without this option or service - the option or service must be ordered with the system.
: This option or service is needed to support a working system - the option or service must be ordered with the system or be
: System performance or function will be enhanced if this option or service is ordered.
DA - 11424 North America — Version 7 — August 19, 2003
Page 5
QuickSpecs
Systems
Step 2 - Select base system
Step 2 - Select base system
Step 2 - Select base systemStep 2 - Select base system
HP AlphaServer GS320 (1224 MHz)
AlphaServer GS320 systems require selection of the following items:
Mandatory Purchases:
Mandatory Purchases:
Mandatory Purchases:Mandatory Purchases:
Base system with operating system license (either OpenVMS or Tru64 UNIX), which includes one 1224-MHz CPU module
Minimum of one memory module
Required Options and Services:
Required Options and Services:
Required Options and Services:Required Options and Services:
Software media and documentation for first system onsite
Installation and/or startup services
System management console or device and software with equivalent functionality
Recommended Services:
Recommended Services:
Recommended Services:Recommended Services:
HP Care Pack Service Package
VIS Services
NOTE:
NOTE:
NOTE: NOTE:
anticipated near-term system growth.
The base system should be selected in the context of the number of hardware partitions required, the total capacity required, and the
AlphaServer GS320 (1224-MHz) Base Systems
AlphaServer GS320 (1224-MHz) Base Systems
AlphaServer GS320 (1224-MHz) Base SystemsAlphaServer GS320 (1224-MHz) Base Systems
Model
Model
ModelModel
Model 24
Model 24
Model 24
Model 24
Model 32
Model 32
Model 32
Model 32
OS
OS
OSOS
Tru64 UNIX
Tru64 UNIX
OpenVMS
OpenVMS
Tru64 UNIX
Tru64 UNIX
OpenVMS
OpenVMS
System Boxes/
System Boxes/
System Boxes/System Boxes/
QBBs Included
QBBs Included
QBBs IncludedQBBs Included
3/6
3/6
3/6
3/6
4/8
4/8
4/8
4/8
Total CPUs
Total CPUs
Total CPUsTotal CPUs
Supported
Supported
SupportedSupported
24
24
24
24
32
32
32
32
Input Power
Input Power
Input PowerInput Power
120/208V
380-415V
120/208V
380-415V
120/208V
380-415V
120/208V
380-415V
Order Number
Order Number
Order NumberOrder Number
DA-320DG-AA
DA-320DG-AB
DY-320DG-AA
DY-320DG-AB
DA-320EG-AA
DA-320EG-AB
DY-320EG-AA
DY-320EG-AB
DA - 11424 North America — Version 7 — August 19, 2003
AlphaServer GS320 base systems contain one CPU module. Additional SMP CPUs may be added, up to the limits shown in above table. SMP CPU
options include an operating system SMP license.
HP Capacity on Demand
HP Capacity on Demand
HP Capacity on DemandHP Capacity on Demand
(CoD) CPUs
AlphaServer GS320 base systems can be configured with optional HP Capacity on Demand
(CoD) CPUs for non-disruptive future capacity expansion. The CPUs will be field installed as
part of the system installation. The total number of CPUs - base CPU, SMP CPUs, and CoD
CPUs - must adhere to the limits shown in the above table. Refer to the HP Capacity on
Demand Program described in the "Upgrades"section.
GS160/320 CoD SMP CPU, includes one 6/1224-MHz CPU module with 16-MB on-board cache,
Tru64 UNIX SMP license, and CoD program license
GS160/320 CoD SMP CPU, includes one 6/1224-MHz CPU module with 16-MB on-board cache,
OpenVMS SMP license, and CoD program license
3X-KN8AC-AD
3X-KN8AC-AE
3X-KN8CC-AD
3X-KN8CC-AE
DA - 11424 North America — Version 7 — August 19, 2003
Memory options are engineered specifically for use with this series and include additional required components that are integral to the system
architecture.
Memory options consist of a series of base modules that contain one memory array. A second array (called
"upgrades" in the table) may be added to a base module in the factory or in the field.
Memory Configuration Guidelines
Memory Configuration Guidelines
Memory Configuration GuidelinesMemory Configuration Guidelines
Memory options should be selected in the context of the application's sensitivity to memory bandwidth and memory capacity, and the number of hardware
partitions. This will determine the number of memory base modules and upgrades needed. The total capacity required will determine the size of the arrays to
be chosen.
The configuration of memory may influence the performance of applications, and there are numerous ways to configure the choices of memory base modules
and upgrade DIMMs. The following general guidelines can lead to several configuration choices. Application-specific guidelines will help narrow down the
choices.
Configuring for capacity: The highest capacity is achieved when the 3X-MS8AA-DB/DU combination is used.
Configuring for performance: Interleaved operations reduce the average latency and increase the memory throughput over non-interleaved
operations. Each memory base module is capable of 4-way interleaving with one array (no upgrades added) or 8-way interleaving with two arrays
(base module plus one upgrade). A QBB configured with eight arrays (four base modules plus four array upgrades) provides 32-way interleaving and
has the maximum potential memory bandwidth. Refer to "Memory Applications Examples" below to determine which applications gain the most
benefit from this bandwidth.
Memory modules should be configured in powers of 2: that is, 0, 1, 2, or 4 base modules in a QBB. Upgrades should also be installed in powers of 2:
0, 1, 2, or 4 base modules in a QBB.
Although mixed-capacity memory modules may be configured, the highest bandwidth is achieved when a QBB is populated with eight identical arrays:
four base modules and four upgrades. The next-highest bandwidth would be four base modules (four arrays).
If it is not possible to match the capacities of all the arrays, the next best choice is to configure pairs of identical base modules, or base
module/upgrade combinations. For example, a configuration of two 2-GB base modules (3X-MS8AA-CB), each with a 1-GB upgrade (3X-MS8AABU), is a better choice than a configuration of three 2-GB modules (3X-MS8AA-CB).
DA - 11424 North America — Version 7 — August 19, 2003
Page 8
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Options
Memory Application Examples
Memory Application Examples
Memory Application ExamplesMemory Application Examples
Configuring memory is a compromise between cost, total memory capacity, and memory bandwidth requirements. The behavior of the application must be
used to define the most-desired configuration. Some applications are sensitive to memory capacity, some are sensitive to memory bandwidth, some are
sensitive to neither. If actual application measurements are not available, the following may be used as guidelines:
Large memory (VLM) applications, in which large amounts of memory can substantially reduce I/O, may be optimized for total memory capacity and
future capacity growth. In VLM applications, the right balance might be one memory base module, with upgrade, for every two CPUs. This would
result in one memory array per CPU.
Typical commercial applications, such as transaction processing (OLTP) and multi-user timesharing, usually operate efficiently from cache and may not
be materially affected by memory bandwidth. Memory configuration is a balance between memory bandwidth and future capacity growth. It is
advisable to match the number of arrays to the number of CPUs.
Data mining can benefit from additional memory bandwidth. It is best to match the number of memory base modules to the number of CPUs.
The most demanding high-performance technical applications (HPTC) achieve a performance level that is directly proportional to memory bandwidth.
In these cases, configure one memory base module, with upgrade, per CPU. This results in two memory arrays per CPU.
The following table represents how 8 GB could be configured in a 4-CPU QBB in each of the four referenced applications. The numbers under each
application represent how many of each memory option would be ordered.
1-GB base module
1-GB upgrade
2-GB base module
2-GB upgrade
The following additional configuration options utilizing the 4-GB base module are available:
4-GB base module
4-GB upgrade
NOTE:
NOTE:
NOTE: NOTE:
Step 5 - Evaluate Configuration Requirements to Support Optional Partitioning
Step 5 - Evaluate Configuration Requirements to Support Optional Partitioning
Step 5 - Evaluate Configuration Requirements to Support Optional PartitioningStep 5 - Evaluate Configuration Requirements to Support Optional Partitioning
Configuration Requirements for Partitions
Configuration Requirements for Partitions
Configuration Requirements for PartitionsConfiguration Requirements for Partitions
Configuring partitions requires some attention to detail with respect to minimum requirements for option selection, population, and option placement.
Minimum Hardware Required per AlphaServer GS320 Hardware Partition
Minimum Hardware Required per AlphaServer GS320 Hardware Partition
Minimum Hardware Required per AlphaServer GS320 Hardware PartitionMinimum Hardware Required per AlphaServer GS320 Hardware Partition
N/R = Not recommended - For these applications, configure either four or eight like-sized memory options rather than one or two.
A single AlphaServer GS320 can be divided into logical hardware partitions, each running an instance of Tru64 UNIX or an instance of OpenVMS.
Each partition is allocated its own dedicated "shared-nothing" set of hardware resources: QBB(s), CPU module(s), memory module(s), and I/O.
Multiple-QBB hard partitions within a GS server do not provide complete hardware failure isolation across hard partitions. Single hard partitioned
QBBs within the server do provide hardware failure isolation.
Each hardware partition is viewed as a unique node, from a system point-of-view, with its own instance of Tru64 UNIX or OpenVMS operating system
and application software, independent system console, and error log.
Hardware partitions are defined on QBB boundaries; each partition is an integer multiple of QBBs.
Up to six hardware partitions are supported on GS320 Model 24 systems; up to eight hardware partitions are supported on Model 32 systems
One system management console (3X-DS8BA-xx or 3X-DS8DA-xx) and one console hub (3X-DS8AA-AA) are recommended per system.
Supported option rules apply for maximum configurations of each AlphaServer GS320 system partition. Care must be exercised to ensure that any
planned reconfiguration of hardware partitions will not violate option support rules.
– Configuring a QBB with a total of 8 GB for specific applications
Application
Application
ApplicationApplication
VLM
---
--224
22
22
--
OLTP, Timesharing
Data Mining
HPTC
4
4
-
--
N/RN/R
DA - 11424 North America — Version 7 — August 19, 2003
Page 9
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Options
Each hardware partition requires a minimum of one QBB, however, multiple QBBs are allowed within a single hardware partition. The first QBB in a hardware
partition must be configured with the minimum hardware listed below. This, and other QBBs in the partition, can be configured with additional hardware once
this minimum requirement is met.
One Alpha 21264 6/1224-MHz CPU module
One 3X-MS8AA-BB/CB/DB memory module (1 GB, 2 GB, 4 GB)
One 3X-KFWHA-AA system I/O module and one 3X-DWWPA-AA master PCI drawer. Depending upon configuration, this may require the use of a
3X-H9A20-AD/AE/AF expansion cabinet
AlphaServer GS320 systems are normally configured according to standard module placement rules, and are shipped with one copy of the operating
system installed at the factory (Tru64 UNIX or OpenVMS). However, systems with hardware partitions offer hardware and software configuration
flexibility. Factory integration services (VIS) are recommended to enable custom module configuration and factory installation of multiple copies of
the operating system on hardware partitioned systems.
Optimizing System Resources
Optimizing System Resources
Optimizing System ResourcesOptimizing System Resources
The following configuration guidelines can be used to improve performance in systems or in each partition of a hardware-partitioned system.
Balance the resources in the system (or hardware partition) based upon the available backplane space and the proposed option populations:
Sparsely configured systems, those using half or less than half of their available capacity for CPUs, memory, and PCI drawers, should be configured
with the options concentrated in as few QBBs as possible. For example, a GS320 Model 32 with 16 CPUs, 16 memory modules, and four PCI
drawers would usually be configured in the first four QBBs. The first four QBBs would be "active" and the 5th through 8th QBBs would be available for
expansion.
Densely populated systems, those using more than half of their available capacity for CPUs, memory, and PCI drawers, should be configured with the
options spread out across all QBBs.
Configure active QBBs symmetrically, each with CPUs, memory, and PCI drawers.
Configure the I/O adapters so that each active QBB has direct access to the most frequently accessed data.
System Software Required for AlphaServer GS320 Hardware Partition Support
System Software Required for AlphaServer GS320 Hardware Partition Support
System Software Required for AlphaServer GS320 Hardware Partition SupportSystem Software Required for AlphaServer GS320 Hardware Partition Support
Software Licensing for Hardware Partitions
Software Licensing for Hardware Partitions
Software Licensing for Hardware PartitionsSoftware Licensing for Hardware Partitions
Base systems include operating system license (Tru64 UNIX or OpenVMS) that licenses hardware partitions up to the physical limit of the base system
package: six hardware partitions for Model 24 systems, eight partitions for Model 32 systems.
User and capacity-based licensing is unaffected by hardware partitions. Examples:
If a product is licensed for 200 concurrent users, these users can be split among the partitions, but cannot exceed 200 total users.
If users have an enterprise capacity license for a product, that license can be loaded into the license databases on each of the hardware partitions.
Licensing Partitioned AlphaServer GS320 Systems for Both OpenVMS and Tru64 UNIX
Licensing Partitioned AlphaServer GS320 Systems for Both OpenVMS and Tru64 UNIX
Licensing Partitioned AlphaServer GS320 Systems for Both OpenVMS and Tru64 UNIXLicensing Partitioned AlphaServer GS320 Systems for Both OpenVMS and Tru64 UNIX
If the system requires both OpenVMS and Tru64 UNIX operating systems be licensed, one operating system license is included in the base system
and the second is added as a line item. The second operating system license upgrade, which includes the license for only one CPU, would be added
to the order using the following part numbers. Order appropriate media and documentation kits from Step 13.
Only those SMP processors intended for use with the second operating system must be similarly licensed. Use the following license-only part numbers
to add an SMP license for any CPUs intended for use with the second operating system:
The order of licensing is not important, but the following examples are similarly constructed for clarity. The configuration starts with a Tru64 UNIX base
system part number and the addition of OpenVMS licenses.
Example 1: 32-CPU GS320 system in which all processors are licensed for both OpenVMS and Tru64 UNIX:
Base system order would include: DA-320EE-Ax and 31 3X-KN8AB-AD SMP upgrade CPUs
Add one QB-63PAQ-AG OpenVMS software upgrade and 31 QL-MT1A9-6R OpenVMS Alpha SMP licenses
Example 2: 32-CPU GS320 system in which all processors are licensed for Tru64 UNIX and 16 processors are also licensed for OpenVMS:
Base system order would include: DA-320EE-Ax and 31 3X-KN8AB-AD SMP upgrade CPUs
Add one QB-63PAQ-AG OpenVMS software upgrade and 15 QL-MT1A9-6R OpenVMS Alpha SMP licenses
User and capacity-based licenses would be added for the second operating system environment as though it were a standalone system.
OpenVMS software upgrade for GS160/GS320
Tru64 UNIX software upgrade for GS160/GS320
OpenVMS Alpha SMP license for GS160/GS320
Tru64 UNIX Alpha SMP license for GS160/GS320
QB-63PAQ-AG
QB-595AN-AA
QL-MT1A9-6R
QL-MT4A9-6R
DA - 11424 North America — Version 7 — August 19, 2003
Step 6a - Redundant (N+1) Power SuppliesStep 6a - Redundant (N+1) Power Supplies
Power supplies included with Model 24 and Model 32 systems can support all combinations of CPUs, memory, and I/O that can be configured
within the system boxes.
Additional 48V power regulators can be ordered to provide N+ 1 power redundancy.
For Model 24 systems, order three power supplies to achieve N+ 1 capability; for Model 32 systems, order four power supplies to achieve N+1
capability.
Step 6b - Internal System Expansion
Step 6b - Internal System Expansion
Step 6b - Internal System ExpansionStep 6b - Internal System Expansion
AlphaServer GS320 Model 24 and Model 32 systems support two additional shelves in the power cabinet
Available choices are:
2000W 48V power supply
H7506-BA
One additional PCI drawer (master or expansion)
One additional PCI drawer (master or expansion) and one DS-SL13R-xx StorageWorks shelf, or
One or two StorageWorks DS-SL13R-xx shelves
Mixed configurations of BA36R and DS-SL13R-xx shelves are supported
System power cabinet provides space for up to two forward facing storage shelves.
Up to two DS-SL13R-xx Ultra3 SCSI (LVD) shelves; each shelf supports a maximum of 14
Ultra3 disk drives
Each single-bus Ultra3 shelf requires a 3X-KZPCA-AA Ultra2 (LVD) SCSI adapter or DS-KZPCCxx RAID controller and a SCSI cable to connect controller to shelf
Each split-bus Ultra3 shelf requires two 3X-KZPCA-AA Ultra2 (LVD) SCSI adapters, at least one
dual-channel 3X-KZPEA-DB Ultra3 (LVD) SCSI adapter, or DS-KZPCC-xx RAID controllers and
SCSI cables to connect controller to shelf
Ultra3 shelves connected to 3X-KZPCA-AA adapters in the power cabinet require BN38C-02
2-meter cables; DS-KZPCC-xx RAID controllers require BN37A-02 2-meter cables.
Ultra3 shelves connected to 3X-KZPCA-AA adapters in an attached expander cabinet require
BN38C-10 10-meter cables; DS-KZPCC-xx RAID controllers require BN37A-10 10-meter
cables.
Ultra3 shelves connected to 3X-KZPCA-AA adapters in a remote expander cabinet require 10
20-meter BN38C-xx cables, depending upon physical cabinet location; DS-KZPCC-xx RAID
controllers require BN37A-xx cables.
Ultra3 Universal drives are listed in a subsequent section
StorageWorks Model 4314R Ultra3 SCSI (LVD) single-bus Universal drive rackmount shelf,
International except Japan
StorageWorks Model 4314R Ultra3 SCSI (LVD) single-bus Universal drive rackmount shelf, Japan
StorageWorks Model 4354R Ultra3 SCSI (LVD) split-bus Universal drive rackmount shelf, International
except Japan
StorageWorks Model 4354R Ultra3 SCSI (LVD) split-bus Universal drive rackmount shelf, Japan
NOTE:
NOTE:
NOTE: NOTE:
Model 4314 shelf with DS-KZPCC-CE RAID controller does not support a disk drive in the last slot.
DS-SL13R-AA
DS-SL13R-AJ
DS-SL13R-BA
DS-SL13R-BJ
DA - 11424 North America — Version 7 — August 19, 2003
Page 11
QuickSpecs
Options
Power Option for
Power Option for
Power Option forPower Option for
DS-SL13R-xx Shelves
DS-SL13R-xx Shelves
DS-SL13R-xx ShelvesDS-SL13R-xx Shelves
System I/O Expansion
System I/O Expansion
System I/O ExpansionSystem I/O Expansion
Redundant power supply for 4314R Ultra3 (LVD) StorageWorks shelf, North America
Redundant power supply for 4314R Ultra3 (LVD) StorageWorks shelf, International
HP AlphaServer GS320 (1224 MHz)
Additional power supply provides N+ 1 power for 4314R Ultra3 (LVD) StorageWorks shelves;
power supply uses a dedicated location in the shelf.
Not required for 4354R shelves.
Model 24 systems support up to 12 PCI drawers; Model 32 systems support up to 16 PCI
drawers. One PCI drawer included in Model 24 and Model 32 base systems.
Model 24 and Model 32 power cabinets provide space for one additional PCI drawer if no
more than one internal storage shelf is configured.
Additional PCI drawers and storage shelves can be configured in 3X-H9A20-AD/AE/AF I/O
expansion cabinets, described in a subsequent section.
All PCI drawers contain 14 PCI slots configured into four PCI buses. Two of the buses have
four slots each; the other two buses have three slots each.
There are two types of PCI drawers: expansion drawers and master drawers. Base systems
include one PCI master drawer with 12 configurable PCI slots.
Expansion drawers contain 14 PCI slots and an N+1 redundant power system; expansion
drawers are used for most PCI expansion applications.
Optional master drawers contain 13 configurable PCI slots, N+1 redundant power system,
plus the console ports and storage devices required for use as a system console. (These devices
are listed on page 2. Note that the Fast Ethernet adapter is not included with optional master
PCI drawers.) Optional master drawers have two applications:
As redundant console sub-systems
As consoles for individual partitions in hardware partitioned systems
PCI drawers are connected to a QBB utilizing a 3X-KFWHA-AA system I/O module that
connects to the PCI drawer using two BN39B cables.
DS-SE2UP-AA
DS-SE2UP-AI
PCI Drawer Expansion
PCI Drawer Expansion
PCI Drawer ExpansionPCI Drawer Expansion
PCI drawers are connected to a QBB utilizing a 3X-KFWHA-AA system I/O module that
connects to the PCI drawer using two BN39B cables.
Maximum one additional drawer in system power cabinet; see "External Expansion Cabinets"
for more details.
PCI drawers can be split between multiple QBBs as long as all QBBs are contained within the
same hardware partition.
PCI drawers mounted in a common H9A20 Expansion Cabinet can server multiple systems.
Master PCI shelf mount box for system and I/O expansion cabinets with standard I/O PCI module
and 13 PCI expansion slots. (The 1st master comes standard with all systems and includes a standard
Ethernet network card and the system module and cable pair for connection to the QBB.)
Expansion PCI shelf mount box for system and I/O expansion cabinets with 14 PCI expansion slots
System I/O module for connecting to master or expansion PCI shelves
I/O module cable for connection between I/O module and master or expansion PCI shelves mounted
in system power cabinet; two are mandatory per system I/O module
3X-DWWPA-AA
3X-DWWPA-BA
3X-KFWHA-AA
BN39B-04
DA - 11424 North America — Version 7 — August 19, 2003
Additional PCI drawers and storage shelves can be installed in optional 3X-H9A20-AD/AE/AF expansion cabinets. Up to four 3X-H9A20AD/AE/AF cabinets are supported.
3X-H9A20-AD/AE/AF I/O expansion cabinet can be configured to hold all disk BA36R StorageWorks shelves or
DS-SL13R-xx Ultra3 StorageWorks shelves or combination of StorageWorks shelves and PCI drawers.
If no PCI drawers are configured, cabinet supports up to eight BA36R or five DS-SL13R-xx StorageWorks shelves.
If one PCI drawer is configured, cabinet supports up to five BA36R or four DS-SL13R-xx StorageWorks shelves.
If two PCI drawers are configured, cabinet supports up to four BA36R or three DS-SL13R-xx StorageWorks shelves.
If three PCI drawers are configured, cabinet supports up to two BA36R or two DS-SL13R-xx StorageWorks shelves.
If four PCI drawers are configured, cabinet supports one BA36R or DS-SL13R-xx StorageWorks shelf.
BA36R and DS-SL13R-xx StorageWorks shelves can be combined in the same expansion cabinet.
If large quantities of disks are required, the use of StorageWorks Storage Array cabinets and components is highly recommended.
Systems installed in the US and Canada may use the 3X-H9A20-AD when 120V input power is required. In all other cases, the 3X-H9A20-AF is
preferred because of the ability to support dual AC input.
3X-H9A20-AD/AE/AF cabinets may be joined to GS320 systems. PCI drawers placed in these cabinets require 7-meter I/O cables.
3X-H9A20-AD/AE/AF cabinets may be placed up to 6 meters from the system cabinet. Multiple expander cabinets may be connected to one
another or placed separately. Each group of free-standing H9A20 cabinets requires an end-panel trim kit (CK-H9A20-AB).
PCI drawers placed in remote cabinets require 10-meter I/O cables.
Black I/O expansion cabinet for use with GS320 systems, includes two 120V single-phase power
controllers and cords for use in US and Canada - Does not support dual AC input configurations
Black I/O expansion cabinet for use with GS320 systems, includes two 220-240V single phase
power controllers and cords for use in Europe – Supports dual AC input configurations
Black I/O expansion cabinet for use with GS320 systems, includes two 200-240V single phase
power controllers and cords for use in US, Canada, and Japan – Supports dual AC input configurations
Black end-panel trim kit for remote 3X-H9A20-AD/AE/AF cabinets
I/O module cables for connection between I/O module and master or expansion PCI drawers
mounted in 3X-H9A20-AD/AE/AF expansion cabinet adjacent to the system; two cables (BN39B-07
or BN39B-10) are mandatory per PCI drawer.
I/O module cables for connection between I/O module and master or expansion PCI drawers
mounted in a second expansion cabinet or in remote 3X-H9A20-AD/AE/AF expansion cabinets; two
cables (BN39B-07 or BN39B-10) are mandatory per PCI drawer.
3X-H9A20-AD
3X-H9A20-AE
3X-H9A20-AF
CK-H9A20-AB
BN39B-07
BN39B-10
DA - 11424 North America — Version 7 — August 19, 2003
Page 13
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Options
Step 7 - Storage
Step 7 - Storage
Step 7 - StorageStep 7 - Storage
Step 7a - Storage Adapters and Controllers
Step 7a - Storage Adapters and Controllers
Step 7a - Storage Adapters and ControllersStep 7a - Storage Adapters and Controllers
Tru64 UNIX supports a maximum of 64 total SCSI controllers per operating system instance (hardware partition). OpenVMS supports a maximum of
26 total SCSI controllers per operating system instance. Total SCSI controllers (all types) in the system must be within these limits regardless of the
maximum per system I/O adapter limitations. Refer to the "Supported Options List" for specific configuration rules.
Each master PCI drawer contains embedded SCSI controllers (a FIS disk and a CD), which is included in the overall count of SCSI controllers
configured in the system (or partition). Tru64 UNIX counts FIS disk and CD-ROM as an embedded SCSI device. OpenVMS counts the FIS disk only as
an embedded SCSI device. Therefore, one (OpenVMS) or two (Tru64 UNIX) SCSI controllers per master PCI drawer must be included in the total
count of SCSI devices in the system.
Calculating the total number of SCSI controllers in the system (or partition) is done by adding all the devices in the system that the operating system
categorizes as a SCSI device. Tru64 UNIX includes the following devices in this count: KZPBA-CA, KZPBA-CB, 3X-KZPBA-CC, 3X-KZPCA-AA, DSKZPCC-CE, DS-KGPSA-CA., DS-KGPSA-DA Fibre Channel, and two embedded master PCI components per master PCI drawer. OpenVMS includes
the following devices in this count: KZPBA-CA, KZPBA-CB, 3X-KZPBA-CC, 3X-KZPCA-AA, 3X-KZPEA-DB, DS-KZPCC-AC, and one embedded master
PCI component per master PCI drawer.
For cluster configurations, use Y cable (BN39A-0G).
Manufacturing may substitute correct cable lengths depending on configuration.
NOTE:
NOTE:
NOTE: NOTE:
PCI drawers must be included in this calculation.
"Per System" quantities apply to systems or to each hardware partition. The SCSI adapters included in the base system or in 3x-DWWPA-AA master
PCI Fibre Channel adapter (uses one PCI slot); requires Fibre Channel with SC
connector for adapter
2-GB PCI Fibre Channel adapter, (uses one PCI slot); requires Fibre Channel
cable with LC connector for adapter
BN38C-xx cable
VHDCI male-to-68-pin HD male UltraSCSI cable
xx=02, 03, 05, 10, 20 meters (use -02 for connecting SCSI adapter to
SCSI devices when both the PCI shelf and StorageWorks shelf are in the
system cabinet or in an adjacent expansion cabinet; use -05, -10, and -20 for
connecting SCSI adapter to SCSI devices when the PCI shelf and
StorageWorks shelf are in two different cabinets)
NOTE:
NOTE:
NOTE: NOTE:
per partition.
* = Tru64 UNIX V5.1 is required to support 62 adapters per partition and 13 adapters per PCI drawer. Tru64 UNIX 4.0G supports 24 adapters
Maximum # Supported
Maximum # Supported
Maximum # SupportedMaximum # Supported
Tru64 UNIX
Tru64 UNIX
Tru64 UNIXTru64 UNIX
Per
System
26/62*26/26*
62261326264
8888
888888
24/62*24/26*12/13*
Per
QBB
Per PCI
Drawer
13262613
OpenVMS
OpenVMS
OpenVMSOpenVMS
Per
System
Per
QBB
242412
Per PCI
Drawer
DS-KGPSA-CA
DS-KGPSA-DA
DS-KGPSA-EA
BNGBX-xx
3R-Axxxx-AA
3R-Axxxx-AA
KZPBA-CA
3X-KZPBA-CC
BN38C-xx
DA - 11424 North America — Version 7 — August 19, 2003
Page 14
Loading...
+ 30 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.