2022年动态分区迁移基础知识和故障诊断.docx

《2022年动态分区迁移基础知识和故障诊断.docx》由会员分享，可在线阅读，更多相关《2022年动态分区迁移基础知识和故障诊断.docx（41页珍藏版）》请在淘文阁 - 分享文档赚钱的网站上搜索。

1、精选学习资料 - - - - - - - - - 动态分区迁移（ LPM）基础学问和故障诊断简介Live Partition Mobility LPM 在 Power6 上引入,旨在在迁移到其他主机时在 VIOS 和固件升级过程中帮忙防止停机；LPM 也削减了创建新 LPAR 和设置时所需的工作量,这对于应用程序而言是必要的；大部分客户将 LPM 活动视为一种日常工作,但许多客户都不明白准确流程或正在发生的事情；本文将展现克服或修复 LPM 问题的步骤；图 1. AIX I/O 堆栈LPM 关键点关于 LPM 务必记住： LPM 将正在运行的分区从一个物理服务器迁移到另一个,同时保护完整的事务

2、完整性并转移整个环境：处理器状态、内存、虚拟设备和已连接的用户；分区在关闭时也可以进行迁移（消极迁移）,操作系统和应用程序必需驻留在共享储备器上；LPM 先决条件您必需在启用了 Advanced Power Virtualization Feature 的 POWER6 （或更高版本）上至少拥有两台机器：一个源和一个目标；操作系统和应用程序必需驻留在一个共享外部储备器（ Storage Area Network）上；除了这些硬件要求外,您仍必需拥有：一个硬件治理掌握台- HMC（可选）或 IVM ；目标系统必需拥有足够的资源,比如 CPU 和内存；LPAR 不应当拥有物理适配器；您的虚拟 I/

3、O 服务器（virtual I/O server ,VIOS）必需拥有一个 Shared Ethernet Adapter SEA 并被配置为桥接到移动分区使用的那个 Ethernet 网；它必需能够供应对移动分区使用的全部磁盘资源的虚拟拜访才能（必需是物理磁盘（而不是规律卷）；NPIV 或 vSCSI ）；假如使用 vSCSI ,就虚拟目标设备名师归纳总结 - - - - - - -第 1 页,共 23 页精选学习资料 - - - - - - - - - 必需使用 AIX 5.3J 版或更高版本,VIOS 1.4 版或更高版本,HMC V7R310 或更高版本,固件必需是 efw3.1 或更

4、高版本；LPM 过程中所发生的事图 2. 一般 LPM 图示下面的步骤描述了图 2 中的一般 LPM 图示：1. 分区配置文件（此时处于活动状态）从源复制到目标 FSP；2. 配置目标上的储备器；3. 移动程序服务分区（Mover Service Partition,MSP）被激活；4. 分区迁移开头；a. 大部分内存页面被移动；b. 全部线程转为闲置状态；5. 激活过程在目标上复原；a. 最终的内存页面被移动；b. 清理储备器和网络流量；6. 取消源上的储备器资源配置；7. 从源 FSP（Flexible Service Processor）移除分区配置文件；如何进行 LPM 名师归纳总结

5、- - - - - - -第 2 页,共 23 页精选学习资料 - - - - - - - - - 进行 LPM 之前,需要验证源和目标两端的资源可用性；假如验证由于某种错误而失败,就需要修复错误才能连续下一步；有时,验证过程可能会显现一些警告消息,不用管它们；使用 HMC GUI 进行 LPM 图 3 展现如何使用 HMC GUI 来验证 LPAR；在 System management - Servers - Trim屏幕中,挑选 LPAR 名称：Operations - Mobility - Validate图 3. 验证 LPAR验证屏幕（如图 4 所示）显示, upt0052 LPA

6、R 被验证,以便从trsim迁移到dash,假如名师归纳总结 需要,必需指定目标 HMC；第 3 页,共 23 页- - - - - - -精选学习资料 - - - - - - - - - 图 4. Validation 窗口图 5 显示 LPM 显现了一条警告消息,忽视该消息,挑选Close连续迁移；名师归纳总结 - - - - - - -第 4 页,共 23 页精选学习资料 - - - - - - - - - 图 5. 验证通过并显现一般警告消息Partition Migration Validation屏幕（见图 6 ）显示信息被选中,以便设置到另一个托名师归纳总结 管系统的分区迁移；挑

7、选Migrate以验证信息；第 5 页,共 23 页- - - - - - -精选学习资料 - - - - - - - - - 图 6. 验证通过后迁移预备就绪迁移终止后,如图 7 所示,挑选Close ；名师归纳总结 - - - - - - -第 6 页,共 23 页精选学习资料 - - - - - - - - - 图 7. 迁移进程使用命令行选项的 HMC 要验证本地 HMC 中的 LPM,输入以下代码：migrlpar -o v -m source cec -t target cec -p lpar to migrate 要验证远程 HMC 中的 LPM,输入：migrlpar -o v

