动态分区迁移(LPM)基础知识和故障诊断(共28页)

1、本文介绍如何配置动态分区迁移（LPM）并对其进行故障诊断。本文还简要解释了一些 LPM 基础概念、故障诊断问题、以及各种问题的简单(jindn)修复方法。简介(jin ji)Live Partition Mobility (LPM) 在 Power6 上引入，旨在在迁移到其他主机时在 VIOS 和固件升级过程中帮助避免(bmin)停机。LPM 也减少了创建新 LPAR 和设置时所需的工作量，这对于应用程序而言是必要的。大部分客户将 LPM 活动视为一种日常工作，但很多客户都不了解确切流程或正在发生的事情。本文将展示克服或修复 LPM 问题的步骤。图 1. AIX I/O 堆栈LPM 关键点关于

2、 LPM 务必记住：LPM 将正在运行的分区从一个物理服务器迁移到另一个，同时维护完整的事务完整性并转移整个环境：处理器状态、内存、虚拟设备和已连接的用户。分区在关闭时也可以进行迁移（消极迁移），操作系统和应用程序必须驻留在共享存储器上。 HYPERLINK /developerworks/cn/aix/library/au-LPM_troubleshooting/index.html l ibm-pcon 回页首LPM 先决条件您必须在启用了 Advanced Power Virtualization Feature 的 POWER6 （或更高版本）上至少拥有两台机器：一个源和一个目标。操作

3、系统和应用程序必须驻留在一个共享外部存储器（Storage Area Network）上。除了这些硬件要求外，您还必须拥有：一个硬件(yn jin)管理控制台- HMC（可选）或 IVM。目标系统必须拥有足够(zgu)的资源，比如 CPU 和内存。LPAR 不应该(ynggi)拥有物理适配器。您的虚拟 I/O 服务器（virtual I/O server，VIOS）必须拥有一个 Shared Ethernet Adapter (SEA) 并被配置为桥接到移动分区使用的那个 Ethernet 网。它必须能够提供对移动分区使用的所有磁盘资源的虚拟访问能力（NPIV 或 vSCSI）。如果使用 vS

4、CSI，则虚拟目标设备必须是物理磁盘（而不是逻辑卷）。必须使用 AIX 5.3J 版或更高版本，VIOS 1.4 版或更高版本，HMC V7R310 或更高版本，固件必须是 efw3.1 或更高版本。 HYPERLINK /developerworks/cn/aix/library/au-LPM_troubleshooting/index.html l ibm-pcon 回页首LPM 过程中所发生的事图 2. 普通 LPM 图示下面的步骤描述了图 2 中的普通 LPM 图示：分区配置文件（此时处于活动状态）从源复制到目标 FSP。配置目标上的存储器。移动(ydng)程序服务分区（Mover S

5、ervice Partition，MSP）被激活。分区迁移(qiny)开始。大部分内存页面(y min)被移动。所有线程转为闲置状态。激活过程在目标上恢复。最后的内存页面被移动。清理存储器和网络流量。取消源上的存储器资源配置。从源 FSP（Flexible Service Processor）移除分区配置文件。 HYPERLINK /developerworks/cn/aix/library/au-LPM_troubleshooting/index.html l ibm-pcon 回页首如何进行 LPM进行 LPM 之前，需要验证源和目标两端的资源可用性。如果验证由于某种错误而失败，则需要修复

6、错误才能继续下一步。有时，验证过程可能会出现一些警告消息，不用管它们。使用 HMC GUI 进行 LPM图 3 展示如何使用 HMC GUI 来验证 LPAR。在System management - Servers - Trim屏幕中，选择 LPAR 名称：Operations - Mobility - Validate图 3. 验证 LPAR验证屏幕（如图 4 所示）显示(xinsh)，upt0052 LPAR 被验证，以便从trsim迁移(qiny)到dash，如果需要，必须指定(zhdng)目标 HMC。图 4. Validation 窗口图 5 显示 LPM 出现了一条警告消息，忽略

