Installation and Upgrade Guide
You can move from the EFI interface to MP and back again. Similarly, you can move from MP
to the operating system and back.
1.2.3 Virtual Connect (VC) on HP BladeSystem c-Class Enclosures
HP Virtual Connect (VC) is a set of interconnect modules and embedded software available for
HP BladeSystem c-Class enclosures. VC simplifies the setup and administration of server
connections. Where most server interconnect choices come with compromises such as too many
cables or too much to manage, VC reduces the number of network cables and simplifies
management while adding the unique ability to wire everything once, then add, replace or
recover servers in minutes instead of hours or days.
VC is enabled with a choice of Ethernet and Fibre Channel modules designed for the HP
BladeSystem. The built-in HP Virtual Connect manager defines a server connection profile for
each server bay—even before a server is installed. This profile establishes the Media Access
Control (MAC) addresses for all Network Interface Controllers (NICs), the World Wide Names
(WWNs) for all Host Bus Adapters (HBAs), and the SAN boot parameters. The profile then holds
them constant so that even if the server is changed, the configuration and connection profile stay
constant. When a new server takes its place, the same profile is assigned.
For more information about VC, select the Virtual Connect networking link at the following
website:
http://www.hp.com/go/bladesystem/virtualconnect
In addition, see the HP Virtual Connect for c-Class BladeSystem User's Guide, available at the
following location:
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00865618/c00865618.pdf
1.2.4 Cell-Based Server Terminology
A cell-based server—such as the HP rx7620, rx8720, or Superdome server—is a hardware complex
that can run one or more operating systems and that supports dividing hardware resources into
nPartitions. Thus, it enables you to configure a complex into one large system or into several
smaller systems.
All processors and memory are contained in cells, each of which can be assigned for exclusive
use by an nPartition. An nPartition defines a subset of the server hardware resources that is used
as an independent system environment. An nPartition has its own EFI system boot interface and
each nPartition boots and reboots independently. Each nPartition provides both hardware and
software isolation so that hardware or software faults in one nPartition do not affect other
nPartitions within the same server complex.
By using HP software-based nPartition management tools, you can configure nPartition definitions
for a server without physically modifying the server hardware configuration. The main
administration tools for nPartitions are the Partition Manager, which provides a graphical
interface, and the nPartition Commands, which provides a command-line interface. Versions of
these interfaces are provided on HP-UX, Linux®, and Microsoft® Windows® systems. The
nPartition Commands tool is also available on Linux systems. MP and EFI can also perform
nPartition administrative tasks. Slightly different tool sets and capabilities are available on
different server models. For more information, see your hardware documentation. In addition,
see the nPartition Administrator's Guide (previously titled HP System Partitions Guide: Administration
for nPartitions).
1.2.5 Getting Started: Main Steps After You Unpack Your Integrity Server
When you unpack your Integrity server, the main steps for getting OpenVMS up and running
are those listed in Table 1-2. As indicated in the third column, some of the instructions are
provided in this manual. However, for the most up-to-date information specific to your Integrity
1.2 Getting to Know Your Integrity Server 27