Realize new workload migration and consolidation possibilities

10
Generate commands for creating the new vPars and
infrastructure
In order to create a vPar from table 2, use the
vparcreate
command for each row, with command line parameters based
on the table cells as follows:
• vPar Name:
– p {name}
• Cores:
– a core::{number}
• RAM:
– a mem::{megabytes}
• FC ports: if you have configured your VSP to work with GUIDMGR, then for each of the required virtual HBAs, add
– a hba:avio_stor::npiv:/dev/fcdN
where
/dev/fcdN
is the device file of the physical Fibre Channel port on the VSP that you wish to use with the vPar.
If you have decided to manage the virtual World Wide Names (WWNs) manually, then use parameters in the format
– a hba:avio:,,{Port WWN},{Node WWN}:npiv:/dev/fcdN
For more information, see HP-UX vPars and Integrity VM NPIV at hp.com/go/vPars.
• Other non-NPIV storage:
For virtual disks and dvds backed through storage mounted to the VSP, the command format is:
– a [disk|dvd]:avio_stor::[disk|lv|file]:
where
[disk|dvd]
refers to how the vPar will see the storage and
[disk|lv|file]
refers to how the VSP views
the physical backing store.
• Internal-only virtual LAN and virtual LAN “vswitches”:
– a network:avio_lan::vswitch:{vswitch_name}
Where
{vswitch_name}
is the name of a virtual switch that was created during the VSP creation phase (see “Install
the VSP (server or nPartition) with HP-UX vPars and Integrity VM 6.1”). The only difference between an internal-only
LAN and standard vswitch is whether the vswitch is backed by a LAN port. Each vswitch may be connected to one
physical LAN, and each physical LAN may be connected either to a vswitch or be configured for DIO.
• DIO LANs: Assuming that you assigned one or more network devices to the DIO resource pool in the “Install the VSP
(server or nPartition) with HP-UX vPars and Integrity VM 6.1” section, the command parameters would be:
– a lan:dio::hwpath:{hardware path}
Examples
The following example shows the conversion of a resource planning table entry for a typical vPar with multiple LANs, a
virtual DVD, and one virtual HBA:
Table 3. Example vPar with multiple LANs
vPar
name
Cores RAM FC ports
(NPIV)
Other non-NPIV storage
(file, disk or lvol backed)
Internal-only
virtual LAN
Virtual
LANs
vswitches
# DIO
LANs
(physical)
vPar view Backing
store
my_vPar 2 4 GB 1 DVD install.iso recovLAN dbLAN
mgmtLAN
0