7、该消息，选择Close继续迁移。图 5. 验证通过(tnggu)并出现一般警告消息Partition Migration Validation屏幕（见图 6）显示信息被选中，以便设置(shzh)到另一个托管系统的分区迁移。选择Migrate以验证(ynzhng)信息。图 6. 验证通过后迁移准备就绪迁移结束(jish)后，如图 7 所示，选择Close。图 7. 迁移(qiny)进程使用(shyng)命令行选项的 HMC要验证(ynzhng)本地 HMC 中的 LPM，输入以下代码：migrlpar -o v -m source cec -t target cec -p lpar to mig

8、rate要验证远程(yunchng) HMC 中的 LPM，输入：migrlpar -o v -m source cec -t target cec -p lpar to migrate -ip target hmc -u remote user注意，作为远程用户，您可能愿意使用hscroot命令。使用以下迁移命令执行本地 HMC 中的 LPM：migrlpar -o m -m source cec -t target cec -p lpar to migrate使用以下迁移命令执行远程 HMC 中的 LPM：migrlpar -o m -m source cec -t target cec

9、-p lpar to migrate -ip target hmc -u remote user如果源和目标之间的配置问题导致 LPAR 发生 MPIO (Multipath IO) 失败，输入以下命令继续（如果适用的话）：migrlpar -o m -m wilma -t visa -p upt07 -redundantpgvios 0 -n upt07_noams_npiv -u hscroot -vlanbridge 2 -mpio 2 -w 60 -d 5 -v -isource_msp+name=wilmav2,dest_msp_name=visav2 -ip destiny4 HY

10、PERLINK /developerworks/cn/aix/library/au-LPM_troubleshooting/index.html l ibm-pcon 回页首故障诊断本节介绍可能遇到的各种错误及其更正方法。如果需要跨两个不同的 HMC 进行 LPM，在迁移时，需要在两个 HMC 之间设置适当的授权。如果没有设置适当的授权，将显示以下mkauthkey错误：hscrootdestiny4: migrlpar -o v -m trim -p UPT0052 -ip hmc-arizona -uhscroot -t arizona HSCL3653 The Secure Shell

11、(SSH) communication configuration between the sourceand target Hardware Management Consoles has not been set up properly for userhscroot. Please run the mkauthkeys command to set up the SSH communicationauthentication keys.要克服(kf)这个错误，输入：hscrootdestiny4: mkauthkeys -g -ip hmc-arizona -u hscrootEnter

12、 the password for user hscroot on the remote host hmc-arizona如果正在迁移一个 POWER7 Advanced Memory Expansion (AME) 分区(fn q)，那么对于任一 POWER6 机器，将显示以下错误：hscrootdestiny4: migrlpar -o v -m trim -p UPT0052 -ip hmc-liken -u hscroot -t wilma HSCLA318 The migration command issued to the destination HMC failed with

13、the following error: HSCLA335 The Hardware Management Console for the destination managed system does not support one or more capabilities required to perform this operation. The unsupported capability codes are as follows: AME_capabilityhscrootdestiny4:要更正这个错误，要么(yo me)迁移到 POWER7，要么移除这个 AME 然后再进行迁移

14、。如果您正在迁移一个 Active Memory Sharing (AMS) 分区(fn q)，但 AMS 设置不正确，或者目标上没有空闲的分页设备，将显示以下错误：hscroothmc-liken: migrlpar -o v -m wilma -t visa -ip destiny4 -u hscroot -pupt0060 -mpio 2 Errors:HSCLA304 A suitable shared memory pool for the mobile partition was not found on thedestination managed system. In orde

15、r to support the mobile partitions, thedestination managed system must have a shared memory pool that can accommodate thepartitions entitled and maximum memory values, as well ad its redundant pagingrequirements. If the destination managed system has a shared memory pool, inabilityto support the mob

16、ile shared memory partition can be due to lack of sufficient memoryin the pool, or lack of a paging space device in the pool that meets the mobilepartitions redundancy and size requirements. Details:HSCLA297 The DLPAR Resource Manager (DRM) capability bits )x) for mover servicepartition (MSP) visav2

