After restarting the lpar as a Shared memory partition, I used lparstat and vmstat to view the lpars' Shared memory Settings.
作为共享内存分区重新启动lpar之后，我使用lparstat和vmstat查看lpar的共享内存设置。
HMC view of LPARs on the 9119-fha.
9119-fha上lpar的hmc视图。
The LPARs' shared memory profile settings
LPAR 的共享内存配置设置
The LPARs are assigned "logical" shared memory.
给LPAR分配 “逻辑”共享内存。
My environment consists of close to 100 AIX LPARs.
我的环境由接近 100 个AIXLPAR 组成。
Log in to the LPARs and search for runaway processes.
登录LPAR并搜索失控的进程。
Multiple LPARs on a server connected to the IB fabric.
一个连接到IB构造的服务器上的多个lpar。
None of my AIX LPARs had any dedicated physical hardware.
我的AIXLPAR都没有任何专用的物理硬件。
But how do I tell if the LPARs really need all that memory?
但是，如何查明LPAR是否确实需要所有内存呢？
We could not simply power up the old p5 and start the LPARs.
我们无法简单地启动老的p5并启动LPAR。
In this environment, we would need to create just five LPARs.
在这种情况下，我们将只需要创建五个LPAR。
These were the rootvg disks that belonged to my client LPARs.
这些是属于客户机LPAR的rootvg磁盘。
Configured on the blade were a VIOS (IVM) and two AIX 6.1 LPARs.
这台刀片服务器上配置了一个VIOS (ivm)和两个AIX 6.1LPAR。
However, LPARs can be used to complement other availability strategies.
然而，LPAR可以用于弥补其他可用性策略。
These LPARs span the range of environments and application types at UPMC.
这些LPAR涵盖UPMC 中的各种环境和应用程序类型。
The pSeries test machine used was a p570+ configured into multiple LPARs.
我们使用的pSeries测试机器是一台配置为多个 LPAR 的p570+。
Production, test, and development LPARs are all mixed on all Power servers.
生产、测试和开发LPAR在所有Power服务器上混合部署。
Modify the LPARs properties to map the new virtual adapters to LPAR adapters.
通过修改lpar属性把新的虚拟适配器分配给lpar适配器。
Refer to the output below, from one of the LPARs before and after the upgrade.
下面是升级之前和之后一个LPAR的输出。
Likewise, the VIOS used to serve DS8300 storage to client LPARs, will also remain.
同样地，用来向客户机LPAR提供DS8300存储的VIOS也将继续存在。
Using the previous steps in this article, your new LPARs load the Linux installer.
新的LPAR使用本文前面提到的步骤装载Linux安装程序。
If you set the image to read-only, you can present it to several LPARs simultaneously.
如果把映像设置为只读的，就可以同时向多个LPAR提供它。
The next step was to migrate my existing dedicated-memory LPARs to shared-memory LPARs.
下一步是把现有的专有内存LPAR迁移到共享内存 LPAR。
The VIO client LPARs will go to the other VIO server for their disk and network resources.
VIO客户机lpar会通过另一个VIO服务器访问磁盘和网络资源。
The working set for both LPARs came to roughly 9.3GB, which would fit nicely into the pool.
这两个LPAR 的工作集大约为 9.3GB，这与池的大小相适应。
Only a little over 160mb of data exists for around 100 LPARs with a sample rate of one hour.
对于大约100个LPAR和一小时的取样速率，数据只有160MB多一点儿。
In this step, you configure the DHCP server to provide network boot information to new LPARs.
在这一步骤中，需要配置DHCP服务器以为新的LPAR提供网络引导信息。
The install data for each of the LPARs in the cell is included in the same consistency group.
计算单元中的每个LPAR的安装数据包括在相同的一致性分组中。
On the day of the upgrade, I shut down all the LPARs and handed the system over to the IBM CE.
在升级那一天，我关闭所有LPAR，把系统交给IBMCE。
You perform some workload analysis and find that not all of the LPARs are used at the same time.
执行一些工作负载分析，发现不会同时使用所有LPAR。
应用推荐