"Go" HMC and Vios provide storage and network virtualization support for new LPARs

The operating environment of the previous few posts is under IVM, IVM can be regarded as part of the Vios, or an extension to the Vios function, a IVM can only manage 1 physical servers, while the HMC is a one-to-many. In the case where the HMC is managing the physical server, the IVM feature in the Vios will be masked and its corresponding function will be taken over by the HMC.

The following is a command to create a new lpar in the HMC environment:
[Email protected]:~> mksyscfg-r lpar-m server-8231-e2b-sn104a4ar-i "Name=dennis,lpar_env=aixlinux,auto_start=1, boot_mode=norm,mem_mode=ded,min_mem=2048,
desired_mem=4096,max_mem=4096,proc_mode=shared,sharing_mode=uncap,uncap_weight=156,
min_procs=1,desired_procs=2,max_procs=2,min_proc_units=0.2,desired_proc_units=0.4,max_proc_units=1.2,
VIRTUAL_ETH_ADAPTERS=10/0/256//0/1,VIRTUAL_SCSI_ADAPTERS=20/CLIENT/1//17/1, max_virtual_slots=100 "

Creating a virtual machine (LPAR, logical partition) the most critical and relatively troublesome parameter is to provide the LPAR with a network and storage device, which is the two red and blue portions of the above The specific meaning of these two parameters is to create an lpar's blog post with IVM in front of it-enabling network virtualization of AIX systems through the Vios and installing AIX full-length on client partition via Vmlibrary.

It is more concerned about how to construct the specific values of this parameter, first of all the network part, the parameters that need to be determined are virtual Ethernet Client Adapter (VECA) slot num in the LPAR currently being created, this degree of freedom is very high, Basically you can arbitrarily specify a number not exceeding the value specified in Max_virtual_slots (in the case we specify the Max_virtual_slots parameter), this example Veca slot number=10, the more troublesome is Port_vlan_ ID section, because this value will directly determine whether the network device is available in the newly created lpar, so it needs to be assigned to a physically available network device in the Vios, so we need to be in the HMC environment (not IVM, because in the case where the HMC exists, The HMC will block out the IVM command in the Vios, which means that the command can be executed in the Vios environment, but does nothing, without any output, to view information about its network device. Perform:



Displays information about virtual Ethernet Server Adapter (VESA) in the current Vios: it has two VESA, Slots numbers are 30 and addl_vlan_ids=354,355,356, respectively, and addl_vlan_ids=330,331,332,333, if viewed through the lsmap-all-net command in the Vios, The two VESA's have a corresponding sea and backing device, so they can be used by the client partition.

For information about the virtual SCSI Server adapter device in the Vios, you can use the following command under the HMC to view:


where slot number = 17 is the Vssa that we created for this lpar, we just created a virtual SCSI Client Adapter . After this command executes, unlike the Mksyscfg command in IVM, the HMC does not automatically create a corresponding virtual SCSI Server adapter (such as vhost0) in the Vios, which requires the following command to be given to the Vios Partition Create a virtual SCSI Server adapter vm:
[email protected]:~> chhwres-r Virtualio--rsubtype scsi-m Server-8231-e2b-sn104a4ar-o a--id 1-s 18-a "Adapter_type=server, remote_lpar_id=2, remote_slot_num=30"
Of course, if we do not want to specify information about Remote_lpar, then we can use a simplified version of the above command:
[email protected]:~> chhwres-r Virtualio--rsubtype scsi-m server-8231-e2b-sn104a4ar-o a--id 1-s 18-a "Adapte R_type=server "
The above command simply says to create a slot num=18 virtual SCSI Server Adapter in the Vios, and does not specify the ability to use
Information about the client Partition of the Vssa, which means that the Vssa can be bound to any Partition slot of any Partition, but for client adapter, you must specify Remote_lpar _id and remote_slot_num two parameters. Of course, if the corresponding slot num=18 in the Vios already has a vssa, the command will prompt the following error:
Hscl294c Dynamic Add of virtual I/O resources failed:
A Virtual I/O device already exists at slot 18.

If the corresponding slot num=18 in the Vios does not yet have a vssa present, the above command will create a vssa in the Vios, and if you want to see the virtual device Vhost N for that hwres in the Vios, you need to log in to the Vios system. Run the Cfgdev command vios to automatically create a VHOSTX device, otherwise you can only view the number of Vssa in the current vios by Lshwres command:
[Email protected]:~> lshwres-r virtualio--rsubtype scsi-m server-8231-e2b-sn104a4ar--level lpar--filter "lpar_ids= 1 "
...
Lpar_name=vios,lpar_id=1,slot_num=77, State=1,is_required=0,adapter_type=server,
Remote_lpar_id=any,remote_lpar_name=,remote_slot_num=any
...

Once the VHOSTX virtual appliance has been generated through Cfgdev in the Vios, VTD and backing devices can be created as a result of installing the AIX full record on the client partition, as in the vmlibrary.

If weconsider the opposite process of the above operation, in the Vios environment, you must first remove the VTD B on vhostx by using a. RMVDEV-VTD vtdname. Remove RMLV device via Logical volume backing (This step requires caution, deleting a lv, meaning "all Data contained on logical volume XXX would be destroyed ") c. Rmdev-dev VHOSTX
So far these steps are just to delete vhostx this virtual device, but in hwres this layer, for lshwres still can see the vhostx-year-old corresponding hwres still exist, at this time must use Chhwres command to completely remove this hwres.

After you start the Lpar and install AIX, you can log in using SSH, for example, after configuring the network. In this AIX environment, we perform:
bash-3.2# prtconf
The following output will be available:
。。。
System model:ibm,8231-e2b
Machine Serial Number:104a4ar
Processor Type:powerpc_power7
Processor Implementation Mode:power 7
Processor Version:pv_7_compat
Number of Processors:2
Processor Clock speed:3000 MHz
CPU Type:64-bit
Kernel Type:64-bit
LPAR Info:2 Dennis
Memory size:4096 MB
Good Memory size:4096 MB
Platform Firmware level:al730_066
Firmware version:ibm,al730_066
Console login:enable
Auto Restart:true
Full Core:false
。。。
Installed RESOURCE LIST

The following resources is installed on the machine.
+/-= Added or deleted from Resource List.
* = Diagnostic support not available.

Model ARCHITECTURE:CHRP
Model implementation:multiple Processor, PCI bus

+ SYS0 System Object
+ sysplanar0 System Planar
* Vio0 Virtual I/O Bus
* Vscsi0 U8231. E2b.104a4ar-v2-c20-t1 Virtual SCSI Client Adapter
* Hdisk1 U8231. e2b.104a4ar-v2-c20-t1-l8300000000000000 Virtual SCSI Disk Drive
* Hdisk0 U8231. e2b.104a4ar-v2-c20-t1-l8200000000000000 Virtual SCSI Disk Drive
* Cd0 U8231. e2b.104a4ar-v2-c20-t1-l8100000000000000 Virtual SCSI Optical Served by VIO Server
* Ent0 U8231. E2b.104a4ar-v2-c10-t1 Virtual I/O Ethernet Adapter (L-lan)
* VSA0 U8231. E2B.104A4AR-V2-C0 LPAR Virtual Serial Adapter
* Vty0 U8231. E2b.104a4ar-v2-c0-l0 Asynchronous Terminal
+ l2cache0 L2 Cache
+ mem0 Memory
+ proc0 Processor
+ proc4 Processor

The Netizen can compare with the command line parameter that originally created it, see the correspondence between them.

"Go" HMC and Vios provide storage and network virtualization support for new LPARs