HP customers have consistently achieved higher levels of satisfaction when key components of their IT infrastructures are implemented using the Solution Life Cycle. The Solution Life Cycle focuses on rapid productivity and maximum availability by examining customers' specific needs at each of five distinct phases (plan, design, integrate, install, and manage) and then designing their Superdome solution around those needs.

HP offers three pre configured service solutions for Superdome that provide customers with a choice of lifecycle services to address their own individual business requirements.

• Foundation Service Solution: This solution reduces design problems, speeds time to production, and lays the groundwork for long term system reliability by combining pre installation preparation and integration services, hands on training and reactive support. This solution includes HP Support Plus 24 to provide an integrated set of 24×7 hardware and software services as well as software updates for selected HP and third party products.
  
• Proactive Service Solution: This solution builds on the Foundation Service Solution by enhancing the management phase of the Solution Life Cycle with HP Proactive 24 to complement your internal IT resources with proactive assistance and reactive support. Proactive Service Solution helps reduce design problems, speed time to production, and lay the groundwork for long term system reliability by combining pre installation preparation and integration services with hands on staff training and transition assistance. With HP Proactive 24 included in your solution, you optimize the effectiveness of your IT environment with access to an HP certified team of experts that can help you identify potential areas of improvement in key IT processes and implement necessary changes to increase availability.
  
• Critical Service Solution: Mission Critical environments are maintained by combining proactive and reactive support services to ensure maximum IT availability and performance for companies that can't tolerate downtime without serious business impact. Critical Service Solution encompasses the full spectrum of deliverables across the Solution Lifecycle and is enhanced by HP Critical Service as the core of the management phase. This total solution provides maximum system availability and reduces design problems, speeds time to production, and lays the groundwork for long term system reliability by combining pre installation preparation and integration services, hands on training, transition assistance, remote monitoring, and mission critical support. As part of HP Critical Service, you get the services of a team of HP certified experts that will assist with the transition process, teach your staff how to optimize system performance, and monitor your system closely so potential problems are identified before they can affect availability.
  

• HP's Mission Critical Partnership: This service offering provides customers the opportunity to create a custom agreement with Hewlett Packard to achieve the level of service that you need to meet your business requirements. This level of service can help you reduce the business risk of a complex IT infrastructure, by helping you align IT service delivery to your business objectives, enable a high rate of business change, and continuously improve service levels. HP will work with you proactively to eliminate downtime, and improve IT management processes.
  
• Service Solution Enhancements: HP's full portfolio of services is available to enhance your Superdome Service Solution in order to address your specific business needs. Services focused across multi operating systems as well as other platforms such as storage and networks can be combined to compliment your total solution

• Redundant Power Supply
• Redundant Fans
• HP-UX operating system with unlimited user license
• Factory Integration of memory and I/O Cards
• Installation Guide, Operators Guide, and Architecture Manual
• HP Site planning and Installation
• One year warranty with same business day on-site service response

A Superdome system can consist of up to four different types of cabinet assemblies:

• At least one Superdome left cabinet. The Superdome cabinets contain all of the processors, memory and core devices of the system. They will also house most (usually all) of the system's I/O cards. Systems may include both left and right cabinet assemblies containing, a left or right backplane respectively.
• One or more HP Universal Rack cabinets. These 19-inch rack cabinets are used to hold the system peripheral devices such as disk drives.
• Optionally, one or more I/O expansion cabinets (utilizing the Universal Rack). An I/O expansion cabinet is required when a customer requires more PCI cards than can be accommodated in their Superdome cabinets.

Superdome cabinets are serviced from the front and rear of the cabinet only. This enables customers to arrange the cabinets of their Superdome system in the traditional row fashion found in most computer rooms. The width of the cabinet accommodates moving it through common doorways in the U.S. and Europe. The intake air to the main (cell) card cage is filtered. This filter can be removed for cleaning/replacement while the system is fully operational.

A status display is be located on the outside of the front and rear doors of each cabinet. The customer and field engineers can therefore determine basic status of each cabinet without opening any cabinet doors.

For PA-8800 and PA-8900 processors (dual core per processor):

• Superdome 32 processor cores: single cabinet (a left cabinet)
• Superdome 64 processor cores: single cabinet (a left cabinet)
• Superdome 128 processor cores: dual cabinet (a left cabinet and a right cabinet)
  

Each cabinet may contain a specific number of cell boards (consisting of processors and memory) and I/O. See the following sections for configuration rules pertaining to each cabinet. The base configuration product numbers for each of the models are as follows:

A cell, or cell board, is the basic building block of a Superdome system. It is a symmetric multi-processor (SMP), containing:

• Four processor sockets that can hold PA 8600, PA 8700, PA 8800 or PA-8900 processors (only one type is allowed per cell)
• Memory (up to 16-GB RAM with 512-MB DIMMs, 32-GB RAM with 1-GB DIMMs and 64-GB with 2-GB DIMMs.
  NOTE: Only 1 GB and 2 GB DIMMs are supported with Superdome PA 8800 and PA 8900).
• One cell controller (CC)
• Power converters
• Data buses
• Optional link to I/O card cage

Please note the following:

• PA-8600 and PA-8700 processors can be mixed within a Superdome system, but must reside on different cells and in different partitions (nPars). PA-8800 and PA-8900 processors cannot be mixed within a Superdome system with PA-8600 or PA-8700 processors.
• A Superdome PA-8800 and PA-8900 system can support up to 1 TB of memory with 2 GB DIMMs. However, due to the limitation of HP-UX 11i, the maximum amount of memory supported in a partition is 512 GB.
• For PA-8600 and PA-8700 processors: The minimum configuration includes one active processor and 2 GB memory per cell board. The maximum configuration includes four active processor and 16 GB memory per cell board. Each cell board ships with four PA-8600 or PA-8700 processors. However, based on the number of active processors ordered, from one through four processors are activated prior to shipment.
• For PA-8800 and PA-8900 processors: The minimum configuration includes one active processor and 2 GB of memory per cell board. The maximum configuration includes eight active processors and 64 GB of memory per cell board using 2 GB DIMMs. The minimum number of active processors on each cell board is one. Additional processors on the cell board can be activated individually (not in pairs).
• 512 MB, 1 GB and 2 GB DIMMs can be mixed on a cell board in Superdome PA 8800 and PA 8900 systems only.

