• 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 system, 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.

• Mandatory purchase: The system cannot function without this option or service - the option or service must be ordered with the system.
• Required to function: This option or service is needed to support a working system - the option or service must be ordered with the system or be available onsite.
• Recommended: System performance or function will be enhanced if this option or service is ordered.

• Base system with operating system license (either OpenVMS or Tru64 UNIX), which includes one 1001-MHz CPU module
• Minimum of one memory module

• Software media and documentation for first system onsite
• Installation and/or startup services
• System management console or device and software with equivalent functionality

• CarePaqä Priority Service Plan
• VIS Services

• 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.

• AlphaServer GS320 base systems can be configured with optional Compaq Capacity on Demand (CCoD) 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 CCoD CPUs – must adhere to the limits shown in the above table. Refer to the Compaq Capacity on Demand Program described in the ² Upgrades² section.

• 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.

• 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-MS8AA-BU), is a better choice than a configuration of three 2-GB modules (3X-MS8AA-CB).

• 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.

• 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) 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.

• One Alpha 21264 6/1001-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.

• 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.

• 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.

• 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.

• 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.

• 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.

H7506-AA

• AlphaServer GS320 Model 24 and Model 32 systems can support two additional shelves in the power cabinet.

• One additional PCI drawer (master or expansion)
• One additional PCI drawer (master or expansion) and one BA36R or DS-SL13R-xx StorageWorksä shelf, or
• One or two StorageWorks BA36R or DS-SL13R-xx shelves
• Mixed configurations of BA36R and DS-SL13R-xx shelves are supported, but cannot be factory integrated.

• System power cabinet provides space for up to two forward facing storage shelves. There are two configuration options:
• Up to two BA36R-RC/RD StorageWorks shelves; each shelf can hold a maximum of two 5.25-inch devices and one 3.5-inch device or seven
  3.5-inch devices
• Up to two DS-SL13R-xx Ultra3 SCSI (LVD) shelves; each shelf supports a maximum of 14 Ultra3 disk drives

• Each UltraSCSI StorageWorks shelf requires SCSI controller and SCSI cable to connect controller to shelf
• StorageWorks drives are listed in a subsequent section

• Each single-bus Ultra3 shelf requires a 3X-KZPCA-AA Ultra2 (LVD) SCSI adapter or DS-KZPCC-xx 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 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

• Additional power supply provides N+1 power for StorageWorks shelves; power supply uses 3.5-inch slot in StorageWorks shelf; reduces total number of devices supported by one

• StorageWorks drives are listed in a subsequent section

CK-BA35X-HH

• 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 has been 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 in 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.

• 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.

• Additional PCI drawers and storage shelves can be installed in optional 3X-H9A20-AD/AE/AF expansion cabinets. Up to four
  3X-H9A20-AD/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, but cannot be factory configured

• 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 six 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.

• 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-ROM), which is included in the overall count of SCSI controllers configured in the system (or partition). Tru64 UNIX counts FIS disk and CDROM 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 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, KZPCA-AA,
  DS-KZPCC-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, 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.

• Use 2-meter cable to connect adapters, controllers, and shelves within the GS320 power cabinet.
• Use 10-meter cable to connect adapters, controllers to shelves in attached H9A20 expander cabinets.
• Use 10 to 25-meter cables to connect adapters, controllers to shelves in remote expander cabinets.

3R-A2780-AA

254795-001

• TZ88, TSZ07, TLZ09, TKZ62, TKZ63, TKZ90, TLZ9L, TL800, TL891, TL892, TL890, TL893, TL894, TL895, TL896, DS-TLZ10-VA, TSZ20, TSZ08, DLT7000, AIT35, TZ89N

• ESA 12000 Storage Arrays and RAID Array 8000 (HSG80/HSZ80 product set) are supported on Tru64 UNIX and OpenVMS systems.
• ESA 10000 Storage Arrays are supported on Tru64 UNIX and OpenVMS systems.
• SW800 CI Storage Arrays (HSJ5x product set) are supported on OpenVMS systems.
• Complete ordering and configuring information is available at http://www.compaq.com/products/StorageWorks/

NOTE: This website is available in English only.
(Only Tru64 UNIX and OpenVMS operating systems options are supported.)

• HSZ80 UltraSCSI RAID controllers for RA8000 and ESA12000 are supported under Tru64 UNIX and OpenVMS.
• HSZ80 UltraSCSI RAID controllers require platform kit 400569-001 for Tru64 UNIX or 400571-001 for OpenVMS. PCMCIA software kit, 400566-001/QB-678AA-SA, also required for each controller.
• HSZ80 UltraSCSI controllers require KZPBA-CB/3X-KZPBA-CC adapters and BN38C cables (and UltraSCSI hubs if used)

