Upgrade scenarios which do not require a reinstall of the operating system
Operating
system
HP-UX
OpenVMS
Windows
Server 2008
1
Note cautions in
Possible changes due to VC profile mapping on the upgraded server blade
Virtual Connect Manager supports assigning a VC server profile to each bladed server. Profiles
can include VC-assigned:
UUID
serial number
Ethernet port MAC addresses with network assignments
FC HBA connection WWNs with FC SAN assignments.
The VC-assigned MAC addresses, FC WWNs, UUID and serial number can come from blocks of
values supplied by VCM or from user-defined blocks of values. Alternatively, the factory-assigned
UUID, serial number, Ethernet port MAC addresses and FC HBA connection WWNs can be used.
The following information pertains to all of these options.
When performing an upgrade it is critical to understand how the server profile connection entries
will be mapped to ports on the upgrade server as this may impact the OS. What happens is
somewhat different for FC SAN assignments compared to Ethernet network assignments, so each
is described separately below.
The FC SAN connection entries in a profile should be thought of as sets of entries. If there are N
Virtual Connect FC Interconnect modules in an enclosure (where N is rounded up to an even
number) then there are N FC SAN connection entries per set. The first N entries are mapped to
the FC HBA ports on the Monarch blade, the second set of N entries are mapped to the FC HBA
ports on the first auxiliary blade, the next set of N entries to the next auxiliary blade, until all of
the FC connection entries have been mapped to ports or until there are no more FC HBA ports
available to map entries to. Below are a few examples of upgrading a BL860c i2 to a BL870c i2
in an enclosure with 4 Virtual Connect FC Interconnect modules where the BL860c i2 becomes the
Monarch blade in the upgrade server.
If the profile assigned to the BL860c i2 server had 4 or fewer FC SAN connection entries then
those entries are still mapped to the FC HBA ports on the original BL860c i2 blade (since it
is the Monarch in the new server). There will be no FC SAN connection entries mapped to
any ports on the auxiliary blade in the upgraded server.
If the profile assigned to the BL860c i2 server had more than 4 FC SAN connection entries
then the first 4 entries are still mapped to the FC HBA ports on the original BL860c i2 blade
(since it is the Monarch in the new server). The additional FC SAN connection entries (up to
82
Optional components
Virtual Connect
VC
no VC
X
X
X
X
X
X
X
X
"Possible changes due to VC profile mapping on the upgraded server blade" (page 82)
HP Virtual Machines
HPVM
no HPVM
X
X
X
X
N/A
N/A
N/A
N/A
OS reinstall required?
1
NO
NO
1
NO
NO
1
NO
NO
1
NO
NO
Need help?
Do you have a question about the Integrity BL860c i2 and is the answer not in the manual?
Questions and answers