Each I/O chassis provides twelve I/O slots. Superdome PA-8600 and Superdome PA-8700 support I/O chassis with 12 PCI 66 capable slots, eight supported via single (1x) ropes (266 MB/s peak) and four supported via dual (2x) ropes (533 MB/s peak). Superdome PA-8800 and PA-8900 supports I/O chassis with 12 PCI-X 133 capable slots, eight supported via single enhanced (2x) ropes (533 MB/s peak) and four supported via dual enhanced (4x) ropes (1066 MB/s peak).

Each Superdome cabinet supports a maximum of four internal I/O chassis. The optional I/O expansion cabinet can support three I/O chassis enclosures (ICE), each of which supports two I/O chassis for a maximum of six I/O chassis per I/O expansion cabinet.

Each Each cell board connects to at most one I/O chassis, and therefore the number of I/O chassis supported is dependent on the number of cells present in the system. A Superdome system can have more cells than I/O chassis. For instance, an 8 cell Superdome can have one to eight I/O chassis. Each partition must have at least one I/O chassis with the number of I/O chassis not exceeding the number of cells.

A 4-cell Superdome supports four I/O chassis for a maximum of 48 PCI slots.

An 8-cell Superdome supports eight I/O chassis for a maximum of 96 PCI slots. Since a single Superdome cabinet only supports four I/O chassis, an I/O expansion cabinet and two I/O chassis enclosures are required to support all eight I/O chassis.

A 16-cell Superdome supports 16 I/O chassis for a maximum of 192 PCI slots. Since two Superdome cabinets (left and right) only support eight I/O chassis, two I/O expansion cabinets and four I/O chassis enclosures are required to support all 16 I/O chassis. The four I/O chassis enclosures are spread across the two I/O expansion cabinets, either three ICE in one I/O expansion cabinet and one ICE in the other or two ICE in each.

Superdome's core I/O provides the base set of I/O functions required by every Superdome partition. Each partition must have at least one core I/O card in order to boot. Multiple core I/O cards may be present within a partition (one core I/O card is supported per I/O backplane); however, only one may be active at a time. Core I/O will utilize the standard long card PCI form factor but will add a second card cage connection to the I/O backplane for additional non-PCI signals (USB and utilities). This secondary connector will not impede the ability to support standard PCI cards in the core slot when a core I/O card is not installed.

Newer sx2000 based systems (which support only the PA-8900) do not require and do not support the traditional core I/O card. These systems do require LAN connectivity at a minimum to support system boot. Other I/O cards can be added to this basic functionality.

Any I/O chassis can support a Core I/O card that is required for each independent partition. A system configured with 16 cells, each with its own I/O chassis and core I/O card could support up to 16 independent partitions. Note that cells can be configured without I/O chassis attached, but an I/O chassis cannot be configured in the system unless attached to a cell.

The core I/O card's primary functions are:

• Partitions (console support) including USB and RS-232 connections
• 10/100Base-T LAN (general purpose)

Other common functions, such as Ultra/Ultra2 SCSI, Fibre Channel, and Gigabit Ethernet, are not included on the core I/O card. These functions are, of course, supported as normal add in cards.

The unified 100Base-T Core LAN driver code searches to verify whether there is a cable connection on an RJ-45 port or on an AUI port. If no cable connection is found on the RJ-45 port, there is a busy wait pause of 150 ms when checking for an AUI connection. By installing the loopback connector (description below) in the RJ-45 port, the driver would think an RJ 45 cable was connected and would not continue to search for an AUI connection, hence eliminate the 150 ms busy wait state:

The I/O expansion functionality is physically partitioned into four rack mounted chassis-the I/O expansion utilities chassis (XUC), the I/O expansion rear display module (RDM), the I/O expansion power chassis (XPC) and the I/O chassis enclosure (ICE). Each ICE supports up to two 12-slot I/O chassis.

When an I/O Expansion cabinet is ordered as an upgrade to a Superdome system, it includes the factory testing and integration of any components that are ordered at the same time as the cabinet. This includes any I/O Chassis, PCI or PCI-X cards and peripherals. If it is ordered as an upgrade but not at the time of the Superdome system, additional installation assistance may be required and can be ordered as field installation products.

The only field rackable I/O expansion components are the ICE and the 12 slot I/O chassis. Either component would be field installed when the customer has ordered additional I/O capability for a previously installed I/O expansion cabinet.

No I/O expansion cabinet components will be delivered to be field installed in a customer's existing rack other than a previously installed I/O expansion cabinet. The I/O expansion components were not designed to be installed in racks other than the 10K G2 Universal Rack. In other words, they are not designed for Rosebowl I, pre merger Compaq, Rittal, or other third party racks.

The I/O expansion cabinet is based on the 10K G2 Universal Rack and all expansion components mount in the rack. Each component is designed to install independently in the rack. The 10K G2 Universal Rack has been modified to allow I/O interface cables to route between the ICE and cell boards in the Superdome cabinet. I/O expansion components are not designed for installation behind a rack front door. The components are designed for use with the 10K G2 Universal Rack perforated rear door.

The I/O chassis enclosure (ICE) provides expanded I/O capability for Superdome. Each ICE supports up to 24 I/O slots by using two 12 slot Superdome I/O chassis. The I/O chassis installation in the ICE puts the I/O cards in a horizontal position. An ICE supports one or two 12 slot I/O chassis. The I/O chassis enclosure (ICE) is designed to mount in a 10K G2 Universal Rack and consumes 9U of vertical rack space.

To provide online addition/replacement/deletion access to I/O cards and hot swap access for I/O fans, all I/O chassis are mounted on a sliding shelf inside the ICE.

Four (N+1) I/O fans mounted in the rear of the ICE provide cooling for the chassis. Air is pulled through the front as well as the I/O chassis lid (on the side of the ICE) and exhausted out the rear. The I/O fan assembly is hot swappable. An LED on each I/O fan assembly indicates that the fan is operating.

Although the individual I/O expansion cabinet components are designed for installation in any Rack System E cabinet, rack size limitations have been agreed upon. IOX Cabinets will ship in either the 1.6-meter (33U) or 1.96-meter (41U) cabinet. In order to allay service access concerns, the factory will not install IOX components higher than 1.6 meters from the floor. Open space in an IOX cabinet will be available for peripheral installation.

