This section explains the 615XX message series.
[Description]
An error has occurred during the process set in "8.6 Network Parameter Auto-Configuration for Cloning Images" of the "ServerView Resource Coordinator VE Setup Guide".
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 "8.6.2 Maintenance" of the "ServerView Resource Coordinator VE Setup Guide".
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 deployment 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 used 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 used 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.
[Description]
A timeout error has occurred during processing of the network parameter auto-configuration settings registered in "8.6 Network Parameter Auto-Configuration for Cloning Images" of the "ServerView Resource Coordinator VE Setup Guide".
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.
For a.: UDP port 69
For b.: Port 67 of IP Address %u-%u-%u-%u
For c.: Port 68 of IP Address 0.0.0.0
For d.: Port 68 of IP Address 0.0.0.0
For e.: Port 4011 of IP Address %u-%u-%u-%u
For f.: 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 RC 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 RC console finishes, and then perform the operation again.
The status of operations being performed can be checked on Recent Operations of the RC console.
