Known problems and workarounds
Various problems were encountered while researching and completing some of the tasks described in this document. This appendix describes them and offers workaround solutions for each problem encountered:
This error occurs when an LPAR is missing a default profile or a current profile. This causes some VMControl operations to fail and prevents the removal of the LPAR itself.
This problem occurs during capture of a virtual appliance. If the OS of the virtual server being captured is installed on a volume on the V7000, and that volume has spaces in its name, FlashCopy will not be used to copy the volume.
If two operating systems are clones of one another, the FSM will not be able to differentiate between them. When discovering two operating systems that are clones, the FSM will correctly discover the first operating system, but the second will be seen as the same operating system as the first.
A.1 DNZVMP016E: Internal application error
This error occurs when an LPAR is missing a default profile or a current profile. Some VMControl operations can fail, preventing the removal of the LPAR itself. To determine if a particular LPAR has these profiles defined, issue the following command from the FSM command line:
lssyscfg -r prof -m <LPAR name> -Flpar_id:name
Example A-1 Missing values
USERID@f3efsm:~> lssyscfg -m Server-7895-22X-SN102736B -r lpar -F lpar_id,name,default_profile,curr_profile
2,TemplateOS,,
1,7895_SN102736B_VIOS1,,
3,AIX71template,OriginalProfile,OriginalProfile
The workaround to this problem is to assign values to the empty variables using the chsyscfg command on the FSM’s command line. The commands are at the following site:
A.2 FlashCopy not used during capture of a virtual appliance
This problem occurs during capture of a virtual appliance. If the OS of the virtual server being captured is installed on a volume on the V7000, and that volume has spaces in its name, FlashCopy will not be used to copy the volume. If the image repository is hosted by a VIO server, the dd command will be used by the capture (or copy) operation instead. The capture operation succeeds but takes significantly longer than it does when FlashCopy is used.
The “Capture virtual appliance” job log shows the following message:
DNZLOP899I Storage copy services is unable to copy one or more disks using the FlashCopy function, because FlashCopy is not configured. The server that controls the image repository will copy the disks.
To prevent this problem, do not use spaces when naming volumes on the V7000 (for example, use AIX_bootdisk instead of AIX boot disk).
A.3 Discovering cloned operating systems
If two operating systems are clones of each other, the FSM is unable to differentiate between them. When discovering two operating system that are clones, the FSM correctly discovers the first. The FSM will create a new object to represent this operating system and its discovery status will be set to new. Discovery of the second operating system succeeds. However, instead of creating a new object to represent the second operating system, the FSM lists the second operating system as “previously discovered” and the IP address of the second operating system will simply be added to the list of IP addresses associated with the first.
Because the operating systems’ file systems are clones, they contain identical UIDs, Tivoli GUIDs, and SSH keys. To correct this issue, new UIDs, GUIDs, and SSH keys must be generated for one of the two operating systems, and the Common Agent Services agent must be restarted.
The information center provides the procedure:
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.