Refer to the 10K G2 Series Rack Best Practices Guide for information on rack deployment, stabilization, and transportation. Go to http://HP.com/go/rackandpower for more information.

All peripherals qualified for use with Superdome and/or for use in a Rack System E are supported in the I/O expansion cabinet as long as there is available space. Peripherals not connected to or associated with the Superdome system to which the I/O expansion cabinet is attached may be installed in the I/O expansion cabinet.

No servers except those required for Superdome system management such as Superdome Support Management Station or ISEE may be installed in an I/O expansion cabinet.

Peripherals installed in the I/O expansion cabinet cannot be powered by the XPC. Provisions for peripheral AC power must be provided by a PDU or other means.

If an I/O expansion cabinet is ordered alone, its field installation can be ordered via option 750 in the ordering guide (option 950 for Superdome Advanced Architect Program Channel partners).

The DVD solution for Superdome requires the following components per partition. External racks AF004A or AF014A must also be ordered with the DVD solution.

Hardware Partitions
A hardware partition (nPar) consists of one or more cells that communicate coherently over a high bandwidth, low latency crossbar fabric. Individual processors on a single cell board cannot be separately partitioned. nPars are logically isolated from each other such that transactions in one nPar are not visible to other nPars within the same complex.

Each nPar runs its own independent operating system. Different nPars may be executing the same or different revisions of an operating system. On HP Integrity Superdome systems, nPars may be executing different operating systems altogether (HP-UX, Windows Server 2003 or Linux). Please refer to the HP Integrity Superdome section for details on these operating systems.

Each nPar has its own independent processors, memory and I/O resources consisting of the resources of the cells that make up the nPar. Resources may be removed from one nPar and added to another without having to physically manipulate the hardware just by using commands that are part of the System Management interface.

Superdome HP-UX 11i supports static nPars. Static nPars imply that any nPar configuration change requires a reboot of that nPar. In a future HP-UX release, dynamic nPars will be supported. Dynamic nPars imply that the nPar configuration changes do not require a reboot of that nPar. Using the related capabilities of dynamic reconfiguration (i.e. on-line addition, on-line removal), new resources may be added to an nPar and failed modules may be removed and replaced while the nPar continues in operation.

NOTE: It is possible for PA-8800 and PA-8900 nPars to co exist with Itanium 2 1.6 GHz nPars in the same Superdome system, but on different partitions. Customers can configure an Itanium 2 1.6 GHz nPar in an HP-9000 Superdome running PA-8800 or PA-8900 (and vice versa) in the field only. Factory orders for mixed Itanium and PA RISC nPars are not allowed.

Virtual Partitions
A virtual partition (vPar) provides the capability of dividing a system into different HP UX operating system images.

VPars is available on HP-UX 11i and therefore can run on Superdome PA 8600/PA 8700 servers. vPars on Superdome PA-8800 and PA-8900 is also supported.

1) Which processors can be mixed in a Superdome?

The first step in determining which processors can be mixed within a Superdome is to look at the chipset. A Superdome can only support one type of chipset (legacy chipset or sx1000 chipset or sx2000) at a time.

The legacy chipset only supports the PA RISC architecture. The PA 8600, PA 8700, and PA 8700+ processors were supported with this chipset. As a result, they can be mixed within the Superdome but they cannot be mixed with processors supported by other chipsets (i.e., Itanium 9M with the sx1000 chipset).

With the sx1000 and sx2000 chipsets, processors of like architectures (PA RISC and Itanium architectures) that are supported by the specific chipset can be mixed in separate hard partitions. For example, the HP 9000 Superdome supports mixing the PA 8800 and PA 8900 processors in separate hard partitions. As an example, a subset of the PA RISC and Itanium processors (PA 8800, PA 8900 and Itanium 9M processors) can be supported at the same time in different hard partitions within a Superdome.

The table below highlights which processors can co-exist on a Superdome in separate hard partitions.

2) In order to run an Itanium-based partition in an HP 9000 server, what changes are required?

In order to add a new partition with Itanium 2 9M processors on an HP 9000 Superdome, the following steps are required:

Step #1: Upgrade firmware on PA-RISC based partitions

Step #2: Create a new hard partition in the Superdome for Itanium 2-based cell (s)

Step #3: Plug in cell boards for Itanium 2-based cells

Step #4: Some I/O cards may need to be added for that specific hard partition (Windows does not support the identical set of I/O cards that HP-UX 11i supports)

Step #5: Load operating system for Itanium 2-based partition

Upgrading a PA-RISC partition to support Itanium 2 processors would require similar steps:

Step #1: Upgrade firmware on PA-RISC based partitions

Step #2: Pull out existing PA-RISC cell boards

Step #3: Swap existing memory into cell boards for Intel Itanium 2 processor (protects investment in current memory)

Step #4: Plug in cell boards for Itanium 2-based cell boards

Step #5: Some I/O cards may need to be added for that specific hard partition (Windows does not support the identical set of I/O cards that HP-UX 11i supports)

Step #6: Load operating system for Itanium 2-based partition

The in-box addition of Itanium 2 processors can be done with no additional hardware, no new chassis and no change to backplane.

3) When will mixing of PA-RISC and Itanium 2 processors be available?

Support for mixing PA RISC and Itanium 2 processors within systems based on the sx1000 and/or sx2000 chipsets (in separate hard partitions) is available now

4) Is mixing of PA-RISC and Itanium processors factory configurable?

NO. The way to do this is to enable PA RISC systems that shipped from the factory to add Itanium partitions later on in the field. In addition, HP offers the ability to enable Itanium based systems that shipped from the factory to add PA RISC partitions later on in the field.

The current policy is not to allow PA RISC or Intel Itanium based partitions to be added to systems in the factory. However, depending on the geographic region, shipment of Superdome systems with a mix of PA RISC and Intel Itanium based partitions may be possible.

5) How long does it take to add an Itanium-based partition in an HP 9000 customers?

The effort required to add an Itanium-based partition to an HP 9000 Superdome is slightly more than what is required to add a new PA-RISC-based partition. In both cases you have to create a new hard partition in the Superdome, plug in cell boards for the new processors and load the operating system. There are no hardware changes required to support mixing of processor types. The only known difference at this time is that a customer would need to upgrade the firmware to support the Itanium architecture. The process is currently being tested by R&D. This document will be updated as we learn more through testing.

