- 论坛徽章:
- 0
|
找到相关的解释了,如下:
After alternate disk install cloning, improper hostname resolution may cause HMC RSCT errors
Abstract
A properly defined system hostname is critical for RSCT function. This TIP reminds you that cloning can cause hostname resolution problems.
Contents
Dynamic LPAR relies on Service Focal Point and RSCT. This means that TCP/IP, including the hostname on the HMC, must be configured. The /etc/hosts files in the HMC and all LPARs must have entries for all entities with the hostname appearing first in any list of aliases.
A problem with DLPAR can exist after using the altinst_rootvg cloning procedure to create the second LPAR. The file /etc/ct_node_id had the same contents on both LPARs so RSCT may detect only one LPAR to manage. Development is aware of this and is working on a circumvention and correction. In the meantime, a workaround is to run the following two commands after the first boot of the new LPAR:
/usr/sbin/rsct/install/bin/uncfgct -n
/usr/sbin/rsct/install/bin/cfgct
A subsequent reboot will cause the partitions to be synchronized from an RSCT perspective. The duplicate /etc/ct_node_id condition are likely to cause negative behaviors in a HACMP scenario between cloned LPARs. Cloning an LPAR with a mksysb tape/DVD will likely cause the same problem. NIM installs avoid this problem as a unique /etc/ct_node_id file is created.
另外,以下是alt_disk_install OBC参数的含义:
-O Performs a device reset on the target altinst_rootvg. This will cause alt_disk_install to NOT retain any user defined device configurations. This flag is useful if the target disk or disks will become the rootvg of a different system (such as in the case of logical partitioning or system disk swap).
-B Would specify not running bootlist after the mksysb or clone. If set, then -r flag cannot be used.
-C Clone rootvg.
所以,综合来看,应该是楼主没有使用OBC参数导致,大家意下如何?
另,yddll,多写几个字可以么?如你上书5字符有太多含义可以解释了,谢谢! |
|