"Turn" enables network virtualization of AIX systems via the Vios

In our previous blog post, we have successfully installed an AIX system in a newly created lpar through file-backed device and vmlibrary, and then we discuss how to complete the network functionality of the newly installed AIX system with the help of the Vios. To make it easier for readers to read, let's simply identify where we are at the moment:

 

is an approximate schematic of the network support provided by the Vios to the newly installed AIX system, the Vios is responsible for providing a virtual Ethernet Apapter for AIX (see the connection between VESA and Veca in the figure), then the Vios crosses the sea through the POWERVM Hypervisor (that is, using the functionality provided by Hypervisor firmware) to use physical Ethernet adapter to communicate with the outside world.

After the last blog post, we can log in to the AIX system, but the network section is not yet open, which is the main part of this blog post to discuss. In the previous article, we used the following command when creating a new Lpar:

-bash-3.2$ mksyscfg-r lpar-i "name=nim,lpar_env=aixlinux,auto_start=1,boot_mode=norm,mem_mode=ded,min_mem=1024,
desired_mem=2048,max_mem=2048,proc_mode=shared,sharing_mode=uncap,uncap_weight=128,
min_procs=1,desired_procs=1,max_procs=2,min_proc_units=0.25,desired_proc_units=0.5,
Max_proc_units=2,\ "virtual_eth_adapters=4/0/3//0/0,5/0/4//0/0\" "

This command is very long and violent, but at the moment our focus is in the Blackbody Red section, which will provide two virtual Ethernet Adapter for the newly generated VM Lpar, because the new lpar will exist as its client form relative to the Vios, the Lpar. So the official name of Virtual Ethernet Adapter, the new Lpar (for a simple start-up, followed by the names Nim to represent the Lpar) is virtual Ethernet Client Adapter (Veca). Here's a brief explanation of the two weird parameters behind,4/0/3//0/0, it is the concrete manifestation of ' slot_number/is_ieee/port_vlan_id/additional_vlan_ids/is_trunk/is_required ', its core information has 3: Slot_number, PORT_VLAN_ID and Is_trunk.
Slot_number is the slot_number of this veca in the Nim virtual machine, and port_vlan_id is the most important, which represents the Veca in the current virtual machine and which virtual Ethernet Server in the Vios Adapter (VESA) is bound to each other, that is, the VESA and Veca identified in the line, is_trunk that the virtual Ethernet Adapter is used to connect the external network, in the client Partition, of course, is not necessary, because we only deal with VESA in the Vios, the latter need to connect external network (by using the physical Ethernet adapter through the SEA). We will explain the parameters here again when we do it in detail.

Now that we are logged into the newly installed AIX, we can see the following two Veca with the Lsdev command (corresponding to the previous creation of an lparvirtual_eth_adapters=4/0/3//0/0,5/0/4//0/0"parameter):


(in general, the upper OS will not know whether the underlying device is virtual or physical, but we can see from the command output above that Aix clearly knows that both ent0 and ent1 are virtual I/O devices, because all this set of things is exclusively provided by IBM, including AIX, So that's not surprising)

You can use the LSCFG command to see the details of these two virtual devices:


I use the mouse hightlight part is ent0 location code, where V2-C4-T1 information is at this time we are concerned about, C4 represents the device slot number=4, which is the parameter to create it4/0/3//0/0are in agreement.

Next, in order for the newly installed AIX system to have access to the external network, it is necessary to establish a sea (Shared Ethernet Adapter) in the Vios, so now we need to log in to the Vios environment to find the port_vlan_id=3 VESA, Then set up a sea device for it.

In the Vios, we can see some of the following things that are related to network devices:


On our current experimental IBM P server, there are two physical Ethernet adapter devices that correspond to ent0 and Ent1 respectively, both of which have cable connections to a switch, so ent0 and ent1 can be used as the backing of the sea device Device.
In the Ent4, Ent5,ent6 and ent7 are VESA on the Vios respectively, in order to configure AIX network, need to find the same VLAN ID as ent0 or ent1 in Aix, we take the example of Ent0 in Aix, It corresponds to the VESA VLAN id=3 in the Vios. So we need to find out which VLAN id=3 in ent[4,7] in the Vios. In the Vios environment, execute the lshwres command:


The Hightlight section is shown in the Vios, VLAN ID = 3 VESA slot num=5, and then with the lsmap-all-net command:
-bash-3.2$ lsmap-all-net
SVEA Physloc
------ --------------------------------------------
Ent4 U8204. E8a.068b7e4-v1-c3-t1

SEA NO SHARED ETHERNET ADAPTER FOUND

SVEA Physloc
------ --------------------------------------------
ENT5 U8204. E8a.068b7e4-v1-c4-t1

SEA NO SHARED ETHERNET ADAPTER FOUND

SVEA Physloc
------ --------------------------------------------
ent6 u8204.e8a.068b7e4-v1-c5-t1

SEA NO SHARED ETHERNET ADAPTER FOUND

SVEA Physloc
------ --------------------------------------------
Obviously, the red part indicates that the ENT6 corresponds to the slot num=5, so it's VLAN id=3. ENT6 is the VESA that corresponds to our new virtual machine Veca. With this information, you can create a sea for ENT6:

、

In the above command line, in order to facilitate network configuration work on other LPARs, we created an identical sea ent9 for ent[4,6], whose backing device is Ent1, which is a physical Ethernet adapter, We've all seen it before. (What else can we see from this command?) Can see a sea can support multiple client partition network function, this is why it is called shared Ethernet adapter reason, and a sea only a backing device, in our case is ent1, The latter is an actual Ethernet Adapter used to communicate information with the outside world)

After the above steps are complete, the network interface of the newly installed AIX system can be configured via Ifconfig en0 (at this point its status is defined), which is similar to the configuration under Linux. When you're done, ping my own host:
# ping 192.16.10.94
PING 192.16.10.94: (192.16.10.94): Data bytes
Bytes from 192.16.10.94:icmp_seq=0 ttl=63 time=9 ms
Bytes from 192.16.10.94:icmp_seq=1 ttl=63 time=0 ms
Bytes from 192.16.10.94:icmp_seq=2 ttl=63 time=0 ms
After the configuration is complete, the status of the ent0 has changed to available.

Once the network is through, it can be a little easier, and the next task is to configure the newly installed AIX as a NIM server. See the next blog post.

This article transferred from: http://blog.chinaunix.net/uid-23769728-id-3315871.html

"Turn" enables network virtualization of AIX systems via the Vios