6) Will mixing impact the overall performance of a Superdome (i.e. would an Itanium-based partition have the same performance in a mixed Superdome as in a Superdome only populated with Itanium 2 processors)?

No. For example, suppose you have a hard partition with 16 Intel Itanium 2 9M processors. This partition would have the same performance in a system with a mix of PA-RISC and Itanium 2-based hard partitions as a server where all of the other partitions are Itanium 2-based. This is assuming that besides the type of processors, all of the other configuration options are the same (memory, cell board locations, number of partitions, etc).

7) Can I add PA-RISC processors to an Itanium-based Integrity Superdome?

Yes. HP offers the ability to enable Itanium-based systems that shipped from the factory to add PA-RISC partitions later on in the field. This serves as a safety net/insurance policy. If the customer determines after the fact that a specific application is not ready for the Itanium technology, they can simply add a PA-RISC hard partition to that Integrity Superdome and continue the execution of the application while it is certified.

8) Why can't PA-8700+ processors be mixed with Itanium 2 9M processors?

For years, HP has had a high level of investment protection with the HP 9000 Superdome. Customers have been provided with the maximum investment protection level by keeping their investment in PA8600 and PA8700 processors while adding the higher speed PA8700+. In addition, each processor type runs at its rated speed so there is no downgrading of the higher speed processors (some competitors are erroneously saying Superdome has to downgrade the higher speed processors). For example, the PA8700 runs at a full 750 MHz while the PA8600 runs at 550 MHz-there is no forcing of the PA8700 down to 550 MHz just to obtain compatibility. This is possible because the processor speeds are independent from the bus speeds.

The Intel Itanium processor family is an advanced architecture featuring exceptional floating point and SSL performance. The Itanium 2 processors have the processing power that is consistent with a Superdome class high-end server. In addition, the Itanium processor accesses cache memory using a data block that is greater than twice the size of the PA8600, PA8700, and PA8700+. Thus, the Itanium processor family and subsequent PA-8800 and PA-8900 processors require a different chipset than the PA8600, PA8700, or PA8700+ processors. One of the key restrictions in mixing processors is that all cell boards in a given Superdome must have the same chipset. The PA-8700+ is supported by a legacy chipset that only supported PA-RISC processors. As a result, the PA-8700+ can only be mixed with PA-8700 and PA-8600 processors. In order to support Itanium 2 9M processors in their current HP 9000 Superdome, the customer would be required first to upgrade all of their PA-8700+ processors to PA-8800 or PA-8900 processors utilizing the sx1000 chipset. Once this is complete, the customer would then have the option of adding the Itanium 2 9M processor in a separate partition because it is also supported by the sx1000 chipset.

9) Why aren't Itanium 6M processors and mx2 dual core processor modules supported?

The original plan was to enable PA RISC systems that shipped from the factory to add Itanium based partitions later on. The plan was not to allow PA RISC based partitions to be added to systems that shipped from the factory as Itanium based servers with Itanium 6M processors and/or mx2 dual core processor modules. This is the only case where we encounter a problem with no support for Itanium 6M processors and mx2 dual core processor modules. If a customer has already made the decision to go with Integrity Superdomes, it is very unlikely that they will take a back step to PA RISC based partitions. Conversely, if a customer wants to upgrade a PA RISC based partition to be Itanium based, they are much more likely to use the Itanium 9M processor than the Itanium 6M processors or mx2 dual core processor modules because of the added performance and larger cache sizes.

Finally, this feature requires a significant amount of resources to test the different type of configurations supported in a Superdome. In order to provide this functionality in a timely basis to customers, we had to narrow the scope. Thus, the decision was made to not support Itanium 2 6M processors and mx2 dual core processors in a mixed processor type of system.

If a customer with Itanium 6M processors or mx2 dual core processor modules wants to add PA RISC modules, they would need to first upgrade the partitions with Itanium 6M processors or mx2 dual core processor modules to Itanium 9M processors and then they could add a PA RISC based partition to the Superdome.

10) Which versions of the HP-UX 11i operating system will be supported?

Currently HP supports HP UX 11.11 (HP UX 11i v1) for the PA RISC architecture as well as 11.23 (HP UX 11i v2) for Itanium processors and PA RISC processors in a mixed environment. Based on HP's testing, using HP UX 11.11 (HP UX 11i v1) in a mixed configuration requires a PA RISC Firmware update.

11) Does a customer have to power down when they add an Itanium-based partition to a PA-RISC-based Superdome?

It depends. If the existing PA-RISC based partitions are running HP-UX 11i v2 and PDC 22.1 (released in December 2004) then an Itanium-based partition may be added while the PA-RISC partitions are active. If the customer is running WLM it must be patched for proper operation in a mixed environment. We are currently checking with the WLM team to see what impact this would have on the PA-RISC partitions.

HP's shipping firmware for PA RISC processors does not fully support mixing if the PA RISC partitions are running HP UX 11i v1. In this case, downtime for all PA RISC based partitions would be required to update to the new PDC. The partitions could all be updated independently if desired. The above comment regarding WLM also applies.

12) What are the minimum firmware requirements for mixing various operating environments?

The matrix below describes the minimum firmware requirements:

Any of the above operating environments may be used on a mixed Superdome. In the process of testing all of the above combinations some issues and restrictions were discovered with WLM, gWLM and the GUI version of partition manager on HP-UX 11i v1. Firmware, operating system or application updates can resolve these issues. However, such updates may not always be possible or practical.

The following mixing scenarios serve to illustrate the issues that were found during testing and possible ways to work around or resolve them. For simplicity, the first three scenarios assume that all the PA partitions in the Superdome are running the same version of HP-UX. The fourth scenario explains the more general case where the PA partitions are running different versions of HP-UX.

Scenario 1: PA-8800 Partitions running HP-UX 11i v1 HWE 0312 or 0406 mixed with Itanium 2 1.6 GHz
Known issue with the GUI version of Parmgr:
Both of these HWEs shipped with Parmgr V1. This version of Parmgr and the stack that sits under it are not capable of managing Integrity partitions. Parmgr generates error messages when trying to access the Integrity cells and display information about them.