17、 indicate that partition mobility functions are not supportedon the partition.HSCLA2FF An internal Hardware Management Console error has occurred. If this errorpersists, contact your service representative.要更正这个错误，执行(zhxng)下面一项操作，或者同时执行两项操作：由于这个问题与冗余 AMS 设置有关，因此目标 AMS 池应该拥有针对一个特定(tdng) AMS 池的冗余能力，这个

18、 AMS 池定义为 Shared Memory Pool，包含两个只用于高可用性 HMC 的 Paging VIOS 分区。用户可以为每个 Shared Memory Partition 选择主要和替代分页 VIOS。要了解 AMS 的相关细节，请参阅 “ HYPERLINK /developerworks/cn/aix/library/au-pwr6_ams/ t _blank 一位客户配置(pizh) Active Memory Sharing 的经历”（developerWorks，2009 年 8 月）了解(lioji)更多信息。目标 AMS 池中应该有足够的空间用于分页设备。如果试图

19、将 LPAR 从 Power7 迁移到 Power6 CPU，将得到以下错误：hscrootdestiny4: migrlpar -o v -m dash -t arizona -ip hmc-arizona -u hscroot-p upt0053 Errors:HSCLA224 The partition cannot be migrated because it has been designated to use a processor compatibility level that is not supported by the destination managed system

20、. Use the HMC to configure a level that is compatible with the destination managed system.上述错误的解决方案可是下列之一：迁移到 POWER7。将处理器模式更改为适当的模式（就像在目标托管系统中一样）。在 HMC GUI 中更改处理器模式的步骤如下：选择(xunz) LPAR 并取消其激活状态。转到Configuration-Manage Profiles。选择(xunz)需要激活的配置文件。转到Processors，将Processor compatibility mode:更改为(i wi)需要的设置

21、并使用相同的配置文件引导它。LPAR 应该在源和目标 MSPs 上拥有相同的共享 vSCSI 磁盘：hscrootdestiny4: migrlpar -o v -m dash -t arizona -ip hmc-arizona -u hscroot-p upt0058 Errors:The migrating partitions virtual SCSI adapter cannot be hosted by the existing virtual I/O server (VIOS) partitions on the destination managed system. To mi

22、grate the partition, set up the necessary VIOS hosts on the destination managed system, then try the operation again. Details:HSCLA356 The RMC command issued to partition arizona failed. This means that destination VIOS partition arizona2 cannot host the virtual adapter 6 on the migrating partition.

23、 HSCLA29A The RMC command issued to partition failed. The partition command is:migmgr -f find_devices -t vscsi -C 0 x3 -d 1The RMC return code is:0The OS command return code is:85The OS standard out is:Running method /usr/lib.methods/mig_vscsi85The OS standard err is: The search was performed for th

24、e following device descriptions: 2.0 262144 0 1 1 2 0 x81000000000000000 0 no vdasd 1 NI_RESERVE 261120017380003D30194072810XIV03IBMfcp UDID 解决方案如下(rxi)：确保(qubo)目标 MSP 能够访问源 MSP 访问的 vSCSI 磁盘。还要确保磁盘(c pn)没有被预订。当映射正确时，如果您仍然得到相同的错误，可能是由于源和目标 MSP 之间的 FC 适配器的类型不同。对于映射方法，请参阅 “故障诊断” 部分的最后一个Note小节。在目标 CEC 中

25、，如果 LPAR 没有足够的 CPUs，将得到以下错误：hscpedestiny4: migrlpar -o v -m dash -t wilma -p upt0053 -ip defiant2 -uhscroothmc-arizona -u hscrootErrors:The partition cannot be migrated because the processing resources it requires exceeds the available processing resources in the destination managed systems shared p

26、rocessor pool. If possible, free up processing resources from that shared processor pool and try the operation again.解决方案如下：我们需要通过 DLPAR 减少 LPAR 中的 CPU，或者更改配置文件。可以通过在目标机器的几个客户机上使用 DLPAR 操作（如果适用）来减少处理器单元数量，从而(cng r)增加目标机器的处理器数量。如果(rgu)目标 CEC 没有足够内存，则：hscpedestiny4: migrlpar -o v -m extra5 -t dash -p

