This section explains the 65XXX message series.
[Description]
An error occurred while creating obj. obj has not been created.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while deleting obj. obj has not been deleted.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while modifying the information of obj. The information of obj has not been modified.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while moving obj. obj has not been moved.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while registering obj. obj has not been registered.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while modifying the configuration of obj. The configuration of obj has not been modified.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while moving obj between servers. obj has not been moved.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while collecting the snapshot image. The snapshot image has not been collected.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while restoring the snapshot image. The snapshot image has not been restored.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while importing obj. obj has not been imported.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while unregistering obj. obj has not been unregistered.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while starting the L-Server console.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while powering on the L-Server. The power is not ON.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while powering off the L-Server. The power is not OFF.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while rebooting the L-Server. Rebooting has not been performed.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while registering a user group. The user group has not been registered.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while changing a user group. The user group has not been changed.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
An error occurred while deleting a user group. The user group has not been deleted.
[Corrective Action]
Check the message number displayed in the details in the dialog, and perform the appropriate action.
[Description]
Registration failed as there is already a registered user with the same user ID.
[Corrective Action]
Enter a user ID that has not been registered, and register it.
[Description]
The directory server could not be communicated with.
[Corrective Action]
Check the following and take corrective action accordingly.
Check whether the settings for communication with the directory server are correct.
Settings for communication with the directory server can be checked using the rcxadm authctl command.
For details, refer to "1.7.10 rcxadm authctl".
When performing the following operations, it is necessary to register the certificate with Resource Orchestrator again.
Reinstallation of ServerView Operations Manager
Reinstallation of the directory server used by ServerView Operations Manager
Updating of the certificate of ServerView Operations Manager
Updating of the certificate of the directory server used by ServerView Operations Manager
For details on how to register a certificate, refer to "4.5 Installing and Configuring Single Sign-On" in the "Setup Guide CE".
Confirm that the directory server has been started.
Then perform the operation again.
[Description]
Refer to the explanation in "Message number 65841" in the "Messages VE".
[Corrective Action]
Refer to the explanation in "Message number 65841" in the "Messages VE".
[Description]
The user information registered in the directory service could not be changed.
The following causes are possible:
The specified password is not compliant with the user password policy of the directory service
[Corrective Action]
Check the user password policy for the directory service and ensure that the specified password is compliant with the policy.
[Description]
The user cannot be created as a user with the same name as the user user exists in the directory service.
[Corrective Action]
Check if the specified user ID is correct.
When using a user registered in directory service in Resource Orchestrator, create a user with the settings configured not to register a user in directory service using the directory service operation definition file.
For details on the directory service operation definition file, refer to "6.6.1 Settings for Tenant Management and Account Management" in the "Operation Guide CE".
[Description]
The user cannot be changed as the specified user user does not exist in the directory service.
A user in the directory service may have been deleted.
[Corrective Action]
Perform one of the following corrective actions:
Delete the current user, then create a new one.
After creating a user in the directory service, add it to the members of "cn=IflowUsers,ou=group,base_DN" group.
[Description]
A user cannot be registered as the group group_name does not exist in the directory service. There is an error in directory service environment.
[Corrective Action]
Create the group "cn=group_name,ou=group,base_DN" in directory service.
[Description]
Operations of obj_name in the directory service failed.
[Corrective Action]
Check the information in detail_message or the logs in the directory service, and perform corrective action for the error.
[Description]
Export to the file specified for file_name failed.
[Corrective Action]
After confirming the path to the specified file name, perform the operation again.
[Description]
The process was canceled due to one of the following reasons:
There is an error in the format of value for item in a configuration definition file, L-Server XML file, L-Server template XML file, resource pool XML file, image XML file, user XML file, network configuration information XML file, or the [Create an L-Server] dialog
An invalid character has been used
There is no value set
There is an error in the format of value for item specified in the XML file of disk resource configuration information for VM guests
There is an error in the format of value for item specified in the iSCSI boot information XML file.
The network resource name and the subnet name of the public LAN subnet are different
The network resource name and the admin LAN subnet name are different
When performing switchover of operating or standby storage, the content of the replication definition file is incorrect
The value for item that has been specified in the XML file to create tenant folders, or in the XML file of the L-Server has a formatting error
A tagged VLAN has been configured for a network resource for which PXE boot is specified
When PXE boot is specified, and an image is also specified
When retrieving the L-Server, the L-Server name has been specified incorrectly
The format of value for item specified in a VM specific information definition file contains an error
An L-Server cannot be linked with a virtual machine on the specified VM host
An L-Server cannot be created for specified VM host
Modification is not possible for an existing L-Server
One of the following is displayed in item:
Disk (Disk name)
Type
operation
Key value of the resource definition information
An element or attribute name of the L-Server XML file
An element or attribute name of the L-Server template XML file
An element or attribute name of the image XML file
A key value in the [Create an L-Server]
An element or attribute name of the resource pool XML file
Pool.name
There is an error in the value specified for the name attribute of the Pool element.
VmHost.ip
There is an error in the value specified for the ip attribute of the VmHost element.
VmHost (ip=IP address of the VM host defined in XML).Disks.Disk.name
There is an error in the value specified for the name attribute in the Disk element in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in XML).size
There is an error in the value of the size attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in XML).path
There is an error in the value of the path attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
An element or attribute name of the iSCSI boot information XML file
Network name, AddressSet name
The network resource name and the public LAN subnet name are different.
Network name, ManagementLanSubnet name
The network resource name and the admin LAN subnet name are different.
An element or attribute name of the XML file to create tenant folders
PXENetworkLink or net
ServerImageLink.id
ServerImageLink.name
NICs.NIC.NICIndex
The L-Server name when retrieved
processors shares
memory shares
processors weight
memory startup size
memory buffer rate
memory weight
Network auto
There is an error in the value specified for automatic configuration.
VmHost(api_type)
Parameter key name (customize file name)
ExternalPorts vlanautosetting
There is an error in the value specified for VLAN automatic configuration of an external connection port.
NetworkSwitchPort number
There is an error in the value specified for external connection port of LAN switch blades.
PhysicalLANSegment
There is an error in the value specified for physical LAN segment name.
An element or attribute name of the XML file of network configuration information
Password
VirtualStorage (virtual storage name)
max definable memory size
[Corrective Action]
Perform the operation again after checking the content displayed in item, and resolving the cause of the error.
Disk (Disk name)
The value of "value" in the disk information is incorrect.
When performing the switchover operation of operating or standby storage, check the content of the replication definition file.
Type
When importing a configuration definition file in the RCXCSV V2.0 format:
An invalid value is specified in the section name.
Correct the definitions in the configuration definition file.
When importing a configuration definition file in the RCXCSV V1.0 format:
Something other than Chassis, EtherSwitch, or ServerBlade is specified for the resource type.
Correct the definitions in the configuration definition file.
operation
A value other than "new", "change", or a hyphen ("-") is specified in the operation field, or there is a mistake in the operation area of the section header.
Only "new" or a hyphen ("-") can be specified in the sections after the line of "#Backup configuration".
Correct the definitions in the configuration definition file.
Key value of the resource definition information
An invalid value is specified for the displayed key, or there is a mistake in the displayed key value in the section header.
Correct the definitions in the configuration definition file.
For details on the values that can be specified for item, refer to "Appendix A Format of CSV System Configuration Files" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
An element or attribute name of the L-Server XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the L-Server XML file and correcting the definition.
An element or attribute name of the L-Server template XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the XML file of the L-Server template and correcting the definition.
An element or attribute name of the image XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the image XML file and correcting the definition.
A key value in the [Create an L-Server]
Perform the operation again after correcting the value corresponding to the displayed key value.
When IP address is displayed in value
An IP address outside the range that can be allocated to the network resource has been specified.
Specify an unused IP address for the network resource, and perform the operation again.
Pool.name
Review the value of the name attribute in the Pool element, correct the definition, and then perform the operation again.
VmHost.ip
Review the value of the ip attribute in the VmHost element, correct the definition, and then perform the operation again.
VmHost (ip=IP address of the VM host defined in XML).Disks.Disk.name
Review the value of the name attribute in the Disk element in the VmHost element for which an IP address of the VM host defined in XML is specified for ip.
VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in XML).size
Review the value of the size attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip, correct the definition, and then perform the operation again.
VmHost(ip=IP address of the VM host defined in XML).Disks.Disk(name=Disk resource name defined in XML).path
Review the value of the path attribute in the Disk element to which disk resource name defined in XML is specified for name, in the VmHost element for which an IP address of the VM host defined in XML is specified for ip, correct the definition, and perform the operation again.
An element or attribute name of the iSCSI boot information XML file
Perform the operation again after reviewing the value in the iSCSI boot information XML file and correcting the definition.
An element or attribute name of the resource pool XML file
Perform the operation again after correcting the value corresponding to the displayed key value in the resource pool XML file and correcting the definition.
Network name, AddressSet name
Specify the same value for both the network resource name and the public LAN subnet name.
Network name, ManagementLanSubnet name
Specify the same value for both the network resource name and the admin LAN subnet name.
An element or attribute name of the XML file for tenant folders
Perform the operation again after correcting the value corresponding to the displayed key value in the XML file of the tenant folder and correcting the definition.
PXENetworkLink or net
For the network resource for which PXE boot is specified, select a network resource that does not have a tagged VLAN configured.
ServerImageLink.id
When specifying PXE boot, images cannot be specified.
After specifying only PXE boot, perform the operation again.
ServerImageLink.name
The specified image is incorrect.
Review the specified image, and perform the operation again.
NICs.NIC.NICIndex
Check that sequential numbers starting from 0 are used for the NICIndex element value of each NIC element.
The L-Server name when retrieved
If an L-Server name was not specified when retrieved, specify the name and perform the operation again.
If an L-Server name was specified, check and correct the name.
processors shares
Review the CPUShare value defined in the L-Server template, import the L-Server template, and then perform the operation again.
When using a VM specific information definition file, review the value of processor_share, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the CPUShare element has been entered in the XML file, review the value specified for the CPUShare element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the CPUShare value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
memory shares
Review the MemoryShare value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_share, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryShare element has been entered in the XML file, review the value specified for the MemoryShare element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the MemoryShare value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
processors weight
Review the CPUWeight value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of processor_weight, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the CPUWeight element has been entered in the XML file, review the value specified for the CPUWeight element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the CPUWeight value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
memory weight
Review the MemoryWeight value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_weight, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryWeight element has been entered in the XML file, review the value specified for the MemoryWeight element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the MemoryWeight value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
memory buffer rate
Review the MemoryBuffer value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_buffer_rate, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the MemoryBuffer element has been entered in the XML file, review the value specified for the MemoryBuffer element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the MemoryBuffer value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
memory startup size
Review the StartupRAM value defined for the L-Server template, import the L-Server template again, and then perform the operation again.
When using a VM specific information definition file, review the value of memory_startup_size, modify the definition, and perform the operation again.
When an error occurs while creating an L-Server using commands:
If the StartupRAM element has been entered in the XML file, review the value specified for the StartupRAM element, and then perform the operation again.
When an error occurs when starting an L-Server:
Review the StartupRAM value defined for the L-Server, modify the L-Server using commands, and then perform the operation again.
Network auto
Perform the operation again after reviewing the value specified for automatic configuration and correcting the definition.
Parameter key name (customize file name)
Perform the operation again after correcting the value corresponding to the displayed parameter key value in the displayed customization file and correcting the definition.
VmHost(api_type)
Perform the corrective action according to the executed operations.
When linking a configured virtual machine to an L-Server:
Check the OS types of the virtual machine and VM host that are linked to each other, and perform the operation again.
When creating an L-Server:
Check if the OS type of the VM host for L-Server creation and the VM management software for managing the VM host are appropriate, and perform the operation again.
When changing L-Server configurations:
Check if the OS type of the VM host for L-Server creation and the VM management software for managing the VM host are appropriate, and the communication status with VM management software, and perform the operation again.
ExternalPorts vlanautosetting
Perform the operation again after checking the value specified for VLAN automatic configuration for the external connection port and correcting the definition.
NetworkSwitchPort number
Perform the operation again after checking the value specified for number for the LAN switch blade external connection port and correcting the definition.
PhysicalLANSegment
Perform the operation again after checking the value specified for the physical LAN segment and correcting the definition.
An element or attribute name of the XML file of network configuration information
Perform the operation again after checking the value corresponding to the displayed key name in the network configuration information XML file and correcting the definition.
Password
There may be an error in the value specified for the Password element in the user XML file or the value may have been specified for the Password element when not possible. Review the value of the Password element in the user XML file, correct the definition, and perform the operation again.
VirtualStorage (virtual storage name)
The value of "value" in the virtual storage information is incorrect. When performing the switchover operation of operating or standby storage, check the content of the replication definition file. When performing switchover operations using Disaster Recovery after damage, ensure that virtual storage exists on the backup site and is not registered in the pool.
max definable memory size
When using a VM specific information definition file, review the value of max_definable_memory_size, modify the definition, and perform the operation again.
For details, refer to "VM Specific Information Definition File" in "E.1.1 Definition Files" in the "Setup Guide CE".
[Description]
The process was canceled because the specified resource value is not registered.
The resource value may not be included in the access scope of the user or user group that performed the operation.
When value is "image key = xxx"
The process was canceled because the registered cloning image was deleted due to deletion of a host from VMware vCenter Server.
When "(create)" follows after value:
The process was canceled because one of the following applies to the specified physical server:
The specified physical server does not exist
The specified physical server is not registered in the resource pool
The specified physical server is already assigned as an L-Server
The specified physical server is already assigned as a spare server
The physical server resource does not exist in the resource pool
When "(Spare)" follows after value:
The process was canceled as the resource specified as a spare server does not exist.
When "(Primary)" follows after value:
The process was canceled as the resource specified in the physical server usage change does not exist.
The specified physical server does not exist
The specified physical resource pool does not exist
The physical server resource does not exist in the specified resource pool
When value is "PhysicalServer"
When the resource type is "PhysicalServer", the physical server which satisfies the conditions may not exist or may be in an incorrect status.
When "(Storage pool)" follows after value:
The process was canceled because one of the following applies to the specified disk resource:
The specified disk resource is not registered in the resource pool
The virtual storage resource in which the specified disk resource was created is not registered in the resource pool
When "value" is "IOVirtualOptionPool"
The process was canceled because one of the following applies to the specified address set resource:
There is no address pool to store the address set resources to allocate to L-Servers
There are no unused address set resources in the address pool
When value is "NetworkDevice", and "(ip=IP_address)" follows after the value:
The network device with the admin IP address IP_address is not registered.
When value is "Server", and "(ip=IP_address)" follows after the value:
The server with the admin IP address IP_address is not registered.
When value is "NetworkDevice", followed by "(ip=IP_address, port=port_name)":
There are no ports with the port_name for the network device registered using the admin IP address, IP_address. Check the "port name" displayed in the resource details of the network device tree.
When value is "VmHost(ip=IP address of VM host defined in XML)"
The process was canceled as the VM host which has the IP address defined in the XML does not exist.
When value is Pool(name=storage pool name defined in XML)
The process was canceled as the storage pool defined in XML does not exist.
[Corrective Action]
You cannot modify by specifying an unregistered resource name.
Perform the operation again after specifying a resource name that is already registered.
When a resource name already registered is specified:
There is an error in the key value for the resource name in the section header. Perform the operation again after correcting the configuration definition file.
When registering new resource information with the specified resource name:
Change the operation to "new".
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 definition files, refer to "Configuration when Creating a Physical L-Server without Specifying a Model Name in the L-Server Template" in "D.5.1 Definition Files" of the "Setup Guide CE".
When value is "image key = xxxx"
Perform the operation again after restoring the deleted cloning image and using a command to modify the L-Server configuration. When modifying the L-Server configuration, set an appropriate value in the ServerImageLink element.
Perform the operation again after setting the access scope of resources.
When value is "PhysicalServer"
A physical server that matches the specified conditions may not exist, or the status may be invalid. Check that the L-Server definition and the physical server in the specified server pool meet or exceed all of the following conditions.
Number of CPUs
CPU Clock Speed
Memory Size
Number of NICs
Number of FCs in the FC connection pattern
For the recovery procedure, refer to "Message number 62508".
Check that the network configuration of the admin LAN matches completely, including NIC redundancy.
A physical server cannot be found that has the number of FCs specified in the FC connection pattern. Refer to "4.3.1.2 Storage Configuration" in the "Setup Guide CE" for information on how to obtain the FC information for the physical server.
When "value" is "IOVirtualOptionPool"
Check the following:
There is an address pool to store the address set resources
There is an unused address set resource in the address pool
There may be differences between the values in the definition files and the actual configuration information of that server.
Check that the correct values have been entered.
For details on the definition file, refer to "Appendix I Definition Files" of the "Setup Guide CE".
When value is "NetworkDevice", and "(ip=IP_address)" follows after the value:
Register the network device (for which IP address is used as the management IP address) as a resource, and retry.
When value is "Server", and "(ip=IP_address)" follows after the value:
Register the rack mounted server (for which IP address is used as the management IP address) as a resource, and retry.
When value is "NetworkDevice", and "(ip=IP_address and port=port_name)" follows after the value:
Check the port name (the one displayed in the resource details of the network device that is registered in an IP address that is a management IP address), change it to a correct port name and retry.
When value is "VmHost(ip=IP address of VM host defined in XML)"
Define the IP address of an existing VM host in the XML and perform the operation again.
When value is Pool(name=storage pool name defined in XML)
Define an existing storage pool in the XML and perform the operation again.
[Description]
The process was aborted as a file with an extension that is not the target of operation was specified.
[Corrective Action]
Specify a file with an extension that is the target of operation, and perform the operation again.
[Description]
The specified file already exists.
[Corrective Action]
Change the file name and perform the operation again.