Alternatives to running Parmgr GUI on the PA partitions:

• Integrity partitions (and PA partitions) may be managed from the SMS
• Integrity partitions (and PA partitions) may be managed by parcmds from any partition
• Integrity partitions (and PA partitions) may be managed by the GUI version of Parmgr on any
• Integrity partition
  

The minimum firmware listed in the table above is sufficient for running this configuration.

Possible Upgrades:
If it is important to be able to use the parmgr GUI on the PA HP UX 11i v1 you can upgrade HP UX to HWE 0412 and follow the process in Scenario 2. If a customer upgrades to any 11i v1 HWE beyond HWE 0412 (HWE 0509 and later) then the proper nPar provider is already included in the HWE and the firmware upgrades in Scenario 2 are sufficient to get full functionality.

Known issue with the GUI version of Parmgr:
HP-UX 11i v1 HWE 0412 introduced Parmgr V2. This version of Parmgr will exhibit the same issues as Scenario 1 with the minimum required firmware from the table. However, upgrades to firmware and the nPar provider will make this version of Parmgr fully functional and capable of managing Integrity partitions. See the upgrade section below for details.

Alternatives to running Parmgr GUI on the PA partitions:
These are essentially the same as Scenario 1.

• Integrity partitions (and PA partitions) may be managed from the SMS
• Integrity partitions (and PA partitions) may be managed by parcmds from any partition
• Integrity partitions (and PA partitions) may be managed by the GUI version of Parmgr on any
• Integrity partition
  

The minimum firmware listed in the table above is sufficient for running this configuration.

Possible upgrades:
If it is important to be able to use the parmgr GUI on the PA partitions to manage the Integrity partitions the following updates must be made to the system:

PDC must be at revision 22.3 or higher in the 11.i v1 partition. This version of PDC contains a single fix on top of PDC 22.1 that compensates for the byte reversal in the cell info structure between PA and Integrity (this is due to the different "endianness" of the processors). PDC 22.3 will be released as part of SMS rel_6.0 in September 2005.

Integrity firmware must be upgraded to the version that supports vPars. This version of Integrity firmware contains a fix that populates I/O slot information in cell info structures used by the PA partition management stack. Currently shipping Integrity firmware does not populate this information and causes the PA management stack to report errors for Integrity cells. This version of Integrity firmware will be released as part of SMS rel_6.0 in September 2005.

The nPartition provider ("nPar" bundle) must be updated to version B.11.11.01.04 or above. This version will first be released on HP UX 11.i v1 HWE 0509. The version of nPar provider that shipped with HWE 0412 did not properly handle the single core Madison 9M processors.

Scenario 3: PA-8800 partition or PA-8900 partition running 11.i v2 (HWE 0409 or 0505) mixed with Itanium 1.6 GHz

This is the simplest scenario. The minimum firmware listed in the table is sufficient and all the partition management tools just work. The PA partition can manage other PA partitions and the Integrity partition and vice versa. Enjoy.

Scenario 4: PA-8800 or PA-8900 partitions running a mixture of the above scenarios mixed with Itanium 1.6 GHz

The previous scenarios apply to the individual partition pairs. For instance, say you have a Superdome with a PA8800 11.i v1 HWE0406 partition, a PA8900 11.i v1 HWE0412 partition a PA8800 11.i v2 partition and an Integrity partition. As described in Scenario 1 the PA8800 11.i v1 HWE0406 partition will not be able to recognize the Integrity cells. Manage the Integrity partition from the SMS, the PA8800 11.i v2 partition or using parcmds. As described in Scenario 2, the PA8900 11.i v1 HWE0412 partition cannot manage the Integrity partition with out the firmware and nPar provider upgrades outlined above. Use the SMS, the PA 11.i v2 partition or parcmds to manage the Integrity partition.

Global Workload Manager (gWLM)
gWLM 1.1.1 was first released with HP UX 11.i v2 HWE0505. It has the same issue with "uname -i" as WLM. This only affects gWLM iCAP SRDs. VPAR, PSET and FSS SRDs work correctly in mixed environments. The gWLM team plans to remedy this issue in the first maintenance release of gWLM. Contact gwlmfeedback@rsn.hp.com for a workaround if you have a gWLM 1.1.1 customer who needs to deploy an iCAP SRD on a mixed complex before the first maintenance release is available.

NOTE: Online addition/replacement for cell boards is not currently supported and will be available in a future HP UX release. Online addition/replacement of individual processors and memory DIMMs will never be supported.)

Superdome high availability offering is as follows:

• Processor: The features below nearly eliminate the down time associated with processor cache errors (which are the majority of processor errors).
  
  • Dynamic processor resilience w/ Instant Capacity enhancement.
    
  • Processor cache ECC protection and automatic de allocation
    
  • Processor bus parity protection
    
  • Redundant DC conversion
    
• Memory: The memory subsystem design is such that a single SDRAM chip does not contribute more than 1 bit to each ECC word. Therefore, the only way to get a multiple-bit memory error from SDRAMs is if more than one SDRAM failed at the same time (rare event). The system is also resilient to any cosmic ray or alpha particle strike because these failure modes can only affect multiple bits in a single SDRAM. If a location in memory is "bad", the physical page is de-allocated dynamically and is replaced with a new page without any OS or application interruption. In addition, a combination of hardware and software scrubbing is used for memory. The software scrubber reads/writes all memory locations periodically. However, it does not have access to "locked-down" pages. Therefore, a hardware memory scrubber is provided for full coverage. Finally data is protected by providing address/control parity protection.
  • Memory DRAM fault tolerance (i.e., recovery of a single SDRAM failure)
  • DIMM address/control parity protection
  • Dynamic memory resilience (i.e., page de-allocation of bad memory pages during operation)
  • Hardware and software memory scrubbing
  • Redundant DC conversion
  • Cell COD
• I/O: Partitions configured with dual path I/O can be configured to have no shared components between them, thus preventing I/O cards from creating faults on other I/O paths. I/O cards in hardware partitions (nPars) are fully isolated from I/O cards in other hard partitions. It is not possible for an I/O failure to propagate across hard partitions. It is possible to dynamically repair and add I/O cards to an existing running partition.
  • Full single-wire error detection and correction on I/O links
  • I/O cards fully isolated from each other
  • Hardware for the prevention of silent corruption of data going to I/O
  • On-line addition/replacement (OLAR) for individual I/O cards, some external peripherals, SUB/HUB
  • Parity protected I/O paths
  • Dual path I/O