• HSG80 Fibre Channel controllers for RA8000, MA8000, ESA12000, EMA12000 are supported under Tru64 UNIX and OpenVMS.
• HSG80 Fibre Channel controllers require platform kit 380553-001/QB-65RAB-SA for Tru64 UNIX or 380555-001/QB-65RAC-SA for OpenVMS. Software kit, 128697-B21 HSG80 ACS V8.4F or 128698-B21 V8.4P, also required for each HSG80 ordered.
• HSG80 Fibre Channel controllers require DS-KGPSA-CA/DS-KGPSA-DA Fibre Channel adapters, BNGBX cables, and fiber hubs or switches (see Fibre Channel Hubs, Switches, and Components)

• HSV110 Enterprise Virtual Storage Array Fibre Channel Controllers are only supported with a minimum of Tru64 UNIX V5.1 at this time
• HSV110 Storage Controllers require a platform kit for Tru64 UNIX V5.1 - 250193-B21, SAN VCS Controller Software kit - 250203-B22, also required for each controller pair

• HSJ54 CI Storage Array controllers are supported under OpenVMS V7.2-1H1 with CIPCA-BA CI controllers; QB-5C4AA-SA software kits required for each external cache (one for HSJ50, two for HSJ52, four for HSJ54).
• HSJ54 CI Storage Array controllers require star couplers (SC008-AB, -AC or -AD) with CIPCA-BA adapters and BNCIA cables
• Controllers require KZPBA or CIPCA SCSI adapters or controllers, as appropriate.

HSJ54-AJ

• UltraSCSI hubs are supported with KZPBA-CB/3X-KZPBA-CC PCI differential SCSI adapters.

DS-DSGGD-BA

• One Fast Ethernet adapter is included in base systems; connection of system to Ethernet requires twisted-pair cable.

• Require 3X-DWWPA-AA /BA PCI shelf mount box
• Each adapter/controller uses one PCI slot
• A maximum of sixteen network adapters - 3X-DE602-xx, DEGPA-xx, 3X-DEFPA-xx - are supported per system or hardware partition.

BN26M-xx

• Up to two PCI System Area Network controllers are supported on a GS320 partition
• Two-node clusters can be configured by ordering a CCMAB-AA for each node and one BN39B-04 or BN39B-10 cable; cable connects directly to CCMAB-AA in each node.
• For a two-node cluster that will not be rebooted when adding additional members, order one CCMAB-AA adapter and one BN39B-04 or BN39B-10 cable for each node, and one CCMHB-AA hub for the cluster.
• For three or four node clusters, order one CCMAB-AA adapter and one BN39B-04 or BN39B-10 cable for each node and one CCMHB-AA hub for the cluster
• CCMHB-AA includes four CCMLB-AA line cards and supports up to four nodes; expansion up to eight system nodes can be achieved by adding up to four additional CCMLB-AA line cards
• If two or more CCMAB-AA controllers are configured in each node (dual rail), a second CCMHB-AA hub is required
• If using a MEMORY CHANNEL adapter module (54-24962-01) prior to revision D02, up to two MEMORY CHANNEL adapters can be placed on a PCI bus, however, no additional PCI devices can be placed on the same PCI bus, and the remaining slots must be left empty

• Each system in the cluster requires a TruCluster Server software license
  (QL-6BRAQ-AA)
• Alternately a TruCluster Plus Software package including licenses for: TruCluster Server, Logical Storage Manager, and AdvFS Utilities can be ordered (QP-6R9AQ-AA)

• Requires OpenVMS V7.2-1H1 or later and OpenVMS Cluster license
  (QL-MUZAQ-AA)

• In cases where nodes must be separated by a longer distance than standard copper cables allow, the CCMFB option converts the output of the standard CCMAB controller or CCMLB line card to single-mode fiber optic cable. The fiber optic connection may be up to 2,000 meters long between two CCMAB controllers connected in virtual hub mode, or 3,000 meters between a CCMAB controller and a CCMHB hub. (The connection from the CCMHB hub to a second system may also be 3,000 meters). The CCMFB option requires a second PCI slot in the system from which it draws power only. It is normally connected to the corresponding CCMAB controller with the short BN39B-01 cable. The CCMFB is also used in the CCMHB hub where it occupies a slot normally used by the CCMLB line card, limiting expansion to four radial fiber optic connections.
• The CCMHB-BA hub expansion box provides additional slots for up to eight fiber optic connections. Two standard length, single-mode fiber optic cables are available (BN34R-10 and BN34R-31); however, users normally provide this connection. Customers should reference the TIA/EIA 568-A Commercial Building Telecommunications Cabling Standard, Section 12.3.4. Fiber optic connectivity is completely transparent to the systems using it and has no performance impact.
• Up to two CCMHB-AA hubs may be mounted in a 3X-H9A20-AD expansion cabinet by utilizing a 2T-MAVRK-AA rack-mounting kit for each hub. A second MEMORY CHANNEL Hub (CCMHB-AA or CCMHM-BA) mounted in an expansion cabinet reduces the amount of StorageWorks shelves by one.

