1.2 Collecting Investigation Data(Cloud Edition)

This section explains how to collect investigation data that is necessary to find the cause of the problem.

The following describes collecting investigation data with the collection commands (ctmg_collectinfo or rcxadm agtctl snap) and collecting investigation data for storage management software and VM management products.

Refer to "13.2 ctmg_collectinfo (Collection of Investigation Data)" in the "Reference Guide (Command/XML) CE" for information on the command.
Refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE" for information on the command.

Collection procedure

Collect data on the server with the following procedure.

Log in the server as a user with administrative privileges of the OS.
Administrative privileges are required to collect investigation data.
Execute either the command ctmg_collectinfo, or the rcxadm agtctl snap -full and pmdiag commands.
Note that which command to execute depends on the function of the server.
- For the admin server
  [Windows Manager]
  >"Installation_folder\RCXCTMG\bin\ctmg_collectinfo" dir <RETURN>
  [Linux Manager]
  # /opt/FJSVctmg/bin/ctmg_collectinfo.sh dir <RETURN>
- For the managed server
  [Windows][Hyper-V]
  >"Installation_folder\Agent\bin\rcxadm" agtctl snap [-dir dir] -full <RETURN>
  >"Installation_folder\RCXCTMGA\bin\pmdiag <RETURN> (*1)
  [Linux]
  # /opt/FJSVrcxat/bin/rcxadm agtctl snap [-dir dir] -full <RETURN>
  # /opt/FJSVssqc/bin/pmdiag <RETURN> (*2)
  [VMware][KVM][OVM for x86 3.2]
  # /opt/FJSVrcxat/bin/rcxadm agtctl snap [-dir dir] -full <RETURN>
  [Solaris]
  # /opt/FJSVrcvat/bin/rcxadm agtctl snap [-dir dir] -full <RETURN>
Note
For VMware ESXi, because the agent of this product cannot be installed, you cannot execute investigation data collection commands.
*1: When the dialog window is displayed, specify a folder to save data, then click . After the message "Processing Completed Successfully ..." is displayed, collect following files in the folder.
- PMDiag?.cab
"?": denotes the index number of each of created files. No number is placed if only one file is created.
*2: Execution results will be stored in /tmp. Collect following files.
- ・pmdiag_*.tar.gz
- ・pmdiag_*.log
"*": denotes <host name>_<timestamp>. Timestamp format may differ according to system environment.
Collect investigation data for the storage management product and the VM management product.
For information about the collection procedures, see the manuals of these products.
[VMware]
When the VM management product is VMware vCenter Server, perform the operation as follows. Because the file size of investigation data is large, make sure that there is enough storage space before the operation.
1. Start VMware vSphere(TM) Client, and then connect to VMware vCenter Server as a user with system operation administrative privileges.
2. From the menu, select [Administration]-[Export System Logs].
3. Specify VMware vCenter Server as the object to export.
4. Specify the location to store and click <OK> button.
[Citrix Xen]
In the creating a L-Server or the collecting a cloning image, there is a possibility that the problem occurs by the sysprep of Windows processing or processing the mini setup when the error of following vmerrno =820 occurs.
- 67390 creating VM guest failed. detail=(timeout occurred while executing the customizing process.,vmerrno=820, ip=IP_address, host=VM_host_IP_address)
- 67397 FJSVrcx:ERROR:67397:failed to create image. detail=(timeout occurred while executing the customizing process.,vmerrno=820,ip=ip=IP_address, host=VM_host_IP_address)
Collect sysprep logs, Windows mini setup logs and customize tool logs on the VM guest according to the followin procedure.
1. Start XenCenter and connect it to the VM host to manage.
2. Force shutdown the VM guest that the error occurs to when it is running state.
3. Detach the disk at the position 0 of the VM guest in the storage tab.
4. Attach the disk that is detached from the VM guest according to the above-mentioned procedure to a Windows VM guest that is possible to start normaly.
  At this time, it does not care that the VM guest is running state or stopped state.
5. Start the VM guest that the disk attached to and logon as administrator account.
6. There is a possibility that the attached disk cannot be refered by the Explorer etc. when it is attached to the VM guest in the running state.
  Rescan disks with the disk managed tool when the disk is not refered.
7. Collect the all files in the following folders from the attached disk.
  (The following are examples when the system drive of the attached disk is recognized as G drive.)
  - G:\Windows\Panther
  - G:\Windows\System32\sysprep
  - G:\Program Files (x86)\Fujitsu\Resource Orchestrator\WinGuestCustomizeTool (in case of 64bit system)
  - G:\Program Files\Fujitsu\Resource Orchestrator\WinGuestCustomizeTool (in case of 32bit system)
8. Shutdown the VM guest.
9. Detach the disk that is attached to the VM guest.
10. Attach the disk to the VM guest that the error occurs to in storage tab.
Send the collected investigation data to Fujitsu technical support.