27、upt0027Errors:There is not enough memory: Obtained: 2816, Required: 4608. Check that there is enough memory available to activate the partition. If not, create a new profile or modify the existing profile with the available resources, then activate the partition. If the partition must be activated w

28、ith these resources, deactivate any running partition or partitions using the resource, then activate this partition.可以(ky)采用如下任一解决方案：可以通过使用 DLPAR 操作或通过更改配置文件来减少 LPAR 中的内存量。可以通过使用 DLPAR 操作减少其他 LPARs 的内存来增加目标机器的内存。如果源、目标 VIOS 和 LPAR 之间没有建立 RMC (Resource Monitoring and Control) 连接，将得到以下错误：hscpedestiny

29、4: migrlpar -o v -m dash -t trim -p upt0053Errors: The operation to check partition upt0053 for migration readiness has failed. The partition command is:drmgr -m -c pmig -p check -d 1The partition standard error is: HSCLA257 The migrating partition has returned a failure response to the HMCsrequest

30、to perform a check for migration readiness. The migrating partition innot ready for migration at this time. Try the operation again later. Details:HSCLA29A The RMC command issued to partition upt0053 failed. The partition commend is:drmgr -m -c pmig -p check -d 1The RMC return code is:1141The OS com

31、mand return code is:0The OS standard out is:Network interruption occurs while RMC is waiting for the execution of the commandon the partition to finish.Either the partition has crashed, the operation has caused CPU starvation, orIBM.DRM has crashed in the middle of the operation.The operation could

32、have completed successfully. (40007) (null)The OS standard err is:要修复(xif)这个问题，请参阅 “Dynamic LPAR tips and checklists for RMC authentication and authorization”（developerWorks，2005 年 2 月）了解更多信息。如果正在试图迁移的分区拥有带有双 VIOS 设置的 MPIO，目标虽拥有双 VIOS 但没有针对(zhndu) MPIO 正确设置，则可能会得到以下错误：hscrootehmc-liken: migrlpar -o

33、v -m wilma -t visa -ip destiny4 -u hscroot -pupt0060Errors:HSCLA340 The HMC may not be able to replicate the source multipath I/Oconfiguration for the migrating partitions virtual I/O adapters on the destination. This means one or both of the following: (1) Client adapters that are assigned to diffe

34、rent source VIOS hosts may be assigned to a single VIOS host on the destination; (2) Client adapters that are assigned to a single source VIOS host may be assigned to different VIOS hosts on the destination. You can review the complete list of HMC-chosen mappings by issuing the command to list the v

35、irtual I/O mappings for the migrating partition. HSCLA304 A suitable shared memory pool for the mobile partition was not found on the destination managed system. In order to support the mobile partition, the destination managed system must have a shared memory pool that can accommodate the partition

36、s entitled and maximum memory values, as well as its redundant paging requirements. If the destination managed system has a shared memory pool, inability to support the mobile shared memory partition can be due to lack of sufficient memory in the pool, or lack of a paging space device in the pool th

37、at meets the mobile partitions redundancy and size requirements. Details:HSCLA297 The DLPAR Resource Manager (DRM) capability bits 0 x0 for mover servicepartition (MSP) visav2 indicate that partition mobility functions are not supported on the partition.HSCLA2FF An internal Hardware Management Conso

38、le error has occurred. If this error persists, contact your service representative. Warning:HSCLA246 The HMC cannot communicate migration commands to the partition visav2.Either the network connection is not available or the partition does not have a level of software that is capable of supporting p

39、artition migration. Verify the correct network and migration setup of the partition, and try the operation again.解决方案如下(rxi)：检查(jinch)双 VIOS 的正确性、适配器的可用性、以及 SAN 和交换机中的映射。如果上述解决方案无法实现(shxin)，可以：执行带-mpio 2的migrlpar命令。但是，这样做可能会失去 MPIO 磁盘的双 VIOS 设置。因此，这通常不 是 PowerVM 的推荐解决方案。如果 Source VIOS 拥有 “非推荐” NPIV，