BN35S-02

• AlphaServer GS320 systems require the ability to log console messages, provide remote access for service and support, and, in some cases, manage multiple hardware partitions. The system management console is mandatory if the customer has no other means to provide these capabilities.
• PC-based system management console is required for system power-up, diagnostics, console partitioning, and console display and logging for use with AlphaServer GS160/320 systems.
• Includes network interface cards, universal modem, console software, 101-key keyboard, mouse, and console documentation kit
• A monitor is required for use with the system management console. Choose monitor listed in Step 12.
• Systems configured with redundant consoles or employing hardware partitioning require the ability to connect multiple consoles. A console hub is mandatory if the customer has no other means to provide these capabilities.

ConsoleWorks Upgrade Licenses

• System management consoles include ConsoleWorks, which support s up to eight partitions on a single system
• Support for additional GS Series partitions on a second GS system requires the purchase of an add-on license for 2, 4, or 8 partitions on that system
• Use of a single console for management of multiple GS systems requires use of a multiple port Ethernet Hub such as HP Procurve Series

• 3X-DS8BA-AA/BA includes a localization kit for use in U.S., Canada, Japan, Mexico, Brazil, Argentina, Peru, and Taiwan.
• 3X-DS8BA-AB/BB includes a localization kit for use in Great Britain, Ireland, Hong Kong, Singapore, and Malaysia

• The system management console includes a line cord for use in North America. Order a country-specific line cord if required.

• Graphics support for an AlphaServer GS320 can be provided through use of a graphics adapter

SN-PBXGF-AB

• Graphics monitors other than those listed below can be used if compatible with SVGA graphics ordered with system.
• Selection of video extension cable and country-specific power cord is mandatory for all monitors; order power cord as appropriate.
• Add or order appropriate keyboard and mouse
• Monitors will ship with, but not be integrated with systems.

• Select a keyboard and mouse
• Select an opal OpenVMS keyboard for use with VT5xx text terminals.
• All keyboards listed may not be available in all geographies

• Media and documentation required for first system on site
• Software Processor Code = Q

• Tru64 UNIX base systems include pre-installed software, Base license, Unlimited User license, Server Extension license, Internet Express, and iPlanet Web Server Enterprise Edition 4.0

• OpenVMS base systems include Base license and Compaq Enterprise Integration Server License Package Revision V3.0A
• OpenVMS Concurrent Use licenses provide the right to interactively use the operating system by the specified number of concurrent users on a designated OpenVMS system. OpenVMS Concurrent Use licenses can be moved from one system to another at user discretion and can be shared in a mixed OpenVMS VAX and OpenVMS Alpha cluster.

• One SMP Extension License (included in the SMP CPU upgrade) is mandatory for each CPU after the first CPU.
• For each AlphaServer GS320 CPU in an OpenVMS Galaxy, one OpenVMS Galaxy License is mandatory.
• Compaq layered products are licensed as follows:
• One capacity license per system
• One user license per use
• Up to eight instances of OpenVMS are supported in OpenVMS Galaxy configurations on AlphaServer GS320 Model 32 systems, up to six instances on Model 24 systems.
• One OpenVMS Base Operating System License (included in base system) is mandatory for AlphaServer GS320 configured as an OpenVMS Galaxy system.

• Base system order would include a DY-320DE-Ax and 23 3X-KN8AB-AE SMP upgrade CPUs
• Add one QL-66XAA-3E Galaxy 8-CPU license and one QL-66XAA-3F Galaxy 16-CPU license for a total of 16 Galaxy licenses for the 16-CPU hard partition with Galaxy.

• Installation or Installation and Startup is required for all AlphaServer GS320 systems.
• Select one of the optional CarePaq Priority Service Packages described below that best supports the customer’s operational requirements for system availability.

