This section explains messages starting from VSYS10100.
Failed to acquire authorization information from the access controller. Org-ID=[{0}], User-ID=[{1}], Detail=[{2}]
Description
An attempt to obtain authorization information from access control has failed.
Parameter
{0}: Tenant name
{1}: User ID
{2}: Detailed information
Corrective Action
Check whether the User ID exists.
Refer to "Chapter 3 Configuring Users and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for details.
Invalid folder name. [System-ID: {0}][Folder-Name: {1}]
Description
An invalid folder name has been specified.
Parameter
{0}: L-Platform ID
{1}: Folder name
Corrective Action
Check whether the folder name has been specified correctly.
Invalid L-Server name. [Server-ID: {0}][L-Server-Name: {1}]
Description
An invalid L-Server name has been specified.
Parameter
{0}: Server ID
{1}: L-Server name
Corrective Action
Check whether the L-Server name has been specified correctly.
Configuration [key=hostname-header] error. [System-ID:{0}]
Description
An attempt to set the host name has failed because there is an error with the definition file.
Parameter
{0}: L-Platform ID
Corrective Action
Check for any error with the "hostname-header" settings in the following file.
[Windows Manager]
Installation_folder\RCXCFMG\config\vsys_config.xml
[Linux Manager]
/etc/opt/FJSVcfmg/config/vsys_config.xml
Counter has overflowed. [System-ID: {0} counter: {1}]
Description
The serial number counter for the host name setup function has overflowed.
Parameter
{0}: L-Platform ID
{1}: Key name of the counter
Corrective Action
Reset the serial numbers.
Alternatively, change the definitions for the host name settings.
Duplicate host names. [System-ID: {0} Server Name: {1}]
Description
A host name is specified more than once.
Parameter
{0}: L-Platform ID
{1}: Server name
Corrective Action
Specify a server name that does not duplicate the name of an existing server, and then execute the deployment again.
Invalid host name. [System-ID: {0} Server Name:{1}]
Description
The host name is invalid.
Parameter
{0}: L-Platform ID
{1}: Server name
Corrective Action
When the method for setting the virtual server host name is set to "server name", ensure that invalid characters for the host name are not used in the server name.
When the method for setting the virtual server host name is set to "prefix + serial number", ensure that invalid characters for the host name are not used in the prefix settings.
When the method for setting the virtual server host name is set to "tenant name + serial number", ensure that invalid characters for the host name are not used in the tenant name.
Characters that can be used for the host name are alphanumerics and hyphens (-). Names consisting solely of numbers are not allowed.
Refer to "9.4 Setting the Host Names for Virtual Servers" in "Setup Guide CE" for information on setting the host name for the virtual server.
Key not found. [Key: {0}]
Description
The specified key name does not exist.
Parameter
{0}: Key name
Corrective Action
Specify a valid key name in cfmg_resethostnamecounter (Reset Serial Numbers for Host Name Settings) command, and then re-execute the command.
Configuration [key=default-import-os] error. [L-Server Name: {0}]
Description
An attempt to import an L-Server has failed because there is an error with the definition file.
Parameter
{0}: L-Server name
Corrective Action
Check for any error with the "default-import-os" settings in the following file.
[Windows Manager]
Installation_folder\RCXCFMG\config\vsys_config.xml
[Linux Manager]
/etc/opt/FJSVcfmg/config/vsys_config.xml
The status of Server[{0}] is [CLONING]
Description
The server is currently cloning.
Parameter
{0}: Server ID
Corrective Action
Check the status of the managed server, and then try again.
User doesn't have the right of access. [Org-ID:{0}, User-ID: {1}, API:{2}, Status{3}, Code:{4}, Message:{5}]
Description
The user does not have the operated access authority.
Parameter
{0}: Tenant name
{1}: User ID
{2}: API
{3}: Status
{4}: Code
{5}: Message
Corrective Action
It is not possible to operate it because there is no access authority in the User ID.
Refer to "Chapter 3 Configuring Users and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for details.
There are no normal status systems in the tenant. [Org-ID:{0}]
Description
There is no normal status L-Platforms within the tenant.
Parameter
{0}: Tenant name
Corrective Action
Check the L-Platform status and re-execute.
There are no servers to be started in the system. [System-ID:{0}]
Description
There are no servers ready to be started in the L-Platform.
The server whose boot priority is set to 0 is not the target of this operation.
Parameter
{0}: L-Platform ID
Corrective Action
Check the status of the server in the L-Platform and re-execute.
To have a server the target of this operation, set the server's boot priority to the value other than 0.
There are no servers to be stopped in the system. [System-ID:{0}]
Description
There are no servers ready to be stopped in the L-Platform.
The server whose boot priority is set to 0 is not the target of this operation.
Parameter
{0}: L-Platform ID
Corrective Action
Check the status of the server and re-execute.
To have a server the target of this operation, set the server's boot priority to the value other than 0.
There are no servers to be started in the tenant. [Org-ID:{0}]
Description
There are no servers ready to be started in the tenant.
The server whose boot priority is set to 0 is not the target of this operation.
Parameter
{0}: Tenant name
Corrective Action
Check the status of the server and re-execute.
To have a server the target of this operation, set the server's boot priority to the value other than 0.
There are no servers to be stopped in the tenant. [Org-ID:{0}]
Description
There are no servers ready to be stopped in the tenant.
The server whose boot priority is set to 0 is not the target of this operation.
Parameter
{0}: Tenant name
Corrective Action
Check the status of the server and re-execute.
To have a server the target of this operation, set the server's boot priority to the value other than 0.
Status returned from CBRM is illegal. [System-ID:{0}]
Description
The response status code received from the resource management function is incorrect.
Parameter
{0}: L-Platform ID
Corrective Action
Continue by implementing measures in accordance with the displayed messages VSYS10095 or VSYS10096.
Status returned from CBRM is illegal. [Org-ID:{0}]
Description
The response status code received from the resource management function is incorrect.
Parameter
{0}: Tenant name
Corrective Action
Continue by implementing measures in accordance with the displayed messages VSYS10095 or VSYS10096.
Starting all servers in all tenants is not supported.
Description
Batch server start-up for all tenants is not supported.
Corrective Action
Specify a particular tenant and re-execute
Stopping all servers in all tenants is not supported.
Description
Batch server shutdown for all tenants is not supported.
Corrective Action
Specify a particular tenant and re-execute
All servers that can be started in the system are already running. [System-ID:{0}]
Description
All servers that can be started within the L-Platform are already running.
Parameter
{0}: L-Platform ID
Corrective Action
Check the status of the server and re-execute.
All servers that can be stopped in the system are already stopped. [System-ID:{0}]
Description
All servers that can be stopped within the L-Platform are already stopped.
Parameter
{0}: L-Platform ID
Corrective Action
Check the status of the server and re-execute.
All servers that can be started in the tenant are already running. [Org-ID:{0}]
Description
All servers that can be started within the tenant are already running.
Parameter
{0}: Tenant name
Corrective Action
Check the status of the server and re-execute.
All servers that can be stopped in the tenant are already stopped. [Org-ID:{0}]
Description
All servers that can be stopped in the tenant are already stopped.
Parameter
{0}: Tenant name
Corrective Action
Check the status of the server and re-execute.
Target resource is busy. [code:{0}][message:{1}]
Description
The target is busy.
Parameter
{0}: Resource management function message ID
{1}: Resource management function message
Corrective Action
Wait for a brief period and then try again.
The server of Solaris Container is included in this L-Platform[{0}].
Description
The Solaris Zones server is included in the L-Platform.
Parameter
{0}:L-Platform ID
Corrective Action
Confirm that the Solaris Zones server is not included in the displayed L-Platform.
ServerType [{0}] isn't found.
Description
The specified L-Server template cannot be found.
Parameter
{0}: L-Server Template name
Corrective Action
Check whether the specified L-Server template exists.
Network[{0}] does not exist in this L-Platform[{1}].
Description
The specified network does not exist in the L-Platform.
Parameter
{0}: Network ID
{1}: L-Platform ID
Corrective Action
Check whether the network exists.
System disk isn't specified. [Image-ID:{0}]
Description
The disk size of the image is not specified.
Parameter
{0}: Image ID
Corrective Action
Ensure that the disk size of the image is specified.
Management software is not registered. [Software:{0}]
Description
The required server management product has not been registered.
Parameter
{0}: Name of the server management product
Corrective Action
Check the status of the server management product.
NIC[NIC-NO:{1}] does not exist in this L-Server[SERVER-ID:{0}].
Description
An NIC with the specified number does not exist in the L-Server.
Parameter
{0}: Server ID
{1}: NIC number
Corrective Action
Ensure that the specified server or NIC is correct.
NIC or NIC GROUP exists on the network[{0}].
Description
NIC or NIC GROUP exists on the specified segment.
Parameter
{0}: Network ID
Corrective Action
Ensure that the specified segment is correct.
These parameters cannot be specified at a time[{0},{1}].
Description
These specified parameters cannot be specified at the same time.
Parameter
{0}: Specified parameter
{1}: Specified parameter
Corrective Action
Ensure that the specified parameter is correct.
Some servers do not satisfy conditions for the operation in this L-Platform[{0}].
Description
The L-Platform contains servers that do not satisfy operating conditions.
Parameter
{0}: L-Platform ID
Corrective Action
Check the VM type and the OS of the server, and the status of the server management product in the L-Platform.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Target resource is locked. [code:{0}][message:{1}]
Description
The processing failed because the operation target contains locked resources.
Parameter
{0}: Resource management function message ID
{1}: Resource management function message
Corrective Action
Specify resources that are unlocked, and perform the processing.
The server[Server-ID:{0}] is one of the SLB backend servers.
Description
The specified server is a target for distribution by the server load balancer.
Parameter
{0}: Server ID
Corrective Action
Check whether the specified server is correct.
The nic[Server-ID:{0} nic-No:{1}] is attached to one of the SLB backend servers.
Description
The specified NIC is connected to a server that is target for distribution by the server load balancer.
Parameter
{0}: Server ID
{1}: NIC number
Corrective Action
Check whether the specified NIC is correct.
Snapshot[Resource-ID:{1}] does not exist in this L-Server[SERVER-ID:{0}].
Description
The snapshot with the specified resource ID does not exist in the L-Server.
Parameter
{0}: Server ID
{1}: Resource ID
Corrective Action
Ensure that the specified server or resource ID is correct.
Resource[Global-IP:{0}] does not exist in this L-Platform[{1}].
Description
The specified global IP address does not exist in the L-Platform.
Parameter
{0}: Global IP address
{1}: L-Platform ID
Corrective Action
Ensure that the specified L-Platform and global IP address are correct.
Resource[Global-IP:{0}] already exists in this L-Platform[{1}].
Description
The specified global IP address already exists in the L-Platform.
Parameter
{0}: Global IP address
{1}: L-Platform ID
Corrective Action
Ensure that the specified L-Platform and global IP address are correct.
If the above does not apply, contact Fujitsu technical staff.
Snapshot[Resource-ID:{1}][Disk-ID:{2}] already exists in this L-Server[SERVER-ID:{0}].
Description
The snapshot with the specified resource ID and disk ID already exists.
Parameter
{0}: Server ID
{1}: Resource ID
{2}: Disk ID
Corrective Action
Ensure that the specified snapshot is correct.
If the above does not apply, contact Fujitsu technical staff.
Backup history[Task-ID:{0}] already exists.
Description
The backup history with the specified task ID already exists.
Parameter
{0}: Task ID
Corrective Action
Ensure that the specified backup history is correct.
If the above does not apply, contact Fujitsu technical staff.
User doesn't have the right of access. [Org-ID:{0}, User-ID:{1}, L-Platform ID:{2}, OperationGroup:{3}]
Description
The user does not have the operated access authority.
Parameter
{0}: Tenant name
{1}: User ID
{2}: L-Platform ID
{3}: Operation privileges
Corrective Action
It is not possible to operate it because there is no access authority in the User ID.
Refer to "Chapter 3 Configuring Users and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for details.
User doesn't have the right of access. [User-ID:{0}, OperationGroup:{1}]
Description
The user does not have the operated access authority.
Parameter
{0}: User ID
{1}: Operation privileges
Corrective Action
It is not possible to operate it because there is no access authority in the User.
Refer to "Chapter 3 Configuring Users and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" for details.
Deleting the specified server[Server-ID:{0}] is not supported.
Description
The specified server cannot be deleted.
Parameter
{0}: Server ID
Corrective Action
Check the VM type and the OS of the server, and the status of the server management product.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
Deleting the specified disk[Disk-ID:[{0}] is not supported.
Description
The specified disk cannot be deleted.
Parameter
{0}: Disk ID
Corrective Action
Check the VM type and the OS of the server, and the status of the server management product.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
The disk[Disk-Name:[{0}] cannot be attached because it is used by another server.
Description
The specified disk is already used by another server.
Parameter
{0}: Disk resource name
Corrective Action
A disk already used by another server cannot be attached.
Detach it from that server, or attach another disk.
Raw disk is attached to the server[Server-ID:{0}].
Description
A disk with the type "Raw Disk" is connected to the server.
Parameter
{0}: Server ID
Corrective Action
Delete the existing disk, and reexecute the command.
The value of VDI User is invalid.
Description
An invalid VDI user name is specified.
Corrective Action
Check if the user name specified for the VDI user is correct.
A VM of the VDI User already exists in the VDI pool.
Description
The VDI user's virtual machine exists in the specified VDI pool.
Corrective Action
Two or more virtual machines of one VDI user cannot be registered in a VDI pool.
Check whether the VDI user name or the VDI pool has been specified correctly.
Operations of the server[Server-ID:{0}] is not supported.
Description
No operations are supported for the specified server.
Corrective Action
Check whether the specified server is correct.
When the above actions do not solve the problem, collect this message and the investigation data, and then contact Fujitsu technical staff.
The domain name of VDI User is invalid.
Description
The domain name of the VDI user is invalid.
Corrective Action
Check if the domain name of the VDI user is correct.