Realize new workload migration and consolidation possibilities

11
Command:
vparcreate –p my_vPar –a core::2 –a mem::4096 \
–a dvd: avio_stor::file:/images/install.iso
vparmodify –p my_vPar –a hba:avio_stor::npiv:/dev/fcd1
vparmodify –p my_vPar –a network:avio_lan::vswitch:recovLAN
vparmodify –p my_vPar –a network:avio_lan::vswitch:dbLAN \
–a network:avio_lan::vswitch:mgmtLAN
The next example covers a vPar with no sharable LANs (other than an internal-only LAN), but with one LAN to be
assigned directly to it:
Table 4. Example vPar with only an internal LAN
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
vp2 2 4 GB 1 - - recovLAN 0 1
Command:
vparcreate –p vp2 –a core::2 –a mem::4096
vparmodify –p vp2 –a hba:avio_stor::npiv:/dev/fcd1
vparmodify –p vp2 –a network:avio_lan::vswitch:recovLAN
vparmodify –p vp2 –a lan:dio::hwpath:0/0/0/4/0/0/0
Verifying the new vPar and VSP configurations
Prior to attempting to provision the various virtual partitions, confirm that the vPars have the expected resources. This
can be done with the
vparstatus
,
vparnet
, and
vparhwmgmt
. Referring back to table 2, if the appropriate commands
were run to create these vPars, one would expect the command output to be:
Figure 1. Confirming vPar configurations
# vparstatus
[Virtual Partition]
Num Name RunState State
=== ========================== ============ =========
1 db1 DOWN Inactive
2 app1 DOWN Inactive
3 app2 DOWN Inactive
4 ignite DOWN Inactive
[Virtual Partition Resource Summary]
Virtual Partition CPU Num Num Total MB
Num Name Min/Max CPUs IO Memory
=== ========================== ======= ==== ==== =========
1 db1 1/127 3 6 6144
2 app1 1/127 2 5 4096
3 app2 1/127 2 6 4096
4 ignite 1/127 1 3 3072
# vparstatus –v
[Virtual Partition Details]
Number: 1
Name: db1
RunState: DOWN
State: Inactive
[CPU Details]
Min/Max: 1/127
System assigned [Count]: 3
[Memory Details]
Total Memory(MB): 6144
[OL* Details]