This section explains the 611XX message series.
[Description]
Startup of the manager failed.
The exit code of the command executed internally is displayed for code=%1.
[Corrective Action]
When mgr_name is "Task Manager" and code is "environment error"
The configuration of the manager restart is incorrect.
For details, refer to "Appendix A Notes on Operating ServerView Resource Coordinator VE" of the "ServerView Resource Coordinator VE Operation Guide" and restart the manager service.
When restarting the manager, stop it and then restart it.
For a code other than the above
Restart the manager.
When restarting the manager, stop it and then restart it.
For how to stop and start managers, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Stopping of the manager failed.
The name of the service which has not been stopped is given for mgr_name.
The exit code of the command executed internally is displayed for code=%1.
[Corrective Action]
[Windows]
Open "Services" from "Administrative Tools" on the Control Panel, and then stop the relevant service on the [Services] window.
[Linux]
Use the service command and stop the relevant service.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Starting of the service mgr_name comprising the manager failed.
The exit code of the command executed internally is displayed for code=%1.
[Corrective Action]
When mgr_name is "HBA address rename setup service"
Check the status of the HBA address rename setup service, and if it is "Stopping" then start the HBA address rename setup service.
For how to start the HBA address rename setup service, refer to "6.2.2.1 Settings for the HBA address rename setup service" of the "ServerView Resource Coordinator VE Setup Guide".
When mgr_name is something other than the above
Restart the manager. When the service comprising the manager has been started, stop the service of the manager and restart it. For how to stop and start managers, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The manager cannot be started because of the problem indicated in code=%1.
One of the following is indicated for %1:
timeout
A timeout has occurred during starting of the manager.
environment error
An error has occurred in the boot environment of the manager.
internal error
An internal error has occurred.
[Corrective Action]
Restart the manager.
When restarting the manager, stop it and then restart it.
For how to stop and start managers, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
Check the port number used by the manager, and change it as necessary.
For details, refer to "Appendix C Port List" of the "ServerView Resource Coordinator VE Setup Guide".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
No license file was found in directory.
[Corrective Action]
There is a chance that Resource Coordinator VE has not been installed successfully.
After uninstalling it, perform installation again.
[Description]
The status of the server server_name has been changed to status.
"error" or "fatal" is displayed for status.
[Corrective Action]
Locate the fault using the RC console.
The detailed information can be checked by starting the management software for each resource.
For operation from the RC console, refer to "Chapter 2 User Interface" of the "ServerView Resource Coordinator VE Setup Guide".
[Description]
Server switchover or failback failed because the source managed server original_server was not powered off.
The name of the managed server to be replaced is displayed for original_server.
The exit code of the command executed internally is displayed for code=%1.
[Corrective Action]
When the exit code displayed for %1 is "7"
The error may have occurred because a part of the manager program is not operating.
[Windows]
Open "Services" from "Administrative Tools" on the Control Panel, and then confirm that the following services have been started on the [Services] window.
Deployment Service
PXE Services
TFTP Service
[Linux]
Use the service command and confirm that the following services have been started.
scwdepsvd
scwpxesvd
scwtftpd
When the services have been started
Check the following:
Whether the managed server original_server is powered on
When the managed server original_server is powered on, manually power it off, and then perform manual switching or failback to original_server from the RC console.
When the managed server original_server is powered off, in that state perform either manual switching or failback from the RC console.
Whether communication with the server management unit is possible
Use the ping command or another method to check if there is a problem with the network environment between the admin server and the server management unit.
If a cable is disconnected from the LAN connector, connect it.
Whether Write (reference and updating) authority is possessed for the SNMP setting of the management blade
Check the SNMP community name set from the RC console.
If it was omitted, "public" will be specified.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
That the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values
For details of checks and the setup method, refer to the manual of the server being used.
When the services have not been started
[Windows]
Open "Services" from "Administrative Tools" on the Control Panel and execute the following operations on the [Services] window, and then perform manual switching or failback again.
Stop the Deployment Service
Stop the PXE Services
Stop the TFTP Service
Start the TFTP Service
Start the PXE Services
Start the Deployment Service
Stopping services
On the [Services] window, select the service to be stopped.
Right-click, select [Properties] from the displayed menu, and then click <Stop>.
Starting services
On the [Services] window, select the service to be started.
Right-click, select [Properties] from the displayed menu, and then click <Start>.
[Linux]
Use the service command, and after performing the following operations perform manual switching or failback again.
Stop scwdepsvd
Stop scwpxesvd
Stop scwtftpd
Start scwtftpd
Start scwpxesvd
Start scwdepsvd
Stopping services
Use the following command to stop services.
# service service_name stop <RETURN> |
Starting services
Use the following command to start services.
# service service_name start <RETURN> |
Note
When manual switching or failback will be performed again due to this message, perform the operation regardless of the status of original_server.
See
For server switchover, refer to "10.2 Switchover" of the "ServerView Resource Coordinator VE Operation Guide".
For failback, refer to "10.3 Post-Switchover Operations" of the "ServerView Resource Coordinator VE Operation Guide".
When the exit code displayed for %1 is something other than "7"
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Stopping of the manager failed.
[Corrective Action]
Perform stopping of the manager again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
A manager terminated abnormally.
[Corrective Action]
Restart the manager.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An error of the HBA address rename setup service PxeMtftp|PxeParser|PxeService has occurred.
One of the following is indicated for %1:
PxeParser: malloc returned NULL, there is insufficient memory available
There is not enough virtual memory available.
PxeService: Unable to Start TFTP Server
The TFTP Server could not be started.
[Linux]
The PxeMtftp message of the HBA address rename setup service is not output.
[Corrective Action]
[Windows]
Restart the HBA address rename setup service after exiting applications currently being used or increasing the amount of virtual memory.
To increase the amount of virtual memory, open "System" on the Windows Control Panel, and select the [Advanced] tab on the [System Properties] window.
[Linux]
Restart the HBA address rename setup service after exiting applications currently being used or increasing the amount of virtual memory.
Refer to the OS manual for the method for increasing the amount of virtual memory.
Execute the netstat -na command using the Windows command prompt and check if the UDP port 69 is already used by another program. When the port is not in use, start the HBA address rename setup service again.
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]
A service has stopped abnormally.
The service name stopped is displayed for service_name.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Control of the PXE server failed.
Processing of the WWN settings for the HBA of the server may fail.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An internal error has occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Obtaining the information of the admin server failed.
Processing of the WWN settings for the HBA of the server may fail.
[Corrective Action]
Check the following and resolve the problem:
Check the status of the admin server.
If the status is off, power on the admin server.
Check the startup status of the manager.
When the manager is stopped, start the manager.
The startup status of the manager can be checked using the following methods.
[Windows]
Open "Services" from "Administrative Tools" on the Control Panel, and check that the status of the Resource Coordinator Manager service on the [Services] window is "Started".
[Linux]
Use the service command and confirm that the "rcvmr" service has been started.
For details, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
Check if there is a problem with the network environment between the server used for the HBA address rename setup service and the admin server.
If a cable is disconnected from the LAN connector, connect it.
For HBA address rename setup service, refer to "6.2.2.1 Settings for the HBA address rename setup service" of the "ServerView Resource Coordinator VE Setup Guide".
Information
Check if the cause of the problem has been removed by examining the update information of the synchronization time in the [HBA address rename setup service] dialog. If the synchronization time is not updated within 15 minutes, the cause of the problem has not been removed.
If this does not resolve the problem, collect troubleshooting information of the HBA address rename setup service environment and contact Fujitsu technical staff.
[Description]
type information was not detected for a server blade.
"NIC for admin LAN" is displayed for type.
[Corrective Action]
There is a chance that the server blade has no NIC to use for the admin LAN or the management blade cannot correctly recognize the server blade's NIC.
Check the admin window of the management blade to see if the server blade's NIC is being recognized correctly.
If it is not being recognized correctly, remount the server blade and power it on.
For the PRIMERGY BX900 series, check that the setting for Automatic Inventory Retrieval on the management blade is "automatic". If the setting has already been made, there is a chance that the management blade has not yet recognized the admin LAN NIC. Wait a short while, and then check the admin window of the management blade to see if the server blade's NIC is being recognized correctly.
When using PRIMERGY BX620S5 or later servers, the NIC may not be recognized correctly if the power has not been turned on even once after mounting in the chassis.
Turn the power is on, and then check the admin window of the management blade to see if the server blade's NIC is being recognized correctly.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The processing of operation has failed.
The operation name is displayed for operation.
An error message indicating the reason processing of operation failed is displayed after this message (Multiple error messages may be displayed).
[Corrective Action]
Check the error number of the message related to operation which is displayed after this message, and take the corrective action indicated for that message.
[Description]
After processing of operation failed, processing of automatic recovery (rollback) failed.
The operation name is displayed for operation.
Before this message is output, an error message indicating that processing of operation failed in "Message number 61143" is output.
Also, an error message indicating the reason processing of automatic recovery (rollback) failed is displayed after this message (Multiple error messages may be displayed).
[Corrective Action]
Refer to the corrective action for "Message number 61143" output before this message, and take the corrective action for the cause of the failed operation.
Then check the error number of the error message indicating the cause of failure of automatic recovery (rollback) output after this message, and take the corrective action indicated for that message.
[Description]
The requested process cannot be performed as obj is undergoing server switchover.
[Corrective Action]
Perform the operation again after performing failback or continuation on the server.
[Description]
Failback or continuation has been executed for obj, which is not undergoing server switchover.
[Corrective Action]
Check that server switchover has been performed and then perform the operation again.
[Description]
As the maximum (limit) would be exceeded, no more resource can be registered.
[Corrective Action]
No action is required.
[Description]
The server OS category specified during server registration or agent registration is incorrect.
If this message is output during server registration, the server has been registered successfully but agent registration has failed.
[Corrective Action]
When os_name is VMware, select "VM Host" for the server OS category and execute agent registration.
[Description]
The status of the type resource name has been changed to status.
"error" or "fatal" is displayed for status.
[Corrective Action]
Locate the fault using the RC console.
The detailed information can be checked by starting the management software for each resource.
For operation from the RC console, refer to "Chapter 2 User Interface" of the "ServerView Resource Coordinator VE Setup Guide".
[Description]
value conflicts with the address_type of obj.
The following causes are possible:
The specified value conflicts with the address_type of obj
The value of an already registered obj is wrong
One of the following is displayed for address_type:
IP address
MAC address
network address
One of the following is displayed for obj:
admin server
Indicates the admin server.
Resource name
Indicates an already registered resource.
subnet name
Indicates an already registered subnet.
[Corrective Action]
When the specified value conflicts with the address_type of obj
Check and correct the value specified and then perform the operation again.
When the value of an already registered obj is wrong
Change the value of obj, and then perform the operation again.
[Description]
As the target chassis chassis_name has not been registered with the external software external_software, control of the server server_name failed.
The chassis name is displayed for chassis_name.
The name of the external software is displayed for external_software.
The name of the server is displayed for server_name.
[Corrective Action]
Register the target chassis with the external software.
After that, perform the operation again.
[Description]
As that target chassis chassis_name has not been registered as the target of management for the external software external_software, control of the server server_name failed.
The chassis name is displayed for chassis_name.
The name of the external software is displayed for external_software.
The name of the server is displayed for server_name.
[Corrective Action]
Register the target chassis as the target of management by the external software.
After that, perform the operation again.
[Description]
An error occurred during the configuration of virtual I/O settings.
A detailed message is displayed for detail.
[Corrective Action]
Check the content of detail, and take corrective action.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
There is an inconsistency in the state of resources registered with the external software external_software and the actual state.
The name of the external software is displayed for external_software.
[Corrective Action]
When performing operations with the external software at the same time, stop the operations temporarily.
After that, perform the operation again.
[Description]
As there is a problem with the state of the server, assignment of a server profile failed.
The name of the external software is displayed for external_software.
The name of the server is displayed for server_name.
A detailed message is displayed for detail.
[Corrective Action]
Check the state of the server, and perform hardware replacement if there is a problem with the server.
After confirming the state of the server is normal, perform the operation again.
[Description]
A license error has occurred with the external software external_software.
The name of the external software is displayed for external_software.
A detailed message is displayed for detail.
[Corrective Action]
Check that the license settings of the external software have been configured correctly.
After confirming the license settings have been configured correctly, perform the operation again.
[Description]
A function not supported by the server server_name has been included in the server profile profile_name.
The name of the server is displayed for server_name.
The name of the server profile is displayed for profile_name.
The name of the external software is displayed for external_software.
A detailed message is displayed for detail.
[Corrective Action]
Check that the BIOS or iRMC firmware versions of the servers which the server profile is to be allocated to are compliant with the server profile function. If the version is not compliant, upgrade to a compliant version or refer to the manual of the external software, and correct the function settings in the server profile to one that is supported.
After performing the corrective action above, perform the operation again.
[Description]
The power of the server server_name has not been stopped.
The name of the server is displayed for server_name.
[Corrective Action]
Stop the power of the server.
After that, perform the operation again.
[Description]
The I/O device used for the assignment of the server profile to the server server_name was not found.
The name of the server is displayed for server_name.
[Corrective Action]
Check the server profile and mount the necessary I/O device.
After that, perform the operation again.
[Description]
There is an inconsistency in the configuration of the external software external_software.
The name of the resource is displayed for resource_name.
The name of the external software is displayed for external_software.
A detailed message is displayed for detail.
[Corrective Action]
Refer to the manual of the external software, and take corrective action.
After that, perform the operation again.
[Description]
A compatibility problem between the server server_name and the external software external_software has occurred.
The name of the external software is displayed for external_software.
The name of the server is displayed for server_name.
[Corrective Action]
Refer to the external software external_software, and replace the server server_name with a compatible model.
After that, perform the operation again.
[Description]
The external software external_software has not been installed.
The name of the external software is displayed for external_software.
[Corrective Action]
Install the external software.
After that, perform the operation again.
[Description]
The server profile is invalid.
The name of the server profile is displayed for profile_name.
A detailed message is displayed for detail.
[Corrective Action]
Check the content of the server profile.
After that, perform the operation again.
[Description]
An authentication error occurred during communication with the external software external_software.
The name of the external software is displayed for external_software.
The user name for which authentication failed is displayed for username.
[Corrective Action]
Correct the account information of the external software.
After that, perform the operation again.
[Description]
The external software external_software does not support the server server_name.
The name of the external software is displayed for external_software.
The name of the server is displayed for server_name.
A detailed message is displayed for detail.
[Corrective Action]
Replace the target server with a model that is supported by the external software.
After that, perform the operation again.
[Description]
There is an error in either the virtualization method configuration config_type for servers, or the configuration of the server profiles for servers.
The spare servers for which there is an error in the virtualization method configuration config_type are displayed for servers.
When there are multiple servers, they are displayed separated by commas (",").
[Corrective Action]
Based on the content of servers, check the virtualization method configuration.
When servers is a spare server
Check and correct the virtualization method configuration of the spare server, and then perform the operation again.
When servers is something other than a spare server
Two virtualization methods, VIOM coordination and HBA address rename, have both been configured for the server. Ensure that only one virtualization method is used in a single chassis.
[Description]
The specified external software external_software has not been registered.
[Corrective Action]
Check that there are no mistakes in the configuration of external_software and that external_software has not been deleted.
[Description]
The switchover configuration of the server server_name set as the spare server or the spare server that has been switched to is invalid. If switchover to or failback from server_name is attempted, it will fail.
The cause of the failure of switchover or failback is displayed for detail.
When detail is "expected VIOM server profile not found"
The VIOM server profile configured for the primary server when setting it as a spare server cannot be found. The VIOM configuration may have been changed or deleted.
[Corrective Action]
Follow the content displayed for detail and check the switchover settings for server_name.
When detail is "expected VIOM server profile not found"
Check the state of the server profile from the VIOM management console, perform I/O virtualization configuration for server_name and then repeat the operation.
[Description]
The switchover configuration of the physical server server_name set as the spare server, or the server that was switched from, is invalid. When server_name is selected as a spare server for the switchover process, or when failback is performed, the operation will fail.
The cause of the failure of switchover or failback is displayed for detail.
When detail is "expected VIOM server profile not found"
An already registered agent with the VIOM server profile configured was specified for server_name when setting it as the spare server, but the server profile cannot be found.
When detail is "unexpected VIOM server profile was found"
A VIOM server profile was configured for server_name when setting it as a spare server, but the VM host cannot be detected.
[Corrective Action]
Follow the content displayed for detail and check the switchover settings for server_name.
When detail is "expected VIOM server profile not found"
Check the state of the server profile from the VIOM management console, perform I/O virtualization configuration for server_name and then repeat the operation.
When detail is "unexpected VIOM server profile was found"
When dealing with a spare server or a server that has undergone switchover, check the state of the original server and use the VIOM management console to check the state of the server profile. Then change the I/O virtualization configuration of server_name and perform the operation again.
Or, change the spare server configuration information.
[Description]
The boot configuration settings for spare_servers are inconsistent.
The name of the server for which spare server settings were performed is displayed for server_name.
The names of the physical servers which were specified as the spare servers for server_name are displayed for spare_servers, separated by commas.
[Corrective Action]
Check and correct the boot configurations of the physical servers specified as spare servers, and then perform the operation again.
[Description]
As there is no virtual I/O configuration for server_name, SAN boot cannot be specified.
[Corrective Action]
Check and correct the virtual I/O configuration and then perform the same operation on the spare server again.
[Description]
Another control command is currently being executed.
[Corrective Action]
Wait a couple of minutes and then execute the command again.
[Description]
No license was found for the feature being used.
[Corrective Action]
In order to perform the process, purchase a license for the product which is required for the process.
[Description]
The value specified as type is invalid.
The following is displayed for type:
network address
subnet mask
gateway
nic number
[Corrective Action]
Check and correct the value specified and then perform the operation again.
[Description]
service has not been installed.
The following is displayed for service:
DHCP Server
[Corrective Action]
Install service, and then perform the operation again.
[Description]
service has not been started.
The following is displayed for service:
DHCP Server
[Corrective Action]
Start service, and then perform the operation again.
[Description]
The processing of the function for obj has not been performed.
The reason the processing of function was not performed is displayed for detail.
When function is "deploying cloning image"
Deployment of a cloning image failed.
When detail is "target servers are in different subnets"
Multiple managed servers belonging to differing subnets have been specified as the cloning image deployment destination.
When function is "replacing server"
Re-configuration of hardware information failed.
When detail is "blade types are different"
The blade types after replacement of servers differ from those before replacement.
[Corrective Action]
Resolve the problem taking corrective action based on the content of function and detail.
When function is "deploying cloning image"
When detail is "target servers are in different subnets"
Perform deployment of cloning images to each managed server belonging to the same subnet.
When function is "replacing server"
When detail is "blade types are different"
If the blade type after server replacement differs that of before replacement, delete the registered server, replace the hardware and then perform server registration again.
[Description]
The entered license key cannot be used.
[Corrective Action]
Check if there are any mistakes in the entered license key. If there are no mistakes in the entered license key, check the product name, version, and usage limit applied for when obtaining the license key. Inputting a valid license key will resolve the problem.
[Description]
Startup of the script script_name has failed.
[Corrective Action]
Check the file attributes and environment of the script, and resolve any problems so the script can be executed.
[Description]
The script named script_name has terminated abnormally.
The exit code of the script is displayed for value.
[Corrective Action]
Take corrective action based on the error details.
[Description]
VIOM operations failed, because the spare server settings have been performed for obj.
[Corrective Action]
Release the settings of the spare server, and then perform the operation again.
