This section explains the 671XX message series.
[Description]
The command was executed without OS administrator authority.
[Corrective Action]
Execute the command with OS administrator authority.
When using Windows Server 2008, it is not possible for user accounts not named 'Administrator' that have administrator authority to execute commands with administrator authority even by starting the command prompt from the menu.
Right-click Command Prompt on the menu, and start a command prompt by selecting [Run as administrator] from the displayed menu. Then perform the operation.
[Description]
The option is invalid. "usage" is displayed.
[Corrective Action]
Check and correct the command format, and then perform the operation again.
[Description]
The name obj contains invalid characters.
[Corrective Action]
Specify the name using alphanumeric characters, and underscores ("_"). Check the name, and then perform the operation again.
[Description]
Resources that match obj were not found.
[Corrective Action]
Check the conditions specified.
[Description]
The file filename1 cannot be copied to the file filename2.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
The access authority for the file or directory
That there is sufficient disk area available
[Description]
The file or directory obj cannot be created.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
The access authority for the directory
That there is sufficient disk area available
[Description]
An error occurred during execution of the command obj.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
There is not enough memory available.
[Corrective Action]
Exit any unnecessary programs, and then perform the operation again.
If performing the operation again does not resolve the problem, refer to "1.4.2.6 Memory Size" of the "Setup Guide VE" and check that the memory is sufficient.
[Description]
The specified directory was not found.
[Corrective Action]
Specify the correct directory.
[Description]
The specified time and date are invalid.
[Corrective Action]
Specify the date and time using the format "YYYY/MM/DD hh:mm:ss".
[Description]
The command syntax is incorrect. "usage" is displayed.
[Corrective Action]
Check and correct the command format, and then perform the operation again.
[Description]
An argument was not specified for the option. "usage" is displayed.
[Corrective Action]
Check and correct the command format, and then perform the operation again.
[Description]
The option argument specified is too long.
option may not be displayed.
[Corrective Action]
Check and correct the option argument specified, and then perform the operation again.
[Description]
The option argument specified contains invalid characters.
[Corrective Action]
Check the option argument specified.
For operations where use of line feed characters is prohibited, check that line feed characters have not been inadvertently inserted through copy and pasting.
After checking, perform the operation again.
[Description]
The specified value is outside the allowed range.
[Corrective Action]
Check and correct the value specified and then perform the operation again.
[Description]
The format of the value specified is invalid.
[Corrective Action]
Check and correct the value specified and then perform the operation again.
[Description]
The option argument specified is invalid. "usage" is displayed.
[Corrective Action]
Specify the correct argument, and then perform the operation again.
[Description]
The file format specified for filename is incorrect.
[Corrective Action]
Check the file format.
When "activation.dat" is displayed for filename, refer to "7.2 Collecting a Cloning Image" of the "User's Guide VE" and check the file format of the license information file.
[Description]
The command is already running.
[Corrective Action]
Wait a couple of minutes and then execute the command again.
[Description]
The option argument specified is too short.
option may not be displayed.
[Corrective Action]
Check and correct the option argument specified, and then perform the operation again.
[Description]
The file specified for filename was not found.
[Corrective Action]
Check the file name specified.
[Description]
Access authority is not possessed for the file specified for filename.
[Corrective Action]
Check the owner, the owning group, and access authority of the file.
[Description]
Writing of the file specified for filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
[Description]
Reading of the file specified for filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
[Description]
Opening of the file specified for filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
[Description]
Deletion of the file specified for filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
[Description]
Renaming of the file specified for filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
[Description]
The Resource Orchestrator file filename was not found.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
When "activation.dat" is displayed for filename
Create the license information file "activation.dat" for the managed server.
For details of the license information file, refer to "7.2 Collecting a Cloning Image" of the "User's Guide VE".
When "/opt/FJSVnrmp/lan/public/rcxlanctl" is displayed for filename
When using SUSE Linux Enterprise Sever, the network parameter auto-configuration function is not supported. Perform manual public LAN settings as necessary.
When something other than the above file is displayed for filename
If the error is due to one of the following, restore the entire system, or install Resource Orchestrator again.
When the relevant files have been deleted
When the relevant files have been deleted because of system failure, or disk or file system failure
When operating managers in clusters
There is a chance that the link target of the file displayed for filename is a file on a shared disk for managers.
Mount the shared disk for managers on the node the operation was performed on.
When the cause is not one of the above, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Access to the Resource Orchestrator file filename has been denied.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Writing to the Resource Orchestrator file filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
Check that there are no programs referring to the following files and folders on the admin server:
The image file storage folder
The image file storage folder is the folder specified in "2.1.2 Installation [Windows]" of the "Installation Guide VE".
[Windows]
Installation_folder\Manager\var\control
[Linux]
/var/opt/FJSVrcvmr/control
When "activation.dat" is displayed for filename, check the following:
Check the writing authority for the license information file "activation.dat" on the managed server.
If writing authority for the license information file has not been granted, add writing authority.
For details of the license information file, refer to "7.2 Collecting a Cloning Image" of the "User's Guide VE".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Reading of the Resource Orchestrator file filename failed.
[Corrective Action]
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
[Description]
Opening of the Resource Orchestrator file filename failed.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
When this error occurred during execution of the backup command for manager resources (image file information) of the admin server, check if the system image or cloning image has been modified or deleted.
If the system image or cloning image has been modified or deleted, perform the operation again making sure not to modify or delete the image.
Check if an error message regarding the disk or file system has been output to the system log.
Check if a message indicating file system quota limit or insufficient space has been output to the system log.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Deletion of the Resource Orchestrator file filename failed.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
Check if an error message regarding the disk or file system has been output to the system log.
Check that there are no programs referring to the following files and folders on the admin server:
The image file storage folder
[Windows]
Installation_folder\Manager\var\control
[Linux]
/var/opt/FJSVrcvmr/control
[Description]
Renaming of the Resource Orchestrator file filename failed.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
Check if an error message regarding the disk or file system has been output to the system log.
Check if a message indicating file system quota limit or insufficient space has been output to the system log.
Check that there are no programs referring to the following files and folders on the admin server:
The image file storage folder
[Windows]
Installation_folder\Manager\var\control
[Linux]
/var/opt/FJSVrcvmr/control
[Description]
The specified object obj already exists.
When obj is "AuthManager", the directory service may already exist.
When this message is displayed during spare server configuration, a server including an agent may have been specified as the spare server for a primary server whose server switchover method is backup and restore.
If this message is displayed when registering the license key, obj has already been registered.
[Corrective Action]
Change the name of the object to be created, or after deleting the existing obj perform the operation again.
When obj is "AuthManager", delete the already registered directory service.
For details, refer to "5.10 rcxadm authctl" of the "Command Reference".
When this message is displayed during spare server configuration, exclude registered servers including agents from the targets of spare server configuration.
If this message is displayed when registering the license key, no corrective action is required as the specified license key has already been registered.
[Description]
The specified object name obj was not found or was deleted during processing.
If this message is displayed when a command was executed
There is a chance that the resource type of the specified object name differs from the resource type that can be specified for the command argument.
The specified object name or the resource type of the specified object name is displayed for obj.
If the file was deleted during processing, the resource type is displayed.
When a command was executed, the object name resource type is displayed as follows:
For a physical OS or VM host
server OS
For system images or cloning images, one of the following is displayed:
image
obj(image)
For a directory service
AuthManager
If displayed when server switchover is performed, no agent may be registered in the specified physical server.
[Corrective Action]
Check the existence of the displayed object, and then perform the operation again.
If this message is displayed when a command was executed
Check the resource type of the specified object and then perform the operation again.
If displayed when server switchover is performed
Register an agent on the specified physical server and then perform the operation again.
[Description]
The object obj of the type type exists.
One of the following is displayed for type:
When type is "MAC address"
An already registered server may have been inserted into another slot.
When type is "WWPN"
Specify the same WWPN value as the value which the HBA of the already registered server contains.
When type is "chassis"
The same name as an already registered server may have been specified for the chassis name.
When type is "server"
There are the following possibilities:
When the basic or registered information of the server has been changed
The same name as an already registered chassis has been specified for the server name.
When the subnet information has been registered or changed
A managed server belonging to the specified subnet already exists.
When the admin IP address of the admin server has been changed
A managed server belonging to the subnet including the specified admin IP address already exists.
[Corrective Action]
Take corrective action for the content displayed for type.
When type is "MAC address"
Either delete the registered server or return it to its original slot.
When type is "WWPN"
Change the name to a new one and perform the operation again.
When type is "chassis" or "server"
Change the name to a new one and perform the operation again.
When type is "server"
Either delete the displayed obj or change the admin IP address of obj.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
The type object was not found.
[Corrective Action]
If this message is displayed during server switchover or failback with "physical server" as the type
Perform the operation again after server switchover or failback is completed.
For cases other than the above
Check the existence of the type resource and then perform the operation again.
[Description]
Sufficient access authority is not possessed for the object obj. Processing cannot be continued.
[Corrective Action]
Check the execution authority. Some operations of Resource Orchestrator require the following levels of authority:
Privileged-user authority for Resource Orchestrator
OS administrator authority
Log in again using a user account with the appropriate authority and perform the operation again.
[Description]
User authentication failed. There are the following possibilities:
Login failed as either the user ID or the password was incorrect
Another user has deleted the logged in user or the user's authority has been changed
As settings for Single Sign-On have been performed, login failed when executing the rcxlogin command for Resource Orchestrator
Login failed due to high-load processes
When using Single Sign-On, the user has not been registered in Resource Orchestrator
[Corrective Action]
Enter the correct user ID and password, and then log in again.
Operation is not possible. Request an administrator of Resource Orchestrator to take corrective action.
When the authority of the logged in user has been changed, logging out and then logging in again deactivates menu operations that cannot be performed.
Release the settings for Single Sign-On, and perform login again.
For details, refer to "4.6 Installing and Configuring Single Sign-On" of the "Setup Guide VE".
Enter the user ID and password again, and then log in.
Check if the user is registered in Resource Orchestrator
When using Single Sign-On, register the user account not only with the directory service but also with Resource Orchestrator.
[Description]
The specified object obj was not found.
[Corrective Action]
Check the existence of the displayed object obj and parameters, and then perform the operation again.
[Description]
The option option cannot be specified.
[Corrective Action]
Check the parameter, and then perform the operation again.
[Description]
The option option must be specified.
[Corrective Action]
Check the parameter, and then perform the operation again.
[Description]
The same value was specified.
[Corrective Action]
Check and correct the value specified and then perform the operation again.
[Description]
The command cannot be executed because the object obj holds the type object.
The name of the object is displayed for obj.
One of the following is displayed for type:
For physical servers
physical server
For LAN switches
LAN switch
For VM hosts
VMHost
[Corrective Action]
Delete the type object from the object obj, and then perform the operation again.
[Description]
The number of licenses is insufficient.
[Corrective Action]
The number of licenses necessary for operation has not been registered on the manager.
Register licenses.
[Description]
The object was not found.
[Corrective Action]
Check the status of the specified obj.
[Description]
The specified object obj (type) was not found.
The name of the object that was not found is displayed for obj.
The type of the object obj is displayed for type.
[Corrective Action]
Check the parameter, and then perform the operation again.
[Description]
The command cannot be executed because the function function is not configured for the specified object obj.
"spare server" is displayed for function.
[Corrective Action]
This message will be displayed when server switching is performed in the status where the function is not set for the object obj.
Specify the managed server for which the server switchover function is set or set the function for the server, and then perform the operation again.
For settings for server switchover, refer to "Chapter 8 Server Switchover Settings" of the "User's Guide VE".
[Description]
The command cannot be executed because the status of the object obj is status.
One of the following is displayed for status:
normal
warning
unknown
stop
error
fatal
[Corrective Action]
Check the conditions necessary for operation of obj and change it to the appropriate status.
After changing the status, perform the operation again.
For details of each status, refer to "5.2 Resource Status" of the "Operation Guide VE".
[Description]
The command cannot be executed because the mode of the object obj is mode.
One of the following is displayed for mode:
active
maintenance
[Corrective Action]
Check the status of the object obj, and then perform the operation again.
[Description]
The command cannot be executed because the specified server obj is not in mode mode.
One of the following is displayed for mode:
active
maintenance
[Corrective Action]
Check the mode of the object obj, and then perform the operation again.
This message is displayed when the following operations are performed and the specified server obj is in a mode other than maintenance mode.
Backup of a system image
Restoration of a system image
Collection of a cloning image
Deployment of a cloning image
These operations can only be performed on servers that are in maintenance mode. After placing the target into maintenance mode, perform the operation again.
See
For details of operations using system images, refer to "Chapter 8 Backup and Restore" of the "Operation Guide VE".
For details of operations using cloning images, refer to "Chapter 7 Cloning [Windows/Linux]" of the "User's Guide VE".
[Description]
The type type of obj1 and obj2 is different.
One of the following is displayed for type:
boot device
server type
[Corrective Action]
Take corrective action for the content displayed for type.
"boot device"
Check the boot devices of obj1 and obj2, specify the same managed server for the boot device and perform the operation again.
"server type"
It is not possible to specify combinations of PRIMERGY BX series managed servers and managed servers of other models for obj1 and obj2. Specify the same type of servers for obj1 and obj2, and then perform the operation again.
[Description]
No managed server was found in slot_number of chassis_name.
[Corrective Action]
Check the following:
Whether there is a server in the relevant slot of the displayed chassis
Whether the information of the server in the resource details changes after the following operation is performed
The information of the server blade in the chassis may not be the newest. Update the ROR console, and execute the command again. To update the information, right-click the chassis on the ROR console server resource tree and select [Update] from the displayed menu. Updating of the information may take around 30 seconds.
[Description]
The type object is not specified.
[Corrective Action]
Specify the type object, and then perform the operation again.
[Description]
An error occurred during communication with the target target.
[Corrective Action]
Check the following items in order, resolve the cause of the problem, and perform the operation again.
If this message was displayed when executing a command and target is "Resource Orchestrator Manager", the manager may have stopped. Check "Check the communication destination" and "Port number checks" below, resolve the problem, and perform the operation again.
If this message is displayed when registering servers, resolve the problem, and register the agent again.
Network cable checks
How to Check
Check if the network cable is correctly connected between the admin server and the target server.
Corrective Action
If the network cable is damaged
Replace the cable.
If the network cable is connected incorrectly
Reconnect the cable.
Check the power status of a chassis
How to Check
Check if the chassis is powered on.
Corrective Action
Power on the chassis.
For how to check the power status and power on a chassis, refer to the manual of the server being used.
Check the settings of network devices (e.g. LAN switch) being used
How to Check
Check that the duplex mode configurations of the admin LAN composed of the following admin server and managed servers are correct.
Between the NIC of the admin server and the switch port
Between the NIC of the managed server and the switch port
Corrective Action
If the settings used for duplex mode configuration are incorrect, correct them.
For checks and setup of the admin LAN between the admin server and the managed server, refer to the manuals of the OS and network switches being used.
Check the network environment
How to Check
Execute the ping command on the server where a manager is installed to check the network status.
Check if communication with the agent is possible.
[Windows]
>ping the_IP_addresses_of_managed_servers <RETURN> |
<Example: Normal communication>
Pinging ipaddr with 32 bytes of data: |
<Example: Abnormal communication>
Pinging ipaddr with 32 bytes of data: |
[Linux]
# ping the_IP_addresses_of_managed_servers <RETURN> |
<Example: Normal communication>
PING host name (ipaddr) 56(84) bytes of data. |
<Example: Abnormal communication>
PING host name (ipaddr) 56(84) bytes of data. |
Corrective Action
Check the following items:
For <Example: Normal communication>
"Check the communication destination"
"Firewall checks"
"Port number checks"
"Certification checks"
For <Example: Abnormal communication>
"Firewall checks"
"Network cable checks"
Check the communication destination
How to Check
Check if the programs on the destination of communication are running.
For how to check, refer to "Chapter 7 Logging in to Resource Orchestrator" of the "Setup Guide VE".
Corrective Action
Restart the manager or the agent.
For how to start managers and agents, refer to "Chapter 7 Logging in to Resource Orchestrator" of the "Setup Guide VE".
Firewall checks
How to Check
Check the settings of firewall software set for the admin server and the managed server.
Corrective Action
Change the settings of the firewall to the appropriate values.
For details of the ports to set connection permission for, refer to "Appendix A Port List" of the "Setup Guide VE".
For details of checks and setup of firewalls, refer to the manual of the firewall software being used.
Port number checks
How to Check
Refer to "Appendix A Port List" of the "Setup Guide VE", and check the port numbers of the admin server or managed servers based on the following.
If port numbers are set
If the same port number or service name is being used
Corrective Action
Change the port number to the proper number.
For how to change port numbers, refer to "3.1.2 Changing Port Numbers" or "3.2.6 Changing Port Numbers" of the "User's Guide VE".
Note
If the error message "Message number 67198" is output during restoration of system images or deployment of cloning images and the settings of the port numbers of the managed server are incorrect, check if the restoration of backed up system images or deployment of collected cloning images was performed before the changing of port numbers performed in "3.1.2 Changing Port Numbers" or "3.2.6 Changing Port Numbers" of the "User's Guide VE".
If deployment or restoration was performed, perform recovery as follows:
When system images were restored
Change the port number and then restore the backed up system image.
System images which have been restored cannot be used. Delete any such images.
When cloning images were deployed
Change the port number and then deploy the collected cloning image.
Cloning images which have been deployed cannot be used. Delete any such images.
IP address checks
How to Check
Check if the IP address displayed in the error message is correct.
Corrective Action
If the IP address is incorrect, specify the correct IP address and execute the operation again.
Certification checks
For check methods and corrective actions, refer to "15.7 Cloning Issues Following Manager Re-installation" of the "Operation Guide VE".
Check the load on the network of the admin LAN
How to Check
Check the network load of the admin LAN.
The load may be high when image operations (such as backup and restoration of system images, or collection and deployment of cloning images) are being performed for other managed servers connected to the same admin LAN as the server for registration.
Corrective Action
After the process that is causing the high network load finishes, perform the operation again.
Check the password saved using the rcxlogin -save command
How to Check
Use the rcxlogin -save command to save the password, then uninstall the Resource Orchestrator manager, and check that the manager was not an original installation.
When the password has been saved, the following old folder or directory will remain. The update date will be older than the date when the manager on the admin server was installed.
[Windows]
Folder_configured_in_the_APPDATA_environment_variable_of_each_user\Systemwalker Resource Coordinator\
[Linux]
/Directory_configured_in_the_HOME_environment_variable_of_each_user/.rcx/
Corrective Action
After deleting the password information for the old manager, save the password using the rcxlogin command again, referring to "3.1.2 Uninstallation [Windows]" or "3.1.3 Uninstallation [Linux]" of the "Installation Guide VE".
When the cause is not one of the above, collect troubleshooting information and contact Fujitsu technical staff.
[Description]
Obtaining the information of the admin server failed.
[Corrective Action]
Check the following, resolve the problem, and execute the command again.
The IP address specified might be incorrect.
Check if the IP address specified is the admin server IP address.
There is a chance that the shared disk for managers is not mounted.
When operating managers in clusters, there is a chance that the link target of the file displayed for filename is a file on a shared disk for managers.
Mount the shared disk for managers on the node the operation was performed on.
[Description]
Obtaining DHCP information failed.
[Corrective Action]
Refer to "7.2 Starting and Stopping the Manager" of the "Setup Guide VE", and check whether the "Manager Services" and "Related Services" have been started on the admin server.
If any of these services has been stopped, stop the remaining services and start all of the services again. Then perform the operation in which the error occurred again.
If this does not resolve the problem, the settings of the admin server may have been changed after it was set up. Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An internal error has occurred during communication.
[Corrective Action]
Refer to the corrective action of "Message number 67192".
Information
When this message is displayed when executing the rcxadm mgrctl snap -all command
The troubleshooting information of the server in which this message is displayed will not be obtained. Log in to the target admin server or managed server then collect information by executing the rcxadm mgrctl snap or rcxadm agtctl snap command. After collecting troubleshooting information contact Fujitsu technical staff.
For details, refer to "5.1 rcxadm agtctl" or "5.7 rcxadm mgrctl" of the "Command Reference".
[Description]
A communication error occurred during execution of a manager command.
[Corrective Action]
Take corrective action for the content displayed for detail.
When detail is "(rcxfunc=rcxfunc,command=rcxcommand,rcxerrorno=rcxerrno)"
Refer to the corrective action of "Message number 67192".
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
When detail is "target=127.0.0.1"
The manager may be stopped.
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
A DB access error occurred.
[Corrective Action]
Collect troubleshooting information and contact Fujitsu technical staff.
[Description]
An error has occurred during execution of a manager command.
The details of the message are displayed for detail.
Take corrective action for the content displayed for detail.
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
When "rcxfunc=SoftRM"
When "rcxerrorno=4X"
(rcxfunc=SoftRM,command=rcxcommand,rcxerrorno=40) FJSVrcx:ERROR:68040:rcxcommand:rcxsubcommand:the cloning process terminated abnormally |
or
(rcxfunc=SoftRM,command=rcxcommand,rcxerrorno=41) FJSVrcx:ERROR:68041:rcxcommand:rcxsubcommand:error occurred during the cloning process |
or
(rcxfunc=SoftRM,command=rcxcommand,rcxerrorno=42) FJSVrcx:ERROR:68042:rcxcommand:rcxsubcommand:the cloning process timed out |
or
(rcxfunc=SoftRM,command=rcxcommand,rcxerrorno=43) FJSVrcx:ERROR:68043:rcxcommand:rcxsubcommand:some cloning processes terminated abnormally |
When "rcxerrorno=40"
When the following message is displayed just after the event log message, perform "Corrective action 5".
If it is not displayed, refer to "Corrective action 10".
FJSVrcx:ERROR:68040:rcxcommand:rcxsubcommand:the cloning process terminated abnormally |
When "rcxerrorno=41"
Check if power control operations that affect power control status and operations that affect communication with the manager are being executed simultaneously on the failed managed server.
When such operations are being executed simultaneously, wait for completion of those operations, and then perform this operation again.
When other than rcxerrorno=41
Take corrective action for the following messages which are displayed just after the event log message.
If it is not displayed, refer to "Corrective action 10".
- "Message number 61501"
- "Message number 61502"
When a message other than the above is output
For the corrective action, refer to "Corrective action 10".
The command name is displayed.
Depending on the command name output for rcxcommand, the process where the error occurred can be identified.
rcxsoftimage
An error has occurred during backup of system images or collection of cloning images
rcxsoftdeploy
An error has occurred during restoration of system images or deployment of cloning images
rcxsoftrm
An error has occurred during collection or deployment of cloning images
The subcommand name is displayed.
The IP address of the admin server is displayed.
When "rcxfunc=HBA rename"
When "rcxerrorno=2,3,104,105"
For the corrective action, refer to "Corrective action 3".
When "rcxerrorno=102"
For the corrective action, refer to "Corrective action 2".
When a message other than the above is output
Collect troubleshooting information and contact Fujitsu technical staff.
When "rcxfunc=rcxinitsnmpv3"
"agent command error"
There is a chance that a cloning image that was collected from a server other than a PRIMEQUEST server has been deployed on a PRIMEQUEST server.
Check the deployed cloning images.
When a message other than the above is output
Collect troubleshooting information and contact Fujitsu technical staff.
For "registry access error"
For the corrective action, refer to "Corrective action 4".
For "syscall="
For the corrective action, refer to "Corrective action 10".
For "code=, cmd="
When "code=1", and cmd includes "netsh.exe dhcp server add scope"
There is possibility that a network address that is not available on the Windows standard DHCP server has been specified.
For the corrective action, refer to "Corrective action 11".
When "code=1", and cmd includes "netsh.exe dhcp server scope network_address add reservedip" or "netsh.exe dhcp server scope network_address delete reservedip"
As DHCP server database access may have failed, perform the failed operation again using the following procedure.
If WWN information and server switchover and failback settings have been performed using ETERNUS SF Storage Cruiser coordination, settings of fibre channel switches or storage units may be canceled.
For "FJSVrcx:ERROR:69111:communication error. target=ETERNUS SF Storage Cruiser detail=ERROR:ssmgr8013:Unable to connect to the manager."
For the corrective action, refer to "Corrective action 6".
When "target=ESC"
For the corrective action, refer to "Corrective action 7".
When "Failed to access database for backup."
The database that stores the configuration definition information could not be accessed. The command will not be executed.
For the corrective action, refer to "Corrective action 12".
When "Failed to copy files for backup."
An error occurred as copying of files failed.
For the corrective action, refer to "Corrective action 13".
When "Failed to archive files for backup."
An error occurred as archiving of files failed.
For the corrective action, refer to "Corrective action 14".
[Corrective Action]
Check the following and take corrective action.
Check the Network Environment
Refer to the corrective action of "Message number 67192".
Check the Starting of the Manager
Check whether the manager is active. If it has stopped, start it again.
For how to start managers, refer to "7.2 Starting and Stopping the Manager" of the "Setup Guide VE".
Check the Stop of the Image Operation
Image collection, updating, deployment, or recovery might be being executed. Check the screen of the managed server and confirm that the image operation has been completed. Completion of image operation can be confirmed if the OS login window is displayed.
Recovery
If the problem is resolved by steps 1 to 3, perform step 4. of "Message number 68295".
If this does not resolve the problem, refer to "Corrective action 10".
Check the following and take corrective action.
Check the Network Environment
Refer to the corrective action of "Message number 67192".
Check the Starting of the Manager
Check whether the manager is active. If it has stopped, start it again.
For how to start managers, refer to "7.2 Starting and Stopping the Manager" of the "Setup Guide VE".
Check the Disk Space
The admin server might not have sufficient disk space available.
Check the disk space, and then execute the command again.
The admin server might not have sufficient disk space available.
Check the disk space, and then execute the command again.
Check the status of the admin server, resolve the problem and perform the operation again. Setup of the server might not be complete.
For setup, refer to "2.1 Manager Installation" of the "Installation Guide VE".
If this does not resolve the problem, refer to "Corrective action 10".
There are cases where definition of the network parameter auto-configuration function that can be defined in the cloning image definition has not been performed correctly.
Refer to "7.6 Network Parameter Auto-Configuration for Cloning Images" of the "User's Guide VE", check and correct the definition and then perform the operation again.
When not using this function, refer to "Corrective action 10".
Check the registration status of the ESC manager.
When WWN information has been configured
Refer to "Corrective action 9".
When server switchover or failback has been performed
Refer to "Corrective action 8".
When "detail=ERROR:swsagXXXX..."
Check the cause of the error, referring to the "ETERNUS SF Storage Cruiser Message Guide".
When the cause of the error is a status error of an HBA, check if the HBA WWPN value registered on ESC corresponds with the actual WWPN value.
When WWN information has been configured
Refer to "Corrective action 9".
When server switchover or failback has been performed
Confirm if an agent is registered on the spare server.
When an agent has been registered, confirm if an agent is registered for the spare server on ESC.
When an agent has been registered, delete it from ESC and refer to "Corrective action 8".
When no agent has been registered, refer to "Corrective action 8".
When no agent has been registered, refer to "Corrective action 8".
For cases other than the above
Collect troubleshooting information and contact Fujitsu technical staff.
After resolving the problem, perform the following procedures for restoration.
Perform the operation again, after restoring fibre channel switch zoning and host affinity settings on ESC using the following procedure.
Check the zoning and host affinity settings using the storageadm zone info commands.
Check if the primary server zoning and host affinity settings are in the same status as before the operation. If the status is not the same as before the operation, perform 3. to 4. If the status is the same as before the operation, perform 4.
In the status before the operation, from the ROR console check the zoning and host affinity information displayed in the "WWN Settings" on the [Resource Details] tab of the server.
Using the storageadm zone add/delete commands, restore the primary server zoning and host affinity settings to their original status.
Check if the spare server zoning and host affinity settings are in the same status as before the operation. If the status is not the same as before the operation, perform 5.
In the status before the operation, from the ROR console check the zoning and host affinity information displayed in the "WWN Settings" on the [Resource Details] tab of the server.
Using the storageadm zone add/delete commands, restore the spare server zoning and host affinity settings to their original status.
For details on how to use the storageadm zone command, refer to the "ETERNUS SF Storage Cruiser User's Guide".
After removing the cause of the error, execute the failed operation again.
Collect troubleshooting information and contact Fujitsu technical staff.
Check and correct the value specified and then perform the operation again.
Check the status of the database, resolve the cause of the access error, and then execute the command again.
If a double-byte character is specified for the -dir option of the rcxbackup command, the database access will fail.
Check the status of the destination for backup, resolve the cause of the copying error, and then execute the command again.
Check the status of the destination for backup, resolve the cause of the archiving error, and then execute the command again.