• CarePaq Priority Services are available for AlphaServer systems running Tru64 UNIX or OpenVMS operating systems. Priority Services are designed for the growing number of customers who need support beyond the basic warranty. Five packages are offered - Priority, Priority 24, Priority Silver, Priority Gold, and Priority Executive with coverage for both Principal servers systems and SSPs (Subsequent System Packages) - that meet a full range of customer support requirements.

• 9 x 5 HW/SW support
• 4-hour response on-site hardware support
• 2-hour response for Bronze software support
• License Subscription for Compaq O/S software and embedded L/P (i.e., EIS for OpenVMS, unlimited users, and server extensions for Tru64 UNIX)
• Condist update distribution for OpenVMS or Tru64 UNIX and their layered products. (Layered products not included on Condist can be ordered separately.)

• 24 x 7 HW/SW support
• Named HW engineer
• 4-hour response on-site hardware support
• 2-hour response for Bronze software support
• License Subscription for Compaq O/S software and embedded L/P (i.e., EIS for OpenVMS, unlimited users, and server extensions for Tru64 UNIX)
• Condist update distribution for OpenVMS or Tru64 UNIX and their layered products. (Layered products not included on Condist can be ordered separately.)

• 24 x 7 HW Support. Named Engineer, 4-hour response
• 24 x 7 Silver SW Support - Named Account Rep, 1-hour response Monday – Friday, 8AM-5PM local time; 2-hour response remaining hours
• License Subscription for Compaq O/S software and embedded L/P (i.e., EIS for OpenVMS, unlimited users, and server extensions for Tru64 UNIX)
• Condist update distribution for OpenVMS or Tru64 UNIX and their layered products. (Layered products not included on Condist can be ordered separately.)
• Technical newsletter and SW activity review
• Proactive Patch Notification
• One (1) System Healthcheck per year

• 24 x 7 HW support with Named Engineer, 4-hour response for on-site support
• 24 x 7 Gold SW support - Named Account Rep
• 30-minute callback (critical); 1-hour callback (non-critical)
• License Subscription for Compaq O/S software and embedded L/P (i.e., EIS for OpenVMS, unlimited users, and server extensions for Tru64 UNIX)
• Condist update distribution for OpenVMS or Tru64 UNIX and their layered products. (Layered products not included on Condist can be ordered separately.)
• Technical newsletter, SW activity review and 10 hours Upgrade impact planning
• Proactive Revision Management
• Two (2) System Healthchecks per year
• Mandatory pre-qualification required

• 24 x 7 HW support with Named Engineer, two-hour response for on-site support
• 24 x 7 Gold SW support - Named Account Rep
• 30-minute callback (critical); one-hour callback (non-critical)
• License Subscription for Compaq O/S software and embedded L/P (i.e., EIS for OpenVMS, unlimited users, and server extensions for Tru64 UNIX)
• Software update distribution on CD-ROM: OpenVMS or Tru64 UNIX and their layered products (Layered products not included on Condist can be ordered separately.)
• Technical newsletter, SW activity review and 10 hours Upgrade impact planning
• Proactive Revision Management
• Two (2) System Healthchecks per year
• Customer site must be within 25 miles of a Compaq service location
• Mandatory pre-qualification required

• For Priority, Priority 24, Priority Silver, Priority Gold, and Priority Gold Executive
• HW Support at same level as corresponding package for Principal server
• License Subscription: Compaq O/S (where applicable)
• Telephone support through Principal server covered by full support package

• Preinstallation review
• Unpacking of equipment
• Assemble and test
• Basic product usage info
• No software installation added

• Preinstallation review
• Unpacking of equipment
• Assemble and test
• Basic product usage info
• Install operating systems
• Product configuration
• Print and network access
• Orientation

1 year

3 years

1 year

3 years

• AlphaServer GS320 systems include one-year hardware warranty with 5 x 9, on-site Next Business Day response.
• New Compaq hardware options internal to the AlphaServer enclosure receive the same warranty or service level as purchased with the server.
• External storage devices/cabinets carry their own level of warranty and should be quoted separately for uplifted warranty services.
• In addition to the CarePaq Priority Services, uplifted warranty Supplemental Services are available for separate hardware and software support. For more information on Hardware and Software Supplemental Services and other service options available for AlphaServers, consult your Sales Account Manager or visit http://www.compaq.com/services/

NOTE: This website is available in English only.

• Systems include 90-day Conformance to SPD and Telephone Advisory Support. Select optional Software Supplemental Support Services if required.
• Software service upgrades for Tru64 UNIX include advisory and remedial software support with new version license rights for Tru64 UNIX Base, unlimited users, and Server Extensions
• Software service upgrades for OpenVMS include advisory and remedial software support with new version license rights for OpenVMS Base and Enterprise Integration Package