• Crossbar and Cabinet Infrastructure:
  • Recovery of a single crossbar wire failure
  • Localization of crossbar failures to the partitions using the link
  • Automatic de-allocation of bad crossbar link upon boot
  • Redundant and hotswap DC converters for the crossbar backplane
  • ASIC full burn-in and "high quality" production process
  • Full "test to failure" and accelerated life testing on all critical assemblies
  • Strong emphasis on quality for multiple-nPartition single points of failure (SPOFs)
  • System resilience to Management Processor (MP)
  • Isolation of nPartition failure
  • Protection of nPartitions against spurious interrupts or memory corruption
  • Hot swap redundant fans (main and I/O) and power supplies (main and backplane power bricks)
  • Dual power source
  • Phone-Home capability
• "HA Cluster-In-A-Box" Configuration: The "HA Cluster-In-A-Box" allows for failover of users' applications between hardware partitions (nPars) on a single Superdome system. All providers of mission critical solutions agree that failover between clustered systems provides the safest availability-no single points of failures (SPOFs) and no ability to propagate failures between systems. However, HP supports the configuration of HA cluster software in a single system to allow the highest possible availability for those users that need the benefits of a non-clustered solution, such as scalability and manageability. Superdome with this configuration will provide the greatest single system availability configurable. Since no single-system solution in the industry provides protection against a SPOF, users that still need this kind of safety and HP's highest availability should use HA cluster software in a multiple system HA configuration. Multiple Serviceguard or Serviceguard Extension for RAC clusters can be configured within a single Superdome system (i.e., two 4-node clusters configured within a 32-processor Superdome system).

Any Superdome partition with PA-RISC processors that is protected by Serviceguard or Serviceguard Extension for RAC can be configured in a cluster with:

• Another Superdome with PA-RISC processors
• One or more standalone non Superdome systems with PA-RISC processors
• Another partition within the same single cabinet Superdome (refer to "HA Cluster-in-a-Box" above for specific requirements)

Separate partitions within the same Superdome system can be configured as part of different Serviceguard clusters.

Please note that when you add nodes or initially create a cluster, all nodes must be at the same version of the operating system and Serviceguard. This means that you may have to load an operating system update for hardware enablement of the newer hardware, even on older systems. Please refer to the "Compatibility and Feature Matrix" at http://docs.hp.com/hpux/onlinedocs/4076/SG%20SGeRAC%20EMS%20Support%20Matrix_10 3 03.htm

The following Geographically Dispersed Cluster solutions fully support cluster configurations using Superdome systems. The existing configuration requirements for non-Superdome systems also apply to configurations that include Superdome systems. An additional recommendation, when possible, is to configure the nodes of cluster in each datacenter within multiple cabinets to allow for local failover in the case of a single cabinet failure. Local failover is always preferred over a remote failover to the other datacenter. The importance of this recommendation increases as the geographic distance between datacenters increases.

• Extended Campus Clusters (using Serviceguard with Mirrordisk/UX)
• MetroCluster with Continuous Access XP
• MetroCluster with EMC SRDF
• ContinentalClusters

From an HA perspective, it is always better to have the nodes of an HA cluster spread across as many system cabinets (Superdome and non Superdome systems) as possible. This approach maximizes redundancy to further reduce the chance of a failure causing down time.

Supportability and management features on HP 9000 Superdome are covered in the next section.

Access to the MP is restricted by user accounts. Each user account is password protected and provides a specific level of access to the Superdome complex and service processor commands. Multiple users can independently interact with the service processor because each service processor login session is private. Up to 16 users can simultaneously log in to the service processor through its network (customer LAN) interface and they can independently manage nPartitions or view the server complex hardware states. Two additional service processor login sessions can be supported by the local and remote serial ports. These allow for serial port terminal access(through the local RS 232 port) and external modem access (through the remote RS 232 port).

In general, the service processor (MP) on Superdome servers is similar to the service processor on other HP servers, while providing enhanced features necessary for managing a multiple nPartition server. For example, the service processor manages the complex profile, which defines nPartition configurations as well as complex wide settings for the server. The service processor also controls power, reset, and TOC capabilities, displays and records system events (chassis codes), and can display detailed information about the various internal subsystems.

The primary features available through the service processor are:

• The Service Processor Command Menu: provides commands for system service, status, access configuration, and manufacturing tasks.
  
• Partition Consoles: Each nPartition in a server complex has its own console. Each nPartition's console provides access to Boot Console Handler (BCH) interface and the HP-UX console for the nPartition.
  
• Console Logs: Each nPartition has its own console log, which has a history of the nPartition console's output, including boot output, BCH activity, and any HP-UX console login activity.
  
• Chassis Logs Viewers (Live and Recorded Chassis Codes): Three types of chassis code log views are available: activity logs, error logs, and live chassis code logs.
  
• Virtual Front Panels: Each nPartition's Virtual Front Panel (VFP) displays real-time status of the nPartition boot status and activity, and details about all cells assigned to the nPartition. The VFP display automatically updates as cell and nPartition status changes.

The Support Management Station (SMS) runs the Superdome scan tools that enhance the diagnosis and testability of Superdome. The SMS and associated tools also provide for faster and easier upgrades and hardware replacement.

The purpose of the SMS is to provide Customer Engineers with an industry-leading set of support tools, and thereby enable faster troubleshooting and more precise problem root-cause analysis. It also enables remote support by factory experts who consult with and back up the HP Customer Engineer. The SMS complements the proactive role of HP's Instant Support Enterprise Edition (ISEE) that is offered to Mission Critical customers by focusing on reactive diagnosis for both mission-critical and non-mission-critical Superdome customers.

The user of the SMS is the HP Customer Engineer and HP Factory Support Engineer. The Superdome customer benefits from their use of the SMS by receiving faster return to normal operation of their Superdome server and improved accuracy of fault diagnosis, resulting in fewer callbacks. HP can offer better service through reduced installation time.

Functional Capabilities:
The SMS basic functional capabilities are:

• Remote access via customer LAN
• Modem access (PA-8800 and PA-8900 SMS only)
• Ability to be disconnected from the Superdome platform(s) and not disrupt their operation.
• Ability to connect a new Superdome platform to the SMS and be recognized by scan software.
• Support for up to sixteen Superdome systems
• Ability to support multiple, heterogeneous Superdome platforms (scan software capability).
• System scan and diagnostics
• Utility firmware updates
• Enhanced IPMI logging capabilities (Windows-based ProLiant SMS only)

The optimal configuration of console device(s) depends on a number of factors, including the customer's data center layout, console security needs, customer engineer access needs, and the degree with which an operator must interact with server or peripheral hardware and a partition (i.e. changing disks, tapes). This section provides a few guidelines. However the configuration that makes best sense should be designed as part of site preparation, after consulting with the customer's system administration staff and the field engineering staff.

Customer data centers exhibit a wide range of configurations in terms of the preferred physical location of the console device. (The term "console device" refers to the physical screen/keyboard/mouse that administrators and field engineers use to access and control the server.) The Superdome server enables many different configurations by its flexible configuration of access to the MP, and by its support for multiple geographically distributed console devices.

Three common data center styles are:

• The secure site where both the system and its console are physically secured in a small area.
  
• The "glass room" configuration where all the systems' consoles are clustered in a location physically near the machine room.
  
• The geographically dispersed site, where operators administer systems from consoles in remote offices.

These can each drive different solutions to the console access requirement.

The considerations listed below apply to the design of provision of console access to the server. These must be considered during site preparation.

• The Superdome server can be operated from a VT100 or an hpterm compatible terminal emulator. However some programs (including some of those used by field engineers) have a friendlier user interface when operated from an hpterm.
  
• LAN console device users connect to the MP (and thence to the console) using terminal emulators that establish telnet connections to the MP. The console device(s) can be anywhere on the network connected to either port of the MP.
  
• Telnet data is sent between the client console device and the MP "in the clear", i.e. unencrypted. This may be a concern for some customers, and may dictate special LAN configurations.
  
• If an HP-UX workstation is used as a console device, an hpterm window running telnet is the recommended way to connect to the MP. If a PC is used as a console device, Reflection1 configured for hpterm emulation and telnet connection is the recommended way to connect to the MP.
  
• The MP currently supports a maximum of 16 telnet connected users at any one time.
  
• It is desirable, and sometimes essential for rapid time to repair to provide a reliable way to get console access that is physically close to the server, so that someone working on the server hardware can get immediate access to the results of their actions. There are a few options to achieve this:
  
• Place a console device close to the server.
  
• Ask the field engineer to carry in a laptop, or to walk to the operations center.
  
• Use a system that is already in close proximity of the server such as the Instant Support Enterprise Edition (ISEE) or the System Management Station as a console device close to the system.
  
• The system administrator is likely to want to run X applications or a browser using the same client that they access the MP and partition consoles with. This is because the partition configuration tool, parmgr, has a graphical interface. The system administrator's console device(s) should have X window or browser capability, and should be connected to the system LAN of one or more partitions.

Customers ordering an SMS for the first time for a new PA 8700 Superdome should order the rx2600 SMS. The rx2600 SMS can also be used to manage PA8800/PA-8900 and Integrity Superdomes.

Customers using the earlier-released A180 SMS must replace it with the rx2600 if they expect to use it with new Superdome or Integrity servers. Customers may use an existing rp2470 or A500 SMS to manage any new PA 8700 Superdome.

One rx2600 SMS can support up to 16 Superdomes using a switch. Please note, however, that certain datacenters are so large that the networking structure will not permit the sharing of one SMS for the entire datacenter. The SMS is connected to each PA 8700 Superdome system on a private LAN. It is beneficial to have the SMS in close physical proximity to the Superdome(s) because the Customer Engineer (CE) requires SMS access to service the Superdome hardware. The physical connection from the Superdome is a private Ethernet connection and thus, the absolute maximum distance is determined by the Ethernet specification.

The UNIX rx2600 SMS bundle is comprised of:

• HP rx2600 1.0G 1.5MB processor server Solution
  
• Factory rack kit for rx2600
  
• 1GB DDR memory
  
• 36GB 15K HotPlug Ultra320 HDD
  
• HP-UX 11iv2 Foundation OE
  
• 1 x HP Tape Array 5300 with DVD-ROM and DAT 40
  
• HP ProCurve Switch 2124
  
• CAT 5e Cables

By default, the rx2600 SMS does not come with a display monitor or keyboard unless explicitly ordered to enable console access (the TFT5600 rackmounted display/mouse/keyboard is the recommended solution). See the ordering guide for details on the additional components that are required in order to use the rx2600 SMS as a console.

All SMS software is preloaded in the factory and delivered to the customer as a complete solution. The rx2600 SMS supports only HP UX 11i at this time. Current versions of the SMS software have not been qualified for 64 bit Windows. To ensure only optimal diagnostic solutions are used, an integrated Windows/Linux SMS/Console is not available for PA 8700 Superdomes. All SMS software is preloaded in the factory and delivered to the customer as a complete solution.

PA-8700 Superdome requires scan traffic to be isolated from console traffic, therefore two distinct networks are required for the SMS and/or console. The rx2600 SMS has two LAN connections on the integrated multifunction I/O that can support and connect to two LAN interfaces on the Superdome MP: the Private LAN and the Customer LAN. These two LAN connections allow SMS and console operations to be performed remotely.

The 10/100Base TX port on the rx2600 is required, and is connected to the Private LAN on the Superdome MP. This connection is solely used for the various diagnostics supported by the SMS. The 10/100/1000Base TX port on the rx2600 can optionally be connected to the Superdome MP's Customer LAN for console access to the MP (and the Superdome partitions) from the existing management network. More details on console use of the rx2600 is provided later in this chapter.

For use as an SMS only, the rx2600's 10/100Base-TX port is connected to the Private LAN port on the Superdome MP. This can be done with a direct-connect crossover cable, or by using an Ethernet switch. HP recommends the switched connect configuration for the rx2600 SMS in order for the SMS to be shared with other Superdomes, and remotely accessed.