40、我们将得到以下错误：hscrootehmc-liken: migrlpar -o v -m wilma -t visa -ip destiny4 -u hscroot -pupt0060Errors:HSCLA340 The HMC may not be able to replicate the source multipath I/Oconfiguration for the migrating partitions virtual I/O adapters on the destination. This means one or both of the following: (1) C

41、lient adapters that are assigned to different source VIOS hosts may be assigned to a single VIOS host on the destination; (2) Client adapters that are assigned to a single source VIOS host may be assigned to different VIOS hosts on the destination. You can review the complete list of HMC-chosen mapp

42、ings by issuing the command to list the virtual I/O mappings for the migrating partition. HSCLA304 A suitable shared memory pool for the mobile partition was not found on the destination managed system. In order to support the mobile partition, the destination managed system must have a shared memor

43、y pool that can accommodate the partitions entitled and maximum memory values, as well as its redundant paging requirements. If the destination managed system has a shared memory pool, inability to support the mobile shared memory partition can be due to lack of sufficient memory in the pool, or lac

44、k of a paging space device in the pool that meets the mobile partitions redundancy and size requirements. Details:HSCLA297 The DLPAR Resource Manager (DRM) capability bits 0 x0 for mover servicepartition (MSP) visav2 indicate that partition mobility functions are not supported on the partition.HSCLA

45、2FF An internal Hardware Management Console error has occurred. If this error persists, contact your service representative. Warning:HSCLA246 The HMC cannot communicate migration commands to the partition visav2.Either the network connection is not available or the partition does not have a level of

46、 software that is capable of supporting partition migration. Verify the correct network and migration setup of the partition, and try the operation again.当我们(w men)在 VIOS 中验证时：lsmap -all -npivName Physloc ClntID ClntName ClntOS- - - - -vfchost3 U9117.MMB.100302P-V1-C14 5 upt0052 AIXStatus:LOGGED_INF

47、C name:fcs0 FC loc code:U78C0.001.DBJ0563-P2-C1-T1Ports logged in:35Flags:aVFC client name:fcs1 VFC client DRC:U8233.E8B.100244P-V5-C4-T1Name Physloc ClntID ClntName ClntOS- - - - -vfchost3 U9117.MMB.100302P-V1-C13Status:LOGGED_INFC name:fcs0 FC loc code:U78C0.001.DBJ0563-P2-C1-T1Ports logged in:0Fl

48、ags:4VFC client name: VFC client DRC这里的问题是 vfchost3 和 vfchost8 同时映射到同一个主机（upt0058）且同时映射到同一个物理 FC(fcs0)。这不是推荐的设置。要修复(xif)这个问题，采用以下任一解决方案：我们需要(xyo)在连接到交换机的服务器上将其中一个 vfchost 映射到另一个 FC (fcs1)。可以通过 DLPAR 移除其中(qzhng)一个 vfchost。这个错误基本上代表了源和目标 FC 适配器之间的不兼容性。根据 FC 适配器的特征，这种不兼容性可能源自几个原因（因为对于多种不同的 FC 不兼容性问题或映射

49、问题，我们都有可能得到 “return code of 69”）。hscrootguandu5: migrlpar -o v -m flrx -t dash -ip destiny4 -u hscroot -p upt0064HSCLA319 The migrating partitions virtual fibre channel client adapter 4 cannot be hosted by the existing Virtual I/O Server (VIOS) partitions on the destination managed system. To migrat

50、e the partition, set up the necessary VIOS host on the destination managed system, then try the operation again. HSCLA319 The migrating partitions virtual fibre channel client adapter 3 cannot be hosted by the existing Virtual I/O Server (VIOS) partitions on the destination managed system. To migrat

51、e the partition, set up the necessary VIOS host on the destination managed system, then try the operation again. Details:HSCLA356 The RMC command issued to partition dashv1 failed. This means thatdestination VIOS partition dashv1 cannot host the virtual adapter 4 on the migrating partition. HSCLA29A

52、 The RMC command issued to partition dashv1 failed. The partition command is:migmgr -f find_devices -t vscsi -C 0 x3 -d 1The RMC return code is:0The OS command return code is:69The OS standard out is:Running method /usr/lib/methods/mig_vscsi69 The OS standard err is: The search was performed for the