8、 -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 -p lpar to migrate -ip target hmc -u remot

9、e user 假如源和目标之间的配置问题导致 LPAR 发生 MPIO Multipath IO 失败,输入以下命令连续（假如适用的话）：migrlpar -o m -m wilma -t visa -p upt07 -redundantpgvios 0 -n upt07_n 名师归纳总结 - - - - - - -第 7 页,共 23 页精选学习资料 - - - - - - - - - oams_npiv -u hscroot -vlanbridge 2 -mpio 2 -w 60 -d 5 -v -i source_msp+name=wilmav2,dest_msp_name=visav2

10、 -ip destiny4 故障诊断本节介绍可能遇到的各种错误及其更正方法；假如需要跨两个不同的 HMC 进行 LPM,在迁移时,需要在两个 HMC 之间设置适当 的授权；假如没有设置适当的授权,将显示以下 mkauthkey 错误：hscrootdestiny4: migrlpar -o v -m trim -p UPT0052 -ip hmc-arizona -u hscroot -t arizona HSCL3653 The Secure Shell SSH communication configuration between the source and target Hardwar

11、e Management Consoles has not been set up properly for user hscroot. Please run the mkauthkeys command to set up the SSH communication authentication keys. 要克服这个错误,输入：hscrootdestiny4: mkauthkeys -g -ip hmc-arizona -u hscroot Enter the password for user hscroot on the remote host hmc-arizona 假如正在迁移一个

12、 POWER7 Advanced Memory Expansion AME 分区,那么对于任一 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 the following error: HSCLA335 The Hardware Management Console for the destina

13、tion managed system does not support one or more capabilities required to perform this operation. The unsupported capability codes are as follows: AME_capability hscrootdestiny4: 要更正这个错误,要么迁移到 POWER7,要么移除这个 AME 然后再进行迁移；假如您正在迁移一个 Active Memory Sharing AMS 分区,但 AMS 设置不正确,或者目标上没有闲暇的分页设备,将显示以下错误：hscroot

14、hmc-liken: migrlpar -o v -m wilma -t visa -ip destiny4 -u hscroot -p 名师归纳总结 - - - - - - -第 8 页,共 23 页精选学习资料 - - - - - - - - - upt0060 -mpio 2 Errors: HSCLA304 A suitable shared memory pool for the mobile partition was not found on the destination managed system. In order to support the mobile partit

15、ions, the destination managed system must have a shared memory pool that can accommodate the partitions entitled and maximum memory values, as well ad its redundant paging If the destination managed system has a shared memory pool, inability requirements. to support the mobile shared memory partitio

16、n can be due to lack of sufficient memory in the pool, or lack 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 x for mover service partition MSP visav2 indicate that partition mob

17、ility functions are not supported on the partition. HSCLA2FF An internal Hardware Management Console error has occurred. If this error persists, contact your service representative. 要更正这个错误,执行下面一项操作,或者同时执行两项操作：o 由于这个问题与冗余 AMS 设置有关, 因此目标 AMS 池应当拥有针对一个特 定 AMS 池的冗余才能,这个 AMS 池定义为 Shared Memory Pool,包含两

18、个只用于高可用性 HMC 的 Paging VIOS 分区；用户可以为每个 Shared Memory Partition 挑选主要和替代分页 VIOS ；要明白 AMS 的相关细节,请参阅“ 一位客户配置 Active Memory Sharing 的经受 ”（developerWorks ,2022 年 8 月）明白更多信息；o 目标 AMS 池中应当有足够的空间用于分页设备；假如试图将 LPAR 从 Power7 迁移到 Power6 CPU,将得到以下错误：hscrootdestiny4: migrlpar -o v -m dash -t arizona -ip hmc-arizona

19、 -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. Use the HMC to configure a level that is compatible with the destination managed system. 上述错误的解决方案可是

20、以下之一：名师归纳总结 o迁移到 POWER7；第 9 页,共 23 页将处理器模式更换为适当的模式（就像在目标托管系统中一样）；o- - - - - - -精选学习资料 - - - - - - - - - 在 HMC GUI 中更换处理器模式的步骤如下：挑选 LPAR 并取消其激活状态；转到 Configuration-Manage Profiles；挑选需要激活的配置文件；转到 Processors ,将Processor compatibility mode:更换为需要的设置并使用相同的配置文件引导它；oLPAR 应当在源和目标 MSPs 上拥有相同的共享 vSCSI 磁盘：hscroo

21、tdestiny4: 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 migrate the partition, set up the necessary VIOS hosts on

22、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. HSCLA29A The RMC command issued to partition failed. T

23、he partition command is: migmgr -f find_devices -t vscsi -C 0x3 -d 1 The RMC return code is: 0 The OS command return code is: 85 The OS standard out is: Running method /usr/lib.methods/mig_vscsi 85 The OS standard err is: The search was performed for the following device descriptions: 2.0 262144 0 1

