Filter
Top Products
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 ResourcesOptimizing System Resources
Optimizing 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 SupportSystem Software Required for AlphaServer GS320 Hardware Partition Support
System Software Required for AlphaServer GS320 Hardware Partition Support
Software Licensing for Hardware Partitions
Software Licensing for Hardware PartitionsSoftware Licensing for Hardware Partitions
Software 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 UNIXLicensing Partitioned AlphaServer GS320 Systems for Both OpenVMS and Tru64 UNIX
Licensing 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.
OpenVMS software upgrade for GS160/GS320
QB-63PAQ-AG
Tru64 UNIX software upgrade for GS160/GS320
QB-595AN-AA
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:
OpenVMS Alpha SMP license for GS160/GS320
QL-MT1A9-6R
Tru64 UNIX Alpha SMP license for GS160/GS320
QL-MT4A9-6R
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.
QuickSpecs
HP AlphaServer GS320 (1224 MHz)
Options
DA - 11424 North America — Version 7 — August 19, 2003
Page 10