HP nPartitions (nPars) manual Upgrading the original server, Existing server blade check

processor of each blade (by enclosure bay number) can be chosen individually and the information displayed will include the information needed for comparison.

For more information, see “Processor and heatsink module” (page 39), and “ CPU and heatsink module” (page 111).

DIMM matching and loading rules

The rules regarding DIMM load order change, especially when upgrading from a BL860c i4 to either a BL870c i4 or BL890c i4. For more information on DIMM loading rules, see “DIMM quad load order rules” (page 47).

NOTE: Memory loading rules apply across all blades in a sever depending on the server type (BL870c i4 or BL890c i4) regardless of nPartition configuration.

There are also minimum system memory and performance guidelines must be followed. See the Memory subsystem information for HP Integrity Server Blades (BL860c i4, BL870c i4, and BL890c i4) Technical White Paper (http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA1-1126ENW.pdf).

Optional mezzanine cards

The HP NC532m Dual Port 10GbE BL-c Adapter is restricted to two cards per blade on a BL890c i4. There are no additional rules regarding the number of cards installed or the order of their installation across the blades in an upgraded server blade. Ensure all mezzanine cards follow the mezzanine port to interconnect module mapping detailed in “Installing interconnect modules” (page 17).

Upgrading the original server

Existing server blade check

IMPORTANT: Do not remove Blade Links or other components at this time.

1.f not already booted, verify that the designated Monarch Server (in each partition) is able to boot its OS. For information on launching the OS from the UEFI shell, refer to “UEFI Front Page” (page 26).

2.If the Monarch Server is an HP Virtual Machines (VM) host with active guests or a Virtual Services Platform (VSP) with active Virtual Partitions (vPars), then either stop those guests or vPars now or migrate them to a temporary host server. Refer to the HP Integrity VM or vPar Administrator Guides regarding migration.

3.Backup any important OS data on the Monarch Server and any existing servers, as needed.

4.If the Monarch Server employs Virtual Connect and a partition will grow in size in the upgrade, then you may wish to use the Portable Image tool to assist with the upgrade. Refer to “Preserving VC-assigned MAC addresses in HP-UX by enabling Portable Image” (page 75) and if you choose to use PI, then execute the steps under “Pre-Upgrade Procedure for PI” in that section now.

5.Boot each partition of the Monarch Server, and every other existing blade server to be combined in the upgrade, to the UEFI shell and make sure no problems are seen.

6.Any existing secondary nPartition (that is, any partition which does not include the server Monarch blade, those designated as 'B', 'C', or 'D' partitions) which will be carried over into the upgraded server as secondary nPartitions, must have their UEFI variables backed up now so they can be restored later. See the nPar Administrator Users Guide for BL870c i4 & BL890c i4 for instructions on how to do this. The primary nPartition in the Monarch Server (the partition which includes the server Monarch blade, the one designated as 'A') will not lose UEFI variable data.

7.Shutdown each existing blade server which will be combined into the upgraded server. See “Powering off the server blade” (page 21)

Installing internal components 61