53、 following device description: 2.0 1048576 0 1 -1 1 1 34 2 5 400 6 0 xc0507601a6730036 0 xc0507601a6730037 0 xc0507601a6730036 0 x0 1 0 x201600a0b84771ca 0 x201700a0b84771ca 0 x202400a0b824588d 0 x203400a0b824588d 0 x202500a0b824588d 0 x203500a0b824588d 0 x5005076303048053 0 x5005076303098053 0 x500

54、5076303198053 0 x500507630319c053 0 x500507630600872d 0 x50050763060b872d 0 x500507630610872d 0 x5005076306ib872d 0 x500a098587e934b3 0 x500a098887e934b3 0 x20460080e517b812 0 x20470080e517b812 0 x201400a0b8476a74 0 x202400a0b8476a74 0 x201500a0b8476a74 0 x202500a0b8476a74 0 x5005076304108e9f 0 x500

55、507630410ce9f 0 x50050763043b8e9f 0 x50050763043bce9f 0 x201e00a0b8119c78 0 x201f00a0b8119c78 0 x5001738003d30151 0 x5001738003d30181 0 x5005076801102be5 0 x5005076801102dab 0 x5005076801402be5 0 x5005076801402dab 可以采用以下(yxi)任一解决方案（由于目标 FC 适配器的其他不匹配特征，这些解决方案也可能会失败）：确保源和目标之间的 FC 适配器的特征(tzhng)一致。确保源和目

56、标(mbio)适配器达到同一组目标（检查分区）。确保 FC 适配器连接正确。有时，调试错误需要验证或迁移时的配置日志(rzh)。要获取这个日志，从源 MSP 运行以下命令：alog -t cfg -o cfglogLPM 的 NPIV 映射步骤(bzhu)如下：将 NPIV WWN (World Wide Name) 和 SAN WWN 分区(fn q)（zone）在一起。将 LUN 的 WWN 和 NPIV 客户机 WWN 屏蔽在一起。确保目标源和目标 VIOS 拥有一条道 SAN 子系统的路径。针对 LPM 的 vSCSI 映射步骤：将源和目标 VIOS WWN 和 SAN WWN 分区在

57、一起。确保使用来自 SAN 子系统的源和目标 VIOS 来屏蔽 LUN。 HYPERLINK /developerworks/cn/aix/library/au-LPM_troubleshooting/index.html l ibm-pcon 回页首POWER7 中的 LPM 增强根据进行 LPM 的 “LPM 先决条件” 小节的要求，LPAR 不应该拥有任何物理适配器，但如果它是一个 POWER7，那么它可以连接 Host Ethernet Adapter (Integrated Virtualized Ethernet)。但是，对于一个您想迁移到其他 POWER7 的 POWER7 LP

58、AR 而言，可以连接 HEA，但我们必须在一个新创建的虚拟适配器和处于聚合模式的 HEA 上创建以太网通道。当我们在目标上迁移时，我们只能看到配置了 IP 和以太网通道的虚拟适配器；HEA 将不被迁移。另外，确保将用于在虚拟适配器中 创建以太网通道的 VLANs 同时添加到源和目标 VIOS。在 LPM 之前：# lsdev -Cc adapterent0 Available Logical Host Ethernet Port (lp-hea)ent1 Available Logical Host Ethernet Port (lp-hea)ent2 Available Logical Ho

59、st Ethernet Port (lp-hea)ent3 Available Logical Host Ethernet Port (lp-hea)ent4 Available Virtual I/O Ethernet Port (l-lan)ent7 Available Virtual I/O Ethernet Port (l-lan)ent6 Available Virtual I/O Ethernet Port (l-lan)ent7 Available Virtual I/O Ethernet Port (l-lan)ent8 Available EtherChannel / 802

60、.3ad Link Aggregationent9 Available EtherChannel / 802.3ad Link Aggregationent10 Available EtherChannel / 802.3ad Link Aggregationent11 Available EtherChannel / 802.3ad Link Aggregationfcs0 Available C3-T1 Virtual Fibre Channel Adapterfcs1 Available C3-T1 Virtual Fibre Channel Adapterlhea0 Available