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 or later, 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.
[Cloud Edition]
Description
Resources that match obj were not found.
When creating a physical L-Server
Failed to configure the IP address of the public LAN.
There are the following cases:
When more NICs than the physical server contains have been specified
The network (NIC) specified when creating the L-Server exceeds the number of NICs of the physical server.
When the drivers of cloning images are not the latest
When a number exceeding the number of NICs has not been specified, and the cloning image specified when creating the L-Server was Windows, the drivers of the cloning image may not be the latest.
The number displayed as the index is the same number as the detailed display of the L-Server.
When executing the rcxstorage command:
When "mirror definition" is displayed for obj
The disk matching the description of the replication definition file has not been defined in Resource Orchestrator.
(There are no disks to be recovered in failover or Disaster Recovery.)
When "disk" is displayed for obj
There are no disk resources to be processed.
When performing switchover of operating or standby storage, the disk to be processed was created in advance, and the storage unit supports switchover of operating and standby storage.
When linking a configured physical server to a physical L-Server:
When "disk" is displayed for obj
There are no disk resources to be processed.
When creating a virtual L-Server:
When obj starts with "VLANID"
The virtual network resource specified in the virtual network definition file was not found on the VM host.
When obj is "Admin LAN"
The admin LAN network resource used for communication with the installation server was not found in a resource pool accessible from the tenant.
When executing the rcxadm nsoptctl command
When obj is "PhysicalServer(name=name)"
The physical server name specified in the -server option was not found.
When obj is "PhysicalNIC(position=position)"
The physical NIC of the number position specified in the -position option cannot be found on the physical server.
When obj is "PhysicalLanSwitchPort(PhysicalNic=position)"
The LAN switch blade which links with the physical NIC of the number position specified in the -position option cannot be found.
Corrective Action
Check the conditions specified.
When creating a physical L-Server
When more NICs than the physical server contains have been specified
Check that the network (NIC) specified when creating the L-Server is smaller than the number of NICs of the physical server.
Change the network settings and perform the operation again.
When the drivers of cloning images are not the latest
Delete the created L-Server.
Update the drivers of the cloning image specified when creating the L-Server, and create the cloning image again. Create the L-Server again after specifying the re-created cloning image.
When executing the rcxstorage command:
When "mirror definition" is displayed for obj
Check that the content of the replication definition file is correct, and then execute the command again.
When "disk" is displayed for obj
Check the disk resource to be processed, and perform the command again.
When linking a configured physical server to a physical L-Server:
When "disk" is displayed for obj
Check the disk resource to be processed, and perform the command again.
When creating a virtual L-Server:
When obj starts with "VLANID"
Perform the operation again after checking the target virtual network definition file and resolving the cause of the error.
When obj is "Admin LAN"
Check the following, resolve the problem, and execute the command again.
The admin LAN network resource that can communicate with the installation server exists in a resource pool accessible from the tenant.
The network resource in step a must be the network resource for the admin LAN of the VM host
When using the rcxadm nsoptctl command
When obj is "PhysicalServer(name=name)"
Perform the operation again after checking in the resource details of the server tree that the specified physical server name is correct.
When obj is "PhysicalNIC(position=position)"
Perform the operation again after checking in the resource details of the server tree that there is a physical NIC with the specified number.
When obj is "PhysicalLanSwitchPort(PhysicalNic=position)"
Perform the operation again after checking in the resource details of the server tree that the physical NIC with the specified number is linked with the LAN switch blade.
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.
Check the access authority for the directory.
Check that there is sufficient disk area available.
Confirm the access privileges for the storage directory of the XML files for changing the network.
Check if there is sufficient disk space available in the storage directory of the XML files for changing the network.
Confirm the access privileges for the CSV configuration file.
Check if there is sufficient disk space available in the storage directory of the CSV configuration file.
Confirm that the storage directory of the CSV configuration file is specified using its full path.
Confirm that the folder name of the storage directory of the CSV configuration is a character string containing only alphanumeric characters, underscores ("_"), hyphens ("-"), and periods (".").
Confirm that the content of the avmgr_network.rcxprop definition file is correct.
Confirm that the IP address is contained in the network information of the linked virtual L-Server.
Description
An error occurred during execution of the command obj.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
The keys attribute has been specified simultaneously in the XML definition of the network resource.
In details, multiple detailed information is displayed, separated by commas (,).
In keys, multiple attribute names of the NetworkSwitchPort element (number, lag, name) are displayed, separated by "and".
For "number"
number=specified port number
For "lag"
lag=specified link aggregation name
For "name"
name=port name of the Ethernet fabric switch
Corrective Action
Review the attributes of keys and specify the correct attributes, then perform the operation again.
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 the following, and check that the memory is sufficient.
Refer to "6.1.1.8 Memory Size" in the "Overview".
Refer to "6.1.2.8 Memory Size" in the "Overview".
Description
The specified directory was not found.
Corrective Action
Specify the correct directory.
Confirm that the folder name of the storage directory of the CSV configuration is a character string containing only alphanumeric characters, underscores ("_"), hyphens ("-"), and periods (".").
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.
[Virtual Edition]
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.
[Cloud Edition]
Description
"usage" is displayed.
An argument has not been specified for an option.
A parameter has not been specified.
Corrective Action
Check and correct the command format, and then perform the operation again.
After specifying the parameter, 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.
[Virtual Edition]
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.
[Cloud Edition]
Description
The option argument specified contains invalid characters.
When this message is displayed at rcxadm config import command execution time, an illegal character is included in the definition of XML of the snapshot displayed with option.
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.
When this message is displayed at rcxadm config import command execution time, after removing the following characters of the comment tag from the definition of XML of the snapshot displayed with option, perform the operation again.
Percent("%")
Backslash("\")
Double quotation( " )
Changing line
[Virtual Edition]
Description
The specified value is outside the allowed range.
Corrective Action
Check and correct the value specified and then perform the operation again.
[Cloud Edition]
Description
The specified value is out of range.
One of the following is displayed in value:
Specified value
"XML tag(specified value, range)"
"XML key(specified value, range) server/free/remain amount of ip address/remain amount of MAC address/remain amount of WWN address"
Parameter key name(VM specific information definition file name) (specified value),range
Parameter key name(VM specific information definition file name) (specified value,range)
vlanid=specified value
L-Server NIC index= specified value
NIC No.index vlanid=specified value
The VLANID(LPVID) of the network resource connected to the NIC is not in the scope of specification.
Corrective Action
Check and correct the value specified and then perform the operation again.
When value is one of the following, perform corrective action according to the content:
"XML tag(specified value, range)"
When operating it from the command, perform the operation again after confirming the specified XML.
When operating it from the GUI, perform the operation again after confirming the specified XML.
When an "XML tag" is "Disks.Disk.DiskIndex"
When this message is displayed during increasing of disks for a virtual L-Server, the maximum value of the disk number that has been allocated to the virtual L-Server is the upper limit of the number of disks.
Increase the disks by confirming an unused disk number in the virtual L-Server, and using the command (rcxadm lserver attach). Specify an unused disk number for optional index of the command.
For the upper limit of increasing disks, refer to "Number" in "16.3.3 [Disk] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
"XML key (specified value, range) server"
Perform the operation again after checking the hardware configuration (CPU, memory) of the VM host on which the L-Server is located using the GUI.
"XML key (specified value, range) free"
Perform the operation again after checking the available resources (CPU, memory) of the VM host on which the L-Server is located, and securing sufficient resources.
"XML key(specified value, range) remain amount of ip address/remain amount of MAC address/remain amount of WWN address"
The error may be the result of one of the following:
When using a physical L-Server, the specified NIC number exceeds the upper limit of the supported number
The specified IP addresses, MAC addresses, and WWNs do not exist in the resource pool
There are no vacant addresses in the resource pools of IP addresses, MAC addresses, and WWNs
Perform the operation again after reviewing the values corresponding to the displayed IP addresses, MAC addresses, and WWNs in the L-Server XML file and correcting their definitions. Add the IP addresses, MAC addresses, and WWNs that are necessary for the resource pool.
"Parameter key name(VM specific information definition file name) (specified value),range" or "Parameter key name(VM specific information definition file name) (specified value,range)"
Review the following values, correct the definition, and then perform the operation again.
VM specific information definition file name
Specified value
Range
"vlanid=specified value"
Check the specified vlanid value, resolve the cause of the error, and then perform the operation again.
"L-Server NIC index= specified value"
Check the specified value for the NIC index of the L-Server, resolve the cause, and perform the operation again.
"NIC No.index vlanid=specified value"
Allocate a network resource with VLAN IDs of 2 - 4094 for the NICs configuring UMC.
Review the network resource to connect, and perform the operation again.
If displayed when registering the server as a managed server or registering the hardware information, correct the value defined in the server configuration information file stored in the folder below, and perform the operation again.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
[Virtual Edition]
Description
The format of the value specified is invalid.
Corrective Action
Check and correct the value specified and then perform the operation again.
[Cloud Edition]
Description
The format of the specified value, or the content of the XML specified when performing the following is not correct:
Creating an L-Platform
Creating an L-Server
Modifying an L-Server
Importing an L-Server template
Registration of iSCSI boot information
Registering disk resources for a VM guest
Changing disk resources for a VM guest
Creating tenants
Importing network configuration information
Creating network devices
Changing network devices
"Parameter key name(VM specific information definition file name, specified value, range)"
XML_tag_name
Folder XML
L-Server XML
L-Server Template XML
Network XML
User XML
UserGroup XML
Pool XML
iSCSI XML
vm-disk XML
Tenant XML
NetworkDevice XML
Link XML
Specified_value (IP address, etc.)
-duration
The URL of the FTP server for storing VCD
The user name of the FTP server for storing VCD
The password of the FTP server for storing VCD
Corrective Action
When "-duration" is displayed:
Specify a correct value or format for the option, then perform the operation again.
For details, refer to "5.13 rcxadm logctl" in the "Reference Guide (Command/XML) CE".
When "Parameter key name(VM specific information definition file name, specified value, range)" is displayed:
Perform the operation again after reviewing the value of the file name, specified value and range VM specific information definition file and correcting the definition.
In cases other than the above, correct the specified value or the content of the XML file, and then perform the operation again.
If displayed when registering the server as a managed server or registering the hardware information, correct the value defined in the server configuration information file stored in the folder below, and perform the operation again.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
For XML files, refer to "Chapter 15 XML Files" in the "Reference Guide (Command/XML) CE".
[Virtual Edition]
Description
The option argument specified is invalid. "usage" is displayed.
Corrective Action
Specify the correct argument, and then perform the operation again.
[Cloud Edition]
Description
The option argument specified is invalid. "usage" is displayed.
"Network ManagementLanSubnet" or "Network AddressSet" may be displayed for option
In these cases, both the admin LAN subnet and the public LAN subnet are specified.
Corrective Action
Take corrective action based on the content of option.
When option is "Network ManagementLanSubnet" or "Network AddressSet"
Both the admin LAN subnet and the public LAN subnet are specified.
Based on the type of network resource to be created, specify either the admin LAN subnet or the public LAN subnet.
In other cases
After specifying the correct argument, perform the operation again.
[Virtual Edition]
Description
The file format specified for filename is incorrect.
Corrective Action
Check the file format.
When "activation.dat" is displayed for filename, refer to "17.2 Collecting" in the "User's Guide VE" and check the file format of the license information file.
[Cloud Edition]
Description
The file format specified for filename is incorrect.
If "server_control.rcxprop" is displayed for filename, there is no description starting with "ServerControl," on the first line of the file.
Corrective Action
Check the file format.
Take corrective action based on the content of filename.
When "activation.dat" is displayed:
Check the format of the license information definition file referring to "7.5.3 Manual OS Installation" in the "Setup Guide CE".
When "image_admin_hyperv.rcxprop" or "image_admin_hyperv_user_group_name.rcxprop" is displayed:
Check the specified file format referring to "16.3.5 [OS] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When "server_spec.rcxprop" is displayed:
Check the format of the corresponding definition file, referring to "8.1 Definition Files Commonly Shared when Creating Virtual L-Servers" in the "Setup Guide CE".
When "server_control.rcxprop" is displayed:
Check the file format, referring to "8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE".
When the following files are displayed:
Check the format of the specified server NIC definition file referring to "15.13 Server NIC Definition" in the "Reference Guide (Command/XML) CE".
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\model\Chassis_model_name_product_name.xml
Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\host\VM_host_name.xml
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data/nicdefctl/model/Chassis_model_name_product_name.xml
/etc/opt/FJSVrcvmr/customize_data/nicdefctl/host/VM_host_name.xml
Check the following cases:
That the XML format is correct
That XML tags do not overlap, and the specified values are not exceeded
That the necessary XML tags are specified
That the NIC configuration is correct among the different physical LAN segments
That the physical LAN segment name does not overlap
When "network_device_model.xml" is displayed:
Check the file format, referring to "15.15 Network Device Model Definition" in the "Reference Guide (Command/XML) CE".
When "image_admin_citrixxen.rcxprop" or "image_admin_citrixxen_user_group_name.rcxprop" is displayed
Check the format of specified file, referring to "16.3.5 [OS] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When "server_control.rcxprop" is displayed:
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator needs to check the format of the applicable file referring to "8.8.1 Creating Definition Files" in the "Setup Guide CE".
Description
The command is already running.
Corrective Action
Wait a couple of minutes and then execute the command again.
[Cloud Edition]
Description
The command for backup and restore for manager properties of admin server is already being executed. The command is not executed.
Corrective Action
After the current command is completed, execute the command again when necessary.
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
[Virtual Edition]
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
[Cloud Edition]
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
When "server_spec.rcxprop", "storage_portset.rcxprop" or "storage_mirroring.rcxprop" is displayed for filename:
Check that reading of the file is allowed.
When "storage_portset.rcxprop" is displayed for filename
Check that reading of the file is allowed.
When "FC_connection_pattern_filename.rcxprop" is displayed for filename
Check that reading of the file is allowed.
When "GUIRunOnce_command_definition_file" is displayed for filename
Check that reading of the file is allowed.
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
[Virtual Edition] [Cloud Edition]
Description
The target file for the operation does not exist.
Corrective Action
When file is "avmgr_network.rcxprop"
Check if avmgr_network.rcxprop exists. If it does not exist, create it.
For details on avmgr_network.rcxprop, refer to "2.5.5 Definition File for Configuring the Business and Quarantine Networks" in the "Automatic Quarantining Function User's Guide".
[Virtual Edition]
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 "17.2 Collecting" in 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 "cacerts" is displayed for filename
Files of Resource Orchestrator or external software were not found.
Collect troubleshooting information and contact Fujitsu technical staff.
In other cases
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.
[Cloud Edition]
Description
The process was canceled as the target file was not found.
Corrective Action
When executing the rcxchkmismatch command and filename is "fullbackup_info.xml"
Perform the following corrective actions and then continue restoring the admin server:
There is an error in the directory name of the L-Server restoration log storage directory specified for the argument of the -logdir option.
Specify a correct directory name for the argument of the -logdir option, and then execute the rcxchkmismatch command again.
The rcxreserveid command has not been executed.
Perform the operation for restoring the admin server again, from execution of the rcxreserveid command.
When executing reflection of server NIC definition (rcxadm nicdefctl commit)
There are no folders or files of Resource Orchestrator.
Collect the relevant message and troubleshooting data, and contact Fujitsu technical staff.
When filename is "storage_portset.rcxprop"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should create the definition file, referring to "7.1.1 Creating Definition Files Combining Ports of SAN Storage" in the "Setup Guide CE".
When file_name is "fc_connection_pattern_filename.rcxprop"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should create the definition file referring to "7.1.7 Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
When "cacerts" is displayed for filename
Files of Resource Orchestrator or external software were not found.
Collect troubleshooting information and contact Fujitsu technical staff.
When filename is "cfabric_portprofile_networkresource.rcxprop"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should create the definition file, referring to "9.4.8.4 When Using Port Profile Configuration Files" in the "Design Guide CE".
Information
When automatic configuration of network resources is "Network auto=false", port profiles are not automatically created.
When filename is "ovm_sparc_install_server.rcxprop"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator needs to create a definition file referring to "8.8.1 Creating Definition Files" in the "Setup Guide CE".
When filename is "os_setting.rcxprop" or "os_setting_user_group_name.rcxprop"
Active Directory domain participation is enabled in the L-Server template, but the OS setting property file does not exist is inaccessible. Check that the OS setting property file exists, and is accessible.
When filename is "customize_data/sysprep_guirunonce/GUIRunOnce_command_definition_file.rcxprop" or "customize_data\sysprep_guirunonce\GUIRunOnce_command_definition_file.rcxprop"
The GUIRunOnce command definition file is specified in the L-Server template, but the specified GUIRunOnce command definition file does not exist or is inaccessible. Check that the file exists, and is accessible.
When message is output by rcxnetworkservice
Specify a file as the target of operation, and perform the operation again.
When filename is "vdi_management_info.rcxprop"
Check if a file exists in the following folder:
Installation_folder\SVROR\Manager\etc\customize_data |
When a file exists in the folder, notify the infrastructure administrator of the information in this message.
The infrastructure administrator should then ensure that the file is accessible.
For details on files, refer to "2.3.5.1 Modification of the Coordination Method with VDI Management Server" in the "Release Notes".
When there are no files, no action is necessary.
In other cases
Specify a file as the target of operation, and perform the operation again.
[Virtual Edition]
Description
Access to the Resource Orchestrator file filename has been denied.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
One of the following is displayed in filename:
Resource Name
No permission has been granted for the specified resource.
File Name
Access to the Resource Orchestrator file filename has been denied.
Corrective Action
Take corrective action based on the content of filename.
Resource Name
Perform the operation as a user with permission for the specified resource.
File Name
Collect this message and troubleshooting data, 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.1.6 Installation" in the "Setup Guide VE".
[Windows Manager]
Installation_folder\SVROR\Manager\var\control
[Linux Manager]
/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 the following:
For Virtual Edition, refer to "17.2 Collecting" in the "User's Guide VE".
For Cloud Edition, refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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
Reading 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.
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 the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, 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 Manager]
Installation_folder\SVROR\Manager\var\control
[Linux Manager]
/var/opt/FJSVrcvmr/control
Check if there are any programs referring to the specified CSV results file or its storage folder
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 Manager]
Installation_folder\SVROR\Manager\var\control
[Linux Manager]
/var/opt/FJSVrcvmr/control
[Virtual Edition] [Cloud Edition]
Description
The specified object obj already exists.
When obj is "Antivirus software"
An antivirus software resource with the same name already exists.
When obj is an IP address or an FQDN
If this message is displayed during operation of information for sub manager coordination, manager information already exists.
Corrective Action
Change the name of the object to be created, or delete the existing obj and then perform the operation again.
In any other cases, take corrective action based on the content of obj.
When obj is "Antivirus software"
Either change the resource name of the antivirus software resource to register or delete the already registered antivirus software, and then perform the operation again.
When obj is an IP address or an FQDN
If this message is displayed when operating information for sub manager coordination, change the IP address or FQDN if necessary, and then perform the operation again.
[Virtual Edition]
Description
The specified object obj already exists.
When obj is "AuthManager", the directory service may already exist.
When this message is displayed when configuring a spare server, a server with an agent registered may have been specified as a spare server of a primary server for which the server switchover method is backup and restore.
If this message is displayed when registering the license key, obj has already been registered.
When obj is "IP address-IP address", the DHCP range of the obj may already exist in the OS standard DHCP Service.
When this message is displayed during setting of public LAN (MAC address) information, public LAN (MAC address) information with the same NIC number has been already registered.
When obj is "MAC_address", the MAC address displayed in obj may already exist in the DHCP service.
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.3 rcxadm authctl" in the "Reference Guide (Command) VE".
If this message is displayed when a spare server is configured, exclude the server with an agent registered from the configuration target of the spare server.
If this message is displayed when registering the license key, no corrective action is required as the specified license key has already been registered.
When obj is "IP address-IP address", delete the DHCP range of the obj from the OS standard DHCP Service, and retry the operation.
If trying the operation again is not necessary, perform the following restoration procedure.
Stop the OS standard DHCP Service and disable the automatic startup of the service.
If the manager's "Related Services" have been stopped, start the manager.
For details about how to confirm the service status or start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
When this message is displayed during setting of public LAN (MAC address) information, check the public LAN (MAC address) information, change the MAC address or NIC number, and then perform the operation again.
If this message is displayed during server switchover of a server managed using VIOM or ISM and obj is "MAC_address", that MAC address may have been specified as the virtual MAC address of the server when it was registered in Resource Orchestrator.
Perform the following procedure to change the virtual MAC address to the physical MAC address.
Right-click the target server and select [Hardware Maintenance] - [Reconfigure] in the displayed menu.
Change the virtual MAC address in the displayed dialog to the physical MAC address.
[Cloud Edition]
Description
The specified object obj already exists.
One of the following is displayed for obj:
When obj is "AuthManager"
Directory services may already exist.
When this message is displayed when configuring a spare server, a server with an agent registered may have been specified as a spare server of a primary server for which the server switchover method is backup and restore.
When obj is "IP address-IP address", the DHCP range of the obj may already exist in the OS standard DHCP Service.
When obj is "vnet"
A network resource with the same VLANID has already been created.
When obj is "network_resource_name"
A network resource with the same name already exists.
When obj is "vm-disk-storagemgr"
A storage management software with the same name already exists.
When obj is "vm-disk-vstorage"
A virtual storage resource with the same name already exists.
When obj is "disk resource name defined in XML"
A disk resource with the same name already exists.
When obj is "VmHost (ip=IP address of the VM host defined in XML).Disks.Disk(path=Device path to the disk resource defined in XML)"
A disk resource for VM guests which has the same device path already exists on the specified VM host.
When obj is "VDI management software"
VDI management software with the same name already exists.
The FTP server for storing VCD
If this message is displayed when executing the rcxadm config import command, change the name of the object to import, or either delete or rename obj, and then perform the operation again.
Corrective Action
Either change the name of the object to import, or delete the existing obj, and then perform the operation again.
In any other cases, take corrective action based on the content of obj.
When obj is "AuthManager"
Delete registered directory services.
For details, refer to "5.4 rcxadm authctl" in the "Reference Guide (Command/XML) CE".
If this message is displayed when a spare server is configured, exclude the server with an agent registered from the configuration target of the spare server.
When obj is "IP address-IP address", delete the DHCP range of the obj from the OS standard DHCP Service, and retry the operation.
If trying the operation again is not necessary, perform the following restoration procedure.
Stop the OS standard DHCP Service and disable the automatic startup of the service.
If the manager's "Related Services" have been stopped, start the manager.
For details about how to confirm the service status or start the manager, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
When obj is "vnet"
Either specify a different VLAN ID, or delete the existing network resource, and then perform the operation again.
Use a unique VLAN ID of the network resource for each VFAB, when linking VFABs and tenants in Converged Fabric.
When obj is "network_resource_name"
Change the network resource name, and perform the operation again.
When obj is "vm-disk-storagemgr"
The name of storage management software, "vm-disk-storagemgr" is reserved as the name to register disk resources for VM guests. Delete or rename already registered storage management software, and then perform the operation again.
When obj is "vm-disk-vstorage"
The name of virtual storage resource, "vm-disk-vstorage" is reserved as the name to register disk resources for VM guests. Delete a virtual storage resource, or change the name of the resource that is already registered, and perform the operation again.
When obj is "disk resource name defined in XML"
Either change the name of the disk resource for the VM guest to register, or delete or rename obj, and then perform the operation again.
When obj is "VmHost (ip=IP address of the VM host defined in XML).Disks.Disk(path=Device path to the disk resource defined in XML)"
Either change the device path to register, or delete or rename obj, and then perform the operation again.
When obj is "VDI management software"
Change the name of the object to be created, or delete the existing obj and then perform the operation again.
The FTP server for storing VCD
Unregister the existing FTP server using rcxadm vcdsrvctl unregister, then perform the operation again.
[Virtual Edition] [Cloud Edition]
Description
After checking the following for the displayed object, perform the operation again.
That the object exists
That the object was not deleted during deletion processing
If this error is displayed when a command is executed, check the following.
Corrective Action
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.
Check the resource type of the specified object and then perform the operation again.
The name of the specified object is displayed for obj.
The object name is displayed as follows.
When operating information for sub manager coordination
An IP address or an FQDN
When the object is an antivirus software
The resource name of the target antivirus software
Specify the VM name correctly using the full path in the CSV configuration file.
Check if the specified folder exists. If it does not exist, create it.
Check that the VM host is registered in the specified VM pool.
Check that the VM guest exists on the VM host.
In addition, check that the host name displayed for "DNS Name" in the corresponding virtual PC summary information in the VM management software matches the VM name configured in the CSV configuration file. If the names do not match, execute the rcxadm lserver convert command to link the virtual PC to a virtual L-Server.
For details, refer to "B.1 When Linking of Virtual PCs with Virtual L-Servers Fails" in the "Automatic Quarantining Function User's Guide".
Execute the rcxadm lserver convert command to link this virtual PC to a virtual L-Server.
For details, refer to "B.1 When Linking of Virtual PCs with Virtual L-Servers Fails" in the "Automatic Quarantining Function User's Guide".
Environments in which virtual L-Servers with the same name exist in different folders are not supported.
Change the name of the virtual L-Server and ensure that there are no other virtual L-Servers with the same name.
[Virtual Edition]
Description
The specified object name obj was not found or was deleted during processing.
Check the existence of the displayed object, and then perform the operation again.
Corrective Action
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.
Check the resource type of the specified object and then perform the operation again.
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
There may be no agent registered in the specified physical server.
Register an agent on the specified physical server and then perform the operation again.
[Cloud Edition]
Description
After checking the following for the displayed object, perform the operation again.
That the object exists
That the object was not deleted during deletion processing
That the object meets the conditions
That the object that met the conditions was not deleted during deletion processing
The specified object exists, but the pool where the object is registered has been selected as a global pool of the tenant
That the specified object exists and is included in the access scope of the user group or user that performed the operation
Creation of an L-Server from the ROR console, specifying values in the definition file. The values are larger than the actual number of CPUs and CPU clock speed of a server for which server management software is not used
Registration of a network device for which the registration status is not "already registered" in the network pool is not being attempted
If this error is displayed when a command is executed, check the following:
When the following values are displayed for obj, take the following corrective action based on the content.
When obj starts with "link aggregation(switch=switch,lag=labname)"
When obj is "resource id=ID", "image id=ID", or "Folder id=ID"
When obj is "SimpleTask" and the rcxadm vmhostctl commit is executed
When obj is "VM host name", "virtual storage name", or "resource pool name"
When obj is one of the following:
server OS
VM_host
VM Guest
VM guest name
When obj starts with one of the following values:
TargetServer id=Virtual_machine_ID
PhysicalServer id=Physical_server_ID
When obj starts with one of the following values:
VirtualNetwork
VirtualLanSwitch
When obj starts with one of the following values:
VmGuestStorage(device_name)
VirtualNic(LNic index=NIC_index)
VirtualNic(LNic mac_address=MAC_address)
When obj starts with one of the following values:
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
Corrective Action
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.
Check the resource type of the specified object and then perform the operation again.
The specified object name or the resource type of the specified object name is displayed in obj.
If the object has been deleted during the process, the resource type is displayed.
One of the following is displayed for the resource type of the object name:
When the resource type is "virtual_storage", there is a chance that there is not enough available space on the virtual storage resource.
For a physical OS or VM host
server OS
vm_host
VM host name
For VM guests
VM Guest
VM guest name
For VM management software
VM management software name
For system images and cloning images
image
obj(image)
For shared libraries
library share
For directory service
AuthManager
When the object is an antivirus software
The resource name of the target antivirus software
When the following values are displayed for obj, take the following corrective action based on the content.
The operation has failed because a directory service is not registered.
Perform the operation again after registering a directory service.
An admin LAN subnet or a network resource for the admin LAN was registered before applying the Cloud Edition license.
Delete the admin LAN subnet or the network resource for the admin LAN which was registered before applying the Cloud Edition license. Then, register the admin LAN subnet or the network resource for the admin LAN again.
A request to collect a difference backup was made in the state where a base backup has not been collected.
Collect a base backup, and then repeat the operation.
The definition of NIC that sets the DNS server L-Server is not found. Check whether the NIC for X exists, review the NIC definition on DNS server, and then perform the operation again.
The operation failed because the target resource folder was not specified when a user with multiple access scopes performed an operation.
Creation of an L-Server, with no target resource folder name set
When creating an L-Server, specify the name of the resource folder where the L-Server will be created in the XML file for the L-Server.
For details on resource folder names, refer to the following information:
"Example Creating an L-Server in a resource folder or a tenant" in "15.3.1 Definition Information for Physical L-Servers (XML)" in the "Reference Guide (Command/XML) CE"
"Example Creating an L-Server in a resource folder or a tenant" in "15.3.2 Definition Information for Virtual L-Servers (XML)" in the "Reference Guide (Command/XML) CE"
Creation of a tenant, resource folder, or resource pool, without specifying the name using the hierarchy
When creating tenants, resource folders, or resource pools, specify the name using the folder hierarchy, including the destination resource folder name.
For details on resource folder names, refer to the following information:
"3.10 rcxadm pool" in the "Reference Guide (Command/XML) CE"
"3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE"
"15.8 Resource Folders" in the "Reference Guide (Command/XML) CE"
"15.12 Tenants" in the "Reference Guide (Command/XML) CE"
Moving of a tenant, resource folder, or resource pool, without specifying the -to option for the destination
When moving a tenant, a resource folder, or a resource pool, specify the destination resource folder.
For details on destination resource folders, refer to the following information:
"3.10 rcxadm pool" in the "Reference Guide (Command/XML) CE"
"3.5 rcxadm folder" in the "Reference Guide (Command/XML) CE"
"3.14 rcxadm tenant" in the "Reference Guide (Command/XML) CE"
There is an error in the storage destination specified for the cloning image.
Check if the specified shared library is available.
The operation failed because the ports that make up the lagname link aggregation of the switch LAN switch blade are in the following state.
A link aggregation configuration port does not exist.
The port of the link aggregation configuration has not been recognized by this product.
A member port does not exist in the link aggregation configuration.
The LLDP of the link aggregation configuration port is not valid.
An internal port has not been specified for the member port of the link aggregation configuration.
Review the lagname link aggregation configuration of switch LAN switch blade, then make the correct settings. After this, click the switch LAN switch blade [Update] button in the ROR console to have it recognized by this product.
Refer to "9.4.4 When Using Link Aggregation" in the "Design Guide CE" for information on the settings.
There is no target L-Server for the power operation.
Check the status of the L-Server and whether the L-Server exists in the resource folder.
Power operations of an L-Platform have been performed as the infrastructure administrator (infra_admin) or the infrastructure operator (infra_operator).
Power operations of an L-Platform cannot be performed as the infrastructure administrator (infra_admin) or the infrastructure operator (infra_operator).
For details on the roles which can perform power operations for an L-Platform, refer to "5.1.2 Roles and Available Operations" in the "Design Guide CE".
There is no target L-Platform for the operation.
After checking the existence of the specified L-Platform, perform the operation again.
There is no target L-Server template for the operation.
After checking the existence of the specified L-Server template, perform the operation again.
There is no resource including a MAC address described in the XML file used to import Disaster Recovery.
There are no address set resources that include a MAC address.
Check whether there is an address set that includes a MAC address, and then retry.
There is no resource including a global IP address described in the XML file used to import Disaster Recovery.
There are no address set resources that include a global IP address.
Check whether there is an address set that includes a global IP address, and then try the operation again.
Operations fail, since the specified NIC is not on a server in the physical LAN segment.
Check the server NIC definition.
Automatic network configuration failed, since there is no host for the target of the automatic network configuration.
When message 22705 or 41502 is output in the event log, refer to the details of the relevant message.
The physical LAN segment specified using network resource physical LAN segment is not registered in the server NIC definition. Confirm the server NIC definition and the physical LAN segment of the network resources, and perform the operation again.
The LAN switch blade that links with the physical NIC of the position option cannot be found.
Check the resource details of the server tree that the physical NIC with the specified number is linked with the LAN switch blade.
The cause is one of the following:
The port profile configured by Resource Orchestrator was not found.
The port profile corresponding to the network resource name defined in the definition file for linking the network resource and port profile (cfabric_portprofile_networkresource.rcxprop) was not found.
Notify the infrastructure administrator of the information in this message.
When automatic configuration of network resources is "Network auto=false"
Port profiles are not created automatically.
The infrastructure administrator should create the definition file, referring to "9.4.8.4 When Using Port Profile Configuration Files" in the "Design Guide CE".
When automatic configuration of network resources is "Network auto=true"
Manually create a port profile for the Ethernet Fabric switch and then create or modify the L-Server again.
The network device for fw_device_name is not registered in the network pool of the tenant for name.
Check if the network device for fw_device_name is registered in the network pool of the tenant for name.
When the network device is not registered, check if fw_device_name is registered in the server tree using a different name, and perform the import operation again.
When the network device to use cannot be registered, delete the name L-Platform following the procedure in "4.2 Switchover between Sites Using the Disaster Recovery Function" in the "DR Option Instruction".
The procedure described in "NetApp FAS Storage Configuration" in "D.3.4 When Using NetApp FAS Storage" in the "Design Guide CE" may not have been performed.
Check the storage unit configuration referring to "NetApp FAS Storage Configuration" in "D.3.4 When Using NetApp FAS Storage" in the "Design Guide CE".
The resource to be registered with or canceled from the resource pool, or the resource pool, was not found. Check that the resource or the resource pool exists, and then perform the operation again.
The resource corresponding to ID may have been deleted or migrated.
Check that resources have not been deleted or migrated by other users.
When the resource has been deleted
Re-create or re-register the resource, and perform the operation again.
When the resource has been migrated
Migrate the resource to its original location, and perform the operation again.
There is no disk resource matching the specified size registered in the storage pool.
Or, since disks are divided into multiple storage pools, a disk resource cannot be identified.
Check whether or not an unused disk resource larger than size=%1(GB) has been registered in the storage pool, then perform the operation again.
In condition, %1 is displayed.
size=%1
When a disk resource which can be used by one VM host is divided and registered in multiple storage pools, specify a storage pool as "Resource type", then perform the operation again.
There is no empty address in the address set resource (MAC address) or the address set resource (MAC address) does not exist.
Perform the appropriate corrective action for each condition. In condition, one of the following is displayed:
free address
Perform the operation again, after checking if there are vacant addresses in the address set resources (MAC addresses).
resource
There are no address set resources (MAC addresses). Perform the operation again, after registering the address set resources (MAC addresses) in accessible address pools.
There is a possibility the disk capacity of the selected virtual storage resource is insufficient or the virtual storage resource that can be selected does not actually exist.
There is a chance that there is not enough available disk space on the selected virtual storage.
Check the value of available space indicated by size=%1 (GB), and perform the operation again.
In condition, one of the following is displayed:
size=%1, vm_host=%2
size=%1, vm_host=%2, pool=%3
size=%1, vm_host=%2, virtual_storage=%3
When using RHEL5-Xen as server virtualization software, the contents of the storage connection definition file may be incorrect.
Review the settings in the storage connection definition file.
For details, refer to "8.4 RHEL5-Xen" in the "Setup Guide CE".
When using OVM for x86 3.x as server virtualization software, the system disk for the specified image(template) may not have been configured correctly.
For details, refer to the note in "14.7.1 Virtual Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
A line which does not include definitions of amount_of_memory_capacity and amount_of_cpu_capacity exists in the definition file.
Please remove the line or modify it to a comment line.
For details, refer to "Definition File that Configures Resource Sizes to Secure for VM Hosts [KVM]" in "8.6.1 Creating Definition Files" in the "Setup Guide CE".
There are no FTP servers registered for the guest OS customization function.
Register an FTP server for the guest OS customization.
For details on registration, refer to "3.18 rcxadm vcdsrvctl" in the "Reference Guide (Command/XML) CE".
There is no virtual storage resource which can create a disk resource with the same capacity as in disk_size in the VM host in vmhost_name, or in pool_name in the resource pool.
Check the following about the virtual storage resource:
If free space is sufficient
If a virtual storage resource that accessible by the VM host is registered in the resource pool
If a libvirt storage pool corresponding to the virtual storage resource is configured in the VM host
The operation failed because a system disk was not specified during physical L-Server creation.
Confirm that a system disk (DiskIndex 0) is defined and perform the operation again.
The object specified when an L-Server was created does not exist or is out of the access scope of the user.
For L-Servers for which only configuration definition has been created, even if "Automatic" is displayed for the resource to be used, previous resource settings are retained.
If this message is displayed when starting the L-Server with configuration only, for which "Automatic" is set for the resource to use, perform the following operation based on the content of obj, then perform the operation again.
When obj is "VM host name" or "VM pool name"
In the [Modify L-Server's definition] dialog, configure "VM host to use" again.
When obj is "virtual storage name" or "storage pool name"
From disk definitions in the [Modify L-Server's definition] dialog, configure "Resource type" again.
server OS
VM_host
VM Guest
VM guest name
The following causes are possible:
A VM guest used on the L-Server has been deleted from server virtualization software
During L-Server deletion, system failure of the VM management software server or VM management software has occurred
During L-Server deletion, system failure of admin server or manager occurs
A VM guest used on the L-Server has been moved from server virtualization software to a VM host which is unregistered in VM pool
When using Solaris Zones, OS re-installation in the non-global zone or modification of the global zone in which the non-global zone starts has been performed.
Check that the admin server, manager, VM management software server, or VM management software have been started, and perform the relevant operation.
For a.:
Delete the L-Server.
For b. or c.:
Delete the L-Server again.
For d.:
Migrate VM guests being used on the L-Server to VM hosts that are already registered in the VM pool.
In case of e
Refer to "8.7.10 Advisory Notes for Solaris Zone Usage" in the "Setup Guide CE", and then take corrective action.
TargetServer id=Virtual_machine_ID
PhysicalServer id=Physical_server_ID
The folder where the L-Server was created is different to the location of the VM host where the virtual machine has been built or to the resource pool to which the physical server belongs.
Check that the VM host, or the resource pool and the destination folder for L-Server creation belong to the same tenant. This assumes that there is a configured virtual machine on the VM host, and a physical server belongs to the resource pool.
When the destination folder for L-Server creation does not belong to the same tenant as that of the resource pool, change the value of "Destination folder" (use the -to option for the command operation) to make them belong to the same tenant, and then perform the operation again.
When a resource pool does not belong to a tenant, specify a folder not contained in a tenant as the destination for L-Server creation.
VirtualNetwork
When the target server is VMware, the virtual network indicates a port group on the virtual switch.
VirtualLanSwitch
When the target server is Hyper-V, virtual switch indicates the virtual network of Hyper-V.
The operation has failed because there is no virtual network or virtual switch on the target server of L-Server creation.
Perform the operation again after creating a virtual network or a virtual switch on the target server of L-Server creation.
For details on conditions for automatic creation of virtual networks or virtual switches, refer to "2.2.7 Simplifying Networks" in the "Design Guide CE".
VmGuestStorage(device_name)
VirtualNic(LNic index=NIC_index)
VirtualNic(LNic mac_address=MAC_address)
A virtual disk that has a device_name path, a network with one more index than the NIC, or a network with a MAC address cannot be found in the VM guest allocated to the L-Server.
Check whether one of the items listed exist on the VM guest allocated to the L-Server: virtual disks that contain the path for device_name, networks that have one more network resource than NIC_index, or networks that have MAC_address.
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
The operation has failed because there is no internal resource table.
Wait for a short while and then repeat the operation.
When displayed during L-Server creation
Check that the VM management software specified when registering the VDI management server/VDI management software, and the VM management software linked with the VM host that is in the destination of virtual L-Server creation, are the same.
If they are not the same, modify the VDI management server/VDI management software, and configure the same software.
If the VDI management server/VDI management software is not registered, register it.
In other cases
When the VDI management server/VDI management software with the specified name cannot be found. Check if the VDI management server/VDI management software is registered.
If the VDI management server/VDI management software is not registered, register it.
The target of VDI management software was not found.
After checking that the specified VDI management software is registered with Resource Orchestrator, perform the operation again.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in obj, refer to "Troubleshooting".
When the problem is still not resolved, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
Description
The object obj of the type type exists.
Take corrective action for the content displayed for type.
Corrective Action
An already registered server may have been inserted into another slot.
Either delete the registered server or return it to its original slot.
Specify the same WWPN or WWNN value as the value which the HBA of the already registered server contains.
Change the value to another WWPN value or WWNN value and perform the operation again.
The specified agent is already registered.
When the specified agent is displayed in obj, corrective action is not necessary.
The specified LAN switch is already registered.
When the specified LAN switch is displayed in obj, corrective action is not necessary.
When the SNMP community name is displayed in obj
The combination of the IP address and the SNMP community name of the communication destination of the SNMP trap that show the event details of Resource Orchestrator are already registered.
No action is necessary.
The same name as an already registered server may have been specified for the chassis name.
Change the name to a new one and perform the operation again.
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.
The MAC Address may be the same as one of an already registered server.
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.
Either delete the displayed obj or change the admin IP address of obj.
When performing server switchover of rack mount servers or tower servers that are managed using VIOM or ISM
The MAC address specified when registering the server may be the virtual MAC Address.
Right-click the target server and select [Hardware Maintenance] - [Reconfigure] in the displayed menu. Then change the MAC address specified in the displayed dialog to the physical MAC address.
When the server management software for obj is BladeLogic
There is only one server management software that can be registered. No corrective action is necessary.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Cloud Edition]
Description
The object obj of the type type exists.
Take corrective action for the content displayed for type.
Corrective Action
obj has already been registered in a resource pool.
Perform the operation again after releasing registration of obj from the resource pool.
obj has already been registered in a resource pool.
Check the resource pool of obj, and create it again if necessary.
When physical L-Servers were created, or network resource settings were changed, the IP addresses of the admin LANs, which are used by the physical L-Servers and the managed servers that are registered in the server tree, will overlap.
When physical L-Servers were created, or network resource settings were changed, change the IP address of the admin LAN used by the managed servers that are registered on physical L-Servers or the server tree, then perform the operation again.
The IP address of obj is overlapping with the IP address of the admin LAN used by the L-Servers and the managed servers.
For the admin LAN IP address, specify an IP address not used by another resource, or change the IP address of the resource that is currently overlapping, and then perform the operation again.
The IP address obj of the public LAN specified during creation of the physical L-Server is already in use.
For the created physical L-Server, manually set the public LAN IP address, or review the network configuration after deleting the physical L-Server, and then perform the operation again.
The IQN name in obj is already in use.
Perform the operation again after correcting the specified IQN name.
The IP address in obj is already in use.
Perform the operation again after correcting the specified IP address.
The role name specified when creating roles has already been used.
The role name specified as the new role name during role configuration modification is already being used.
As the basic role name specified during role restoration exists, restoration cannot be performed.
Check if the role name exists in the list of the roles, and perform the operation again.
For details on the list of roles, refer to "12.1 rcxadm role" in the "Reference Guide (Command/XML) CE".
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.
[Virtual Edition]
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.
[Cloud Edition]
Description
A user who does not have sufficient privileges executed the command. The command is not executed.
Corrective Action
Execute the command again, with sufficient privileges.
When obj is a virtual L-Server name and cold migration is performed on a powered on virtual L-Server
Log in using a dual-role administrator account and perform cold migration of the virtual L-Server.
Description
User authentication failed.
[Cloud Edition]
When this message is output during operations for the VM host, the VM guest or the virtual L-Server, authentication with the VM host may have failed.
Corrective Action
The following might apply:
Enter the correct user ID and password, and then log in again.
When a user is logged in to ServerView Operations Manager using another web browser, there is the possibility that the user of ServerView Operations Manager is not registered in Resource Orchestrator.
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.
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.
Enter the user ID and password again, and then log in.
[Virtual Edition]
Release the settings for Single Sign-On, and perform login again.
For details, refer to "Chapter 10 Configuring Single Sign-On" in the "Design Guide VE".
[Cloud Edition]
Check if authentication is possible using the account specified when registering the VM host.
Check the operating status and network settings of the VM host.
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.
[Virtual Edition]
Description
The option option cannot be specified.
Corrective Action
Check the parameter, and then perform the operation again.
[Cloud Edition]
Description
When option is "Pool"
The Pool element cannot be specified in the XML file.
When option is something other than "Pool"
The option option cannot be specified.
Corrective Action
When option is "Pool"
Confirm that there is no Pool element in the XML file and perform the operation again.
When option is "SNMP Community" or "MAC address" and the operation being performed is registration of a server
Perform one of the following corrective actions:
Do not specify the SNMP community or MAC address information for the admin LAN.
Change the settings in the definition file described in "8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE", and then specify the server as a server that can use agents.
When option is something other than the above
Check the parameter, and then perform the operation again.
[Virtual Edition]
Description
The option option must be specified.
Corrective Action
Check the parameter, and then perform the operation again.
[Cloud Edition]
Description
option must be specified. "usage" is displayed.
Corrective Action
Check the parameter, and then perform the operation again.
Take corrective action based on the content of option.
"name"
Specify an appropriate resource name such as an L-Server name or resource name for the -name option, and perform the operation again.
"NICGroups.NICGroup.NICLinks"
Check that the NICLink tag appears twice in the XML file specified in creation or modification of the L-Server.
"-allow deldisk or -deny deldisk"
When the disk cut out from virtual storage is reduced from L-Server, the specification of either option of allow deldisk or -deny deldisk is required.
Specify -allow deldisk or either of -deny deldisk option, and perform the operation again.
"custom"
Specify "true" or "false" for the -attr custom option, and perform the operation again.
"custom=true"
When the -attr systemtype option is specified, It is necessary to specify "true" for the -attr custom.
Specify "true" for the -attr custom option, and perform the operation again.
"systemtype"
The systemtype attribute was not specified when executing "rcxadm image create" on a Windows guest.
Specify "32bit" or "64bit" for the -attr systemtype option, and perform the operation again.
"define"
Specify -define option, and perform the operation again.
Description
The same value was specified.
Corrective Action
Check and correct the value specified and then perform the operation again.
[Virtual Edition]
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.
[Cloud Edition]
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" is displayed.
When this message is output while deleting an admin LAN network resource related to the admin LAN subnet, the admin IP address of the managed server is included in the subnet scope of the specified resources.
For LAN switches
"LAN switch" is displayed.
For VM Hosts
"VMHost" is displayed.
For Virtual Disks
"disk" is displayed.
For Virtual Storage
"vstorage" is displayed.
Corrective Action
Delete the type object from the object obj, and then perform the operation again.
Take corrective action based on the content of type.
When type is "physical server"
After checking the admin IP address of the managed server on the server tree, delete all managed servers with admin IP addresses included in the subnet scope of the specified resources.
When type is "disk"
Delete the L-Server using the disk resource created from the virtual storage resource displayed in obj.
"vstorage"
Delete the L-Server using the virtual storage resource created under the physical storage unit resource displayed in obj.
[Cloud Edition]
Description
There is no disk in the VM guest specified for cloning image collection.
If you omit specifying the storage location when collecting a cloning image for a VM guest, it will be stored in the same location as the disk of the VM guest, but in this case, the storage location could not be determined because the VM guest does not have a disk.
Corrective Action
Perform the operation again after specifying the location to store the cloning image.
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.
[Cloud Edition]
Description
The xml element specified in the filename file or the xml element of the filename resource specified using the command was not found in targetfile.
filename
Specified mapping file or resource name.
targetfile
File to be converted.
xpath
xpath path of the element in the filename file.
Corrective Action
Correct the element definitions in the filename file, and execute the command again.
Or, check the resource name specified in the command and re-execute the command.
[Cloud Edition]
Description
The attribute name of the element specified in the filename file or the attribute name of the filename resource specified in the command cannot be found in the targetfile file. The value could not be changed to the one specified in value because of this.
filename
Specified mapping file or resource name.
targetfile
File to be converted.
xpath
xpath path of the element in the filename file.
name
Attribute name of the element in the filename file.
value
Attribute value of the element in the filename file.
Corrective Action
Re-execute the command in the filename file after correcting the element definition.
Or, check the resource name specified in the command and re-execute the command.
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 18 Settings for Server Switchover" in the "User's Guide VE".
[Virtual Edition]
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
power-off
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.
When "power-off" is displayed in status during registration of the VM host on the VM guest
Perform the operation again after starting the corresponding VM guest.
For details of each status, refer to "11.2 Resource Status" in the "Operation Guide VE".
[Cloud Edition]
Description
The command cannot be executed because the status of the object obj is status.
One of the following is displayed for obj:
Virtual storage resource name
Disk Resource Name
VM name
VM guest name
Library server name
L-Server Name
Physical server name
Network device name
IP address
One of the following is displayed in status:
normal
warning
unknown
stop
error
fatal
power-on or on
Indicates that the power of the server is on.
power-off or off
Indicates the state in which a server is powered off, a VM guest that was operated on an L-Server has been deleted from server virtualization software, or an unregistered VM host has been moved to a VM pool.
not belonging to any storage pool
Indicates that the specified virtual storage resource is not registered in a storage pool.
not accessible
Indicates that no access is available from the specified VM host or server.
not enough space for disk(name=disk)
Indicates that there is insufficient free space on the virtual storage resource. The resource name of the disk is displayed in disk.
not enough free space
Indicates that there is insufficient free space on the virtual storage resource.
defined
Indicates that resources (VM guests, servers, and disks) have not been allocated.
preserved
Indicates that servers have not been allocated.
allocated
shared
reserved
free
excluded
When obj is an IP address and status is "reserved"
Indicates that the IP address is already reserved.
When obj is an IP address and status is "free"
Indicates that the IP address has already been released.
When obj is an IP address and status is "excluded"
Indicates that the IP address has already been excluded.
bound
unavailable
ready
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.
When obj is a network device name
Perform the operation again after waiting a while. When the same errors are displayed, notify the infrastructure administrator of the information in this message.
An infrastructure administrator should collect this message and troubleshooting data, and contact Fujitsu technical staff.
When "defined" is displayed for status during a batch power ON operation
Perform the usual startup operations for the relevant L-Servers.
When status is one of the following:
reserved
free
excluded
Change the IP address of the L-Server or managed server, or delete the L-Platform on which the corresponding server load balancer is deployed, and then perform the operation again.
When reserved is output in Disaster Recovery environments, check that the same IP addresses are not used for different L-Servers among sites.
If an error occurs when registering a guest domain on Oracle VM for SPARC, delete the admin LAN NIC of the virtual L-Server with the specified IP address, and perform the operation again.
When registering an OVM for SPARC guest domain as a VM host and also registering it as an L-Server, check that the IP address is not being used by the VM host or the L-Server.
When obj is the L-Server name
The following causes are possible:
A VM guest used on the L-Server has been deleted from server virtualization software
During L-Server deletion, system failure of the VM management software server or VM management software has occurred
During L-Server deletion, system failure of admin server or manager occurs
A VM guest used on the L-Server has been moved from server virtualization software to a VM host which is unregistered in VM pool
When using Solaris Zones, OS re-installation in the non-global zone or modification of the global zone in which the non-global zone starts has been performed.
The status of an L-Server is not one in which the operation can be performed.
Check that the admin server, manager, VM management software server, or VM management software have been started, and perform the relevant operation.
For a.:
Delete the L-Server.
For b. or c.:
Delete the L-Server again.
For d.:
Migrate VM guests being used on the L-Server to VM hosts which are already registered in the VM pool.
In case of e
Refer to "8.7.10 Advisory Notes for Solaris Zone Usage" in the "Setup Guide CE", and then take corrective action.
For f.
Check the status, power status, and the status of resource allocation of the L-Server. After changing the status as necessary, perform the operation again.
When obj is the VM guest name
When the following is displayed on status, deletion of the L-Server failed because the state of the L-Server (VM guest) which you tried to delete was status.
[Solaris Zones]
"unavailable"
"ready"
[OVM for SPARC]
"bound"
Change to the state where the VM guest can be deleted from the VM host, and perform the operation again.
In addition, corrective action is unnecessary when this error message is output due to an operational mistake.
The tenant administrator or the tenant user must take the following corrective actions:
Notify the infrastructure administrator of the information in this message, and request them to change the state to one where the VM guest can be deleted.
Perform the operation again, after the infrastructure administrator changes the state of the VM guest.
The infrastructure administrator needs to perform the following corrective action.
Change the state to one where the VM guest can be deleted, as requested by a tenant administrator or a tenant user.
In other cases
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 "11.2 Resource Status" in the "Operation Guide CE".
Description
When obj is "PXE Server"
The PXE server is disabled.
When obj is something other than the above
The command cannot be executed because the mode of the object obj is mode.
One of the following is displayed for mode:
active (active mode)
maintenance (maintenance mode)
Corrective Action
When obj is "PXE Server"
Enable the PXE server, and then perform the operation again.
When obj is something other than the above
Check the status of the object obj, and then perform the operation again.
[Virtual Edition]
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 (active mode)
maintenance (maintenance mode)
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
Updating of disk information
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 16 Backup and Restore" in the "User's Guide VE".
For details of operations using cloning images, refer to "Chapter 17 Cloning [Physical Servers]" in the "User's Guide VE".
[Cloud Edition]
Description
Execution of the request failed, as the specified obj is not mode mode.
When obj is a disk resource
One of the following is displayed for mode:
Fibre Channel connection (Fibre Channel connection)
iSCSI connection (iSCSI connection)
When obj is a network device
There is a contradiction in the settings specified in the network configuration information (XML definition).
In mode, one of the following is displayed:
auto-config(auto-configuration of network devices)
When obj is something other than the above
One of the following is displayed for mode:
active
maintenance
Corrective Action
When obj is a disk resource
Check the connection status of the specified obj.
When "FC" is specified for Disk connection type (Disk type) in the L-Server XML
A disk with a Fibre Channel connection is allocated to the L-Server.
When "iSCSI" is specified for Disk connection type (Disk type) in the L-Server XML
A disk with an iSCSI connection is allocated to the L-Server.
When obj is a network device
Correct the contradiction between the settings specified in the auto-configuration of network devices (AutoConfiguration element) and the existence of auto-configuration (Vfab vfabauto attribute), and perform the operation again.
When performing VFAB auto-configuration for obj.
Modify the setting specified in the AutoConfiguration element in the network configuration information (XML definition) to "true", and perform the operation again.
When not performing VFAB auto-configuration for obj
Modify the setting of the Vfab vfabauto attribute specified in the network configuration information (XML definition) to "false", and perform the operation again.
When obj is something other than the above
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 "17.6.2 Backup and Restore" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details of operations using cloning images, refer to "17.5 Cloning Image Operations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Virtual Edition]
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.
[Cloud Edition]
Description
The type type of obj1 and obj2 is different.
One of the following is displayed for type:
boot device
server type
resource type
VMType
OSType
Disk(name=disk resource name defined in XML).size
Disk(name= disk resource name defined in XML).path
folder type
[KVM]
store type is displayed in type, and the disk resource name and its image location type are displayed in obj1 and obj2 respectively.
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.
"resource type"
Check the resource pool type of obj1 and the resource type of obj2, and perform the operation again after specifying a suitable combination of resource pool and resource.
For details on resource pool types and the resources that can be stored, refer to "2.2.2 Resource Pools" in the "Design Guide CE".
If this message is output when registering the disk resource with a storage pool, check whether the disk is the one created in advance using the disk resource.
From the command-line, execute rcxadm disk show.
For details on the rcxadm disk show command, refer to "3.3 rcxadm disk" in the "Reference Guide (Command/XML) CE".
"VMType"
Check the VM type of the resource obj1 and the VM type of the resource obj2, specify resources with the same VM type and then perform the operation again.
The combination of an obj1 resource and an obj2 resource is incorrect. Specify an unused address resource for the combination to be supported, and perform the operation again.
"OSType"
Check the OS type of the L-Server and the images specified in XML, specify resources with the same OS type and then perform the operation again.
"Disk(name=disk resource name defined in XML).size"
Confirm that the value of the size attribute of the disk resource name defined in the XML file is the same for both the obj1 VM host and the obj2 VM host, and then perform the operation again.
In obj1 and obj2, "VmHost(ip=IP address of the VM host defined in XML)" is displayed.
"Disk(name=disk resource name defined in XML).path"
Confirm that the value of the path attribute of the disk resource name defined in the XML file is the same for both the obj1 VM host and the obj2 VM host, and then perform the operation again.
In obj1 and obj2, "VmHost(ip=IP address of the VM host defined in XML)" is displayed.
"folder type"
After checking the type of the existing resource folder, L-Platform, and resource folder specified in the XML file, specify the same type in the XML, and then perform the operation again.
[KVM]
When "store type" is displayed in type, and the disk resource name and its image location type are displayed in obj1 and obj2 respectively
Collection and updating can only be performed when the disk type of the system disk of an L-Server and the image location type of the cloning image are the same. Check the disk type and the image location type, and perform the operation again.
For details, refer to "Conditions for Collection and Updating of Cloning Images" in "8.6.7 Collecting Cloning Images" in the "Setup Guide CE".
An L-Server with a cloning image specified can only be created when the disk type of the system disk of the L-Server and the image location type of the cloning image are the same.
For details, refer to "Conditions for Creating L-Servers that Use Cloning Images" in "8.6.6 Creating L-Servers" in the "Setup Guide CE".
The disk resource name and its image location type are displayed in obj1 and obj2, respectively.
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.
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.
Corrective Action
Check if the network cable is correctly connected between the admin server and the target server.
If the network cable is damaged
Replace the cable.
If the network cable is connected incorrectly
Reconnect the cable.
Check if the chassis is powered on.
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 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
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.
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 Manager]
>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 Manager]
# 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. |
Check the following items:
For <Example: Normal communication>
For <Example: Abnormal communication>
Check if the programs on the destination of communication are running.
For how to check, refer to the following:
For Virtual Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide VE".
For Cloud Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE".
Restart the manager or the agent.
For details on how to start, refer to the following:
For Virtual Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide VE".
For Cloud Edition, refer to "Chapter 2 Starting and Stopping Managers and Agents" in the "Operation Guide CE".
Check the settings of firewall software set for the admin server and the managed server.
Change the settings of the firewall to the appropriate values.
For details of the ports to set connection permission for, refer to the following:
For Virtual Edition, refer to "Appendix A Port List" in the "Design Guide VE".
For Cloud Edition, refer to "Appendix A Port List" in the "Design Guide CE".
For details of checks and setup of firewalls, refer to the manual of the firewall software being used.
For Virtual Edition, refer to "Appendix A Port List" in the "Design 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
For Cloud Edition, refer to "Appendix A Port List" in the "Design Guide CE", 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
Change the port number to the proper number.
For how to change port numbers, refer to the following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
For Cloud Edition, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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 port numbers were changed.
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.
Check if the IP address displayed in the error message is correct.
Check if the FQDN displayed in the error message is correct. Also, check whether it is possible to resolve the name of the relevant FQDN.
If the IP address is incorrect, specify the correct IP address and execute the operation again.
If the FQDN is incorrect, specify the correct FQDN and execute the operation again. If the FQDN name cannot be resolved, correct the content of the hosts file to enable resolution, and then perform the operation again.
For check methods and corrective actions, refer to "4.2 An Error Occurs during Cloning after the Manager is Reinstalled." in "Troubleshooting".
When an error occurs on the DR switchover destination site, also confirm that the configuration operation explained in the following section has been performed.
"Configuration when physical L-Servers are switchover targets" in "Common Configurations" in "3.4 Configuring Managed Resources" in the "DR Option Instruction"
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.
After the process that is causing the high network load finishes, perform the operation again.
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 Manager]
Folder_configured_in_the_APPDATA_environment_variable_of_each_user\Systemwalker Resource Coordinator\
[Linux Manager]
/Directory_configured_in_the_HOME_environment_variable_of_each_user/.rcx/
For Virtual Edition, delete the password information for the old manager, referring to "11.1.2 Uninstallation [Windows Manager]" or "11.1.3 Uninstallation [Linux Manager]" in the "Setup Guide VE", and then save the password again using the rcxlogin command.
For Cloud Edition, delete the password information for the old manager, referring to "11.1.2 Uninstallation [Windows Manager]" or "11.1.3 Uninstallation [Linux Manager]" in the "Setup Guide CE", and then save the password again using the rcxlogin command.
When the cause is not one of the above, collect troubleshooting information and contact Fujitsu technical staff.
[Cloud Edition]
Description
This message is output when a communication error occurs between the L-Server and the manager.
This message is output when a network information configuration error occurs during physical L-Server creation.
An error occurred during communication with the target target.
Corrective Action
Check that an agent is installed on the L-Server.
Check that there is no problem in the network path between the L-Server and the manager.
Execute the command specifying the file for the argument. When target is "Resource Orchestrator Manager", check whether or not the character code for the XML file is UTF-8.
When the configuration of network information has failed during L-Server creation, the physical L-Server cannot be deleted.
Perform the corrective action according to "Corrective Action" for the message.
Then configure the network information using the following method.
Configure the network environment
Execute the rcxadm lserver setup command to send the network information to an L-Server.
For details on the command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
When an error occurs at the DR switchover destination site, also confirm that the procedure explained in the following section has been performed.
"Configuration when physical L-Servers are switchover targets" in "Common Configurations" in "3.4 Configuring Managed Resources" in the "DR Option Instruction"
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 the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE", and check whether the "Manager Services" and "Related Services" have been started on the admin server.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE", 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 this message and troubleshooting data, 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 the following:
For Virtual Edition, refer to "5.2 rcxadm agtctl" or "5.11 rcxadm mgrctl" in the "Reference Guide (Command) VE".
For Cloud Edition, refer to "5.3 rcxadm agtctl" in the "Reference Guide (Command/XML) CE" or "5.11 rcxadm mgrctl" in the "Reference Guide (Command) VE".
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)" or "communication error.submgr:FQDN name SocketError:initialize: name or service not know"
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"
All or part of the manager services may be stopped.
If the manager services have been stopped, start the manager.
For details about how to confirm the service status or start the manager, refer to the following:
For Virtual Edition, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
For Cloud Edition, refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Virtual Edition]
Description
A DB access error occurred.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
A DB access error occurred.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Virtual Edition] [Cloud Edition]
Description
An error has occurred during execution of a manager command.
In detail, the following information is displayed.
Take corrective action based on the content output for detail.
For "quarantine failed(detail=detail)"
Transferring of the L-Server to the quarantine network failed.
detail will be one of the following:
"Two or more L-Server found. ip=IP_address,lserver_key=["Resource_ID", "Resource_ID",...]"
The connection information of the VDI management server specified in the msgnotice command has already been registered.
Corrective Action
Take corrective action based on the content output for detail.
The L-Server for which the IP address of the SNMP trap or REST API has been set was not found.
Check whether linking of the virtual machine or SBC server using this IP address with the L-Server is complete.
In configurations where there are multiple Resource Orchestrator managers, check the following:
Check whether the 413 warning message "Target lserver not found in submanager." has been output in the system log of the first manager of Resource Orchestrator.
If the 413 warning message has not been output, no corrective action is necessary.
Check whether the L-Server is being managed using another sub manager.
If it is being managed using another sub manager, check whether the information for sub manager coordination is configured correctly.
If "submgr:Resource_Orchestrator_manager_IP_address_or_FQDN" is included in detail, the message can be ignored.
Multiple L-Servers for which the IP address of the SNMP trap or REST API has been set were found.
Environments in which multiple L-Servers are configured with the same IP address for reasons such as tenants are being used, are not supported.
Only use an IP address for one virtual L-Server.
The connection information of the VDI management server specified in the msgnotice command has already been registered.
The target VDI management server is already registered. No action is required.
An error occurred during the modification of the L-Server performed during the transfer process of the L-Server to the quarantine network.
Take corrective action explained for the corresponding error message in "Messages".
In configurations where there are multiple Resource Orchestrator managers, check the following, connect to the manager where the problem occurred, and perform corrective action based on the error message.
When "submgr:Resource_Orchestrator_manager_IP_address_or_FQDN" is included in detail
A problem has occurred on the Resource Orchestrator manager corresponding to the IP address or the FQDN.
When "submgr:Resource_Orchestrator_manager_IP_address_or_FQDN" is not included in detail
The problem occurred on the manager on which the rcxadm submgr command was executed.
[Virtual Edition]
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.
[Windows Manager]
[Linux Manager]
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.
Corrective Action
(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 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 |
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.
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"
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.
For the corrective action, refer to "Corrective action 3".
For the corrective action, refer to "Corrective action 2".
Collect troubleshooting information and contact Fujitsu technical staff.
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.
Collect troubleshooting information and contact Fujitsu technical staff.
For the corrective action, refer to "Corrective action 4".
For the corrective action, refer to "Corrective action 10".
[Windows Manager]
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".
DHCP server database access may have failed, so perform the failed operation again.
Communication with the DHCP server corresponding to "ip_addr=IP_address" may have failed.
Check the running state of the network environment and agents, and then execute the failed operation again.
[Linux Manager]
There is possibility that a network address that is not available on the Linux standard DHCP server has been specified.
For the corrective action, refer to "Corrective action 11".
There is also the possibility that DHCP server database access has failed, so perform the failed operation again.
For the corrective action, refer to "Corrective action 6".
For the corrective action, refer to "Corrective action 7".
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".
An error occurred as copying of files failed.
For the corrective action, refer to "Corrective action 13".
An error occurred as archiving of files failed.
For the corrective action, refer to "Corrective action 14".
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 details on how to start managers, refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
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 details on how to start managers, refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
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 details on setup, refer to the following:
Refer to "2.1 Manager Installation" in the "Setup Guide VE".
Refer to "2.1 Manager Installation" in the "Setup Guide CE".
If this does not resolve the problem, refer to "Corrective action 10".
For Virtual Edition, 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 "17.6 Network Parameter Auto-Configuration for Cloning Images" in 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 steps 3 to 4. If the status is the same as before the operation, perform step 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 step 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 Operation 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 (such as the free space on the disk), 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.
[Cloud Edition]
Description
An error has occurred during execution of a manager command.
In detail, the following information is displayed:
Perform corrective action based on the content output for detail.
Corrective Action
When using GDS as storage management software
During the process, the connection between the admin server and the storage management software may have been lost.
Check the power status and communication status of the storage management software.
There may be an error in the GDS settings.
Review the GDS settings.
The storage management software may be overloaded.
Perform the operation again after completing the high-load processing.
When using libvirt as storage management software
During the process, the connection between the admin server and the VM host may have been lost.
Check the power and communication statuses of the VM host and take corrective action, then perform the operation again.
The database that stores the configuration definition information could not be accessed. The command will not be executed.
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.
Description
During server switchover, operations for target on the managed server server_name failed to complete correctly.
Recovery to the status in which ZFS storage pools can be imported, or zones on ZFS storage pools can be used, failed.
The name of the server is displayed for server_name.
One of the following is displayed for target:
ZFS Storage pool (ZFS_storage_pool_name)
Solaris zone (Zone_name)
The name of the command executed on the OS is displayed for command.
The target of the command is displayed for detail. Messages other than the following may be output.
Take corrective action based on the content of target and detail.
For details on the corrective action or the command when a detail other than those below is output, refer to the Oracle Documentation.
Corrective Action
There are no ZFS storage pools to import.
Check that there are ZFS storage pools.
When there are ZFS storage pools, execute import of ZFS storage pools using the following command:
"zpool import -f ZFS_storage_pool_name" <RETURN> |
When there are no ZFS storage pools to import, no corrective action is necessary.
There are no ZFS storage pools with the name ZFS_storage_pool_name to import.
Check the ZFS storage pool ZFS_storage_pool_name.
When creating the zpool_and_zone_recovery.rcxprop definition file, check that there are no errors in the details.
When there is an error in the ZFS storage pool name, execute import of ZFS storage pools using the following command:
"zpool import -f ZFS_storage_pool_name" <RETURN> |
The ZFS storage pool with the name ZFS_storage_pool_name has already been imported.
Check the ZFS storage pool ZFS_storage_pool_name.
When creating the zpool_and_zone_recovery.rcxprop definition file, check that there are no errors in the details.
When there is an error in the ZFS storage pool name, execute import of ZFS storage pools using the following command:
"zpool import -f ZFS_storage_pool_name" <RETURN> |
When ZFS_storage_pool_name is "all pools", execute the following command:
"zpool import -f -a" <RETURN> |
In other cases, execute the following command:
"zpool import -f ZFS_storage_pool_name" <RETURN> |
When there are no errors in the ZFS_storage_pool_name, no corrective action is necessary.
There are no zones with the name Zone_name.
Check that there are no errors in the Zone_name.
When creating the zpool_and_zone_recovery.rcxprop definition file, check that there are no errors in the details.
When there is an error in the zone name, execute the following command:
"zoneadm -z Zone_name attach", "zoneadm -z Zone_name boot" <RETURN> |
The zone with the name Zone_name has already been installed.
When starting of the zone is necessary, execute the following command:
"zoneadm -z Zone_name boot" <RETURN> |
The zone with the name Zone_name has already been started.
No action is necessary.
Starting of the zone with the name Zone_name, which has not been installed, is being attempted.
Execute the following command to install the zone with the name Zone_name.
"zoneadm -z Zone_name attach" <RETURN> |
When starting the zone afterwards, execute the following command.
"zoneadm -z Zone_name boot" <RETURN> |
Installation of the zone with the name Zone_name, which has already been installed and started, is being attempted.
No action is necessary.
There are no zone names to be specified. There is a problem with the method used to execute the command on the OS.
No action is necessary.