The SMS can be accessed remotely from the Management LAN, or directly via RS 232 on an as needed basis. If the customer chooses to access the SMS from the Customer Management LAN, the SMS traffic is on a distinct and private network. Console traffic goes to Customer LAN port on MP. This diagram assumes that the Customer provides the console infrastructure. Note as well that the UNIX rx2600 SMS is supported for use on all current models of Superdome.

Providing the Ethernet switch is configured with the UNIX rx2600 SMS, additional Superdomes can be easily added into the existing infrastructure with minimal disruption and downtime. Each additional Superdome MP's Private LAN port should be connected to the Ethernet switch. Note this will share SMS scan functionality only, not console access.

PA-8700 Superdomes require scan and console to be on separate networks.

Existing PA-8700 Superdome customers may have a Legacy UNIX SMS (e.g. A500 or rp2470) that required a separate console device. Typically a Unix workstation or PC was configured in these environments. These customers may continue to use their existing console device to access any new PA-8700 Superdomes.

A Superdome console must meet the following requirements:

• HP Workstation running HP UX 11.0 or 11i v1
  
• PC running Windows NT, XP, 2000
  
• C1099A terminal server (limited functionality due to text mode only operation)
  
• 10Base-T Ethernet connection or an RS 232 port or both.
  
• X windows emulator for console access on the PC (i.e., Reflection for HP with NS/VT).

For new environments, the UNIX rx2600 SMS can also be used as a console for a PA8700 Superdome by creating a distinct network for the console traffic and including a display and keyboard. Separate networks can be created via two Ethernet hubs or one Ethernet switch. The Customer LAN port on the Superdome MP is then connected through the console hub/switch to the 10/100/1000Base TX port on the integrated I/O of the rx2600.

In order to use the UNIX rx2600 SMS as a console for PA8700 Superdome, the following components must be ordered:

• TFT5600 retractable keyboard/display/mouse
  
• CAT5e cables to create new console network

NOTE: HP-UX BASED SMS UNITS ARE NO LONGER OFFERED, as of October 1, 2007.

The UNIX rx2600 can also be used as an SMS for PA-8800 and PA-8900 Superdomes. The same hardware requirements as detailed in the previous section for the PA8700 SMS apply.

The Windows ProLiant ML350 SMS/Console solution is supported on sx1000-based (i.e. PA-8800/PA-8900 and Integrity) Superdomes only. It is not supported on PA-8700 Superdomes.

The Windows ProLiant SMS:

• Allows local access to SMS by CE.
  
• Provides integrated console access, providing hpterm emulation over telnet and web browser, connecting over LAN or serial to a Superdome system
  
• Provides remote access over a LAN or dialup connection:
  
• ftp server with capability to ftp the firmware files and logs
  
• dialup modem access support (i.e., PC Anywhere or VNC)
  
• Provides seamless integration with data center level management.
  
• Provides partition logon capability, providing hpterm emulation over telnet, X windows, and Windows Terminal Services capabilities.
  

Provides following diagnostics tools:

• Runs HP's proven highly effective JTAG scan diagnostic tools, which offer rapid fault resolution to the failing wire.
  
• Console log storage and viewing
  
• Event log storage and viewing
  
• Partition and memory adviser flash applications
  
• Supports updating platform and system firmware.
  
• Always on event and console logging for Superdome systems, which captures and stores very long event and console histories, and allows HP specialists to analyze the first occurrence of a problem.
  
• Allows more than one LAN connected response center engineer to look at SMS logs simultaneously.
  
• Can be disconnected from the Superdome systems and not disrupt their operation.
  
• Provides ability to connect a new Superdome system to the SMS and be recognized by scan software.
  
• Scans one Superdome system while other Superdome systems are connected (and not disrupt the operational systems).
  
• Supports multiple, heterogeneous Superdome platforms.

The Windows ProLiant SMS/Console is comprised of a ProLiant ML350 G3/G4 and a TFT5600 retractable display monitor/keyboard/mouse to enable console access. This solution also requires (and includes) a switch. This is because scan diagnostics will not work properly if more than one IP address exists on the ProLiant SMS/Console. An important difference between the UNIX rx2600 SMS and the Windows ProLiant SMS/Console is that the ProLiant SMS, by default, provides console functionality whereas the UNIX rx2600 SMS does not. The TFT5600 retractable display/keyboard which is an optional add-on for the UNIX-based rx2600 SMS, is included by default with the Windows ProLiant SMS.

Additionally, the Windows ProLiant SMS/Console includes an internal modem that is intended for connection to a phone line. This is for cases in which the Customer does not want the SMS to be on a public network, and HP Field Services needs to access the SMS (they would then access the SMS via the phone line and PCAnywhere.)

A customer may not substitute any PC running Windows Server 2000 SP4 for the ProLiant SMS/Console due to the specialized software applications that have been qualified on the hardware and OS. Utilizing any other device as the SMS will void the warranty on the Superdome system and degrade the ability to service the system.

The Windows ProLiant SMS bundle is comprised of:

• One HP ProLiant server ML350 G3/G4
  
• One Intel Xeon DP 3.06 GHz processor
  
• Two 256 MB
  
• 36 GB 10K U320 HDD
  
• One internal DVD
  
• One internal V.90 56K modem with phone cord
  
• Windows 2000 Server SP4
  
• Two 25 foot CAT5e cables
  
• One 4 foot CAT5e cable
  
• Ethernet switch and jumper cord
  
• Retractable display/keyboard/mouse
  
• Third party applications

All SMS software is preloaded in the factory and delivered to the customer as a complete solution.

The UNIX rx2600 SMS supports only HP UX 11i at this time. Current versions of the SMS software have not been qualified for 64 bit Windows.

The Windows ProLiant SMS/Console will run Windows 2000 SP4 as the default operating system. The ProLiant SMS/Console will follow the Windows OS roadmap and support later versions of this operating system as needed. The version of the scan tools used on the sx1000 Superdomes also does not require scan traffic to be isolated from console traffic.

One SMS can support up to 16 Superdomes using a switch (the Windows ProLiant SMS can support Integrity Superdomes only, and the UNIX rx2600 SMS can support both Integrity and HP 9000 Superdomes). Please note, however, that certain datacenters are so large that the networking structure will not permit the sharing of one SMS for the entire datacenter. It is beneficial to have the SMS in close physical proximity to the Superdome(s) because the Customer Engineer (CE) requires SMS access to service the Sup