• Evaluate their requirements and current systems/applications environment
• Plan the server partitioning, storage layout, installation, and migration of the new system
• Perform installation and set-up
• Provide initial system performance tuning
• Provide training in the use of the System Control Manager

QS-GS2A9-CP

• Basic Integration Service (YT-CSSIT-V1) System integration, testing, extended burn-in, custom documentation, and installation of a single operating system instance
• Partioning Service (YT-CSSIT-P1) Configuration of additional instances of an operating system
• System integration, testing, extended burn-in, and custom documentation of hardware-partitioned systems

YT-CSSIT-V1

• Staging and Integration of the AlphaServer GS320
• Software load of a single instance of an operating system and current revisions of firmware
• Hardware configuration, custom placement, and integration of internal options of the server per customer specifications
• Installation of a single instance of either Tru64 UNIX or OpenVMS Operating System
• Configuration, exercise, and test of up to one intelligent RAID array controller and associated disks per customer requirements
• Testing of the system and its components for a full 100 hour burn-in
• Mini-CCD (Custom Configuration Documentation) containing equipment listing, system environmental information, and software version levels

YT-CSSIT-P1

• Technical edit of order to guide component selection and option placement
• Software load of an instance of an operating system on a hardware/software partition
• Configuration and hardware integration (as described above) of the server partition per specifications
• Partition testing with the system and its components during the 100 hour burn-in

YT-CSSIT-R1

• Technical edit of order to guide component selection and option placement
• Configuration of the disks of the additional controller pair per customer specifications
• Hardware configuration verification
• Custom disk placement and verification
• Installation of current revisions of firmware
• Configuration, exercise and testing of up to one pair of additional intelligent array controller pair and associated disk drives for each YT-CSSIT-R1
• Controller and disk testing with the system and its components during the 100 hour burn-in

YT-CSSIT-C1

• Technical edit of order to guide component selection and option placement
• Configuration of a cluster per specifications
• Hardware and software configuration verification
• Installation of either Tru64 UNIX TruCluster software or OpenVMS cluster software and configuration of node functions
• Installation of current revisions of firmware
• Cluster failover testing with the system and its components during the full 100 hour burn-in

• A dual-AC power option provides the capability to connect to two separate synchronized AC feeds - a primary AC feed and a secondary AC feed. The feeds can be direct from the power utility, or they can be a combination of utility feeds and UPS or generator feeds. The preferred (primary) feed is chosen and set by the user. In the event of failure of the primary feed, the switch will automatically transfer the load to the secondary feed without power interruption. The selected AC feed can also be switched manually.
• The option cabinet must be positioned adjacent to the system power cabinet and it is bolted to it.
• Power requirements for the dual AC power option are identical to the system to which it is connected.
• The dual-AC switch option can be factory configured or installed as a field upgrade.
• The primary and secondary 3-phase AC sources must be nominally of the same level, frequency and phase rotation. To ensure virtually uninterrupted transfers between the two AC sources, the two input sources must be synchronized, typically within 5 to 15 electrical degrees. Questions regarding the dual-AC option can be answered by an environmental specialist at 1-800-354-9000.
• The primary and secondary 3-phase AC sources must have a THD of less than 10%.

• One AC switch configured within an H9A20 cabinet (3X-H7512-AC/AD). The cabinet has dedicated mounting space for a second AC switch that is not included.
• A second electronic AC switch (3X-H7512-BA/BB) that mounts within the 3X-H7512-AC/AD cabinet.
• AlphaServer GS320 Model 24 and Model 32 systems require both the 3X-H7512-AC/AD and the 3X-H7512-BA/BB

DH-320EF-AX

• Upgrades require the return of the replaced System Box and SMP modules

• AlphaServer trim panel can be ordered to change external top gun blue skins to carbon black

• Customer purchases a system with Tru64 UNIX or OpenVMS CCoD SMP CPU(s) (3X-KN8CA-AD or 3X-KN8CA-AE), or customer purchases Tru64 UNIX or OpenVMS CCoD SMP CPU(s) for field installation within an installed AlphaServer GS320 system.
• When purchasing the CCoD CPU(s), the customer signs a CCoD program agreement to purchase the CPU module(s) within 18 months or upon ² first use² of the module(s).
• A blank copy of the agreement is available through your local Compaq representative or call 1-800-AT-COMPAQ (1-800-282-6672)
  Full program terms are outlined in this agreement.

• The customer will be invoiced for the CPU module(s) upon notification by the customer of ² first use² or expiration of the 18-month period.