This section explains the 672XX message series.
Description
Command execution was canceled. For details, refer to the event output at the same time.
Corrective Action
Refer to the event output at the same time.
Description
There are errors in the definition file.
Corrective Action
Take corrective action for the content displayed for detail.
When detail is "resource not found."
The resource was not found.
Check if the resource exists, correct the definition file, and then perform the operation again.
Check the specified resource.
When the type of resource is tenant, check that the tenant exists.
When the type of resource is pool, check that the VM pool exists.
When the type of resource is physical server, check that the VM host exists and the VM type is "RHEL-KVM".
When resource is "host_config_RHEL-KVM.rcxprop", check that the definition file exists.
When detail is "line is invalid."
There is an error in the "line" line of the definition file.
Check the format, and retry the operation.
Description
Deletion of the cloning image obj failed.
Corrective Action
Refer to the other messages output at the same time.
[Common to All Editions]
Description
The IP address or MAC address specified for obj cannot be used because it is already in use.
There may also be the following cases:
Link information has already been defined for the port of the network device displayed in obj.
Link information has already been defined for the NIC index of the rack mount server displayed in obj.
Corrective Action
Check and correct the option argument specified, and then perform the operation again.
When this message is output, the IP address or MAC address may already be being used for one of the following registered devices.
Chassis
LAN switches
Network devices
Admin servers
Managed servers
Power monitoring devices
For other cases, perform the following corrective actions.
When link information has already been defined for the port of the network device displayed in obj
Define the correct link information in the network configuration information (XML definition), and perform the operation again.
When link information has already been defined for the NIC index of the rack mount server displayed in obj.
Define the correct link information in the network configuration information (XML definition), and perform the operation again.
[Cloud Edition]
Description
The IP address or MAC address specified for obj cannot be used because it is already in use.
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 storage pool. Therefore, disk registration cannot be released.
The specified disk resource is used by an L-Server. Therefore an L-Server cannot be created or modified.
The specified disk resource is used by another L-Server. Therefore, a configured virtual machine cannot be linked with L-Server.
In obj, the MAC address given in "mac_address=" has already been used.
Corrective Action
Check and correct the option argument specified, and then perform the operation again.
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.
Check and correct the value specified in the XML and then perform the operation again.
When two or more disks are defined for a virtual L-Server, please operate again after changing a specification value according to the following.
A specific disk resource is specified for the definition of all disks.
A specific disk resource is not specified for the definition of all disks.
When you do not use obj for other L-Servers, remove obj from the L-Server.
When obj is used with other L-Servers, the executed operation is not supported.
In obj, when the MAC address given in "mac_address=" has already been used
Perform the operation again after correcting the specified MAC address.
[Virtual Edition]
Description
The command cannot be executed because another command is being executed by obj.
In the following cases, a resource name other than the one specified is displayed for obj.
When power operation of a chassis is performed while another process is being executed for a resource mounted in the chassis
When takeover of operations has been performed for a server which has been switched to a spare server and there is another physical OS or VM host that has the server configured as a spare server, and that physical OS or VM host is executing another process
Corrective Action
When obj is "Manager task"
Check the operating status of the admin server. After the operation being executed is complete, perform the operation again.
If this message is displayed while the admin server is stopped, operations being executed on the admin server may remain in the database. Start the admin server to complete the operations being executed on the admin server, or perform the operation again after restoring the collected configuration definition information.
When obj is something other than "Manager task"
Check the object obj and perform the operation again after the other command is complete.
However, when performing registration or deletion of managed servers or LAN switches in the same chassis, commands can only be performed for one resource at a time. This message will be displayed when commands are performed for multiple resources at the same time.
[Cloud Edition]
Description
The requested process cannot be performed as another process is already being performed.
When operations such as creation or starting of an L-Server are performed when the load on the manager is high, the corresponding operation may be still be being performed. Check the progress of the operation in Recent Operations or the Event Log.
When obj is VM guest name (VM guest), the VM host, which the L-Server is running on, detects that the VM guest of the L-Server does not exist, so L-Server deletion fails.
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 operating status of the admin server. After the operation being executed is complete, perform the operation again.
If this message is displayed while the admin server is stopped, operations being executed on the admin server may remain in the database. Start the admin server to complete the operations being executed on the admin server, or perform the operation again after restoring the collected configuration definition information.
When creating or starting an L-Server, while the manager is under a high load.
Check the following:
The hardware configuration of the admin server does not meet the requirements for a manager.
Refer to "6.2.1 All Editions" in the "Overview" and confirm that the hardware conditions described are met.
The CPU utilization of the admin server may be too high.
Check if any high CPU usage applications are running on the admin server.
When obj is the "VM guest name (VM guest)"
Check the name of the VM guest of the L-Server using the GUI or the CLI.
When using the GUI:
Display the ROR console.
Select the L-Server on the orchestration tree.
Select the [Resource Details] tab on the main panel, and check the guest name of the resource.
When using the CLI:
Execute the following command:
>rcxadm lserver show -name L-Server_name <RETURN> |
Check the display of "VmGuest:".
If the VM guest name is not displayed, delete the L-Server again.
If the VM guest name is displayed, check that migration is not being performed from the management screen of the VM management software, and then delete the L-Server again.
When a message is output during deletion of the L-Server, check that the VM guest name of the L-Server is not displayed, and then delete the L-Server again.
When obj is something other than the above
Wait for a short while and then repeat the operation.
Description
image has already been defined.
Corrective Action
Check and correct the object, then perform the operation again.
Description
The cloning image has not been specified.
Corrective Action
When this message is output during cloning image operation, collect the cloning image and then execute the command again.
[Virtual Edition]
Description
The system image of the managed server or the system image of the version specified does not exist.
Corrective Action
Check the system image of the relevant managed server.
If the specified version is incorrect, specify the correct version and execute the command again.
In some cases, the image file may not have been synchronized. Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE", and restart the manager service.
[Cloud Edition]
Description
The system image of the managed server or the system image of the version specified does not exist. 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. Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE", and restart the manager service.
Description
The cloning image has already been deployed to the managed server server_name.
Corrective Action
Check and correct the relevant managed server, then perform the operation again.
Description
The specified servers include servers with different settings.
Corrective Action
Check the boot agent settings for the target server.
For how to check, refer to the following:
For Virtual Edition, refer to "3.4 rcxadm server" in the "Reference Guide (Command) VE".
For Cloud Edition, refer to "3.11 rcxadm server" in the "Reference Guide (Command/XML) CE".
Target servers with the same settings and perform the operation again.
For servers with different settings, process them individually.
Description
The specified servers include servers which contain disks that are the targets of image operations.
Corrective Action
When specifying multiple servers, ensure that servers which contain disks that are already configured as the targets of image operations are not included.
For how to check, refer to the following:
For Virtual Edition, refer to "3.4 rcxadm server" in the "Reference Guide (Command) VE".
For Cloud Edition, refer to "3.11 rcxadm server" in the "Reference Guide (Command/XML) CE".
Process servers which contain disks that are already configured as the targets of image operations individually.
[Virtual Edition]
Description
There is no spare server that matches all of the following conditions. Or the spare server specified does not meet all of the following conditions.
Power control is possible
The status is "normal", "warning", or "stop"
When the spare server is a VM host, it must meet all of the following conditions:
HBA address rename settings are configured, and an agent is registered
The status is "normal" or "warning"
A VM guest does not exist on a VM host (when the settings are not configured to switch to a spare server containing a VM guest)
[Citrix Xen]
It is not configured as the pool master (when the VM host is Citrix XenServer)
The server is not set as the switchover target for another switchover event
The server belongs to the same subnet as the primary server
Corrective Action
Perform one of the following corrective actions:
After checking there is a spare server that matches the above conditions, perform the operation again.
Specify a spare server that meets the above conditions, and then perform the operation again.
Specify a managed server that meets the above conditions as the spare server for use in server switchover, and then perform the operation again.
When setting a VM host as a spare server using the pre-configuration function, do so after importing HBA address rename settings and agent registration.
For details, refer to "12.2 Importing the System Configuration File" in the "User's Guide VE".
[Cloud Edition]
Description
When a physical L-Server has been switched over using its high availability function
There are no physical server resources available as spare servers in the specified spare server resource pool.
In other cases
There is no spare server that matches all of the conditions. Or the spare server specified does not meet all of the following conditions.
Power control is possible
The status is "normal", "warning", or "stop"
When the spare server is a VM host, it must meet all of the following conditions:
HBA address rename settings are configured, and an agent is registered
The status is "normal" or "warning"
A VM guest does not exist on a VM host (when the settings are not configured to switch to a spare server containing a VM guest)
The server is not set as the switchover target for another switchover event
The server belongs to the same subnet as the primary server
Corrective Action
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.
In other cases
Perform one of the following corrective actions:
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
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 G Definition Files" in the "Setup Guide CE".
A physical server cannot be found that has the number of FCs specified in the FC connection pattern.
Refer to "10.1.2 Storage Configuration" in the "Design Guide CE" for information on how to obtain the FC information for the physical server.
After checking there is a spare server that matches the above conditions, perform the operation again.
Specify a spare server that meets the above conditions, and then perform the operation again.
Specify a managed server that meets the above conditions as the spare server for use in server switchover, and then perform the operation again.
When setting a VM host as a spare server using the pre-configuration function, do so after importing HBA address rename settings and agent registration.
For details, refer to "10.2 Importing the System Configuration File" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Description
obj has not been recovered.
Takeover of operations was executed on managed servers that have not performed Auto-recovery or manual switching.
Corrective Action
There is no need to take corrective action, as neither Auto-recovery nor manual switching to the managed server specified has been performed.
Description
The command cannot be executed because a public IP address has not been assigned.
Corrective Action
Check if installation of the software has been completed successfully.
For how to install software, refer to the following:
For Virtual Edition, refer to "Chapter 10 Configuring the Operating Environments of Managed Servers" in the "User's Guide VE".
For Cloud Edition, refer to "Chapter 8 Configuring the Operating Environments of Managed Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
[Virtual Edition]
Description
The IP address specified is invalid.
Corrective Action
When this error occurs during the registration of a managed server
Check that the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN, and then perform the operation again.
When this error occurs when changing the admin IP address of a managed server
Check the following and perform the operation again.
That the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN
That IP addresses before and after changing are in the same subnets, when changing the admin IP addresses for a primary server or a spare server
When this error occurs when changing the admin LAN IP address of an admin server
Check that the IP address specified is the admin LAN IP address of the admin server, and then perform the operation again.
[Cloud Edition]
Description
One of the following is possible:
The IP address specified is invalid.
This message may be output when the rcxvmdiskagt command is executed.
Corrective Action
When this error occurs during the registration of a managed server
Check that the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN, and then perform the operation again.
When this error occurs when changing the admin IP address of a managed server
Check the following and perform the operation again.
That the admin LAN IP address of the specified managed server is included in the subnet of the admin LAN
That IP addresses before and after changing are in the same subnets, when changing the admin IP addresses for a primary server or a spare server
When this error occurs when changing the admin LAN IP address of an admin server
Check that the IP address specified is the admin LAN IP address of the admin server, and then perform the operation again.
If this error occurs during creation of address set resources
Check that the lead and end addresses of the address set resources are correct, and perform the operation again.
For details, refer to "3.1 rcxadm addrset" in the "Reference Guide (Command/XML) CE".
When this message is displayed when the rcxvmdiskagt command was executed
Ensure that the specified IP address is the IP address of admin LAN for the VM host, then perform the operation again.
Description
The range of IP addresses defined on the admin server is already in use.
Corrective Action
Check the range of the IP addresses (DHCP range) defined on the admin server.
Description
An error has occurred on the admin server.
Corrective Action
Check the following:
If setup of the admin server was completed successfully.
For details on setup, refer to the following:
Refer to "2.1 Manager Installation" in the "Setup Guide VE".
Refer to "2.1 Manager Installation" in the "Setup Guide CE".
Whether communication with the server management unit is possible
Use the ping command or another method to check if there is a problem with the network environment between the admin server and the server management unit.
If a cable is disconnected from the LAN connector, connect it.
Whether Write (reference and updating) authority is possessed for the SNMP setting of the management blade
Check the SNMP community name set from the ROR console.
If it was omitted, [public] will be specified.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
Check that the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values.
For details of checks and the setup method, refer to the manual of the server being used.
Refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE", and check whether the "Related services" have been started on the admin server. If they have stopped, restart them.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE", and check whether the "Related services" have been started on the admin server. If they have stopped, restart them.
For details on how to check and start services, refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE".
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE".
After starting any stopped services, perform the operation that resulted in the error again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
Acquisition of managed server information failed because the server cannot communicate with the managed server or server management unit.
Corrective Action
Check the status of the managed server and the server management unit, the value specified for the operand, and the values set for the following:
That the IP address of the server management unit of the managed server is set correctly and the server is operating normally
The SNMP community settings of server management unit for the managed server
That the SNMP community name specified from the ROR console has Read (reference authority) or Write (reference and updating) authority.
The SNMP community settings of the managed server
That the SNMP community name of the managed server has Read (reference authority).
Specify the same SNMP community name for the managed server and the server management unit.
When the managed server is a PRIMERGY or PRIMEQUEST series, that the necessary SNMP service has been configured when installing ServerView Agents, and ServerView Agents is running
That the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values
That the IP address of the managed server specified is correct
Setup of the agent for the specified managed servers was completed successfully
Network settings (such as DNS) of the admin server are correct and the execution of OS network-related commands is completed within seconds
When this message is displayed, take the following corrective actions, depending on the case:
When this message is displayed after reconfiguration of hardware properties following replacement, and there are no problems with the managed server or server management unit
There is a possibility that the reconfigured hardware properties were temporarily unobtainable.
Reconfigure the hardware properties again.
When this message is displayed during deployment of a cloning image
Registration of agents after deployment has failed. Either redeploy the cloning image or refer to step 2 in the corrective action of "Message number 67328" and recover the managed server the image was deployed to.
When a single cloning image was being deployed to multiple managed servers, take corrective action for all of the managed servers.
When a managed server is VMwareESXi
Necessary information cannot be obtained from the required software.
Refer to ServerView Operations Manager in "6.1.1.4 Required Software" in the "Overview", and enable management of the target server using ServerView Operations Manager.
When a managed server is VMware ESXi on another vendor's server, or a managed server is in a configuration in which ServerView ESXi CIM Provider is not used on VMware ESXi on Fujitsu rack mount servers
The definition file may not exist or the target managed server may not have been defined in the definition file.
Refer to "8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE", and check that the definition file name and the defined content are correct.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
An error has occurred during power control of a managed server.
Corrective Action
Check the following and take corrective action.
The SNMP community name set from the ROR console
If it was omitted, [public] will be specified.
Whether or not the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
That the values of the IP address, user name, and password set for the Remote Management Controller when registering the managed server have not been changed from their original values
For details of checks and the setup method, refer to the manual of the server being used.
Description
The chassis has not been registered.
The admin LAN of the chassis including the server to be registered may not have been set correctly.
Corrective Action
After registering a chassis, perform the operation again.
When the chassis has been registered, check the admin LAN settings of the server to be registered.
Description
The managed server specified does not meet the requirements for Auto-recovery or manual switching.
The name of the managed server specified is displayed for obj.
The following detailed causes are displayed for detail.
no image
Backup of the system image of the server specified was not performed.
Corrective Action
Take corrective action based on the detailed cause.
no image
After system images are backed up on the server specified, perform manual switching again.
Description
A Resource Orchestrator agent has not been installed on a managed server.
The name of the managed server is displayed for obj.
Corrective Action
After installing a Resource Orchestrator agent on the managed server, execute the command again.
Description
An error has occurred in LAN switch control.
The network management command is displayed for command.
A character string indicating the process that resulted in an error during network management is displayed for rcxerrno.
One of the following is displayed for mip:
The admin IP addresses of the managed LAN switch
Admin IP addresses or server names of managed servers
An error may occur during the following conditions:
When specifying a different IP address with LAN switch
When specifying a SNMP community name not set in the LAN switch
When the LAN switch is not operating correctly
When the LAN switch mode cannot be acquired correctly
When the LAN switch is replaced with a different type of LAN switch from the original, and restoration performed
When the user ID of the administrator of a LAN switch has not been specified, even though it is required.
When registering the Converged Fabric mode of the PY CB Eth Switch 10/40Gb 18/8+2 LAN switch blade using the representative virtual IP address of the domain
Corrective Action
After checking the following, execute the command again.
That the LAN switch is a supported model
That the LAN switch is the same model as the original
Whether the content of the following settings of LAN switch matches that of Resource Orchestrator
If they are different, correct the settings of both LAN switch and Resource Orchestrator so they match.
The admin IP addresses of LAN switch
The subnet mask for the admin IP addresses of the LAN switch
VLAN ID to which the admin IP addresses of the LAN switch belong
The connection port for the admin IP addresses of the LAN switch
SNMP community name
The user name for remote login
The password for remote login
The privileged password for remote login
Whether there is an abnormality in the communication route between the admin LAN and the LAN switch
Check whether a LAN cable is unplugged or the LAN switch is powered off.
Whether the LAN switch is operating correctly
Check the following, and if necessary, remove the problem using the maintenance procedure of the LAN switch.
The LAN switch is powered on
The SNMP agent is operating normally
The server can connect to the LAN switch using telnet or SSH
Information
When telnet or SSH connection (SSH version 2) is disabled, enable it.
For details on settings, refer to the manual for the LAN switch.
The number of simultaneous connections using telnet or SSH may be limited depending on the model. In that case, log out of other telnet or SSH connections.
When using Converged Fabric mode, it is not necessary to use an SNMP agent, as SNMP communication is not performed. (For only Virtual Edition)
When using SSH connections, check if the firmware version is correct
LAN switch blade PY CB Eth Switch/IBP 10Gb 18/8 (version 1.00 or later)
LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2 (version 1.00 or later)
LAN switch blade PY CB Eth Switch/IBP 1Gb 36/8 (version 4.16 or later)
LAN switch blade PY CB Eth Switch/IBP 1Gb 36/12 (version 3.12 or later)
LAN switch blade PY CB Eth Switch/IBP 1Gb 18/6 (version 3.12 or later)
LAN switch blade PY CB DCB SW 10Gb 18/6/6 (version 2.1.1_fuj or later)
When rccxerrno is "vcs_id" or "rbridge_id", if VCS ID or RBridge ID is correctly configured
Log in to the target LAN switch, and check if VCS ID or RBridge ID is correctly configured.
For details on how to check, refer to the manual for the LAN switch.
When rcxerrno is "fabric_id", "domain_id", or "switch_id", if a Fabric ID, a Domain ID, or a Switch ID is correctly configured
Login to the target LAN switch, and check that the Fabric ID, Domain ID, or Switch ID has been specified correctly.
For details on how to check, refer to the manual for the LAN switch.
When rcxerrno is "user not privileged", if the user ID of the administrator for the LAN switch has been specified
Check if the user ID specified for the LAN switch is that of the administrator.
When registering the Converged Fabric mode of a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2, configure the oob IP address or the representative virtual IP address of the fabric.
Check whether the Mode displayed in the unit name (software name) in the resource details has been updated correctly.
Description
An internal command for obtaining server information may be being executed in another process.
Corrective Action
Wait a couple of minutes and then execute the command again.
Description
Command execution failed on the managed server.
The admin IP address of the managed server or the server name is displayed for mip.
Corrective Action
Check the following on the managed server indicated for mip.
Check that the managed server is not down
If the system is down, start the system from the appropriate OS.
Check that the managed server was started using the appropriate OS
If it was not, change the BIOS settings referring to the manual for the server.
[Linux]
Check if the LAN card is correctly configured and activated on the system by OS-provided commands.
If it has not been configured and activated correctly, configure the LAN card referring to the Linux installation guide.
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
An error has occurred in VLAN settings for LAN switch.
Corrective Action
For the LAN switch of the managed server that was the target of the operation (such as server registration or server deletion) that resulted in the error, confirm the following.
The LAN switch is powered on
The SNMP agent is operating normally
The server can connect to the LAN switch using telnet or SSH
Information
When telnet or SSH connection (SSH version 2) is disabled, enable it.
For details on settings, refer to the manual for the server.
The number of simultaneous connections using telnet or SSH may be limited depending on the model. In that case, log out of other telnet or SSH connections.
VLAN settings for ports with link aggregation configured are not supported by some models.
When the target ports have link aggregation configured, disable the link aggregation, or manually configure the VLANs of the target ports.
For details on how to perform checks and configuration, refer to the manual for each server.
When using end host mode, cannot modify a port VLAN ID, and remove a tag vlan for the external ports which meet the following conditions.
The port is selected as Selected Port
The port has been activated
More than one internal port has the same VLAN.
Deactivate that port or change the VLAN IDs of all the internal ports that have the same VLAN IDs as the external port, and then perform the operation again.
External ports that are Selected Ports can be checked by logging into the LAN switch and running the show pin-interface all command.
When modifying a port VLAN ID, the target port may be in one of the following states:
Port VLAN IDs for before and after the change are configured for the target port
A tagged vlan with the same ID as a port VLAN ID from before the change and a port VLAN ID from after the change are configured for the target port
Perform the following corrective actions:
When port VLAN IDs for before and after the change are configured for the target port
Log in to the LAN switch blade.
Deactivate the external port which has a port VLAN ID from before the change.
Delete the port VLAN ID from the external port.
Activate the external port.
When a port VLAN ID from after the change and a tagged vlan which has the same ID as a port VLAN ID from before the change are configured for the target port
Log in to the LAN switch blade.
Disable the Auto VLAN Uplink Synchronization (AVS) setting.
Deactivate the external port which has a port VLAN ID from before the change.
Delete the port VLAN ID from the external port.
Activate the external port.
After checking the above, if necessary, remove the problem using the maintenance procedure of the LAN switch.
For Virtual Edition, refer to "Replacing LAN Switch Blades" in "6.2.5 Replacing Non-server Hardware" in the "Operation Guide VE" and reflect the VLAN information on the server, then perform the operation again.
For Cloud Edition, refer to "Replacing LAN Switch Blades" in "9.2.5 Replacing Non-server Hardware" in the "Operation Guide CE" and reflect the VLAN information on the server, then perform the operation again.
Description
GLS has not been installed on the managed server.
Corrective Action
Install GLS on the managed server.
Refer to the product manual for the installation method of GLS.
Description
The command terminated abnormally.
Corrective Action
Perform the operation again.
[Virtual Edition]
Description
Password decryption failed.
Corrective Action
When the message above is output during reading of a system configuration file
Confirm if the password is configured using an encrypted character string in the resource definition line for specifying "encrypted" (encrypted password).
For the system configuration file, refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide VE".
When this message is output while the network configuration information file is being read, and "true" is set for the PasswordEncryption element.
Check if an encrypted character string is configured for the Password element or the PrivilegedPassword element.
Refer to "8.1.1 Creation" in the "Reference Guide (Command) VE" for information about network configuration information.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Cloud Edition]
Description
Password decryption failed.
Corrective Action
When the message above is output during reading of a system configuration 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 system configuration files, refer to "Appendix B Format of CSV System Configuration Files" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When this message is output while the network configuration information file is being read, and "true" is set for the PasswordEncryption element or the rcxnetworkservice command is executed.
Check if an encrypted character string is configured for the Password element or the PrivilegedPassword element.
Refer to "15.6.1 Creation" in the "Reference Guide (Command/XML) CE" for information about network configuration information.
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 range of IP addresses specified is incorrect.
One of the following is displayed for code:
9:
An invalid IP address is included in the specified range of IP addresses
10:
The range of the start IP address and that of the end IP address are incorrect
13:
The start IP address and end IP address are not in the same subnet
14:
The start IP address is the same as the subnet number
15:
The end IP address is the same as the broadcast address
102:
The host of the start IP address specified for the redundancy method is not the same
103:
The same subnet of the start IP address specified for the redundancy method has been used
201:
IP addresses of registered managed servers exist outside the range of specified admin IP addresses, or a different subnet was specified when registered managed servers already exist
Corrective Action
Take corrective action based on the content of code.
For "201"
Choose one of the following corrective actions:
Specify a range of addresses including the registered managed server addresses in the same subnet as the range of admin IP addresses prior to change, and then perform the operation again.
Release the IP addresses of the registered managed servers, and then perform the operation again.
For a code other than the above
Check the parameter, and then perform the operation again.
[Virtual Edition]
Description
The option specified for option is not supported.
Corrective Action
Check and correct the option specified, and then perform the operation again.
[Cloud Edition]
Description
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 a physical L-Server was created, "Policy.SpareServerForceOFF Policy.AllowForceOFF" is displayed in option
Both "Use active spare server with forced turning OFF" and "Allow forced turning OFF" cannot be set at the same time.
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.
In other cases
The option specified for option is not supported.
Corrective Action
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 a physical L-Server was created, "Policy.SpareServerForceOFF Policy.AllowForceOFF" is displayed in option
Both "Use active spare server with forced turning OFF" and "Allow forced turning OFF" cannot be set at the same time.
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 disks, specify the -allow deldisk option and try again.
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.
In other cases
Check and correct the option specified, and then perform the operation again.
Description
Deletion of the oldest cloning image failed because it is in use.
Corrective Action
Delete one or more versions of cloning images that are not in use, then perform the operation again.
Description
Deleting the version version of the cloning image failed because it is in use.
Corrective Action
Enable use of the specified version version of the cloning image, and then perform the operation again.
Description
The command command has not been completed successfully on the server server_name.
The name of the server is displayed for server_name.
The name of the command for execution is displayed for command.
The target of the command is displayed for detail.
The following messages may be output:
In the case of "/usr/sbin/ldm list-constraints -x > /etc/opt/FJSVrcvat/config/ovm_config.xml"
This is the process to save the domain configuration of OVM for SPARC.
In the case of "/usr/bin/pkginfo -l SUNWldm"
This is the process to acquire the version of OVM.
In the case of "setdomainconfig -p ppar_id -c default"
Return the domain configuration to the factory-default.
In the case of "/usr/sbin/ldm init-system -f -i /etc/opt/FJSVrcvat/config/ovm_config.xml"
Restore the domain configuration.
In the case of "setpparparam -y -p 0 -s bootscript 'setenv auto-boot? true \n setenv boot-device disk name'"
Set "true" for auto boot of control domain, and set "disk" for boot-device.
In the case of "setpparmode -y -p 0 -m guestboot=off"
Change the setting of guestboot on the switchover target server to "off" in the switchover process.
In the case of "/usr/bin/cp /etc/opt/FJSVrcvat/config/ovm_config.xml target_path"
Back up the XML file of the configuration information.
In the case of "/usr/sbin/shutdown -i6 -g0 -y"
Restart the server.
In the case of "/opt/FJSVrcvat/sys/recover_pci"
Restore the physical IO.
In the case of "/opt/FJSVrcvat/sys/recover_vconsole"
Restore the port of the virtual console.
In the case of "/usr/sbin/ldm start-domain"
Start the domain.
In the case of "/usr/sbin/ldm list-domain -p"
Display the domain configuration information.
In the case of "/usr/sbin/ldm add-spconfig configuration information name"
Save the domain configuration information in the service processor.
Corrective Action
Take corrective action for the content displayed for detail.
For details on the command, refer to the "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual" or the "Oracle VM Server for SPARC Administration Guide" provided by Oracle, and take corrective action as necessary.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
[Virtual Edition]
Description
An error has occurred during the process set in "17.6 Network Parameter Auto-Configuration for Cloning Images" in the "User's Guide VE".
A number corresponding to one of the following processes is displayed for type:
10: PRE_TGTSVR_IMAGE_CREATE
The process before collection of cloning images
11: POST_TGTSVR_IMAGE_CREATE
The process after collection of cloning images
13: POST_TGTSVR_IMAGE_INSTALL
The process after deployment of cloning images
Corrective Action
Take the corrective action for "Message number 61501" or "Message number 61502" displayed in the event log.
When neither "Message number 61501" nor "Message number 61502" are displayed, collect troubleshooting information and contact Fujitsu technical staff.
Description
Login failed.
Corrective Action
Enter the correct user ID and password, and then log in again.
When there is no error in the user ID and password, and the management account is a new addition, there is an error in the password configured during account creation.
For Virtual Edition, set the password given in "Chapter 5 Managing User Accounts" in the "User's Guide VE" again.
For Cloud Edition, set the password given in "Chapter 3 Configuring Users and Customizing Roles" in the "User's Guide for Infrastructure Administrators (Resource Management) CE" again.
Description
Writing to the file or directory specified for filename failed because the file type is invalid.
Corrective Action
After performing one of the following corrective actions perform the operation again.
Change the name of the file or directory displayed for filename
Move or delete the file or directory displayed for filename
Description
The environment variable variable is invalid.
Corrective Action
Check the value of the variable variable and then perform the operation again.
Description
The shell to be started was not found.
Corrective Action
Correct the environment variable SHELL.
Description
Execution of the command described in obj failed.
Corrective Action
Check the following, resolve the problem, and execute the command again.
When <obj> is "migrate_vdi.bat"
That the execution environment of the batch file is correct
migrate_vdi.bat must be executed in the following storage folder:
Installation_folder\SVROR\Manager\opt\FJSVrcxmr\sys\VdiMigrationTool |
In other cases
The command execution environment is correct
Execute the /opt/FJSVrcvhb/bin/rcxhbactl command from a desktop environment.
Users have sufficient command execution authority
There is enough free memory
Description
The file or directory specified for filename was not found.
Corrective Action
Specify an existing file or directory.
Description
The file or directory specified for filename cannot be created.
Corrective Action
Check the access authority for the directory.
Description
There is no home directory for the executing user.
Corrective Action
For the OS user account on which the command has been executed, check if the following has been set and the directory set is on the admin server. Correct them and perform the operation again.
There is an entry of the user account on which the command has been executed on "Local Users and Groups" of the admin server
In the environment valuable of the above account, APPDATA or USERPROFILE exists and the correct directory is set
Description
The chassis chassis_name was not found.
Corrective Action
Check the name of chassis specified.
Description
The specified alias(alias) was not found.
Corrective Action
Execute the following command and check the alias, and then perform the operation again.
[Windows Manager]
>Installation_folder\SVROR\rcxadm certctl list <RETURN> |
[Linux Manager]
# /opt/FJSVrcvmr/bin/rcxadm certctl list <RETURN> |
Example
In the following, client2, client1, server5, server4, server3, server2, and server1 are aliases.
Truststore: |
Description
The keystore file was not found.
Corrective Action
Check that the keystore file exists in the following directory.
When operating managers in clusters, check that the shared disk for managers is mounted, and then perform the operation again.
If it does not exist, collect troubleshooting information and contact Fujitsu technical staff.
When it is a manager
[Windows Manager]
Installation_folder\SVROR\Manager\etc\opt\FJSVssmgr\current\certificate\common_truststore
[Linux Manager]
/etc/opt/FJSVrcvmr/opt/FJSVssmgr/current/certificate/common_truststore
When it is an agent
[Windows] [Hyper-V]
Installation_folder\Agent\StorageRM\Agent\etc\certificate\agent_truststore
[Linux] [VMware] [Xen] [KVM]
/etc/opt/FJSVssagt/certificate/agent_truststore
[Solaris]
/etc/opt/FJSVrcvat/certificate/agent_truststore
Description
The keystore file may be damaged or the file is incorrect.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
Description
An internal error occurred.
Corrective Action
Collect this message and troubleshooting data, and contact Fujitsu technical staff.
Description
The command syntax is incorrect. "usage" is displayed.
Corrective Action
Check and correct the command format, and then perform the operation again.
[Virtual Edition][Cloud Edition]
Description
obj does not support function.
In function, the name of the function that is not supported is displayed.
When function can be used with certain conditions, detailed information is displayed in the following function or detail.
In cases other than the following, this message is displayed when you attempt to use a function that cannot be used by obj. No action is necessary.
As the physical L-Server in obj was created using a method other than linking, changing of the destination network is not supported.
シャーシ未登録の状態で、一括設定インポートによるブレードサーバの仮想WWN設定はサポートしていません。
The L-Server to be quarantined could not be identified from the notification sent from Trend Micro Control Manager.
The settings or operation are incorrect.
detail will be one of the following:
When function is "convert" and detail is "(already in use)"
The VM guest has already been linked to a virtual L-Server.
When the CSV file contains two or more lines with the same VM guest name but with a different host name, linking of the second and subsequent VM guests is not supported.
When function is "create.xml" and detail is "(Two or more LNetworks)"
Creation of the XML for changing the network of virtual L-Servers with multiple NICs is not supported.
When function is "convert with refreship" and detail is "(PhysicalLServer)"
The -refreship option cannot be specified for linking of physical L-Servers.
When function is "convert with refreship" and detail is "(VMType)"
When using the rcxadm lserver convert command
The -refreship option cannot be specified when linking virtual PCs that are not supported by Resource Orchestrator.
When using the convertVMtoLServer command
It is not possible to link virtual PCs that are not supported by Resource Orchestrator.
When detail is (NetworkResource not found)
When the -refreship option is specified, the network settings of VM guests cannot be acquired.
[Citrix Xen]
When function is "convert" and detail is "(not assign a home server)"
As Home Server settings have not been configured, linking to an L-Server cannot be performed.
Corrective Action
Refer to "2.13 Linking Physical L-Servers with Configured SBC Servers" in the "Automatic Quarantining Function User's Guide", and perform linking.
シャーシを登録してから、一括設定インポートによるブレードサーバの仮想WWN設定を行ってください。
[Trend Micro PM]
Refer to "2.12 Linking Virtual L-Servers with Configured Virtual PCs" and "2.13 Linking Physical L-Servers with Configured SBC Servers" in the "Automatic Quarantining Function User's Guide", and perform linking.
Refer to "2.1 Preparations for Using the Automatic Quarantining Function" in the "Automatic Quarantining Function User's Guide", and correct the definition of Policy.
When the following security risks are detected, Resource Orchestrator may not be automatically notified.
The destination of C&C callback communication from multiple terminals is the same IP address
Multiple threats are detected on a single terminal
This error message may be output when manually requesting an action targeting the relevant security risk using the Trend Micro Control Manager Web console.
As it is not possible to perform quarantining using Resource Orchestrator, refer to the information output to the Trend Micro Control Manager Web console and handle the security risk manually.
In other cases, no action is necessary.
When the CSV file contains two or more lines with the same VM guest name but with a different host name, link the failed VM guest with a virtual L-Server using the rcxadm lserver convert command.
For details on the rcxadm lserver command, refer to "4.3 rcxadm lserver" in the "Automatic Quarantining Function User's Guide".
In other cases, no action is necessary.
Refer to "A.4 XML Files for Changing the Network" in the "Automatic Quarantining Function User's Guide" and create an XML file for changing the network that handles multiple NICs.
The -refreship option cannot be specified for linking of physical L-Servers.
When specifying the -refreship option, specify one of the following types of virtual PC supported by Resource Orchestrator for the -with option, and perform the operation again.
VMware
Hyper-V
XenServer
For details on the rcxadm lserver command, refer to "4.3 rcxadm lserver" in the "Automatic Quarantining Function User's Guide".
Delete the information of virtual PCs that are not supported by Resource Orchestrator from the CSV configuration file specified in the -file option and then perform the operation again.
For details on the convertVMtoLServer command, refer to "4.2 convertVMtoLServer" in the "Automatic Quarantining Function User's Guide".
When a virtual network that a VM guest is connected to has not been defined as a network resource on ROR, register the network resource corresponding to the virtual network.
If the subnet defined in a network resource on ROR and the subnet of an IP address set on a VM guest on vCenter do not match, correct the definition of the network resource so the subnets match.
ROR may not have been able to obtain the network information. Wait a couple of minutes and then execute the command again.
[Citrix Xen]
After configuring Home Server settings, wait for a while and then perform the operation again.
In other cases, no action is necessary.
[Virtual Edition]
Description
The object obj does not support function.
The name of the unsupported function is displayed for function.
When function can be used because of usage conditions, the following detailed information will be displayed enclosed in parentheses for function or detail.
For cases other than the following, this message is displayed because use of an unsupported function was attempted for obj. No action is necessary.
"Extended Partitioning Mode is Disable on the PPAR on which the Extended Partition is configured"
"incompatible IBP group configuration between switch-1 and switch-2"
"incompatible mode between switches switch-1 (mode-1) and switch-2 (mode-2)"
"switch=switch,port=port is in unsupported state. (Automatic Migration of Port Profile)"
Corrective Action
Take corrective action based on the content of function.
Configuration cannot be performed while the server is powered on and the server status is something other than "normal".
Take corrective action for the content displayed for detail.
When the settings of the NIC for the admin LAN are a server different to that displayed for obj, configuration of a spare server is not possible.
On PRIMEQUEST 2000 series servers, if the Extended Partitioning Mode of the PPAR partition is "Disable", the function displayed for "function" is not supported for Extended Partition.
The IBP group settings of the switch switch-1 of the switchover source, and the switch switch-2 of the switchover target that is displayed for obj do not match the operation conditions of function.
The modes of the switch switch-1 of the switchover source, and the switch switch-2 of the switchover target that is displayed for obj do not match.
The modes of each switch, "IBP mode", "switch mode", "end-host mode" ,or "Converged Fabric mode" is displayed for mode-1 and mode-2.
Modify the LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2 to a mode other than IBP mode.
The NIC configuration of the target of operation displayed for obj does not match the conditions for spare servers of function.
The function displayed for function is one not supported in the current environment. For details of backup and restore, and cloning, use ServerView Deployment Manager. For I/O virtualization (HBA address rename), please use ServerView Virtual-IO Manager or ServerView Infrastructure Manager.
When this message is displayed for other operations, it is not necessary to perform those operations.
The VM guest displayed for obj does not support movement to the VM host specified as the destination.
The target of operation displayed for obj is a model that does not support function.
Server switchover using backup and restore cannot be used for the server displayed for obj.
This is displayed when a VM host is operating on the server displayed for obj.
The conditions for executed operations have not been satisfied. Check the operation conditions.
This cannot be used with a Linux manager.
The target of operation displayed for obj is a server OS that does not support function.
The IP address displayed in obj is out of the range of IP addresses for which the backup and restore functions for system images can be used.
On PRIMEQUEST 2000 series servers, if the Extended Partitioning Mode is "Enable" the function displayed for "function" is not supported for PPAR partitions.
Automatic Migration of Port Profile (AMPP) is configured for the internal ports of the switches that are the switchover destination of the server.
Log in to the target LAN switch, and check if an Automatic Migration of Port Profile (AMPP) has been configured.
When taking over the VLAN configuration of the switch of the switchover source, release the Automatic Migration of Port Profile (AMPP) settings for the internal ports of the switch that is the switchover target.
When configuring the Automatic Migration of Port Profile (AMPP) for the internal ports of the switch of the switchover target, release the "network settings" of the spare server settings.
The specified VLAN ID is being used for FCoE.
As the server displayed for obj already has VIOM coordination configured as its virtualization method, HBA address rename cannot be set.
The target of operation displayed for obj is server virtualization software that does not support function.
[Citrix Xen]
Setting and release of VM maintenance mode for Citrix XenServer pool masters is not supported.
[Cloud Edition]
Description
The object obj does not support function.
The name of the unsupported function is displayed for function.
When function cannot be used for obj, detail will not be displayed.
When function cannot be used because of usage conditions, the following detailed information will be displayed enclosed in parentheses for detail.
For cases other than the following, this message is displayed because use of an unsupported function was attempted for obj. No action is necessary.
"DiskLink and DiskCopy cannot be specified at the same time"
"DiskLink and ServerImageLink.disk cannot be specified at the same time"
"Server pool,Storage pool,Network pool,Address pool,and Image pool"
"Server pool,Storage pool,Network pool,Address pool,and Image pool"
When obj is something other than "Target network overlaps with admin LAN"
"VM pool,Server pool,Network pool,Address pool,and Image pool"
"VM pool,Server pool,Storage pool,Network pool,and Address pool"
"command options, the XML tag names or the XML tag names=values cannot be specified for VM type"
Corrective Action
When obj is "network_resource_name"
The subnet address of a resource of the admin LAN directly connected to a manager cannot be specified.
Specify the subnet name of the admin LAN, and perform the operation again.
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.
When function is "registering agent"
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.
"8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE"
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:
"8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE"
function cannot be executed, as there is no registered agent.
The function displayed in function cannot be used because the target managed server displayed in obj is a server that cannot use agents.
When function is "registering agent"
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.
"8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE"
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:
"8.1.5 Definition Files when Creating a Virtual L-Server Using VMware ESXi on Another Vendor's Servers or when Creating Virtual L-Servers without Using ServerView ESXi CIM Provider on VMware ESXi on Fujitsu Rack Mount Servers" in the "Setup Guide CE"
The target resource displayed in obj cannot be registered in the resource pool because it is already registered in pool name.
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.
The function displayed in function cannot be used with the resources of an L-Platform.
When you change the alive monitoring settings for an L-Server deployed from an L-Platform, use an XML file that contains only the alive monitoring setting and redundancy elements.
Release L-Servers from L-Platforms when registering the VM host on the VM guest allocated in the L-Server.
The boot disk cannot be deleted.
Target resources cannot be created on or moved to the L-Platform.
Specify the resource folder or tenant for the creation or destination resource folder, and perform the operation again.
The LUN created in advance cannot be deleted.
Use the managed container resource pool of Resource Orchestrator, after changing the managed container resource pool in Resource Orchestrator to the container resource pool used by obj, or changing the obj settings on VM software.
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.
The default gateway of the admin LAN resource that is directly connected from the manager cannot be changed.
In the specified L-Server, "deny_deldisk=true" (do not delete) cannot be specified when detaching a disk allocated from virtual storage.
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.
The DiskCopy element cannot be specified in XML for disks with the disk number 0.
The DiskLink element cannot be specified in XML for disks with the disk number 0.
The DiskLink element and the DiskCopy element cannot be specified in XML for a single disk at the same time.
When a disk resource created in advance is specified, "false" cannot be specified for the Exist element.
When the VM type is KVM and the DiskSize element is specified, specify "true" for the Exist element.
The value specified for "type" cannot be set for disks other than disk number 0.
Try to release disk resource registration using a configuration modification operation.
Use the unregister command to release the registration of obj disk resources, and perform the operation again.
deny_deldisk=true(do not delete) cannot be specified for the disk from which a snapshot has been collected.
When saving a virtual disk (created from virtual storage), delete all snapshots of that virtual L-Server first, and then perform the operation again.
An L-Server cannot be created, as the above elements are not supported when creating an L-Server.
The DiskLink element and the DiskCopy element cannot be specified at the same time.
Specify either the DiskLink element or the DiskCopy element, and perform the operation again.
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.
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.
Dynamic memory settings are enabled for the target resource.
Memory capacity cannot be changed for L-Servers for which dynamic memory settings are 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 "17.2 Modifying" in 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 the VM type is something other than KVM, the Exist element cannot be specified.
function cannot be executed, as the resource to be operated is a physical server for which a spare server has been configured.
Create a resource, using the command for the resource folder.
The specified resources cannot be created on resource folders or an L-Platform.
When registering resources to resource pools
function cannot be executed, as the force option is not supported for resources other than server pools.
When migrating an L-Server between servers
The force option is only supported for Solaris Zones and RHEL-KVM.
Perform the operation again without specifying force.
When alive monitoring is enabled, None cannot be specified for the Redundancy element.
Specify "HA" for the Redundancy element, and then perform the operation again.
For guest domains, delete the disk shared with another L-Server from the VM host. After that, use the GUI or a command to confirm the disk has been deleted, and then perform the operation again.
When using the GUI:
Display the ROR console.
Select the L-Server on the orchestration tree.
From the [Disk Information] on the [Resource Details] tab of the main panel, check that the disk which was being shared is not displayed.
When using the CLI:
Execute the following command:
>rcxadm lserver show -name L-Server_name <RETURN> |
Check "Disk[num]:", the shared disk is not displayed.
[FCConnectionPattern] cannot be used in an environment where the HBA address rename service is configured.
Re-execute without specifying [FCConnectionPattern].
As the hierarchization of tenants is not supported, a tenant cannot be created in or moved into another tenant.
The disk type is not supported.
Configurations cannot be changed, since the specified disk resource is not the disk resource of a VM guest.
Specify a disk resource for VM guest, and perform the operation again.
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.
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.
function cannot be executed, as the resource to be operated does not support the XML tag in detail.
Failed to configure the IP address of the public LAN. IP addresses cannot be configured for the admin LAN.
obj is a product version which cannot be registered in a VM pool.
No action is necessary.
The function cannot be executed, since operations not supported by the target resources were specified.
Perform the operation, using the command for L-Platforms.
The function displayed in function cannot be used with the L-Platform.
The specified interface cannot be used.
The specified L-Server cannot be operated because it has "defined" status.
Saved virtual disks (created from virtual storage) cannot be added to an L-Server from which a snapshot has been collected.
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.
The operation cannot be performed because the L-Server function displayed in function does not support the above elements.
When obj is "network_resource_name"
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.
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 "DefaultGateway"
For the admin LAN connected directly to a manager, do not specify the default gateway.
This cannot be used with a Linux manager.
The subnet mask of the admin LAN resource that is directly connected from the manager cannot be changed.
Periodic queries to the VM management software have not been made, so disk information may have not been obtained. Wait for a short while and then repeat the operation.
Since the setup of Home Server has not been performed, the virtual machine and L-Server cannot be linked.
Perform setting of the Home Server, wait for a short while, and then perform the operation again.
Operation cannot be performed, as the physical server is not connected due to changes to physical server usage.
Virtual disks that cannot be connected to from a VM host with an L-Server deployed cannot be specified.
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 that can connect to virtual disks.
Disk resources cannot be automatically generated on the target storage device.
This command can only be performed for the physical L-Server.
Execute this command for the physical L-Server.
Usage is not possible for physical L-Servers.
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.
The target resource cannot be included when calculating the number of L-Servers creatable for each L-Server template.
The target of operation displayed for obj is a server OS that does not support function.
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
When using an admin server that has been upgraded from ROR V2.3 or V3.0 and the upgrade procedure for overcommit has not been performed, the overcommit attribute cannot be specified. Alternatively, edit the definition file. Refer to "2.3.1.1 Overcommit Definition Files" in the "Release Notes" for more details.
The Exist element is not specified, or true is not specified for the value.
Specify true for the Exist elements and the values, and perform the operation again.
The Exist element is not specified, or true or false was not specified for the value.
Specify the Exist element, or true or false for the value, and perform the operation again.
The resource pool cannot be specified.
When obj is "network_resource_name"
The specified Pool element cannot be specified when changing network resource settings.
After deleting the Pool element, perform the operation again.
The target resource displayed in obj cannot be registered in the resource pool because it is a resource pool type that cannot be registered.
The function displayed in function cannot be used with the current power state (power-off).
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.
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.
[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
After deleting the L-Server, create an L-Server again.
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.
Review the VM type and environment, and then perform the operation again.
function cannot be executed, as the resource to be operated is a VMware FT secondary virtual machine.
The operation is valid for VM and Storage pools.
The setting for displaying the attributes is only valid for VM and Storage pools.
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.
The overcommit attribute is only valid for VM pools.
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.
For guest domains, delete the disk shared with another L-Server from the VM host.
As the redundancy is FT, Redundancy cannot be specified.
Cancel the Redundancy specifications, and perform the operation again.
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.
When registering a configured physical server to a resource pool, specify the -force option and perform the operation again.
Since the operation target resource is a spare server, registration in the server pool cannot be performed.
The function displayed in function cannot be used as the storage has not been configured properly.
When function is "convert L-Server"
Check that the storage has been configured for linking the configured physical server to the L-Server.
The operation is valid for VM pools and server pools.
The resource to be operated cannot be displayed linked to L-Servers.
The subnet address of the admin LAN resource that is directly connected from the manager cannot be changed.
When obj is "UserGroup"
The "supervisor" group cannot be edited and deleted.
When obj is "PhysicalLanSwitch(PhysicalNic=position)"
The message is output when the rcxadm nsoptctl command is executed.
The LAN switch blade switch which links with the number position specified using the -position option is in IBP mode.
Operations for LAN switch blades in IBP mode cannot be performed using the rcxadm nsoptctl command.
Change the mode of the LAN switch blade displayed in switch or perform VLAN operations manually.
Failed to configure the IP address of the public LAN. The same network as the admin LAN cannot be configured for the public LAN.
After creating a physical L-Server, configure the IP address manually. Configure the admin and public LANs in different networks.
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.
No action is necessary.
Perform the operation, using the command for tenants.
The target resource displayed in obj cannot be deleted because it is the last resource pool of resource pool type pool_type.
The server displayed in obj is registered in the resource pool, so the boot agent cannot be changed.
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.
The specified L-Server does not satisfy the conditions for operation. Disk space expansion for L-Servers is only supported for VMware or Hyper-V.
Check the VM type of the specified L-Server, the power status, and the setting conditions for spare servers, change the status or settings appropriately, and perform the operation again.
[Solaris Zones]
The following operations are not supported.
Changes to the configurations of L-Servers using container resource pools outside the scope of management
Attaching and detaching disks of L-Servers
Expansion of L-Server disk capacity
Use of the console
Collection and deletion of cloning images
Collection, recovery, or deletion of snapshots
Migration of VM hosts (live migration)
Migration to VM host for which spare sever settings are configured
When using Solaris Zones (Solaris 11), L-Server creation is not supported.
For an L-Server linked with a virtual machine on a Solaris 11 VM host, the following operations are not supported.
Deleting an L-Server
Modifying L-Server specifications
Modifying the basic information of L-Servers
Attaching and detaching disks of L-Servers
Expansion of L-Server disk capacity
Use of the console
Operation of cloning images
Operation of snapshots
Migration of a VM guest to a different VM host
[OVM for SPARC]
The following operations are not supported.
Expansion of L-Server disk capacity
Use of the console
Collection and deletion of cloning images
Collection, recovery, or deletion of snapshots
When using an admin server that has been upgraded from ROR V2.3 or V3.0 and the upgrade procedure for overcommit has not been performed, the thin provisioning attribute cannot be specified. Alternatively, edit the definition file. Refer to "2.3.1.1 Overcommit Definition Files" in the "Release Notes" for more details.
Since two or more network resources containing the specified IP address exist, the virtual machine cannot be linked with the L-Server.
Check the prerequisites for importing an IP address.
Check that the prerequisites for importing an IP address are met, referring to "18.4.1 Preparations" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Check if more than two network resources with the specified IP address exist.
If there are, re-configure those network resources so they use different IP addresses.
When a network resource cannot be changed, automatic import of an IP address cannot be performed. Change the settings for importing an IP address, and then perform the operation again.
If the problem is still not resolved after performing the above actions, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
The network resource type cannot be specified.
function cannot be executed, as there is an unknown disk on the resource to be operated.
The operation target displayed for obj and the VDI type of the VDI management server or the VDI management software linked with the operation target do not match. Check if the VDI management server and the VDI management software settings are correct.
HBA address rename settings cannot be configured for the server displayed in obj as a virtualization method has been already configured using VIOM.
When allocating disk resources to physical L-Servers from multiple storage chassis, VIOM is necessary.
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.
When obj is "network_resource_name"
Automatic VLAN configuration flags for external connection ports cannot be changed.
Delete vlanautosetting from the ExternalPorts element in the XML definition and then perform the operation again.
The VLAN ID cannot be specified.
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.
The operation is valid for Storage pools.
The thin provisioning attribute is only valid for Storage pools.
The operation is valid for image pools.
The target resource cannot display image information.
The VM host, which the L-Server is running on, detects that the VM guest of the L-Server does not exist, so L-Server deletion fails.
Check the name of the VM guest of the L-Server using the GUI or the CLI.
When using the GUI:
Display the ROR console.
Select the L-Server on the orchestration tree.
Select the [Resource Details] tab on the main panel, and check the guest name of the resource.
When using the CLI:
Execute the following command:
>rcxadm lserver show -name L-Server_name <RETURN> |
Check the display of "VmGuest:".
If the VM guest name is not displayed, delete the L-Server again.
If the VM guest name is displayed, check that migration is not being performed from the management screen of the VM management software, and then delete the L-Server again.
When a message is output during deletion of the L-Server, check that the VM guest name of the L-Server is not displayed, and then delete the L-Server again.
The target resource displayed in obj is server virtualization software that does not support function.
This message is displayed because use of an unsupported function was attempted for obj.
[VMware]
For VMware ESXi, the following operation is not supported.
Backup
[Xen]
The following operations are not supported.
Overcommit
[OVM for x86 2.2]
The following operations are not supported.
Creation of an L-Server without specifying a cloning image
Overcommit
[Solaris Zones]
The following operations are not supported.
Changes to the configurations of L-Servers using container resource pools outside the scope of management
Attaching and detaching disks of L-Servers
Use of the console
Collection and deletion of cloning images
Collection, recovery, or deletion of snapshots
Migration of VM hosts (live migration)
Migration to VM host for which spare sever settings are configured
If this message is displayed during changing of the configuration of an L-Server, changes cannot be made to the configurations of L-Servers using container resource pools that are outside the scope of management.
Use the managed container resource pool of Resource Orchestrator, after changing the managed container resource pool in Resource Orchestrator to the container resource pool used by obj, or changing the obj settings on VM software.
[Citrix Xen]
The following operations are not supported.
Creation of an L-Server without specifying a cloning image
Creation of an L-Server specifying images including data disks
Reuse of data disks
Specification of maximum memory size
Revitalization change of CPU, memory, and data disks
Addition and deletion of virtual NICs
Collection of snapshots with memory
Monitoring of hang-up
Online collection of cloning images
Startup of the console
Installation of VM Tools
[OVM for x86 3.x]
The following operations are not supported.
Creation of an L-Server without specifying a cloning image
Creation of an L-Server specifying personalization with cloning images specified
Creation of an L-Server specifying images including data disks
Collection, restoration, or deletion of snapshots
Reuse of data disks
Specification of CPU reservation values
Specification of memory reservation size
Specification of maximum memory size
Monitoring of hang-up
Online collection of cloning images
Startup of the console
Installation of VM Tools
Raw Disk Mapping (RDM)
Addition and deletion of virtual NICs
Size expansion of virtual disks
Disaster Recovery (DR)
The above tabs specified in the L-Server template cannot be imported, as they are not supported.
Review the L-Server template to see if the above elements are used, and then perform the operation again.
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. Review the XML file and perform the operation again.
CPU
Memory
CPU.NumOfCPU
CPU.CPUPerf
Memory.MemorySize
Disks.Disk.type
When the migration source VM host is not powered off, forced migration cannot be performed.
Execute forced migration while the VM host is powered off.
Otherwise, execute migration again without specifying the -force option.
When function is "migrate"
Forced migration cannot be specified for vmtype.
When function is "revert"
Forced revert cannot be specified for vmtype.
No action is required.
When the VM type is Solaris Containers or RHEL-KVM, the -force option can be specified. Check the VM type specified.
Otherwise, execute migration again without specifying the -force option.
The specified command option, the XML tag or the XML tag values cannot be specified for the VM type specified in the target resources displayed in obj. "Disk size expansion" is supported only for VMware or Hyper-V.
Change or delete the command options, the XML tags or the XML tag values, and perform the operation again.
The specified command options cannot be specified for the resources of the target operation displayed in obj.
Execute the command without specifying the displayed options.
Description
The specified command, subcommand, or option is not supported.
The name of the managed server or the port name is displayed for obj.
The following detailed information is given in detail.
"Manager"
The server displayed for obj is an admin server.
"Port name"
The port name displayed for obj is a port name not supported by Resource Orchestrator.
Corrective Action
Perform checks based on each piece of detailed information, if the combination of resources is incorrect or the values differ, change the values specified or the settings and then perform the operation again.
"Manager"
When this message is displayed during registration of a managed server, check that an admin server is not the target of the operation.
If displayed when performing reconfiguration of hardware properties, check that an admin server has not been mounted in the relevant slot.
"Port name"
When changing port numbers, check there are no mistakes in port names.
For how to change port numbers, refer to following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" in the "User's Guide VE", or "5.11 rcxadm mgrctl" in the "Reference Guide (Command) VE"
Description
The specified managed server cannot perform operation against target.
The name of the managed server is displayed for server.
The target operation of server is displayed for target.
Corrective Action
Correct the specified target.
Description
An error has occurred because the PostgreSQL login user password has been changed.
Corrective Action
The configured user password is not correct.
Check the OS password setting conventions, and set an appropriate password.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
The command cannot be executed because the obj1 is defined as type of obj2.
Corrective Action
After resolving the problem, perform the operation again.
Description
The VM host or VM guest is not supported.
The name of the specified server is displayed for obj.
Corrective Action
Specify the physical OS name, and then perform the operation again.
Description
The IP address specified is incorrect, or the chassis information specified is not registered on the admin server.
Corrective Action
Check the following:
Check that the specified IP addresses of the chassis and server management unit or the server information (such as IP address) are correct.
If there are errors, perform registration again using the correct information.
Check if the chassis is powered on. If the chassis is not powered on, after powering it on, perform registration again.
Description
The LAN switch for connection to the network interface of the managed server for registration is not registered.
Corrective Action
Register the LAN switch for connection to the network interface of the managed server for registration, and then perform the operation again.
How to check and register the destination LAN switch
For Virtual Edition, refer to "C.1 Connections between Server Network Interfaces and LAN Switch Ports" in the "Design Guide VE", and check the LAN switch to be connected to the NIC of the specified managed server.
Refer to "B.3 Resource Definitions" in the "User's Guide VE", add LAN switch definitions to the system configuration file, and then import it again.
For Virtual Edition, refer to "C.1 Connections between Server Network Interfaces and L2 Switch Ports" in the "Design Guide CE", and check the LAN switch to be connected to the NIC of the specified managed server.
Refer to "B.3 Resource Definitions" in the "User's Guide for Infrastructure Administrators (Resource Management) CE", add LAN switch definitions to the system configuration file, and then import it again.
Description
The slot number or IP address of the specified LAN switch is incorrect.
There is a chance that the LAN switch mode has not been acquired successfully.
For a PY CB Eth Switch/IBP 10Gb 18/8 LAN switch blade, the account for the connection blade may not be configured on the management blade.
For the Converged Fabric mode of LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2, the representative virtual IP address of the fabric or the IP address for OOB may be incorrect.
For a PY CB Eth Switch 10/40Gb 18/8+2 LAN switch blade, it may not be possible to acquire the MAC address from the management blade.
When the Converged Fabric mode of a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2 belongs to the Leaf domain, registration may fail since the Leaf domain information is temporarily not recognized by the Master switch of the Root domain.
Corrective Action
Check the mounting position of the LAN switch blade and IP address, specify the correct slot number and IP address, and then perform the operation again.
Check whether the Mode displayed in the unit name (software name) in the resource details has been updated correctly.
For a PY CB Eth Switch/IBP 10Gb 18/8 LAN switch blade, configure the account for the connection blade on the management blade.
For details on the setup method, refer to the management blade manual.
For the Converged Fabric mode of LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2, perform operations specifying the correct IP address and management port.
When using a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2, check whether the MAC address has been acquired from the management blade, and perform the operation again. If the MAC address has not been acquired, collect this message and the investigation data, and then contact Fujitsu technical staff.
When the Converged Fabric mode of a LAN switch blade PY CB Eth Switch 10/40Gb 18/8+2 belongs to the Leaf domain, check whether the Leaf domain information has been acquired from the Master switch of the Root domain, and perform the operation again.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
[Virtual Edition] [Cloud Edition]
Description
When registering or modifying an antivirus software
An antivirus software resource with the same IP address and antivirus software identifier as the resource in obj that is being registered or modified already exists.
When connecting to the quarantine network or the business network
An L-Server with the same name as the L-Server described in the XML files for changing the network already exists.
In other cases
There are multiple resources with the name specified for obj.
Commands cannot be used to operate multiple resources with the same name.
When the resource to register is a cloning image, the image type of a different image has already been registered.
For details on the image type, refer to "14.7 Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Corrective Action
When registering or modifying an antivirus software
In Resource Orchestrator, only one resource can use the same combination of IP address and antivirus software identifier.
Change the IP address specified during registration or changing of the antivirus software, and perform the operation again.
When connecting to the quarantine network or the business network
The L-Server name described in the XML files for changing the network must be identical to the L-Server name contained in the name of the XML file for changing the network. Change either of the L-Server names so they are identical.
When connecting to the quarantine network
Execute the rcxadm avmgr quarantine command.
When connecting to the business network
Execute the rcxadm avmgr unquarantine command.
In other cases
Execute the command after changing the names of resources so no two have the same name.
When it is not possible to change the names of resources with the same name, perform operations from the GUI.
[Virtual Edition]
Description
There are multiple resources with the name specified for obj.
Commands cannot be used to operate multiple resources with the same name.
Corrective Action
Execute the command after changing the names of resources so no two have the same name.
When it is not possible to change the names of resources with the same name, perform operations from the GUI.
[Cloud Edition]
Description
When registering resources to resource pools
obj has already been registered in a resource pool.
When the resource to register is a cloning image, the image type of a different image has already been registered.
For details on the image type, refer to "Point" in "14.7 Image Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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
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.
When creating or starting an L-Server, while the manager is under a high load.
The corresponding operations may still be being performed. Therefore, check the progress of the operation in Recent Operations or the Event Log.
Corrective Action
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 ROR. Change the resource name and then try again.
When the resource being migrated is a cloning image, unregister the resource and then registered it in the migration destination resource pool.
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 "7.4 Changing Settings of LAN Switch Blades and LAN Switches (L2 Switches)" in 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.
When creating or starting an L-Server, while the manager is under a high load.
Check the following:
The hardware configuration of the admin server does not meet the requirements for a manager.
Refer to "6.2.1 All Editions" in the "Overview" and confirm that the hardware conditions described are met.
The CPU utilization of the admin server may be too high.
Check if any high CPU usage applications are running on the admin server.
Description
Login as a Resource Orchestrator user has not been performed.
Corrective Action
Perform the operation again after logging in as a Resource Orchestrator user.
If this message is displayed when executing a command, log in as an administrative user of Resource Orchestrator or with OS administrator authority and perform the operation again.
For details of the authority necessary for executing commands, refer to the following:
Refer to "Chapter 1 Overview" in the "Reference Guide (Command) VE".
Refer to "Chapter 1 Overview" in the "Reference Guide (Command/XML) CE".
For details of how to log in Resource Orchestrator as an administrative user, refer to the following:
Refer to "2.1 rcxlogin" in the "Reference Guide (Command) VE".
Refer to "2.1 rcxlogin" in the "Reference Guide (Command/XML) CE".
When operating managers in clusters, there is a chance that the shared disk for managers is not mounted.
Mount the shared disk for managers on the node the operation was performed on and perform the operation again.
Description
A communication error with the manager occurred during execution of a command.
Corrective Action
Check the following, resolve the problem, and execute the command again.
Check the Network Environment
How to Check
Check that the port number (service name: rcxweb, default: 23461) used by the admin server for the Resource Coordinator Manager service is not being used for another service.
Execute the following command on the server where a manager is installed to check the usage status of the port number.
Display process IDs using port numbers
Example
[Windows Manager]
>netstat -oan | find "0.0.0.0:23461" <RETURN> TCP 0.0.0.0:23461 0.0.0.0:0 LISTENING 2632 -> Process ID is 2632 |
[Linux Manager]
# netstat -lnp | grep ":23461" <RETURN> tcp 0 0 :::23461 :::* LISTEN 4095/httpd -> Process ID is 4095 |
Check that the process ID belongs to the httpd of Resource Orchestrator
Example
[Windows Manager]
>tasklist /svc /FI "PID eq 2632" <RETURN> Image name PID service ========================= ====== ====================================== httpd.exe 2632 ResourceCoordinatorWebServer(Apache) |
[Linux Manager]
# ps -fp 4095 <RETURN> UID PID PPID C STIME TTY TIME CMD root 4095 1 0 Jul18 ? 00:00:00 /opt/FJSVrcvmr/sys/apache/bin/httpd -k start |
Corrective Action
When it was being used by another service, change the port number to be used.
For how to change port numbers, refer to the following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
For Cloud Edition, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When "Data may have been corrupted during file transmission." is displayed, perform the same operation again.
When the port number being used by Resource Coordinator Manager is correct, or the corrective action above does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
A console control error has occurred in the process in the rcxlogin command for hiding passwords.
Corrective Action
If terminal software other than the standard Windows command prompt is being used, check the settings of that software.
If the problem occurs when using the command prompt or the corrective action above does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Description
Operation is not possible as the manager service is running.
The name of one of the running services is displayed for process.
Corrective Action
Refer to the following:
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide VE", and check whether the "Manager Services" and "Related Services" have been stopped on the admin server. If any server is running, stop it.
Refer to "2.1 Starting and Stopping Managers" in the "Operation Guide CE", and check whether the "Manager Services" and "Related Services" have been stopped on the admin server. If any service is running, stop it.
After stopping any started services, perform the operation that resulted in the error again.
[Windows Manager]
When operating managers in clusters, there is a chance that the cluster services for the manager and for the HBA address rename setup service are online on the same node.
Check that the cluster services are not online on the same node in the [Failover Cluster Management] window, and migrate the cluster service for the HBA address rename setup service to another node if it is online on the same node.
When other nodes have failed, perform the operation after recovery.