24、 1 名师归纳总结 - - - - - - -第 10 页,共 23 页精选学习资料 - - - - - - - - - 2 0x81000000000000000 0 no vdasd 1 NI_RESERVE 261120017380003D30194072810XIV03IBMfcp UDID o 解决方案如下：确保目标 MSP 能够拜访源 MSP 拜访的 vSCSI 磁盘；仍要确保磁盘没有被预订；当映射正确时,假如您仍旧得到相同的错误,可能是由于源和目标 MSP 之间的 FC 适配器的类型不同； 对于映射方法, 请参阅“ 故障诊断”部分的最终一个 Note 小 节；在目标 CEC 中,

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

26、 processor pool. If possible, free up processing resources from that shared processor pool and try the operation again. 名师归纳总结 - - - - - - -第 11 页,共 23 页精选学习资料 - - - - - - - - - 解决方案如下：o 我们需要通过 DLPAR 削减 LPAR 中的 CPU,或者更换配置文件；o 可以通过在目标机器的几个客户机上使用 DLPAR 操作（假如适用）来削减 处理器单元数量,从而增加目标机器的处理器数量；假如目标 CEC 没有足够内

27、存,就：hscpedestiny4: migrlpar -o v -m extra5 -t dash -p upt0027 Errors: 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 acti

28、vate the partition. If the partition must be activated with these resources, deactivate any running partition or partitions using the resource, then activate this partition. 可以采纳如下任一解决方案：o 可以通过使用 DLPAR 操作或通过更换配置文件来削减 LPAR 中的内存量；o 可以通过使用 DLPAR 操作削减其他 LPARs 的内存来增加目标机器的内存；假如源、目标 VIOS 和 LPAR 之间没有建立 RMC

29、Resource Monitoring and Control 连接,将得到以下错误：hscpedestiny4: migrlpar -o v -m dash -t trim -p upt0053 Errors: The operation to check partition upt0053 for migration readiness has failed. The partition command is: drmgr -m -c pmig -p check -d 1 The partition standard error is: HSCLA257 The migrating par

30、tition has returned a failure response to the HMCs request to perform a check for migration readiness. The migrating partition in not 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

31、 -m -c pmig -p check -d 1 The RMC return code is: 1141 The OS command return code is: 0 The OS standard out is: Network interruption occurs while RMC is waiting for the execution of the command 名师归纳总结 - - - - - - -第 12 页,共 23 页精选学习资料 - - - - - - - - - on the partition to finish. Either the partition

32、 has crashed, the operation has caused CPU starvation, or IBM.DRM has crashed in the middle of the operation. The operation could have completed successfully. 40007 null The OS standard err is: 要修复这个问题,请参阅“ Dynamic LPAR tips and checklists for RMC authentication and authorization” （developerWorks ,2

33、005 年 2 月）明白更多信息；o假如正在试图迁移的分区拥有带有双 VIOS 设置的 MPIO,目标虽拥有双VIOS 但没有针对 MPIO 正确设置,就可能会得到以下错误：hscrootehmc-liken: migrlpar -o v -m wilma -t visa -ip destiny4 -u hscroot -p upt0060 Errors: HSCLA340 The HMC may not be able to replicate the source multipath I/O configuration for the migrating partitions virtua

34、l I/O adapters on the destination. This means one or both of the following: 1 Client 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

35、hosts on the destination. You can review the complete list of HMC-chosen mappings 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

36、the mobile partition, the destination managed system must have a shared memory 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

37、 memory partition can be due to lack of sufficient memory in the pool, or lack 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 0x0 for mover service partition MSP visav2 indicate

38、that partition mobility functions are not supported on the partition. HSCLA2FF 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

39、network connection is not available or the partition does not have a level of software that is capable of supporting partition migration. Verify the correct network and migration setup of the partition, and try the operation again. 名师归纳总结 - - - - - - -第 13 页,共 23 页精选学习资料 - - - - - - - - - o 解决方案如下：检

40、查双 VIOS 的正确性、 适配器的可用性、以及 SAN 和交换机中的 映射；假如上述解决方案无法实现,可以：执行带 -mpio 2 的 migrlpar 命令；但是,这样做可能会失去 MPIO 磁盘的双 VIOS 设置；因此,这通常不 案；是 PowerVM 的举荐解决方o假如 Source VIOS 拥有“ 非举荐” NPIV ,我们将得到以下错误：hscrootehmc-liken: migrlpar -o v -m wilma -t visa -ip destiny4 -u hscroot -p upt0060 Errors: HSCLA340 The HMC may not be a

41、ble to replicate the source multipath I/O configuration 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 different source VIOS hosts may be assigned to a single VIOS host on the destination; 2 Client

42、 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 virtual I/O mappings for the migrating partition. HSCLA304 A suitable shared memory pool for

43、 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 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 suffici