This section explains messages starting from VSYS10600.
Resource [NETWORK-ID:{0}] doesn't exist.
Description
The network resource does not exist.
Parameter
{0}: Network ID
Corrective Action
A conflict has occurred with the internal processing.
Collect this message and the investigation data, and then contact Fujitsu technical staff.
Status that related Image-ID [SERVER-ID:{0}] doesn't exist in table[image].
Description
The image_id associated with the server_id for the "image" table cannot be obtained.
Parameter
{0}: Server ID
Corrective Action
Check whether there is a problem with the specified server ID.
Check whether there are any problems with the <initialPassword> tag in the image information file that has been registered.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [ORG-ID:{0}] doesn't exist.
Description
The management function resource does not exist.
Parameter
{0}: Tenant name
Corrective Action
Check whether there is a problem with the specified tenant name.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
GIP doesn't complete detach exists. [System-ID:{0}]
Description
There is a global IP address that has not been completely detached.
Parameter
{0}: L-Platform ID
Corrective Action
Detach the global IP address for the firewall, and then try again.
The [Disk-Size:{0}] of less than or equal is specified.
Description
The specified value is less than or equal to the current disk size.
Parameter
{0}: Disk size
Corrective Action
Specify a value greater than the current disk size.
Can not specify a storage pool of the server [vm_type:{0}].
Description
The storage pool cannot be specified.
Parameter
{0}: Server virtualization software
Corrective Action
Make the storage pool [Automatic].
Unsupported operation. [Server-ID:{0}] is [vm_type:{1}]
Description
The operation is not supported.
Parameter
{0}: Server ID
{1}: Server VM type
Corrective Action
Snapshot and restore are not possible if the server virtualization software is RHEL-KVM.
If the above does not apply, check whether the default VM type specification (default-vmtype) in the following configuration file is correct.
[Windows Manager]
Installation_folder\RCXCFMG\config\vsys_config.xml[Linux Manager]
/etc/opt/FJSVcfmg/config/vsys_config.xml
If there is an error with the settings in vsys_config.xml, correct the file and then restart the RCXCF_VSYS WorkUnit by using either the Interstage Management Console or the isstopwu command and the isstartwu command.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE" for information on how to start WorkUnits.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [Software-ID:{0} Patch-ID{1}] doesn't exist in server[Server-ID:{2}].
Description
The patch information corresponding to the specified patch ID does not exist.
Parameter
{0}: Software ID
{1}: Patch ID
{2}: Server ID
Corrective Action
Ensure that the specified patch ID is correct.
When the type of VM is the "RHEL-Xen", the MAC Address must be assigned.
Description
If the VM type is "RHEL-Xen", a MAC address must be specified.
Corrective Action
Ensure that the L-Server template VM type setting is correct.
When the type of VM is the "VMware" or "Hyper-V", the MAC Address can't be assigned.
Description
If the VM type is either "VMware" or "Hyper-V", the MAC address cannot be specified.
Corrective Action
Do not specify a MAC address.
Only one vnic can be set to control NIC.
Description
No more than one control NIC can be specified.
Corrective Action
Specify only one control NIC.
The vnics' number can't exceed the max number of nics according to the image Id assigned.
Description
The number of NICs exceeds the maximum number of NICs that has been set for the specified image ID.
Corrective Action
Check the maximum number of NICs that has been set for the specified image ID, and change the number of NICs so that it does not exceed the maximum number.
Overflow seqNum or the [System-ID: {0}] has a problem. Can't create VDISK-ID.
Description
A disk ID cannot be created, either because there has been an overflow for the number of digits of the disk ID serial number that is assigned automatically, or because there is a problem with the system.
Parameter
{0}: L-Platform ID
Corrective Action
Check whether adding one to the last disk ID serial number already on the L-Platform causes a digit overflow. (The disk ID serial number that is assigned automatically can have up to four digits.)
The [Disk-Size:{0}] assigned overflowed its range.
Description
Specify the disk capacity so that it does not exceed the maximum capacity. The maximum value for the disk capacity is 99999.9 GB.
Parameter
{0}: Disk capacity
Corrective Action
Specify the disk capacity so that it does not exceed the maximum capacity.
The disk name can't be the same.
Description
The specified disk name already exists.
Corrective Action
Specify a disk name that does not exist.
The vdisks' number can't exceed the max number of disks according to the image Id assigned.
Description
The specified number of disks exceeds the maximum number of disks that has been set for the specified image ID.
Corrective Action
Check the maximum number of disks that has been set for the specified image ID, and change the number of disks so that it does not exceed the maximum number.
The [Disk-Size:{0}] exceed the max disk size according to the image Id assigned.
Description
The specified disk capacity exceeds the maximum disk capacity that has been set for the specified image ID.
Parameter
{0}: Disk capacity
Corrective Action
Check the maximum disk capacity that has been set for the specified image ID, and change the disk capacity so that it does not exceed the maximum capacity.
The [Image-ID:{0}] doesn't exist in the table software_link.
Description
The specified image ID does not exist in the "software_link" table.
Parameter
{0}: Image ID
Corrective Action
Ensure that the specified image ID is correct.
The [Image-ID:{0}] doesn't have the OS.
Description
The specified image ID does not contain operating system information.
Parameter
{0}: Image ID
Corrective Action
Specify an image ID that contains operating system information.
Because the VM type is "RHEL-Xen", the Mac Address must be assigned.
Description
If the VM type is "RHEL-Xen", a MAC address must be specified.
Corrective Action
Ensure that the L-Server template VM type setting is correct.
The Image-ID of the [SERVER-ID: {0}] doesn't exist.
Description
The cloning image specified in server {0} does not exist.
Parameter
{0}: Server ID
Corrective Action
Ensure that the specified Image-ID is correct.
At least one of the cpuPerf, numOfCpu or memorySize should be assigned.
Description
None of CPU performance, CPU number, or memory size is specified.
Corrective Action
Specify at least one of CPU performance, CPU number, or memory size
The VM-Type of the [SERVER-ID:{0}] doesn't exist.
Description
The VM type specified in server {0} does not exist.
Parameter
{0}: Server ID
Corrective Action
Ensure that the specified VM-Type is correct.
Because there is only one server in the system[{0}], it can't be released.
Description
Because there is only one server in the L-Platform, the server cannot be returned.
Parameter
{0}: L-Platform ID
Corrective Action
Either return the L-Platform, or create a new server before returning this server.
Failed to get Lserver-Type. [SERVER-ID:{0}]
Description
The processing to get the L-Server type failed.
Parameter
{0}: Server ID
Corrective Action
A conflict has occurred with the internal processing.
Collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource[SERVER-ID:{0}] doesn't exist.
Description
When the server recovery was launched, the specified server could not be found.
Parameter
{0}: Server ID
Corrective Action
Check whether there is any error with the file that was imported using the disaster recovery function.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [DISK-ID:{0}] doesn't exist.
Description
When the server recovery was launched, the specified disk could not be found.
Parameter
{0}: Disk ID
Corrective Action
Check whether there is any error with the file that was imported using the disaster recovery function.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [SERVER-ID:{0}] already exist.
Description
A server with the specified server ID already exists when the server recovery is launched.
Parameter
{0}: Server ID
Corrective Action
Check whether there is any error with the file that was imported using the disaster recovery function.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [DISK-ID:{0}] already exist.
Description
A disk with the specified disk ID already exists when the server recovery is launched.
Parameter
{0}: Disk ID
Corrective Action
Check whether there is any error with the file that was imported using the disaster recovery function.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Resource [Disk Index:{0}] doesn't exist.
Description
No disk with the specified disk number exists.
Parameter
{0}: Disk number
Corrective Action
Check whether there is any error with the file that was imported using the disaster recovery function.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Failed to get snapshot ID. [SERVER-ID:{0}]
Description
An attempt to get a snapshot ID has failed.
Parameter
{0}: Server ID
Corrective Action
A conflict has occurred with the internal processing.
Collect this message and the investigation data, and then contact Fujitsu technical staff.
Failed to get cloningmaster ID. [SERVER-ID:{0}]
Description
The processing to get the cloning master ID failed.
Parameter
{0}: Server ID
Corrective Action
A conflict has occurred with the internal processing.
Collect this message and the investigation data, and then contact Fujitsu technical staff.
The number of servers exceeded the max number of template.
Description
The maximum number of servers was exceeded.
Corrective Action
Check the number of servers deployed in the L-Platform.
The number of servers exceeded the max number of network. [NETWORK-ID:{0}]
Description
The maximum number of servers in the network was exceeded.
Parameter
{0}: NetworkID
Corrective Action
Check the number of servers deployed in the displayed network.
The image can't use the pool. [POOL-NAME: {0}]
Description
The server using the specified image cannot be deployed to the displayed pool.
Parameter
{0}: Pool name
Corrective Action
Ensure that an appropriate image or pool has been specified.
Can't find the specified pool. [POOL-NAME:{0}]
Description
The specified Pool could not be found.
Parameter
{0}: Pool name
Corrective Action
Ensure that the specified Pool name is correct.
The state of the power supply of the server cannot be acquired. [Server-ID: {0}]
Description
The state of the power supply of the specified server cannot be acquired.
Parameter
{0}: Server ID
Corrective Action
Check whether the specified server ID is valid.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Tag [{0}] is required in the request XML.
Description
The specified XML file does not contain a required tag.
Parameter
{0}: Tag name
Corrective Action
Ensure that the XML file is correct.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Pool must be specified when using RHEL-KVM.
Description
A pool must be specified when using KVM.
Corrective Action
Specify a Pool, and then try again.
Storage Pool must be specified when using RHEL-KVM.
Description
A storage pool must be specified when using KVM.
Corrective Action
Specify a Storage Pool, and then try again.
Only existing disk can be attached when using RHEL-KVM.
Description
Only an existing disk can be attached when using KVM.
Corrective Action
Use an existing disk.
The server name[{0}] is illegal.
Description
The specified server name is invalid.
Parameter
{0}: Server name
Corrective Action
If server name has been selected as the method for setting L-Server names when setting the method for setting resource names in the following file, it is not possible to deploy a Solaris Zones server if the following server names are specified.
Solaris 10: Server names starting with "SUNW"
Solaris 11: Server names starting with "SYS"
Specify a name other than those listed above.
[Windows Manager]
Installation_folder\RCXCFMG\config\vsys_config.xml[Linux Manager]
/etc/opt/FJSVcfmg/config/vsys_config.xml
Resource[SERVER-ID:{0},NIC-NO:{1}] already exist.
Description
An NIC with the specified server ID and NIC number already exists.
Parameter
{0}: Server ID
{1}: NIC number
Corrective Action
Ensure that the specified server or NIC is correct.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
One of the NIC of the physical server must connect to admin LAN.
Description
One of the NICs of a physical server needs to be connected to the admin LAN.
Corrective Action
Connect one NIC to the admin LAN.
When creating a physical server by using "CreateLServer" of the L-Platform API, it is necessary to specify the admin LAN for controlNetworkId.
Only existing disk can be attached to the server. [SERVER-ID:{0} vm_type:{1}]
Description
Only existing disks can be attached to the specified server.
Parameter
{0}: Server ID
{0}: VM type
Corrective Action
Use an existing disk.
The disk attached to another server cannot be attached to the server[Server-ID:{0} vm_type:{1}].
Description
A disk attached to another server cannot be attached to the specified server.
Parameter
{0}: Server ID
{0}: VM type
Corrective Action
The disk cannot be attached using this software.
If attaching the disk is necessary, contact the infrastructure administrator.
The image for VDI cannot be used. [Image-ID:{0}].
Description
Images for which VDI coordination is enabled cannot be specified.
The image for VDI cannot be specified.
Parameter
{0}: Image ID
Corrective Action
Specify an image that does not have VDI coordination enabled.
The connect info[{0}] is already set another server.
Description
The specified VDI management server connection information is configured for another server.
Parameter
{0}: VDI management server connection information
Corrective Action
To change the connection information to the same as that set on another server, the force option must be specified.
Check that the specified VDI management server connection information is correct.
All parameters [vdiServer, vdiConnectInfo, vdiPool, vdiUser] must be specified.
Description
The VDI management server, VDI management server connection information, VDI pool name, and VDI user name must all be specified.
Corrective Action
When setting parameters for VDI coordination for servers for which VDI coordination is not enabled, the VDI management server, VDI management server connection information, VDI pool name, and VDI user name must all be specified.
The host name[{0}] is illegal.
Description
The specified host name is invalid.
Parameter
{0}: Host name
Corrective Action
If host name has been selected as the method for setting L-Server names when setting the method for setting resource names in the following file, it is not possible to deploy a Solaris Zones server if the following host names are specified.
Solaris 10: Host names starting with "SUNW"
Solaris 11: Host names starting with "SYS"
Specify a name other than those listed above.
[Windows Manager]
Installation_folder\RCXCFMG\config\vsys_config.xml[Linux Manager]
/etc/opt/FJSVcfmg/config/vsys_config.xml
The VM host cannot be found in the pool. [VM Host:{0}][Pool:{1}]
Description
The VM host was not found in the specified VM pool.
Parameter
{0}: VM pool name
{1}: VM host name
Corrective Action
Ensure that the specified VM pool name and VM host name are correct.
The VM host cannot be found. [VM Host:{0}]
Description
The specified VM host does not exist.
Parameter
{0}: VM host name
Corrective Action
Ensure that the specified VM host name is correct.
If the VM pool in which the specified VM host is registered is a global pool, check whether the operating user has access authority for the tenant that is the deployment destination.
The Virtual Storage cannot be found in the pool. [Virtual Storage:{0}][Pool:{1}]
Description
The virtual storage resource was not found in the specified storage pool.
Parameter
{0}: Storage pool name
{1}: Virtual storage name
Corrective Action
Ensure that the specified storage pool name and virtual storage name are correct.
The Virtual Storage cannot be found. [Virtual Storage:{0}]
Description
The specified virtual storage was not found.
Parameter
{0}: Virtual storage name
Corrective Action
Ensure that the specified virtual storage name is correct.
If the storage pool in which the specified virtual storage is registered is a global pool, check whether the operating user has access authority that is the tenant of the deployment destination.