This section explains the 671XX message series.
[Description]
The resource that matches obj could not be 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.
[Corrective Action]
Review the specified conditions.
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.
[Description]
obj files or directories cannot be created.
[Corrective Action]
Check the following, resolve the cause of the error, and then perform the operation again.
Confirm the access privileges of the directory.
Confirm that there is sufficient disk space.
[Description]
The keys attribute has been specified simultaneously in the XML definition of the network resource.
details displays detailed information.
keys include the following:
When "number and lag"
The number attribute and lag attribute have both been specified in the NetworkSwitchPort tag.
The following is displayed in detail.
number=the specified port number,lag= link aggregation group name
[Corrective Action]
Review the attributes for keys, specify the correct one, then retry.
[Description]
There is an error in the format of the command. "Usage" is displayed.
[Corrective Action]
Change the command format and perform the operation again.
[Description]
"usage" is displayed.
An argument has not been specified for an option.
A parameter has not been specified.
[Corrective Action]
Change the command format and perform the operation again.
After specifying the parameter, perform the operation again.
[Description]
The specified option argument is too long.
option may not be displayed.
[Corrective Action]
Review the specified option argument, and perform the operation again.
[Description]
Invalid characters are included in the specified option argument.
When this message is displayed at rcxadm config import command execution time, an illegal character is included in the definition of XML of the snap shot displayed with option.
[Corrective Action]
Review the specified option argument.
When performing an operation where line breaks are prohibited, confirm that line break codes are not inserted at the end of line when copying and pasting are done.
After confirmation, 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
[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
[Corrective Action]
Perform the operation again after correcting the specified value.
When value is one of the following, perform corrective action according to the content:
"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 values for the NIC index of an L-Server, resolve the cause, and perform the operation again.
[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
Create tenant folders
Importing configuration information
Creating network devices
Changing network devices
"Parameter key name(VM specific information definition file name, specified value, range)"
One of the following is displayed in value:
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
[Corrective Action]
When "-duration" is displayed:
Specify a correct value or format for the option, then perform the operation again.
For details, refer to "1.7.15 rcxadm logctl".
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.
For details on XML files, refer to "Chapter 2 Resource Configuration Information and User Definition Information (XML Files)".
[Description]
A value that cannot be specified for an option argument has been specified. "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.
[Description]
There is an error in the file format specified for filename.
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 specified 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 "8.6.1 When Collecting Cloning Images from Physical L-Servers" of 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 "10.3.5 [OS] Tab" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When "server_spec.rcxprop" is displayed:
Check the format of the corresponding file, referring to "E.1.1 Definition Files" in the "Setup Guide CE".
When "server_control.rcxprop" is displayed:
Check the file format, referring to "Configuration when Creating a Virtual L-Server Using VMware ESXi on Other Vendor's Servers" in "E.1.1 Definition Files" in the "Setup Guide CE".
When the following files are displayed:
Check the format of the specified server NIC definition file referring to "2.11 Server NIC Definitions".
[Windows]
Installation_folder\Manager\etc\customize_data\nicdefctl\model\Chassis_model_name_product_name.xml
Installation_folder\Manager\etc\customize_data\nicdefctl\host\VM_host_name.xml
[Linux]
/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 "2.13 Network Device Model Definition".
[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]
You have no access privileges for the file specified in filename.
[Corrective Action]
Check the owner, the owner group, and access privileges of the specified file.
[Description]
Refer to the explanation in "Message number 67142" in the "Messages VE".
[Corrective Action]
Refer to the explanation in "Message number 67142" in the "Messages VE".
There is also the following case for Resource Orchestrator.
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.
[Description]
The process was canceled as the target file was not found.
[Corrective Action]
When executing the rcxchkmismatch command and file_name 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 file_name is "storage_portset.rcxprop"
Notify the infrastructure administrator of the information in this message.
The infrastructure administrator should create the definition file, referring to "6.1.1 Creating Definition Files for Combining Ports for 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, refer to "Setting the Number of FCs Fitted and their Position for Each Physical Server" in the "Setup Guide CE".
In other cases
Specify a file as the target of operation, and perform the operation again.
[Description]
One of the following is displayed in file_name:
Resource Name
No permission has been granted for the specified resource.
File Name
No access is available for the Resource Orchestrator file name.
[Corrective Action]
Take corrective action based on the content of file_name.
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]
Loading of the Resource Orchestrator file filename has failed.
[Corrective Action]
Check the following, resolve the cause of the error, and then perform the operation again.
Check the system log to see if there are error message(s) regarding the disk or file system.
[Description]
obj already exists.
One of the following is displayed in 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 "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.
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 "1.7.10 rcxadm authctl".
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 "vnet"
Either specify a different VLAN ID, or delete the existing network resource, and then perform the operation again.
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.
[Description]
The error may be the result of one of the following:
The specified object name obj does not exist
There is no object that meets the conditions
The object that met the conditions was deleted deletion processing
The specified object exists, but is not included in the access scope of the user group or user that performed the operation
The target resource folder was not specified when a user with multiple access scopes performed an operation
When a user with multiple access scopes performs the following operations, "Folder:not found" or "Specified_resource_name:not found" is displayed.
Creation of an L-Server, with no target resource folder name set
Creation of a tenant folder, resource folder, or resource pool, without specifying the name using the hierarchy
Moving of a tenant folder, resource folder, or resource pool, without specifying the -to option for the destination
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 "already registered" in the network pool was attempted
When obj starts with the following value, the operation has failed because a system disk has not been specified during physical L-Server creation.
System Disk
If this message is displayed when the command is executed, the resource type of the specified object name may differ from the type of resource that can be specified in the arguments for the command.
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.
When executing a command, one of the following is displayed for the resource type of the object name:
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 resource type is "virtual_storage", there is a chance that there is not enough available space on the virtual storage resource.
When obj is "Selectable virtual_storage(condition)"
There is a possibility where the amount of disk of the selected virtual storage resource is insufficient.
When obj is "Selectable mac_address_set(condition)"
There is no empty address in the address set resource (Media Access Control address) or the address set resource (Media Access Control address) does not exist.
When obj is "resource" or "Pool"
The resource to be registered with or canceled from the resource pool, or the resource pool, was not found.
When obj is "DNSServer.nic=X"
The definition of NIC that sets the DNS server L-Server is not found.
When obj is "nic(position=[nic] server=server)"
Operations fail, since the specified NIC is not on a server in the physical LAN segment.
When obj starts with the following:
The operation has failed because there is no internal resource table.
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
When obj starts with the following:
The operation has failed because there is no virtual network or virtual switch on the target server of 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.
For details on conditions for automatic creation of virtual networks or virtual switches, refer to "1.2.7 Simplifying Networks" in the "Setup Guide CE".
When obj starts with "rcx-portset"
The procedure described in "NetApp FAS Storage Configuration" in "D.3.2 When Using NetApp FAS Storage" of the "Setup Guide CE" may not have been performed.
When obj is "AuthManager"
The operation has failed because a directory service is not registered.
When obj starts with "LServer"
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.
When obj starts with "L-Server Template"
There is no target L-Server template for the operation.
Check that the specified L-Server template exists.
When obj starts with "L-Platform"
There is no target L-Platform for the operation.
Check that the specified L-Platform exists.
When obj starts with "MacAddressSet"
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.
When obj starts with the following:
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.
VmGuestStorage(device_name)
VirtualNic(LNic index=NIC_index)
VirtualNic(LNic mac_address=MAC_address)
When obj starts with the following:
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.
TargetServer id=Virtual_machine_ID
PhysicalServer id=Physical_server_ID
When obj starts with "PhysicalLANSegment"
Operations fail, since a physical LAN segment specified using network resource physical LAN segment is not registered in the server NIC definition.
When obj starts with "link aggregation(switch=switch,lag=labname)"
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.
When obj is "CTMG backup directory(base)"
A request to collect a difference backup was made in the state where a base backup has not been collected.
When obj is ProvisioningNode(name=fw_device_name)
The network device for fw_device_name is not registered in the network pool of the tenant for name.
[Corrective Action]
After checking the following for the displayed object, perform the operation again.
That the object exists
That the object meets the conditions
The access scope of the object has been set
Specification of a target resource folder, when the user has multiple access scopes
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 folder" in "2.3.1 Definition Information for Physical L-Servers (XML)"
"Example Creating an L-Server in a resource folder or a tenant folder" in "2.3.2 Definition Information for Virtual L-Servers (XML)"
When creating tenant folders, 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:
When moving a tenant folder, a resource folder, or a resource pool, specify the destination resource folder.
For details on destination resource folders, refer to the following information:
Check that the values specified in the definition file are less than the actual number of CPUs and CPU clock speed of a server for which server management software is not used.
Change the registration status of network devices to "already registered", and register the network devices in the resource pool again.
When obj starts with the following value, the operation has failed because a system disk has not been specified during physical L-Server creation.
System Disk
Confirm that a system disk (DiskIndex 0) is defined and perform the operation again.
If this message is displayed when the command is executed, perform the operation again after checking the resource type of the specified object.
When the following values are displayed for obj, take the following corrective action based on the content.
"library share" [Hyper-V]
There is an error in the storage destination specified for the cloning image.
Check if the specified shared library is available.
"Selectable virtual_storage(condition)"
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 "E.4.4 Setup" of the "Setup Guide CE".
"Selectable disk(condition)"
There is no disk resource matching the specified size registered in the storage pool.
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
"Selectable mac_address_set(condition)"
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.
"resource" or "Pool"
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.
"DNSServer.nic=X"
The NIC definition to set for the DNS server was not found. Check whether the NIC for X exists, review the NIC definition on DNS server, and then perform the operation again.
"AuthManager"
Perform the operation again after registering a directory service.
"nic(position=[nic] server=server)"
There is no specified NIC on servers. Check the server NIC definition.
When obj starts with one of the following values:
Wait for a short while and then repeat the operation.
VnetRoute
CnmVirtualLanSwitch
CnmVirtualNetwork
When obj starts with one of the following values:
Perform the operation again after creating a virtual network or a virtual switch on the target server of 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.
When obj starts with "rcx-portset"
Check the storage unit configuration referring to "NetApp FAS Storage Configuration" in "D.3.2 When Using NetApp FAS Storage" of the "Setup Guide CE".
When obj starts with "LServer"
There is no target L-Server for the power operation. Check the status of the L-Server, and perform the appropriate operation or specify another resource folder, and then perform the operation again.
When obj starts with "L-Server Template"
There is no target L-Server template for the operation. Specify another L-Server template, and then perform the operation again.
When obj starts with "L-Platform"
There is no target L-Platform for the operation. After checking the existence of L-Platforms, perform the operation again.
When obj starts with "MacAddressSet"
Check whether there is an address set that includes a MAC address, and then retry.
When obj starts with one of the following values:
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.
VmGuestStorage(device_name)
VirtualNic(LNic index=NIC_index)
VirtualNic(LNic mac_address=MAC_address)
When obj starts with one of the following values:
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.
TargetServer id=Virtual_machine_ID
PhysicalServer id=Physical_server_ID
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.
When obj starts with "PhysicalLANSegment"
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.
When obj starts with "link aggregation(switch=switch,lag=labname)"
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 "4.2.4.4 When Using Link Aggregation" in the "Setup Guide CE" for information on the settings.
When obj is "CTMG backup directory(base)"
Collect a base backup, and then repeat the operation.
If the problem is still not resolved after performing the above actions or if a value not indicated above is displayed in obj, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
When obj is ProvisioningNode(name=fw_device_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 "15.3 Switchover Operations when Damaged" in "Operation Guide CE".
[Description]
Refer to the explanation in "Message number 67155" in the "Messages VE".
However, in Resource Orchestrator, one of the following values may be displayed for type:
"VMHost" or "PhysicalServer"
obj has already been registered in a resource pool.
"VM", "Server", "Storage", "Network", "Address", or "Image", and if this message is output during creation of resource pools
obj has already been registered in a resource pool.
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.
"server", and if this message is output during creation of physical L-Servers
The IP address of obj is overlapping with the IP address of the admin LAN used by the L-Servers and the managed servers.
"IP address"
The IP address obj of the public LAN specified during creation of the physical L-Server is already in use.
"iSCSI.iqn"
The IQN name in obj is already in use.
"iSCSI.ip"
The IP address in obj is already in use.
[Corrective Action]
Refer to the explanation in "Message number 67155" in the "Messages VE".
Take corrective action based on the content of type.
"VMHost" or "PhysicalServer"
Perform the operation again after releasing registration of obj from the resource pool.
"VM", "Server", "Storage", "Network", "Address", or "Image", and if this message is output during creation of resource pools
Check the resource pool of obj, and create it again if necessary.
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.
"server", and if this message is output during creation of physical L-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.
"IP address"
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.
"iSCSI.iqn"
Perform the operation again after correcting the specified IQN name.
"iSCSI.ip"
Perform the operation again after correcting the specified IP address.
[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.
[Description]
Refer to the explanation in "Message number 67161" in the "Messages VE".
There is also the following case for Resource Orchestrator.
When option is "Pool"
The Pool element cannot be specified in the XML file.
[Corrective Action]
Refer to the explanation in "Message number 67161" in the "Messages VE".
There is also the following case for Resource Orchestrator.
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 the "Configuration when Creating a Virtual L-Server Using VMware ESXi on Other Vendor's Servers" in "E.1.1 Definition Files" in the "Setup Guide CE", and then specify the server as the server which can use agents.
[Description]
option must be specified. "usage" is displayed.
[Corrective Action]
After checking the parameter, perform the operation again.
Take corrective action based on the content of option.
"name"
Specify the L-Server 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 indispensable.
Specify -allow deldisk or either of -deny deldisk option, and perform the operation again.
[Description]
The request could not be executed because obj contains a type object.
The object name is displayed in obj.
One of the following is displayed in type:
For Physical Servers
"physical server" is displayed.
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]
Perform the operation again after deleting the type object from obj.
Take corrective action based on the content of type.
When type is "disk"
Delete the L-Server using the disk resource created from the virtual storage resource displayed in obj.
When type is "vstorage"
Delete the L-Server using the virtual storage resource created under the physical storage unit resource displayed in obj.
[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 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.
[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 request could not be executed because obj is in the status status.
One of the following is displayed in 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
One of the following is displayed in status:
normal
warning
unknown
stop
error
fatal
power-on
Indicates that the power of the server is on.
power-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.
[Corrective Action]
Check the necessary requirements for the obj operation, and fulfill them. Perform the operation again after fulfilling the requirements.
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
Change the IP address of the L-Server or managed server, then perform the operation again:
reserved
free
excluded
[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 in mode:
Fibre Channel connection (Fibre Channel connection)
iSCSI connection (iSCSI connection)
When obj is something other than the above
Refer to "Message number 67181" in "Messages VE".
[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.
[Description]
Refer to the explanation in "Message number 67182" in the "Messages VE".
However, the following is added to type for Resource Orchestrator:
resource type
VMType
OSType
Disk(name=disk resource name defined in XML).size
folder type
[Corrective Action]
Refer to the explanation in "Message number 67182" in the "Messages VE".
Also, perform the following corrective action depending on the type value:
"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 "1.2.2 Resource Pool" in the "Setup 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 "1.3.4 rcxadm disk".
"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.
"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.
[Description]
An error occurred while communicating with target.
This message is output when a communication error occurs between the L-Server and the manager.
[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.
Refer to the explanation in "Message number 67192" in the "Messages VE".
[Description]
A DB access error has occurred.
[Corrective Action]
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
[Description]
An error occurred in the manager command.
In detail, the following information is displayed:
When "Failed to access database for backup." is displayed
Accessing of the database where configuration definition information is stored failed. The command is not executed.
[Corrective Action]
Perform corrective action based on the content output for detail.
Where there is nothing relevant to detail, refer to "Message number 67198" in the "Messages VE".
"timeout"
When using PRIMECLUSTER 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 PRIMECLUSTER GDS settings.
Review the PRIMECLUSTER GDS settings.
The storage management software may be overloaded.
Perform the operation again after completing the high-load processing.
"Failed to access database for backup."
Check the status of the database, resolve the cause of the access failure, and then execute the command again.
If a string including double-byte characters is specified for the -dir option of the rcxbackup command, accessing of the database will fail.
