This section explains the 615XX message series.
[Virtual Edition]
Description
An error has occurred during the process set in "17.6 Network Parameter Auto-Configuration for Cloning Images" in the "User's Guide VE".
The target managed server is displayed for obj.
One of the following is displayed for event:
PRE_TGTSVR_IMAGE_CREATE
The error occurred in the process performed before collecting cloning images.
POST_TGTSVR_IMAGE_CREATE
The error occurred in the process performed after collecting cloning images.
POST_TGTSVR_IMAGE_INSTALL
The error occurred in the process performed after deploying cloning images.
One of the following is displayed for action:
[Windows]
Installation_folder\Agent\bin\rcxadm
[Linux]
/opt/FJSVrcxat/bin/rcxadm
Corrective Action
The processing results of the network parameter auto-configuration function are output in the following files:
Check the error messages output in these files and take corrective action for those messages.
[Windows]
Installation_folder\Agent\var\log\error_lan.log
[Linux]
/var/opt/FJSVnrmp/logs/error_lan.log
For details, refer to "17.6.2 Maintenance" in the "User's Guide VE".
After resolving the problem, perform the operation again using the following procedures.
Operations
When the error occurred before collection of cloning images
Perform cloning image collection again.
When the error occurred after collection of cloning images
Delete any collected cloning images, and then collect cloning images again.
When the error occurred after deployment of cloning images
When the managed server used for collection of cloning images is the same as that for deployment
Perform cloning image deployment again.
When modifying the definition file of the network parameter auto-configuration function, restore any system images collected before the cloning image was deployed, and then modify the definition file.
When the definition file of the automatic network parameter settings of the collection target has been modified, delete any cloning images collected before the modification was made, and then collect and deploy cloning images again.
When the managed server used for collection of cloning images is different from that for deployment
After resolving the problem, deploy cloning images again.
When the definition file of the automatic network parameter settings of the collection target has been modified, delete any cloning images collected before the modification was made, and then collect and deploy cloning images again.
[Virtual Edition]
Description
A timeout error has occurred during processing of the network parameter auto-configuration settings registered in "17.6 Network Parameter Auto-Configuration for Cloning Images" in the "User's Guide VE".
The target managed server is displayed for obj.
One of the following is displayed for event:
PRE_TGTSVR_IMAGE_CREATE
The error occurred in the process performed before collecting cloning images.
POST_TGTSVR_IMAGE_CREATE
The error occurred in the process performed after collecting cloning images.
POST_TGTSVR_IMAGE_INSTALL
The error occurred in the process performed after deploying cloning images.
One of the following is displayed for action:
[Windows]
Installation_folder\Agent\bin\rcxadm
[Linux]
/opt/FJSVrcxat/bin/rcxadm
Corrective Action
Check the load on the managed server. If there are no problems, perform the operation again based on "Operations" in "Message number 61501".
Description
A socket error of the HBA address rename setup service PxeMtftp|PxeParser|PxeService has occurred.
One of the following is indicated for %1:
PxeMtftp: Unable to bind to socket on port 69, Error=0x%x
PxeParser: Socket Error while binding DHCP Socket: 0x%x, Port 67, IP=%u-%u-%u-%u
PxeService: Initreg-Unable to bind send socket : WSAGetLastError = 0x%x
PxeService: Unable to bind send socket : WSAGetLastError = 0x%x
PxeService: Error 0x%x while binding Socket on Port=4011, IP=%u-%u-%u-%u
PxeService: Error 0x%x while binding DHCP Socket on Port=67, IP=%u-%u-%u-%u
[Linux]
The PxeMtftp message of the HBA address rename setup service is not output.
Corrective Action
Execute the netstat -na command and check if the following port is already used by another program. When the port is not in use, start the HBA address rename setup service again.
UDP port 69
Port 67 of IP Address %u-%u-%u-%u
Port 68 of IP Address 0.0.0.0
Port 68 of IP Address 0.0.0.0
Port 4011 of IP Address %u-%u-%u-%u
Port 67 of IP Address %u-%u-%u-%u
When the detailed information displayed for %1 is something other than the above, or if this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
As another instance of the ROR console is performing LAN switch discovery, the requested LAN switch discovery cannot be performed.
Multiple instances of LAN switch discovery cannot be performed simultaneously on a single manager.
The "LAN switch discovery" is displayed for operation.
Corrective Action
Wait until the LAN switch discovery being performed from another instance of the ROR console finishes, and then perform the operation again.
The status of operations being performed can be checked on Recent Operations of the ROR console.
[Cloud Edition]
Description
The version used for the export of the configuration information and the one used for the import are different.
The version used for the export is output in ExportVersion. When the version information does not exist in the configuration information specified at import, "unknown" is output.
The version used for the import is output in ImportVersion.
Corrective Action
Use the same version for the export and import system.
[Cloud Edition]
Description
The format of the specified value, or the content of the XML specified when performing the following is not correct:
Import of Configuration Information
Detailed information is output in the format "message: error part" for detail.
When the message is "invalid MIME type":
The format of the configuration information specified at import is not in XML format.
The specified MIME type is output in the error part.
When the message is "invalid XML tag":
The format of the XML tag information of the configuration information specified at import is not correct.
The XML tag name of the incorrect format is output in the error part.
When the message is "invalid tag name":
An incorrect resource type exists in the configuration information specified at import.
The highest-level tag of the incorrect resource type is output in the error part. When multiple element names are output, they are displayed separated by commas (",").
When the message is "lack of XML tag":
The configuration information specified at import does not contain all of the configuration information required for the resource type.
The highest-level tag of the resource type and the insufficient resource name are output in the error part. When multiple element names are output, they are displayed separated by commas (",").
When the message is "lack of resource tag":
The resource type information of the configuration information specified at import does not contain all of the required resource information.
The highest-level tag of the resource type and the insufficient resource name are output in the error part, separated by commas (",").
When the message is "duplicate XML tag":
There are multiple highest-level tags of the same resource type in the configuration information specified at import. When importing, multiple instances of the same resource type cannot be processed.
The top-level tag of the resource type is output to the error part. When multiple element names are output, they are displayed separated by commas (",").
Import of Network Configuration Information
Detailed information is output in the format "message: error part" for detail.
When the message is "invalid MIME type":
The format of the network configuration information specified at import is not in XML format.
The specified MIME type is output in the error part.
When the message is "invalid XML tag":
The format of the XML tag information of the network configuration information specified at import is not correct.
The XML tag name of the incorrect format is output in the error part.
When the message is "duplicate XML tag":
There are multiple highest-level tags of the same resource type in the network configuration information specified at import. When importing, multiple instances of the same resource type cannot be processed.
The top-level tag of the resource type is output to the error part. When multiple element names are output, they are displayed separated by commas (",").
Corrective Action
When Importing Configuration Information
Contact Fujitsu technical staff.
When Importing Network Configuration Information
Perform the operation again after checking the content displayed in detail, and resolving the cause of the error.
For the elements and values, refer to "14.6.1 Creating" in the "Reference Guide (Command/XML) CE".
