This section explains the 672XX message series.
[Description]
The IP address or MAC address of obj cannot be used, since the addresses are already being used.
There may also be the following cases:
obj is already in use.
This also applies when an already excluded IP address (an admin server, a managed server, a network address, or a broadcast address) is specified for an exclusion IP address, when configuring a network resource.
The specified disk resource is used for an L-Server. The size and path cannot be changed for the disk resources used by an L-Server.
The specified disk resource is used by an L-Server. The disk resource has been registered in a resource pool. Therefore, disk registration cannot be released.
In obj, the MAC address written in "mac_address=" has already been used.
[Corrective Action]
Review the specified option argument, and perform the operation again.
When this message is output, the same IP address or MAC address may be being used for the following registered devices.
Chassis
LAN switch
Network device
Admin server
Managed server
Power monitoring device
For other cases, perform the following corrective actions.
When obj is already in use
Perform one of following corrective actions:
Review the specified option argument, and perform the operation again.
Exclude obj from an L-Server.
Release registration of obj from the storage pool.
In obj, when the MAC address written in "mac_address=" has already been used
Perform the operation again after correcting the specified MAC address.
[Description]
The requested process cannot be performed as another process is already being performed.
[Corrective Action]
Take corrective action based on the content of obj.
When obj is a network resource
Wait for a short while and then repeat the operation. After deleting the L-Server connected to the network resource, perform the operation again.
When obj is "Manager task"
Check the status of the admin server, and perform the operation again after any operations being executed on the admin server are completed.
If this message is displayed when the admin server is stopped, the operation being executed on the admin server may remain in the database. Start the admin server and complete the operation being executed on the admin server, or restore the configuration definition information already collected, then perform the operation again.
When obj is a LAN switch blade name
The network resource using the LAN switch blade which is displayed in obj exists. Delete the network resource and perform the operation again.
When obj is something other than the above
Wait for a short while and then repeat the operation.
[Description]
Either there is no system image of the managed server, or the specified version of the system image was not found. Or there is no snapshot of the managed server, or the specified version of the snapshot was not found.
[Corrective Action]
Check whether there is a system image or snapshot of the relevant managed server.
If an incorrect version was specified, specify the correct version, and perform the operation again.
There is also a chance that image files have not been synchronized. Restart the manager service referring to "7.2 Starting and Stopping the Manager" in the "Setup Guide CE".
[Description]
There are no spare servers that fulfill the conditions. The specified spare server does not fulfill the following conditions.
Refer to the explanation in "Message number 67220" in the "Messages VE".
When a physical L-Server has been switched over
There are no physical server resources available as spare servers in the specified spare server resource pool.
[Corrective Action]
Check that the physical server in the server pool which was specified as a spare server meets or exceeds all of the following conditions:
Number of CPUs
CPU Clock Speed
Memory Size
Number of NICs
Number of FCs in the FC connection pattern
Refer to the explanation in "Message number 67220" in the "Messages VE".
When a physical L-Server has been switched over
Register an additional physical server resource in the spare server resource pool specified for the target L-Server.
There may be differences between the values in the definition files and the actual configuration information of that server.
Check that the correct values have been entered.
For details on the definition file, refer to "Appendix I Definition Files" of the "Setup Guide CE".
A physical server cannot be found that has the number of FCs specified in the FC connection pattern.
Refer to "4.3.1.2 Storage Configuration" in the "Setup Guide CE" for information on how to obtain the FC information for the physical server.
[Description]
Refer to the explanation in "Message number 67225" in the "Messages VE".
In Resource Orchestrator, this message may be output when the rcxvmdiskagt command is executed.
[Corrective Action]
Refer to the explanation in "Message number 67225" in the "Messages VE".
If this message is output when executing the rcxvmdiskagt command, perform the following corrective action:
Ensure that the specified IP address is the IP address of admin LAN for the VM host, then perform the operation again.
[Description]
Failed to decrypt the password.
[Corrective Action]
When the message above is output during reading of a configuration definition file
Confirm if the password is configured using an encrypted character string in the resource definition line for specifying "encrypted" (encrypted password).
For details on configuration definition files, refer to "Appendix A Format of CSV System Configuration Files" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When the message above is output during reading of a network configuration information file and "true" is specified for the PasswordEncryption element
Check if an encrypted character string is configured for the Password element or the PrivilegedPassword element.
For details on the network configuration information files, refer to "2.6.1 Creation".
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]
The specified option option is not supported.
Refer to the explanation in "Message number 67255" in the "Messages VE".
There are also the following cases for Resource Orchestrator:
When a physical L-Server was created, "NICs.NIC.NetworkLinkfor NICIndex(num)" is displayed in option
Network resources cannot be specified for the displayed NIC.
The number displayed for NICIndex(num) is a value one lower than the number specified when creating the L-Server.
When "-system" or "-force" is displayed in option
The storage unit to which the disk resource, for which an operation was attempted using the rcxadm lserver attach command or the rcxadm lserver detach command, belongs does not support the -system option or the -force option of the rcxadm lserver command used for the switchover of operating and standby storage. Therefore, the -system option and the -force option cannot be specified.
When "resource" is displayed in "option"
The error may be the result of one of the following:
The specified resource is not the target of the movement
The resource has not been registered in the orchestration tree
When "-deny deldisk" is displayed in option
-deny deldisk (do not delete) cannot be specified when reducing disks that have been separated from the virtual storage from the specified L-Server.
[Corrective Action]
Perform the operation again after correcting the specified option.
Refer to the explanation in "Message number 67255" in the "Messages VE".
There is also the following case for Resource Orchestrator:
When a physical L-Server was created, "NICs.NIC.NetworkLinkfor NICIndex(num)" is displayed in option
Change the network resource settings and perform the operation again.
When "-system" or "-force" is displayed in option
Check that switchover of operating or standby storage is being performed for the correct storage unit, or check the content of the replication definition file.
When "resource" is displayed in "option"
Specify a movable resource. Also, register resources that have not been registered in the resource orchestration tree into resource pools.
When "-deny deldisk" is displayed in option
This disk is deleted when reducing disks that have been separated from the virtual storage from the specified L-Server. To reduce, specify the -allow deldisk option and retry.
The -deny deldisk option can only be specified when detaching disks from physical L-Servers or virtual L-Servers with the VM type Hyper-V.
[Description]
The file or directory specified in obj does not exist.
[Corrective Action]
Specify an existing file or directory.
[Description]
Refer to the explanation in "Message number 67280" in the "Messages VE".
In detail, the following detailed information is displayed:
"power-off"
The function displayed in function cannot be used with the current power state (power-off).
"The last pool_type pool cannot be deleted."
The target resource displayed in obj cannot be deleted because it is the last resource pool of resource pool type pool_type.
"pool type mismatched"
The target resource displayed in obj cannot be registered in the resource pool because it is a resource pool type that cannot be registered.
"already exists in pool name"
The target resource displayed in obj cannot be registered in the resource pool because it is already registered in pool name.
"boot disk"
The boot disk cannot be deleted.
"invalid Redundancy"
The function displayed in function cannot be used as L-Server has been located on a VM host with a disabled HA function.
function cannot be executed, as VMware FT has been set for the target resource.
Or function cannot be executed as VMware FT cannot be configured for the target resource.
"Network pool,Address pool,and Image pool"
The target resource cannot be included when calculating the number of L-Servers creatable for each L-Server template.
"VirtualStorage[virtual storage...]", "Pool[storage pool...]", "VirtualStorage[virtual storage],Pool[storage pool]"
The name of the virtual storage resource is displayed in virtual storage.
The name of the storage pool name is displayed in storage pool.
For the function displayed for function, it is not possible to specify system disks and data disks with differing virtual storage or storage pools.
"vmhost[vmtype]"
In vmhost, the VM host name is displayed.
The VM type for the vmhost is displayed in vmtype.
Migration cannot be performed when the VM types of the L-Server and the VM host specified as the migrate destination are different.
"spare server"
Since the operation target resource is a spare server, registration in the server pool cannot be performed.
"some settings exist"
Registration in the server pool cannot be performed because the target operation resource already has an OS installed, or some settings such as I/O virtualization have been configured.
"VMType", "Model", "CPU", "Memory", "Policy.Positioning", "NICs", "Disks.Disk.type", "Policy.SpareSelection", "CPU.NumOfCPU", "CPU.CPUPerf", "Memory.MemorySize", or "FCConnectionPattern"
The above tabs specified in the L-Server template cannot be imported, as they are not supported.
When importing an L-Server template for a physical L-Server, if the following elements are displayed, there is an inconsistency in combinations with other elements described in the XML file.
CPU
Memory
CPU.NumOfCPU
CPU.CPUPerf
Memory.MemorySize
Disks.Disk.type
"Not connected PhysicalServer"
Operation cannot be performed, as the physical server is not connected due to changes to physical server usage.
"VIOM"
HBA address rename settings cannot be configured for the server displayed in obj as a virtualization method has been already configured using VIOM.
"Not Physical Server"
This command can only be performed for the physical L-Server.
Execute this command for the physical L-Server.
"setting VIOM server profile"
In the chassis mounting the server displayed in obj, setting of VIOM is not possible because a server with a virtualization method configured using HBA address rename already exists.
"Network Parameter Auto-Configuration is enabled"
Failed to configure the IP address of the public LAN. The specified cloning images cannot be used, as ROR VE network parameter settings are valid.
"Invalid target network admin LAN"
Failed to configure the IP address of the public LAN. IP addresses cannot be configured for the admin LAN.
"Target network overlaps with admin LAN"
Failed to configure the IP address of the public LAN. The same network as the admin LAN cannot be configured for the public LAN.
When obj is something other than "Target network overlaps with admin LAN"
You are trying to use a function that is not supported by obj, or a function that cannot be used because the status is invalid.
"Invalid agent version"
Failed to configure the IP address of the public LAN. As an agent of a version earlier than ServerView Resource Orchestrator V2.2.1 has been installed, it is not possible to configure a public LAN IP address on the specified cloning image.
When creating a physical L-Server, the IP address cannot be automatically configured if a Red Hat Enterprise Linux image is specified.
When using the created L-Server, manually configure the public LAN IP address.
"disk link"
The DiskLink element cannot be specified in XML for disks with the disk number 0.
"disk copy"
The DiskCopy element cannot be specified in XML for disks with the disk number 0.
"disk link, copy"
The DiskLink element and the DiskCopy element cannot be specified in XML for a single disk at the same time.
"disk type"
The value specified for "type" cannot be set for disks other than disk number 0.
"DiskLink" or "DiskCopy"
An L-Server cannot be created, as the above elements are not supported when creating an L-Server.
"MacAddress"
The operation cannot be performed because the L-Server function displayed in function does not support the above elements.
"release MacAddress" or "reserve MacAddress"
[KVM]
Addition and deletion of NICs and changing of VM type are not possible because the following operations are not supported.
Allocating of a MAC address from the address pool of Resource Orchestrator when modifying virtual L-Server configuration definition information
Releasing of the MAC address allocated from the address pool of Resource Orchestrator
"illegal disk type"
Configurations cannot be changed, since the specified disk resource is not the disk resource of a VM guest.
"disk unregistration"
Try to release disk resource registration using a configuration modification operation.
"Not Virtual Machine" or "Physical Server"
Usage is not possible for physical L-Servers.
"already in use"
A disk that is already being used exclusively by an L-Server cannot be attached to another L-Server.
"last" or "logical server not found"
The function cannot be executed, since operations not supported by the target resources were specified.
"hierarchizing of Tenant folder"
As the hierarchizing of tenant folders is not supported, tenant folders cannot be created in, or moved into, a tenant folder.
"invalid Repurpose"
function cannot be executed, as the resource to be operated does not support the XML tag in detail.
"already in use"
A virtual machine, a physical server, or a disk that is already being used exclusively by an L-Server cannot be connected to another L-Server.
"VM Type", "VMType", or "VM type"
The target resource displayed in obj is server virtualization software that does not support function.
[VMware]
For VMware ESXi, the following operation is not supported.
Backup
[Xen]
The following operation is not supported.
Overcommit
[Oracle VM]
The following operation is not supported.
Creation of an L-Server without specifying a cloning image
Overcommit
"illegal disk type"
The disk type is not supported.
"not creatable storage"
Disk resources cannot be automatically generated on the target storage device.
"can not delete the static disk"
The LUN created in advance cannot be deleted.
"VIOM is required"
When allocating disk resources to physical L-Servers from multiple storage chassis, VIOM is necessary.
"subnet"
The subnet address of the admin LAN resource that is directly connected from the manager cannot be changed.
"mask"
The subnet mask of the admin LAN resource that is directly connected from the manager cannot be changed.
"DefaultGateway"
The default gateway of the admin LAN resource that is directly connected from the manager cannot be changed.
When obj is "network_resource_name" and detail is "AddressSet"
The subnet address of a resource of the admin LAN directly connected to a manager cannot be specified.
When obj is "network_resource_name" and detail is "ManagementLanSubnet"
Subnet addresses of the admin LAN cannot be used for public LAN resources.
The <ManagementLanSubnet> tag cannot be specified when the <Type> tag to specify the network resource type is not set.
When obj is "network_resource_name" and detail is "Pool"
The specified Pool element cannot be specified when changing network resource settings.
obj is "network_resource_name" and detail is "Vlanautosetting"
Automatic VLAN configuration flags for external connection ports cannot be changed.
When obj is "UserGroup", and detail is "supervisor group"
The "supervisor" group cannot be edited and deleted.
"Pool"
The resource pool cannot be specified.
"Type"
The network resource type cannot be specified.
"Vlanid"
The VLAN ID cannot be specified.
"other tenant folder"
A resource that is being used by a powered on L-Server cannot be moved to another tenant.
Stop the L-Server before moving the resource.
The following resources cannot be moved:
Powered on L-Servers
Folders that contain powered on L-Servers
Resource pools used by powered on L-Servers
Folders or resource pools that contain resource pools used by powered on L-Servers
"The resources used are permission denied."
Access authority is necessary for some resources displayed in obj, which are used by the L-Server.
Check the status of the resources used by the L-Server.
"storage is not configured properly"
The function displayed in function cannot be used as the storage has not been configured properly.
"unknown disk"
function cannot be executed, as there is an unknown disk on the resource to be operated.
"converted vm" or "converted server"
function cannot be executed, as the resource to be operated is an L-Server linked to either a configured physical server or a virtual machine.
"secondary vm of VMware FT"
function cannot be executed, as the resource to be operated is a VMware FT secondary virtual machine.
"exist spare server settings"
function cannot be executed, as the resource to be operated is a physical server for which a spare server has been configured.
"agent is not registered"
function cannot be executed, as there is no registered agent.
"Server pool,Storage pool,Network pool,Address pool,and Image pool"
The operation is valid for VM pools.
The elements in the resources registered in the resource pool cannot be displayed for the resource to be operated.
Reserve information for configuring HA cannot be displayed, as the resource to be operated is not a VM pool.
"Server pool,Storage pool,Network pool,Address pool,and Image pool"
The operation is valid for VM pools and server pools.
The resource to be operated cannot be displayed linked to L-Servers.
"VM pool,Server pool,Storage pool,Network pool,and Address pool"
The operation is valid for image pools.
The target resource cannot display image information.
When registering resources to a resource pool, and "force" is displayed
function cannot be executed, as the force option is not supported for resources other than server pools.
"Dynamic Memory is enabled"
Dynamic memory settings are enabled for the target resource.
Memory capacity cannot be changed for L-Servers for which dynamic memory settings are enabled.
"Exist"
When the VM type is something other than KVM, the Exist element cannot be specified.
"DiskLink and ServerImageLink.disk cannot be specified at the same time"
When the L-Server template with the "setting for disk deployment when specifying an image" is specified, a disk which was created (and saved) from virtual storage cannot be specified.
"remaining disk"
For the specified L-Server, a disk which was created (and saved) from virtual storage cannot be specified. The disk can be only specified for virtual L-Servers with the Hyper-V VM type.
"L-Server with snapshot"
Saved virtual disks (created from virtual storage) cannot be added to an L-Server from which a snapshot has been collected.
"not connectable disk resource from VM host"
Virtual disks that cannot be connected to from a VM host with an L-Server deployed cannot be specified.
"disk with snapshot"
deny_deldisk=true(do not delete) cannot be specified for the disk from which a snapshot has been collected.
"product version of VM management software"
In environments where an SCVMM that has not been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later is being used, one of the following operations was performed:
Connection of the L-Server to a disk that was allocated from a virtual storage and saved
Detachment (without deletion) of a disk that was allocated from a virtual storage and saved, from an L-Server.
"disk size, exist"
When the VM type is KVM and the DiskSize element is specified, specify "true" for the Exist element.
"disk link, exist"
When a disk resource created in advance is specified, "false" cannot be specified for the Exist element.
"L-Platform", "Folder", or "Tenant Folder"
The function displayed in function cannot be used with the L-Platform.
"Folder.[tag name]"
The specified resources cannot be created on resource folders or an L-Platform.
"belongs to L-Platform"
The function displayed in function cannot be used with the resources of an L-Platform.
"can not belongs to L-Platform"
Target resources cannot be created on or moved to the L-Platform.
"deny_deldisk=true is specified"
In a specified L-Server, when detaching a disk allocated from virtual storage, the disk is deleted.
"HBA address rename cannot use FCConnectionPattern."
FCConnectionPattern cannot be used in an environment where the HBA address rename service is configured.
"The resource is registered in pool"
The server displayed in obj is registered in the resource pool, so the boot agent cannot be changed.
"agent not available"
The function displayed in function cannot be used because the target managed server displayed in obj is a server that cannot use agents.
"agent available"
The target managed server displayed in obj cannot be registered as the VM host that cannot use agents because it has been registered as a server that can use agents.
"HA is required for AliveMonitoring"
When alive monitoring is enabled, None cannot be specified for the Redundancy element.
[Corrective Action]
When obj is "Target network overlaps with admin LAN"
After creating a physical L-Server, configure the IP address manually. Configure the admin and public LANs in different networks.
When obj is something other than "Target network overlaps with admin LAN"
No action is necessary.
When detail is "VMType", "Model", "CPU", "Memory", "Policy.Positioning", "NICs", "Disks.Disk.type", "Policy.SpareSelection", "CPU.NumOfCPU", "CPU.CPUPerf", "Memory.MemorySize", or "FCConnectionPattern"
Review the L-Server template to see if the above elements are used, and then perform the operation again.
If the following elements are displayed, review the XML file and perform the operation again.
CPU
Memory
CPU.NumOfCPU
CPU.CPUPerf
Memory.MemorySize
Disks.Disk.type
When obj is "network_resource_name" and detail is "AddressSet"
Specify the subnet name of the admin LAN, and perform the operation again.
When obj is "network_resource_name" and detail is "ManagementLanSubnet"
Specify a different value for the subnets of the admin and public LANs, and perform the operation again.
When creating a network resource for the admin LAN using the public LAN subnet, add the <Type>admin</Type> tag, and specify the <ManagementLanSubnet> tag.
When obj is "network_resource_name" and detail is "Pool"
After deleting the Pool element, perform the operation again.
obj is "network_resource_name" and detail is "Vlanautosetting"
Delete vlanautosetting from the ExternalPorts element in the XML definition and then perform the operation again.
When obj is "DefaultGateway" and detail is "ManagementLanSubnet name = "" , Type = admin"
For the admin LAN connected directly to a manager, do not specify the default gateway.
When function is "convert L-Server" and detail is "storage is not configured properly"
Check that the storage has been configured for linking the configured physical server to the L-Server.
When detail is "some settings exist"
When registering a configured physical server to a resource pool, specify the -force option and perform the operation again.
When detail is "Dynamic Memory is enabled"
When changing the memory capacity with dynamic memory enabled
Perform the operation using VM management software.
The changed values are reflected on the configuration of the L-Server by periodic queries made to the VM management software.
For details on the reflection of L-Server configuration by periodic queries, refer to "11.2 Modifying an L-Server" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When changing the memory capacity using Resource Orchestrator
Change the settings of the target virtual machine to static memory using VM management software.
After the change has been reflected on the L-Server, perform the operation again.
When detail is "release MacAddress" or "reserve MacAddress"
After deleting the L-Server, create an L-Server again.
When detail is "illegal disk type"
Specify a disk resource for VM guest, and perform the operation again.
When detail is "disk unregistration"
Use the unregister command to release the registration of obj disk resources, and perform the operation again.
When detail is "L-Platform"
Perform the operation, using the command for L-Platforms.
When detail is "Folder"
Create a resource, using the command for the resource folder.
When detail is "Tenant Folder"
Perform the operation, using the command for tenants.
When detail is "can not belongs to L-Platform"
Specify the resource folder or tenant folder for the creation or destination resource folder, and perform the operation again.
When detail is "deny_deldisk=true is specified"
In the specified L-Server, when detaching a disk allocated from virtual storage, the disk is deleted.
To reduce, specify deny_deldisk=false. The deny_deldisk argument may also be omitted.
The -deny_deldisk=true argument can only be specified when detaching disks from physical L-Servers or virtual L-Servers with the VM type Hyper-V.
When detail is "DiskLink and ServerImageLink.disk cannot be specified at the same time"
Modify the L-Server template or change the setting so that disks which were created (and saved) from virtual storage will not be used, and then perform the operation again.
When detail is "remaining disk"
Review the VM type and environment, and then perform the operation again.
When detail is "L-Server with snapshot"
When adding a saved virtual disk (created from virtual storage) to a virtual L-Server, delete all snapshots of that virtual L-Server first, and then perform the operation again.
When detail is "not connectable disk resource from VM host"
Check the VM management software to see if the VM host with an L-Server deployed can connect to virtual disks, and then perform the operation on the L-Server which can connect to virtual disks.
When detail is "disk with snapshot"
When saving a virtual disk (created from virtual storage), delete all snapshots of that virtual L-Server first, and then perform the operation again.
When detail is "product version of VM management software"
Check if the SCVMM being used has been upgraded to Microsoft(R) System Center 2012 Virtual Machine Manager or later. If not, upgrade SCVMM and then perform the operation again.
When detail is " HBA address rename cannot use FCConnectionPattern."
Re-execute without specifying FCConnectionPattern.
When function is "registering agent" and detail is "agent not available"or "agent available"
Perform one of the following corrective actions:
Make the target managed server displayed in obj the server for VM hosts which can use agents by modifying the settings in the definition file explained in the following section. Then, register the agent.
"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"
Make the target managed server displayed in obj the server for VM hosts which cannot use agents by deleting that server. After this, register the server and agent, referring to the following section:
"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 detail is "HA is required for AliveMonitoring"
Specify "HA" for the Redundancy element, and then perform the operation again.
[Description]
Refer to the explanation in "Message number 67295" in the "Messages VE".
There are also the following cases for Resource Orchestrator:
When registering resources to resource pools
obj has already been registered in a resource pool.
When moving resources from the resource pool
A resource that has the same name as obj is registered in the destination resource pool.
When performing user authentication using directory service
obj is already registered in one of the following locations. The names are not-case-sensitive.
Root folder
Same resource folder
Same tenant folder
Inside the same resource pool
When importing the configuration information for the operation of Disaster Recovery environments
There are multiple VM guests or VM hosts specified in obj.
When the name on management software has been changed, reverse the change, and perform the operation again.
When operating network devices
There are multiple network devices specified in obj.
When creating a L-Server, resource pool, folder, or tenant
There are the following possibilities:
A resource with the same name already exists.
When created directly under the orchestration tree, an L-Server template with the same name may exist.
[Corrective Action]
Refer to the explanation in "Message number 67295" in the "Messages VE".
When registering resources to resource pools
With Resource Orchestrator, if obj has already been registered in a resource pool, it is displayed because currently registered resources cannot be registered. No action is necessary.
When moving resources from the resource pool
Resources with the same name cannot be registered on this product. Change the resource name and then try again.
When performing user authentication using directory service
A resource with the same name as an already registered resource is displayed, because it cannot be registered at the same time. Change the resource name, and then perform the operation again.
When operating network devices
Execute the command again, referring to "3.5 Changing LAN Switch Settings" of the "User's Guide for Infrastructure Administrators (Resource Management) CE", after changing the network device name using the GUI.
When creating a L-Server, resource pool, folder, or tenant
Change the name and perform creation again.
