This section explains the 69XXX message series.
[Description]
An error occurred while communicating with target.
[Corrective Action]
Refer to the explanation in "Message number 69111" in the "Messages VE".
Also, perform the following corrective action depending on the target value.
If the IP address of VM management software is displayed:
Check whether communication with the VM management software is possible.
Use a ping command, etc. to check whether there is a problem with the network environment between the admin server and the VM management software.
If a LAN cable has become disconnected, reconnect it.
If the VM management product has VM management software, check whether there is a problem with connecting to the VM management product from the VM management software.
If the IP address of VM management software is displayed:
Perform the following corrective action depending on the value of detail.
For "VMware vCenter Server communication error(Virtual_storage_resource_name)"
Check the status of the virtual storage resources registered in the storage pool.
When the status is something other than "unknown", corrective action is not necessary as a communication error has occurred but recovery is complete.
When the status is "unknown", update virtual storage resources.
If the status does not change, perform the following corrective action:
Check that "VMware vCenter Server" is operating correctly on the IP address output for target.
For details on the check method, refer to the manual of the "VMware vCenter Server".
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
If a huge amount of these messages is output to the event log and makes it difficult to find the other messages, perform the following action:
Obtain the span of time when these messages were output.
The messages are output at about three minutes interval to the number of virtual storage that are showed on the storage tree.
Each page of event logs has ten items. With this in mind, you can reach to the span of time quicker by specifying appropriate page number.
Retrieve the messages that were output during the span of time which was obtained by step 1. from the system logs and the event logs of ROR console.
The system logs do not contain all messages.
Refer to "Appendix A System Log Messages" in "Messages VE" to know which kind of messages are output.
Up to the latest 20,000 messages are stored in the ROR console event log.
a) System log
Select the messages of the product that are output during the span of time which was obtained by step 1. The messages of this product can be identified by event types of "application" and source names that start with "JSE_SWRC_FJSVRCX".
b) Event log of the ROR console
Display the event logs whose status are "Error" only.
Sort the logs by event ID.
Make a rough estimate of the number of messages that were output by dividing the span of time which is retrieved by step 1. by three minutes. Also make a rough estimate of the number of pages which contain messages other than this message.
Lastly, extract messages other than this message which were output during the span of time which was retrieved in step 1.
For "VMware vCenter Server communication error"
Check that VMware vCenter Server is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the VMware vCenter Server manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "System Center Virtual Machine Manager communication error(Virtual_storage_resource_name)"
Check the status of the virtual storage resources registered in the storage pool.
When the status is something other than "unknown", corrective action is not necessary as a communication error has occurred but recovery is complete.
When the status is "unknown", update virtual storage resources. If the status does not change, take the following corrective action.
Check that SCVMM is operating correctly on the IP address output for target.
For details on the check method, refer to the SCVMM manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "System Center Virtual Machine Manager communication error"
Perform the following corrective actions:
Check that SCVMM is operating correctly on the IP address output for target.
For details on the check method, refer to the SCVMM manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "Oracle VM Manager communication error(Virtual_storage_resource_name)"
Check the status of the virtual storage resources registered in the storage pool.
When the status is something other than "unknown", corrective action is not necessary as a communication error has occurred but recovery is complete.
When the status is "unknown", update virtual storage resources.
If the status does not change, perform the following corrective action:
Check that Oracle VM Manager is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the Oracle VM Manager manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
For "Oracle VM Manager communication error"
Check that Oracle VM Manager is operating correctly on the IP address output for target.
For details on the check and configuration method, refer to the Oracle VM Manager manual.
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
If the IP address of storage management software is displayed:
Perform the following corrective actions:
The necessary settings for the storage management software may not have been completed. For details, refer to "D.3 Pre-setup Preparations (Storage)" of the "Setup Guide CE".
Check that communication is possible with the IP address output for target.
For the recovery procedure, refer to "Message number 67192".
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
Refer to the explanation in "Message number 69122" in the "Messages VE".
[Corrective Action]
Refer to the explanation in "Message number 69122" in the "Messages VE".
There is also the following case for Resource Orchestrator.
If a physical L-Server has been deleted:
There may be an error in the HBA BIOS settings.
Perform the following check and corrective action:
Check whether spin up delay has been set
If spin up delay has been set in HBA BIOS settings, cancel the setting and perform the operation again.
